Skip to content

File Loading

Jump to bottom
Guillaume W. Bres edited this page Nov 19, 2023 · 12 revisions

RINEXCLI

With RINEXCLI we are interested in loading either very simple or advanced contexts.
A very simple context is one unique type of RINEX, probably from a single provider.
When loading advanced context, we're interested in solving Navigation solutions.

RNX2CGGTTS

RNX2CGGTTS shares the same interface as RINEXCLI.
RNX2CGGTTS is simply another way to format the Navigation solutions.
Thefore you can apply anything that is explained with respect to real Navigation applications in RINEXCLI, to the RNX2CGGTTS application.

File loading

  • -f accepts a single (local) file
  • -d accepts a local directory that may contain subfolders with a maximal depth of 5

Both -f and -d can be used any amount of times. This should let you load everything you need easily.

File naming conventions

Note that all our applications accept files that do no follow standard naming conventions.
We may propose interface that will help you generate data that follow naming conventions.

File compression

rinex-cli:

  • supports native CRINEX decompression: you can load compressed Observation RINEX directly
  • supports native GZ decompression but your file names must be terminated by .gz so we can determine the GZ decompression is required
  • supports native CRNX compression (when generating data)
  • does not support native GZ compression yet (when generating data)

Examples

When identifying your RINEX data, it is sometimes easier to do it one file at a time.
In this case -f with a single file is how you do it:

rinex-cli -i -f test_resources/CRNX/V3/ESBC00DNK_R_20201770000_01D_30S_MO.crx.gz

When we have state of the art contexts, we can unlock advanced applications with only a couple of files.
In this tight yet advanced example, we stack good quality Observation, Navigation and one SP3 file and we're already compatible with PPP (centimetric) positioning:

rinex-cli -i \
  -f test_resources/CRNX/V3/ESBC00DNK_R_20201770000_01D_30S_MO.crx.gz \
  -f test_resources/NAV/V3/ESBC00DNK_R_20201770000_01D_MN.rnx.gz \
  -f test_resources/SP3/GRG0MGXFIN_20201770000_01D_15M_ORB.SP3.gz

Special care when loading Observation Data ⚠️

All Observation data that your pool contains should come from a single data provider (a single receiver).
Our current interface does not have the ability to describe two different receivers (2D contexts).
Having observations from two different receivers is not compatible with the physics we implement in RINEXCLI.

We recommend loading your Observation data with -f (individually).
The other option (for example when spanning more than 24h of data), is to have one folder that contains data from the same station, that you can then load with -d.

Directory and recursive loading

-d is most convenient when trying to overlap your RINEX Observations with Navigation, Meteo sensors and IONEX.
Being recursive, it is most likely compatible with well organized folders.

In this example, we overlap lazily one file 2023(DOY=254) with an entire set we downloaded from CDDIS

rinex-cli -i \
  -f test_resources/CRNX/V3/ESBC00DNK_R_20201770000_01D_30S_MO.crx.gz \
  -f test_resources/NAV/V3/ESBC00DNK_R_20201770000_01D_MN.rnx.gz \
  -f test_resources/SP3/GRG0MGXFIN_20201770000_01D_15M_ORB.SP3.gz

If we look closer, the Navigation files were sorted by Constellation, yet it is still compatible with -d because it will browse recursively up to 5 subfolders.

Process more than 24h of data

All our post processing apps accepts any amount of files. This means you can load more than 24 hours of data from a given data provider.
In otherwords, you can post process more than 24 hours of data.
In theory, we have no limitations on that.

Position solving use case

When solving navigation solutions, we need overlapping Observation and Navigation Data.
The presence of SP3 in the pool is a big plus to the solving process: we highly recommend adding SP3 of that day.

Clone this wiki locally