#GPS#satellite#trilateration#technology#GNSS

How GPS Actually Works: Satellites, Signals, and Trilateration

A clear explanation of how GPS determines your position: the satellite constellation, radio signals traveling at light speed, atomic clocks, relativity corrections, and why you need at least four satellites.

by 8 min readLast reviewed

Your phone can tell you where you are within a few meters, anywhere on Earth, using satellites about 20,000 kilometers overhead. The core idea is simple: measure how long radio signals take to arrive, turn those times into distances, and let geometry do the rest. This guide works through that idea with real numbers, then explains why a fix is sometimes off and how it gets corrected.

I build ground control software for drones, so these numbers are part of my daily work: every waypoint and photo position in a flight depends on them.

The Constellation

GPS is operated by the US Space Force. According to GPS.gov, its satellites orbit at about 20,200 km, circle the Earth twice a day, and are arranged in six orbital planes. The government commits to at least 24 operational satellites 95% of the time and has flown around 31 for over a decade, so that at least four are visible from virtually anywhere.

Each satellite continuously broadcasts its own orbital position (ephemeris) and timing information kept by onboard atomic clocks.

Step 1: Turning Time Into Distance

Radio signals travel at the speed of light, 299,792,458 m/s:

distance = (time received − time sent) × speed of light

Worked numbers, computed from the speed of light and the 20,200 km orbit:

SituationValue
Travel time from a satellite directly overhead≈ 67.4 ms
Travel time from a satellite on the horizon (≈ 25,800 km away)≈ 86.0 ms
Range error from a 1 microsecond timing error≈ 300 m
Range error from a 1 nanosecond timing error≈ 30 cm

A phone's quartz clock is nowhere near nanosecond-accurate, so its raw measurements could be off by kilometers. Timing is the whole game.

Step 2: Trilateration

Knowing your distance from one satellite places you somewhere on a sphere around it. A second satellite narrows that to a circle; a third reduces it to two points, one of which is usually far out in space and can be discarded.

A flat, two-dimensional version makes this concrete. A beacon at (0, 0) says you are 5 units away, and a beacon at (8, 0) also says 5. The two circles cross at (4, 3) and (4, −3). A third beacon at (4, 10) measures 7 units, which picks (4, 3), because (4, −3) would be 13 units away. GPS does the same in three dimensions.

Why Four Satellites, Not Three?

Because your receiver has no atomic clock. Its clock error, the clock bias, adds the same unknown offset to every distance it measures. These biased distances are called pseudoranges.

So the receiver solves for four unknowns: three position coordinates plus its clock bias. Four satellites give four equations; every extra satellite helps average down errors.

To check this, I ran a small Python simulation: a receiver on the Earth's surface, satellites at 20,200 km, and a deliberate 1 ms clock error, which adds about 300 km to every pseudorange. Solving the four-unknown system recovered both the position (to well under a millimeter, since the simulation has no other noise) and the 1 ms bias, with exactly four satellites and with six.

A side effect: once the clock bias is solved, the receiver knows the time very precisely. GPS.gov states that GPS delivers UTC with ≤ 30 nanoseconds time-transfer accuracy (95%) for a specialized fixed timing receiver, which is why many networks use GPS for time.

Einstein in Your Pocket

GPS must also correct for relativity. Satellite speed slows their clocks (special relativity), while weaker gravity at altitude speeds them up (general relativity). The net effect is roughly 38 microseconds per day fast. At 300 m per microsecond, that would be more than 10 km of range error per day if it were not compensated.

What Degrades the Fix

GPS.gov separates the accuracy of the signal in space from the accuracy of your device's position:

  • Satellite orbit and clock errors. The commitment is a global average user range error (URE) of ≤ 2.0 m (95%); GPS.gov reports a measured ≤ 0.643 m on April 20, 2021. URE is a ranging error, not a position error.
  • Ionosphere and troposphere. The atmosphere slows and bends signals. Ionospheric delay depends on frequency, so dual-frequency receivers can largely remove it (NOAA NGS). Low satellites near the horizon pass through the most atmosphere and are the noisiest.
  • Multipath. Signals reflected off buildings or water arrive late. NOAA notes multipath can cause height errors over 2 dm even with survey-grade RTK equipment.
  • Blockage. Buildings, bridges, trees and indoor use are, per GPS.gov, among the most common causes of a wrong position.

Overall, the GPS performance standard commits to a global average of ≤ 8 m horizontal and ≤ 13 m vertical (95%). These are conservative commitments; GPS.gov notes smartphones are typically accurate to about 4.9 m under open sky. More practical detail is in our guide to GPS accuracy factors.

Dilution of Precision (DOP)

The same range errors produce small or large position errors depending on where the satellites are in the sky. NOAA NGS describes DOP as the ratio of positioning accuracy to measurement accuracy: range errors get multiplied by it. It comes as HDOP (horizontal), VDOP (vertical), PDOP (3D, where PDOP² = HDOP² + VDOP²) and TDOP (time).

I computed DOP for two sky layouts:

Sky layoutHDOPVDOPPDOP
7 satellites spread around the sky, one overhead0.981.461.76
6 satellites bunched in one quarter of the sky3.432.604.30

With good geometry, a 3 m range error becomes about 3 m horizontally; bunched up, it becomes about 10 m. That is why a fix in a narrow street, with only a strip of sky visible, is worse than one in an open field.

Why Vertical Error Is Larger

In the well-spread layout, VDOP was still larger than HDOP. That is normal. Horizontally, satellites surround you on all sides, so their errors partly cancel. Vertically, every usable satellite is above you; the Earth blocks everything below the horizon. The official figures reflect this: 13 m vertical versus 8 m horizontal, and NOAA's best RTK accuracy class lists 2–4 cm vertical versus 1–2 cm horizontal.

I have seen this myself when operating drones: GPS altitude did not match the actual height. There is also a second cause, since GPS heights are measured from an ellipsoid, not sea level. Both are covered in why GPS altitude is inaccurate.

How Phones Get a Fix Quickly (A-GPS)

A standalone receiver starting cold must find which satellites are up and download their orbit data from the slow satellite broadcast. Phones use Assisted GPS (A-GPS): the network supplies orbit data, approximate time and a rough location (from cell towers or Wi-Fi), so the chip knows where to look. This speeds up the first fix; the position itself still comes from satellite ranging. Phones also use several constellations at once (GPS, GLONASS, Galileo and BeiDou), meaning more satellites and usually better DOP.

Corrections: SBAS, RTK and PPK

All correction systems share one trick: a receiver at a precisely known location measures the errors, and that information fixes your measurements.

  • SBAS. The FAA's WAAS uses surveyed reference stations across North America; master stations generate a correction message every second, broadcast via geostationary satellites. The FAA says GPS/WAAS receivers reach a few meters of accuracy and are warned within six seconds of hazardously misleading information. Europe's EGNOS and India's GAGAN are similar.
  • RTK (real-time kinematic). A nearby base station streams its measurements to the rover, which uses the signal's much finer carrier phase. NOAA NGS describes relative accuracy on the order of a centimeter.
  • PPK (post-processed kinematic). Same principle, but base and rover data are logged and combined afterwards, so no live link is needed.

In my drone work, position errors that standalone GPS could not fix were resolved with RTK and PPK. RTK fits when you need precision during the flight; PPK when you only need it in the data afterwards.

From Signal to Coordinates

The output is latitude, longitude and height, which can be written in several coordinate formats or projected into UTM. New to the numbers? Start with what a GPS coordinate is.

See it in action: open My Location to view your device's current fix and reported accuracy, or use our GPS coordinates finder to read coordinates anywhere on the map.

Sources

Related Posts

#GPS#GLONASS#Galileo

GPS vs GLONASS vs Galileo vs BeiDou: The Four Global Navigation Systems Compared

GPS is just one of four global satellite navigation systems. Compare GPS, GLONASS, Galileo, and BeiDou (orbits, satellite counts, civil signals), plus QZSS, NavIC, and correction methods like SBAS, RTK, PPK, and PPP.

9 min read
Read More
#GPS#accuracy#satellite

How Accurate Is GPS? Real Numbers: 5 m on Phones, 1 cm with RTK

How accurate is GPS? Typically about 5 meters on smartphones — down to centimeters with RTK. See accuracy by device type and the factors that degrade it, with practical tips.

13 min read
Read More
#GPS#altitude#elevation

Why GPS Altitude Is So Inaccurate (and What the Numbers Actually Mean)

GPS vertical error is larger than horizontal error, and the height your device shows may be measured from an ellipsoid that sits tens of meters away from sea level. Here are the geometry, the geoid, worked Seoul and New York examples, and a practical checklist.

8 min read
Read More