Observation Identification

Observation RINEX

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.

To answer all these requirements, the report we synthesize will study:

• expose all available signals and constellations
• analyze the time frame and data gaps for each signal and constellation
• plot all signal observations to rapidly determine where you might have problems

rinex-cli offers other options to deal with Observation RINEX, some of them being:

• -z for ZeroRepair and repair bad observations (invalid RINEX) prior positioning. Checkout these examples where we are able to resolve PPP solutions while the station provided invalid observations (on some signals)
• tbin, split, merge to format and work with those files
• diff operation to perform RX(A) - RX(B), usually dedicated to phase and clock analysis

Compliancy

Loading Observation RINEX will unlock signal plots.
Combining Observation RINEX to Navigation RINEX will unlock NAVI compliancy. Combining Observation RINEX to NAV+SP3+Clock RINEX will unlock the PPP compliancy.
If Observations and Clock RINEX were expressed in the same timeframe, in the same timescale, you unlock PPP+Ultra.