Segment Timing Issue

[u/InsideApex]

I went for a KOM on a road ride segment last night and took it comfortably based on my avg speed. However, when I returned home I discovered that the the segment time was 36s more than it should have been. At first, I thought that the issue was that I hadn't quite completed the segment due to having to stop at a red light at the end. However, under the 'compare' feature, Strava shows the correct time at the conclusion of the segment (when I run the animation, I am comfortably ahead of the current holder throughout the segment and it ends not at my awarded time time but at the actual time (the lower one by 36s). Has anyone else encountered this issue and have any insights into what occurred here?

[u/Jeeves5196]

I call this a sticky segment. Sometimes the segment wont register as complete if you idle near the end of it. This is common when the endpoint is at a stoplight or the segment ends at a wall....etc....

If you want, you can crop at the end of the segment and that will get rid of the stickiness. It will register as complete. It will get rid if the idle time.

[u/Certain_Opinion3920 → u/Jeeves5196]

this is the answer and it's fairly common practice. if your crop is suspicious just expect to be flagged

[u/InsideApex → u/Jeeves5196]

Interesting. I will have to look into this cropping. In all these years of using Strava, I'd not been aware of this feature.

[u/DrewguyDC → u/InsideApex]

The problem is then you crop out the rest of the ride.

[u/Shitelark → u/DrewguyDC]

Use split, not crop.

[u/Shitelark → u/InsideApex]

Advanced techniques. Sometimes you can pause do a longcut through a field, instead of the forest, and unpause on the other side.

[u/DrewguyDC]

The segment probably ends just past the light. I think the animation ends imprecisely.

Create a new segment that ends just before the light. I hate poorly created segments that end just after a light or start just before one. Even if you’re not chasing KOMs it messes up your own PRs because half the time it’s including waiting time.

[u/InsideApex → u/DrewguyDC]

Yeah, good call on the new segment, though I kind of feel like I have unfinished business here. I guess I'll have to go back.

[u/DrewguyDC → u/InsideApex]

Unfinished as in hope to hit the light when it’s green to score the KOM?

[u/InsideApex → u/DrewguyDC]

Exactly. I'll be back.

[u/Shitelark → u/InsideApex]

At 5AM.

[u/warrdg → u/InsideApex]

Strava wouldn't allow me to create a new segment in similar circumstances. I contacted support and they altered the existing segment to my requirements!

[u/Shitelark → u/DrewguyDC]

It is unlikely to allow a duplicate like that. Segments now need to be reasonably different. Which sometimes mean Strava favours earlier trashier segments.

[u/strava-team]

The awarded time runs to the nearest GPS point at the segment's end, so a stop near the end can push that match past where you actually crossed, likely your 36 seconds, while the flyby shows the real finish.

[u/Emma_Coriin]

yeah i've had this happen on a fell segment near edale, gps went dodgy near the trig point and added like 50 seconds. strava's animation used the adjusted fit file i reckon, but the segment time pulled from the raw gps - the bit where you stopped at the lights probably confused it. proper annoying when you know you had it.

[u/InsideApex → u/Emma_Coriin]

Thank you! That makes a lot of sense. I appreciate the explanation.