Crate rinex 

RINEX

RINEX (Receiver Independent EXchange) parser and formatter.
The RINEX format is fully open source and is specified to answer the requirements of navigation and much more.

To contribute to either of our project or join our community, you way

• open an Issue on Github.com
• follow our Discussions on Github.com
• join our Discord channel

Advantages :rocket:

• Fast and powerful parser
• Open sources: read and access all the code
• Seamless Gzip decompression (on flate2 feature)
• All modern GNSS constellations, codes and signals
  • GPS, Galileo, BeiDou and QZSS
• Time scales: GPST, QZSST, BDT, GST, UTC, TAI
• Efficient seamless compression and decompression
  • modern rewrite of the Hatanaka compression algorithm
• RINEX V4 full support, including
  • new Ionospheric coorections
  • new Time offset corrections
  • precise Earth Orientation updates
• Supports Observation, Navigation, Meteo and Clock RINEX, other RINEX-like formats have their own parser:
  • IONEX (Ionosphere Maps)
  • DORIS (special observations)
• Many pre-processing algorithms including Filter Designer
• Several file operations: merging, splitting, time binning (batch)
• Several SERDES operations:
  • to and from JSON with serde
  • to and from Ublox messages with ublox
  • to GNSS binary (currently limited to GPS protocol) with protos

Warnings :warning:

• Navigation is currently not feasible with Glonass, SBAS and IRNSS
• File production might lack some features, mostly because we’re currently focused on data processing

Citation and referencing

If you need to reference this work, please use the following model:

Nav-solutions (2026), RINEX: analysis and processing (MPLv2), https://github.com/nav-solutions

Library features

All RINEX formats described in the following table are supported natively, we do not hide a specific format under compilation options. The parser is smart enough to adapt to the file revision, you don’t need specific options to work with RINEX V2 or RINEX V4, and you may work with both at the same time conveniently.

We offer one compilation option per format, to provide more detail and “enhance” the capabilities for that format. For example:

• obs relates to the Observation RINEX format and provides special iterators and processing feature for this file format.
• nav: is the heaviest amongst all options, because it relies on heavy external libraries like nalgebra and anise.

Note that this library requires std library at all times, it is not planed to make it no-std compatible.

Our log feature unlocks debug traces. Please avoid using the trace level, as it is dedicated to debugging our file decompressor and is very verbose. In a complex processing pipeline, you can adjust the verbosity for each library, for example, this command line would define a default trace level, but increase that level to debug for the RINEX library only:

export RUST_LOG=trace,rinex=debug

We offer many serialization (and deserialization) options:

• serde for standard serdes, usually to JSON
• ublox: to serialize RINEX structures to UBX messages and construct RINEX structures from UBX messages
• binex: same thing for BINEX protocol
• rtcm: same thing for RTCM protocol
• gnss-protos: to serialize RINEX structures to raw GNSS navigation messages, for example GPS messages, or collecting a RINEX structure from GPS messages. For example, this could be the high level entrypoint to a GNSS simulator.

GNSS-QC (Quality check) relates to complex geodesic processing workflows, usually starting from RINEX files, by means of this library. To support demanding GNSS-QC operations, we provide two options:

• The qc option is the entry point, it provides means to manipulate thos files. For example, merging two files into one.
• The processing features builds on top qc and is expected to provide all requirements to complex GNSS-QC workflows.

Formats & revisions

The parser supports RINEX V4.0, that includes RINEX V4 Navigation files.
All revisions are supported by default and without compilation options: the parser automatically adapts.

RINEX formats & applications

Type	Parser	Writer	Content	Record Indexing	Timescale
Navigation (NAV)	:heavy_check_mark:	:heavy_check_mark:	Ephemerides, Ionosphere models	NavKey	SV System time broadcasting this message
Observation (OBS)	:heavy_check_mark:	:heavy_check_mark:	Phase, Pseudo Range, Doppler, SSI	ObsKey	GNSS (any)
CRINEX (Compressed OBS)	:heavy_check_mark:	:heavy_check_mark:	Phase, Pseudo Range, Doppler, SSI	ObsKey	GNSS (any)
Meteorological data (MET)	:heavy_check_mark:	:heavy_check_mark:	Meteo sensors data (Temperature, Moisture..)	MeteoKey	UTC
Clocks (CLK)	:heavy_check_mark:	:construction:	Precise temporal states	ClockKey	GNSS (any)
Antenna (ATX)	:heavy_check_mark:	:construction:	Precise RX/SV Antenna calibration	antex::Antenna	:heavy_minus_sign:
Ionosphere Maps (IONEX)	Moved to dedicated parser	:heavy_check_mark:	Ionosphere Electron density	Record Key	UTC
DORIS RINEX	Moved to dedicated parser	:heavy_check_mark:	Temperature, Moisture, Pseudo Range and Phase observations	Record Key	TAI / “DORIS” timescale

Contributions

Contributions are welcomed, we still have a lot to accomplish, any help is always appreciated.
We wrote these few lines to help you understand the inner workings.
Join us on Discord to discuss ongoing and future developments.

Modules

antex

Antex (ATX) - special RINEX, for antenna caracteristics

carrier

Carrier channels and associated methods

clock

RINEX Clock files parser & analysis

error

hardware

Receiver and antenna

hatanaka

RINEX compression / decompression module

header

RINEX file Header

marker

Geodetic marker

meteo

Meteo RINEX module

navigation

Navigation module

observation

Observation RINEX module

prelude

Package to include all basic structures

prod

Package dedicated to file production.

production

record

types

version

RINEX revision description

Structs

Rinex

Rinex comprises a Header and a Record section.

Enums

Bibliographydocsrs

Important articles and references that proved useful when designing this library