Pace Accuracy
Mstrlucky74
Registered Users Posts: 13
Legendary Explorer
Legendary Explorer
I know there have been some issues with the accuracy of current pace. But how accurate have others found average pace to be? In the attached pic that would be my average pace, correct? Thank you.
0
Comments

Anyone? Thx0

Hi,
You are correct it is average pace of Your run.
Cheers, Maciek0 
Thanks. How accurate have most found this to be?0

It is exactly accurate as long as the distance and time are as it is simply distance/time. Whether it matches what shows on the watch during an activity is a different story but this is simply doing match on the totals.
I hope this helped answer your question. If so, please mark it as a solution so others can look for it if they have the same question.0 
Mstrlucky74 wrote:Thanks. How accurate have most found this to be?
Given that the Spark3 is device dedicated for running I assume that it was the more accurate of the two but short of actually running on a premeasured course I'm not sure how to prove it.0 
TheOtherPete wrote:Mstrlucky74 wrote:Thanks. How accurate have most found this to be?
Given that the Spark3 is device dedicated for running I assume that it was the more accurate of the two but short of actually running on a premeasured course I'm not sure how to prove it.
Even on a certified Half Marathon last week my watch recorded 21.21 KM But Strava says 21.1. It also depends on the race line and if you walk in woods with cloudy weather reception off GPS might be off and you might miss more meters.0 
xray79 wrote:Distance measured by any GPS device is different per device on the same run/route. That is because of the fact that the GPS has an inaccuracy of a few %.0

TheOtherPete wrote:xray79 wrote:Distance measured by any GPS device is different per device on the same run/route. That is because of the fact that the GPS has an inaccuracy of a few %.
A variance in distance between devices is totally normal. The nature of consumer grade GPS is that each data point collected is only accurate to within 15m30m of your actual location. We give it a lot more credit than it deserves, it is not exact, it is an estimate. The watch collects the data points and then tries to figure out a route using them (considering that some points may overlap or duplicate) and a corresponding speed. The watch then smooths the data to come up with the most reasonable route taken according to the algorithm it is programmed with. This is why every watch, even two of the same model, will come up with different distances and speeds, as they are collecting different GPS data. Plus if one device has an altimeter and one does not (your phone may but the watch does not) the difference in vertical distance will also impact the totals. Two GPS points collected may be 50m apart from one another on the horizontal plain, but if they are on a steep hill might actually be 100m in actual distance (think of the length of the base of a steep triangle versus the length of the slanted side). Each device deals with vertical distance differently and some do it better than others.0 
tfarabaugh wrote:A variance in distance between devices is totally normal. The nature of consumer grade GPS is that each data point collected is only accurate to within 15m30m of your actual location. We give it a lot more credit than it deserves, it is not exact, it is an estimate. The watch collects the data points and then tries to figure out a route using them (considering that some points may overlap or duplicate) and a corresponding speed. The watch then smooths the data to come up with the most reasonable route taken according to the algorithm it is programmed with. This is why every watch, even two of the same model, will come up with different distances and speeds, as they are collecting different GPS data. Plus if one device has an altimeter and one does not (your phone may but the watch does not) the difference in vertical distance will also impact the totals. Two GPS points collected may be 50m apart from one another on the horizontal plain, but if they are on a steep hill might actually be 100m in actual distance (think of the length of the base of a steep triangle versus the length of the slanted side). Each device deals with vertical distance differently and some do it better than others.
You bring up a good point about elevation  I don't know if the smartphone is recording that realtime or its just the software (MapMyRun) that is adding that information in after the fact. TomTom's MySports web site also shows elevation for the route I ran so I am betting that is just used to let you know how much elevation you covered, not distance.
I just did some Googling about the same issue and the consensus seems to be that even if are running a very hilly course the amount of extra distance the hills adds is so insignificant that it is more of a rounding error.
Shamelessly stolen from http://www.letsrun.com/forum/flat_read.php?thread=2192407
"An 8% slope would be 8 (feet/meters/yard/cubits...) of rise for every 100 (feet/meters/yards/cubits...) of run.
Doing simple Pythagorean solution of a^2 + b^2 = c^2 where a=100, b=8, gives us:
10,000 + 64 = c^2 (where c is your distance actually run up the slope).
Solving for c gives us 100.3, or a difference of 0.3%
This means for every mile (5280 feet) measured on the flat when actually running up a steep (8%) slope, you actually ran 5297 feet, or a stunning 17 feet longer. 10 mile run? That's 170 feet difference. You sure you can map anything on mapmyrun to that level of accuracy?"0