Changes

{{DISPLAYTITLE:GPS Accuracy of Garmin, Polar, and other Running Watches}}<div style="float:right;">__TOC__</div>I evaluated the real -world accuracy of GPS watches while running over 212,500 000 miles/419,000Km and recording over 1050,000 data points as part of my evaluation of the [[Best Running Watch]]es. Under good conditions most of the watches are all remarkably good, but when things get a little tough the differences become more apparent. The table below is a vastly simplified summary However, '''none of the results, rating the best device as a 10 then comparing the others. (Note watches have GPS accuracy that is good enough to be used for displaying your current pace''10' does not indicate perfect. As a result, just the best I've measured so far.){| class="wikitable"! Device! Trueness! Precision! Overall|-| {{Garmin 205}}| 10.0| 10.0| 10.0|-| {{Garmin 910XT}} with added the test results for various [[Footpod]]| 7s as they can be far more accurate than GPS, but more importantly they tend to have far less moment-to-moment variation so they can give a far better display of your current pace.4| 9(Note that my accuracy tests focus on the ability to measure distance, not the moment in time position, though the two are obviously related.8) | 9.0|-| {{Garmin 310XT}} with [[Footpod]]| 5File:GPS Accuracy.8png| 9.1none| 7.9thumb|-800px| iPhone 4s| 4An infographic of the accuracy of the GPS running watches.4| 9The top right corner represents the most accurate watches.6| 7(This graphic uses ISO 5725 terminology.2|-| {{Garmin 310XT}} no [[Footpod)]]| 4The table below is a simplified summary of the results, where a '10' would be a perfect device.9| 8(For an explanation of the ISO 5725 terms 'trueness', 'precision' and 'accuracy', see below.1| 6.8|-)| {{Polar RC3 :GPSAccuracy-summary}}| 5The values used are simply 10 minus the value for trueness (average) and precision (standard deviation from true). The overall is the combination of trueness and precision.7| 6Repeatability is how consistent a watch is in providing the same value for the same course segment.9| 6'''Important''': Manufacturers do not typically release the type of GPS chipset used, so the information in this table is based the best available data, but it should be treated with caution.5|}

''Main article: [[GPS Testing Methodology]]'' Simply taking a GPS watch on a single run does not provide sufficient data to reasonably evaluate its accuracy. So to To gather the data for this test I marked my usual running ran the same route at repeatedly, recording laps every 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, turn arounds and one bridge that I go goes under. The a 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]].]]=Accuracy, Trueness and Precision(plus Repeatability)=For this evaluation I'll use the ISO 5725 definition of [http://en.wikipedia.org/wiki/Accuracy_and_precision Accuracy as the combination of trueness and precision]:.

|[[File:High precision Low accuracy.svg|none|thumb|x300pxx200px|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.]]|[[File:High accuracy Low precision.svg|none|thumb|x300pxx200px|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. I use the traditional approach to standard deviation (variation from mean) as well as a modified approach that uses variation from the true value. (It is more common in many fields to use "accuracy" to mean closeness to true value and "validity" to mean the combination of accuracy and precision. However, I feel that the meanings used by ISO 5725 are closer to the common usage. If a company sold 'accurate' 12 inch pipes and shipped half of them as 6 inches and half as 18 inches, they would meet the traditional definition of accuracy, but few people would be happy with the product. ) In addition, I calculate a value for "repeatability", which is a measure of how likely a watch is to give the same distance measurement for a specific course. I calculate the standard deviation for each segment of the course, and then take the average. A high repeatability score can mask poor accuracy and can convince users they have a good device.

The table below shows summary data for each device. The count field is how many measurements I have for that combination of condition and device, with each measurement being a quarter mile distance. I generally aim for over 1,000 data points to even out the effects of weather, satellite position and other factors. The Trueness is the absolute of the mean, though nearly all watches tend to read short. The standard deviation is provided based on the variance from the mean and the variance from the known true value. The average pace error is shown to give a sense of how much error you're likely to see in the display of current pace. This is an average error not a worst case. The data shown below is a summary the accuracy based on all the sections. If you'd like more detailed information, I've divided split off the [[Detailed Statistics for GPS Running Watches]] for the laps into those results under different conditions. {{:GPS Accuracy-statistics}}The "Accuracy (Combined)" column has an indication of statistical significance compared with the most accurate entry. The key to this indication is: † p<0.05, * p< 0.01, ** p< 0.001, *** p< 0.0001, **** p< 0.00001, ***** p< 0.000001==Progress of newer watches==I expected GPS watches to improve with time, but the opposite appears to be happening. With the Garmin devices especially, you can see that go the older watches generally do far better than the newer ones. I suspect this is due to compromises to get better battery life and smaller packaging and the cost of GPS accuracy. ==Smartphone Accuracy==There are various things you will need to do in order to get the level of accuracy I found with Smartphones. See [[Running With A Smartphone#Optimizing GPS Accuracy| Optimizing Smartphone GPS Accuracy]] for details. ==Interpretation and Conclusions==What do these statistics mean? This is my interpretation:* Under normal conditions the GPS accuracy is quite good for most devices.* The accuracy of a calibrated [[Footpod]] is far better than any GPS device. Without calibration the Footpod is more accurate than any watch currently on the market with the exception of the 310XT/910XT with a Footpod backing up the GPS. * The [[Polar M400]], [[Garmin Fenix 2]], and [[Garmin 10]] are noticeably poorer than the other devices. I found the accuracy of the M400/Fenix2/10 in general usage to be rather grim, and I did some testing pairing them up with the 610 or the 310XT. In all cases the Fenix2/10 would have poor accuracy compared with the 610 or 310XT on the same run. * The Fenix2 would repeated loose satellite reception, something I've not seen (the M400 has done this once). The statistics do not reflect just how bad the Fenix2 is, as some of the data is too bad to analyze. * The results of the Garmin 610 & 620 indicate the problems with the 10 are not inherent in a smaller device. * The improvement in GPS accuracy of the 620 with updated firmware shows just how important the software can be. With the earlier firmware the 620 lost over a mile over a 20 mile run! * '''The accuracy of all devices is better in a straight line than on curves or twisty routes'''. My course is a tough test for GPS devices with many curves and only a few relatively straight sections. * Not surprisingly, for many devices accuracy drops going under the bridge. However, those some devices do great in this section, probably because it's fairly straight. * More interestingly the trueness just after the bridge is even lower, suggesting that the GPS watches are immediately after struggling to reacquire the satellites. * The turnarounds are even less accurate than going under a lap bridge, but Power Lines do not seem to impact accuracy noticeably. * The [[Footpod]] improves the accuracy of the 310XT. ** Note that goes under I'm intentionally using an uncalibrated Footpod (factor = 1.000) to gather data for a comparison of Foodpod and GPS. * The older Garmin 205 does remarkably well. =Footpod Accuracy=The accuracy of a Footpod is far higher than GPS, as well as more consistent and quicker to react to changes in pace. For any given run, the average pace error from the bridgeFootpod is only 7 seconds/mile (at a 9:00 min/mile pace) or 5 seconds/Km (at a 5:30 min/Km pace). In practical terms, those I've found that go next I always have to use a Footpod to pace a marathon or under for critical speedwork. For details of how the Footpod calibration was done, see [[GPS Testing Methodology]]. =Trail Running and GPS=Trail running tends to be rather harder for a watch to measure accurately. There are far more twists and turns, and for a [[Footpod]] your footsteps tend to be uneven. I realized how bad the problem was when running some mountain bike trails and my GPS watch said I'd only been traveling at walking pace. This prompted me to survey and evaluate the accuracy of various devices on these mountain bike trails. The table below is preliminary data, but you'll notice how the results are dramatically worse than my usual GPS testing. The Polar V800, which does really well on my greenway tests has serious problems on trails, though it's still one of the better watches I've tested so far. The Suunto Spartan Trainer shows its strength more clearly on the mountain bike trails, coming in far ahead of other GPS watches. The [[Stryd]] footpod is vastly more accurate than GPS, and unlike GPS it could be calibrated to improve its accuracy even further. {{:GPS Accuracy-TrailSummary}} =Which Chipset? =While the specific chipset used in a GPS watch will impact its accuracy, there are many other factors that come into play. The physical packaging of the chipset, the antenna used, the particular features that are implemented, and the software that interprets the raw data will influence the overall accuracy. It's important to note that the SiRF chipsets such as "SIRFstarIV" are not a single chipset, but rather an overall architecture with several specific chipsets bearing the same name. =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 power linesbasis of a single run, those 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. {| class="wikitable" |- valign="top"|[[File:310XT Bad.jpg|none|thumb|x500px| 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. ]]|[[File:910XT Good.jpg|none|thumb|x500px|The {{Garmin 910XT}} on the same run having no problems, and only the standard, expected level of inaccuracy.]]|- valign="top"|[[File:310XT Good.jpg|none|thumb|x500px|Two days later and it's the turn of the {{Garmin 310XT}} to have a good day.]]|[[File:910XT Bad.jpg|none|thumb|x500px|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.]]|}=Some Devices Are Better Than Others=Below is a section of two runs showing the same section of the course, both taken at the same time, one from the Garmin 310XT and the other from the Garmin 620 with the early firmware. (With the later firmware the tracks from the 620 look like the 310XT.) {| class="wikitable" |- valign="top"|[[File:ExampleGarmin310.jpg|none|thumb|x500px| You can see the GPS tracks (thin red line) are close together and then all the rest lap markers (normalyellow diamonds)are clustered nicely. The blue dots on the GPS tracks are the actual GPS recordings.]]|[[File:ExampleGarmin620. jpg|none|thumb|x500px|By contrast, the 620 has much wider GPS tracks and dispersed lap markers. ]]|}=GPS Short and long measurements=As you can see from the images below, the GPS track tends to take shortcuts around bends, reducing the length of the measured track. This cutting of the corners indicates the devices are doing some post-hoc smoothing to try to overcome the GPS errors. The more smoothing they do, the better the accuracy is likely to be in a straight line and the worse it is around corners or twisty courses. In my discussions with engineers working on GPS systems, this type of smoothing is often performed with a[http://en.wikipedia.org/wiki/Kalman_filter Kalman filter]. (When I've tested using software without smoothing I found the measurements were long on my course rather than short, which is almost always the case.)[[File:GPS Shortcuts.jpg|none|thumb|500px|The GPS tracks in red showing the tendency to cut the corners on the curves.]]Often GPS measurements of races, especially marathons record a longer distance than the race. This is partly because the USATF technique for measuring the distance takes a path that is no more than 12 inches away from the tangent (corner), and few runners are able to run that close. In a large marathon you can be forced to take a line that is a long way from the tangent. The other factor is that on a straight line, the GPS error tends to give a slightly longer measurement. {| class="wikitable" |- valign="top"[[File:GPS Marathon.jpg|none|thumb|500px|Here you can see the GPS line is not following the straight road, giving a longer reading on the Thunder Road Marathon. Notice that the GPS is also included a cutting the corner at the top (we didn'mixedt run through the building).]]|[[File:GPS MarketSt.jpg|none|thumb|x300px|Here' category s another example of running down Market Street in San Francisco, where you can see the errors that reflects all would add to the sectionsdistance. ]]|}=GPS Accuracy and Weather=GPS Accuracy is slightly better with clear skies than with cloud cover. The difference between completely clear and fully overcast is generally less than 0.1% and my testing includes a similar mix of cloud cover for each watch, so I ignore this difference. However, rain can degrade accuracy by 0.3-3.1%, with the better watches being impacted the least. Because it does not rain that frequently where I test, this has created some potential bias in my testing so I now ignore measurements taken during the rain. This has only made a slight difference to the results, but it ensures consistence. =GPS Accuracy and Seasons=I run in a wooded area with mostly deciduous trees, so the foliage varies by Condition season. This foliage can have a noticeable impact on GPS accuracy, with better accuracy during the bare winter months than the rest of the year. This difference is mostly 0.1-1.5%, but in some cases can be as large as 2.5%. Because of this, my testing now ignores data from the winter months when the trees are bare. The short winter here in the south of the US means that the impact on the overall results are small, but like the weather impacts noted above, this does ensure greater consistency. =GPS Accuracy and Pace=[[File:AccuracyAndPace.jpg|none|thumb|500px| A plot of GPS precision against pace. The red line is the correlation.]]There have been reports of GPS accuracy changing with pace, but as you can see from the graph above, my testing does not show this. =GPS and GLONASS=I have found that GPS plus GLONASS produces less accuracy than GPS alone, something that is a little counterintuitive. I have no definitive explanation for this, and I do have a working hypothesis. My thought is that enabling both GPS and GLONASS will increase the number of satellites above the horizon, and a modern chipset can have over 50 channels. This means the chipset will have access to far more satellites with both systems enabled. However, I don't believe that the chipset will use all the available satellites when calculating its position. In an urban, or wooded environment, the satellites nearest the horizon will have the weakest signal, and the satellites closest to directly overhead will have the strongest signal. If the chipset were to use only the strongest 5-6 signals, then it's likely to choose the satellites that are closest to being directly overhead. That means the satellites chosen are relatively close together, which is a poor geometry that reduces accuracy. (In GPS terms this is called Dilution of Precision, or DoP.) I've talked to a GPS specialist who tells me that they have seen this in GPS systems they've tested (though not necessarily consumer grade systems.) What this means in the real world is that if you're in an environment with a partial view of the sky due to tree cover for low buildings then GPS on its own is likely to provide better accuracy. If you're in an environment with a clear view of the sky from horizon to horizon, then Deviceit's less clear to me which system is likely to provide better accuracy, and I've not tested this in practice. Given that the theoretical accuracy of GLONASS is not quite as good as GPS I'm not sure that enabling both systems will improve matters. It's possible that GLONASS will do relatively better at extreme polar latitudes due to its different orbital patterns.==Garmin 920XT and GLONASS==The [[Garmin 920XT]] is significantly worse with GLONASS enabled.

! Condition! Device! CountAccuracy! Trueness (Average Distance Error)! 95% withinPrecision! Standard DeviationRepeatability

| rowspanGarmin 920XT|style="7background-color: #FAE983;"|Normal6.6| {{Garmin 205}}style="background-color: #D2DE81;"| 7797.5| style="background-color: #9DCF7EFED680;"|0.014% (725.9 Ft/Mile 13.8 m/Km)| 0.063 (331.2 Ft/Mile 62.7 m/Km)| style="background-color: #C6DA80D1DD81;"|0.031 (165.6 Ft/Mile 317.4 m/Km)5

| iPhone 4s| 668| style="background-color: #FFDE82;"|0.030% (160.8 Ft/Mile 30.5 m/Km)| 0.070 (372.0 Ft/Mile 70.5 m/Km)| style="background-color: #ECE582;"|0.035 (186.0 Ft/Mile 35.2 m/Km)|-| {{Polar RC3 GPS}}| 983| style="background-color: #A8D27F;"|0.015% (79.8 Ft/Mile 15.1 m/Km)| 0.082 (434.7 Ft/Mile 82.3 m/Km)| style="background-color: #FFE082;"|0.041 (217.4 Ft/Mile 41.2 m/Km)|-| {{Garmin 310XT}} with [[Footpod]]| 2787| style="background-color: #D0DD81;"|0.020% 920XT (105.5 Ft/Mile 20.0 m/Km)| 0.073 (384.7 Ft/Mile 72.9 m/KmGLONASS)| style="background-color: #F8E983FEC77D;"|0.036 (192.3 Ft/Mile 36.4 m/Km)|-| {{Garmin 310XT}} no [[Footpod]]| 1210| style="background-color: #FEEA83;"|0.025% (134.6 Ft/Mile 25.5 m/Km)| 0.083 (439.4 Ft/Mile 83.2 m/Km)| style="background-color: #FFDF82;"|0.042 (219.7 Ft/Mile 41.6 m/Km)|-| {{Garmin 910XT}} with [[Footpod]]| 514| style="background-color: #A1D07E;"|0.014% (75.4 Ft/Mile 14.3 m/Km)| 0.059 (311.5 Ft/Mile 59.0 m/Km)| style="background-color: #B3D57F;"|0.030 (155.8 Ft/Mile 29.5 m/Km)|-| All| 6941| style="background-color: #D2DE81;"|0.020% (106.4 Ft/Mile 20.1 m/Km)| 0.075 (394.4 Ft/Mile 74.7 m/Km)| style="background-color: #FFEB84;"|0.037 (197.2 Ft/Mile 37.3 m/Km)|-| rowspan="7"|Under Bridge| {{Garmin 205}}| 66| style="background-color: #9DCE7E;"|-0.014% (72.8 Ft/Mile 13.8 m/Km)| 0.148 (780.4 Ft/Mile 147.8 m/Km)| style="background-color: #FA8671;"|0.074 (390.2 Ft/Mile 73.9 m/Km)|-| iPhone 4s| 59| style="background-color: #9FCF7E;"|0.014% (74.0 Ft/Mile 14.0 m/Km)| 0.067 (356.1 Ft/Mile 67.4 m/Km)| style="background-color: #DDE182;"|0.034 (178.0 Ft/Mile 33.7 m/Km)|-| {{Polar RC3 GPS}}| 86| style="background-color: #FB9975;"|0.056% (296.3 Ft/Mile 56.1 m/Km)| 0.156 (825.3 Ft/Mile 156.3 m/Km)| style="background-color: #F97A6F;"|0.078 (412.7 Ft/Mile 78.2 m/Km)|-| {{Garmin 310XT}} with [[Footpod]]| 222| style="background-color: #FFDA81;"|0.032% (168.6 Ft/Mile 31.9 m/Km)| 0.098 (520.0 Ft/Mile 98.5 m/Km)| style="background-color: #FECA7E;"|0.049 (260.0 Ft/Mile 49.2 m/Km)|-| {{Garmin 310XT}} no [[Footpod]]| 99| style="background-color: #63BE7B;"|0.007% (35.3 Ft/Mile 6.7 m/Km)| 0.084 (446.0 Ft/Mile 84.5 m/Km)| style="background-color: #FFDD82;"|0.042 (223.0 Ft/Mile 42.2 m/Km)|-| {{Garmin 910XT}} with [[Footpod]]| 43| style="background-color: #B2D47F;"|0.016% (86.1 Ft/Mile 16.3 m/Km)| 0.168 (889.0 Ft/Mile 168.4 m/Km)| style="background-color: #F8696B;"|0.084 (444.5 Ft/Mile 84.2 m/Km)|-| All| 575| style="background-color: #E9E482;"|0.023% (121.2 Ft/Mile 22.9 m/Km)| 0.124 (654.2 Ft/Mile 123.9 m/Km)| style="background-color: #FCA777;"|0.062 (327.1 Ft/Mile 62.0 m/Km)|-| rowspan="7"|Post Bridge| {{Garmin 205}}| 66| style="background-color: #DEE182;"|0.022% (113.9 Ft/Mile 21.6 m/Km)| 0.048 (250.9 Ft/Mile 47.5 m/Km)| style="background-color: #7AC47C;"|0.024 (125.5 Ft/Mile 23.8 m/Km)|-| iPhone 4s| 54| style="background-color: #FDB97B;"|0.044% (233.5 Ft/Mile 44.2 m/Km)| 0.060 (314.9 Ft/Mile 59.6 m/Km)| style="background-color: #B6D67F;"|0.030 (157.4 Ft/Mile 29.8 m/Km)|-| {{Polar RC3 GPS}}| 84| style="background-color: #F8696B;"|0.074% (390.7 Ft/Mile 74.0 m/Km)| 0.100 (526.4 Ft/Mile 99.7 m/Km)| style="background-color: #FEC87E;"|0.050 (263.2 Ft/Mile 49.8 m/Km)|-| {{Garmin 310XT}} with [[Footpod]]| 188| style="background-color: #FDC27D;"|0.041% (216.2 Ft/Mile 41.0 m/Km)| 0.075 (394.8 Ft/Mile 74.8 m/Km)| style="background-color: #FFEB84;"|0.037 (197.4 Ft/Mile 37.4 m/Km)|-| {{Garmin 310XT}} no [[Footpod]]| 95| style="background-color: #FCA877;"|0.051% (268.6 Ft/Mile 50.9 m/Km)| 0.074 (388.5 Ft/Mile 73.6 m/Km)| style="background-color: #FCEA83;"|0.037 (194.3 Ft/Mile 36.8 m/Km)|-| {{Garmin 910XT}} with [[Footpod]]| 40| style="background-color: #FDBC7B;"|0.043% (229.1 Ft/Mile 43.4 m/Km)| 0.043 (226.4 Ft/Mile 42.9 m/Km)| style="background-color: #63BE7B;"|0.021 (113.2 Ft/Mile 21.4 m/Km)|-| All| 527| style="background-color: #FDB47A;"|0.046% (243.4 Ft/Mile 46.1 m/Km)| 0.079 (415.6 Ft/Mile 78.7 m/Km)| style="background-color: #FFE583;"|0.039 (207.8 Ft/Mile 39.4 m/Km)|-| rowspan="7"|Turn Around| {{Garmin 205}}| 72| style="background-color: #FECE7F;"|0.036% (192.5 Ft/Mile 36.5 m/Km)| 0.052 (273.9 Ft/Mile 51.9 m/Km)| style="background-color: #8FCA7D;"|0.026 (136.9 Ft/Mile 25.9 m/Km)|-| iPhone 4s| 62| style="background-color: #FA7E70;"|0.066% (349.7 Ft/Mile 66.2 m/Km)| 0.089 (471.3 Ft/Mile 89.3 m/Km)| style="background-color: #FED780FAE983;"|0.045 (235.6 Ft/Mile 44.6 m/Km)|-| {{Polar RC3 GPS}}| 92| style="background-color: #FA8270;"|0.065% (341.7 Ft/Mile 64.7 m/Km)| 0.154 (814.6 Ft/Mile 154.3 m/Km)| style="background-color: #FA7D6F;"|0.077 (407.3 Ft/Mile 77.1 m/Km)|-| {{Garmin 310XT}} with [[Footpod]]| 205| style="background-color: #FB9B75;"|0.056% (294.2 Ft/Mile 55.7 m/Km)| 0.083 (439.2 Ft/Mile 83.2 m/Km)| style="background-color: #FFDF82;"|0.042 (219.6 Ft/Mile 41.6 m/Km)|-| {{Garmin 310XT}} no [[Footpod]]| 107| style="background-color: #FB9273;"|0.059% (311.8 Ft/Mile 59.1 m/Km)| 0.115 (605.8 Ft/Mile 114.7 m/Km)| style="background-color: #FCB47A;"|0.057 (302.9 Ft/Mile 57.4 m/Km)|-| {{Garmin 910XT}} with [[Footpod]]| 43| style="background-color: #FCA777;"|0.051% (270.2 Ft/Mile 51.2 m/Km)| 0.051 (270.7 Ft/Mile 51.3 m/Km)| style="background-color: #8CCA7D;"|0.026 (135.3 Ft/Mile 25.6 m/Km)|-| All| 581| style="background-color: #FB9975;"|0.056% (296.5 Ft/Mile 56.2 m/Km)| 0.102 (536.1 Ft/Mile 101.5 m/Km)| style="background-color: #FDC67D;"|0.051 (268.0 Ft/Mile 50.8 m/Km)|-| rowspan="7"|Power Line| {{Garmin 205}}| 127| style="background-color: #9FCF7E;"|0.014% (73.7 Ft/Mile 14.0 m/Km)| 0.046 (245.1 Ft/Mile 46.4 m/Km)| style="background-color: #74C37C;"|0.023 (122.5 Ft/Mile 23.2 m/Km)|-| iPhone 4s| 110| style="background-color: #FFEB84;"|0.026% (135.2 Ft/Mile 25.6 m/Km)| 0.058 (305.3 Ft/Mile 57.8 m/Km)| style="background-color: #ADD37FE1E282;"|0.029 (152.7 Ft/Mile 28.9 m/Km)|-| {{Polar RC3 GPS}}| 167| style="background-color: #D3DE81;"|0.020% (107.2 Ft/Mile 20.3 m/Km)| 0.072 (377.7 Ft/Mile 71.5 m/Km)| style="background-color: #F1E783;"|0.036 (188.8 Ft/Mile 35.8 m/Km)|-| {{Garmin 310XT}} with [[Footpod]]| 515| style="background-color: #FFEB84;"|0.026% (135.5 Ft/Mile 25.7 m/Km)| 0.069 (366.5 Ft/Mile 69.4 m/Km)| style="background-color: #E7E482;"|0.035 (183.2 Ft/Mile 34.7 m/Km)|-| {{Garmin 310XT}} no [[Footpod]]| 203| style="background-color: #FED580;"|0.034% (179.0 Ft/Mile 33.9 m/Km)| 0.072 (377.9 Ft/Mile 71.6 m/Km)| style="background-color: #F2E783;"|0.036 (188.9 Ft/Mile 35.8 m/Km)|-| {{Garmin 910XT}} with [[Footpod]]| 90| style="background-color: #D9E081;"|0.021% (110.9 Ft/Mile 21.0 m/Km)| 0.048 (254.4 Ft/Mile 48.2 m/Km)| style="background-color: #7DC57C;"|0.024 (127.2 Ft/Mile 24.1 m/Km)|-| All| 1212| style="background-color: #F8E983;"|0.025% (130.5 Ft/Mile 24.7 m/Km)| 0.067 (351.5 Ft/Mile 66.6 m/Km)| style="background-color: #D9E081;"|0.033 (175.8 Ft/Mile 33.3 m/Km)|-| rowspan="7"|Mixed| {{Garmin 205}}| 1110| style="background-color: #A0CF7E;"|0.014% (74.5 Ft/Mile 14.1 m/Km)| 0.070 (371.2 Ft/Mile 70.3 m/Km)| style="background-color: #EBE582;"|0.035 (185.6 Ft/Mile 35.2 m/Km)|-| iPhone 4s| 953| style="background-color: #FFDA81;"|0.032% (168.9 Ft/Mile 32.0 m/Km)| 0.073 (384.8 Ft/Mile 72.9 m/Km)| style="background-color: #F8E983;"|0.036 (192.4 Ft/Mile 36.4 m/Km)|-| {{Polar RC3 GPS}}| 1412| style="background-color: #FAE983;"|0.025% (131.8 Ft/Mile 25.0 m/Km)| 0.102 (539.9 Ft/Mile 102.3 m/Km)| style="background-color: #FDC57D;"|0.051 (269.9 Ft/Mile 51.1 m/Km)|-| {{Garmin 310XT}} with [[Footpod]]| 3917| style="background-color: #F4E783;"|0.024% (128.2 Ft/Mile 24.3 m/Km)| 0.077 (406.2 Ft/Mile 76.9 m/Km)| style="background-color: #FFE884;"|0.038 (203.1 Ft/Mile 38.5 m/Km)|-| {{Garmin 310XT}} no [[Footpod]]| 1714| style="background-color: #FFE283;"|0.029% (152.6 Ft/Mile 28.9 m/Km)| 0.087 (457.9 Ft/Mile 86.7 m/Km)| style="background-color: #FFDA81;"|0.043 (229.0 Ft/Mile 43.4 m/Km)|-| {{Garmin 910XT}} with [[Footpod]]| 730| style="background-color: #C8DB80;"|0.019% (100.3 Ft/Mile 19.0 m/Km)| 0.071 (377.2 Ft/Mile 71.4 m/Km)| style="background-color: #F1E783;"|0.036 (188.6 Ft/Mile 35.7 m/Km)|-| All| 9836| style="background-color: #F5E883;"|0.024% (128.8 Ft/Mile 24.4 m/Km)| 0.082 (432.6 Ft/Mile 81.9 m/Km)| style="background-color: #FFE182;"|0.041 (216.3 Ft/Mile 41.0 m/Km)

==Accuracy by Device then ConditionSuunto Spartan Ultra and GLONASS==The [[Suunto Spartan Ultra]] seems to do particularly poorly with GLONASS enabled.

! Device! Condition! Count! 95% withinAccuracy! Trueness (Average Distance Error)! 95% withinPrecision! Standard DeviationRepeatability

| rowspanSuunto Spartan Ultra 1.6.14|style="6background-color: #E2E282;"|{{Garmin 205}}7.1| Normalstyle="background-color: #79C47C;"| 779| 09.063 (331.2 Ft/Mile 62.7 m/Km)5| style="background-color: #9DCE7EFED881;"|0.014% (72.9 Ft/Mile 136.8 m/Km)| 0.063 (331.2 Ft/Mile 62.7 m/Km)| style="background-color: #CADB80D8DF81;"|0.031 (165.6 Ft/Mile 317.4 m/Km)

| Under BridgeSuunto Spartan Ultra 1.6.14.GLONASS| 66style="background-color: #FCB179;"| 0.148 (780.4 Ft/Mile 147.8 m/Km)9| style="background-color: #9DCE7ED4DE81;"|7.5|style="background-0.014% (72.8 Ft/Mile 13.8 m/Km)color: #F9756E;"| 0.148 (780.4 Ft/Mile 1473.8 m/Km)3| style="background-color: #FA8571FDB57A;"|5.0|}==Garmin Epix and GLONASS==0The [[Garmin Epix]] has slightly better accuracy with WAAS than without it, and GLONASS didn't degrade the accuracy the way it does with other devices.074 My belief is that enabling WAAS effectively disables GLONASS, as WAAS is GPS specific (390and only available in North America.2 Ft) There is EGNOS Ground Segment is the equivalent of WAAS for GLONASS/GPS/Mile 73Galileo in Europe.9 m/Km){| class="wikitable" |- valign="top"!Device!Accuracy!Trueness!Precision!Repeatability

| Post BridgeGarmin Epix with GLONASS+WAAS| 66style="background-color: #FFE082;"| 06.048 (250.9 Ft/Mile 47.5 m/Km)2| style="background-color: #DDE182D6DF81;"|0.022% (113.9 Ft/Mile 217.6 m/Km)4| 0style="background-color: #FDBE7C;"|5.048 (250.9 Ft/Mile 47.5 m/Km)3| style="background-color: #7BC47CD6DF81;"|0.024 (125.5 Ft/Mile 237.8 m/Km)4

| Turn AroundGarmin Epix with WAAS| 72style="background-color: #FFDF82;"| 06.052 (273.9 Ft/Mile 51.9 m/Km)2| style="background-color: #FECE7FC8DB80;"|07.036% (192.5 Ft/Mile 36.5 m/Km)7| 0.052 (273.9 Ft/Mile 51style="background-color: #FDB77A;"|5.9 m/Km)1| style="background-color: #91CB7DF7E883;"|0.026 (136.9 Ft/Mile 256.9 m/Km)7

| Power LineGarmin Epix| 127style="background-color: #FDC37D;"| 0.046 (245.1 Ft/Mile 465.4 m/Km)| style="background-color: #9ECF7EF3E783;"|0.014% (73.7 Ft/Mile 146.0 m/Km)8| 0.046 (245.1 Ft/Mile 46style="background-color: #FB9C75;"|4.4 m/Km)| style="background-color: #75C37CF2E783;"|6.80|}==Garmin Fenix 5X and GLONASS==Continuing the theme of poor accuracy with GLONASS enabled, the [[Garmin Fenix 5X]] demonstrates even worse performance than its peers.023 (122The values shown below are rather dramatically worse with GLONASS enabled than without.5 Ft/Mile 23My anecdotal observation is that sometimes the Fenix 5X does a little worse with GLONASS than normal, possibly in line with other Garmin devices, and sometimes it seems to just get lost and produce dramatically worse results.2 m/Km){| class="wikitable sortable"!Device!Accuracy!Trueness!Precision!Repeatability

| MixedFenix 5X 4.30| 1110style="background-color: #FEC97E;"| 05.070 (371.2 Ft/Mile 70.3 m/Km)6| style="background-color: #A0CF7EEDE683;"|0.014% (74.5 Ft/Mile 146.1 m/Km)9| 0style="background-color: #FCA377;"|4.070 (371.2 Ft/Mile 70.3 m/Km)5| style="background-color: #F1E783F3E783;"|0.035 (185.6 Ft/Mile 35.2 m/Km)8

| rowspanFenix 5X 4.30 GLONASS|style="6background-color: #F97B6F;"|3.5iPhone 4s|style="background-color: #FFE082;"|6.2| Normalstyle="background-color: #F8696B;"|1.6| 668style="background-color: #F97B6F;"|3.5| 0}Below you can see a visual representation of the problems. Many of the tracks are a little worse than normal, but you generally follow the path. A small subset of the tracks are dramatically worse, either showing and offset from the actual path, or sometimes it looks like the sampling frequency has dropped, suggesting that the watch is only periodically able to get a location fix. This latter phenomenon is rather surprising to me and goes against my hypothesis of why GLONASS has worse accuracy.070 (372I would expect there would be more satellites available with GLONASS enabled, which would result in the watch selecting the subset with the strongest signal that are more likely to have a narrow angle of separation, which would result in increased Dilution of the Precision.0 Ft/Mile 70These tracks suggest that the Fenix 5X is unable to get any location fix for brief periods.5 m/Km){| class="wikitable" style="backgroundmargin-left: auto; margin-colorright: auto; border: #FFDF82none;"|- valign="top"0|[[File:BridgeFenix 5X 4.30 GLONASS.jpg|center|thumb|x300px| The GPS tracks from the Fenix 5X with GLONASS enabled. This diagram has tracks color coded with green indicating good accuracy through to red indicating poor accuracy, and the lap markers as blue dots.030% (160]]|- valign="top"|[[File:BridgeFenix 5X 4.8 Ft/Mile 30.5 m/Km)jpg|none|thumb|x300px|Here's the tracks from testing with GLONASS disabled for comparison.]]|}=GPS Accuracy and Sampling Rate=GPS watches default to recording a sample frequently enough that accuracy is not compromised. However, several devices offer the option of recording less frequently to improve battery life at the cost of accuracy. These devices actually turn off the GPS receiver, turning it on periodically for just long enough to get a fix. The images below are from the [[2014 Badwater 135]] using the [[Suunto Ambit2| 0Suunto Ambit2 R]] with recording set to one minute intervals.070 (372As you can see, accuracy suffers on curves, but is fine on the straights.0 Ft/Mile 70For a course like Badwater, the one minute recording interval was fine as the course has few turns.5 m/Km){| styleclass="backgroundwikitable" |-colorvalign="top"|[[File:GPS Sampling Curve.jpg|none|thumb|x300px|On a curve, the infrequent samples tend to 'cut the corners' and are quite inaccurate.]]|[[File: #F2E783;"GPS Sampling Straight.jpg|none|thumb|x300px|On the straight sections, the one minute sampling does not lose any accuracy.]]0|[[File:GPS Sampling Comparison.jpg|none|thumb|x300px|Here's a comparison of 1 minute sampling (red) with 1 second sampling (blue). On my GPS testing course the 1 minute sampling lost nearly 2 miles over a 16 mile run.035 ]]|}=GPS Accuracy and Recording Rate (186Smart/1-Second)=While the GPS sampling rate mentioned above has a huge impact on GPS accuracy, the same isn't true for recording rate. These two ideas seem to get confused.GPS sampling rate allows a watch to turn off the GPS receiver for short periods to conserve battery life while sacrificing GPS accuracy. Some Garmin watches can be configured to either record every second, or only record when something happens, such a change in heart rate or change in direction, something they call "smart recording." With a smart recording in normal GPS mode, the GPS system is continually active, so there's no loss in accuracy. To verify this, I tested the [[Garmin Fenix 5X]] in both the smart recording mode I normally use, and one second recording mode for comparison. As you can see, the two modes are virtually identical, and the differences are most likely due to chance (p=0 Ft/Mile 35.2 m/Km72). {| class="wikitable sortable"!Device!Accuracy!Trueness!Precision!Repeatability

| Under BridgeFenix 5X 4.30 Smart Recording| 59style="background-color: #FEC97E;"| 05.067 (356.1 Ft/Mile 67.4 m/Km)6| style="background-color: #9FCF7EEDE683;"|0.014% (746.0 Ft/Mile 14.0 m/Km)9| 0style="background-color: #FCA377;"|4.067 (356.1 Ft/Mile 67.4 m/Km)5| style="background-color: #E2E282F3E783;"|0.034 (178.0 Ft/Mile 336.7 m/Km)8

| Post Bridge| 54| 0.060 (314.9 Ft/Mile 59Fenix 5X 4.6 m/Km)30 One Second Recording| style="background-color: #FDBA7BFDBF7C;"|0.044% (233.5 Ft/Mile 44.2 m/Km)| 0.060 (314.9 Ft/Mile 59.6 m/Km)| style="background-color: #BAD780;"|0.030 (157.4 Ft/Mile 29.8 m/Km)|-| Turn Around| 62| 0.089 (471.3 Ft/Mile 89.3 m/Km)| style="background-color: #FA7E70;"|0.066% (349.7 Ft/Mile 66.2 m/Km)| 0.089 (471.3 Ft/Mile 89.3 m/Km)| style="background-color: #FED580;"|0.045 (235.6 Ft/Mile 44.6 m/Km)|-| Power Line| 110| 0.058 (305.3 Ft/Mile 57.8 m/Km)| style="background-color: #FEEA83;"|0.026% (135.2 Ft/Mile 25.6 m/Km)| 0.058 (305.3 Ft/Mile 57.8 m/Km)| style="background-color: #B0D47F;"|0.029 (152.7 Ft/Mile 28.9 m/Km)|-| Mixed| 953| 0.073 (384.8 Ft/Mile 72.9 m/Km)| style="background-color: #FFDA81;"|0.032% (168.9 Ft/Mile 32.0 m/Km)| 0.073 (384.8 Ft/Mile 72.9 m/Km)| style="background-color: #FFEB84;"|0.036 (192.4 Ft/Mile 36.4 m/Km)|-| rowspan="6"|{{Polar RC3 GPS}}| Normal| 983| 0.082 (434.7 Ft/Mile 82.3 m/Km)| style="background-color: #A8D27FE5E382;"|0.015% (79.8 Ft/Mile 15.1 m/Km)| 0.082 (434.7 Ft/Mile 82.3 m/Km)| style="background-color: #FFDF82;"|0.041 (217.4 Ft/Mile 41.2 m/Km)|-| Under Bridge| 86| 0.156 (825.3 Ft/Mile 156.3 m/Km)| style="background-color: #FB9A75;"|0.056% (296.3 Ft/Mile 56.1 m/Km)| 0.156 (825.3 Ft/Mile 156.3 m/Km)| style="background-color: #F97A6FFB9073;"|0.078 (412.7 Ft/Mile 78.2 m/Km)|-| Post Bridge| 84| 0.100 (526.4 Ft/Mile 99.7 m/Km)| style="background-color: #F8696B;"|0.074% (390.7 Ft/Mile 74.0 m/Km)| 0.100 (526.4 Ft/Mile 99.7 m/Km)| style="background-color: #FEC77DFBE983;"|0.050 (263.2 Ft/Mile 49.8 m/Km)|-| Turn Around| 92| 0.154 (814.6 Ft/Mile 154.3 m/Km)| style="background-color: #FA8270;"|0.065% (341.7 Ft/Mile 64.7 m/Km)| 0.154 (814.6 Ft/Mile 154.3 m/Km)| style="background-color: #FA7D6F;"|0.077 (407.3 Ft/Mile 77.1 m/Km)}|-| Power Line| 167| 0.072 (377.7 Ft/Mile 71.5 m/Km)| style="background-color: #D3DE81;"|0.020% (107.2 Ft/Mile 20.3 m/Km)| 0.072 (377.7 Ft/Mile 71.5 m/Km)| styleDevice Specific Notes="background-color: #F8E883;"|0.036 (188For those interested in some of the details of how devices are configured for testing, here are some additional notes.8 Ft/Mile 35.8 m/Km)|-| Mixed| 1412| 0* Garmin devices are set to 'smart recording'.102 (539.9 Ft/Mile 102.3 m/Km)| style="backgroundI did try an informal test with the 620 using 1-color: #F9E983;"|0.025% (131.8 Ft/Mile 25.0 m/Km)| 0.102 (539.9 Ft/Mile 102.3 m/Km)| style="background-color: #FDC47D;"|0.051 (269second recording, but it appeared to make no difference.9 Ft/Mile 51.1 m/Km)|-| rowspan="6"|{{Garmin 310XT}} with * For details of the calibration of the [[Footpod]]| Normal| 2787| 0.073 (384.7 Ft/Mile 72.9 m/Km)| style="background-color: #D0DD81;"|0.020% (105see [[GPS Testing Methodology]].5 Ft/Mile 20.0 m/Km)| 0.073 (384.7 Ft/Mile 72.9 m/Km)| style="background-color: #FEEA83;"|0.036 (192.3 Ft/Mile 36.4 m/Km)|-| Under Bridge| 222| 0.098 (520.0 Ft/Mile 98.5 m/Km)| style="background-color: #FFDB81;"|0.032% (168.6 Ft/Mile 31.9 m/Km)| 0.098 (520.0 Ft/Mile 98.5 m/Km)| style="background-color: #FEC97E;"|0.049 (260.0 Ft/Mile 49.* The Fenix 2 m/Km)|-| Post Bridge| 188| 0.075 (394.8 Ft/Mile 74.8 m/Km)| style="background-color: #FDC27D;"|0.041% (216.2 Ft/Mile 41.0 m/Km)| 0.075 (394.8 Ft/Mile 74.8 m/Km)| style="background-color: #FFE984;"|0.037 (197.4 Ft/Mile 37.4 m/Km)|-| Turn Around| 205| 0.083 (439.2 Ft/Mile 83.2 m/Km)| style="background-color: #FB9B75;"|0.056% (294.2 Ft/Mile 55.7 m/Km)| 0.083 (439.2 Ft/Mile 83.2 m/Km)| style="background-color: #FFDD82;"|0.042 (219.6 Ft/Mile 41.6 m/Km)|-| Power Line| 515| 0.069 (366.5 Ft/Mile 69.4 m/Km)| style="background-color: #FFEB84;"|0.026% (135.5 Ft/Mile 25.7 m/Km)| 0.069 (366.5 Ft/Mile 69.4 m/Km)| style="background-color: #EDE582;"|0.035 (183.2 Ft/Mile 34.7 m/Km)|-| Mixed| 3917| 0.077 (406.2 Ft/Mile 76.9 m/Km)| style="background-color: #F3E783;"|0.024% (128.2 Ft/Mile 24.3 m/Km)| 0.077 (406.2 Ft/Mile 76.9 m/Km)| style="background-color: #FFE683was tested with and without WAAS support activated;"|0WAAS helped slightly.038 (203.1 Ft/Mile 38.5 m/Km)|-| rowspan="6"|{{Garmin 310XT}} no * The [[FootpodGarmin 920XT]]| Normal| 1210| 0.083 (439.4 Ft/Mile 83.was tested with Watch Firmware 2 m/Km)| style="background-color: #FDEA83;"|0.025% (134.6 Ft/Mile 25.5 m/Km)| 0.083 (439.4 Ft/Mile 83.50, GPS Firmware 2 m/Km)| style="background-color: #FFDD82;"|0.042 (219.7 Ft/Mile 41.6 m/Km)|-| Under Bridge| 99| 0.084 (44670 using smart recording.0 Ft/Mile 84.5 m/Km)| style="background-color: #63BE7B;"|0.007% (35.3 Ft/Mile 6.7 m/Km)| 0.084 (446.0 Ft/Mile 84.5 m/Km)| styleGarmin 620 Issues="background-color: #FFDC81;"|0The Garmin 620 had some notorious problems with its GPS accuracy.042 (223.0 Ft/Mile 42.2 m/Km)|-| Post Bridge| 95| 0.074 (388.5 Ft/Mile 73.6 m/Km)| style="background-color: #FCA877;"|0.051% (268.6 Ft/Mile 50.9 m/Km)| 0.074 (388.5 Ft/Mile 73.6 m/Km)| style="backgroundThe table below shows the changes with various firmware versions, culminating in the GPS-color: #FFEB84;"|0.037 (194.3 Ft/Mile 36.8 m/Km)|-| Turn Around| 107| 030 firmware that resolved the issues.115 I've including some testing I did without EPO data (605.8 Ft/Mile 114.7 m/KmNoEPO row below)| style="background-color: #FB9273;"|0.059% and with a Footpod (311.8 Ft/Mile 59.1 m/Km+FP row below)| 0.115 (605.8 Ft/Mile 114.7 m/Km)| style="background-color{{: #FCB37A;"|0.057 (302.9 Ft/Mile 57.4 m/Km)|GPS Accuracy-g620}}{| Power Line| 203| 0.072 (377.9 Ft/Mile 71.6 m/Km)| style="background-color: #FED580;"|0.034% (179.0 Ft/Mile 33.9 m/Km)| 0.072 (377.9 Ft/Mile 71.6 m/Km)| styleclass="background-color: #F8E983;wikitable"|0.036 (188.9 Ft/Mile 35.8 m/Km)|-| Mixed| 1714| 0.087 (457.9 Ft/Mile 86.7 m/Km)| style="background-color: #FFE383;"|0.029% (152.6 Ft/Mile 28.9 m/Km)| 0.087 (457.9 Ft/Mile 86.7 m/Km)| stylevalign="background-color: #FED981;top"|0.043 (229.0 Ft/Mile 43.4 m/Km)|-| rowspan="6"|{{Garmin 910XT}} with [[Footpod]]| Normal| 514| 0.059 (311.5 Ft/Mile 59.0 m/Km)| style="background-color: #A1D07E;"|0.014% (75.4 Ft/Mile 14.3 m/Km)| 0.059 (311.5 Ft/Mile 59.0 m/Km)| style="background-colorFile: #B6D67F;"|0.030 (155Garmin620 Offset1.8 Ft/Mile 29.5 m/Km)jpg|-none| Under Bridgethumb| 43x500px| 0Here you can see the last repeat is offset.168 (889.0 Ft/Mile 168Starting at lap marker 49, the track follows the same outline as the more accurate tracks, but is offset.So marker 50 should be near 4 m/Km)| style="background-color: #B2D47F;"|0.016% (86.1 Ft/Mile 16.3 m/Km)| 0.168 (889.0 Ft/Mile 168.4 m/Km)| style="background-color: #F8696B;"|0.084 (444.5 Ft/Mile 84., 51 near 37, 52 near 2 m/Km)|-| Post Bridge| 40| 0.043 (226.4 Ft/Mile 42.9 m/Km)| style="background-color: #FDBC7B;"|0.043% (229., 53 near 1 Ft/Mile 43, and the finish near the start.4 m/Km)]]| 0.043 (226.4 Ft/Mile 42.9 m/Km)| style="background-color[[File: #63BE7B;"|0Garmin620 Offset2.021 (113.2 Ft/Mile 21.4 m/Km)jpg|-none| Turn Aroundthumb| 43x500px| 0.051 (270.7 Ft/Mile 51.This is a simple out and back run of ~3 mmiles/5 Km)| style="background-color: #FCA777;"|0.051% (270.2 Ft/Mile 51.2 m/Km)| 0, but you can see after the turn around the Garmin 620 records a gradually widening gap, even though it follows the right overall shape.051 (270The outbound track is fairly accurate, the return is messed up.7 Ft/Mile 51.3 m/Km)| style="background-color: #8ECA7D;"|0.026 (135.3 Ft/Mile 25.6 m/Km)|-| Power Line| 90| 0.048 (254.4 Ft/Mile 48.2 m/Km)| style="background-color: #D8E081;"|0.021% (110.9 Ft/Mile 21.0 m/Km)| 0.048 (254.4 Ft/Mile 48.2 m/Km)| style="background-color: #7EC57C;"|0.024 (127.2 Ft/Mile 24.1 m/Km)|-| Mixed| 730| 0.071 (377.2 Ft/Mile 71.4 m/Km)| style="background-color: #C8DB80;"|0.019% (100.3 Ft/Mile 19.0 m/Km)| 0.071 (377.2 Ft/Mile 71.4 m/Km)| style="background-color: #F7E883;"|0.036 (188.6 Ft/Mile 35.7 m/Km)]]

==Interpretation=Garmin Fenix 2 Issues=What do these statistics mean? This is my interpretation:* Under normal conditions Like the Garmin 620, I've had similar GPS accuracy is quite good for all devicesissues with the Fenix 2. * Not surprisinglyIn fact, accuracy drops going under the bridge. * More interestingly Fenix 2 is the trueness just after only device I've ever had that has given the bridge is even lower"lost satellite reception" message on my usual running route. Because of these issues Garmin replaced my Fenix 2 under warranty, suggesting that and below are the results for the GPS original and new watches are struggling to reacquire the satellites. * The turnarounds are even less accurate than going under a bridge, but Power Lines replacement watch also gave "lost satellite reception" repeatedly and the error values for the Fenix 2 do not seem to impact accuracy noticeably. * The [[Footpod]] improves reflect these problems as the accuracy of the 310XTdata from those runs was useless for analysis. ** Note that I'm intentionally using an uncalibrated Footpod suspect there are three (factor = 1.000possibly related) to gather data for a comparison of Foodpod and problems with the Fenix 2:# The MediaTek GPSchipset is not as accurate as the SiRF chipset. * The Garmin 205 does remarkably well, especially for an older devicebest results from the Fenix 2 are generally mediocre. * Without # The Fenix 2 records the Footpod, the 310XT has similar problems to the RC3 on the turn aroundright shape track, but the RC3 does quite a bit worse under the bridge.=Recommendations=Here are offset by some recommendations for GPS watchesdistance.* GPS watches are accurate enough for most general running.* Adding This does not look like a Footpod to the {{Garmin 310XT}} improves its typical accuracyproblem that would manifest itself randomly. * It takes time for # Occasionally the GPS watches to acquire Fenix 2 will report "lost satellite reception", and I have several instances of this where the satellitesdate and time were wrong after reception was lost. Some watches tended to say they are ready to go before they have an optimal lock. Therefore, to improve accuracy try to give them If a little more time. Note that some newer GPS watches such as device has the [http://www.amazon.com/Garmin-010-01128-30-Forerunner-620-Bundle/dp/B00FBYYC90 Garmin 620] have wrong time, then it will expect the ability satellites to be preloaded with the satellite in different positions, reducing this startup time and start up in accuracy dramatically.* The GPS watches are not accurate enough will be unable to perform any type of [[Practical Interval Training| interval training]]. Instead, use a track or measure out the distance using some other mechanism.* GPS is not accurate enough to give acquire a good reading of current paceposition fix. =Even GPS Watches I have Bad Days=While it's tempting to take four instances where the various GPS watches on workout file was stored with a single run and simply compare the totalsdate in April 2019, this is a flawed approach. Evaluating indicating that was the devices GPS accuracy on date when I terminated 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 workout and bad days, and that applies attempted to GPS watches as well. To illustrate this, the images below are from two runs, recorded on 9/20 and 9/22reacquire satellite lock. In each run one case I recorded data on both noticed the 310 date 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 set incorrectly on the 310XT, but on 9/22 watch display after the situation is reversedsatellite lost message. If you were to have evaluated There are also reports from various users about lost satellite reception and the two watches on 2019 date. This problem might also explain the basis of a single runoffset track above, you would conclude that one is much better than but only if 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 clock was out by a statistical analysis to work out which is really bettervery small amount. {{:GPS Accuracy-Fenix2}}

|[[File:310XT BadFenix2 Getting Lost.jpg|none|thumb|x500pxx400px| This is an example of just how bad the Fenix 2 can be. This is a short run, with the start and finish in the same place. The {{Garmin 310XT}} having track up to marker 18 is not bad, but then the Fenix 2 loses reception for a bad daycouple of miles. When it gets reception back, it tracks wildly off course, ending up with a position that's out by around a mile.]]|[[File:Fenix2 Getting Lost3.jpg|none|thumb|x400px|Another example of the Fenix 2 getting lost. You can see on marker 41 is a long way off the upper route, probably about half a mile off. Notice how messy the rest of the course where it got a little confused and off trackis as well. ]]|[[File:910XT GoodFenix2 Getting Lost4.jpg|none|thumb|x500pxx400px|The {{Garmin 910XT}} on Here you can see the same run having no problems, and only the standard, expected level of inaccuracyFenix 2 track is a confused mess.]]

|[[File:310XT GoodFenix2 Getting Lost5.jpg|none|thumb|x500pxx400px|Two days later The first part of this run goes okay, but at marker 61 things to go a little astray, and it's at marker 65 the turn of GPS lock is lost, then briefly regained until marker 70. Not unreasonably, the {{Garmin 310XT}} Fenix 2 assumes straight-line movement until GPS lock is reacquired, but then rather bizarrely seems to have assume that the straight-line movement is correct and records a track that is about half a good daymile/1 Km off.]]|[[File:910XT BadFenix2 Short1.jpg|none|thumb|x500pxx400px|AgainThis is more how the GPS track should look, but even on this track is recorded on run the same Fenix 2 lost nearly a mile in a 20 mile run as the image to the left. The {{Garmin 910XT}} gets a little confused at the start]]|[[File:Fenix2 Getting Lost6.jpg|none|thumb|x400px|This GPS track looks reasonable until marker #54, and then again around lap 27the track gets offset, but strangely it stays offset until the last marker.]]

* 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.* 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. I wait for 5+ minutes between the watches saying they have sufficient satellites locked in, so this should not be a problem with the data shown here, but I could do some tests where I turn on the watch from a cold state, then start running as soon as they claim they have a lock.