Operate
RINEX Logger
How Private CORS records the incoming RTCM stream, closes each UTC day, generates RINEX, and exposes daily archives.
Included in every planRINEX Logger is included for active base stations. The difference between plans is archive retention: Starter 3 months, Team 6 months, Business 12 months, Enterprise 12 months.
Daily logging pipeline
GNSS Base
│ RTCM 3.x
▼
Private CORS mountpoint
├── realtime NTRIP → rover
└── RTCM logger → hourly chunks
│
00:00 UTC
▼
finalize previous day
▼
RTCM → RINEX
OBS + NAV
▼
archive + QC
What happens at 00:00 UTC?
The new UTC day begins logging immediately. The previous day is finalized in the background and placed in the conversion queue. Logging for the new day does not wait for conversion of the previous day.
Archive statuses
| Status | Meaning |
|---|---|
| Recording | The current UTC day is still being logged. |
| Finalizing | The previous day has closed and its chunks are being prepared. |
| Converting | The RTCM archive is being converted to RINEX. |
| Ready | The daily RINEX archive is available for download. |
| Partial | An archive exists, but stream coverage or navigation content is incomplete. |
| Failed | The archive could not be finalized; the server may retry according to recovery policy. |
Download
Open RINEX Logger in the Private CORS dashboard, select or view the required base/mountpoint, choose the archive date, and download the available daily RINEX package.
Retention
Historical RINEX files remain available according to the active plan. Raw RTCM is an operational intermediate and is not advertised as a long-term proprietary receiver-raw archive.