Revert to GPS-based altitude when corrected elevation is erroneous

Although GPS altitude may be fairly inaccurate, modern GPS should filter movement to at least provide a more reasonable elevation profile than topo maps in certain areas.

For example, this route

http://www.strava.com/activities/135105550

produces an elevation gain of over 3000 feet, when in reality it the correct elevation profile is probably under 2000 ft.  My phone's GPS produces better results than this. 

I would like to be able to choose to use the GPS altitude for routes with erratic elevation topo profiles.

49

Comments

13 comments
  • I've actually drawn graphs of elevation profile of my one ride. I recorded it with Wahoo Fitness app on Samsung Galaxy S3, because with Strava app I couldn't anyway get GPS altitude recording out.

    Visual inspection shows that at least for me GPS altitude would be much better that sharp spikes produced by Strava elevation "correction". In addition to comparing those I made a graph also by using Google's elevation data (public API), which was much more flat.

    Funny thing is that if I go to a group ride with others using Garmins with barometers, and I record with Strava Android app, the end result is that Strava shows we haven't been riding together in the group ride but still gives us different elevation profiles! I guess if Strava would invest a bit for generating better elevation database, they could do this easily by just using those rides with barometer data in their database and use those barometer derived elevations to correct elevation for the rest.

    0
    Comment actions Permalink
  • Well, Galaxy S3 has a barometric sensor, so it's no surprise that your recordings are more accurate than Strava's "corrected" elevation profile. Anyway, an option to revert the "correction" to the original recorded data would be much appreciated!

    0
    Comment actions Permalink
  • Definitely need this. But what I don't understand is how Strava comes up with its crazy elevation adjustments sometimes, given it's usually pretty good when using the route builder.

    0
    Comment actions Permalink
  • Yes, I have a cross race where all those who uploaded from a Garmin had the corrected altitude, mine show Zero, yes nothing! So an ability to edit the altitude would be handy.

    0
    Comment actions Permalink
  • +1 to let the user disable elevation correction

    0
    Comment actions Permalink
  • Rode my first century yesterday and I uploaded the ride to both Runkeeper and Strava.  Runkeeper shows 4000+ feet of climb.  Strava shows 72.  Gee thanks Strava.

    0
    Comment actions Permalink
  • will this issue called has feature ever see the day of light ?  why does it takes ages to implement from strava (;

    0
    Comment actions Permalink
  • Unfortunatly elevation correction does a bad job here in switzerland. My ride are usualy inlated by 15% to 20%. So I add my vote to this feature. 

    Regards,

    0
    Comment actions Permalink
  • I have simply had it up to here (raises hand to my 5-7 frame about eye-level). Strava MUST hire actual monkeys to do their code because they cant read a simple GPS reading worth a flying fuck! Other sites (Garmin, Ride with GPS, Wahoo, Endomondo) are all within 5-10 ft of altitude totals for a given ride. Not Strava. Nooooooooooooooooooo... they are off as much as 200 ft! WHY THE HELL DO CHALLENGES if the altitude values are inaccurate?

    Strava, YOU FUCKING SUCK!!!

    0
    Comment actions Permalink
  • I actually have the problem with my Strava and Garmin Connect. I use a forerunner 735XT which is GPS based and not barometric. I ran with a pro trail runner in the weekend and he uses a Fenix 3, which has a barometric meter. We did some hill repeats with the hill being around 34m high. When I uploaded my run, with the  elevation correction enabled, Garmin connect gave me 59m and Strava gave me 62m. The Fenix 3 showed an elevation of  119m which is pretty accurate considering the run we did. So 119m should be correct. When I disable the elevation correction in Garmin Connect is shows 117m which is pretty accurate. How the hell can the elevation correction be wrong, when it is supposed to make it right?

    Any idea how I can fix this? And I don't want to buy a Fenix 3 :)

    0
    Comment actions Permalink
  • Yes, would be nice to revert.
    Had a couple of rides recently where due to large temperature swings I ended up at an elevation of -150m, although total elevation was reasonable.
    After attempting to elevation correct, it is now wildly overestimated (almost triple what it should be) and i'd like to go back to gps calculated values

    0
    Comment actions Permalink
  • Hello I ride around a lake with an iPhone SE and strava shows 900 meters of climb - so it is destroying my good data each time. Please can we have some feedback on this? Should I use an app that is not even storing the data I give it? Thanks for any response.

    0
    Comment actions Permalink
  • This is an old thread but I would like to add some extra info: in the Netherlands we like to participate in beach-races, which run anywhere from 20 to 120 kilometers, solely on the beach. I am currently preparing for a short race (34 km) in januari and therefore, I do some rides on the beach. I noticed yesterday that the altitude values are way off. Our beaches are very flat, mostly at or slightly above sea level. Never more than a few meters variance. I know that Strave throws away my altitude data (Samsung Galaxy S6), but on a beach I would expect the Strava data to be more or less at sea level for the whole ride. A did a ride yesterday and Strava shows a rather bumpy ride, with the altitude varying between 2 meters above sea level and 15 meters above sea level. One indication this is Strava-corrected data is that we did a two-way ride (second part is the same as the first part only in the other direction. The altitude data is mirrored on the way back, which makes sense. However: if this is Strava-data, how is it possible that there are such large variances in height?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post