Release Notes
RINGO v0.9.0 (January, 2024)⌗
1. New Features⌗
-
New command “rnxcsv”
Converts a RINEX observation file to a csv file. This command also supports qc output via “–qcmode” flag that includes timeseries of each linear combination and cycle slip flags. -
Support for direct reading of Compact RINEX (Hatanaka Format) files
Enables reading of Compact RINEX (Hatanaka Format) files natively, without using the external program “CRX2RNX”. -
Wildcard support for Powershell in the Windows version
Enables filename pattern expansion with wildcards (e.g., “*”, “?”, “A-X”) in Powershell. -
Support for RINEX 4.01 update (2023-07-10)
Added support for new observation codes included in the RINEX 4.01 update on 2023-07-10. -
Support for BINEX 0x7f update (2023-08-31)
Added support for QZSS L1C/B and other modern signals included in the BINEX 0x7f update on 2023-08-31. -
New opt “–deepMerge” for merge
Enables merging observation data deeply via “–deepMerge” flag. This can merge data with the same epochs taking into account differences in satellites and observation codes. -
New opt “–phaseshift”
Enables to apply phase shift corrections in output for the related commands. -
Observation code mapping change for RINEX version conversions “ObscodeMapping” section is added to change default observation codes mapping table that is used for RINEX version conversions.
-
Performance improvements
Speed up the output and enable parallel reading of multiple input files.
2. Misc⌗
- Output contents of unknown header labels, not ignored
- Support for reading interrupted obs data from correct position
- Skip observation data with unknown observation codes
- Keep LLI flags to the following data that are skipped by the change of data interval. This feature can be controlled by “–ignore-skipped-lli” and “–seconds-keep-lli” flags.
- Change behavior when invalid values are recorded in the “ANTENNA” related headers from an error to a warning, and the invalid antenna values are output as is
3. Bug fixes⌗
- Fix typo in the help message of “cal” command
- Fix an issue in which the number of epochs in QC changes by one when the time tag contains a decimal number of seconds
- Fix an issue in qc result that number of observation data was not calculated if the observation data include clock offsets > 0 msec at the beggining of the file
- Fix an issue that only one “IONOSPHERIC CORR” or “TIME SYSTEM CORR” could be output even if multiple values were stored in a navigation file.