A virtual reference station (VRS) is a network RTK method that generates reference data for a location close to a GNSS rover. A network of continuously operating reference stations supplies the observations, and the rover receives the resulting data through a correction service. For a survey team, the practical choice depends on service coverage, receiver compatibility, connectivity and the project coordinate system.
This guide explains the workflow, the equipment to prepare and the checks to complete before collecting survey points.
How does a virtual reference station work?
- The reference network observes GNSS signals. Fixed stations send their observations to network processing software, which models errors across the service area.
- The rover provides its approximate location. A VRS service uses this location to generate suitable virtual reference data. Check the provider’s requirements for sending the rover position.
- The rover receives corrections. Internet services commonly deliver the data through NTRIP. The selected mountpoint and correction format must match the account and receiver configuration.
- The survey team checks the result. Configure the project reference system and validate observations against known control before accepting new measurements.
NTRIP is the protocol used to transport GNSS data over the internet. VRS describes how network reference data are produced. The BKG overview explains the transport components, and Trimble’s operating guidance describes the approximate rover-position requirement. BKG NTRIP overview · Trimble rover-position guidance
What equipment and service access do you need?
- A compatible GNSS RTK receiver. Confirm the supported correction format, firmware and connection route for the exact model.
- A controller and field software. Check receiver connection, project settings, antenna-height entry and the required data export.
- An active correction account. Obtain the provider’s coverage information, caster address, port, mountpoint and access requirements.
- An internet connection for the correction link. Test connectivity at the work site using the receiver, controller or another supported device.
- Project control and a power plan. Prepare known points, suitable batteries and a procedure for handling interruptions.
Match these requirements to the current TOKNAV GNSS receiver range. Confirm the proposed model against the service you intend to use.
Set up the rover before fieldwork
- Confirm coverage and account access with the correction provider.
- Set the project coordinate reference, height system and any required transformation.
- Enter the caster, port, credentials and correct mountpoint. Enable rover-position reporting where the service requires it.
- Check that correction data are arriving and review the receiver’s solution status and correction age.
- Measure a known control point and compare the result with the project acceptance criteria. Repeat checks after relevant configuration or correction-source changes.
- Export a small sample and confirm that the receiving software reads the coordinates and attributes correctly.
Use the CORS/VRS setup checklist for preparation and the NTRIP configuration guide for connection checks.
When should you choose VRS or a local base?
Consider VRS when a suitable service covers the work area
VRS can reduce daily local-base setup where the project has dependable correction access and connectivity. Confirm the provider’s service limits, coordinate reference and support arrangements for the intended location.
Consider a local base when the project needs a site-controlled reference
A local base can suit work areas with limited network service or projects organized around their own reference station. Plan the base coordinates, communication route, power, security and crew responsibilities.
Compare these decisions in the VRS versus RTK base-station guide. For a correction-network project, review the TOKNAV CORS and VRS solution.
Check accuracy in your project reference system
Set acceptance tolerances from the project specification. Review the antenna height, coordinate reference, satellite environment, correction continuity and independent control observations together. Keep a record of the configuration and repeat measurements where the project requires them. NOAA NGS guidance discusses control and observation checks for real-time GNSS work. NOAA NGS real-time positioning guidelines (PDF)
A VRS connection test before committing to a receiver kit
A successful account login is only the first check. Ask the supplier to demonstrate the proposed receiver, controller and correction service together. Keep the same project reference system throughout the test so that connection faults and coordinate-setting faults can be investigated separately.
| Test stage | Record in the trial | Acceptance question |
|---|---|---|
| Connect | Receiver firmware, field-software version, caster, mountpoint and position-reporting setting; keep passwords out of shared reports. | Does the selected stream actually deliver usable correction data? |
| Check control | Point identifier, antenna height, solution status, correction age and horizontal/vertical differences against independent control. | Do the observations meet your project tolerances? |
| Interrupt and recover | What the operator sees during a planned connection interruption, how observations are flagged and the control check after recovery. | Can the crew identify and recheck observations affected by the interruption? |
| Export | A small point file with agreed units, point IDs, codes and height reference. | Does the receiving office software interpret the sample correctly? |
Swipe to view all columns.
What should a VRS quotation separate?
Separate receiver hardware, controller, field-software licence, correction subscription, mobile data, accessories and training. Ask who supplies and renews each service. For multiple crews, confirm concurrent-user terms with the correction provider rather than assuming one account covers every rover.
What if the receiver connects but coordinates are wrong?
Pause production observations. Compare the project reference, units, antenna settings and control values before changing the correction source. Use the NTRIP connection and validation guide to record the setup, then send the model and test observations with your VRS configuration enquiry.
Frequently asked questions
What is the difference between CORS, VRS and NTRIP?
CORS describes continuously operating reference stations. VRS is a method of producing network RTK reference data for the rover’s area. NTRIP provides an internet transport protocol for GNSS data streams.
How do I confirm that my receiver works with a VRS service?
Give the supplier and service provider the receiver model, firmware, controller, field software and proposed mountpoint. Ask them to confirm the correction format and connection settings, then complete a field check.
How should I validate a VRS survey?
Use an agreed coordinate reference, correct antenna settings and known control points. Check the complete configuration before production work and record the observations required by the project specification.
Get help choosing a VRS-ready receiver configuration
Tell us your country, survey application, current receiver or preferred model, correction service and required output. We can review the receiver and field-workflow requirements with you.
