Guides
Preparing and handing off GNSS post-processing data
Separate observations from orbit and clock products, then align coverage, time systems and supported versions. Changing extensions does not compute a position solution.
Which format should you choose?
Choose by the role each file plays in your workflow.
- Preserve observations and acquisition context
- Select products for the analysis period
- Deliver a reproducible package
Preserve observations and acquisition context
Check RINEX type and version, observation codes, constellations, time system, epoch interval and gaps. Retain station, receiver and antenna metadata, original device logs and conversion settings.
Select products for the analysis period
Check SP3 satellites, coverage, time system and reference frame. Distinguish predicted from observation-based intervals, provider and product series; supply separate clock files or other inputs required by the software. SP3 alone may not provide all auxiliary data.
Deliver a reproducible package
Test loading in the actual software with compatible satellites and periods. Include filenames, provenance, checksums, conversion and processing settings, software versions and coordinate/time systems. Record gaps, exclusions and solution quality indicators; do not overwrite originals.
Formats to consider
RINEX
Good for: Provide receiver observations or navigation messages for post-processing
Less suitable for: Replace a finished track or a precise orbit product
SP3
Good for: Provide satellite orbit and clock information for the analysis period
Less suitable for: Store the receiver's code and phase observations
Before you export
- Check sharing scope for station or antenna positions and device logs. Readable files do not guarantee positioning accuracy; validate observation conditions and processing models.