완료

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.

331

댓글

  • 공식 댓글

    As of February 20, 2020, we will now show moving time and elapsed time, as well as pace based on elapsed time, on the mobile activity analysis screen for all activity types. 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. 

    Athletes still have the ability to tag activities as races, which will show elapsed time instead of moving and use elapsed time for average pace and splits. Runs in which athletes pause/unpause their devices will also continue to respect the time that the device was unpaused as the moving time.

    For more about moving time, speed, and pace calculations, see Moving Time, Speed, and Pace Calculations

    댓글 작업 고유 링크
  • Completely agreeing!

    For me, there are absolutely NO reason what so ever to use anything else than elapsed time. It's perfectly fine that strava wishes to give us the possibility to record moving time (and if it worked it would be even better) but why on earth is this function not voluntarily????? For me this gives me some trouble since Strava belives that i am not moving a couple of minutes of my run, when truth is I never stopped once during the run.

    Give me the possibility to choose atleast. When running in the terrain moving time is of no interest.

    48
    댓글 작업 고유 링크
  • I strongly agree with this one. Also Strava regularly displays my total time and elapsed time as different when I don't stop at all. This regularly happens in races for me and therefore displays time incorrectly. Garmin Connect has been much more accurate here.

    47
    댓글 작업 고유 링크
  • Please make the "moving time" optional. Elapsed time is more accurate - I have no need for paces calculated using moving time.
    36
    댓글 작업 고유 링크
  • I fully agree with the proposal here. Moving time is a meaningless metric to me personally and I suspect this is the case for a lot of runners. The suggestion of re-tagging each training run as a 'race' as the solution does not really work as then there would be no differentiation between training runs and races in my training log. Particularly when running (or walking with hands on knees, as is mostly the case!) on steep terrain, strava may be calculating this as non-moving time which is not the case. Even if I do stop to catch my breath on a steep incline, I think it is only fair that this time is included as the breather surely helps my pace in the remainder of the run. Please make it optional to select elapsed time for all activities, not just races. Thanks.
    30
    댓글 작업 고유 링크
  • if you edit run mark it as a race and it recalculates on elapsed time

    17
    댓글 작업 고유 링크
  • False sense of accomplishment, indeed!

    Not only should it be an option because of personal preference, but the when it comes to hiking and other slower paced activities, there's a very small difference between moving and not moving from a satellite's perspective.  As a result, my published moving times and pace are regularly extremeley embellished.  For example, on a recent 33 mile hike, my moving time was recorded at 9h11m which is a breakneck speed for a hike of that length and caused many of my followers to applaud in awe, and it was somewhat deflating to have to explain over and over that this was actually an inaccurate recording. Strava is otherwise a great app, but it has to present the data in an honest way and tell the real story. Thanks!

    15
    댓글 작업 고유 링크
  • Recently I moved to a very "hilly" area, where I saw my overall pacing on hills go from 8-10min/mile to something closer to 15-20min/mile! Tons of sections of nearly vertical terrain where running blends in with hiking and sometimes real rock climbing (yikes!). Several of those sections end up with traveling few little distance horizontally, though I might have spent 5min climbing 200feet at nearly 70-80 degrees, and this is assumed to be "resting time".

    Please, add a toggle button that allows one quickly to choose between displaying "elapse time" or "moving time".

    Keep it up!

    14
    댓글 작업 고유 링크
  • I strongly agree! Please use the elapsed time !
    14
    댓글 작업 고유 링크
  • Hi.  As a MTB rider I'm also more interested in elapsed time.  Please add this feature to an other wise good app.

     

    Thanks

    13
    댓글 작업 고유 링크
  • I agree. This would be a nice desired feature!

    12
    댓글 작업 고유 링크
  • Another vote to make moving time optional - if not remove it altogether.  I run obstacle courses and we slow down at obstacles at lot, but that is still part of the race.  I have zero interest in my moving time, it is completely irrelevant.  Setting each run to race is not an option because it only updates the web version not what is shown on the iPhone app so I am forever showing inaccurate, misleading information in Strava.

    I don't understand why Strava can't at least make moving time optional?  If nothing else, it will give them good data to determine how many people actually use moving time versus elapsed so they know where to focus future development efforts :-)

    11
    댓글 작업 고유 링크
  • 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

    11
    댓글 작업 고유 링크
  • I just completed the World Champion Reebok Spartan run in Tahoe where we ran for 15 miles with obstacles sprinkled in-between.  My official time was 4:50 but my app time was 3:48 due to the side activities.  I need the mobile app to show the elapse time not moving time or give me the option to display.  It gives my team a false sense of accomplishment unless they go to the web site version.

    10
    댓글 작업 고유 링크
  • +1 on this. Moving time is of no interest - at leat not to me

    8
    댓글 작업 고유 링크
  • +1 for making elapsed time the default. C’mon Strava, do the right thing.

    8
    댓글 작업 고유 링크
  • I totally agree here and Strava is doing nothing in this regard! Their algorithms are so very bad they make this site useless. There is a "race" tag, but the only thing that does is changing the title of the activity. All stats and comparisons are still using the so called moving time. Please please please, give a way turn off moving time. It's just not working.

    5
    댓글 작업 고유 링크
  • Everything is already based on moving time everywhere. Even when setting type to race. It totally stupid. I did two runs not too long ago and the faster run Strava marked as the slower one. Just because they felt like subtracting a bigger random number of minutes. It's totally insane. And I cannot compare y runs or anything as it all based on the totally non-working moving time. Who in their sane mind wants moving time? If I stop, I rest.  That should count. Why wouldn't it? It makes a huge difference.

    Even if I wanted moving time, Strava's faulty algorithm is so bad it renders it useless. If my heart rate for example keeps going up, why would it think I am stopping, just rolling my thumbs? I am working my butt off, and Strava just shaves off these minutes saying they don't count. WTF???

    5
    댓글 작업 고유 링크
  • +1 for this one. Personally I commute and for me elapsed time (including traffic lights, general traffic etc.) is more relevant as I want to monitor overall cycling time from/to work and other places around the cityy

    5
    댓글 작업 고유 링크
  • I strongly agree.

    Especially since the algorithm which determines the "moving time" seems to be a random number generator !

     

     

    5
    댓글 작업 고유 링크
  • YES! Moving pace is severely misleading for running! I know no reason to use moving pace at all, please at least give an option to switch.

    5
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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??

    5
    댓글 작업 고유 링크
  • 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".

    5
    댓글 작업 고유 링크
  • YES. Please! This is really screwing up my ability to track actual performance. How is this thread a year old with nothing changed? It's SO fundamental to making Strava work properly. I didn't stop at all on my 7-mi run once today and there's a 3-min difference between moving & elapsed. (also worth noting... the verbal cues while running seem to use elapsed time which makes things even more confusing when you log in after and it says you performed way better than you did... quite discouraging, really). Please fix!!!

    4
    댓글 작업 고유 링크
  • This change is essential. Maybe it's OK for interval sessions, or repeats, but anything else is fooling yourself.

    If your "moving time" for a marathon shows 3:30, but you actually took 4:30 because you stopped to stretch, chat to friends at aid stations, or ducked into the shops to go to the toilet, then Strava will report a number that is totally unrealistic for you.

    On long rides/runs/hikes, stopped time is recovery time, and should be included by default.

    4
    댓글 작업 고유 링크
  • Years and nothing updated.

    Goodbye Strava. Hello Runkeeper.

    4
    댓글 작업 고유 링크
  • Well, I'm not paying for premium just because of this "issue". Would someone from the staff care to explain what is the logic behind keeping this pace calculation method? I just want to be heard and maybe I will be convinced that this is the right way to go, if only one of you would explain this clearly. Seriously. It does not bother me much and I don't have respect for people who don't even properly train anyway, but I respect the sports and I expect Strava to respect the sports as well. Moving pace calculation is not even useful in any meaningful way. I can achieve the same 'Moving pace' with a thousand different ways and a thousand different run-rest combination because moving pace statistic is not CONSERVATIVE. I can run with a pace X for 5 minutes and stop for 2 hours then continue running with same speed, or I can run with pace X for 5 minutes and stop for 10 minutes and I can run for 2 hours with same speed and voila! I have exactly the same 'Moving pace' between these two different runs. Why? Because this statistic is completely meaningless. It's not conservative. So why have it? What can I possibly achieve by knowing that moving pace, exactly?

    If some staff would care to explain this thoroughly to me, I will be a completely satisfied customer and I will always pay for premium. I promise you.

    4
    댓글 작업 고유 링크
  • Hi lauren,

     

    You ran 10 minute miles. If you want to see 9 minute in your stats, you should run a little faster for a minute after you obviously rest at stop lights.

     

    In your logic I can even run with a pace of 3min/mile with fifteen 1 minute rests.

     

    Regards.

    4
    댓글 작업 고유 링크
  • Two years and Strava has done nothing about it. I'm going back to Free version

    4
    댓글 작업 고유 링크

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

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

새 게시물