Skip to main content

This was sent to me by a friend. It's from the University of Salzburg.
GPS article

Runners, mariners, airmen, and wilderness trekkers beware: Your global positioning system (GPS) is flattering you, telling you that you have run, sailed, flown, or walked significantly farther than you actually have. And it’s not the GPS’s fault, or yours.
Blame the statistics of measurement. Researchers at the University of Salzburg (UoS), Salzburg Forschungsgesellchaft (SFG), and the Delft University of Technology have done the math to prove that the distance measured by GPS over a straight line will, on average, exceed the actual distance traveled. They also derive a formula for predicting how big the error will be. The open-access paper was published in the International Journal of Geographical Information Science; an earlier version is available on Arxiv.
GPS course calculations are subject to both interpolation error (a function of the sampling interval) and measurement error (the everyday orneriness of real-world physical systems). The Salzburg team—including first author Peter Ranacher of UoS and senior author Siegfried Reich of SFG—discovered a systematic bias in distance measurement errors.
Measurement errors have many causes. The paper specifically cites: propagation delay (atmospheric fluctuations affect the speed of the GPS signal); ephemeris error (uncertainty in the precise position of the GPS satellite); satellite clock drift; hardware error (the shortcomings of the terrestrial GPS unit); signal reflections (which can increase the length of the signal path); and unfavorable satellite geometry (available GPS satellites are too low in the sky or too close together or too few, for example).
Put them together and you have readings that scatter around the true position. The Salzburg researchers found that distances derived from position measurements with randomly distributed errors will, on average, come up longer than the actual separation between two points. There are three components to their calculation:
• The reference distance (d0): the actual Euclidean distance between two points
• The variance (Vargps): the “mean of the square minus the square of the mean” of the position error, an index of how accurate the position measurement is. Variance is the square of the standard deviation, σ2
• The autocorrelation (C, perhaps more properly the autocovariance) of the measurement error. This can vary from a maximum of Vargps (if the errors are closely covariant) to 0 (if they are random) to -Vargps (if there is an inverse correlation).
The Salzburg formula for the average Overestimation of Distance (OED) is then,
OED = (d02 + Vargps - C)1/2 - d0
The variance is always positive, so if the autocorrelation is lower than the variance, the overestimation of distance will always be positive. And the autocorrelation is generally lower than the variance.
The problem becomes particularly acute when the user (or the GPS) calculates the total distance traveled by adding together the lengths of multiple segments. The differences between the true and measured distance will fluctuate—sometimes short, but more often long. Because the GPS-measured distance skews long, though, the total GPS distance error will tend to grow with each added segment.
Not content with mere calculation, Ranacher, Reich, and their colleagues went on to test their findings experimentally. In an empty parking lot, they staked out a square course 10 m on a side, reference-marked each side at precise 1-m intervals, and set a GPS-equipped pedestrian (a volunteer, one hopes) to walk the perimeter 25 times, taking a position reading at each reference mark.
The researchers analyzed the data for segment lengths of 1 meter and 5 meters. They found that the mean GPS measurement for the 1-m reference distance was 1.02 m (σ2 = 0.3) and the mean GPS measurement for the 5-m reference distance was 5.06 m (σ2 = 2.0). They also ran a similar experiment with automobiles on a longer course, with similar results.
Now, that pedestrian-course error of 1.2 to 2 percent isn’t huge. But it is big enough that your GPS watch could tell you you’re crossing the finish line of a 42,195-meter marathon while the real terminus is more than 400 meters ahead.
That’s not a hypothetical example. For years, runners have complained that their GPS watches and other devices have mismeasured the distances they’ve run over supposedly verified courses, or suddenly finding that they set personal record times the first time they use a GPS to measure their course. There have been a number of confident explanations. Most involved either interpolation error (measuring the distance between successive plots as a straight line, which will likely report a shorter-than-actual distance over a twisty course) or the runner’s non-optimal choice of routes (adding to the verified distance on each leg, and reporting a longer actual distance traveled). Maybe they’ll like this explanation better.
The Ranacher team’s results do not mean that measuring the lengths of complex courses by GPS is futile. They point out that moment-by-moment GPS velocity measurement is not subject to the same sources of error, so that calculating distance traveled by integrating velocity should yield reasonably accurate results.
Learn More
GPS GPS error Global Positioning System University of Salzburg
Original Post

Replies sorted oldest to newest

You'll need to read the actual paper (as opposed to the above description of it) to understand that what the paper proves is for a particular type of trajectory (consisting of only straight lines between GPS samples) and a particular method of calculating distance traveled (the summation of its estimates of those straight line distances, or simply connecting the dots), a GPS it will always overestimate the true distance.

A simple example of this is if you walk in a straight line carrying a GPS. Each sample it takes as you walk will probably be slightly to the left or slightly to the right of where you actually are. If it calculates distance by simply connecting those dots, that path will always be longer than the straight line path that you took.

But GPS units don't use this method of simply connecting the dots to calculate distance. They use filters to smooth out those dots because they know, for the most part, people don't run or bike in zig-zag paths. They tend to follow straight lines or smooth curves, so the GPS filters the data to approximate the straight line or smooth curve that you probably followed, and calculates the distance of that smooth path. Of course that estimate of your path is not perfect. Sometimes it is slightly longer, and yes sometimes it is slightly shorter, than your actual path.
Mark,
I think you are spot on. I have come to the same conclusion after thinking about it overnight.
It is those left and right displacements that add distance. The traces from most running GPSs uploaded to Strava and Garmin, no longer have that zigzag appearance, which they often used to have 7 or 8 years ago. Smoothing algorithms have been evolving and overall the excess distance has reduced slightly. What I have now found by analysing many traces of the same race, is that different watch models give slightly different results.
TomTom Sports watch can give a sightly shorter result than the true distance.
Garmins models vary, mostly slightly long.
Strava iPhone app and Strava Android apps give longer results.
All of this assumes a given benchmark steel-taped distance with which to make the comparison, right? Maybe I should read the entire paper. Alan doesn't state how the "verified distance" was established.

What about frequency of reading? I know GPS units have improved significantly over the years. But to the extent that there are many fewer points recorded than a JC measurement, there will be some error regardless of the validity of the algorithm, no? Does anyone know what the reading frequency (recording of points frequency) current consumer models offer?

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×