geoprimsField-grade geospatial math

RTK and PPK precision budget

The precision a receiver's a mm + b ppm specification promises over your baseline, horizontal and vertical, scaled to a confidence level and compared with your target.

A published result changed on 2026-10-19: The RTK accuracy calculator's 95% horizontal factor is now the NSSDA's 2.4477 (√χ²₂,0.95, FGDC-STD-007.3-1998) instead of a rounded 2.448, matching… Changelog

48mm

The spec gives 48 mm across at this range.

Vertical precision
Provenance
Computed by
survey.gnss.rtk-budget 1.2.0, core 0.1.0
Model
Precision = a + b × 10⁻⁶ × baseline, the way receiver specifications state it (1σ, ideal conditions); at 95% the horizontal value is multiplied by 2.4477 (the two-dimensional factor) and the vertical by 1.96 (FGDC-STD-007.3-1998, Appendix 3-A)
Accuracy
Manufacturer specifications assume open sky, good geometry, and no multipath; field results are often worse. A root-sum-square of the two terms would read lower
Notes
None
Cites
Henning, W., NOAA National Geodetic Survey, User Guidelines for Single Base Real Time GNSS Positioning; Tersus GNSS Inc., How does Tersus handle long-range single baseline RTK positioning?; Federal Geographic Data Committee, Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy

Something look off?

Your values

Showing an example. Change anything.
More options 2
GNSS receiver profiles

Loading…

Run many at once from a CSV

Loading…

How we got thisFormula, worked example, sources, and proof

Model: Precision = a + b × 10⁻⁶ × baseline, the way receiver specifications state it (1σ, ideal conditions); at 95% the horizontal value is multiplied by 2.4477 (the two-dimensional factor) and the vertical by 1.96 (FGDC-STD-007.3-1998, Appendix 3-A)

Show your work

  1. Distance term

    b × 10⁻⁶ × baseline

    1 × 10⁻⁶ × 40,000 m = 40 mm

  2. Horizontal precision

    (a + distance term) × confidence factor

    (8 + 40) mm × 1 = 48 mm

The same steps an agent gets from the MCP server with explain: true.

Accuracy: Manufacturer specifications assume open sky, good geometry, and no multipath; field results are often worse. A root-sum-square of the two terms would read lower

When to use this: Use this when you need to know if an RTK or PPK setup can meet a job's tolerance before you go to the field. Enter the receiver's a mm plus b ppm spec, the baseline to the base or network, and your target. It returns horizontal and, if given, vertical precision as stated or scaled from one sigma to 95%, and says whether you are within, near, or beyond the target.

Limitations: The answer is what the maker's spec promises under open sky with good satellite geometry and no multipath. Real work under trees, near buildings, or with poor geometry is often worse. The two terms are added straight, as specs state them. The 95% option assumes the entered terms are one-sigma values; do not apply it to a specification already stated as RMS, 95%, or another confidence basis. The tool does not model antenna height errors, setup errors, or the accuracy of the base coordinates.

Worked example: Tersus Oscar over a 40 km baseline. Source: Tersus GNSS technical blog (April 6, 2023): its Oscar receiver example gives 48 mm horizontal and 55 mm vertical over 40 km. It is golden test vector v006, and every build checks the tool still gives its answer within its tolerance.

You enter

Baseline
40 km
Horizontal a
8 mm
Horizontal b
1
Vertical a
15 mm
Vertical b
1

You get

Horizontal precision
48 mm
Vertical precision
55 mm

Review: Not yet independently reviewed by a licensed surveyor.

Last verified: 2026-09-22, when a maintainer last confirmed this tool's sources at the issuer. See the sources ledger.

Status: version 1.2.0, core 0.1.0. See this tool in the verification report.

Changes

Checked against: 25 golden test vectors (download the test vectors, each with its source and tolerance). See how results are checked and every source.

Constants this tool assumes

Values you do not enter, and where each comes from.

Two-dimensional 95% factor
2.4477 — National Standard for Spatial Data Accuracy
One-dimensional 95% factor
1.9600 — National Standard for Spatial Data Accuracy

Sources

Terms

PPK: post-processed kinematic
Like RTK, but the corrections are applied after the survey, from logged base and rover data. Source: User Guidelines for Single Base Real Time GNSS Positioning
RTK: real-time kinematic
GNSS positioning corrected live from a base station or network, good to about a centimeter plus about a millimeter per kilometer from the base. Source: User Guidelines for Single Base Real Time GNSS Positioning