This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

REQUEST: Permanently override Barometric Altimeter data

FEATURE:
Permanently offer to override the barometric altimeter data with GPS elevation data.

I currently have a Fenix 3HR and find that the altimeter data recording using the barometric data slowly drifts. For example, during a hill session, I can lose around 5feet per lap. Over the space of the session, this slowly adds up to over 50feet of error.

I know that you can request that a particular session uses GPS data instead through Connect online but this isn't a Global setting. I would like to see a Global setting to permanently use GPS co-ordinates and associated Elevation data instead as I find this much more accurate. I'm a little confused as to why this isn't already an option since the functionality is already through on an session-by-session basis and it is obviously there for devices that do not have the Barometric altimeter.

I contacted Garmin through chat to be sure I wasn't just missing something but nope, it just doesn't exist if your device is already an ABC watch.


Current watch: Fenix3HR Sapphire
  • It used to be a device level option in GC web.
  • Former Member
    0 Former Member
    TrippyZ Unfortunately, if your watch has barometric altimeter, Garmin has the default for elevation correction disabled. You can enable elevation correction after you complete an activity to view that activity only, but it defaults back to disabled for the next activity. If the option to turn off the barometer data for elevation were possible, I guarantee Garmin would have less complaints and exchanges from people who come to the conclusion their device is defective because they don't fully understand how a barometric altimeter affects elevation; or as in the OP's case, they understand how it works, but they just don't want that data.
  • TrippyZ Yeah, I saw that on a Reddit thread. The Old GC classic website but it's now been removed. No idea why.