Another Strava query. Sorry!

TheSmithers

Just been out on a ride this evening and achieved a KOM on a segment. I'm appearing in 1st place on the leaderboard table for the segment, however everywhere else suggests that they previous rider is still KOM. For example, the bit down the right hand side where it shows the fastest man, fastest woman and then your fastest time. Do new KOMs have to go through a verification process or something.

Pure vanity on my part at the end of the day. But it matters dammit!

EDIT: Here is the segment in question: http://app.strava.com/segments/4299090

Cleat Eastwood

Followed the link in your sig and you are KoM by .1mph - enjoy, wont be long before someone comes along and snaffles it. well done

sloppyschleckonds

Pretty sure Strava nullifies your KOM if you are running Tri Bars, TT bike or anything over 32mm rims.

smidsy

On my run on Sunday it lists my fastest speed as 72.3mph!!! Despite the speed graph topping out at 55.8mph, so it is not by any means foolproof.

smoggysteve

You want to see a strava issue - look at the top times on this race I did last week. look at the fastest time. EPO users I think!!

http://app.strava.com/segments/2487283

springtide9

SmoggySteve wrote:

You want to see a strava issue - look at the top times on this race I did last week. look at the fastest time. EPO users I think!!

http://app.strava.com/segments/2487283

It's because someone has created a segment of more than one Lap! They need to ead the manual which states:

Segments that include multiple loops through the start/end points will always only match one loop, no matter how many loops the segment actually is. This can cause for some very strange times as the time it took you to complete one loop is stretched over the actual segment distance which can include multiple loops.

So Strava thinks you are completing the full distance of the segment (multiple laps) every lap.

Full details at:
https://strava.zendesk.com/entries/2095 ... ing-Issues


----
Problematic Segments:
Loops/Laps
Some segments are frequently more challenging for our current segment matching algorithm. A segment that is a loop and has similar start and end points will not be able to distinguish direction, meaning whether it was performed clockwise or counterclockwise. Segments that include multiple loops through the start/end points will always only match one loop, no matter how many loops the segment actually is. This can cause for some very strange times as the time it took you to complete one loop is stretched over the actual segment distance which can include multiple loops.

Loop segments should be one lap and will only be matched and timed between the start and finish line of the loop.

Out and Backs
Another issue that can come up with our segment matching algorithm is turnaround points. Out and backs can also cause false matches if you go past the turnaround point to turnaround or if you turnaround prior to the turnaround point but have completed at least 75% of the out and back. It is currently not possible for our segment matching system to detect these details.

Similar start/endpoints

The segment matching algorithm has difficulty distinguishing segments with the same or similar start and end points. Although these segments are different, or have some significant intermediate variation, some segment may match your activity that you didn't complete fully. This can be confusing for the segment leaderboards and the accuracy of the segment in general, which we understand. If you match as segment that you feel you should not have matched, feel free to contact support and we can help remove the segment from your activity.

Timing Issues:

Recording intervals vary between devices - for example, the mobile app records every 3-4 seconds while Garmins usually use smart recording which has a varied recording interval. Segment matching works the same on each GPS dataset, but depending on the unique data and recording interval, can yield different results. Segment matching uses the GPS points in the data closest to the start and endpoints of the segment, and as this can vary with each activity, timing on a segment can vary slightly because of this. At the present time, we don't interpolate or extrapolate GPS data to normalize for the exact start and end positions of the segment.

TheHound

Hijacking the thread seeing as it seems to have died anyway.

Can you hide segments with the iPhone app or does it have to be done via the website?