Purpose of a CORS network
A Continuously Operating Reference Station observes GNSS signals from a stable, documented location. A network combines stations, data collection, quality procedures, and user services. It may support surveying, construction, mapping, agriculture, deformation monitoring, research, and reference-frame realization.
Not every CORS network is an NRTK network. Some only archive RINEX, some broadcast individual RTCM streams, and others feed a network engine. The design should begin with required services and quality, not with a receiver shopping list.
Trust depends on both continuity and geodetic integrity. A fast stream from incorrect coordinates is not a reliable service; a perfect monument with frequent outages cannot support continuous RTK.
Coverage and site planning
Station spacing depends on service area, atmosphere, latitude, elevation, terrain, redundancy, and performance targets. There is no universal number. Critical zones should remain usable during one-station maintenance or failure.
Site surveys evaluate sky visibility, reflective surfaces, radio interference, security, access, lightning exposure, and long-term occupation. A convenient location that is likely to be moved has limited geodetic value.
Partner stations can improve geometry and resilience when reference frames and redistribution rights are compatible. Imported streams must retain a clear originating-service label.
Monument, antenna, and coordinates
The monument ties the antenna to stable ground or structure. Thermal expansion, vibration, construction changes, and repeatable antenna-height measurement are documented. Antenna model, radome, orientation, and calibration affect consistency.
Coordinates are determined from long observations and appropriate processing or network adjustment. Reference frame, epoch, height, and transformations are recorded. An autonomous receiver average is not sufficient for a professional reference origin.
Equipment changes are recorded in a station log and reflected in RTCM or RINEX metadata where possible. Monitoring can flag unexpected antenna or receiver descriptions after maintenance.
Power, communications, and physical protection
Receivers, modems, routers, and accessories require stable power. UPS, batteries, solar systems, or a secondary supply are selected from measured consumption and expected outage duration.
Fiber, fixed wireless, or cellular links can carry NTRIP. Reliability and latency matter more than raw bandwidth. A second communication technology reduces common-mode failures.
Lightning, surge protection, grounding, cable routing, and physical access need professional design. A station can remain online after an unauthorized antenna change, so inspections and equipment records complement electronic alerts.
RTCM, RINEX, PPK, and PPP services
Real-time services publish individual-base or network RTCM through an NTRIP Caster. The sourcetable describes formats, messages, constellations, coordinates, and GGA requirements. Individual rover accounts control access.
RINEX archives support quality control, PPK, PPP, coordinate time series, and recovery when live corrections were unavailable. Hourly files and clear sampling intervals make targeted download practical.
PPK combines base and mobile observations after collection. PPP uses precise orbit and clock products and has different convergence characteristics. These methods complement, rather than replace, a live RTK service.
| Service | Data | Primary use |
|---|---|---|
| Local RTK | One station’s RTCM | Centimeter positioning near the base |
| NRTK | Multi-station network corrections | Consistent regional coverage |
| PPK | Base and mobile RINEX | Post-mission trajectory or point processing |
| PPP | Observations and precise products | Absolute high-accuracy processing |
Operations, quality control, and governance
Daily checks cover absent stations, last-data age, and file generation. Weekly reviews examine repeated outages, disk capacity, client activity, and backups. Periodic geodetic analysis evaluates coordinates, multipath, and time series.
Access roles define who may add stations, change mountpoints, manage users, and download archives. Rover positions can be sensitive, so collection, retention, and tenant isolation are documented.
Partner agreements define redistribution rights and capacity. Technical access to a sourcetable does not automatically grant permission to republish it. Backup and disaster-recovery procedures cover configuration, tenant data, subscriptions, and valuable archives.
CORS network FAQ
What does CORS mean in GNSS?
CORS means Continuously Operating Reference Station: a stable GNSS station designed for continuous observations and, depending on the service, real-time correction broadcasting.
Is every CORS network an NRTK network?
No. A CORS network may only archive observations. It becomes an NRTK service when multiple stations feed a network engine that models spatial errors for rovers.
Why archive RINEX when RTCM is already streamed?
RINEX supports quality control, PPK, PPP, recomputation, research, and long-term coordinate analysis. It complements the live stream.