Resting Time in Segment Efforts

All our segments are ranked according to 'Total Elapsed Time.' We like to think of our segments like a race, and in a race, the clock keeps running even if you stop. Resting time can be captured in a segment effort if you rest or turn around near the beginning or end of the segment.

 

Identifying resting or turn around time

Viewing your activity on the web version of Strava is the easiest way to analyze your segment efforts. Click on a segment from the list and select 'Analyze' (highlighted below) from the expanded segment view.

 

skitch.png

 

You can compare your speed on the analysis graph with your location on the map to identify where you were going at what speed. Toggle the clock icon (highlighted below) to view your speed charted over time

 

Chatty_commute___Ride___Strava_2.png

 

If there is resting time included in your segment effort, you will see your speed flatline (likely around 0 miles or km per hour as shown below) for an extended period of time. 

 

Fullscreen_3_31_17__11_34_AM.png

 

Turnaround time is a bit harder to identify because you are still moving. You can look at the map to see what chunk of your ride was timed for that segment. In the example below, the path timed for the segment effort is highlighted in blue and you can see where the athlete turned around before the segment started:

 

Cesta_z_pr_ce__ZDV__kopce_LT____Ride___Strava.png 

 

Why is resting time sometimes included in segment efforts?

As you've probably noticed, GPS data isn't perfect and there is often some margin of error with your data. To account for moderate GPS drift, our segment matching algorithm has to be a little loose. If our matching process was more strict, you'd often miss out on segments.

If you cross through the segment start point range to stop or turn around you may prematurely trigger the segment timer. In the example below, moving past the segment start point triggered the timer and the athlete did not travel far enough beyond the start to re-trigger the segment timer when they returned. 

 

Strava___Admin_Visualizer_897621917.png

 

If you stop or turn around near the end of the segment, you risk not moving far enough beyond the segment end point to trigger the segment timer to stop. In the example below, the athlete stopped after just finishing the segment and their resting time was counted towards the segment effort.

 

Strava___Admin_Visualizer_869033734.png

 

Preventing resting time in segment efforts

It may not be possible to avoid this issue if the segment has bad start or end points. Segments that end at the top of a climb, close to an intersection, or even at a common hangout spot are likely to produce bad matches. We recommend placing the segment end just before the natural stopping point for best results. The same is true for segments with a start point at a trailhead or an intersection. A segment start point just past the actual starting point will produce better matches. 

Learn more about Optimizing Segment Creation.

We always recommend riding through a segment start or end point. If you need to turn around or stop, we recommend avoiding the start or end point by about 70 meters. 

 

FAQ

Can you fix my segment effort?

No, we are unable to adjust segment efforts after they've been recorded. Refer to the tips in this article to avoid poor segment matches in the future.

Was this article helpful?
1 out of 2 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.