Skip to content

File Loading

Guillaume W. Bres edited this page Jul 2, 2024 · 12 revisions

File Loading interface

RINEX-Cli supports both simplistic and advanced operations.
A single RINEX does not allow advanced operations like post processed navigation.
You need to load at least two of them. The application allows loading all RINEX formats and SP3 files as well, for advanced operations.

Command line interface

Use -f to load a single file. You can load as many as you need.
Use -d to load a parse a directory. By default, we tolerate a maximal depth of 5. If that is not enough, you can increase that with --depth. You can parse as many directories as you need.

File naming conventions

Our tools do not care for filenames conventions. They can process files that do not follow standard naming conventions.

When generating output, our tool will generate files that do follow naming conventions. This has two consequences

  • you can use our file generation interfaces to follow naming conventions (from inputs that do not)
  • when working with modern files (long V3 RINEX like filenames), we cannot entirely form a valid RINEX filename if your inputs do not follow naming conventions. That's simply because some information are only described by the filename itself.

File compression

CRINEX (Compressed OBS RINEX) are supported natively.
Gzip compressed files are supported natively but their names must be terminated by .gz.
Z compressed files are not supported. They must be manually decompressed first.

Observation RINEX special mention ⚠️

RINEX-Cli does not support RTK nor differential processing entirely.
You are restricted to loading Observations that come from the same receiver. Otherwise, the results you will get will be incorrect.

We recommend either loading your Observation RINEX individually (-f) or sort them in dedicated folders (-d OBS/2024)

Context compliancy

When unsure what your input data allows to do, simply use the QC Summary Report to double check what you can do or not.

Process more than 24h of data

Our tools adapt to the input data and are not limited to one RINEX of one kind.
You can load 48h of RINEX observations for example. You can navigate for more than 24h and there is not theoretical limitation.

Our application is not tested yet for more than 24h timeframes - this will come soon.

Precise Products

Our tools support RINEX, include Clock RINEX and SP3 input products. This means they are compatible with precise navigation. The applications will automatically adapt to the forwarded data.

⚠️ in theory precise products should not be mixed. It is recommnded to use precise products that were published by the same agency. But that may only truly apply to applications targetting the best precision.

Loading single files

Use -f to load your dataset, one file at a time:

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

Form a PPP compliant context with 3 files:

rinex-cli \
    -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 \

Recursive loader

-d is most convenient when loading many files.

TODO: example
Clone this wiki locally