The following article redescribes the problem with how the times of segment efforts are currently measured, suggests a solution, and provides an exemplaric implementation: Accurate timing of Strava segments
And additionally I don't see how it should work that Strava automatically changes the start and endpoint of already created segments. Segments always begin and end on recorded GPS points, never between two recorded points. If the same or some other rider make an attempt on a segment with a higher GPS resolution Strava still wouldn't know if some of the extra points are more suitable for the segment start point and end point. Therefore Tobias idea only works for applying segment efforts, not for changing segment coordinates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.