Moving Time?

Maybe the GPS was lost and thus there was no pace for a few moments? It's a rather big difference though. Is there a clear drop in your pace when looking at the charts?

Exactly the same is happening to me. I ran 5k the other day in 20'20" but the "moving time" says 18'29", almost 2 minutes different. The same happened in a 10K race, this time the difference between the real time and the moving time was 1'08"......
It is too much difference, I hope it is not because the GPS gets lost because that would mean that the distance is not well calculated neither.

Any idea how to solve this??

Thanks

OK, wild guess here --

Position location is within about 10 feet. You're moving maybe 7 mph tops. Somewhere in the course of the run you're handing off from one group of satellites to another and the "resolution" on the triangulation is rounding off on your position.

You might check your accuracy by tracking times at a faster pace -- log the course in a car at 30 mph.

Anyone figure out yet how to get moving time in older data? the data uploaded today has it, but the data preivously in doesn't. Obviously you need to trip a recalc but I can't seem to figure out how to do that!

thanks

-R

Anyone figure out yet how to get moving time in older data? the data uploaded today has it, but the data preivously in doesn't. Obviously you need to trip a recalc but I can't seem to figure out how to do that! thanks-R

For older rides just open the ride and go down the left column to the bottom and select Elevation Corrections Enabled. After the correction is applied you will also find that Moving Time has been added for that ride. :D

OK, wild guess here --

Position location is within about 10 feet. You're moving maybe 7 mph tops. Somewhere in the course of the run you're handing off from one group of satellites to another and the "resolution" on the triangulation is rounding off on your position.

You might check your accuracy by tracking times at a faster pace -- log the course in a car at 30 mph.

Actually, that pace (4 min/Km) is around 9.2 or 9.3 mph.
But that is exactly my point, if the GPS gets lost and during that triangulation believes that one it's not moving.. then the measure of the distance when you run is not accurate neither (unless is recalculated later), which defeats the whole purpose of the GPS

Same problem here. For years I've been recording my exact moving time to certain points on my rides. Always used a cheap cycle computer. Now that I have this cool, expensive device, I find I can't rely on "moving time"!! And to further complicate things, I get three different times for every ride: "time", "moving time" and "elapsed time". So which is which?

Directly from the FAQ:

Garmin Connect provides three Time measurements on the Details page:

Time

Time is the recording time reported by the device. For Fitness devices, this should equal the Time value reported on the device. For other devices, this should equal the amount of time elapsed from the actual Start and Finish time of an activity.

Avg Speed/Pace is based off the Time value.

Moving Time

Garmin Connect calculates Moving Time by removing the amount of time when the user is stopped. This is helpful for customers who upload activities with a Garmin device that either don't have AutoPause or have AutoPause turned off. For those who have AutoPause turned on or hit the Stop and Start button in the middle of an activity, the Moving Time should be very close or equal to Time.

Avg Moving Speed/Pace is based off the Moving Time value.

Elapsed Time

Garmin Connect calculates the Elapsed Time by the amount of time elapsed from the actual Start and Finish time of an activity. This is helpful for customers with a Garmin device that have AutoPause turned on or hit the Stop and Start button in the middle of an activity. For those who don't have AutoPause or have that feature turned off on their device, Elapsed time should be very close or equal to Time.

In case you forgot where to find the FAQ - right here: http://connect.garmin.com/help/faq#details

Have been enjoying exploring the new features in the recent update, especially liking having elevation correction and the ability to edit summary data.

One query though regarding Moving Time. How is this calculated? I know it is supposed to be the total elapsed time minus any 'stopped' time, but yesterday I went for a short run and uploaded it so that I could check out the data in the 'new' Garmin Connect. I know that I ran continuously for 25 minutes (24:59 according to my device, TC and GC) but my Moving Time is given as 24:32. I don't know where the other 27 seconds went?! I was running the entire time on a route where there are no stops for traffic etc. Any ideas?

Hello Adamjowitt and Paticorunner:

I have encountered the same problem as you both have rightly identified. This has been occuring for many of my recent activities.

I have exported the data of the activities with errors to find out where the issue originated from. The bug appears to be at the point where each new lap begins where the speed becomes nil for a few seconds. This should not be the case obviously. If you add up all the seconds with no speed of all affected lap changes, you get the total difference in time between the moving time and the time. I am assuming here there was no time in the activity where your speed was nil or had very low speed, as the case you have described.

I have advised the Call center at Garmin earlier today so that the engineers are aware of it. The person I have talked to understood quite well what I described so that he should provide enough hints to have it fixed.

Hope this helps. Until this is fixed, I would generally not rely of the moving time related statistics.

Hope this helps and thanks for documenting the issue in the first place as I too was wondering what was happening.

Sylvain

Thanks Sylvain, I wonder if they will get around to fixing this anytime soon?

It isn't usually a big problem, but it is a bit annoying. I have been looking through some of my recent runs and found that most laps have a Moving Time 2 - 10 seconds less than the Elapsed Time. Recently I have found a few laps where the Moving Time is actually 1-2 seconds greater than the Elapsed Time!?

Sometimes there are weird results with short laps. I autolap every km and sometimes find I end a run just after a lap has been recorded. The other day I stopped about 7.5sec after my 5km autolap, so ended up recording a short lap of 22m. GC shows that the Moving Time for that lap was 0:00, so somehow I managed to cover 22m in no time!

Because all of my runs are continuous with no stops and starts I just look at the Total Time and don't worry about the moving time.