TOKNAV INSIGHTS

GNSS RTK System Explained: Base, Rover and Correction Workflow

Q: Can one receiver workflow support both network RTK and a local base?

That is a configuration question. Start by describing the correction methods required across the work sites, then confirm the communications, operating process and equipment needed for each route.

Archive article

SYSTEM PLANNING GUIDE

Choose the base, rover or receiver route that fits the project

An RTK system is a working chain: rover receiver, correction source, communications, control setup and field software. Start with the role the project needs, then build a shortlist around the actual operating conditions.

Rover receiver

For a field crew using network corrections or a local base to collect survey, construction, GIS or guidance data.

Use the RTK receiver guide

Local base

For a project that needs its own temporary corrections, local control or a radio-based working route.

Review the tBase route

CORS / VRS infrastructure

For an organisation planning reference stations, managed corrections and multiple users or sites.

Explore CORS/VRS planning

What the project needs	System route to assess	Questions to settle first
One crew can use an available correction service	Rover + network corrections	Coverage, account access, mobile connectivity, coordinate reference and field software.
A site needs its own corrections for a local project	Base + rover	Control point, radio or communication plan, antenna placement, setup checks and working range.
A wider operation needs managed reference-station infrastructure	CORS / VRS network	Reference-station design, data links, correction delivery, monitoring and operator workflow.

Move from a search term to a project-ready shortlist

Set the application, required output and coordinate reference for the project.
Choose the correction source that is realistic for the actual field locations.
Shortlist the rover receiver, base or CORS/VRS route with the controller, software, power and communication path as one configuration.

Next, choose the RTK receiver workflow, browse the GNSS receiver product paths or use the receiver workflow comparison. Each route leads to the same final step: provide the project context before asking for a configuration or quotation.

Questions before you specify a GNSS RTK system

How do I decide between a rover, a local base and CORS/VRS?

Begin with the correction route the field work actually needs. A rover uses an available correction source; a local base supports project-owned corrections; CORS/VRS is for managed reference-station infrastructure across users or sites.

Can one receiver workflow support both network RTK and a local base?

That is a configuration question. Describe the correction methods required across the work sites, then confirm the communications, operating process and equipment required for each route.

What should be confirmed before a CORS/VRS project is scoped?

Confirm the service area, proposed station locations, communication links, correction delivery, monitoring expectations and the users or applications the network must serve.

Why should coordinate setup be discussed before hardware selection?

Coordinates and project control affect the field workflow and deliverable. Defining them early helps ensure that receiver, correction source and software are planned around the actual work.

NEXT STEP

Request an RTK system configuration

Share the country, project area, application, correction route and intended deliverable. Select the relevant product type on the contact form to start a focused discussion.

Request RTK system guidance