How RTK differs from standalone GPS
Real-time kinematic positioning uses carrier-phase measurements and reference information to estimate a rover’s position relative to a reference. Under suitable conditions, it can deliver much finer positioning than an ordinary standalone code-based solution. However, “RTK fixed” is a solution state—not a guarantee that a map, landing point or survey deliverable is correct. The reference coordinates, antenna installation, correction quality, environment and complete processing workflow still matter. [S05]
What is being compared?
“GPS” is often used loosely for a receiver that may also use other satellite constellations. “RTK” describes a positioning technique rather than an additional constellation. A useful comparison identifies the actual signals and processing modes instead of placing two marketing labels in opposing columns.
A standalone receiver estimates position without a live local correction service. An RTK rover combines its observations with information from a reference station or network. This adds another dependency: the correction path. Losing that path does not necessarily mean every navigation function disappears, but the solution may change. The manufacturer’s documented transitions are more useful than a generic claim that the system either “has RTK” or does not. [S05]
| Question | Standalone positioning | RTK workflow |
|---|---|---|
| What supports the solution? | Satellite measurements and receiver processing | Satellite measurements plus reference information |
| Is an external correction path required? | Not for ordinary standalone operation | Normally required for live RTK corrections |
| What must be checked? | Quality, installation and intended use | Those checks plus reference and correction integrity |
| Is the map automatically correct? | No | No |
Precision and correctness are different
Imagine a reference station whose entered coordinates are wrong by 1.5 metres. A rover may then repeatedly report positions with excellent internal consistency while carrying a systematic offset. Repeating the measurement does not necessarily expose the original coordinate mistake.
This hypothetical example explains why repeatability is not enough. A system can be precise around the wrong answer. For a mapping job, an independent check point can test the end-to-end result in a way that the receiver’s own status indicator cannot.
The same reasoning applies to antenna height. A coordinate for an antenna phase centre is not automatically a coordinate for the camera, landing gear or ground surface. Those relationships need a defined reference frame and a documented measurement method.
What should a buyer ask?
THL’s suggested comparison starts with the task. Does the user need repeatable navigation, accurate survey products, precise geotagging or a combination? Then identify which part of the system claims to meet that need.
Ask how corrections are obtained, how their age is displayed, what happens when they stop, and whether the full solution status is available in exported logs. Ask how the reference position is established and how antenna offsets are represented. Finally, request an example validation workflow using independent evidence rather than only screenshots of a “fixed” indicator.
These questions make product advice useful without inventing a universal accuracy ranking. GPS.gov specifically warns that user accuracy depends on receiver characteristics and surrounding conditions as well as the transmitted service. [S04]
A practical acceptance example
Suppose a team needs repeatable image positions for a small site. A proposed demonstration could use several independently established check locations, repeated flights under a defined configuration, and a record of correction continuity. The team would agree its acceptance tolerances before collecting data.
The report should distinguish horizontal from vertical differences, state the coordinate reference system, and describe whether checks were used in processing or kept independent. Reusing processing control points as the only proof of accuracy weakens the independence of the check.
This is a suggested evidence structure, not a survey standard or a substitute for a qualified surveyor’s requirements. Its value is that it turns “centimetre accuracy” into a question that can actually be tested.
How the calculator fits
An almanac-based visibility tool estimates approximate satellite geometry. It can help examine the sky view at a planned time, but it cannot determine whether carrier ambiguities will resolve, whether corrections are trustworthy or whether a survey will meet its specification. Satellite count should not be converted into a guaranteed error in metres.
Use it with How Many Satellites Does a Drone Need? For the aircraft’s response to degraded positioning, read Understanding Drone Return-to-Home Systems.
The purchasing decision
Choose the positioning workflow that supplies the evidence your task needs. RTK can be valuable, but the complete chain—from reference coordinates through correction transport to final output—deserves as much attention as the receiver label. The strongest comparison is not “RTK beats GPS”; it is “this tested workflow meets this stated requirement under these conditions”.
Sources and further reading
S04 · GPS.gov — GPS accuracy
S05 · ESA Navipedia — Real Time Kinematics
Tools and related readingEngineering tools: UAS Engineering Calculators.
Related reading: How Many Satellites Does a Drone Need?; Understanding Drone Return-to-Home Systems; What Is a Test Card?.