Difference between revisions of "GPS Accuracy"
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 | + | 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 | + | 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 | + | 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" | ||
− | ! | + | ! Device |
+ | ! Condition | ||
! Count | ! Count | ||
− | ! Trueness | + | ! Trueness (Average) |
! Precision (Standard Deviation) | ! Precision (Standard Deviation) | ||
− | ! 95% within | + | ! 95% within |
− | |||
|- | |- | ||
− | | Normal | + | | {{Polar RC3 GPS}} |
− | | | + | | rowspan="5"| |
− | | 0. | + | Normal |
− | | | + | | 897 |
− | + | | style="background-color: #9DCE7E;"| | |
− | | 1 | + | 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) | ||
|- | |- | ||
− | | | + | | {{Garmin 310XT}} with [[Footpod]] |
− | | | + | | 2453 |
− | | 1. | + | | style="background-color: #63BE7B;"| |
− | | | + | 1.000% (1.9 Ft/Mile 0.4 m/Km) |
− | + | | style="background-color: #C0D980;"| | |
− | | | + | 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 |
− | | | + | | style="background-color: #82C77C;"| |
− | + | 0.996% (18.8 Ft/Mile 3.6 m/Km) | |
− | | | + | | style="background-color: #FFDC81;"| |
− | | | + | 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]] |
− | | | + | | 481 |
− | | 4. | + | | style="background-color: #9ECF7E;"| |
− | | 3. | + | 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: | ||
− | * | + | * 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 | + | * 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 | + | * The turnarounds are even less accurate than going under a bridge, but Power Lines do not seem to impact accuracy noticeably. |
− | * The | + | * 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. |
=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. | ||
− | |||
* Gather data from some other [[Best Running Watch| GPS Running Watches]]. | * Gather data from some other [[Best Running Watch| GPS Running Watches]]. | ||
− | + | ** 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 | + | ** 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]). | ||
− | |||
* 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 | + | * 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. | ||
− | + | * Write up general GPS accuracy. | |
− | * Write up general GPS | ||
− | |||
* 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 15: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.
Contents
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.
2 Accuracy, Trueness and Precision
For this evaluation I'll use the definition of Accuracy as the combination of trueness and precision:
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.
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.