You are reading a single comment by @yoshy and its replies.
Click here to read the full conversation.
-
On my tour I ended up riding with a German software engineer for a long time, he was really interested in this stuff and had set up his own way of measuring altitude and was using a couple to try and verify the results. I'm being deliberately vague because I can't remember much of what he was talking about but it was really interesting, I'll drop him an email today and see if he can send any info about his setup over
yoshy
Lukas
My biggest gripe with Strava: rides recorded using a Garmin usually have a higher average speed and greater recorded elevation than the same ride recorded using the smartphone app.
I understand why the speed might be different (assuming both based on GPS, no sensors), particularly on a commute/through town, because ten seconds pass before Auto-Pause does what it is supposed to (and this doesn't always work if it's cloudy/wet/congested, due to poor GPS signal)... But, I've always envied friends' stats at the end of a week where we've ridden together; I look like the wimp who only rides on the flat (although, in/around Manchester, this isn't difficult).
Example: 14km morning commute when plotted in Route Planner estimates 57m or elevation, but the Strava records zero.
The same route in reverse, in the evening, allegedly rises 101m, but the app only records around 50m.
I know Garmin gets its data from an inbuilt barometric altimeter, or something, so should be/IS more accurate, but I feel aggreived at the prospect of having to pay Garmin Tax for that extra performance.