Bug in short segment showing impossible KOM speed
The following (well contested) segment: http://app.strava.com/segments/785206
Shows a new KOM today. The rider is shown to have averaged 98.9kmh but on his ride the maximum speed attained is ~62kmh
I'd say that's a bug :-) (and I want my KOM back cause it took a good leadout to get it :-)
Comments are currently closed for this discussion. You can start a new one.
2 Posted by justind on 28 Jan, 2012 08:55 AM
Here's another one showing the same sort of error. It's a 60kmh road so not likely to be a car either
http://app.strava.com/segments/757289
3 Posted by Chris H on 30 Jan, 2012 12:11 AM
Just flag the ride for abnormally high speed. Refer to heart rate data in "performance". It ed steady through the whole segment and we all know 61 mph is pretty far fetched
Support Staff 4 Posted by Travis Robison on 01 Feb, 2012 01:17 AM
Hi Justin,
Unfortunately this is just due to some bad data from his GPS unit. That, and this type of problem can happen more on short, straight Strava segments.
It's likely that this rider has smart recording set to "on" which records less GPS points and there were only maybe 5 GPS points recorded during this whole segment. And we don't interpolate between GPS points so we have to measure the time between the two collected GPS points that are closest to the start and finish of the segment. This can lead to some very skewed times on these types of segments.
I've unmatched the riders to both of these segment because their times are just too inaccurate. But I do believe they were both on bikes. In general short straight segments will remain problematic for our segment system until we start to interpolate between points. Sorry for the inconvenience.
Regards,
Travis
Travis Robison closed this discussion on 01 Feb, 2012 01:17 AM.