-
So regarding your previous comment on GPS glitches etc., have a look at this segment I just stumbled across when checking my morning commute:
https://www.strava.com/segments/8419504
OK, the first one looks like it might be related to Strava's moving time bug that many people have ranted about. It affects running really badly as it trusts some of the data from the device, but not the data that would give a more sensible answer. If there's a hole in the data then it generally picks the wrong data and arrives at the wrong answer.
If you zoom out a bit on the top ride you can see what happens:-
https://www.strava.com/activities/192185063/analysis/6403/6875
No data for a minute and 10 seconds but when the data arrives again it uses the GPS location of the last known location (the South side of the bridge), which is why it ends up jumping the length of the bridge in 3 seconds.
Strava should be better at detecting this and clearing it up.
Greenbank-
Yeah, that's the kind of thing I meant by 'GPS glitch'. It's really annoying that Strava clearly not only has no algorithm to 'fix' stuff like that, there is also furthermore no filter to keep clearly wrong stuff from actually appearing on leaderboards. (As I said, even a simple maximum allowable velocity would be better than nothing, but there is not even that)
SwissChap
So regarding your previous comment on GPS glitches etc., have a look at this segment I just stumbled across when checking my morning commute:
https://www.doogal.co.uk/StravaSegment.php?id=8419504
1 Giancarlo G. 00:00:03 355.3km/h
2 Don C. 00:00:04 266.5km/h
3 Loïc B. 00:00:06 177.7km/h
4 Emdad R. 00:00:09 118.4km/h
4 Ian W B. 00:00:09 118.4km/h
6 Joey J. 00:00:11 96.9km/h
7 Henrik P. 00:00:12 88.8km/h
8 Darren N. 00:00:13 82km/h
9 Gavin S. 00:00:14 76.1km/h
9 Ashley P. 00:00:14 76.1km/h
To be fair, that's the worst I've seen in a while...