Huge Discrepancy in Elevation Gain between Wahoo and Strava iOS Apps
#51
Method to My Madness
Thread Starter
Join Date: Nov 2020
Location: Orange County, California
Posts: 3,867
Bikes: Trek FX 2, Cannondale Synapse x2, Cannondale CAAD4, Santa Cruz Stigmata 3
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 2068 Post(s)
Liked 1,561 Times
in
1,082 Posts
#53
Senior Member
Join Date: Jul 2015
Location: reno, nv
Posts: 2,329
Bikes: yes, i have one
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 1152 Post(s)
Liked 1,197 Times
in
697 Posts
i did some research a while back while writing my own app...
some interesting stuff regarding elevation and how strava handles it:
https://support.strava.com/hc/en-us/...-Your-Activity
and this if you need force barometric data for devices that don't support it or for those that do but strava has not caught up yet:
https://developers.strava.com/docs/uploads/
i consider this a bit of a hack since any elevation data can be uploaded this way. i think i only use this for one case and all others are just .fit files since they are smaller.
some interesting stuff regarding elevation and how strava handles it:
https://support.strava.com/hc/en-us/...-Your-Activity
and this if you need force barometric data for devices that don't support it or for those that do but strava has not caught up yet:
https://developers.strava.com/docs/uploads/
i consider this a bit of a hack since any elevation data can be uploaded this way. i think i only use this for one case and all others are just .fit files since they are smaller.
Likes For spelger:
#54
Senior Member
Try riding a completely flat route along the coast and use the GPS to determine altitude. The resulting profile should be flat. If its not you have an indication how much GPS derived altitude data deviates.
#55
Advocatus Diaboli
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,702
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4800 Post(s)
Liked 1,547 Times
in
1,014 Posts
Does Strava with their elevation correction, as an example, rely on their presumed database of eg. hundreds/thousands of past rides along same routes where a barometric altimeter provided inputs -- and conceivably Strava could average those inputs for a theoretically more accurate correction?
#56
I'm good to go!
Join Date: Jul 2017
Location: Mississippi
Posts: 15,288
Bikes: Tarmac Disc Comp Di2 - 2020
Mentioned: 52 Post(s)
Tagged: 0 Thread(s)
Quoted: 6352 Post(s)
Liked 4,955 Times
in
3,413 Posts
Does Strava with their elevation correction, as an example, rely on their presumed database of eg. hundreds/thousands of past rides along same routes where a barometric altimeter provided inputs -- and conceivably Strava could average those inputs for a theoretically more accurate correction?
Or is the amount of wacky data just too enormous? Even if you look at just relative info, how do you filter out stuff like errors for the constantly changing atmospheric pressure? While you could go out and get nearby weather reports now you are adding quite a bit of complication to the algorithms. I have gone for a ride and the barometer changed enough to have my starting elevation and ending elevation which are the same place be off by 400 ft and maybe quite a bit more.
So maybe they don't. If you know the complication to coding that would add and then multiply that by all the other things that would have to be looked at with their unique set of things to complicate the code, then with the other regular things like creating new features and new flashy looking user experiences (which we all dislike.... initially till we get use to them) the Strava and other sites programmers are trying just to keep up with, then it might be too much for them to worry about.
I've also wondered if they do this for estimated power too. There are some instances they come up with a really bogus high power for my efforts that I can't really come up with a explanation for. Especially since many are the same route and roughly the same time.
Last edited by Iride01; 12-21-21 at 11:10 AM.
#57
Senior Member
Join Date: Jan 2010
Location: TC, MN
Posts: 39,520
Bikes: R3 Disc, Haanjo
Mentioned: 354 Post(s)
Tagged: 1 Thread(s)
Quoted: 20810 Post(s)
Liked 9,456 Times
in
4,672 Posts
Does Strava with their elevation correction, as an example, rely on their presumed database of eg. hundreds/thousands of past rides along same routes where a barometric altimeter provided inputs -- and conceivably Strava could average those inputs for a theoretically more accurate correction?
#58
Senior Member
Join Date: Jul 2015
Location: reno, nv
Posts: 2,329
Bikes: yes, i have one
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 1152 Post(s)
Liked 1,197 Times
in
697 Posts
Does Strava with their elevation correction, as an example, rely on their presumed database of eg. hundreds/thousands of past rides along same routes where a barometric altimeter provided inputs -- and conceivably Strava could average those inputs for a theoretically more accurate correction?
I've wondered about this same thing too. Not just Strava, but RWGPS and all the others too.
Or is the amount of wacky data just too enormous? Even if you look at just relative info, how do you filter out stuff like errors for the constantly changing atmospheric pressure? While you could go out and get nearby weather reports now you are adding quite a bit of complication to the algorithms. I have gone for a ride and the barometer changed enough to have my starting elevation and ending elevation which are the same place be off by 400 ft and maybe quite a bit more.
So maybe they don't. If you know the complication to coding that would add and then multiply that by all the other things that would have to be looked at with their unique set of things to complicate the code, then with the other regular things like creating new features and new flashy looking user experiences (which we all dislike.... initially till we get use to them) the Strava and other sites programmers are trying just to keep up with, then it might be too much for them to worry about.
I've also wondered if they do this for estimated power too. There are some instances they come up with a really bogus high power for my efforts that I can't really come up with a explanation for. Especially since many are the same route and roughly the same time.
Or is the amount of wacky data just too enormous? Even if you look at just relative info, how do you filter out stuff like errors for the constantly changing atmospheric pressure? While you could go out and get nearby weather reports now you are adding quite a bit of complication to the algorithms. I have gone for a ride and the barometer changed enough to have my starting elevation and ending elevation which are the same place be off by 400 ft and maybe quite a bit more.
So maybe they don't. If you know the complication to coding that would add and then multiply that by all the other things that would have to be looked at with their unique set of things to complicate the code, then with the other regular things like creating new features and new flashy looking user experiences (which we all dislike.... initially till we get use to them) the Strava and other sites programmers are trying just to keep up with, then it might be too much for them to worry about.
I've also wondered if they do this for estimated power too. There are some instances they come up with a really bogus high power for my efforts that I can't really come up with a explanation for. Especially since many are the same route and roughly the same time.
#59
Senior Member
Join Date: Mar 2010
Location: Seattle, WA
Posts: 23,208
Mentioned: 89 Post(s)
Tagged: 0 Thread(s)
Quoted: 18883 Post(s)
Liked 10,646 Times
in
6,054 Posts
If I was Strava, I wouldn't update my DEM from incoming ride data because the quality of the elevation numbers is so variable. Also because it would allow people to troll you kind of like how they used to "digital dope" but just send rides with deliberately bad data to break a segment or something.
#60
Senior Member
Join Date: Jul 2015
Location: reno, nv
Posts: 2,329
Bikes: yes, i have one
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 1152 Post(s)
Liked 1,197 Times
in
697 Posts
If I was Strava, I wouldn't update my DEM from incoming ride data because the quality of the elevation numbers is so variable. Also because it would allow people to troll you kind of like how they used to "digital dope" but just send rides with deliberately bad data to break a segment or something.
here is where I read about how strava improves their DEM:
https://support.strava.com/hc/en-us/...s/115000024864
#61
Senior Member
Join Date: Aug 2009
Location: Minneapolis
Posts: 5,789
Bikes: 2022 Salsa Beargrease Carbon Deore 11, 2020 Salsa Warbird GRX 600, 2020 Canyon Ultimate CF SLX disc 9.0 Di2, 2020 Catrike Eola, 2016 Masi cxgr, 2011, Felt F3 Ltd, 2010 Trek 2.1, 2009 KHS Flite 220
Mentioned: 20 Post(s)
Tagged: 0 Thread(s)
Quoted: 4435 Post(s)
Liked 3,064 Times
in
1,894 Posts
Somewhat different issue, but I've been getting very different values from planned ridewithgps routes and the elevation recorded with my wahoo when I actually ride the ride.
Top part of the image is the actual ride, uploaded from my Wahoo to ridewithgps. Bottom part of the image is the route planned with ridewithgps. As the two maps indicate, i followed the planned route very closely.
Ride was also uploaded to strava, which indicated 32.98 miles, 1631 feet of climbing.
Go figure.
Top part of the image is the actual ride, uploaded from my Wahoo to ridewithgps. Bottom part of the image is the route planned with ridewithgps. As the two maps indicate, i followed the planned route very closely.
Ride was also uploaded to strava, which indicated 32.98 miles, 1631 feet of climbing.
Go figure.