Automatic Elevation Recalibration during an activity??!

I think it doesn't work. I have the same problem with a lot of weird elevation.

Why do you want to correct the elevation data? There is already a built in correction in the watch that gives you the elevation up/down and the function in GC is mainly for GPS based altitude and for devices that doesn't do the magic based on barometric elevation.

I have continuous calibration enabled and it works for me. For elevation I get what I got with my F3 for years and I find the values reasonable.

As a note there is a known bug with the altitude recording that also affects the elevation but the continuous calibration isn't the problem. It is something else, or a combination of things. I got it a couple of times but since a restart of the watch it has been ok.

https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/193733/elevation-question

Yes, I think the OP is confusing Continuous (automatic) Elevation Calibration with, with Elevation Correction.

Continuous Elevation Calibration, which is what the OP sounds like they are describing, has worked flawless on my watch. In fact, the elevation modelling is FAAARRRRR more accurate than when I don't use it. With it turned on, it's never been off by more than 4 meters, and my elevation charts make a lot more sense now. It is using the GPS signal to determine the elevation calibration, not the map file. GPS signals, people often don't realize, aren't just determining your X-Y coordinates, they also can determine your Z (vertical) elevation - it's only as accurate as the X-Y calculation (which as we all know can be off by like 5-10 meters), but that's usually good enough. The Watch primarily still uses the barometer for elevation data, and just periodically checks it against the GPS data to make sure the weather and other factors haven't caused it to drift.

Elevation Correction, which is a Garmin Connect feature that you would use after an activity is completed and saved, basically overrides the watch's recorded elevation data, and replaces it with the elevation data from their map. It will be less accurate, because map elevation data is low-resolution, and when you cross a bridge it will think you were on the water/ground below the bridge.

I would never recommend using Elevation Correction, unless for some reason the elevation data recorded on your activity is way far off. I would always recommend using continuous elevation calibration in the watch, however, as in my experience it's been impressively accurate.

https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/195689/fenix-6-series---sensor-hub-beta-v2-53---fixes-stepped-elevation

For as far as I know the continuous calibration uses the built-in DEM (digital elevation model) and not GPS to correct the elevation offset (compatible models only of course). GPS is far less accurate in vertical than in horizontal directions, see https://support.garmin.com/en-US/?faq=QPc5x3ZFUv1QyoxITW2vZ6.

True, but the DEM model in the mountains is even less accurate. So I suggest to turn the autocalibration OFF when you need accuracy in elevation measurement.

C.sco said:

I would always recommend using continuous elevation calibration in the watch, however, as in my experience it's been impressively accurate.

I am curious, do you use it when you're in the mountains?

From Garmin (I cannot remember anymore where I found this):

"We’ve improved the in-activity auto calibration for the altimeter by leveraging the DEM provided in our preloaded cartography data. Our new default is now “Continuous” mode (Settings > Sensors > Altimeter > Auto Cal. > During Activity). This continuous calibration setting enables an algorithm that uses both DEM and GPS elevation as references to offset any altimeter drift due to weather-related pressure changes during an activity. These improvements are provided in a long-term manner without sacrificing the main benefit of a separate altimeter sensor on the device: the ability to accurately track short-term elevation change and provide responsive elevation-related data during an activity (e.g. hill repeat workouts). Note: the At Start calibration also occurs when Continuous is enabled."

For my experience when hiking, it is much much better to turn it off. Every time you pause your activity, and then unpause, it recalibrates - and this usually means it goes several tens of meters off. You end up with a track with many many discontinuities in elevation.