0.2.0
|
Multi-GNSS Raw Measurement Data. More...
Classes | |
struct | UbxRxmRawxData |
Repeated data in this message. More... | |
Public Attributes | |
std::vector< UbxRxmRawxData > | data |
Repeated block. | |
int8_t | leapS |
uint8_t | numMeas |
Number of measurements to follow. | |
double | rcvTow |
std::bitset< 1UL *8UL > | recStat |
Receiver tracking status bitfield (see graphic below) | |
std::array< uint8_t, 2 > | reserved1 |
Reserved. | |
uint8_t | version |
Message version (0x01 for this version). | |
uint16_t | week |
Multi-GNSS Raw Measurement Data.
This message contains the information needed to be able to generate a RINEX 3 multi-GNSS observation file. This message contains pseudorange, Doppler, carrier phase, phase lock and signal quality information for GNSS satellites once signals have been synchronized. This message supports all active GNSS.
int8_t NAV::vendor::ublox::UbxRxmRawx::leapS |
GPS leap seconds (GPS-UTC). This field represents the receiver's best knowledge of the leap seconds offset. A flag is given in the recStat bitfield to indicate if the leap seconds are known.
double NAV::vendor::ublox::UbxRxmRawx::rcvTow |
Measurement time of week in receiverblocal time approximately aligned to the GPS time system. The receiver local time of week, week number and leap second information can be used to translate the time to other time systems. More information about the difference in time systems can be found in RINEX 3 documentation. For a receiver operating in GLONASS only mode, UTC time can be determined by subtracting the leapS field from GPS time regardless of whether the GPS leap seconds are valid. [s]
uint16_t NAV::vendor::ublox::UbxRxmRawx::week |
GPS week number in receiver local time [weeks]