March 7, 2017 • 558 Views
The IGS RINEX Working Group recently announced the release of documents detailing the RINEX 3.03 Update 1. The document, along with a full description of the release notes, is available on the IGS Knowledge Base.
Receiver Independent Exchange Format (RINEX) is a data interchange format for raw satellite navigation data, enabling users to post-process the received data themselves, as needed for optimal results. It is
considered the standard for storing all data needed for GNSS positioning and navigation, providing a means to seamlessly store data transmitted from the GNSS and GEO/SBAS satellites, as well as meteorological data and fundamental observations made by GNSS receivers.
The first proposal for RINEX was developed by the Astronomical Institute of the University of Bern for the easy
exchange of the GPS data to be collected during the first large European GPS campaign EUREF 89. RINEX version 1 was introduced in 1989, with version 2, which added the possibility to include tracking data from systems such as GLONASS and SBAS, in 1990.
Release of RINEX version 3 was developed partially in response to the introduction of Europe’s Galileo, as well as enhanced GPS with new frequencies and observation types. Additional version 3 sub-versions included support for Japan’s QZSS, additional information on China’s BeiDou, enumeration of Russia’s GLONASS code phase biases, requirements for generation of consistent phase observations across different tracking modes, and unofficial space-borne receiver definitions used in RINEX 2.20. RINEX 3.03 was developed to build upon this by adding support for India’s IRNSS, new BeiDou B1 signal conventions, and other improvements.
Due to the wide industrial use of RINEX, its development is managed jointly by the IGS and Radio Technical Commission for Maritime Services-Special Committee 104 (RTCM-SC104). The IGS RINEX Working Group was established in December of 2011 to update and maintain the RINEX format to meet the needs of the IGS and the GNSS industry Learn more about this in the IGS Knowledge Base.