Custom Query (104 matches)
Results (19 - 21 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3 | fixed | Duplicate data records in generated RINEX files | ||
| Description |
When the RTCM data contains GPS and Glonass data, data records are output both when receiving the 1004 GPS message and the 1012 Glonass message. Observed in NO_RTCM3_MAIN mode with RINEX v. 2. A patch is attached to output a data record only after receiving the last RTCM message for an epoch. |
|||
| #4 | fixed | Specify data types in RINEX files | ||
| Description |
In NO_RTCM3_MAIN mode, space is allocated in the generated RINEX files for all possible data types. That causes much whitespace in the files. The attached patch implements a suggested enhancement to let the main program specify which data types to handle. If no data types are specified, the functionality is unchanged. Tested with RINEX v. 2. |
|||
| #5 | fixed | Read RTCM 1013 message to get full date | ||
| Description |
The RTCM RTK message time tags are time of week (GPS) and time of day (Glonass). When reading logged data offline, the 1013 message can be read to get full date for the RINEX header. The attached patch implements reading of the 1013 message in NO_RTCM3_MAIN mode. No change is made if NO_RTCM3_MAIN is undefined, and the header records created in rtcm3torinex.c are unchanged. |
|||
