Custom Query (104 matches)
Results (1 - 3 of 104)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#165 | fixed | BNC Posibility to disable the epoch check | ||
Description |
BNC automatically checks the epoch and does not generate observations output to the Feed Engine nor Ephemerids if the epoch is not aligned with the systems local. Instead, only a "Wrong observation epoch(s)" message appears in the log. This makes BNC useless for anything that is not real-time. I would suggest there should be a "yes/no" option (set to yes by default) that allows the user to choose whether or not to perform this check. |
|||
#103 | fixed | Possible wrong value of N4 (DF134) in IGS RTCM3EPH feed | ||
Description |
Hi, I am using IGS RTCM3EPH feed and I noticed that RTCM V3 GLONASS ephemeris message (1020) is provided with GLONASS-M N4 (DF134) value 1, even though the value should be 6 for the current year like in broadcast ephemeris. DF 134 refers to GLONASS four-year interval number starting from 1996. And it is can be calculated in following way: M4 = ceil( ( current_year - 1996 ) / 4.0 ); Thanks much, Altti Jokinen NovAtel Inc. |
|||
#134 | invalid | Old GNSS week in BCEP00BKG0 for BeiDou and Galileo | ||
Description |
Hi, I noticed that old GNSS week and TOE is provided for many BeiDou satellites and also for Galileo PRN8. See log as an attachment. Best regards, Altti Jokinen |