Completed

Let users specify whether moving time or elapsed time is relevant to that activity

When runs or rides are uploaded to Strava, time spent stationary or with very little movement is ignored when evaluating the whole average pace of the activity.  So for example, a run last night where I had to stop for 50s to tie some shoe laces ignores those 50s when calculating the average pace.

For running, I think this gives a misleading impression of pace.  I can run 5min/miles for a mile, providing I run for 15s, stop, run for 15s, stop, run for 15s, stop, etc etc etc.  And if I recorded such an activity on Strava, that's what the activity would show.  

I would like to suggest a toggle switch for an activity - "Elapsed time or moving time" - which can be specified on run by run basis so that if I want to see my pace based on total elapsed time, I can; and vice versa.

I strongly suspect that this would be a feature only desireable for runners.

324

Comments

240 comments
  • I totally agree with this. I find elapsed time more useful than movint time.

    1
    Comment actions Permalink
  • This misleading change of lap time and race time change happened to me too.....
    Ran an Official Half Marathon in Lichfield and beat my PB - and thank's for www.stuweb.co.uk if records my official time from when I cross the start and cross the finish line (with out adding minutes)

    and after changing my run type from run to race on Strava, it added 8 minutes to my time.... strange as I didn't use auto pause or stop at all.... I race trying to beat my PB.... so why add minutes ?

    Strava needs to do a few things here I feel as also if the race is measured Officially and Garmin use satellite to track me errors often occur and this race fell short and only measure 13.06 but got longer reading form other runners of similar time - I think Strava needs a button to click and it can register this run as an Official Half Marathon (but because it didn't measure it as 13.1) Strava refuse to class this as a Half Marathon.... it can look at every who ran the race and trace the route and notice that a satellite can make slight errors
    (like using FindFriends and I can trace my friend who is next to me and find Apple think she's in the next road or field .... errors occur with satellites 

    2
    Comment actions Permalink
  • How is this not resolved yet? Lately I've been doing run and burpees intervals and strava cuts off all my burpees time wtf. Switching the segment to ``Race`` is NOT a viable solution.

    2
    Comment actions Permalink
  • Still no updates?? Where I run regularly, there is a half mile tunnel. Because the GPS data is lost upon entry, Strava counts the distance but thinks I get from one side to the other in about 30 seconds. Skews all my times and results and PB's.
    The MOST annoying thing, to exclude the ridiculously inaccurate PB's I have to save as a workout - which forces me to use the incorrect average pace. So I have to tell everyone I've done another race and ran another 4 minute mile, in the middle of my 7 minute mile average.


    Sort it out Strava, just let us use elapsed time, this is getting silly now. 

    1
    Comment actions Permalink
  • Agree with most people above. I really want Strava to record what i choose to set IM my Clock, when running, biking, swimmingpool ,etc.

    1
    Comment actions Permalink
  • I second this one too. For hikes especially, steep uphills are treated like still time and moving vs elapsed difference there may go to hours!

    1
    Comment actions Permalink
  • Something has changed recently and through reading these posts I would suggest that it's a difference between Android v's iPhone. For example, my partner and I have recently done the same run, for me my Moving time = 2:54:35, Elapsed = 3:35:45, for her Moving time = 3:35:34, Elapsed = 3:35:44. We have the same watch Suunto Baro 9 (ALL same settings), only difference is I sync through Suunto App on Android, she syncs via Suunto App on iPhone. 

    IF I change to race, then of course Moving marries up to Elapsed, but why should I have to change all my training runs to a Race to reflect correct pace and splits? 

    I understand why the difference as Strava incorrectly thinks that I have no forward motion, yes there were some pauses during the run, but on the majority of what Strava sees' as pauses was actually climbing time over a very steep gradient, i.e. forward motion at times was minimal and slow. 

    Suunto App shows the correct elapsed time as per my watch.

    Final Surge shows the incorrect moving time which is fed from Strava, pointing the finger squarely at Strava. 

    Please Strava, give users the choice, why force this method on your users? 

    2
    Comment actions Permalink
  • Please change this.. I want to stay with strava but can't without reliable times

    2
    Comment actions Permalink
  • I notice there have been no posts so far this month, so hoping to add to the pressure for some action on this. This has been a problem for me since I got a Polar Vantage V, has tainted my view of Strava and made me reluctant to consider an upgrade to Summit, waiting instead for a better app to come along.

    It is no problem on the few runs I do with no breaks in positional data, but hugely problematic on the majority of my runs with tunnels or lots of tree foliage. I get that accurate moving time is maybe too big an ask given the huge variety of data formats from the different OEMs, so I too would like an option to calculate average pace on elapsed rather than moving time.

    I accept that time waiting to cross roads or level crossings would affect my pace adversely but would prefer that to posting inaccurately flattering average pace all the time. Just give people the choice of Elapsed or Moving, without forcing them to post every training run as a Race. Not perfect, but relatively easy for you to implement and keep most people happy. Those that don't want the change, or want to kid themselves on pace, can keep the moving time averages.

    4
    Comment actions Permalink
  • We could use this our advantage. What if we sprint as hard as we can for 30 seconds, wait and recover then repeat for a segment. We may be able to get some amazing times if Strava ignores any time when we aren't moving.

    How much time does it really to add a setting that says "Don't mess with my times"?

     

    -1
    Comment actions Permalink
  • @Shane, I think many of us have given up on this ever happening. Three years of posts and comments about implementing a feature that the technology is already in place to facilitate seems like it would be sufficient. I gave up hope on it a long time ago.  

    1
    Comment actions Permalink
  • MapMyRun already has the feature built in.

    2
    Comment actions Permalink
  • Wait a second. What if you are on a 100 mile bike ride and stop for lunch. Did you actually count that time as effort?  Elapsed time has no meaning if you dont want to include breaks.  Garmin devices with auto-pause enabled show the actual moving average speed. But when you load a static (indoor ride) to Garmin,as it gets replication to Strava, it counts the break times as part of the speed calculations. So even though I went 14.5 for 2.7 hours of moving time, Strava counts it as 11.5 mph for 3.3 hours of moving time.  Elapsed time in this sort of interupt driven effort is meaningless. 

     

    -1
    Comment actions Permalink
  • Nothing I suggested affects you Doug. If you want to carry on posting your average pace against moving time (as I myself would on long bike rides with breaks) you still can. If you want your average posted against elapsed time, like for a race, you can do that too if given the option, but without having to declare a training run as a race. It works for everyone and is so simple to develop, it's hard to understand why Strava don't just do it.

    1
    Comment actions Permalink
  • Doug, I think that even recording that ride is pointless.  How do you compare it to the same 100 mile ride without the break?  Perhaps the first part of the ride before lunch could be worth it, but even then you will have been taking it a little easier knowing all the distance still to go.

    0
    Comment actions Permalink
  • STRAVA, any update on this? My run stats are useless with "moving time," as it is not accurate at all. It's been almost 5 years since the original post. Surely you have some solution now??

    4
    Comment actions Permalink
  • Completely agree. On super steep walks or climbs the actual time can vary significantly from moving time particularly on a hike or climb where GPS accuracy is set to longer time intervals. A toggle switch would be great.

    1
    Comment actions Permalink
  • I don't get why everyone uses Strava - this "feature" alone is annoying at best - it took me ages to work out what was being done to my "pace" - only switching all my runs to "race" do i get what the "real" value - the value all other apps/programs would calculate.

    1
    Comment actions Permalink
  • How do you even have to implement this as a new feature? Just display the data as it is. Why not just have the default settings on import show the raw data, as you do when marking a workout as a race? I mean come on, it's already implemented! Do you really expect us to pay you guys to reinvent the wheel here?? Data is data. Display it; don't manipulate it. I don't need Strava to guesstimate how long I stopped during my run. It's entirely inaccurate and doesn't serve any purpose. I just want to see my real pace and elapsed time. That means the time between when I pressed 'start' on my watch to when I pressed 'stop'. Why should I give you my money if you can't even get the basics right? 

    4
    Comment actions Permalink
  • Katie, the problem is that Strava doesn't know how to calculate moving time. It's extremely faulty. When I trail run for example, I never stop. Still strava moving times shaves off 10-20% of the time. Then trying to compare my runs with other runs, only the moving time is used and the comparisons do not make any sense.

    Anyone serious cannot use Strava as its quality is like a dry sponge left in the sun for 7 years.

    4
    Comment actions Permalink
  • Good morning, 
    Thanks for your 'Official Comment' on this. I do have a question please. You state "....We will continue to highlight moving-time-based pace in the main activity feed because we believe moving time is a more accurate measure of how long an athlete was active", why are you doing this? 

    For example on a trail run where I am climbing and my forward motion is minimal due to the gradient, Strava is incorrectly recording this as a 'pause', but in reality my forward motion is slow due to having to climb a hill. I am still moving, or I am catching my breath, i.e. if you decide to calculate pace based on moving time, for this type of activity your decision to do this is wrong, wrong, wrong. I want my main feed to show pace based on elapsed time, whether or not that elapsed time also includes my pauses to catch my breath, slow forward movement etc. 

    Please explain if I have misunderstood something in you explanation? 
    Kind regards.

    AW.

    4
    Comment actions Permalink
  • I appreciate the official comment from Strava (after literally years of people complaining about this).

    However, the comment shows that Strava does not take training seriously in any way, and is just a social platform for people to feel good about themselves. As SO MANY people have pointed out, Strava simply strives to make you pace look as fast as possible by fudging the numbers when you "stop" (i.e. run slowly or climb a steep hill).

    I have gone back to using RunKeeper to keep logs of my actual run data, Strava is now just a way for me to stay in the know about what friends are up to but it certainly cannot be considered a "training tool".

    4
    Comment actions Permalink
  • How can Strava be so backwards and think 'moving time' is more accurate then actual time. Moving time means absolutely nothing to me as like has been mentioned before a slow hill climb is assumed to be stationary. What is the point in having an auto pause function when it still auto pause when you have this turned off. Just stop being ridiculous and give everyone actual time. Recording every run as a race is just stupid. Please fix this. Thanks.

    4
    Comment actions Permalink
  • Lol Strava.
    You're cute.

    Too little too late - I've long ago cancelled premium subscription, and now use Garmin connect to compare my training and progress.

    Strava is NOT a training tool, it's a cute little app for social networking.

    2
    Comment actions Permalink
  • Alan Wheat: "For example on a trail run where I am climbing and my forward motion is minimal due to the gradient, Strava is incorrectly recording this as a 'pause', but in reality my forward motion is slow due to having to climb a hill. I am still moving, or I am catching my breath, i.e. if you decide to calculate pace based on moving time, for this type of activity your decision to do this is wrong, wrong, wrong. I want my main feed to show pace based on elapsed time, whether or not that elapsed time also includes my pauses to catch my breath, slow forward movement etc."

    — Have you tried turning auto-pause off in the app settings during those portions of your route? I got a patchy portion of the route in a few of my activities because that portion was so steep that the auto-pause would engage but then it didn't disengage until I had run quite a long distance (interestingly, it didn't happen with other apps, those are much quicker to react). Now I've fixed it by turning Strava's auto-pause off whenever I going to run uphill that same steep portion.

    If you turn auto-pause off the moving time and the elapsed time become the same.

    You may also want to crop off the last metres of your activity since those may be an artefact from the time between you ended recording your activity and the time you uploaded it to the Strava database, so that time may have been added to the elapsed time.

    -1
    Comment actions Permalink
  • Hi Zephyr, thanks for your suggestion, I do not have auto pause on, I am not using the Strava app, I am using my Suunto Baro 9 (this has auto pause turned off too). Checked, double checked, it's not on.

    Read my earlier post ref: https://support.strava.com/hc/en-us/community/posts/208848057/comments/360008349712

    Strava in their wisdom believe that there's no forward motion, but in reality I am climbing a very steep incline and at times stop to catch my breath/ rest legs etc. I want this stopped time to be included in my overall elapsed time, it is my choice that I have stopped, if Strava then takes it that this is not to be included in my elapsed time then it results in my overall pace calculation being pointless. 

    Give us the choice Strava, why should I mark every training run as a Race? 

    3
    Comment actions Permalink
  • Alan Wheat Now total elapsed time is shown in the activity along with the pace calculated with the total time. Just look there and you will have the stats you want. What you are asking is very selfish for your activity only. If I do interval runs, I want to know my pace when moving, because thats the stat I am interested. Same thing if I go cycling 150Km and stop for lunch.. Same thing if I swim laps and intervals in a pool.. Your case is the minority, just live on with what you have.. All the stats you need are now there...maybe you should consider marking your activity as a hike if you have long and slow climbing sections. 

    -4
    Comment actions Permalink
  • Why even have the ability to turn auto-pause off if Strava is just going to guess when I stopped? I'm fine having this as a feature, but making it the default time / pace on the top of every workout is not useful, as is described in the entirety of this thread.

    How did Strava come to the conclusion that the current method is the best measure for training?

    You can turn auto-pause on, or, pause your workout if training intervals, stop for a pee, etc. However, you can't simply turn off your guesstimate on moving time and pace.

    Utilizing a loophole in the user interface isn't an acceptable work-around to promote. It's a lazy solution to a problem.

    3
    Comment actions Permalink
  • Did anyone see the response of Strava Katie here ? It is pinned on the first page of this forum, that for her and for strava, this whole issue is solved. I mean solved by sweeping it under the rug. 

    https://support.strava.com/hc/en-us/community/posts/208848057-Let-users-specify-whether-moving-time-or-elapsed-time-is-relevant-to-that-activity

     

    Strava just sent out a newsletter about changes requested by users. This forum has been up for 6 years now so what is really a request and what is marketing pleasure ...? 

    I just wrote a little article on this where you'll find absolutely nothing new, but just repeating what everybody has been shouting here. It is us who would like to decide that we want to see real or false data ! But normally the option should be the contrary. Give the real precise data and make a button to calculate if we wanted by moving time. What strava does is giving false data and no options ! 

    https://www.strava.com/athletes/775091/posts/8392748

    3
    Comment actions Permalink
  • Pasquale Gurzi' , really appreciate you taking the time to respond to my last comment.

    Please, read everyone's posts on this matter. Quite simply, runners are asking for the choice, because.....

    1. For those of us running over mountainous terrain, Strava is guessing that I have paused because my forward motion appears to be static during steep ascents which results in an incorrect pace over my entire training run

    2. They already have the solution i.e. set to 'Race' but why should we have to set all out training runs to a 'Race'

    3. If you want to do interval runs then pause your run or turn on auto-pause, you have the option, those who want elapsed time do not have the option.

    4. On the Strava feed, the main activity is still calculated by moving time

    There's nothing selfish about it at all, you only have to read the entirety of this discussion thread to understand this.

    Enjoy your intervals.

    2
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post