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

Comments

227 comments
  • I don't understand why elapsed time would be difficult for a programmer. It's pretty simple: calculate the difference between the clock time when you press "start" and the clock time when you press "finish"; or start a timer (also easy to do) with "start" that is turned off with "finish": then calculate pace based on the total elapsed time. Easy peasy. 

    Until today, I thought I was getting elapsed time by having "auto-pause" turned off--but no. Frustrating--I have no idea now what my true pace has been. Seems the only option is to go back through each and every activity (I run every day) and turn each run into a "race." 

    I like Strava because most of the local running community is on it. But I'm going to look for a better run-tracker. It is absolutely ridiculous that Strava doesn't even offer an option for elapsed time. 

    1
    Comment actions Permalink
  • I recently realized that I'm having the same issue...when I press FINISH on my iWatch, the run time is accurate but once the data is uploaded to the Strava app on my iPhone, the run time has been "adjusted".  I really want to track the total elapsed time of my run.  This seems completely odd that this is an issue.

    But as a band-aid, I wonder if choosing "Outdoor Walk" on my iWatch instead of "Outside Run" would give me real elapsed time, since this option already does not allow auto-pause?

    1
    Comment actions Permalink
  • Moving time? Really? Who thought that was a good idea. There's a pause button isn't there???!! Come on devs, this should not be a hard feature to implement.

    2
    Comment actions Permalink
  • Ok since I'm still getting emails from this a few YEARS later, here's what I do if I want ELAPSED TIME to be equal to MOVING TIME. This means strava will count time where you don't move and calculate your pace, so if you run 1000m in 500/500 (1:30 per 500) and take a 2 minute break in between, your final pace will be 5 min/km (ELAPSED TIME) instead of 3 min/km (MOVING TIME)

    THIS MIGHT ONLY WORK IF YOU HAVE A WATCH
    Strava respects your pauses, meaning if you don't touch your watch at all except START and STOP you will get MOVING TIME and all your PAUSES will be deleted from the default track. If you at any point you pause your watch manually, Strava will respect that and will not cut the time where you STAND STILL, including it in the default calculation that will be shown

    So basically after you start your activity, do a pause then resume, final time should be EQUAL for BOTH MOVING AND ELAPSED. 

    0
    Comment actions Permalink
  • Adrian, this trick with pausing the watch works only with Garmin watches. I have a SUUNTO watch. I just tested this trick a few days ago and confirmed that it doesn't work. The right solution would be to rely on a device auto-pause and never post-process the data on upload. Then everyone would be happy.

    0
    Comment actions Permalink
  • Obviously Strava does not care about this issue despite at least 5(!) years of complaints about it.

     

    Apparently they deliberately are leaving this as it is, presumably because the bulk if their userbase loves to feel like they're faster than they actually are....

     

    Time to get rid of the premium subscription, why pay for a service that doesn't actually give you just that...service.  

     

    1
    Comment actions Permalink
  • Adrian Chiru: Cheers, I tried this trick with Strava on Apple Watch, unfortunately it doesn't work :(

    Sent a feedback email to Strava Support over a month ago, still zero response.

    So irritating for many athletes, especially the trail/ultra community. Noticed Strava have a presence at UTMB this week, I wonder if it will highlight to them the problem! Great that the top athletes have their races available on Strava for all to view, shame it is impossible for them to show the correct race time. e.g. Kilian's 2017 UTMB 2nd place was 19:16:59 (https://utmbmontblanc.com/en/page/107/107.html), Strava time ... 18:46:15 (https://www.strava.com/activities/1165484495). Such a fundamental error, you can see from the elapsed time over 30 mins is auto-paused. Come on guys, this is an athlete with over 85000 followers, people notice these kinds of things! 

    0
    Comment actions Permalink
  • Not sure if this has been said before, but I noticed that if you log in to the activity using the full website (ie. not the app) there is an option under the distance to “correct the distance”. Doing this changes the time to the total elapsed time without having to select race.

    0
    Comment actions Permalink
  • Cheers @Neil. Actually I tried this before, but 'correcting the distance' just allows Strava to apply an algorithm to parse the raw data from your GPS device, if you press 'revert' afterwards it goes back to the GPS device. It is used to remove outliers and smooth noisy data (https://support.strava.com/hc/en-us/articles/216919487-How-Distance-is-Calculated).

    Although it does change the time (for some reason - they don't specify why - it is a black box process unfortunately) it doesn't revert back to the elapsed time. I tried it on several of my files and it just added a bit of time, but not to the total elapsed time. I have no idea why correcting the GPS positions should change the time of an activity ...

    0
    Comment actions Permalink
  • This is at the very top of the list for feature requests, and I can't imagine it would require too much resources to add a switch to the activity options to calculate the activity based on moving time or total elapsed time.... I mean it sort of already done for you when you click 'race'. There are many activities where the 'moving time' calculated is just plain wrong, and elapsed time is a far better indicator.

    3
    Comment actions Permalink
  • I strongly agree. I use a Fitbit Ionic to track playing Ultimate Frisbee. On my Fitbit app my game will be for example 1.5 hours, but when it syncs with Strava it shows 1 hour and with a much higher run rate, as some of the time is spent standing or walking slowly. I don't want to mark it as a race, just as a normal activity.

    0
    Comment actions Permalink
  • Grrrrrr.... Strava, please fix this already...

    0
    Comment actions Permalink
  • After switching from Surge + Fitbit uploads to Apple watch and the native app my bootcamp sessions have dropped from an hour to 12 minutes  .  How is this bug still a thing?

    1
    Comment actions Permalink
  • +1 for this. I would much rather view my times/splits as the actual time I started and stopped my run, but I don’t want to have to mark every single run as a “race”, because I also like to differentiate between training runs and race days on the training log.

    1
    Comment actions Permalink
  • Good to see that over 3 years later this is still a problem.  I put running on the back shelf for a while to focus on other activities.  I was surprised to see such good numbers when I got back into it.  It wasn't until I started a training regiment that had "you run for 30 minutes" sessions that I noticed it was off.  For example, I ran 30 minutes last night, and Strava only shows 26.  It was run walk intervals, but I never stopped, and auto pause is off.  This doesn't work for me.

    2
    Comment actions Permalink
  • I was directed by support to leave my request here - I also would like to have the option of choosing elapsed time as my default rather than moving time.  I don't feel moving time is very useful to me - and it makes my average pace look faster than it actually is.

    2
    Comment actions Permalink
  • I suppose this modification must not be difficult.  They never apply such a modification.
    I would like to migrate to another applications.  Do any guys know any recommended apps?

    1
    Comment actions Permalink
  • OK here's my problem. Please let me know if I'm missing something or being obtuse. I train & race on my bike in an indoor velodrome. Both sessions mean I warm up on rollers, train/race for c20mins, rest for c15mins and then repeat that cycle maybe 4 times. I use a Garmin Edge 820 to record data (speed, cadence, HR and distance). It's set to autopause, as I don't want the timer running when I'm on a rest break. Because it's indoors the GPS is turned off.

    Rides are uploaded to Garmin Connect and then onto Strava. Gamin Connect records the ride perfectly, ignores the rest breaks so gives me average stats for only when my bike is moving. Strava seems incapable of doing this and averages my stats against the total time from when I switch the Garmin on to when I switch it off again. I've tried GPS on and off, manual stopping & starting the Garmin, but nothing seems to work. Am I doing something wrong or is Strava just not capable of this? 

    Starve does recognise the AutoPause when I'm outside and with GPS on. If I stop on a ride (for ubiquitous coffee & cake) Strava won't record total time, just moving time. 

    I'm foxed by this!

    1
    Comment actions Permalink
  • Glenn Grant - you're not being obtuse, or missing anything.

    The problem is that Strava is total rubbish as a training tool, it is nothing more than a social media app for athletes.

    They are fully aware of this but like they themselves say, just because something is popular amongst the community, doesn't mean that they will implement it.

    That, to me, translates as "we just don't listen".

    Stick with your Garmin software.
    Use free version of Strava, but please don't encourage them by actually giving them money.

    I have been a premium subscriber for years, but have now cancelled it because of this and other issues (no heart rate notifications).

    2
    Comment actions Permalink
  • As I see it Strava can make the change which if extremely simple (user prefers actual time then use actual data, if user prefers moving time then use the inaccurate calculation). Telling us they don't have time to implement is a pathetic excuse.

    More info:

    https://support.strava.com/hc/en-us/community/posts/208856437/comments/360003221052

     

    2
    Comment actions Permalink
  • The official comment on this post is from August 30, 2016, 2.5 years ago, stating "we know that [this requested feature is] popular within the community" and "This proposed project will be considered as soon as resources allow."

    Does that mean that despite 205 comments from the community, most of them in favor of this feature, you did put resources on this in the last 2.5 years?

     

    1
    Comment actions Permalink
  • YES!  Please allow users to specify elapsed time vs. moving time!  Paces based on Strava's calculations of moving time are very misleading and inaccurate.

    0
    Comment actions Permalink
  • This is a problem for Indoor Swimming as well.  It is very annoying that Pace is reported slower on Strava.

    Garmin Connect shows Time 1:09:17 and Avg Pace 2:16 min/100 yd.
    Strava shows 1:03:32 Moving Time and Pace 2:21/100yd.
    Distance and Calories match.

    Looking at laps, the times match on each platform so it seems the Strava Pace is calculated using Total Time despite correctly reporting moving time.

    0
    Comment actions Permalink
  • I do endurance racing, in which rests are an integral part of racing strategy.  

    I just did my first race using Strava and discovered all the stats ignore resting time and steep uphill.  MapMyRun doesn't do that.  I'm now officially moving back to MapMyRun.

    Bye Strava.

    1
    Comment actions Permalink
  • +1 I did a 7 mile run yesterday and Strava decided to auto-pause all of the hills and knock 4 minutes off my time. My Suunto watch shows the accurate pace but when importing to Strava they mess with the data and it becomes useless. Accuracy is everything.

    0
    Comment actions Permalink
  • I'd also really prefer elapsed time over moving time. As i'm doing something called "orienteering" there are times where i can end up moving very little trying to figure out where i am and where i need to go. Which makes "moving time" really misleading as the times where i move little is very much a part of my run.

    1
    Comment actions Permalink
  • Check out MapMyRun.  It provides this functionality.

    0
    Comment actions Permalink
  • So, any updates from Strava 3 years later?

    2
    Comment actions Permalink
  • I use Strava for orienteering only to be dismayed I can't switch off the 'moving time' option. It gives a totally false result. I want to include time I stop for map reading or at control points, it's part of the race and training. I have to keep the recordings 'private' as they don't tally anything like with the real race results and it could look like I was trying to embellish my efforts :( 


    3
    Comment actions Permalink
  • I totally agree with this. I find elapsed time more useful than movint time.

    1
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post