GPS pacing errors: bridges, tall buildings and tangents
GPS can misread pace on bridges, through tunnels and between tall buildings. Check your lap pace against course markers and allow for the extra distance you may run around corners.
Why GPS pace errors are more visible in races
GPS watches estimate pace from position changes over time. That’s fine when the signal is clean and you run a straight line. But racing adds problems: you weave, you run close to buildings, you run under bridges, and GPS sampling/smoothing can lag behind your true speed.
Ten GPS pacing errors to recognise
1) Using instantaneous pace as your primary guide
Instant pace jumps when the signal jitters—then you surge to “fix it”—then it jumps again. That’s how runners accidentally turn a steady marathon into a series of micro-intervals.
Fix: Use lap pace (1 km) or average pace, plus a pace band.
2) Starting before GPS has a solid lock
If you start while your watch is still figuring out satellites, your early track can be messy, which impacts pace and distance.
Fix: Start GPS early. Wait for a solid lock. Don’t start recording in a tunnel or under a roof.
3) Urban canyon pacing (tall buildings)
Tall buildings can block and reflect signals, causing “urban canyon” problems and multipath errors. Your track may zig-zag on the map while you ran straight.
Fix: Don’t chase pace in cities. Use lap/average pace + RPE until you’re out of the canyon.
4) Bridges, tunnels, underpasses
Under/through obstructions, GPS may temporarily lose signal or mis-estimate position, producing random pace spikes.
Fix: Hold effort for 30–90 seconds, ignore spikes, and rely on the next km marker + lap pace.
5) Trees and heavy cover
Even outside cities, tree cover can degrade signal quality. Your “instant pace” becomes a mood swing.
Fix: Same solution: lap pace + RPE + pace band.
6) Auto-pause (or too-aggressive auto-stop)
Auto-pause can distort your pacing and splits if it triggers incorrectly in crowds or on tight turns.
Fix: Turn it off for races.
7) Chasing people (weave → surge → brake)
This is not just a pacing mistake—it’s a distance mistake. You run extra metres and spend extra energy.
Fix: Pick a clean line, accept small delays, and move through gaps smoothly—never with a surge.
8) Trusting watch distance over the course
On a certified course, the official distance is measured along the shortest possible route runners are allowed to take. Your GPS distance is your personal path, plus GPS error.
Fix: Pace off official km markers and your pace band. Use watch distance as “approximate.”
9) Running wide on every corner
Every wide turn adds distance. Do it 30–60 times and you’ve quietly changed the event.
Fix: Learn tangents (below). A direct line can reduce unnecessary distance.
10) Trying to “make up” GPS error with effort
If GPS says you’re slow (but you feel fine), surging to “correct” it is the classic trap.
Fix: Trust effort and lap pace. The signal may improve after the obstruction, but accumulated distance error can remain.
A simple watch setup
Suggested settings:
- Auto-lap: 1 km (or manual lap at km markers if GPS is chaotic)
- Turn off auto-pause
- If your watch supports it: use the best GNSS mode you can afford battery-wise (especially for cities)
- Display pace as lap pace / smoothed pace (avoid raw instant pace)
Backup plan: carry a pace band or memorize 5K/10K/HM checkpoints. When GPS lies, your band doesn’t.
Bridges, tunnels, tall buildings: what to do in the moment
When GPS breaks, your job is to avoid reacting abruptly to an unreliable reading.
| Scenario | What you’ll see | What to do | What NOT to do |
|---|---|---|---|
| Tall buildings | Instant pace spikes, weird track | Hold effort; use lap pace + RPE | Surge repeatedly to “fix” pace |
| Bridge/underpass | Sudden slow/fast pace, distance jump | Ignore for 30–90s; reset at next marker | Brake hard or sprint to correct |
| Tunnel | Pace drops or freezes | Run by feel; lap at marker after exit | Panic-slow because the watch “says” slow |
| Tight turns/crowds | Stop-start splits | Run clean line; accept small delays | Weave and surge (costs energy + distance) |
Why your marathon “ran long” on GPS
If you ran a certified marathon and your watch says 42.5–43.0 km, you’re not alone. Here are the main reasons:
1) Certified courses are measured on the shortest possible route
Road race certification standards define measurement along the shortest possible route an athlete could take within the permitted road area. Your actual route (weaving, running wide, passing) is usually longer.
2) The measurement line isn’t “the middle of the road”
Certification procedures measure close to the inside of turns (within a defined margin), and they include a small “short course prevention factor” so the course is not accidentally short.
3) Your GPS track isn’t a measuring wheel
GPS error increases in tall buildings, under bridges, and under cover. Even small errors can add up over 42 km.
Run a direct legal line
Course measurement follows the shortest permitted route. The useful running habit is to connect turns with a smooth, direct line where the course and crowd allow it. Run the shortest legal line only where it is safe and practical. Sudden lane changes to chase every apex can add distance and interfere with other runners.
Look ahead, respect cones and marshals, and leave room for others. Avoid weaving across the road to reach an ideal line. In crowds, a predictable path matters more than saving a few metres.
Practise the setup and line choice
Within an ordinary easy run, notice where you can connect bends smoothly without crossing traffic, leaving the permitted path or changing speed. You do not need a separate tangent workout.
Practise the watch fields you intend to use. Lap averages can reduce short-term fluctuation, but GPS-based lap distance can still be wrong. Course markers and your checkpoint plan provide another reference.
Race-day checklist (copy/paste)
- ✅ GPS locked before the start
- ✅ Auto-pause OFF
- ✅ Primary pacing field = lap pace (1 km)
- ✅ Backup pacing = pace band + course km markers
- ✅ First 10K: no surges to “fix” GPS
- ✅ Turns: a smooth direct legal line (only where legal/safe)
- ✅ Crowds: smooth line beats weaving
FAQ
Does a long GPS record prove the course was long?
No. Your path and GPS error both affect recorded distance.
Should I follow instantaneous pace under a bridge?
Avoid reacting to an isolated implausible value. Use effort and later reliable references.
Should I run a smooth direct legal line at every turn?
No. Choose a smooth direct legal line without weaving, and give other runners space.
References
Signal obstruction and reflection affect measurement; the shortest permitted course line is a different issue. A long or short GPS recording can reflect both your route and measurement error.