Data Analysis

Report synthesis and QC

The default behavior of this toolbox is to generate analysis reports.
The only opmodes that do not generate a report are the File Operations as they target output products synthesis. You can then use the toolbox to analyze the output products you have just generated.

In this example, a single file is loaded and no operation is requested: a basic report is synthesized.

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

Other options

A few options allow controlling the report synthesis

• -o allows customizing the report name. Otherwise, it is named after the input product.
• -f stands for --force and forces report synthesis. In complex workflows, you can use the toolbox with different options in a row, and we stack the new chapters to the previous report. Check out our survey tutorials for that.

Similarities with teqc

We share similarities with teqc which will prove convenient
to advanced "teqc" users. Among them:

• Quick GNSS filters (-G, -R, ...) still exist
• Similar navigation analysis including sampling report
• Similar signals analysis and reporting
• Like TEQC we evaluate some markers that emphasize what the input context is compatible with and capable of, but we go beyond that with slightly finer definitions

Differences with teqc

Unlike teqc:

• We are not limited to RINEX V2, V3. V4 RINEX is fully supported.
• We integrate a complete position solver (similar to RTKLib) so you can kind of get the best of teqc and rtklib at once
• We do not limit ourselves to the analysis of GPS and Glonass constellations or L1 and L2 signals. For example, other combinations will be analyzed or processed. The library is supposed to support all RINEX format for every signal, that applies to military signals in theory, not tested in practice obviously. Feel free to contribute.
• We have no means to detect data duplicates as of today: duplicated epochs will reflect in the results.

Next step

• QC Summary report