CONNECTED FIELD WORKFLOW
A productive RTK workflow is a complete system: a rover that suits the field task, a correction service that reaches the site, and a clear plan for what happens when coverage is limited.
Plan the receiver and correction route together
For construction layout, boundary work, topographic survey and GIS data collection, start by matching the receiver to the working method. The TOKNAV GNSS receiver range is the natural starting point for a rover, base or network-RTK discussion. Then confirm whether the crew will receive corrections from a local CORS/VRS service, a project base station, or both.
This avoids a common procurement mistake: choosing hardware first and discovering later that the site has no usable correction route. Our goal is to help your team start work with a practical, supportable configuration.
When CORS/VRS is the right fit
A CORS or VRS network is usually a good option when the work area has reliable mobile data and an approved correction service. It reduces the need to establish a local base every day, which can simplify multi-site field work. See the VRS solution overview for the workflow and the services to verify before deployment.
If coverage, subscription access or site policy is uncertain, prepare a base-station fallback. Our VRS vs. RTK base station guide explains the operational trade-offs without assuming one approach fits every site.
Build a dependable field setup
- Confirm correction availability: check the CORS/VRS provider, login method, reference frame, coverage and mobile-data conditions at the actual work location.
- Select the field role: decide whether the receiver will operate as a rover, a temporary base, or part of a mixed workflow. For a compact network-RTK receiver option, review the NET660 product page.
- Agree the acceptance check: define control checks, tolerance and the process to follow when corrections drop or the result looks inconsistent.
Questions teams ask before ordering
Can one receiver work with either VRS or a local base?
That depends on the receiver configuration, the correction protocol, the controller software and the project workflow. Share these details before ordering so the proposed setup is checked against the intended use.
What information should we send for a configuration recommendation?
Please include country or region, application, required field role, controller or data-collection software, correction source, expected mobile coverage and project schedule.
When should we keep a base-station fallback?
Keep one where CORS/VRS access, cellular coverage, radio policy or site access could interrupt a network-RTK workflow. The right fallback depends on the operating environment and required uptime.
CONFIGURATION REVIEW
Tell us your field workflow.
Send your location, application, correction source and equipment list. TOKNAV will help you define a receiver and CORS/VRS setup for a practical technical discussion.