Resting Time in Segment Efforts

All our segments are ranked according to 'Total Elapsed Time.' We like to think of our segments as 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 turnaround time

With a Strava subscription, you can view your segment efforts on the Strava website. Depending on the activity type, you may be able to analyze your segment efforts and identify resting or turnaround time.

  • Certain activity types (including rides and snowsports) will allow you to click on a segment from the list and select Analyze (highlighted below) from the expanded segment view.
    English1.jpg
  • You can compare your speed on the analysis graph with your location on the map to identify where you were going at what speed. Select the clock icon (highlighted below) to view your speed charted over time
    English2.jpg
  • 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 (highlighted in blue.) In the example below, the path time 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 

If you activity type does not have the option to analyze segment efforts (running and hiking for example), it may be more challenging to identify whether there is resting or turnaround time is included in your segment effort. However, these segments are still ranked according to elapsed time and we still recommend taking steps to prevent this issue.

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 endpoint 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

Unfortunately, in this scenario we're unable to adjust your segment effort time. However, there are a few ways you can prevent issues in the future:

  • We always recommend riding through a segment's start or endpoint. If you need to turn around or stop, we recommend avoiding the start or endpoint by about 70 meters.
  • It may not be possible to avoid this issue if the segment has a bad start or endpoint. We recommend placing the end of the segment just before the natural stopping point and the segment start point just past the actual starting point for the best results. Learn more about Optimizing Segment Creation.
Was this article helpful?
10 out of 18 found this helpful

Comments

0 comments

Article is closed for comments.