GNSS Accuracy Decoded: Why Positioning is a Game of Probabilities

GNSS accuracy is not one fixed number; it is a statistical claim wrapped around receiver quality, satellite geometry, signal environment, correction state, antenna setup, coordinate frame, and test method.

Most sensors make accuracy feel simple. A temperature probe might specify a range, a resolution, and a maximum error. A GNSS receiver looks similar on a datasheet, but the number hides more assumptions. A receiver can output latitude and longitude with many decimal places while the real position is still meters away.

That is why the usual sensor checklist behaves differently for GNSS:

• Range: Global. A GNSS receiver can operate almost anywhere with sky view.
• Resolution: Extremely fine. Coordinates can be reported with millimeter-level numeric resolution.
• Accuracy: Variable. Depending on signal quality, correction state, antenna setup, and environment, the error can range from centimeters to dozens of meters.

This contrast, fine numeric resolution with potentially large real-world error, is why GNSS datasheets need statistical reading instead of a simple plus-or-minus interpretation.

The reason is that satellite positioning is a ranging problem. Each fix depends on time measurements from multiple satellites, and each measurement carries noise, atmospheric delay, multipath, receiver uncertainty, and geometry effects. The result is not a single guaranteed point. It is a cloud of possible positions.

This guide explains how to read that cloud. We will separate accuracy from precision, decode CEP, RMS, 2DRMS, and R95, show how DOP changes field results, and then map what changes when a receiver moves from single-point GNSS to centimeter-level RTK positioning.

Accuracy vs Precision in GNSS

Accuracy and precision are often used as if they mean the same thing. In GNSS, mixing them up leads to bad receiver comparisons.

• Accuracy means closeness to the true coordinate. The question is: did the receiver land on the right place?
• Precision means repeatability. The question is: do repeated fixes cluster tightly together?

The Target Analogy

• High precision, low accuracy: All your shots hit the same spot, but that spot is far from the bullseye. In GNSS, this often points to a systematic error.
• Low precision, high accuracy: Your shots scatter around the target, but the average center is close to the bullseye. In GNSS, this usually points to random error.

A receiver can be precise but inaccurate. If the antenna offset is wrong, the base-station coordinate is wrong, or the map layer uses a different datum, every point may repeat neatly while staying shifted from the true location. That is why a beautiful track overlay is not enough proof of absolute accuracy. For the coordinate-frame side of that problem, see Beyond WGS84.

The reverse can also happen. A noisy receiver may scatter around the true coordinate. The average may be close, but each individual fix is too unstable for control, mapping, or repeatable measurement. For robotics, field mapping, and machine guidance, both properties matter: the receiver needs a stable output and the output needs to be tied to the correct coordinate frame.

CEP, RMS, and R95 Explained

Most confusion starts when two datasheets describe accuracy with different confidence metrics. A "1 m" number can mean median performance, root-mean-square spread, or a 95% containment radius. Those are not interchangeable claims.

The practical comparison table is:

Under a simplified two-dimensional Gaussian assumption, CEP, DRMS, and R95 can be converted with stable multipliers. 2DRMS is a separate conservative shorthand, roughly twice DRMS, and should not be treated as identical to every vendor's R95 definition. The exact multiplier depends on the error model, but the lesson is stable: a CEP number always looks smaller than a high-confidence containment number for the same receiver.

The Conversion Cheat Sheet

Engineers often need to compare a datasheet using CEP against one using RMS or a 95% statement. Assuming a standard two-dimensional error distribution, these multipliers give a practical conversion starting point:

• Scenario: A module claims a single-point positioning accuracy of 1.2 m CEP.
• To DRMS: Multiply by 1.19 -> 1.43 m DRMS.
• To R95: Multiply by 2.08 -> 2.5 m R95.

A fair datasheet comparison therefore starts by asking which confidence level each vendor used. Without that step, the smaller number may simply be the lower-confidence claim.

Why Dice Explain GNSS Accuracy

Why can those multipliers work at all? Because many GNSS accuracy calculations treat the final error as approximately Gaussian. That assumption is not magic. It comes from adding many smaller error terms together.

The Dice Experiment

Imagine rolling one die. The result is uniform: 1 through 6 have equal probability. That is not Gaussian. Now roll three dice, record the sum, and repeat the experiment 100,000 times. The histogram starts to form a bell curve because there are many more ways to make middle values than edge values.

function random_die() {
    return floor(random(1, 6));
}

for (i = 0; i < 100000; i++) {
    s = random_die() + random_die() + random_die();
    histogram[s] += 1;
}

The Central Limit Theorem

The Central Limit Theorem explains why this matters. A GNSS position error is not one clean error source. It is the sum of satellite clock residuals, orbital uncertainty, ionospheric delay, tropospheric delay, signal effects, multipath, receiver noise, antenna effects, and local geometry.

Individual errors may not be Gaussian. Their sum often behaves close enough to a Gaussian distribution that CEP, DRMS, R95, and similar statistical tools become useful. The assumption is never perfect, but it is practical when the test environment and confidence metric are stated clearly.

How to Read a GNSS Accuracy Claim

An accuracy line is only useful when the footnotes are visible. Before treating a number as a requirement, check these conditions:

This is where a GNSS accuracy article connects to the physical error model. Metrics describe the shape of the result, while the GNSS error budget explains where the result came from: satellite clock, ephemeris, ionosphere, troposphere, multipath, receiver noise, and geometry.

Why DOP Changes Position Error

DOP stands for Dilution of Precision. It is not a separate error source like multipath or atmospheric delay. It is a geometry multiplier. When satellites are spread across the sky, the receiver can separate timing errors into a cleaner position solution. When satellites cluster in one part of the sky, the same ranging error expands into a larger position error.

• HDOP describes the horizontal geometry effect on latitude and longitude.
• VDOP describes the vertical geometry effect on altitude.

The simplified relationship is:

The Rule of Thumb

This explains why satellite count alone is a weak quality indicator. Twelve satellites with poor geometry can perform worse than eight satellites spread across a better sky.

Vertical accuracy is usually weaker than horizontal accuracy because satellites are above the receiver, not below it. The geometry has less vertical leverage, so altitude error often grows faster than horizontal error under the same ranging conditions.

In open sky, HDOP may sit around 0.7. In an urban canyon or beside tall structures, HDOP can rise toward 4.0, and horizontal accuracy can degrade roughly in proportion even before multipath is considered. Near buildings, tree lines, slopes, machinery, or greenhouse structures, HDOP can climb while reflected signals increase at the same time. The receiver may still produce a coordinate, but the probability cloud is larger and less symmetric.

What RTK Changes About GNSS Accuracy

RTK does not make the probability problem disappear. It changes which error terms remain dominant.

With ordinary single-point GNSS, the rover depends on broadcast satellite data, atmospheric models, its antenna environment, and its receiver design. With RTK, a nearby reference receiver observes many of the same satellite-side and atmospheric errors. The rover uses correction data to remove much of the shared error and then solves carrier-phase ambiguity for a centimeter-level fixed solution.

That is why an RTK receiver can report a much tighter horizontal result than a standalone receiver under the same sky. It is also why RTK is sensitive to correction age, baseline length, cycle slips, multipath, and antenna installation. A fixed solution is a strong state, but it is not magic. The RTK Trick explains how double differences and integer ambiguity resolution produce that state—and why a Fixed solution can still be wrong.

The distinction matters in real applications. For RTK GPS for robotics and outdoor robot navigation, the receiver may need centimeter-level global anchoring, but the control stack still has to handle state changes, local obstruction, heading behavior, and sensor fusion. For mapping work, the receiver may be fixed while the final boundary still depends on coordinate frame, field workflow, and the map layer.

Testing GNSS Accuracy in the Field

Reading the datasheet is the first step. Testing the receiver in the environment where it will actually work is the second.

The Golden Rule of Testing

The golden rule is simple: the reference system must be better than the device under test. If you are evaluating a meter-level receiver, a surveyed control point or a higher-grade RTK system is enough. If you are validating centimeter-level behavior, the reference coordinate, antenna mount, correction source, and logging method all need tighter control.

A practical field test should log:

• Timestamp, latitude, longitude, altitude, and fix mode.
• Satellite count, HDOP, correction age, and RTK float/fixed state.
• Antenna type, antenna height, mount position, and surrounding obstructions.
• Reference coordinate, coordinate frame, and map layer or survey control source.
• Whether the test is static, dynamic, repeated-loop, or revisit-based.

For agriculture and field operations, the most expensive failure is often not a single noisy point. It is a consistent point in the wrong place. A field boundary can look repeatable while acreage, datum, base-station coordinates, or sampling workflow still create the wrong operational result. That is the failure mode behind field mapping accuracy.

No Budget for High-End Gear?

If you do not have a survey control point, repeated tests still help. Park the receiver in one place and log the point cloud. Drive the same route several times and compare overlays. Revisit the same physical target at different times of day. These tests will not prove absolute accuracy, but they reveal precision, drift, multipath sensitivity, and correction-state stability.

Conclusion

GNSS accuracy is a probability claim shaped by metric choice, environment, correction state, antenna setup, geometry, and reference coordinates. A single number such as 1.2 m, 30 cm, or 1 cm is only useful after you know whether it is CEP, RMS, R95, single-point, float, fixed, static, dynamic, open sky, or field tested.

Zero Jiang

Founder, Kalmix

Dedicated to making high-precision GNSS positioning accessible and reliable for global developers building autonomous systems and robust RTK hardware.