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.

320

댓글

  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • Please change this.. I want to stay with strava but can't without reliable times

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

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

    0
    댓글 작업 고유 링크
  • MapMyRun already has the feature built in.

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

     

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

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

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

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

    0
    댓글 작업 고유 링크

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

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

새 게시물