Unable to disable Elevation Corrections

You can correct elevation by doing a full edit. Still annoying that they broke the disable button.

Still not working and after waiting almost a week for support to reply to my support ticket they asked completely pointless questions.
Over three weeks and still not fixed, poor performance from Garmin but worse poor release testing.

I have an ironman race coming up, one would expect you have a industry leader device for which you pay premium so you get peace of mind. Completely failed on their upgrade, cannot disable elevation correction and it expects me to believe that I climb mt. Everest every day and jump down before I even complete my climb. Frustrating.

I have this problem. I have an Edge 500 with a built in barometric altimeter. On previous rides when I uploaded to Garmin Connect the elevation corrections were always set to disabled by default (which I understand to be correct due to the built in altimeter). Lately when I have been uploading, the elevation corrections are showing as enabled. If I click disable nothing changes. The elevation data that shows in Garmin Connect is also different to the data on my device.

Anyone had this problem and is there a way to manually disable elevation corrections prior to uploading any future rides? - whether that be a setting on Garmin Connect or my Edge 500?

I'm not sure whether the problem occurred since I upgraded the software on my device or since Garmin Connect have been upgrading all of the software.

Any help or advice would be much appreciated.

Thanks

AR01UK, this is the known bug referred to in this thread. It wasn't part of the upgrade, it appeared prior to that. It is a problem with GC, not the unit or the app.

I suggest trying to file a support request with www.garmin.com... I can't because I get the http 500 error message, but the more the merrier.

This is a known error and started sometime between 3 and 5 Feb probably during the GC maintenance shutdown. I have an Edge 510 with exactly the same issue.

However: I reckon it might be a button display issue. Make a note of your elevation gain, click Disabled and see if the gain changes. I reckon that mine actually defaults to Disabled even though it says Enabled, based on the shape of my regular commute (the local survey data are incorrect on part of a climb).

When I repeatedly click Disabled it toggles between Enabled and Disabled.

I think you are right, Ive only had mine a few days and I was playing with manual setting of elevation. I got it wrong and recorded a few rides well below see level. So if the elevation correction was actually affecting the data it would have over written my subterranean adventures.

I have downloaded an Altimeter app and have done some research for local land mark heights. I have now saved a fair few markers with correct elevations I hope. Will see if that helps the accuracy issues. So far so good it seems but I have only done one short ride. Did read somewhere that if you want the most accurate data recorded, you should set the elevation before you set off on each ride?!

Yesterday I had a reply from Garmin support, they told me to delete IE temporary files or cache on other browsers.
Even gave instructions on how to do it in different browsers.
Did not make a blind bit of difference on any browser, even a newly installed IE11 had the problem.
I can only assume Garmin support are using the "100 ways to delay the customer whilst we try and fix the real problem" book.
Not very satisfactory, in fact over a month now and no sign of any fix.

Now the button seems to be working. It's possible to enable/disable elevation corrections, but the numbers aren't correct, and different from my numbers on Edge 200. Over a month and still this bug?!? Is that difficult fixing this?!?

Yep, it is now working again.

What do you mean 'the numbers aren't correct' dracula_pt? The Edge 200 (I think) has a gps altimeter, which is reasonably inaccurate. Enabling or disabling elevation correction will switch you between your inaccurate gps and the local survey data of unknown accuracy. This is not a bug.