Custom Query (104 matches)
Results (43 - 45 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #105 | fixed | Transition from Qt 4.x to Qt5 | ||
| Description |
Migrate from Qt4 to Qt5.
Use c++11 standard newmat updaten QtWebKit is, as of 5.6, no longer part of the standard build and has been succeeded by QtWebEngine, see QWebEngineView, see here, here See https://github.com/mlytvyn80/bnc (BNC fork ported to Qt5 and newmat11) |
|||
| #104 | fixed | No Glonass with RTCM_3.2 data | ||
| Description |
Using BKG Ntrip Client Version 2.12.6 we get no Glonass with RTCM_3.2 streamed basestation data. If we include a RTCM_3 stream we get Glonass with both. If we just have a RTCM_3 stream we get Glonass. With version 2.8 it worked but had caps and dropouts. Any ideas? |
|||
| #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. |
|||
