RINEX File Format Conversion¶
RINEX OBS File Format Conversion (4, 3, 2 to 2, 3, 4)¶
Observation Types Mapping¶
The used observation types mapping is hard-coded in**gfzrnx**. It can be shown up via the following command:
The information in columns 2, 3 and 4 is treated as a comment only and is not used.Remark
During the conversion process, the data values - observation, loss of lock indicator (LLI), signal strength indicator (SSI) - are left as they are. The LLI meaning differs between versions 2 and 3 or 4 and the Interpretation of bits 1 and 2 has to be used with caution!
RINEX-2 to RINEX-3 or 4¶
Please use this conversion only if you are sure that the output files are usable in the environment the data are supplied to! The output format for this conversion/transition is RINEX-3.01 to be standard-compliant. The 2-characters observation types are kept as they are except the code observations for GPS and GLONASS (see below).
As RINEX-3 is the standard output format of gfzrnx, simply run:
or orgfzrnx -finp pots0070.15o -fout ::RX3::00,DEU -sei in
gfzrnx -finp pots0070.15o -fout ::RX3::DEU,00 -sei in
to create a RINEX-3 compliant output file name POTS00DEU_R_201500700_01D_30S_MO.rnx .
For naming details, see the Automatic Output File Naming section.
A hard-coded observation types mapping for the GPS and GLONASS code observations is implemented:
| System | RINEX-2 | RINEX-3/ 4 |
|---|---|---|
| G | P1 | C1W |
| G | C1 | C1C |
| G | P2 | C2W |
| G | C2 | C2C |
| System | RINEX-2 | RINEX-3/ 4 |
|---|---|---|
| R | P1 | C1P |
| R | C1 | C1C |
| R | P2 | C2P |
| R | C2 | C2C |
This is used because both Px and Cx code types are mapped to the single Cx? RINEX-3 or 4 code type.
RINEX-3 or 4 to RINEX-2¶
The RINEX-2 output version is 2.11.
Use the --version_out or -vo command line parameter to define the RINEX format version of the output file.
gfzrnx -finp pots0070.15o -fout pots0070.15o_rx2 -vo 2
gfzrnx -finp POTS00DEU_R_201500700_01D_30S_MO.rnx -fout pots0070.15o --version_out 2
Specific Observation Type Selection¶
In the RINEX-3 or 4 format, one can have multiple observation types per data type and frequency (tracking mode or channel attribute). For a specific observation type selection for the format conversion, you can use the observation types selection feature in addition. Add the -ot command line parameter to the upper command like in the example below to select the RINEX-3 or 4 observation types to be converted and to get a distinct conversion.
Observation Type Selection via Signal Priorities¶
By default, the following signal priorities per frequency and satellite system are used for the RINEX-3 or 4 to RINEX-2 conversion:
| Sat. System | Freq. Num. | RINEX-3 Signal Priority |
|---|---|---|
| G - GPS | 1 | PRWCSLXYMN |
| G - GPS | 2 | PRWCDSLXYMN |
| G - GPS | 5 | IQX |
| . | ||
| R - GLO | 1 | PC |
| R - GLO | 2 | PC |
| R - GLO | 3 | IQX |
| R - GLO | 4 | ABX |
| R - GLO | 6 | ABX |
| . | ||
| E - GAL | 1 | BCX |
| E - GAL | 5 | IQX |
| E - GAL | 6 | BCX |
| E - GAL | 7 | IQX |
| E - GAL | 8 | IQX |
| . | ||
| J - QZS | 1 | SLXCZ |
| J - QZS | 2 | SLX |
| J - QZS | 5 | IQX |
| J - QZS | 6 | SLX |
| . | ||
| C - BDS | 1 | IQX |
| C - BDS | 2 | IQX |
| C - BDS | 5 | DPX |
| C - BDS | 6 | IQX |
| C - BDS | 7 | IQX |
| C - BDS | 8 | DPX |
| . | ||
| I - IRN | 5 | ABCX |
| I - IRN | 9 | ABCX |
| . | ||
| S - SBS | 1 | C |
| S - SBS | 5 | IQX |
The observation code's priority is LCDS: phase, code, doppler and signal strength. It defines the basis for the selection of the other observation types of that frequency, if existing. You can update the internal signal priority list by providing update records via the -pr3rx2 command line parameter. According to the upper table, it should consist of a comma-separated list of a satellite system identifier, colon, frequency number, colon, and the signal priority string. Observation types not covered by the priority string are simply ignored via conversion. See the following example:
The same priority string per satellite system for different frequencies can be given combined.
Used Observation Types¶
The observation types per satellite system used for the format conversion can be found as COMMENTs in the RINEX file header.
*********************************************************** COMMENT
* WARNING - FORMAT CONVERSION * COMMENT
* ------------------------------------------------------- * COMMENT
* The data values: observation, loss of lock (LLI) and * COMMENT
* signal strength (SSI) indicators are left as they are. * COMMENT
* The LLI meaning differs between versions 2 and 3 * COMMENT
* and the Interpretation of bit 1 and 2 has to be * COMMENT
* used with caution !!! * COMMENT
*********************************************************** COMMENT
COMMENT
RINEX 3 -> 2 TYPE CONVERSION DETAILS: COMMENT
------------------------------------- COMMENT
C C1I -> C1 COMMENT
C C6I -> C6 COMMENT
C C7I -> C7 COMMENT
C D1I -> D1 COMMENT
C L1I -> L1 COMMENT
C L6I -> L6 COMMENT
C L7I -> L7 COMMENT
C S1I -> S1 COMMENT
C S6I -> S6 COMMENT
C S7I -> S7 COMMENT
------------------------------------- COMMENT
E C1X -> C1 COMMENT
E C5X -> C5 COMMENT
E C7X -> C7 COMMENT
E C8X -> C8 COMMENT
E D1X -> D1 COMMENT
E L1X -> L1 COMMENT
E L5X -> L5 COMMENT
E L7X -> L7 COMMENT
E L8X -> L8 COMMENT
E S1X -> S1 COMMENT
E S5X -> S5 COMMENT
E S7X -> S7 COMMENT
E S8X -> S8 COMMENT
------------------------------------- COMMENT
G C1C -> C1 COMMENT
G C2X -> C2 COMMENT
G C5X -> C5 COMMENT
G D1C -> D1 COMMENT
G L1C -> L1 COMMENT
G L2W -> L2 COMMENT
G L5X -> L5 COMMENT
G C2W -> P2 COMMENT
G S1C -> S1 COMMENT
G S2W -> S2 COMMENT
G S5X -> S5 COMMENT
...
Remark¶
To avoid the selection of an observation type with sparse observations using Signal Priorities mode, it can be useful to add the -rsot command line parameter (remove sparse observations types) in addition.
gfzrnx -finp pots0070.15o -fout pots0070.15o_rx2 -vo 2 -rsot 40
gfzrnx -finp POTS00DEU_R_201500700_01D_30S_MO.rnx -fout pots0070.15o -vo 2 -rsot 40
RINEX NAV File Format Conversion (3.04/3.05)¶
There is a significant change in the GLONASS broadcast records in the RINEX version 3.05 (one additional record).
The GFZRNX output version is always the highest supported one. For the RINEX-3 standard output, a "dummy" record is added to be 3.05 standard compliant.
If you can't use this latest 3.05 version because e.g. your software does not support this, you can create a 3.04-formatted file via the -vo, -version_out command line parameters.
This works for splice operations too.