If you have gone into our mapping app recently you will have already seen a popup with a new release note which says:
If you load a GPX track1 then, as well as telling you the elapsed time and average speed, it now also shows you the moving time and average moving speed. Calculating these figures is an inexact science when relying on GPS data due to "jitter" so this is an experimental feature and we would be interested in your thoughts on whether you think the figures we are getting are accurate and how they compare with the figures quoted by your GPS.
What this means that if you load a GPX track into our app then the track stats box is now a little larger with more information in.
To illustrate this here's a walk we did up Whernside some years ago.
As with the previous release we still have Elapsed Time (which is 5h 15m 19s in this case) and Ave. Speed (1.66mph 2.67kph) but now we also have Moving Time (4h 3m 19s) and a (moving) Ave. Speed (2.15mph 3.46kph).
So that suggests we were stationary for 72 minutes which, at first glance, seems high. However when you look at the data we didn't start until 3 minutes after the track begins, we ended 3 minutes before the track ends, we stopped at the foot of the Ribblehead viaduct for 9 minutes, 8 minutes on the bridge over the railway line, 5 minutes at Netherscar, 3 & 2 minute breathers on the way up, 29 minutes for lunch at the summit, 4 minutes for some reason coming down, 1 minute when we met the Dales High Way, and another 3 minutes on that Way.
In total that's 70 minutes I've identified and suddenly the moving figures seem very plausible.
However, and this is big "however", calculating moving time is a black art as all GPSs suffer from "jitter" (so even if you sit still you still appear to be moving about a bit) and everyone has to cope with that when calculating moving times. So we would be interested in what your GPS itself says your moving time or speed is for any tracks you upload, how it compares with what our app says, and which you think is more accurate.
Let us know, either here or directly.
Looking at the moving time data for some of my tracks I get the following results (list is in the format walk name, WalkLakes time, Basecamp time, GPS unit time from screen shot, Nasmith Time - track converted to route in Basecamp then loaded into WalkLakes) times in hrs & min
Black Mountain inc Carmarthen Fan, 6.37, 5.39, 5.55, 6.52 Scafell Pike, 7.12, 6.24, 6.27, 6.15 Great Gable, 6.19, 5.11 , 5.08, 4.51 Helvellyn, 5.37, 4.42, 4.41, 4.40 Newlands Round, 6.34, 5.23, 5.38, 4.52
At this stage I'd be unwilling to say which is the most accurate, but I'm a quite a quick walker & tend to overtake most people and often when confronted by a boulder field take longer & quicker strides and use momentum to keep from toppling rather than contemplate & plan each step, also on day walks lunch is normally taken in 2 stops, plus the comfort breaks we all take but don't normally mention, then there are the momentary stops for photo's which I tend to take a lot off. With regard to the above tracks the 3 middle ones were done in great heat last autumn and therefore I stopped when I normally wouldn't & on the Newlands round I was talking to someone waiting at dale head for 19min.
For me I've been recording the Basecamp moving time & the converted Nasmith time to get a rough comparison and use that knowledge of what I'm capable of when plotting new walks, which I feel is the most important thing.