62 GPS Location: Architecture and Error Control

ux-design

location

awareness

gps

62.1 Start With the Decision

A receiver can see four satellites and still produce a poor fix. Clock, atmosphere, geometry, and multipath each change the answer.

62.2 Route Overview

This is part 2 of 2. Review GPS Location: Ranging Methods for the preceding evidence.

62.3 Learning Objectives

Trace a GPS fix through receiver architecture.
Estimate timing, geometry, and propagation error effects.

62.4 Chapter Roadmap

GPS Architecture
Satellite Synchronization
Relativity Effects in GPS
Relativistic Time Dilation
Checkpoint: Satellite Timekeeping
GPS Position Calculation
Position from Satellite Signals
Uber GPS Accuracy in Manhattan
GPS Error Sources
Checkpoint: Operational Accuracy
Knowledge Check
Quiz: GPS Fundamentals
Interactive Quiz: Match Concepts
Interactive Quiz: Sequence the Steps
Key Takeaway
For Kids: Meet the Sensor Squad!
Concept Relationships
See Also
Try It Yourself
Common Pitfalls
Overbuilt Initial Prototypes
Security During Development
Failure Modes and Recovery
Label the Diagram
What’s Next
Code Challenge

62.5 GPS Architecture

Before deciding how Ephemeris, Clock, Atmospheric, Almanac shapes gps architecture, inspect Figure 62.1 beside Ground Antenna. Together, Ephemeris, Clock, Atmospheric, Almanac and Ground Antenna frame the gps architecture claim: gps system overview.

Overview of GPS system architecture showing the three segments: space segment with satellites, control segment with ground stations, and user segment with GPS receivers — Figure 62.1: GPS System Overview

Read Ephemeris, Clock, Atmospheric, Almanac alongside Ground Antenna in Figure 62.1; their named relationship makes gps system overview concrete. For gps architecture, Ephemeris, Clock, Atmospheric, Almanac supplies visible evidence; Ground Antenna constrains the decision. In Figure 62.1, retain Ephemeris, Clock, Atmospheric, Almanac beside Ground Antenna so gps architecture remains explicit.

GPS is TDoA (Inverted):

Satellites play the part of static devices (but are transmitters). Mobile device measures reception time using its clock. Uses satellite’s transmitted time for the time difference. For each satellite: measures (ToF + c × clockOffset). These are pseudoranges (erroneous distances).

62.6 Satellite Synchronization

Before deciding how Synchronization Key shapes satellite synchronization, inspect Figure 62.2 beside Cost: ~$50,000 - $100,000. Together, Synchronization Key and Cost: ~$50,000 - $100,000 frame the satellite synchronization claim: how are satellites synced.

Figure 62.2: How are satellites synced

Read Synchronization Key alongside Cost: ~$50,000 - $100,000 in Figure 62.2; their named relationship makes how are satellites synced concrete. For satellite synchronization, Synchronization Key supplies visible evidence; Cost: ~$50,000 - $100,000 constrains the decision. In Figure 62.2, retain Synchronization Key beside Cost: ~$50,000 - $100,000 so satellite synchronization remains explicit.

How Satellites Stay Synchronized:

Atomic Clocks On Board (Caesium or Rubidium). Cost: ~$100,000 per clock. Accuracy: ~1 nanosecond per day. All satellites share time reference.

But They Aren’t Static?. True! But we know their orbits precisely. Can predict positions quite accurately. Small errors do creep in…

Ground Control Segment:. Dedicated ground stations monitor satellite orbits. Track actual positions vs predicted. Upload corrections to satellites. Must model relativistic effects!

Before deciding how Satellite 1 shapes satellite synchronization, inspect Figure 62.3 beside GPS Satellite Positioning. Together, Satellite 1 and GPS Satellite Positioning frame the satellite synchronization claim: satellite orbit monitoring.

GPS satellites orbit continuously above a receiver. Labels give orbital velocity of about 14,000 km/h and altitude of about 20,200 km. — Figure 62.3: Satellite Orbit Monitoring

Read Satellite 1 alongside GPS Satellite Positioning in Figure 62.3; their named relationship makes satellite orbit monitoring concrete. For satellite synchronization, Satellite 1 supplies visible evidence; GPS Satellite Positioning constrains the decision. In Figure 62.3, retain Satellite 1 beside GPS Satellite Positioning so satellite synchronization remains explicit.

Relativistic Effects:

Special Relativity: Satellite clocks run slower due to velocity (~7 μs/day slower). General Relativity: Satellite clocks run faster due to weaker gravity (~45 μs/day faster). Net Effect: ~38 μs/day faster → must be corrected!

Relativity Effects in GPS

Without relativistic corrections, GPS would accumulate ~10 km of error per day. Here’s why:

Special Relativity (time dilation from velocity): Satellites orbit at $v \approx 3,874$ m/s. Time dilation factor: $\gamma = \frac{1}{\sqrt{1 - \frac{v^2}{c^2}}} \approx 1 + \frac{v^2}{2c^2}$

For GPS: $\frac{v^2}{2c^2} = \frac{(3,874)^2}{2 \times (3 \times 10^8)^2} \approx 8.3 \times 10^{-11}$

Clock runs slower by: $8.3 \times 10^{-11} \times 86,400 \text{ s/day} \approx 7.2$ μs/day

General Relativity (gravitational time dilation): At GPS orbit altitude (20,200 km), gravitational potential is weaker than at Earth’s surface. Clock rate difference: $\frac{\Delta t}{t} = \frac{GM}{c^2} \left(\frac{1}{r_{\text{surface}}} - \frac{1}{r_{\text{orbit}}}\right)$

Where $GM_{\text{Earth}} = 3.986 \times 10^{14}$ m³/s², $r_{\text{surface}} = 6.37 \times 10^6$ m, $r_{\text{orbit}} = 2.66 \times 10^7$ m.

$\frac{\Delta t}{t} \approx 5.3 \times 10^{-10} \Rightarrow 5.3 \times 10^{-10} \times 86,400 \approx 45.9 \text{ μs/day faster}$

Net effect: $45.9 - 7.2 = 38.7$ μs/day clock advancement

Position error if uncorrected: Light travels at $c = 3 \times 10^8$ m/s, so: $\text{Error} = c \times \Delta t = 3 \times 10^8 \times 38.7 \times 10^{-6} \approx 11,600 \text{ m/day}$

GPS solution: Satellite clocks are pre-adjusted to run at 10.22999999543 MHz (instead of exactly 10.23 MHz) to cancel the net +38.7 μs/day drift.

Relativistic Time Dilation

Explore: Change the satellite velocity or altitude to see how relativistic effects change. GPS satellites at 20,200 km altitude traveling at 3,874 m/s experience a net +38.7 μs/day clock advancement, which must be corrected.

Checkpoint: Satellite Timekeeping

You now know:

Satellite atomic clocks and ground control keep the shared time reference usable.
Relativity matters at GPS orbit: about 7 us/day slower from velocity, 45 us/day faster from gravity, and 38.7 us/day net.
Without correction, the timing drift would accumulate about 10 km of position error per day.

62.7 GPS Position Calculation

Before deciding how Sat 1 shapes gps position calculation, inspect Figure 62.4 beside rx. Together, Sat 1 and rx frame the gps position calculation claim: gps position calculation.

Figure 62.4: GPS position calculation

Read Sat 1 alongside rx in Figure 62.4; their named relationship makes gps position calculation concrete. For gps position calculation, Sat 1 supplies visible evidence; rx constrains the decision. In Figure 62.4, retain Sat 1 beside rx so gps position calculation remains explicit.

Position Equations:

For each satellite $i$ :

\rho_i = \sqrt{(x_i - x_r)^2 + (y_i - y_r)^2 + (z_i - z_r)^2} + c \cdot \Delta t + E_i

Where: $\rho_i$ = pseudorange to satellite $i$ (measured). $(x_i, y_i, z_i)$ = satellite $i$ position (known from ephemeris). $(x_r, y_r, z_r)$ = receiver position (unknown). $c$ = speed of light. $\Delta t$ = receiver clock offset (unknown). $E_i$ = error term (atmospheric delays, etc.).

Four Unknowns:

$x_r$ (receiver X position). $y_r$ (receiver Y position). $z_r$ (receiver Z position). $\Delta t$ (clock offset).

Need at least 4 satellites to solve for 4 unknowns!

62.8 Position from Satellite Signals

Scenario: Your GPS receiver picks up signals from 4 satellites. You need to understand how position is derived from raw timing measurements.

Given data (simplified to 2D for clarity):

Satellite	Known Position (km)	Signal Travel Time	Pseudorange (km)
Sat A	(0, 20200)	67.33 ms	20,185.0
Sat B	(14290, 14290)	67.28 ms	20,170.0
Sat C	(-14290, 14290)	67.38 ms	20,200.0
Sat D	(20200, 0)	67.40 ms	20,206.0

Step 1: Convert time to distance

Each pseudorange = speed of light x travel time:

Sat A: 299,792 km/s x 0.06733 s = 20,185.0 km

Step 2: Notice the clock offset

All pseudoranges include the same unknown clock error. If the receiver clock is 50 nanoseconds fast, every pseudorange is 15 meters too long. The fourth satellite lets us solve for this offset.

Step 3: Solve the system of equations

With 4 equations and 4 unknowns (x, y, z, clock offset), the receiver’s least-squares solver finds the position. In practice, modern receivers process signals from 10-12 satellites simultaneously, using the extras to improve accuracy and detect anomalies.

Key insight: Each additional satellite beyond 4 reduces position error by approximately 20-30%. A receiver tracking 8 satellites achieves roughly 2-3 meter accuracy versus 5-10 meters with exactly 4.

62.9 Uber GPS Accuracy in Manhattan

Uber discovered in 2015 that GPS-based pickup locations in Manhattan were consistently wrong by 20-50 meters — enough to place riders on the wrong side of a city block or on a different street entirely. This caused 15-20% of Manhattan pickups to require phone calls between driver and rider, adding an average 4.2 minutes per trip and costing an estimated $50 million annually in driver idle time.

Root cause analysis: Manhattan’s dense skyscraper grid created severe multipath interference. GPS signals bounced off glass and steel facades, arriving at smartphone receivers via indirect paths that added 50-200 nanoseconds of delay — translating to 15-60 meters of position error.

The technical challenge in numbers:

Environment	GPS Accuracy	Pickup Success Rate
Open suburban	3-5 meters	94%
Low-rise urban	8-15 meters	87%
Midtown Manhattan	20-50 meters	72%
Financial District (canyon)	30-80 meters	61%

Uber’s multi-technology solution (2016-2019):

Sensor fusion: Combined GPS with phone accelerometer and gyroscope data. Dead reckoning between GPS fixes reduced error during multipath events.
Map matching: Snapped estimated positions to the road network using Hidden Markov Models. A rider on 5th Avenue would never be placed in the middle of a building.
3D building models: Used Manhattan building height data to predict which satellites would have clear sky views versus multipath interference, weighting satellite signals accordingly.
Wi-Fi fingerprinting: Added Wi-Fi access point signal strengths as supplementary positioning data in areas with dense AP coverage.

Results after implementation:

Manhattan pickup accuracy improved from 25-50m median error to 8-12m
Phone calls for pickup coordination dropped 62%
Average pickup time decreased by 2.8 minutes
Annual savings estimated at $32 million in reduced driver idle time

Lesson for IoT designers: Any IoT application that depends on GPS positioning in urban environments must budget for multipath mitigation. Raw GPS alone is insufficient — sensor fusion, map matching, and supplementary positioning technologies are essential for sub-10-meter accuracy in built-up areas.

62.10 GPS Error Sources

Before deciding how 1.0 m shapes gps error sources, inspect Figure 62.5 beside 3.0 m. Together, 1.0 m and 3.0 m frame the gps error sources claim: gps error sources.

GPS error sources compare ephemeris, clocks, ionosphere, troposphere, multipath and receiver contributions. The table gives 4.0 m total RMS and notes difficult-to-reduce multipath and receiver noise. — Figure 62.5: GPS error sources

Read 1.0 m alongside 3.0 m in Figure 62.5; their named relationship makes gps error sources concrete. For gps error sources, 1.0 m supplies visible evidence; 3.0 m constrains the decision. In Figure 62.5, retain 1.0 m beside 3.0 m so gps error sources remains explicit.

Signal Strength Challenge:

GPS signal transmitted at 20 watts. Travels 20,200 km (GPS orbit altitude). Received power: ~10^-16 watts (incredibly weak!). Various atmospheric effects introduce errors.

Error Source	Typical Error	Mitigation
Ionospheric delay	±5 m	Dual-frequency correction
Tropospheric delay	±0.5 m	Modeling
Satellite clock	±2 m	Ground station corrections
Ephemeris	±2.5 m	Frequent updates
Multipath	±1 m	Antenna design, averaging
Receiver noise	±0.3 m	Better receivers

Checkpoint: Operational Accuracy

You now know:

Four satellites solve the minimum four unknowns; 10-12 satellites let receivers improve and cross-check the solution.
Dense streets can add 50-200 ns of delay and 15-60 m of position error.
A weak 20 W satellite signal arriving from 20,200 km needs correction, filtering, and honest quality metadata.

62.11 Knowledge Check

Quiz: GPS Fundamentals

Interactive Quiz: Match Concepts

Interactive Quiz: Sequence the Steps

Key Takeaway

GPS is an inverted TDoA system where satellites broadcast synchronized time signals and receivers calculate position from pseudoranges. Four satellites are the minimum (3 position unknowns + 1 clock offset), but more satellites improve accuracy through overdetermined solutions. The system’s genius is treating the receiver’s cheap clock offset as a solvable unknown rather than requiring expensive atomic clocks in every device. The biggest practical limitations are multipath (signal reflections in cities) and the complete inability to work indoors due to signal attenuation through building materials.

For Kids: Meet the Sensor Squad!

GPS is like playing Marco Polo with satellites in SPACE!

62.11.1 Messages from Space

“How does my phone know where I am?” asked the LED one day, staring at the blue dot on a map.

Temperature Terry knew the answer. “There are 24 special satellites orbiting Earth, way up in space — about 20,000 kilometers high! Each one is basically shouting ‘I’M HERE and the time is 3:00:00.000000!’”

“But how does that help?” asked Lila.

“Imagine you’re blindfolded in a big park,” said the microcontroller. “Three friends stand in different spots and each one shouts ‘I’m 50 meters from you!’ or ‘I’m 30 meters from you!’ With three distances, there’s only ONE spot where you could be standing!”

“That’s TRILATERATION!” cheered the battery. “GPS works the same way, but instead of friends shouting, it’s satellites sending time signals. Your phone calculates how far each satellite signal traveled by how long it took to arrive.”

“But here’s the tricky part,” said Sammy. “Radio signals travel at the SPEED OF LIGHT — 300,000 kilometers per second! That’s SO fast that if your phone’s clock is off by just ONE MILLIONTH of a second, it’s wrong by 300 meters!”

“That’s why we need a FOURTH satellite!” explained Max. “Three satellites tell us where we are, and the fourth one helps us figure out exactly what time it is. The satellites have super-expensive atomic clocks that cost $100,000 each, but our phones can figure out the right time by using math!”

“So GPS is really about TIME, not just PLACE!” realized Lila.

“Exactly! And the satellites are so far away that their signals are incredibly weak when they reach us. That’s why GPS doesn’t work inside buildings — the signals can’t get through walls and ceilings!”

62.11.2 Key Words for Kids

Word	What It Means
Satellite	A special machine orbiting Earth in space that sends time signals to GPS receivers
Speed of Light	The fastest speed in the universe — 300,000 km per second! GPS signals travel this fast
Atomic Clock	A super-accurate clock on satellites that loses less than 1 second in a MILLION years
Pseudorange	A distance measurement that’s slightly wrong because your phone’s clock isn’t perfect

Concept Relationships

How this chapter connects to other IoT concepts:

Foundation for: GPS Accuracy Enhancement builds on error sources and pseudorange concepts to implement DGPS/RTK corrections. Contrasts with: Indoor Positioning which requires entirely different technologies where satellite signals fail. Atomic clocks: Satellite Synchronization explains why GPS provides an authoritative time source for distributed IoT systems. Multipath: Wireless Fading and Interference explains why signal reflection affects all RF systems, not just GPS. Case study: Urban IoT Challenges Manhattan multipath problem affects all outdoor location services.

62.11.3 Exercise 1: Observe GDOP Changes

Use a satellite tracking app (GPS Test, GPSTest+ for Android):

Record satellite positions and HDOP/GDOP in open field (good sky view)
Walk to urban area between buildings (limited sky view)
Compare satellite count and geometry

What to observe: Open sky shows 8-12 satellites spread across sky, GDOP ≈ 1.5-2.5. Urban canyon shows 4-6 satellites clustered overhead, GDOP ≈ 4-10. Notice how GDOP directly affects reported accuracy (accuracy = UERE × GDOP).

62.11.4 Time to First Fix (TTFF)

Test GPS acquisition speed:

Turn off GPS, wait 10 minutes (ephemeris data expires)
Cold start: Enable GPS in airplane mode (no A-GPS assistance)
Time how long until position fix
Repeat with cellular data enabled (A-GPS active)

What to observe: Cold start takes 30-60 seconds (must download ephemeris from satellites at 50 bits/second). Warm start with A-GPS takes 5-15 seconds (ephemeris downloaded from cellular network at kilobits/second). This demonstrates value of assistance data.

62.11.5 Track Multipath Environments

Use GPS logger app to record tracks in different environments:

Open field: Walk 100-meter straight line, record GPS track
Urban canyon: Walk same distance between tall buildings, record track
Forest: Walk under dense tree canopy, record track
Compare actual distance to GPS-calculated distance

What to observe: Open field track is smooth and accurate (±5m). Urban track has large jumps and zigzags (±20-50m from multipath reflections). Forest track has gaps where signal is lost entirely. This demonstrates environmental impact on GPS performance.

Common Pitfalls

Overbuilt Initial Prototypes

Adding too many features before validating core user needs wastes weeks of effort on a direction that user testing reveals is wrong. IoT projects frequently discover that users want simpler interactions than engineers assumed. Define and test a minimum viable version first, then add complexity only in response to validated user requirements.

Security During Development

Treating security as a phase-2 concern results in architectures (hardcoded credentials, unencrypted channels, no firmware signing) that are expensive to remediate after deployment. Include security requirements in the initial design review, even for prototypes, because prototype patterns become production patterns.

Failure Modes and Recovery

Designing only for the happy path leaves a system that cannot recover gracefully from sensor failures, connectivity outages, or cloud unavailability. Explicitly design and test the behaviour for each failure mode and ensure devices fall back to a safe, locally functional state during outages.

Label the Diagram

62.12 What’s Next

Continue to GPS Accuracy and Enhancement to learn about the GPS error budget, differential GPS corrections, and RTK techniques that achieve centimeter-level accuracy for precision applications.

Previous	Up	Next
Location Awareness Fundamentals	UX Design	GPS Accuracy and Enhancement

Code Challenge

62.13 Continue Your Route

This final part closes the route from GPS Architecture through Code Challenge. Return to GPS Location: Ranging Methods or continue from the ux-design module index.