Does GPS Count Hills? Distance Errors on Slopes and Curves

Mostly, no. A GPS app adds up distance on a flat map, so on a hill it misses the small extra length of the climb. That error is tiny: on a 10% grade the road is only 0.5% longer than its horizontal distance, and curves cost well under 1% when the app records a fix every second. Altitude itself doesn’t hurt GPS accuracy at all. If GPS and your car disagree by several percent on a mountain drive, the grade isn’t the reason. Blocked signal, slow recording and the car’s own bias are.

Here are the real numbers, the causes that do matter, and how to get a trustworthy distance on hilly, winding roads.

Does GPS account for hills when measuring distance? #

A GPS speedometer adds up the distance between successive positions using latitude and longitude, so the climb itself isn’t included. Your car’s odometer counts wheel turns along the road surface, slope and all.

The gap is the difference between the slope and its flat projection. It grows with the square of the grade, so it stays small on any road a car can climb:

Over a 20-mile mountain drive with half of it on 8% climbs and descents, the grade accounts for about 0.03 miles, under 200 feet. Climbing 1,000 m over 10 km of trail is an average 10% grade and adds only about 50 m. That’s far less than the percent or two a car odometer typically carries from its tires.

So the old advice to “calibrate” GPS distance for hills with a 1.05 to 1.2 multiplier is wrong. On almost any route, a multiplier that size would overstate your distance by 5 to 20%.

Does high altitude make GPS less accurate? #

Not in any way you’d notice. GPS satellites orbit about 20,200 km up, so being 3,000 m up a mountain changes nothing about your distance to them. The receiver already corrects for the delay the atmosphere adds to the signal, and that delay gets smaller the higher you go, because there’s less air above you.

What changes in the mountains is how much sky you can see:

• Valley walls and cliffs hide satellites low on the horizon. With the rest bunched overhead, position errors grow, especially sideways.
• Forest canopy weakens signals, and wet leaves are worse than dry ones. GPS accuracy under trees covers that in detail.
• Rock faces reflect signals. A reflected signal travels a longer path, which pushes the calculated position off.

On an open summit or high plateau, GPS often works better than in a city. Terrain decides accuracy, not height.

Does GPS speed read low when you’re going uphill? #

Only by the same tiny ratio. Phone GPS chips report horizontal ground speed, worked out from the Doppler shift of the satellite signals, so on a 10% climb at a true 60 mph the GPS shows about 59.7 mph.

If you’re seeing 3 to 5 mph gaps on climbs, look at these instead:

• Your car reads high all the time. Most speedometers over-read by a few percent on every road, as explained in GPS vs car speedometer.
• You’re changing speed. Cars slow on climbs and speed up on descents, and a smoothed GPS reading trails by a second or two during those changes, most noticeably when you brake hard for a bend on the way down. GPS speed lag explains why.
• The terrain blocks satellites. A cliff or a steep valley wall weakens the fix exactly where the road climbs.

Why does GPS lose distance on curves? #

GPS draws your route as straight lines between fixes. On a curve, each straight line is a chord across the arc you actually drove, so it’s slightly shorter. How much depends on how far you travel between fixes and how tight the curve is.

At one fix per second, which is what Speedometer GPS records, the loss is small on everything except hairpins:

The shortfall applies only on the curve itself, not on the straights between. So a twisty 10-mile road typically comes up short by a fraction of a percent overall.

Recording interval matters more than the curve #

The table assumes a fix every second. Many fitness apps and watches record less often to save battery, every few seconds or only when your direction changes. At 5-second intervals the loss on a curve is roughly 25 times larger, since it grows with the square of the gap. If one app reads noticeably shorter than another on winding roads, check its recording rate before blaming GPS.

Slow switchbacks #

Speedometer GPS adds one more effect. To stop a parked phone from collecting phantom distance, it ignores steps under 5 m between one-second fixes. Below about 18 km/h (11 mph) every step is shorter than that, so if you crawl round hairpins at walking pace, those stretches aren’t counted.

Why do mountain drives still read short? #

When GPS and the odometer disagree by 2% or more on a hilly, winding route, it’s almost always one of these:

1. Signal gaps. In a deep valley or under thick forest, fixes get worse or stop. Speedometer GPS doesn’t count distance from fixes worse than ±20 m, and when a good fix returns it joins the dots with a straight line that cuts across the bends it couldn’t see. That keeps false distance out at the cost of missing some real distance.
2. Tunnels. The app throws out any jump over 200 m between fixes as a glitch, so at 80 km/h any gap longer than about nine seconds, including a long tunnel’s whole length, is left out of the trip.
3. Your odometer’s bias. A car reading 3% high logs 20.6 miles on a true 20-mile loop, hills or no hills. On gravel or dirt, wheelspin adds a little more to the odometer while GPS reads slightly short, so the gap widens.
4. Short test distances. Over one or two miles, a single bad fix is a big share of the total. Compare over 20 miles or more.
5. Different starting points. Starting the GPS trip before or after you zeroed the odometer loses a few tenths.

The full list of reasons the two totals part ways, on any road, is in why GPS trip distance doesn’t match your odometer.

How to get an accurate distance on hills and winding roads #

There’s no correction factor that fixes hairpin corner-cutting or a valley with no sky, and a blanket multiplier just adds a new error. What helps:

1. Mount the phone high on the windshield or dash, where it sees as much sky as possible, and plug it in. A cup holder or door pocket loses satellites on every climb.
2. Set it up before you drive. Open the app, wait for the GPS pill to show GOOD or EXCELLENT, and press Start. Don’t touch it again until you’ve stopped. Twisty roads are exactly where your eyes need to stay up.
3. Check the fix afterwards, not during. The pill turns amber (FAIR, 10 to 20 m) or red (POOR, beyond 20 m) when the signal is weak. A passenger can watch it, and the saved trip’s route and speed chart show you later where the signal dropped.
4. Compare over long distances, and against distance markers on straight sections rather than across a string of hairpins.
5. Plan with map distance, record with GPS. For deciding where to stop for fuel, a mapping app’s route distance is the best estimate, because it’s measured along the road. GPS records what you actually drove, detours included.

Altitude is the one reading on a hill that does benefit from calibration. GPS altitude is noticeably less precise than horizontal position, often off by tens of metres. Watches and phones with a barometric altimeter give smoother climb totals, but a barometer drifts as the weather changes, and resetting it to a known elevation at a trailhead or pass sign fixes that. Speedometer GPS shows GPS altitude under the speed, which is handy for knowing roughly how high a pass is. It measures distance horizontally like most GPS apps, so expect it to match the map rather than your odometer.

Is the car odometer or GPS better for hilly trips? #

For total distance on a mountain trip, both are good to within a few percent, and they fail in different ways:

If you’ve measured your car’s odometer error with GPS on a flat highway, you can correct the odometer and get the best of both. On a route with long tunnels or thick forest, lean on the odometer.

Frequently asked questions #

Does GPS distance include elevation? #

Usually not. Phones and most GPS apps measure horizontal distance between positions, and some fitness devices fold in elevation. On real roads the missing slope distance is small: about 0.1% on a 5% grade and 0.5% on a 10% grade.

Does altitude affect GPS accuracy? #

Not directly. Satellites are about 20,200 km up, so a few thousand metres of elevation makes no difference, and there’s less atmosphere to delay the signal up high. Mountains hurt GPS through terrain: valley walls, cliffs and forest block or reflect signals, while open summits usually get excellent fixes.

Why is my GPS speed lower than my speedometer going uphill? #

Mostly because your speedometer reads a few percent high all the time, and partly because GPS lags a second or two while your speed changes on the climb. The grade itself lowers GPS speed by about half a percent at 10%, which is 0.3 mph at 60 mph.

Why is my phone’s GPS altitude wrong? #

Vertical accuracy is always worse than horizontal, because all the satellites are above you and none are below to balance the geometry. Some phones also report height above the GPS reference ellipsoid rather than above sea level, which can differ by tens of metres depending on where you are.

Should I trust GPS or my car on a switchback road? #

For speed, the car is steadier on switchbacks because GPS smoothing lags while you slow for each turn. For total distance, both are close: GPS may read a fraction of a percent short, and your odometer may read a percent or two long on worn tires.