Option to undo Elevation Correction and revert to Barometric Altimeter

I'd like to be able to reverse the elevation calculation.  I was curious if my barometer was shorting me on my Garmin 500, so I had Strava recalculate my elevation.  It ended up being about 100 feet shorter in elevation, so I wanted to go back to using my barometer.

Currently the only way to do this is submit a ticket and have a customer service rep do this.  This erases the ride name, resets the bike chosen, erases all Kudo's and comments.  Kind of a hassle too.



  • Official comment

    Hi Everyone!

    Good news! You can now revert back to your original elevation by clicking Elevation (?) again. 

    If you'd like to learn more about Elevation click here

    If you'd like to see some of the frequently asked questions about Elevation click here

  • Unfortunately you don't always suspect your elevation until hours later - after other folks have uploaded their data.  Then to delete and reupload will most likely cost you kudos' and comments.

  • The work around suguested is not ideal, because deleting the ride and adding it again removes all kudos & comments! no warning that there is no roll back option!
  • Same same - my Garmin 500 recorded a realistic ~1600m elevation gain (verified against about 4999 others riding the same Gran Fondo route). I clicked the elevation correction and now I've gained 3300m.

    So, it comes down to whether I want to keep accurate records (ie delete the activity and upload it again), or whether I value the comments and kudos.

    I'm more of an accurate data kind of guy... deletion time...

    It's a bit rubbish and needs to be fixed. Months ago.

  • It's over 2 years since this was submitted. Why is it still not fixed? How hard can it be? There are 2 simple options:

    1. When elevation is corrected, save the original value and give the user the chance to pick their preferred outcome.

    2. Allow the user to re-upload the file. Currently Strava recognises when a file is the same as an existing one and won't upload it. Instead, it could ask "This workout already exists, would you like to overwrite elevation data only in the existing workout?" This would keep everything else (Kudos, comments etc.) linked to the workout. 

  • Ride with GPS allows this option to turn Elevation Correction back off if you don't agree with it. They've offered that for years, before I committed to Strava. Come on Strava - it's not that hard to do and it's been 2 years since these posts and replies. 

  • Come on Strava: What's happening here? Nothing for two years?

    Seems the "correction" algorithm changed recently, too. It used to be that we would hit that if we wanted to cheat and get a bit of extra elevation. Now it's inconsistent: Seems to be affected by the recording frequency, because I can go on the same ride with friends, and our barometric altimeters will be off one anther by 1000ft or so. Mine is always the lowest. Then if we hit correction, the "corrected" elevation will be even more off between us (and it tends to reduce my elevation gained by 500 ft or more). I record my rides at 5sec, and most people record at 1s or 'smart'.

  • This issue was reported 2 years and 9 months ago. Nothing has been done. Do you have any engineers at Strava? Have you lost all your source code?

  • At least, a simple warning could be on screen telling the user that this option can not be undone. So simple!

  • I can see where you're coming from Jeff! A simple "revert to barometric altimeter data" option would work great. 

    In the meantime, another option is to delete and reupload the activity yourself - and you wouldn't have to write into us. You would still erase comments and kudos however. 

  • I have the same problem and am not happy with the idea of deleting and loosing all my kudos & comment. May be it is an option that should be remove is in my case it does not work.

  • I was going to submit the same request :-)

    I use the Strava Android App, and I noticed that immediately after the ride the Elevation is "almost" correct, but then the Strava Elevation auto-correction kicks in and it double the Elevation!!

    For example, a ride I know ha an elevation of around 1200 mt., first the Strava show 1455 mt., but later it skyrocket to an absurd 2843 mt.(I've uploaded a screenshot before and after Elevation auto-correction) ...

    If i try to export the gpx from Strava and import into Sport Tracks with Elevation Correction plugin it became a more precise 1115 mt. ... so something is totally wrong with auto Elevation Correction, and having a setting to disable it would be great ...


  • I wondering why it taking so long to fix it ... The Strava Elevation Correction is the worst things on this great site. I don't understand why they don't make it simply optional. Today ride was 1089 mt., but after Strava recalculate it, it became an absurd 3531 mt. There really is no need for this. Make it optional, or take it off at all till the Elevation Correction really works (if ever ...). Thanks.

  • The elevation correction is becoming a running joke on strava, especially on climbing challenges. That makes climbing challanges kinda meaningless as you know the data is fake. Same thing happened on todays ride, the data from the phone itself was super accurate for a phone, right on the road and no excessive bumps. I was really glad to see such accurate results but then, strava elevation correction kicked in and now it looks just horrible and provides unusable data for elevation. I mean, you must know how faulty this algorithm is, it's not so hard to make it optional ! Included the picture of before and after, as you can see it added 600m+ of elevation on what was already like 200m+ of addition elevation due to gps coverage. So now it's almost 2x the real elevation gain! By this "calculation" I only need to ride around (probably much less then) 3500m of elevation to complete the"Rapha Rising: Three Ranges" challenge of riding 8,800 meters. Please fix it as it's super annoying for android and iphone users!

  • I would really like a feature to toggle between elevation correction enabled and disabled.  My particular case is that I use a Garmin Edge 510 which has a barometric altimeter.  This device allows me to automatically upload my activity data to the Garmin Connect website via bluetooth connection between the Edge and my smartphone and the internet connection of the smartphone.  I then like to transfer this data to Strava without having to manually hook my Edge up to the computer via USB.  There are various ways to do this, but many of them end up with Strava applying an elevation correction and there isn't a way to revert back to the actual data which was recorded with a barometric altimeter.  I can do manual export of the ride from Garmin Connect and upload to Strava of that file, but Strava will call it a "mobile" device and apply elevation correction.  I have discovered the service from that seems to work really well, but activities transferred in that manner don't seem to have a device tag at all and Strava applies the elevation correction. seems to maintain the Edge 510 device tag and therefore no elevation correction is applied, but that service takes an unknown amount of time to transfer the activity which is something I want to move away from.  Please either allow for elevation corrections to be toggled on and off, or allow for manually selecting the recording device so it could undo the default application of an elevation correction and revert back to the actual data in the activity file (I'm not sure if that second suggestion would really work, just an idea!).  

    For example, the following activities are all recorded with my Garmin Edge 510 with barometric altimeter and this is how Strava treats the data depending on how the file was handled.

    File was exported from Garmin Connect as a GPX, then uploaded manually to Strava. ->

    File was "synced" between Garmin Connect and Strava using Tapiriik. ->

    File was "synced" between Garmin Connect and Strava using Copymysports. ->

  • Pretty hard ride yesterday.

    My Garmin 810 recorded: 3.205 m elevation gain (the race organization said: 3.204 m), so I think it was pretty accurate :)))

    After uploaidng it to Strava I had 5.272 m. I was really upset... it's a joke.

    Please let the option to reverse this correction.... well, I don't know why we all calll this correction.

    As many user, I think this is by far the worst thing about Strava.

  • Along with the option of which dataset to use, it would be great to show which dataset has been used on the ride page. A small green, amber & red light alongside the elevation figure perhaps? (Barometric, GPS, strava)

    This would hopefully assist to deconstruct the growing ameorta that seems to exist in the climbing challenges where nobody appears to be saying that their elevation has been corrected using stravas algorithms despite using barometric altimeters. Most of us here know these are the wrong figures (embarrassing wrong actually) & it makes these challenges more & more inaccurate.

    I actually heard the term 'elevation doping' in regards to this the other day...

  • Thanks for your response Elle, your input is appreciated.

    your screen shot definitely shows where it is clear for ones own rides, but what I meant was an indicator for other users rides. I do hope more options & accuracy become available in regards to these elevation discrepancies. thanks!
  • My 2 cents:  I think the smart people at Strava need to come up with a better algorithm for elevation correction.  I have two devices I experiment with (Android cell phone, and a Garmin 510).  In some areas where I ride (very populated San Diego, by the way), my non-barometric elevation data is a joke.  Sometimes it's exaggerated by a factor of 3!  One ride in particular I have scientifically determined (analyzing from many sources) to be 1500' of climbing in a new development surrounded by steep hills.  My Garmin 510 tells me it's 600', which is not correct.  My Android phone tells me it's 3000' feet, which is also far from correct.  The truth lies between these two vastly different numbers.  For some strange reason the corrected elevation profile looks like the world's scariest roller coaster when the roads are actually pretty flat and smooth.  They certainly don't go up/down 50 feet every 300 feet, like the profile suggests.  Please improve your algorithm to make this more accurate!  And don't get me started on the elevation data going over bridges!  Going back to the Garmin 510 (which has a barometric altimeter), not sure why it is so inaccurate (on the low side) in this one particular neighborhood.  I recently purchased it specifically for its advertised GPS accuracy and altimeter.  Please, please, please improve your elevation algorithm!!!  I know it's mathematically possible.  Maybe one suggestion is to give the user the ability to adjust some parameters before the elevation correction to smooth out the jaggedness of the elevation correction (perhaps distance between recalculated track points, or specifying a maximum slope).  Thanks!

  • Please, you should try to fix this problem!! The Strava Elevation Correction is the worst thing on this GREAT and ADDICTED sport app I ever had. I did a ride which the elevation was  aproximately 2000m and after uploading the workout to Strava the elevation increased up to more than 3000m.  Yesterday my ride was 450m.., but after Strava recalculate it , it became 733m. I have a Suunto Ambit3 sport (without barometer) and I usually compare my elevation with other elevations from my friends (who whas barometric devices) and the elevetion is pretty the same till I put it in the Strava.

    It drives me crazy, please maket it optional or take it off at all till the elevation correction really works. 


  • Same problem. Delete and reupload doesn't work for me (Suunto Ambit2) - when I upload automatically from Movescount, the device is shown as the Ambit2, but after a manual upload, it just says "Mobile" and has corrected elevation again.

  • I have even moe bizarre situation. My friend and I, both garmin 510, do the same ride, and he routinely gets 100's of feet more of climbing (like 2100 vs 1700, that's like almost 25% more)

    any ideas? ride on garmin connect have the same (or very similar) elevations

    this is bizarre

  • Sigh ! This is typical of all software companies. Addressing issues is never a straightforward Yes or No. Am utterly disappointed with STRAVA



  • just tried something that seems to work...In garmin connect export ride as export original.  unzip the zip file..inside is .fit file .. i uploaded this into garmin and elevation was exactly the same..bit of mess on but only takes couple mins..  did i just get lucky..??!!  btw i'm using an edge 510 

  • +1 i dont know why this has not be added yet. some times stravas correction are spot on compared to garmins connects corrections, and some times they are way off for no reason. so a simple revert button would be great

  • I just did a "Correct Elevation" on a ride with a 920xt, just to find out that the Strava elevation is HORRIBLE on that particular set of roads. It is full of elevation spikes which are not real.

    PLEASE add the capability to revert the Elevation correction......

  • I ride a local park all the time (Red Rock Canyon in Colorado Springs), and something is seriously wrong with the data that Strava uses to calculate elevation gain.  There are at least a couple major glitches where Strava's elevation data jumps up a hundred feet or so where in reality there is no climb at all.  The good news is I get about 300' of bonus "climbing" every time I revert to Strava's calculation.  Is there any way to report bad data for rides like this that are otherwise well documented?

  • it's been nearly 3 years since the original idea was posted, and as you can see, the lack of it hurts a lot of people. would it be soooo hard, to implement the undo option?

  • All I can say is I am glad I am not paying for this, who would pay for something that can't show your device elevation profile correctly, can't calculate elevation gain, can't show heart rate correctly, scales graphs wrong. If I can graph the gpx file in a spreadsheet surely they can sort their site out.

  • Replying to follow this thread if there is ever an update. I too would love to be able to toggle elevation correction in some cases to see if the Strava correction is "better" and revert if not.

    In my case, all of the devices I use have barometric altimeters and are generally good. Sometimes a storm messes with pressure and I get clearly bad elevation data. In those cases I'd like to see if Strava is better (e.g. locations I've hit multiple times like start and end are generally about the same elevation) but trail runs in the mountains don't always seem improved.

    Deleting and re-uploading, as noted, is not a good solution. Seems like the toggle should at least be enabled for sources with barometric elevation data. Garmin Connect and Sport Tracks (and probably just about everywhere) allow toggling the elevation data, and it seems the customer service folks have access to that feature, so is there some reason Strava feels users should not have access to it?

Please sign in to leave a comment.

Didn't find what you were looking for?

New post