How Does RTK GNSS Work? Complete Technical Guide 2026
Every modern infrastructure project, topographical survey, and cadastral mapping operation relies on precise spatial data. However, standard Global Navigation Satellite Systems (GNSS) — the technology powering smartphones and car navigation — only provide positioning accurate to a few metres. This variance is entirely inadequate for civil engineering, property boundary demarcation, or machine control, where a discrepancy of a few centimetres can result in catastrophic misalignment or legal disputes.
To bridge the massive gap between metre-level estimation and millimetre-level certainty, the surveying industry relies on RTK — Real-Time Kinematic positioning. By employing advanced carrier-phase tracking and receiving continuous real-time correction data, RTK GNSS receivers eliminate the atmospheric and timing errors that plague standard GPS, achieving highly reliable ±8 mm precision.
Understanding the fundamental mechanics behind RTK — including how signals are tracked, how ambiguities are mathematically resolved, and how correction streams are delivered via CORS or local base stations — is essential for any surveyor, civil engineer, or procurement manager stepping into the field. This comprehensive technical guide breaks down the science, the hardware, and the operational logic that power modern GNSS RTK systems.
1. What Is RTK GNSS?
Real-Time Kinematic (RTK) is a highly sophisticated differential positioning technique used to enhance the precision of position data derived from satellite-based positioning systems (such as GPS, GLONASS, Galileo, BeiDou, QZSS, and NavIC).
STANDARD GNSS (PSEUDO-RANGE):
Standard receivers calculate position by measuring the time it takes for a signal to travel from the satellite to the receiver. Because the satellite's exact position is known, calculating the travel time multiplied by the speed of light yields the distance (pseudo-range). However, as these signals travel through the Earth's ionosphere and troposphere, they are inevitably delayed and distorted. These atmospheric delays, combined with satellite clock errors and orbital deviations, result in a standard accuracy of 2 to 5 metres.
RTK GNSS (CARRIER-PHASE):
Instead of merely timing the signal code, an RTK receiver examines the carrier wave itself. The carrier wave operates at a much higher frequency (with a wavelength of roughly 19 centimetres for the L1 band) than the pseudo-random code. By measuring the exact phase of this 19-centimetre wave as it reaches the antenna, the receiver can determine the distance to a fraction of a wavelength. However, the receiver does not inherently know exactly how many full wave cycles exist between the satellite and the antenna — a mathematical puzzle known as the "integer ambiguity". RTK relies on a secondary, stationary correction source to help resolve this ambiguity instantly.
2. How RTK Calculates Position
The transformation from raw satellite signals to a highly accurate project coordinate happens in a fraction of a second. Here is the step-by-step mechanical process occurring inside an RTK receiver:
The roving RTK receiver tracks signals from multiple satellite constellations. Modern multi-band receivers, such as the APEKS AP80 Pro and AP60 Vision, utilise 1408 channels to simultaneously track GPS, GLONASS, BeiDou, Galileo, QZSS, and NavIC. Tracking multiple constellations ensures adequate geometry even in obstructed environments.
The receiver begins observing the carrier waves from all visible satellites. It measures the fractional phase of the wave as it hits the antenna, establishing an incredibly precise, yet initially incomplete, distance measurement due to the unknown number of full wave cycles.
Simultaneously, a stationary base station or CORS network — which is positioned on a strictly known, highly accurate coordinate — observes the exact same satellites. Because the base knows its exact true location, it instantly calculates the atmospheric delay and clock errors affecting the signals. It transmits these precise error corrections to your rover via internet (NTRIP) or radio.
The rover's internal RTK engine compares its own raw carrier-phase measurements against the pristine correction data streaming from the base. Applying advanced algorithms, the receiver calculates the exact integer number of full wavelengths between the satellite and the antenna. Once this mathematical ambiguity is successfully resolved, the receiver locks the solution.
With the ambiguity resolved, the receiver transitions into a "Fixed" state. It continuously outputs coordinates accurate to ±8 mm relative to the base station. The data collector software then immediately applies local geoid models and UTM projections to map the point to your project drawing.
3. Single, Float, and Fixed: The Three Solution States
When operating an RTK receiver, the surveyor must constantly monitor the receiver's solution state on their data collector screen. Not all GNSS coordinates are equal. You must understand the three distinct mathematical states the receiver moves through to guarantee your survey is legally and technically sound.
| Solution State | Ambiguity Status | Typical Accuracy | What It Means for Surveying |
|---|---|---|---|
| Single (Autonomous) | Unresolved | 1 to 5 metres | The rover is tracking satellites but is receiving NO correction data from a CORS or base. Unsuitable for any precise surveying. |
| Float | Calculating / Unresolved | ±300 to 1000 mm | The rover is receiving correction data, but the RTK engine has not yet mathematically locked onto the exact integer of wavelengths. Do not record topographic points in this state. |
| Fixed | Resolved | ±8 to 15 mm | The integer ambiguity is fully resolved. The receiver has locked the carrier phase. This is the only state acceptable for high-precision engineering, setting-out, and cadastral work. |
4. CORS and NTRIP: How Corrections Are Delivered
For an RTK rover to achieve a Fixed solution, it must receive continuous data. The modern standard for delivering this data relies on extensive, stationary infrastructure rather than surveyor-owned base stations.
WHAT IS CORS?
A Continuously Operating Reference Station (CORS) network is a vast web of permanent, high-grade GNSS base stations installed by governments or private entities across a state or country. These stations monitor satellites 24/7. When your rover connects to the network, the central server calculates a Virtual Reference Station (VRS) near your exact location and sends customised correction data tailored to your specific atmospheric conditions.
WHAT IS NTRIP?
NTRIP (Networked Transport of RTCM via Internet Protocol) is the digital delivery mechanism. Rather than relying on crackly, line-of-sight radio waves, NTRIP streams the correction data over the standard cellular internet. APEKS models like the AP10 and AP60 Vision feature built-in 4G LTE modems. By simply inserting a local data SIM card and entering the server IP, Port, Username, and Password, the receiver dials into the CORS network and receives real-time corrections seamlessly.
5. Local Base Station: When CORS Is Not Available
While CORS networks are incredibly efficient, they possess two critical vulnerabilities: they require active mobile cellular coverage, and they require a paid network subscription. When operating in remote mining sectors, deep forestry, or regions with underdeveloped infrastructure, CORS via NTRIP becomes impossible.
THE BASE AND ROVER SETUP:
In the absence of a network, surveyors must deploy their own physical base station. You establish a stationary receiver (the Base) over a known, reliable control monument. The Base tracks the satellites, calculates the localised atmospheric error, and transmits these corrections directly to your roving receiver via internal UHF radio or Long Range (LoRa) transmission.
HARDWARE CONSIDERATIONS:
Standard internal UHF radios typically offer a range of 2 to 5 kilometres depending on topography. For remote, heavy-duty projects requiring vast coverage without moving the base, surveyors deploy external high-power radios. The APEKS MAX5 acts as a dedicated 5W LoRa Base Station, pushing clean, reliable correction signals up to 15 kilometres across rugged terrain without relying on a single cell tower.
6. What Affects RTK Accuracy
Even when your receiver reports a "Fixed" state, several environmental and systemic factors dictate the absolute precision of your gathered coordinates.
- Baseline Length: In RTK, the distance between your rover and the correction source (the base station or nearest CORS mast) is the baseline. Atmospheric conditions degrade as distance increases. For UHF base stations, accuracy generally drops by 1 ppm (part per million) per kilometre. For CORS networks, exceeding a 50 km baseline introduces substantial risk of vertical error.
- Differential Age: This represents the latency (in seconds) between when the base records an error and when your rover applies the correction. A healthy differential age must stay below 3 seconds. If it spikes to 5 or 10 seconds due to poor 4G internet, accuracy heavily degrades.
- Multipath Interference: GNSS signals bounce off sheer building facades, dense wet tree canopies, and large bodies of water before hitting the antenna. This "multipath" confuses the receiver. Modern receivers use advanced algorithms to reject bounced signals, but dense urban canyons remain challenging.
- Pole Tilt: Historically, holding the survey pole perfectly plumb using the physical spirit bubble was mandatory; a slight tilt introduced centimetres of error. Today, models like the APEKS AP40 Laser+ and AP80 Pro utilise a calibration-free 120° IMU (Inertial Measurement Unit). This sophisticated sensor measures the exact angle of the pole and mathematically compensates for the tilt in real time, allowing surveyors to capture accurate points while the pole is slanted.
7. Common RTK Problems and Fixes
Cause: The RTK engine cannot resolve the integer ambiguity. This is almost always caused by severe multipath interference (surveying directly against a tall building or under dense tree canopy), poor satellite geometry, or a baseline that is exceptionally long.
Fix: Move the rover into a clear, open sky view and allow it to initialize and gain a Fixed solution first. Once Fixed, slowly walk back into the challenging environment. If working off a CORS network, verify that your distance to the nearest physical reference station has not exceeded 50 to 70 km.
Cause: The rover has entirely lost its stream of correction data. The mathematical link is broken.
Fix: If using a CORS network, check the 4G signal strength on your data collector or receiver. You likely walked into a cellular dead zone, or your NTRIP subscription has expired. If using a local UHF base, you have likely walked behind a large topographic obstruction (like a hill or dense forest block) that is completely blocking the line-of-sight radio transmission. Elevate the base station antenna.
Cause: This indicates an issue with data latency or hardware setup. A high differential age means the corrections are arriving too late. Alternatively, the IMU tilt compensation may be improperly handling an extreme magnetic environment, or the datum/geoid model selected in the software is incorrect.
Fix: Check the "Differential Age" metric in your software; if it is bouncing between 5 and 10 seconds, your cellular internet connection is too poor to sustain precision. If using IMU, ensure you have adequately walked with the pole to initialise the sensor, and keep the pole tip firmly planted. Finally, strictly verify that the correct local coordinate projection and geoid model are active.
FAQ
Does RTK require an internet connection to work?
What is the difference between PPK and RTK?
Why does my receiver track 1408 channels?
How far can a rover be from a CORS station?
What does a 120-degree IMU do for RTK surveying?
1408 CHANNELS. FIXED IN 30 SECONDS. EVERY APEKS MODEL.
APEKS RTK receivers track 1408 channels across 6 constellations with calibration-free 120° IMU as standard. Built-in 4G for direct CORS connection. No geo-fence restrictions.
View APEKS RTK Receivers →References
- ISO 17123-8:2015 — Optics and optical instruments — Field procedures for testing geodetic and surveying instruments — Part 8: GNSS field measurement systems in real-time kinematic (RTK)
- RTCM Standard 10403.3 — Differential GNSS Services
- APEKS AP80 Pro Technical Datasheet, 2026
- APEKS AP60 Vision Technical Datasheet, 2026
- APEKS AP40 Laser+ Technical Datasheet, 2026
- APEKS AP10 Technical Datasheet, 2026
- APEKS MAX5 Base Station Datasheet, 2026