Soldato
- Joined
- 9 Nov 2005
- Posts
- 9,180
- Location
- Southampton, hopefully not too hot, or too cold
Went from the Strava segment you linked! Really wish there was some kinda 'correction' you could flag on Strava segments to correct dodgy elevation data with other data from riders who've ridden it (I believe segment data comes from the creators GPS data?). I mean Strava are aware of screwy data as there's even a 'Fix elevation data' built into their ride data system.![]()
From only using Strava for the last year, I've found it to have several flaws including...
Blatantly dodgy elevation data to used to create some segments eg. http://www.strava.com/segments/2284551 vs http://www.strava.com/segments/15435477
Categorised climbs that don't conform to Strava's own rule of a minimum 3% gradient average (multiplied by climb length in metres being 8000+) when using "Segment Explore" eg. http://www.strava.com/segments/12840251
Ride recordings that you choose to keep private and off the leaderboard (like say yesterday when I took along my smartwatch to compare against my Lezyne Super GPS) interfere with your personal weekly distance, achievement and leaderboard stats
It doesn't keep PBs for different bikes separate, so any segments I do on my road bike at least uphill and on flat should beat my fatbike, but having records for the fatbike for training purposes would be useful
etc.
My Lezyne has a barometer which is used to give its own view of a ride's elevation, but when I've asked Strava to correct it using their own elevation data, I've had the ride data corrected by approximately -10 to +10%! Makes it all a bit pointless as a Lezyne feature, if Strava's data is more accurate!