![]() |
Strava elevation
I mapped a 70 mile ride last week on ridewithgps.com and it had my climbing at 1700 feet. Rode it with my Strava Ap, and it said 800 feet. Why the big difference.? Are they calculating differently? I also notice when I get done with my ride on Strava it over reports my distance from when it actually ends the ride or run.
|
If you're using Strava with a smartphone, then it has to rely on map data to figure out your elevation, but if you go on overpasses or something that often doesn't show up. Also if there are elevation changes or unknown elevations between the mapped elevation levels you'll lose that gain in your summary as well. If you use a Garmin with an altimeter you'll get a more accurate reading.
I'm not sure ridewithgps works though. |
Google "richardson effect", or check out http://en.wikipedia.org/wiki/How_Lon...onal_Dimension
Or, imagine you're running, and your body bobs up and down 4cm each stride. After an hour at a cadence of 85, you've gone up and down 5100 times, or 20,400cm. Thats 600ft of elevation gain and loss. Now, does that count? Applied to cycling, imagine bumps in the road, 1 foot here, 1 foot there. Does that count? Who decides? Some algorithms smooth those out, some dont. |
figured it was using the altitudes listed on Google Maps
|
Originally Posted by DeanB
(Post 14602846)
If you're using Strava with a smartphone, then it has to rely on map data to figure out your elevation, but if you go on overpasses or something that often doesn't show up. Also if there are elevation changes or unknown elevations between the mapped elevation levels you'll lose that gain in your summary as well. If you use a Garmin with an altimeter you'll get a more accurate reading.
I'm not sure ridewithgps works though. The answer to OP's question is that Strava selectively filters out small elevation changes to smooth the data (to avoid the "Richardson Effect" jmX mentioned). DEM will often NOT have accurate data for roads but rather simple low-res topographic data which doesn't account for roads cutting through hills, bridges, etc. Also, RWGPS uses very little smoothing in their calculation. |
Originally Posted by nhluhr
(Post 14604687)
This doesn't make any sense. Both RWGPS and map data are using DEM data for elevation, probably the 30-ft resolution version if you're in the USA.
The answer to OP's question is that Strava selectively filters out small elevation changes to smooth the data (to avoid the "Richardson Effect" jmX mentioned). DEM will often NOT have accurate data for roads but rather simple low-res topographic data which doesn't account for roads cutting through hills, bridges, etc. Also, RWGPS uses very little smoothing in their calculation. |
I used strava for the first time yesterday and when I paused it at the end of my ride and recorded it my time was 1hr 45min 22sec for 27.6 miles. When I looked it up on my computer this morning it had my time as 2hr 8min don't remember the seconds for total moving time. I know the first time was accurate because I looked at my watch when I started and when I finished. Has anyone had similar experiences?
|
Bump because I'm going to try Strava out for the first time this week and I'm curious also...
|
| All times are GMT -6. The time now is 06:08 AM. |
Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.