Difference between revisions of "GPS Accuracy"

From Fellrnr.com, Running tips
Jump to: navigation, search
User:Fellrnr (User talk:Fellrnr | contribs)
User:Fellrnr (User talk:Fellrnr | contribs)
Line 1: Line 1:
I evaluated the real world accuracy of GPS watches using the {{Garmin 310XT}} and the {{Garmin 910XT}} while running over 1,100 miles/1,800Km and recording over 4,000 data points. On average, the watches were remarkably good, but this is because the errors even out.
+
I evaluated the real world accuracy of GPS watches while running over 1,500 miles/2,800Km and recording over 7,000 data points. Under good conditions the watches are all remarkably good, but when things get a little tough the differences become more apparent.  
  
 
=Methodology=
 
=Methodology=
Simply taking a GPS watch on a single run does not provide sufficient data to reasonably evaluate its accuracy. So to gather the data for this test I marked my usual running route at quarter-mile intervals, using a [http://www.jonescounter.com/ Jones counter] to provide an accurate measure of distance. The Jones counter is the device used to certify courses, and I followed the [http://www.usatf.org/Products-/-Services/Course-Certifications/USATF-Certified-Courses/Certify-Your-Course.aspx USATF course certification process]. The course I run along is a little challenging for GPS, with lots of twists, tree cover, and one bridge that I go under. The bridge carries a 4 lane road, so it's wide enough to cause the watches to briefly loose GPS signal. However, I believe that it's reasonably representative of real-world conditions, and probably less challenging than running in the city with skyscrapers. At both ends of the course there is a turnaround, and I set the mark an eighth of a mile from the end. That way I can evaluate how well the watches handle an about turn. So far I have recorded 4,658 GPS points, 3,881 using a {{Garmin 310XT}} and 777 using a {{Garmin 910XT}}. This represents 1,164 miles/1,874 Km of running.  
+
Simply taking a GPS watch on a single run does not provide sufficient data to reasonably evaluate its accuracy. So to gather the data for this test I marked my usual running route at quarter-mile intervals, using a [http://www.jonescounter.com/ Jones counter] to provide an accurate measure of distance. The Jones counter is the device used to certify courses, and I followed the [http://www.usatf.org/Products-/-Services/Course-Certifications/USATF-Certified-Courses/Certify-Your-Course.aspx USATF course certification process]. The course I run along is a little challenging for GPS, with lots of twists, tree cover, power lines, and one bridge that I go under. The bridge carries a 4 lane road, so it's wide enough to cause the watches to briefly loose GPS signal. However, I believe that it's reasonably representative of real-world conditions, and probably less challenging than running in the city with skyscrapers. At both ends of the course there is a turnaround, and I set the mark an eighth of a mile from the end. That way I can evaluate how well the watches handle an about turn.  
 
[[File:Course Overview.jpg|none|thumb|500px|This is the course I use to evaluate the accuracy of [[Best Running Watch| GPS Running Watches]].]]
 
[[File:Course Overview.jpg|none|thumb|500px|This is the course I use to evaluate the accuracy of [[Best Running Watch| GPS Running Watches]].]]
  
Line 15: Line 15:
  
 
=Accuracy=
 
=Accuracy=
I've divided the laps into those that go under the bridge, those that are immediately after a lap that goes under the bridge, those that turn around and then all the remainder (normal).  
+
I've divided the laps into those that go under the bridge, those that are immediately after a lap that goes under the bridge, those that go next to or under the power lines, those that turn around and then all the rest (normal).  
 
{| class="wikitable"
 
{| class="wikitable"
! Type
+
! Device
 +
! Condition
 
! Count
 
! Count
! Trueness
+
! Trueness (Average)
 
! Precision (Standard Deviation)
 
! Precision (Standard Deviation)
! 95% within +/-
+
! 95% within
! Dropouts
 
 
|-
 
|-
| Normal
+
| {{Polar RC3 GPS}}
| 3,452
+
| rowspan="5"|
| 0.19%
+
Normal
| 3.01%
+
| 897
| 12.0%
+
| style="background-color: #9DCE7E;"|
| 1.8%
+
0.994% (33.1 Ft/Mile 6.3 m/Km)
 +
| style="background-color: #FFEB84;"|
 +
0.037 (195.6 Ft/Mile 37.0 m/Km)
 +
| 0.074 (391.2 Ft/Mile 74.1 m/Km)
 
|-
 
|-
| Under Bridge
+
| {{Garmin 310XT}} with [[Footpod]]
| 252
+
| 2453
| 1.27%
+
| style="background-color: #63BE7B;"|
| 3.51%
+
1.000% (1.9 Ft/Mile 0.4 m/Km)
| 14.0%
+
| style="background-color: #C0D980;"|
| 100.0%
+
0.031 (163.0 Ft/Mile 30.9 m/Km)
 +
| 0.062 (326.0 Ft/Mile 61.8 m/Km)
 
|-
 
|-
| After Bridge
+
| {{Garmin 310XT}} no [[Footpod]]
| 448
+
| 594
| 2.24%
+
| style="background-color: #82C77C;"|
| 3.18%
+
0.996% (18.8 Ft/Mile 3.6 m/Km)
| 12.7%
+
| style="background-color: #FFDC81;"|
| 1.8%
+
0.042 (221.9 Ft/Mile 42.0 m/Km)
 +
| 0.084 (443.8 Ft/Mile 84.1 m/Km)
 
|-
 
|-
| Turn Around
+
| {{Garmin 910XT}} with [[Footpod]]
| 217
+
| 481
| 4.01%
+
| style="background-color: #9ECF7E;"|
| 3.76%
+
0.994% (33.7 Ft/Mile 6.4 m/Km)
| 15.0%
+
| style="background-color: #9ECF7E;"|
| 2.3%
+
0.027 (145.1 Ft/Mile 27.5 m/Km)
 +
| 0.055 (290.2 Ft/Mile 55.0 m/Km)
 +
|-
 +
| '''All'''
 +
| '''4425'''
 +
| style="background-color: #76C37C;"|
 +
'''0.998% (12.4 Ft/Mile 2.3 m/Km)'''
 +
| style="background-color: #DEE182;"|
 +
'''0.034 (178.4 Ft/Mile 33.8 m/Km)'''
 +
| '''0.068 (356.7 Ft/Mile 67.6 m/Km)'''
 +
|-
 +
| {{Polar RC3 GPS}}
 +
| rowspan="5"|
 +
Under Bridge
 +
| 85
 +
| style="background-color: #FA8771;"|
 +
0.952% (252.8 Ft/Mile 47.9 m/Km)
 +
| style="background-color: #F96A6C;"|
 +
0.078 (411.0 Ft/Mile 77.8 m/Km)
 +
| 0.156 (821.9 Ft/Mile 155.7 m/Km)
 +
|-
 +
| {{Garmin 310XT}} with [[Footpod]]
 +
| 212
 +
| style="background-color: #F8E983;"|
 +
0.985% (81.0 Ft/Mile 15.3 m/Km)
 +
| style="background-color: #EDE683;"|
 +
0.035 (186.7 Ft/Mile 35.4 m/Km)
 +
| 0.071 (373.3 Ft/Mile 70.7 m/Km)
 +
|-
 +
| {{Garmin 310XT}} no [[Footpod]]
 +
| 58
 +
| style="background-color: #FFE483;"|
 +
1.018% (96.8 Ft/Mile 18.3 m/Km)
 +
| style="background-color: #FECB7E;"|
 +
0.047 (250.3 Ft/Mile 47.4 m/Km)
 +
| 0.095 (500.5 Ft/Mile 94.8 m/Km)
 +
|-
 +
| {{Garmin 910XT}} with [[Footpod]]
 +
| 42
 +
| style="background-color: #6FC17B;"|
 +
0.998% (8.4 Ft/Mile 1.6 m/Km)
 +
| style="background-color: #C4DA80;"|
 +
0.031 (164.8 Ft/Mile 31.2 m/Km)
 +
| 0.062 (329.7 Ft/Mile 62.4 m/Km)
 +
|-
 +
| '''All'''
 +
| '''397'''
 +
| style="background-color: #FFEB84;"|
 +
'''0.984% (84.7 Ft/Mile 16.0 m/Km)'''
 +
| style="background-color: #FDB87B;"|
 +
'''0.053 (281.5 Ft/Mile 53.3 m/Km)'''
 +
| '''0.107 (563.0 Ft/Mile 106.6 m/Km)'''
 +
|-
 +
| {{Polar RC3 GPS}}
 +
| rowspan="5"|
 +
Post Bridge
 +
| 166
 +
| style="background-color: #FB9474;"|
 +
0.956% (231.2 Ft/Mile 43.8 m/Km)
 +
| style="background-color: #FB8F73;"|
 +
0.066 (348.8 Ft/Mile 66.1 m/Km)
 +
| 0.132 (697.6 Ft/Mile 132.1 m/Km)
 +
|-
 +
| {{Garmin 310XT}} with [[Footpod]]
 +
| 365
 +
| style="background-color: #FFDE82;"|
 +
0.980% (107.0 Ft/Mile 20.3 m/Km)
 +
| style="background-color: #D2DE81;"|
 +
0.033 (172.0 Ft/Mile 32.6 m/Km)
 +
| 0.065 (344.0 Ft/Mile 65.2 m/Km)
 +
|-
 +
| {{Garmin 310XT}} no [[Footpod]]
 +
| 110
 +
| style="background-color: #FEC87E;"|
 +
0.973% (144.3 Ft/Mile 27.3 m/Km)
 +
| style="background-color: #FFE984;"|
 +
0.038 (199.3 Ft/Mile 37.7 m/Km)
 +
| 0.075 (398.6 Ft/Mile 75.5 m/Km)
 +
|-
 +
| {{Garmin 910XT}} with [[Footpod]]
 +
| 86
 +
| style="background-color: #FDBB7B;"|
 +
0.969% (166.3 Ft/Mile 31.5 m/Km)
 +
| style="background-color: #8AC97D;"|
 +
0.026 (134.7 Ft/Mile 25.5 m/Km)
 +
| 0.051 (269.4 Ft/Mile 51.0 m/Km)
 +
|-
 +
| '''All'''
 +
| '''727'''
 +
| style="background-color: #FDC67D;"|
 +
'''0.972% (148.1 Ft/Mile 28.0 m/Km)'''
 +
| style="background-color: #FED680;"|
 +
'''0.044 (231.0 Ft/Mile 43.7 m/Km)'''
 +
| '''0.087 (462.0 Ft/Mile 87.5 m/Km)'''
 +
|-
 +
| {{Polar RC3 GPS}}
 +
| rowspan="5"|
 +
Turn Around
 +
| 92
 +
| style="background-color: #F8696B;"|
 +
0.943% (301.9 Ft/Mile 57.2 m/Km)
 +
| style="background-color: #F8696B;"|
 +
0.078 (411.1 Ft/Mile 77.9 m/Km)
 +
| 0.156 (822.2 Ft/Mile 155.7 m/Km)
 +
|-
 +
| {{Garmin 310XT}} with [[Footpod]]
 +
| 244
 +
| style="background-color: #FCA677;"|
 +
0.962% (200.2 Ft/Mile 37.9 m/Km)
 +
| style="background-color: #FFE383;"|
 +
0.040 (209.8 Ft/Mile 39.7 m/Km)
 +
| 0.079 (419.7 Ft/Mile 79.5 m/Km)
 +
|-
 +
| {{Garmin 310XT}} no [[Footpod]]
 +
| 64
 +
| style="background-color: #FCB079;"|
 +
0.965% (184.7 Ft/Mile 35.0 m/Km)
 +
| style="background-color: #F9736D;"|
 +
0.075 (395.2 Ft/Mile 74.9 m/Km)
 +
| 0.150 (790.5 Ft/Mile 149.7 m/Km)
 +
|-
 +
| {{Garmin 910XT}} with [[Footpod]]
 +
| 48
 +
| style="background-color: #FA8972;"|
 +
0.953% (249.8 Ft/Mile 47.3 m/Km)
 +
| style="background-color: #87C87D;"|
 +
0.025 (132.8 Ft/Mile 25.2 m/Km)
 +
| 0.050 (265.7 Ft/Mile 50.3 m/Km)
 +
|-
 +
| '''All'''
 +
| '''448'''
 +
| style="background-color: #FB9674;"|
 +
'''0.957% (228.2 Ft/Mile 43.2 m/Km)'''
 +
| style="background-color: #FCAA78;"|
 +
'''0.058 (304.1 Ft/Mile 57.6 m/Km)'''
 +
| '''0.115 (608.1 Ft/Mile 115.2 m/Km)'''
 +
|-
 +
| {{Polar RC3 GPS}}
 +
| rowspan="5"|
 +
Power Line
 +
| 167
 +
| style="background-color: #DCE182;"|
 +
0.987% (66.4 Ft/Mile 12.6 m/Km)
 +
| style="background-color: #F2E783;"|
 +
0.036 (188.8 Ft/Mile 35.8 m/Km)
 +
| 0.072 (377.5 Ft/Mile 71.5 m/Km)
 +
|-
 +
| {{Garmin 310XT}} with [[Footpod]]
 +
| 457
 +
| style="background-color: #96CC7D;"|
 +
0.994% (29.5 Ft/Mile 5.6 m/Km)
 +
| style="background-color: #A7D17E;"|
 +
0.028 (149.5 Ft/Mile 28.3 m/Km)
 +
| 0.057 (299.1 Ft/Mile 56.6 m/Km)
 +
|-
 +
| {{Garmin 310XT}} no [[Footpod]]
 +
| 115
 +
| style="background-color: #D2DE81;"|
 +
0.988% (60.9 Ft/Mile 11.5 m/Km)
 +
| style="background-color: #FFE483;"|
 +
0.039 (207.4 Ft/Mile 39.3 m/Km)
 +
| 0.079 (414.7 Ft/Mile 78.5 m/Km)
 +
|-
 +
| {{Garmin 910XT}} with [[Footpod]]
 +
| 90
 +
| style="background-color: #FCEA83;"|
 +
0.984% (83.5 Ft/Mile 15.8 m/Km)
 +
| style="background-color: #63BE7B;"|
 +
0.022 (113.8 Ft/Mile 21.6 m/Km)
 +
| 0.043 (227.6 Ft/Mile 43.1 m/Km)
 +
|-
 +
| '''All'''
 +
| '''829'''
 +
| style="background-color: #B8D67F;"|
 +
'''0.991% (47.2 Ft/Mile 8.9 m/Km)'''
 +
| style="background-color: #C5DA80;"|
 +
'''0.031 (165.2 Ft/Mile 31.3 m/Km)'''
 +
| '''0.063 (330.5 Ft/Mile 62.6 m/Km''')
 
|}
 
|}
  
 
=Interpretation=
 
=Interpretation=
 
What do these statistics mean? This is my interpretation:
 
What do these statistics mean? This is my interpretation:
* Away from the bridge and the turnaround, the average distance recorded (trueness) is quite good, averaging out to 0.19%, which is 30"/74cm per quarter mile.  
+
* Under normal conditions the GPS accuracy is quite good for all devices, though the 310XT/910XT with a Footpod have a slight advantage.  
* Not surprisingly, the trueness drops going under the bridge and is 1.27% (201"/500cm). More interestingly, the trueness just after the breach is even lower at 2.24% (355"/885cm). This suggests that the GPS watches are struggling to reacquire the satellites.
+
* Not surprisingly, the accuracy drops going under the bridge. More interestingly the trueness just after the bridge is even lower, suggesting that the GPS watches are struggling to reacquire the satellites.  
* The turnarounds are even less true than going under a bridge, resulting in an average distance that is out by 4.01% (635"/1,582cm).
+
* The turnarounds are even less accurate than going under a bridge, but Power Lines do not seem to impact accuracy noticeably.  
* The precision of the GPS watches is 3-4%, which means that 95% of samples will fall within 12-15% of the correct distance. For normal laps, that is 95% of laps are within 159'/4.8m per quarter mile.
+
* The [[Footpod]] improves the accuracy of the 310XT and the 910XT, especially on the turn around and under the bridge.
* As expected, the GPS watches have dropouts (use satellite signal) on every lap that goes under the bridge. The watches also have dropouts 1.8% of the time on normal laps.
+
* Without the Footpod, the 310XT has similar problems to the RC3 on the turn around, but the RC3 does worse under the bridge.
  
 
=Recommendations=
 
=Recommendations=
 
This data leads me to a few conclusions.
 
This data leads me to a few conclusions.
 
* GPS watches are accurate enough for most general running.
 
* GPS watches are accurate enough for most general running.
 +
* Adding a Footpod to the {{Garmin 310XT}} and the {{Garmin 910XT}} improves their accuracy.
 
* It takes time for the GPS watches to acquire the satellites. The watches tended to say they are ready to go before they have an optimal lock. Therefore, to improve accuracy try to give them a little more time. Note that some newer GPS watches such as the [http://www.amazon.com/Garmin-010-01128-30-Forerunner-620-Bundle/dp/B00FBYYC90 Garmin 620] have the ability to be preloaded with the satellite positions, reducing this startup time and start up in accuracy dramatically.
 
* It takes time for the GPS watches to acquire the satellites. The watches tended to say they are ready to go before they have an optimal lock. Therefore, to improve accuracy try to give them a little more time. Note that some newer GPS watches such as the [http://www.amazon.com/Garmin-010-01128-30-Forerunner-620-Bundle/dp/B00FBYYC90 Garmin 620] have the ability to be preloaded with the satellite positions, reducing this startup time and start up in accuracy dramatically.
 
* The GPS watches are not accurate enough to perform any type of [Practical Interval Training| interval training]. Instead, use a track or measure out the distance using some other mechanism.
 
* The GPS watches are not accurate enough to perform any type of [Practical Interval Training| interval training]. Instead, use a track or measure out the distance using some other mechanism.
Line 80: Line 263:
 
=Next Steps=
 
=Next Steps=
 
This is an initial analysis of the data I have, and there are a number of further evaluations to do.
 
This is an initial analysis of the data I have, and there are a number of further evaluations to do.
* Separate out the data from the {{Garmin 310XT}} and the {{Garmin 910XT}} to see how they compare accuracy.
 
 
* Gather data from some other [[Best Running Watch| GPS Running Watches]].  
 
* Gather data from some other [[Best Running Watch| GPS Running Watches]].  
** I am in the process of evaluating the [http://www.amazon.com/Polar-Heart-Rate-Monitor-Black/dp/B00BV81U7W Polar RC3 GPS], but I don't think it will make my recommendation for [[Best Running Watch]es. It may however provide a useful example of poor quality GPS reception, and as I've seen some rather erratic tracks (note to self, check Oct 10 run).
+
** I will evaluate the [http://www.amazon.com/Garmin-010-01128-30-Forerunner-620-Bundle/dp/B00FBYYC90 Garmin 620] when it becomes available as it has some promising functionality.
** I will evaluate the [http://www.amazon.com/Garmin-010-01128-30-Forerunner-620-Bundle/dp/B00FBYYC90 Garmin 620] when it becomes available as it has some promising looking functionality.
+
** I am gathering data on an older Garmin 205. It's not a watch I'd recommend, but it will be interesting to see if the technology has improved over time.
 +
** I will soon start gathering data on an iPhone 4S to see how it compares with dedicated devices.  
 
* Add in some graphs of the distribution of accuracy, and possibly a [http://en.wikipedia.org/wiki/Q%E2%80%93Q_plot Q-Q plot] (which shows reasonably [http://en.wikipedia.org/wiki/Normal_distribution normal distribution]).
 
* Add in some graphs of the distribution of accuracy, and possibly a [http://en.wikipedia.org/wiki/Q%E2%80%93Q_plot Q-Q plot] (which shows reasonably [http://en.wikipedia.org/wiki/Normal_distribution normal distribution]).
* Examine and compare specific runs where GPS quality is lower. I have some examples where I recorded the run with two watches, and only one had poor accuracy (and not the same one each time).
 
 
* Check how GPS accuracy changes over the course of a run, as I've seen a distinct tendency for the watches to say they are good to go when they don't really have an optimal lock on the satellites.
 
* Check how GPS accuracy changes over the course of a run, as I've seen a distinct tendency for the watches to say they are good to go when they don't really have an optimal lock on the satellites.
* Look at how accurate the GPS watches are for measuring innovation, and compare with barometric data.
+
* Look at how accurate the GPS watches are for measuring elevation, and compare with barometric data.
 
* Check for any correlation between accuracy and running pace.
 
* Check for any correlation between accuracy and running pace.
 
* Look for any correlation between accuracy and the use of heart rate monitor. The radio signal from the heart rate monitor could interfere with accuracy.
 
* Look for any correlation between accuracy and the use of heart rate monitor. The radio signal from the heart rate monitor could interfere with accuracy.
* Evaluate how a [[Footpod]] influences accuracy. Most of my runs are with a Footpod, and this may improve the accuracy if GPS is lost.
+
* Write up general GPS accuracy.
* Write up general GPS accuracy and talk about WAAS.
 
* Check if the power lines have any impact of accuracy.  
 
 
* List the sources of potential error.
 
* List the sources of potential error.
 
* Evaluate the accuracy of the [[Footpod]] alone, both trueness and precision.
 
* Evaluate the accuracy of the [[Footpod]] alone, both trueness and precision.

Revision as of 16:43, 31 October 2013

I evaluated the real world accuracy of GPS watches while running over 1,500 miles/2,800Km and recording over 7,000 data points. Under good conditions the watches are all remarkably good, but when things get a little tough the differences become more apparent.

1 Methodology

Simply taking a GPS watch on a single run does not provide sufficient data to reasonably evaluate its accuracy. So to gather the data for this test I marked my usual running route at quarter-mile intervals, using a Jones counter to provide an accurate measure of distance. The Jones counter is the device used to certify courses, and I followed the USATF course certification process. The course I run along is a little challenging for GPS, with lots of twists, tree cover, power lines, and one bridge that I go under. The bridge carries a 4 lane road, so it's wide enough to cause the watches to briefly loose GPS signal. However, I believe that it's reasonably representative of real-world conditions, and probably less challenging than running in the city with skyscrapers. At both ends of the course there is a turnaround, and I set the mark an eighth of a mile from the end. That way I can evaluate how well the watches handle an about turn.

This is the course I use to evaluate the accuracy of GPS Running Watches.

2 Accuracy, Trueness and Precision

For this evaluation I'll use the definition of Accuracy as the combination of trueness and precision:

This is an example of high precision, as all the hits are tightly clustered. However, the trueness is poor as all the hits are off center, so accuracy is low.
This shows good trueness, as all the hits are around the center. On average they are on target, but there is poor precision, as the hits are scattered.

We can look at trueness by measuring the average lap length and precision by measuring the standard deviation.

3 Accuracy

I've divided the laps into those that go under the bridge, those that are immediately after a lap that goes under the bridge, those that go next to or under the power lines, those that turn around and then all the rest (normal).

Device Condition Count Trueness (Average) Precision (Standard Deviation) 95% within
Polar RC3 GPS

Normal

897

0.994% (33.1 Ft/Mile 6.3 m/Km)

0.037 (195.6 Ft/Mile 37.0 m/Km)

0.074 (391.2 Ft/Mile 74.1 m/Km)
Garmin 310XT with Footpod 2453

1.000% (1.9 Ft/Mile 0.4 m/Km)

0.031 (163.0 Ft/Mile 30.9 m/Km)

0.062 (326.0 Ft/Mile 61.8 m/Km)
Garmin 310XT no Footpod 594

0.996% (18.8 Ft/Mile 3.6 m/Km)

0.042 (221.9 Ft/Mile 42.0 m/Km)

0.084 (443.8 Ft/Mile 84.1 m/Km)
Garmin 910XT with Footpod 481

0.994% (33.7 Ft/Mile 6.4 m/Km)

0.027 (145.1 Ft/Mile 27.5 m/Km)

0.055 (290.2 Ft/Mile 55.0 m/Km)
All 4425

0.998% (12.4 Ft/Mile 2.3 m/Km)

0.034 (178.4 Ft/Mile 33.8 m/Km)

0.068 (356.7 Ft/Mile 67.6 m/Km)
Polar RC3 GPS

Under Bridge

85

0.952% (252.8 Ft/Mile 47.9 m/Km)

0.078 (411.0 Ft/Mile 77.8 m/Km)

0.156 (821.9 Ft/Mile 155.7 m/Km)
Garmin 310XT with Footpod 212

0.985% (81.0 Ft/Mile 15.3 m/Km)

0.035 (186.7 Ft/Mile 35.4 m/Km)

0.071 (373.3 Ft/Mile 70.7 m/Km)
Garmin 310XT no Footpod 58

1.018% (96.8 Ft/Mile 18.3 m/Km)

0.047 (250.3 Ft/Mile 47.4 m/Km)

0.095 (500.5 Ft/Mile 94.8 m/Km)
Garmin 910XT with Footpod 42

0.998% (8.4 Ft/Mile 1.6 m/Km)

0.031 (164.8 Ft/Mile 31.2 m/Km)

0.062 (329.7 Ft/Mile 62.4 m/Km)
All 397

0.984% (84.7 Ft/Mile 16.0 m/Km)

0.053 (281.5 Ft/Mile 53.3 m/Km)

0.107 (563.0 Ft/Mile 106.6 m/Km)
Polar RC3 GPS

Post Bridge

166

0.956% (231.2 Ft/Mile 43.8 m/Km)

0.066 (348.8 Ft/Mile 66.1 m/Km)

0.132 (697.6 Ft/Mile 132.1 m/Km)
Garmin 310XT with Footpod 365

0.980% (107.0 Ft/Mile 20.3 m/Km)

0.033 (172.0 Ft/Mile 32.6 m/Km)

0.065 (344.0 Ft/Mile 65.2 m/Km)
Garmin 310XT no Footpod 110

0.973% (144.3 Ft/Mile 27.3 m/Km)

0.038 (199.3 Ft/Mile 37.7 m/Km)

0.075 (398.6 Ft/Mile 75.5 m/Km)
Garmin 910XT with Footpod 86

0.969% (166.3 Ft/Mile 31.5 m/Km)

0.026 (134.7 Ft/Mile 25.5 m/Km)

0.051 (269.4 Ft/Mile 51.0 m/Km)
All 727

0.972% (148.1 Ft/Mile 28.0 m/Km)

0.044 (231.0 Ft/Mile 43.7 m/Km)

0.087 (462.0 Ft/Mile 87.5 m/Km)
Polar RC3 GPS

Turn Around

92

0.943% (301.9 Ft/Mile 57.2 m/Km)

0.078 (411.1 Ft/Mile 77.9 m/Km)

0.156 (822.2 Ft/Mile 155.7 m/Km)
Garmin 310XT with Footpod 244

0.962% (200.2 Ft/Mile 37.9 m/Km)

0.040 (209.8 Ft/Mile 39.7 m/Km)

0.079 (419.7 Ft/Mile 79.5 m/Km)
Garmin 310XT no Footpod 64

0.965% (184.7 Ft/Mile 35.0 m/Km)

0.075 (395.2 Ft/Mile 74.9 m/Km)

0.150 (790.5 Ft/Mile 149.7 m/Km)
Garmin 910XT with Footpod 48

0.953% (249.8 Ft/Mile 47.3 m/Km)

0.025 (132.8 Ft/Mile 25.2 m/Km)

0.050 (265.7 Ft/Mile 50.3 m/Km)
All 448

0.957% (228.2 Ft/Mile 43.2 m/Km)

0.058 (304.1 Ft/Mile 57.6 m/Km)

0.115 (608.1 Ft/Mile 115.2 m/Km)
Polar RC3 GPS

Power Line

167

0.987% (66.4 Ft/Mile 12.6 m/Km)

0.036 (188.8 Ft/Mile 35.8 m/Km)

0.072 (377.5 Ft/Mile 71.5 m/Km)
Garmin 310XT with Footpod 457

0.994% (29.5 Ft/Mile 5.6 m/Km)

0.028 (149.5 Ft/Mile 28.3 m/Km)

0.057 (299.1 Ft/Mile 56.6 m/Km)
Garmin 310XT no Footpod 115

0.988% (60.9 Ft/Mile 11.5 m/Km)

0.039 (207.4 Ft/Mile 39.3 m/Km)

0.079 (414.7 Ft/Mile 78.5 m/Km)
Garmin 910XT with Footpod 90

0.984% (83.5 Ft/Mile 15.8 m/Km)

0.022 (113.8 Ft/Mile 21.6 m/Km)

0.043 (227.6 Ft/Mile 43.1 m/Km)
All 829

0.991% (47.2 Ft/Mile 8.9 m/Km)

0.031 (165.2 Ft/Mile 31.3 m/Km)

0.063 (330.5 Ft/Mile 62.6 m/Km)

4 Interpretation

What do these statistics mean? This is my interpretation:

  • Under normal conditions the GPS accuracy is quite good for all devices, though the 310XT/910XT with a Footpod have a slight advantage.
  • Not surprisingly, the accuracy drops going under the bridge. More interestingly the trueness just after the bridge is even lower, suggesting that the GPS watches are struggling to reacquire the satellites.
  • The turnarounds are even less accurate than going under a bridge, but Power Lines do not seem to impact accuracy noticeably.
  • The Footpod improves the accuracy of the 310XT and the 910XT, especially on the turn around and under the bridge.
  • Without the Footpod, the 310XT has similar problems to the RC3 on the turn around, but the RC3 does worse under the bridge.

5 Recommendations

This data leads me to a few conclusions.

  • GPS watches are accurate enough for most general running.
  • Adding a Footpod to the Garmin 310XT and the Garmin 910XT improves their accuracy.
  • It takes time for the GPS watches to acquire the satellites. The watches tended to say they are ready to go before they have an optimal lock. Therefore, to improve accuracy try to give them a little more time. Note that some newer GPS watches such as the Garmin 620 have the ability to be preloaded with the satellite positions, reducing this startup time and start up in accuracy dramatically.
  • The GPS watches are not accurate enough to perform any type of [Practical Interval Training| interval training]. Instead, use a track or measure out the distance using some other mechanism.

6 Even GPS Watches have Bad Days

While it's tempting to take the various GPS watches on a single run and simply compare the totals, this is a flawed approach. Evaluating the devices GPS accuracy on the basis of a single sample does not tell you much. It's a bit like evaluating an athlete's ability on the basis of one event; everyone has good days and bad days, and that applies to GPS watches as well. To illustrate this, the images below are from two runs, recorded on 9/20 and 9/22. In each run I recorded data on both the 310 and 910 watches, hitting the lap button on both at as close to the same time as is humanly possible. On 9/20 the 910XT was far more accurate than the 310XT, but on 9/22 the situation is reversed. If you were to have evaluated the two watches on the basis of a single run, you would conclude that one is much better than the other. But which device would win would depend on the particular day. This is why I've accumulated a lot of data to do a statistical analysis to work out which is really better.

The Garmin 310XT having a bad day. You can see on the upper half of the course where it got a little confused and off track.
The Garmin 910XT on the same run having no problems, and only the standard, expected level of inaccuracy.
Two days later and it's the turn of the Garmin 310XT to have a good day.
Again, this track is recorded on the same run as the image to the left. The Garmin 910XT gets a little confused at the start, and then again around lap 27.

7 Next Steps

This is an initial analysis of the data I have, and there are a number of further evaluations to do.

  • Gather data from some other GPS Running Watches.
    • I will evaluate the Garmin 620 when it becomes available as it has some promising functionality.
    • I am gathering data on an older Garmin 205. It's not a watch I'd recommend, but it will be interesting to see if the technology has improved over time.
    • I will soon start gathering data on an iPhone 4S to see how it compares with dedicated devices.
  • Add in some graphs of the distribution of accuracy, and possibly a Q-Q plot (which shows reasonably normal distribution).
  • Check how GPS accuracy changes over the course of a run, as I've seen a distinct tendency for the watches to say they are good to go when they don't really have an optimal lock on the satellites.
  • Look at how accurate the GPS watches are for measuring elevation, and compare with barometric data.
  • Check for any correlation between accuracy and running pace.
  • Look for any correlation between accuracy and the use of heart rate monitor. The radio signal from the heart rate monitor could interfere with accuracy.
  • Write up general GPS accuracy.
  • List the sources of potential error.
  • Evaluate the accuracy of the Footpod alone, both trueness and precision.