완료

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

댓글

  • So can this be used to hack segments? Sprint flat out, stop and recover, repeat.

    -1
    댓글 작업 고유 링크
  • I don't know how this hasn't been fixed in 3 years. I started running with my friend and our moving times are completely different even though we're running side by side the whole time. Strava tells me that I'm running a minute and a half faster than her per mile. Its a shame because I like the app otherwise, but since moving time is so broken I can't trust any of my results.

    1
    댓글 작업 고유 링크
  • Still not fixed. Really disappointed in you Strava!

    3
    댓글 작업 고유 링크
  • I've only recently confirmed that Strava does, indeed, drop random amounts of time from my activities. I've actually used two apps at the same time for more than 2 years because, as much as I like Strava, the pacing is so inaccurate that it's really meaningless. Finally, I at least have an explanation but I'm really disappointed to find out that it's been an issue for so long without resolution. Nope, switching the runs to "race" isn't an acceptable solution for me. If it were, there would be no point in having different categories. I want to differentiate races from runs from long runs. While the ego stroke is nice to have, I'd like to know what my pace really is, particularly when I'm running side by side with another Strava user who ends up with an entirely different time than I get. For me, there really isn't a point in having an app that intentionally gives inaccurate data.

    It appears that some folks want to factor out time for pauses like red lights. In my mind, isn't that what the AutoPause feature is for? But, as has been said before, the solution is obvious. Users need to have the option to choose which measure they want to record. In my opinion, that choice ought to be in Settings so that I don't have to make the choice on every run but I'll choose every time if that's what I have to do. Just gimme the ability to record elapsed time instead of this...this..."moving time" thing.

    0
    댓글 작업 고유 링크
  • A feature showing one's elapsed time would be simple for Strava to add to the "Run Type" menu because it's already there now, but it currently requires one to call the activity a "Race."  Strava can simply duplicate that menu item and process that allows one to call results a "Race," and then give the new menu item a title other than "Race," such as "Elapsed Workout."  Since the code is already there, adding this extra feature could take less than 20 minutes. 

    2
    댓글 작업 고유 링크
  • Agree... Elapsed time should be the default. Many runners use Strava to train for races and seeing moving time vs elapsed time can be very misleading.

    2
    댓글 작업 고유 링크
  • Will go to Premium as soon as this is changed to elapsed time. But little hope....

    2
    댓글 작업 고유 링크
  • You can try the script I have developped to solve the issue: https://github.com/cgoillot/GPX_Correct

     

    0
    댓글 작업 고유 링크
  • I agree completely for this! I don't care about my pace or "moving time", I care about the total number of minutes I was jogging for. 

    The "Race" option on a Run is great for runs, but this feature needs to be added for Hikes as well. I want to know exactly how long a hike took me, not how much "moving time" you think I had.

    I'm using Strava to record my total times, so I can keep a log of my fitness and progression. Currently, if I want to accurately record my hikes time wise, I have to set it as a Run, with the Race option selected. 

    0
    댓글 작업 고유 링크
  • Today Strava went nuts and removed more than 3 minutes from my 45 minute run even though I never stopped. Usually my Suunto Ambit3 watch generates a high quality GPS data so I was really surprised to see so much discrepancy.

    Here are mile splits according to Strava: 

    8:36, 8:38, 8:42, 7:57, 7:53

    And here are the actual mile splits:

    9:18, 9:37, 10:00, 8:00, 7:56

    The second and third miles had some hills and tree coverage so it is possible the GPS data was less accurate, but that isn't the reason to cut so much time.

    The overall distance is the same. I'd never pay the premium membership until Strava starts taking the data seriously. I don't need to impress anyone with faster, unrealistic pace.

     

    2
    댓글 작업 고유 링크
  • Actually for trail runs both moving time and total elapsed time are important. I often make breaks for various reasons (enjoying the view, taking pictures, have a snack, get water from a creek ...). The moving time reflects my performance, but the elapsed time is the real time I needed. I would like to have both displayed, with the elapsed time in the graph that displays elevation, heart rate and cadence. This would help me make planning decisions for similar runs.

    -1
    댓글 작업 고유 링크
  • Well, the fact that almost three years passed from not addressing this issue tells me nothing but that Strava doesn't care about it. They do not even post here anymore, which is impolite to all of the users.

    I switched to Sports Tracker. I strongly encourage all of you to do the same, since there is no any sense of using Strava with this behavior.

    I didn't remove my account from Strava before, but after reading almost everything on this thread and seeing Strava did nothing, I am going to remove it right now.

    Good bye Strava and good job, another user lost.

     

    0
    댓글 작업 고유 링크
  • The last comment from Oliver is actually important. In Movescount with time on x-axis of the charts and the chart zoom feature I can do pretty good analysing of non-running time in my previous races and see where I can improve. I can find out exactly how long I spent at each aid station (cadence chart is usually good for that). In Strava even if you switch run type to race, breaks are still invisible (because of mileage on x-axis).

    1
    댓글 작업 고유 링크
  • Oliver, Strava cuts way more time than a sum of your breaks. Moving time would be useful if it was correct, but it isn't most of the time. Just today Strava reduced my 3h15m run to 2 hours. I had several stops but there is no way I was stopped for 1h15m - 30-35 minutes at most. So Strava has cut extra 40-45 minutes which is a lot if you think about it. This was a slow run/hike on a challenging icy terrain with a lot of elevation gain. But still that isn't a reason to reduce my time and inflate my pace that much. This actually makes my run look like a lesser effort than it actually was.

    2
    댓글 작업 고유 링크
  • Strava support, you could at least reply to this thread and provide an ETA or close the feature request .

    Garmin does this pretty well, in addition to much faster watch sync better iphone App, colour screens even in entry level watches. So if you want to cater for cyclers and people that prefers this moving time  fine.. just tell the runners and they'll go buy another brand!!

    2
    댓글 작업 고유 링크
  • I’m training with some mates trying to compare times isn’t possible without this feature. Tagging as a race does work... but it’s not a race, we are training and comparing times. Would be a great feature to include.

    2
    댓글 작업 고유 링크
  • I cannot express how much the "moving time" element of Strava annoys me. It is the number one factor that detracts from the app. If I have to stop to drink water or get food on a trail run, so be it. It is still part of the length of my overall workout. To ignore this will artificially pump up my stats. I want to know my real stats, not some stats that Strava thinks will make me fell better about myself.

    2
    댓글 작업 고유 링크
  • Requests for this have been completely ignored. For me who does fell / mountain running Strava ignores the time spent ascending slowly. This make my data worthless. Why anybody would want to subscribe to Strava is beyond mw, what a waste of money. There is much better analytical data available from both Garmin Connect and Moves Count. If my running weren't on Strava I really wouldn't bother.

    0
    댓글 작업 고유 링크
  • I really think it depends on the type of activity. If you do 100Km and you stop on the top of the mountain for a 20 min lunch rest then you dont want this time to be counted. In certain cases you dont want to screw up your stats just because you had a flat tire or to lace your shoes. I also understand that certain people want to have rest time included in the activity. I think they should provide more features there.

    0
    댓글 작업 고유 링크
  • I'm with Jonathan H. on this (and others).  I just went out for a ride today with some friends for a spin and all of our Garmins registered 16.6 avg pace.  I have my Garmin set to not calculate when I'm not moving (an I have speed and cadence sensors going along with the GPS).  It works just fine.  But strava took my ride down to a 14.4 avg pace making it look like I got dropped, bonked, or something.  We will stop for flats, mechanical issues, to let cards get around us at stop signs to be courteous and not bleep-holes and all of us have our Garmins set to not calculate that stopped time.  This is lame and to quote Jonathan H. - It is the number one factor that detracts from the app.  I FULLY agree.  I understand what one of the forum comments mentioned about the running and wanting to track that non-moving time.  As one of the comments also mentioned, there should be a switch in a config area that can be toggled for this (and not just for one ride).  Hoping to see some progress on this soon.  Thank You!

    0
    댓글 작업 고유 링크
  • Both values have meaning to me, so I don't know why they don't just display both. Or, if that takes too much space (I actually don't think so), just have a toggle button.

    0
    댓글 작업 고유 링크
  • I cancelled my subscription today because of this issue. I'm not interested in moving time. I would think that the actual time of your training session would be the default setting and if you wanted to see just moving time then there would be a toggle for that. The last official response to this thread is well over a year ago now so it seems that hee haw is ever going to be done about it. Peace ✌️

    1
    댓글 작업 고유 링크
  • @Brian Williams, Strava makes it very confusing with how it handles the auto-pause. Well, if you have a Garmin device and you use a pause during an activity at least once, or if the auto-pause activates, then Strava switches into a mode where it turns its own moving time algorithm off and just reports the entire elapsed time. So people who use an auto-pause on their device essentially get opposite of what they want. 

    And vice versa, people who want to see the entire time don't use auto-pause on their devices, but then Strava forces its moving time algorithm during upload and throws away any time it considers non-moving.

    And to make this worse the workaround above works only with Garmin devices and all owners of other brand devices can't control this at all. For example, the moving time algorithm is always forced on me when I upload from my Suunto Ambit3 watch.

    It would be way simpler if moving/non-moving time was always decided at the device level (e.g. manual pause or auto-pause) and no extra processing was done on upload. That's what all other platforms do. I guess, historically Strava couldn't do that because GPX files don't contain information about pauses so Strava had to invent this not-very-well-working moving time algorithm.

    1
    댓글 작업 고유 링크
  • The default pace shown on each activity really should be elapsed time, as is done for races. It's the only honest pace calculation. If  people want to also see moving time, that's fine, but don't use it for pace. If there is actually demand for moving time pace, add it as a reference in the workout summary, but don't imply that it's your actual pace.

    3
    댓글 작업 고유 링크
  • This thread is up since 2015 and nothing has been done . Is there anybody watching this forum at all from Strava ? I don't think so. It doesn't take a smart person to understand what we want here . Let users define that moving time or elapsed time is used to define Pace ! Even if it doesn't make any sense to keep the moving time function: let it be users defined so we can have a choice ! 

     

    Come on guys. 3 years ! 

    1
    댓글 작업 고유 링크
  • Posting to pile on regarding this issue. I've been noticing this more and more lately.

    I use a Suunto Ambit3 Peak which automatically syncs my data over from Movescount.

    I went back and spot-checked quite a few runs. I run a similar route multiple times per week, and have seen differences in moving/elapsed time as low as 6 seconds, and then this morning's run, nearly 2 minutes. I do not stop for breaks, nor do I slow down to even a brisk walking pace at any time during my weekday runs. I am moving 100% of the time, from the instant I press start on my watch, to the instant I stop it. I do have a few moderately significant climbs in my run, which is where this algorithm really seems to show itself. On flatter routes, the issue is definitely less pronounced.

    As a test, I tried exporting a GPX track from an activity from Movescount, then manually importing it to Strava. This method appeared to show my elapsed/moving time as the same (which it was). I then compared with the same activity that had been automatically pulled in from Movescount. I could see how Strava had "smoothed" the elevation profile and totally skewed the pace data. 1 kilometre of running still appeared to be 1 kilometre when looking at the map, but the pace and time taken to run that distance was inexplicably different. Even the elevation gain is completely different, usually granting me more climbing than was actually accomplished.

    I'm not sure if disabling automatic sync and just manually uploading everything is a functional workaround until Strava finally looks at this issue (not getting my hopes up), or if I just managed to luck out with the one run I tested with. If it is, then why bother having the automatic integration if the data is going to be imported and then skewed right away?

    I have definitely noticed this issue more since I switched from a simple Garmin device (Forerunner 15) to a Suunto watch last fall. It's my assumption that Strava "trusts" data more that comes from a watch that doesn't include the barometric altimeter data (which is odd, because these more expensive watches that have these additional features would presumably give you a more accurate representation of the terrain and distance covered). The data that appears in Movescount is always dead-on accurate and consistent. I'm more inclined to trust the data that comes off the device that was physically strapped to my body while I was performing my activity, rather than what some algorithm thinks I accomplished by looking at the data after the fact and arbitrarily saying I was standing still for minutes at a time during a 45 minute run.

    I don't understand the hesitation to at least give users the option to display their data using either the elapsed or moving time, particularly in instances when that "moving time" is completely meaningless and in no way reflects what actually happened during the activity.

    3
    댓글 작업 고유 링크
  • I hate the fact that Strava appears to know exactly what I want when it comes to elapsed time versus moving time when doing indoor runs. I'm definitely not the only one who has a problem with this.
     
    I had to pause my run to take care of some "business", and I of course, paused my Garmin.
     
    Garmin Connect is polite enough to give me BOTH times. But Strava chooses elapsed over moving. Why is it so hard to just give users the option to choose which one is included in their activity?
     
    Or here's a crazy idea: INCLUDE BOTH!!!!
     
    And the fact that Strava has not responded to this on their community support page at all is proof once again, they really just don't care.
    2
    댓글 작업 고유 링크
  • I don't know why this elephant-in-the-room issue has been ignored by Strava for so long. Maybe the bottom line is that the marketing folks at Strava know that in most cases using moving time will make paces look better, and people will generally be happier to see their paces look better, so those happy people will prefer to use Strava over some other [more honest?] app that doesn't make them look as fast.  Maybe it's about the marketing. Off hand, I can't think of any other reason (since it would be such a simple fix). "I like Strava because Strava makes me look good!"

    3
    댓글 작업 고유 링크
  • Really would like to see a feature to voluntarily choose COUNT ALL ELAPSED TIME.  Pulling my hair out regarding the Auto-pause, which is not a true Auto-pause, because pausing also when disabled..... How about linking disabled Auto-pause to automatically COUNT ALL ELAPSED TIME. That would be awesome. Thanks for considering this.

    0
    댓글 작업 고유 링크
  • Don't pull your hair out dude, just Tag as "Race" and you get total elapsed time.  This gives you that and this was Strava's response when I queried them about Running and move time.

    -3
    댓글 작업 고유 링크

댓글을 남기려면 로그인하세요.

원하는 것을 찾지 못하셨나요?

새 게시물