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.

311

Comments

221 comments
  • Only a person who doesn't have any Strava followers or is never actually racing would suggest tagging every run as a race. That is a ridiculous workaround even though it kind of works. Races are prominently marked as such in the feed and I'd look silly if all my runs looked like races.

    3
    Comment actions Permalink
  • Really, Ron?? Strava is just for newbies and not serious users who just want inflated stats and boost their egos??

    Well...that's a pretty condescending and quite frankly - a pretty sh*tty - comment to make. Makes you sound like one of those typical elitist, holier than thou, "my sh*t doesn't stink" runners that everyone hates. In short, it makes you sound like a d*ck. I know a great many serious users who would vehemently disagree with you.

    If I'm on a take it easy training run and happen to stop to take a dump, I don't want those five minutes included in my time. If I'm in an actual race, then by all means I prefer elapsed time to see what I really did.

    I've never had Strava "throw out" time because I was moving too slow. Ever. I do trail runs that have plenty of uphills where I was literally walking. If anything, I was moving too slow for my Garmin GPS to pick up my pace. Strava doesn't have jack to do with "extrapolating" time. It reports what's reported to it.

    If there's a blizzard outside and I'm doing a workout on my treadmill and I stop to refill my water bottle, why would I want to include that time?!

    Giving people the option to choose isn't going to kill you, Ron.

    Let me ask you this: have YOU stopped using Strava???

    Yeah...I didn't think so...

    0
    Comment actions Permalink
  • Anthony R, yes, I stopped using Strava! They have repeatedly told me that they don't count time that they consider is "too slow". That's how their algorithm work. I have even sent them multiple runs where I never stopped and still Strava shaves off random minutes. Sometimes my faster time is considered slower because Strava shaved off more random minutes in one run and not the other.

    If Strava insist on using moving times, at least get it right and not shave off random minutes. I will say it again, Strava is only for newbies and people who like inflated times to boost their egos. To show off how fancy and nice their times are when in reality it's not really that good of a time. This as Strava randomly shaving off minutes.

    Now, why would anyone wants to use moving time in the first place? If I stop, my heart rate goes down and you cannot compare it with a run where you didn't stop. This doesn't make any sense? If so I would run 5 minutes, rest 5 minutes, and so on. Suddenly I will have a fantastic "moving time"! Again, this make "feel good" but is living in a fantasy land and dosn't show the true effort spent on that run. When comparing runs it has to be against another run with equal run, not one against where you were sitting on your butt waiting for you heart rate coming down and then keep going.

    1
    Comment actions Permalink
  • Average pace is such a fundamental metric that users at least need to have the option of basing this off either moving or elapsed time.
    Having switched auto pause off, I think the default should be to calculate pace from elapsed time.
    There appears to be an issue (possibly only with Suunto devices) of “stacked points” where there are data points in the file with time but no GPS location.
    I’ve no interest in calling every run a race - that’s ludicrous.
    This is a fundamental issue and warrants the resources to fix it over other Labs development projects - get the foundations right first!

    1
    Comment actions Permalink
  • Ron:

    I'd say I agree with some of what you say if they are indeed shaving off time, but your insistence on calling people who use Strava essentially a bunch of know nothing "newbs" who all they care about is inflated numbers and ego coddling is a dick comment at best.

    It's your holier than thou attitude and your "Look at me...I'm a REAL runner" and "Why on Earth would ANYONE care about moving time?!?!" approach to talking about people on here is what makes you the only person whose ego seems to need stroking.

    0
    Comment actions Permalink
  • ...and if Strava is only for newbies, then tell me why two of my friends who CONSTANTLY podium every triathlon they're in use Strava?

    That's right...I guess they just don't know any better, right?

    Maybe I should send them your way so you can straighten them out, since obviously someone who has com[eted in something like five Ironman's marathons and still uses Strava MUST be an attention seeking newb. Right?

    0
    Comment actions Permalink
  • @Anthony, whether Strava throws away some time and how much it throws depends on a watch model. I've been following this and similar threads for several years now. I know there have been huge issues with some earlier Garmin models. I know that there is an ongoing issue with import from Suunto watches. In case of Suunto the moving time actually depends on whether it is imported automatically or uploaded manually as GPX.
    Strava just doesn't invest enough in making this code work reliable and seem to focus only on recent Garmin models.

    To make the whole thing even more complicated, if you use a Garmin watch and press pause at least once during your run (or have an auto-pause do that for you), then Strava silently switches from moving to elapsed time. So perhaps in your case you have an auto-pause enabled on your watch - that's why your Strava times are exactly the same as reported by Garmin. In my case moving time is shorter than elapsed time by at least a few seconds on pretty much every single run.

    0
    Comment actions Permalink
  • Strange that Ron is browsing this thread and posting if he 'stopped using Strava' ?

     

    I like to use it to compare how Ive done on certain routes over time, and its easy enough to go back to previous training to see what I did before certain events.

     

    But yes I too wish strava would sort this issue, it really cant be too difficult...

    0
    Comment actions Permalink
  • My thoughts exactly...if Strava sucks that much and he's stopped using it, why bother to post comments? Whatever Strava does or doesn't do shouldn't really concern Ron.

    And no...it really isn't that difficult to do. I just chalk it up to Strava just either doesn't care what users actually want, or they just don't care what users actually want.

    0
    Comment actions Permalink
  • Neil, I still get notifications about this and hoping some day Strava will fix it. Then I can start using Strava. In the meantime it's useless.

    A simple thing like comparing previous runs doesn't work as it always using so-called-moving time where the time get shaved off random minutes. I had for example a run that took longer and Strava decided it was faster as it randomly shaved more more minutes on that run compared to other runs. Never stopped on any of them, but Strava still think "hey let make my runs look better than they really are and remove a few random minutes".

    I have no idea how any serious person uses Strava. You get completely bogus data with it.

     

    0
    Comment actions Permalink
  • Anthony, why would I keep posting if I thought everything was great? Then I would be a happy camper and busy using it.

    -1
    Comment actions Permalink
  • I guess the only action you can take is to go to the appstore and rate the app with one star. The App & Community are greats, but numbers are indeed pretty useless for any runner.

    0
    Comment actions Permalink
  • As much as I want this to be properly implemented, I think Strava will never fix this and here is the reason.

    With the current implementation Strava doesn't have to care about pauses on all possible types of devices that the data can be imported from to Strava. Strava simply crunches the data on upload and removes the paused time anyway.

    Now let's imagine this is done properly and all pausing as well as auto-pausing is handled at device level like it done in all other platforms.

    Problem #1 - GPX format can't describe pauses. And even if Strava imports FIT files from all devices now it would have to deal with a whole matrix of all possible devices and how they record pause. I know that Strava sort of handles pauses for Garmin devices, but not for any other types of devices.

    Problem #2 - implementing auto-pause in Strava app is probably more complex, because unlike the server upload case it can't see the entire data, only previous data, so deciding when exactly to turn auto-pause on becomes more difficult. That is probably a reason why auto-pause is turned off by default for running in the app.

    Problem #3 - ignorant users will complain that Strava now counts time they wait at stoplights unless Strava makes an app update that forces running auto-pause on. But not all users allow automatic updates of their apps so this whole thing becomes a complicated mess.

    My guess is that with exception of relatively small percentage of Strava users who want true data the rest are either ignorant, which is more likely, or like their pace to be inflated.

    0
    Comment actions Permalink
  • Just set your Garmin to actual time. Job done.

    -3
    Comment actions Permalink
  • This is such a frustrating part of strava. What's the point in having an auto pause function if your run auto pauses when auto pause is turned off. No point in using strava if it can't even record accurate information. What is worse is that people have been complaining on here for over 3 years now and it still hasn't been fixed.

    2
    Comment actions Permalink
  • I finally found where moving time is useful! When I’m swimming intervals, it’s incredibly helpful for Strava to only use my moving time to work out my pace .... only in this case, Strava decides to use elapsed time 🤦🏻‍♂️😂

    But seriously, the logic is obviously there to decide to use moving or elapsed based on activity type so why aren’t Strava listening to the community and using elapsed on runs? 🤷🏻‍♂️😕

    0
    Comment actions Permalink
  • @Stanislav C. what you say makes sense regarding auto-pause on other devices and explains a bit why it works the way it does. I'm not looking for that, just a global option in the app or on the website to not remove pauses. At the moment this IS actually possible per run by setting a run to "race" on the website.

    0
    Comment actions Permalink
  • Agreed for the need of a toggle switch between moving and elapsed time.
    If, however, it is easy enough to fix this problem by selecting Run Type as "Race", then I'll go with this solution as being sufficient in lieu of a toggle switch.

    But then please also add the Type Race option to Swim activities as a means to toggle between elapsed and moving time - for some reason my moving and elapsed time is totally different on many open water swims, and Strava incorrectly defaults to using moving time. And I have no way to correct it - can't edit, can't file upload, can't toggle to elapsed time - just a totally meaningless record of results (think Olympic athlete pace for me!)

    Similarly, seeing that Strava completely lacks in dealing with multi sport activities, the least it should be able to do is giving me the Race option, and in doing so allowing me to toggle between elapsed and moving time (Transitions in triathlon are recorded incorrectly as I'm obviously sitting down changing gear, and Strava uses moving time instead).

    0
    Comment actions Permalink
  • Better still, "Strava please take the information the way that Garmin gives it to you and use it exactly like that. Don't change it, don't amend it, don't fiddle with it and don't break multi sport activities up into various different activities".
    Garmin does a great job with recording - either Strava must take it as is, or Garmin must improve their Garmin Connect website (re connections, comments etc)  and I'll gladly go over to them.

    1
    Comment actions Permalink
  • It utterly flies in the face of everything Strava is supposed to be. I can’t compare my runs to others or even my own for that matter. Two days ago I had a simple non-stop trail run where Race pace and Run pace were some 8% divergent.  Even the Race-pace workaround is imperfect - the corrupt moving time is still used elsewhere like trending and View Prior efforts - I have outliers that I suspect (now) are more likely due to a bad algorithm rather than personal-best performance.  I’ve triggered a downgrade out of Premium effective in 3 mos on my annual renewal (beats pounding sand!).

    Fwiw, my watch is a Suunto. On the plus side I DO believe if I pause mid-run for even a second then Strava defers to my watch’s moving time. (Something else in the knowledge base made me think that only worked with Garmins.) But really, I shouldn’t have to hack Strava like that. 

    EDIT: 2 days later, another run (4mi) with long steep steps (several repeats) and I again did some manual pause but watch's autopause also kicked in.  Strava is clearly using its own moving time on this one.  My watch says 50+ minutes, Strava moving time is 39+ minutes and the 39 minutes is the recorded time for the run.  Uy yuy yuy Strava.

    1
    Comment actions Permalink
  • The latest example of Strava moving time ridiculousness from a friend - a 12 hour alpine climb shows as a 46 min activity. Yeah - 8 miles and 7,000 vertical feet with 5:48/mile average pace. Why not?

    1
    Comment actions Permalink
  • Yes I agree.  Make the default time equal the total moving time and have the option of removing stops/breaks.

    1
    Comment actions Permalink
  • As someone mentioned YEARS ago...I am trying to calculate my Elapsed Time since that is what will be used for a running race, so using Moving Time is inaccurate if I stop for 2 minutes to go to the bathroom, I'd rather see that split using my real time, not the moving time so I can better calculate my finish. 

    1
    Comment actions Permalink
  • I want to add to this.

    Moving time MAY be ideal for some, but not for everyone.

    When doing Nordic Skiing, there is no option for Race, so it still shaves off my "not moving fast enough" minutes.

    And some of my walks are walks, but need to set them to Run + Race to make the time accurate.

    Yesterday, I did a 8:45 walk with my kid, but it showed up as a 5 hour walk instead.. That makes no sense to me.

    This should be fixed!

    Dont fix this only with the "Run + Race" workaround. Thats _just_ a workaraound, and not even a good one...

    Please. Include this in future update!

     

    1
    Comment actions Permalink
  • +1 on this, as a minimum, elapsed time should be default. Then if Strava have resources, allow users to chose. 

    1
    Comment actions Permalink
  • this is ridiculous - yet another strata feature that people have been asking for for years, Stravas official reply is that "we are aware of the requests from the community but we are too busy thinking up shit that we think you will like, instead of giving you things that you are telling us you will like"

    NEW KUDO EMOJIS? WTF STRAVA?

    cancelled my premium membership might continue to use it free but not giving my money to a social media app that doesn't listen to their community

    10
    Comment actions Permalink
  • How do I remove myself from this useless thread? Strava doesn't care.

    0
    Comment actions Permalink
  • Joar Øverland - you can't - we will be waiting till we are old dying men before Strava gives us anything we want.

    But look - we have new EMOJIS!

    0
    Comment actions Permalink
  • Does Strava have the timeline to fix this BUG? I called this a BUG because it is the very basic requirement for runners. Using moving time instead of elapsed time makes no sense. 

    5
    Comment actions Permalink
  • +1 for making elapsed time the default. C’mon Strava, do the right thing.

    8
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post