Keeping Survey Work Moving When RTK Corrections Drop starts with identifying what failed: the connection carrying corrections, the correction feed, or the satellite measurements themselves. Before sending a crew to a remote property or construction site, ask for a plan that separates those problems. Bringing extra equipment is useful only if it addresses the actual interruption.
GNSS, short for Global Navigation Satellite System, covers satellite positioning systems including GPS. RTK, or real-time kinematic positioning, uses corrections from a known reference point to improve positioning during fieldwork. Those corrections must reach the moving field receiver, called the rover, through a data connection.
Three problems that need different responses
Cellular service disappears
If cellular service carries the corrections, losing that connection interrupts delivery. Radio offers another delivery path: CHCNAV identifies radio links as an option for construction sites and places without cellular coverage.
Ask whether the crew can use a local base station—a reference receiver—and send corrections by radio instead. Confirm the equipment and proposed setup before departure. A fallback should be something the crew has prepared to use, not simply an option mentioned when the connection fails.
The connection exists, but corrections do not arrive
A connected device is not the same thing as a working correction stream. RTK depends on receiving the correction data, not merely having cellular service.
The field plan should therefore ask two separate questions: Is the communications connection working, and are usable corrections reaching the rover? Also ask whether the proposed backup depends on the same correction feed. If it does, do not count it as an independent alternative to that feed.
Satellite reception is the problem
GNSS positioning still depends on satellite measurements. One reception problem is multipath: signals reflect off buildings, terrain, or nearby structures and reach the antenna indirectly, degrading the calculated position.
Do not assume that switching from cellular to radio resolves obstructed or reflected satellite signals. That changes the correction delivery path, not the satellite observations. Likewise, offline processing should not be promised as a cure for poor reception. Emlid describes its connectivity-free workflow in clear-sky conditions, not as guaranteed recovery at every difficult location.
Keeping Survey Work Moving When RTK Corrections Drop
Build the backup plan around one distinction: which tasks need positioning results immediately, and which can wait until the recorded measurements are processed afterward?
Prepare a live alternative
For work that needs real-time positioning, discuss a local-base radio setup with the survey lead. Useful questions include:
- What known reference point will support the base?
- Is the proposed radio setup suitable for the planned work?
- How will the crew check the alternative setup before relying on its results?
- Who decides whether to change methods or pause the affected task?
These are planning questions, not universal technical specifications or state licensing requirements. Have the licensed survey professional responsible for the project confirm the method and acceptance criteria.
Prepare post-processing before the outage
PPK, or post-processed kinematic positioning, calculates positions after fieldwork from recorded satellite measurements. In Emlid’s described workflow, the base and rover both record raw measurements, which software processes afterward. A live radio or cellular connection between them is not needed during collection.
PPK can therefore provide a backup when the RTK link fails, provided the necessary data are recorded. The trade-off is timing: results arrive after processing. That does not replace immediate positioning feedback for a task that needs an answer in the field.
Before leaving, confirm the recording procedure, required files, and person responsible for processing. Emlid’s Reach instructions call for recording on both receivers and choosing the same satellite systems on the base and rover. Those instructions are equipment-specific; follow the documentation for the actual receivers being used.
Related reading: Before Demolition, Build Survey Monument Protection Into the Work Plan
Test the handoff from field to office
Make a practice collection that includes exporting and processing the files. Emlid’s Stop & Go workflow, which collects individual points during brief rover stops, illustrates why this matters. It uses base and rover logs plus a CSV point-data file exported from its app. Its documentation says the CSV (PENZD) export option cannot be used for that workflow.
Also ask the survey lead whether a total-station alternative is appropriate for tasks that cannot continue with the proposed GNSS backups, and what preparation that would require. Treat that as a project-specific decision, not an automatic substitution.
Before dispatch, put the primary correction method, live backup, recording procedure, processing responsibility, and pause-work decision in one field plan. Resolve those questions while the crew can still change its equipment and schedule.
Featured image: Image by paulbr75 from Pixabay (Pixabay Content License)
Footnotes & Sources
- What Is RTK GPS and How Does It Improve Positioning Accuracy? | CHCNAV, Agriculture, April 17, 2026. — GNSS and RTK fundamentals, correction delivery by cellular or radio, known reference points, and multipath.
- PPK surveying: achieve centimeter accuracy offline, Emlid Blog, March 23, 2021. — Offline PPK workflow, its potential as an RTK backup, clear-sky qualification, and delayed positioning results.
- How to log data for PPK | Reach RS4 / RS4 Pro, docs.emlid.com. — Equipment-specific base and rover logging, matching satellite selections, downloading logs, and subsequent processing.
- How to log data for Stop & Go with Emlid Flow | Reach RS4 / RS4 Pro, docs.emlid.com. — Stop & Go point collection, required logs and CSV export, and the incompatible CSV (PENZD) option.