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

Cannot switch of Elevation Correction?

Former Member
Former Member
Hi,

I am still on the old connect site. For the last tour I uploaded from my Edge 500, the Elevation Correction was suddenly enabled, though I never used that before. In my area the correction does not really give good results, so I'd like to stick with what the device reports. But I cannot even turn it off, if I click on the Disabled under Additional Information in the activity view nothing happens.

Does anybody has an idea how I could remedy that? (I know I could manually change the elevation gain for the activity, but I don't remember the actual value)

Thanks!

Cheers, Robert
  • You must load the activity with Garmin Communicator Plugin ("upload" button on the web site) instead of Garmin Express... this worked for me.
  • Former Member
    0 Former Member
    That's what I did, I don't use Garmin Express.
  • There is a long thread regarding this going on in the Edge 510 forum.
    https://forums.garmin.com/showthread.php?72836-Elevation-Corrections-Enabled-bug-anyone-else-got-this
    It seems the elevation correction for activities on the Garmin Connect website is stuck on "enabled" by default and it cannot be changed to "disabled". The Garmin Connect Mobile App on the smartphone also reflects the value from from the website. The Edge 510 unit itself shows the elevation as measured by the unit and without the correction applied by the Garmin Connect website. Most of us prefer to use the elevation as measured with the barometric altimeter in the GPS unit rather than the calculated elevation that Garmin Connect is forcing as default which cannot be changed back to "disabled."
  • Former Member
    0 Former Member
    Thanks for the link, that's interesting.

    It seems the issue did not affect all servers all at once. While for the guys in that thread it started already earlier, I still did a ride on March 8 where it uploaded with disabled elevation corrections, and then only with the next ride on March 12 it uploaded with enabled corrections.

    Cheers, Robert