GPS Accuracy of Garmin, Polar, and other Running Watches

From, Running tips
Jump to: navigation, search

I evaluated the real world accuracy of GPS watches while running over 6,000 miles/9,600Km and recording over 25,000 data points as part of my evaluation of the Best Running Watches. Under good conditions most of the watches are remarkably good, but when things get a little tough the differences become more apparent. However, none of the watches have GPS accuracy that is good enough to be used for displaying your current pace. For current pace, the only viable option is to use a Footpod, and my review of running watches lists those that can display current pace from a Footpod while still using GPS for your course.

An infographic of the accuracy of the GPS running watches. The top right corner represents the most accurate watches. (This graphic uses ISO 5725 terminology.)

The table below is a simplified summary of the results, where a '10' would be a perfect device. (For an explanation of the ISO 5725 terms 'trueness', 'precision' and 'accuracy', see below.)

Device Accuracy Trueness Precision
Footpod (calibrated) 7.7 9.9 7.7
Polar V800 7.6 9.8 7.6
Garmin 205 6.8 9.5 6.9
Garmin 910XT with Footpod 6.8 8.7 7.1
iPhone 4s 6.8 9.1 6.9
Garmin 310XT with Footpod 6.6 9.4 6.7
Garmin 610 6.4 8.2 6.9
Garmin 620 (3.30) 6.3 8.2 6.7
Garmin 310XT no Footpod 5.9 9.1 6.1
Samsung Galaxy S3 5.8 8.7 6.0
Suunto Ambit2 R 5.8 8.8 5.9
Footpod (uncalibrated) 5.5 7.5 6.2
Polar RC3 GPS 5.1 8.4 5.4
TomTom Cardio Runner 5.0 6.6 6.3
Garmin Fenix 2 (3.30) 4.7 7.3 5.4
Garmin 10 4.1 6.1 5.6
Garmin 620 (pre-v3.30) 3.7 6.6 4.7
Polar M400 3.5 5.9 5.0
Garmin Fenix 2 (pre-v3.30) 3.2 7.2 3.8

The values used are simply 10 minus the value for trueness and standard deviation. The overall is 10 minus the standard deviation from true values.

1 Methodology

Main article: GPS Testing Methodology

Simply taking a GPS watch on a single run does not provide sufficient data to reasonably evaluate its accuracy. To gather the data for this test I ran the same route repeatedly, recording laps every quarter mile. The course is challenging for GPS, with lots of twists, tree cover, power lines, turn arounds and goes under a bridge. However, I believe that it's reasonably representative of real-world conditions, and probably less challenging than running in the city with skyscrapers.

2 Accuracy, Trueness and Precision

For this evaluation I'll use the ISO 5725 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. 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. )

3 Accuracy

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 split off the Detailed Statistics for GPS Running Watches for the results under different conditions.

Device Count Trueness
(Average Distance Error)
Standard Deviation
(From mean)
Standard Deviation
(From true)
Average Pace Error
(from 9:00 min/mile) (from 5:30 min/Km)
Footpod (calibrated) 3724 0.13% (7.1 Ft/Mile, 1.3 m/Km) 2.34% (123.4 Ft/Mile, 23.4 m/Km) 2.34% (123.6 Ft/Mile, 23.4 m/Km) 0:13 0:08
Polar V800 1095 0.22% (11.5 Ft/Mile, 2.2 m/Km) 2.41% (127.1 Ft/Mile, 24.1 m/Km) 2.42% (127.6 Ft/Mile, 24.2 m/Km) 0:13 0:08
Garmin 205 1125 0.47% (24.9 Ft/Mile, 4.7 m/Km) 3.14% (166.0 Ft/Mile, 31.4 m/Km) 3.18% (167.9 Ft/Mile, 31.8 m/Km) 0:17 0:10
Garmin 910XT with Footpod 725 1.28% (67.8 Ft/Mile, 12.8 m/Km) 2.94% (155.4 Ft/Mile, 29.4 m/Km) 3.21% (169.6 Ft/Mile, 32.1 m/Km) 0:17 0:11
iPhone 4s 956 0.90% (47.3 Ft/Mile, 9.0 m/Km) 3.12% (164.9 Ft/Mile, 31.2 m/Km) 3.25% (171.6 Ft/Mile, 32.5 m/Km) 0:18 0:11
Garmin 310XT with Footpod 3724 0.62% (33.0 Ft/Mile, 6.2 m/Km) 3.30% (174.1 Ft/Mile, 33.0 m/Km) 3.36% (177.2 Ft/Mile, 33.6 m/Km) 0:18 0:11
Garmin 610 2085 1.77% (93.3 Ft/Mile, 17.7 m/Km) 3.14% (165.9 Ft/Mile, 31.4 m/Km) 3.61% (190.3 Ft/Mile, 36.1 m/Km) 0:19 0:12
Garmin 620 (3.30) 1130 1.76% (92.9 Ft/Mile, 17.6 m/Km) 3.28% (173.1 Ft/Mile, 32.8 m/Km) 3.72% (196.5 Ft/Mile, 37.2 m/Km) 0:20 0:12
Garmin 310XT no Footpod 1945 0.94% (49.8 Ft/Mile, 9.4 m/Km) 3.94% (208.0 Ft/Mile, 39.4 m/Km) 4.05% (213.9 Ft/Mile, 40.5 m/Km) 0:22 0:13
Samsung Galaxy S3 832 1.28% (67.7 Ft/Mile, 12.8 m/Km) 4.00% (211.4 Ft/Mile, 40.0 m/Km) 4.20% (222.0 Ft/Mile, 42.0 m/Km) 0:23 0:14
Suunto Ambit2 R 1025 1.15% (60.9 Ft/Mile, 11.5 m/Km) 4.08% (215.7 Ft/Mile, 40.8 m/Km) 4.24% (224.1 Ft/Mile, 42.4 m/Km) 0:23 0:14
Footpod (uncalibrated) 3724 2.46% (129.8 Ft/Mile, 24.6 m/Km) 3.81% (201.0 Ft/Mile, 38.1 m/Km) 4.53% (239.3 Ft/Mile, 45.3 m/Km) 0:24 0:15
Polar RC3 GPS 1433 1.65% (86.9 Ft/Mile, 16.5 m/Km) 4.62% (244.2 Ft/Mile, 46.2 m/Km) 4.91% (259.2 Ft/Mile, 49.1 m/Km) 0:27 0:16
TomTom Cardio Runner 946 3.42% (180.6 Ft/Mile, 34.2 m/Km) 3.65% (192.8 Ft/Mile, 36.5 m/Km) 5.00% (264.2 Ft/Mile, 50.0 m/Km) 0:27 0:17
Garmin Fenix 2 (3.30) 1111 2.68% (141.4 Ft/Mile, 26.8 m/Km) 4.61% (243.3 Ft/Mile, 46.1 m/Km) 5.33% (281.4 Ft/Mile, 53.3 m/Km) 0:29 0:18
Garmin 10 1042 3.89% (205.4 Ft/Mile, 38.9 m/Km) 4.37% (231.0 Ft/Mile, 43.7 m/Km) 5.86% (309.2 Ft/Mile, 58.6 m/Km) 0:32 0:19
Garmin 620 (pre-v3.30) 3213 3.37% (178.1 Ft/Mile, 33.7 m/Km) 5.27% (278.4 Ft/Mile, 52.7 m/Km) 6.26% (330.5 Ft/Mile, 62.6 m/Km) 0:34 0:21
Polar M400 831 4.11% (217.3 Ft/Mile, 41.1 m/Km) 4.98% (262.8 Ft/Mile, 49.8 m/Km) 6.46% (341.1 Ft/Mile, 64.6 m/Km) 0:35 0:21
Garmin Fenix 2 (pre-v3.30) 4378 2.79% (147.4 Ft/Mile, 27.9 m/Km) 6.16% (325.3 Ft/Mile, 61.6 m/Km) 6.76% (357.2 Ft/Mile, 67.6 m/Km) 0:37 0:22

3.1 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 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.

3.2 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, 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 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.
    • Note that 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.

4 Recommendations

Here are some recommendations for GPS watches.

  • Most GPS watches are accurate enough for casual running. However, the M400, Fenix2, and 10 have such serious problems that I would not recommend them even for casual usage.
  • The better devices are accurate enough for most runners if their limitations are understood.
  • None of the devices were accurate enough for a runner to trust the display of current pace for training or race pacing.
    • For interval training, use a track or measure out the distance using some other mechanism.
    • For general training or for races, use a device that supports displaying pace from the Footpod while using GPS for distance.
  • Adding a Footpod to the Garmin 310XT improves its GPS accuracy.
  • For the Garmin 610 there was no difference with and without the Footpod. (Trueness was 3.33%/3.32%, Precision was 3.54%/3.68%, with/without).
  • It takes time for the GPS watches to acquire the satellites. Some 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 inaccuracy dramatically.

5 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 Footpod 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, I've found that I always have to use a Footpod to pace a marathon or for critical speedwork. For details of how the Footpod calibration was done, see GPS Testing Methodology.

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 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.)

You can see the GPS tracks (thin red line) are close together and the lap markers (yellow diamonds) are clustered nicely. The blue dots on the GPS tracks are the actual GPS recordings.
By contrast, the 620 has much wider GPS tracks and dispersed lap markers.

8 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 Kalman filter. (When I tested using software without smoothing I found the measurements were long on my course rather than short, which is almost always the case.)

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.

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 cutting the corner at the top (we didn't run through the building).
Here's another example of running down Market Street in San Francisco, where you can see the errors that would add to the distance.

9 Garmin 620 Issues

The Garmin 620 had some notorious problems with its GPS accuracy. The table below shows the changes with various firmware versions, culminating in the GPS-3.30 firmware that resolved the issues. I've including some testing I did without EPO data (NoEPO row below) and with a Footpod (+FP row below).

Device Count Trueness
(Average Distance Error)
Standard Deviation
(From mean)
Standard Deviation
(From true)
Average Pace Error
(from 9:00 min/mile)
Average Pace Error
(from 5:30 min/Km)
Garmin 620 (original v2.80) 711 2.52% (133.3 Ft/Mile, 25.2 m/Km) 4.04% (213.5 Ft/Mile, 40.4 m/Km) 4.77% (251.8 Ft/Mile, 47.7 m/Km) 0:26 0:16
Garmin 620 (original v2.90) 480 2.11% (111.4 Ft/Mile, 21.1 m/Km) 3.87% (204.4 Ft/Mile, 38.7 m/Km) 4.41% (232.9 Ft/Mile, 44.1 m/Km) 0:24 0:15
Garmin 620 (replacement v2.90) 421 5.31% (280.6 Ft/Mile, 53.1 m/Km) 6.00% (316.6 Ft/Mile, 60.0 m/Km) 8.02% (423.3 Ft/Mile, 80.2 m/Km) 0:43 0:26
Garmin 620 (replacement v3.00) 425 4.68% (247.3 Ft/Mile, 46.8 m/Km) 5.80% (306.3 Ft/Mile, 58.0 m/Km) 7.46% (393.8 Ft/Mile, 74.6 m/Km) 0:40 0:25
Garmin 620 (replacement v3.00, NoEPO) 324 2.85% (150.7 Ft/Mile, 28.5 m/Km) 4.71% (248.5 Ft/Mile, 47.1 m/Km) 5.51% (290.7 Ft/Mile, 55.1 m/Km) 0:30 0:18
Garmin 620 (replacement v3.00, +FP) 852 3.38% (178.4 Ft/Mile, 33.8 m/Km) 5.97% (315.2 Ft/Mile, 59.7 m/Km) 6.86% (362.2 Ft/Mile, 68.6 m/Km) 0:37 0:23
Garmin 620 (replacement v3.00, GPS 3.30) 1130 1.76% (92.9 Ft/Mile, 17.6 m/Km) 3.28% (173.1 Ft/Mile, 32.8 m/Km) 3.72% (196.5 Ft/Mile, 37.2 m/Km) 0:20 0:12
Here you can see the last repeat is offset. Starting 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, 51 near 37, 52 near 2, 53 near 1, and the finish near the start.
This is a simple out and back run of ~3 miles/5 Km, but you can see after the turn around the Garmin 620 records a gradually widening gap, even though it follows the right overall shape. (The outbound track is fairly accurate, the return is messed up.)

10 Garmin Fenix 2 Issues

Like the Garmin 620, I've had similar GPS accuracy issues with the Fenix 2. In fact, the Fenix 2 is the only device I've ever had that has given the "lost satellite reception" message on my usual running route. Because of these issues Garmin replaced my Fenix 2 under warranty, and below are the results for the original and new watches. The replacement watch also gave "lost satellite reception" repeatedly and the error values for the Fenix 2 do not reflect these problems as the data from those runs was useless for analysis. I suspect there are three (possibly related) problems with the Fenix 2:

  1. The MediaTek GPS chipset is not as accurate as the SiRF chipset. The best results from the Fenix 2 are generally mediocre.
  2. The Fenix 2 records the right shape track, but offset by some distance. This does not look like a typical accuracy problem that would manifest itself randomly.
  3. Occasionally the Fenix 2 will report "lost satellite reception", and I have several instances of this where the date and time were wrong after reception was lost. If a GPS device has the wrong time, then it will expect the satellites to be in different positions and will be unable to acquire a position fix. I have four instances where the workout file was stored with a date in April 2019, indicating that was the date when I terminated the workout and attempted to reacquire satellite lock. In one case I noticed the date and time was set incorrectly on the watch display after the satellite lost message. There are also reports from various users about lost satellite reception and the 2019 date. This problem might also explain the offset track above, but only if the clock was out by a very small amount.
Device Count Trueness
(Average Distance Error)
Standard Deviation
(From mean)
Standard Deviation
(From true)
Average Pace Error
(from 9:00 min/mile)
Average Pace Error
(from 5:30 min/Km)
Garmin Fenix 2 original 2.50 1511 1.72% (91.0 Ft/Mile, 17.2 m/Km) 5.98% (315.5 Ft/Mile, 59.8 m/Km) 6.22% (328.4 Ft/Mile, 62.2 m/Km) 0:34 0:21
Garmin Fenix 2 replacement 3.10 404 3.29% (173.5 Ft/Mile, 32.9 m/Km) 5.36% (283.2 Ft/Mile, 53.6 m/Km) 6.29% (332.3 Ft/Mile, 62.9 m/Km) 0:34 0:21
Garmin Fenix 2 replacement 3.20 641 3.32% (175.4 Ft/Mile, 33.2 m/Km) 5.68% (300.1 Ft/Mile, 56.8 m/Km) 6.58% (347.6 Ft/Mile, 65.8 m/Km) 0:36 0:22
Garmin Fenix 2 replacement 3.20 (No WAAS) 867 3.24% (171.3 Ft/Mile, 32.4 m/Km) 6.50% (343.4 Ft/Mile, 65.0 m/Km) 7.27% (383.8 Ft/Mile, 72.7 m/Km) 0:39 0:24
Garmin Fenix 2 replacement 3.70 (+FP) 741 3.72% (196.2 Ft/Mile, 37.2 m/Km) 6.85% (361.6 Ft/Mile, 68.5 m/Km) 7.79% (411.5 Ft/Mile, 77.9 m/Km) 0:42 0:26
Garmin Fenix 2 replacement (Hotstart) 214 2.78% (146.8 Ft/Mile, 27.8 m/Km) 5.22% (275.8 Ft/Mile, 52.2 m/Km) 5.92% (312.6 Ft/Mile, 59.2 m/Km) 0:32 0:20
Garmin Fenix 2 replacement 4.00, GPS 3.30 1111 2.68% (141.4 Ft/Mile, 26.8 m/Km) 4.61% (243.3 Ft/Mile, 46.1 m/Km) 5.33% (281.4 Ft/Mile, 53.3 m/Km) 0:29 0:18
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 track up to marker 18 is not bad, but then the Fenix 2 loses reception for a couple of miles. When it gets reception back, it tracks wildly off course, ending up with a position that's out by around a mile.
Another example of the Fenix 2 getting lost. You can see marker 41 is a long way off the route, probably about half a mile off. Notice how messy the rest of the track is as well.
Here you can see the Fenix 2 track is a confused mess.
The first part of this run goes okay, but at marker 61 things to go a little astray, and at marker 65 the GPS lock is lost, then briefly regained until marker 70. Not unreasonably, the Fenix 2 assumes straight-line movement until GPS lock is reacquired, but then rather bizarrely seems to assume that the straight-line movement is correct and records a track that is about half a mile/1 Km off.
This is more how the GPS track should look, but even on this run the Fenix 2 lost nearly a mile in a 20 mile run.
This GPS track looks reasonable until marker #54, and then the track gets offset, but strangely it stays offset until the last marker.

11 Polar V800 GPS Accuracy

As you can see from the numbers above, the V800 is remarkably accurate. The V800 uses the latest SiRF chipset, rather than the MediaTek chipset that has caused so many problems in the Garmin 620 and Garmin Fenix 2. This SiRF chipset includes satellite prediction to reduce the time it takes to acquire the first satellite lock. This generally works pretty well, but is not as fast as the MediaTek chipset.

12 GPS Accuracy and Pace

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.

13 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 R with recording set to one minute intervals. As you can see, accuracy suffers on curves, but is fine on the straights. For a course like Badwater, the one minute recording interval was fine as the course has few turns.

On a curve, the infrequent samples tend to 'cut the corners' and are quite inaccurate.
On the straight sections, the one minute sampling does not lose any accuracy.
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.

14 Device Specific Notes

For those interested in some of the details of how devices are configured for testing, here are some additional notes.

  • Garmin devices are set to 'smart recording'. I did try an informal test with the 620 using 1-second recording, but it appeared to make no difference.
  • For details of the calibration of the Footpod see GPS Testing Methodology.
  • The Fenix 2 was tested with and without WAAS support activated; WAAS helped slightly.

15 Next Steps

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

  • 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.
  • Look at how accurate the GPS watches are for measuring elevation, and compare with barometric data.
  • Write up general GPS accuracy.