edrobbin
Regular
Sorry if this has been covered before, but I'm literally the latest of late people to the Strava party. Have been happy for years with keeping myself to myself on Garmin.
I've got the VeloViewer bolt on so as to look at all the segments i've ridden over the years - lots of smug, self satisfied back slapping over the last week or so - got some pretty decent positions on very popular segments. But, I've noticed a couple of my better ones look a bit odd.
There's one; "York Road blast off" between Westminster Bridge and Waterloo station where the KOM speed was 173.8mph - clearly a GPS glitch right - the map shows the guy straight-lining to the city and back. (My profile pic was on that segment!)
There's another one where the KOM was doing 70-odd mph - "Bridge St (up)" as you approach Westminster Bridge from P-square. You can't really do that on a bike can you?
How do these glitches happen & can't Strava run some sort of check to exclude cycle times over xx mph?
I've got the VeloViewer bolt on so as to look at all the segments i've ridden over the years - lots of smug, self satisfied back slapping over the last week or so - got some pretty decent positions on very popular segments. But, I've noticed a couple of my better ones look a bit odd.
There's one; "York Road blast off" between Westminster Bridge and Waterloo station where the KOM speed was 173.8mph - clearly a GPS glitch right - the map shows the guy straight-lining to the city and back. (My profile pic was on that segment!)
There's another one where the KOM was doing 70-odd mph - "Bridge St (up)" as you approach Westminster Bridge from P-square. You can't really do that on a bike can you?
How do these glitches happen & can't Strava run some sort of check to exclude cycle times over xx mph?