Observation Identification

Observation Data Identification

RINEXCLI -i and related options demonstrations.

When using Observation Data, you most likely want to know if your data is compatible with a Position solving strategy and what Position solutions (PVT) you can expect. Typically:

• the Timescale in use: the time system in which observations are expressed
• the time frame of the observations
• what Constellation and Space Vehicles (SV) are in sight
• the signal conditions (SNR, quality..)

The presence of data gaps in Observations will most likely inhibit position solving in those time frames.

We'll run the identification process on ESBC00DNK_R_20201770000_01D_30S_MO hosted in this repo.
The following applies as long as at least one Observation file is present in the pool.

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

The time frame tells you that the observations are expressed in GPST as most (all?) existing Observation RINEX.

TODO

The position of the geodetic Marker is contained in the file Header (also refered as Apriori Position)

TODO

This means that the reference station (ESBC00DNK) has measured and estimated the receiver position and it can be used as an Apriori Position in the process of resolving PVT solutions.

The file contains vehicles that belong to GPS, Glonass, BeiDou, QZSS, Galileo, EGNOS, BDSBAS and SDCM.
The receiver is state of the art : The receiver is operated professionnaly, with a peak of best signal quality estimated at approx. SNR=54 dB. The sampling is fixed at 2 points per minute and was very steady, since no gaps have been detected.