This is driving me nuts. There are several segments in the climbs near me which have KOMs with OBVIOUS bad GPS data; in some cases the entire Top-10 is comprised of rides with bad GPS! I’m talking OBVIOUS bad: Like 215 mph, 91mph, tons of 60-80mph -- up 12% hills! The GPS map on Strava shows them riding over water, trees, looping over roads, going in straight lines through the forest, etc.
Most of them can be flagged. It’s annoying that Strava can’t figure out how to automatically flag an 80 or 200 mph segment, but oh well.
BUT there are several rides -- including KOMs! -- which can NOT be flagged! When you try to flag it, you fill out the “reason” box, click the “flag” button, and the box just clears. I’ve tried multiple browsers, with multiple flagging reasons, over multiple days. No matter WHAT, some of these BOGUS KOMs and Top-10s simply cannot be flagged!
WHAT GIVES?
Also: Why are there certain segments which have sooooooooo many bad GPS errors?
In those cases, I would suggest submitting a support ticket to Strava with the segment link and a list of the activities that are obviously false. They should be able to address it from their side. I’m guessing those activities may have already been flagged a couple times and somehow “resolved”, so it won’t let you flag them again, but not certain on that. Once it has been flagged twice and resolved, it won’t let others flag it again even if there is a problem and you need to go through the support ticket route.
As far as some segments having bad GPS errors, that can sometimes be due to obstructions blocking the GPS signal. Things like heavy trees, large buildings, etc… It will lose track of your position and then pick up a bit of a signal further along and connect a straight line between the points. Not sure if that would explain what you are seeing, but does happen at times.
Reply
Login to the community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.