Modify ↓
Opened 10 years ago
Closed 9 years ago
#25 closed defect (fixed)
message from Loukis regarding GLONASS MSM
| Reported by: | stuerze | Owned by: | stoecker |
|---|---|---|---|
| Priority: | normal | Component: | BNC |
| Version: | Keywords: | RTCM MSM encoding | |
| Cc: | stuerze |
Description
I have a suspicion that the degradation of the GLONASS ephemeris may have been corrupting the RTCM MSM GLONASS measurements and would like to ask if this is something you are aware of. The reason I am asking is because I had problems with solutions involving MGEX GLONASS observations but the solutions based on IGS-sourced RINEX files and conventional RTCM streams from the RTS appeared to behave well. Is there a reliance on the GLONASS ephemeris within the RTCM MSM encoding software that could be affected by the corrupted messages?
Attachments (0)
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 9 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
It depends on the frequency number (and the calculated clock offset). I'm not aware of any other dependencies. But as RTCM format is reducing the available data ranges I believe, that data simply did not match into the data format anymore. With RAW data that is not an issue, as it is possible to store large outliers as well.