Ignore:
Timestamp:
Sep 9, 2026, 3:45:54 PM (12 days ago)
Author:
stuerze
Message:

updates regarding RTCM-SSR

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/RTCM3/RTCM3coDecoder.cpp

    r11010 r11011  
    207207      memcpy(&_phaseBias,  &phaseBiasSav, sizeof(phaseBiasSav));
    208208      memcpy(&_vTEC,       &vTECSav,      sizeof(vTECSav));
    209       memcpy(&metaDataSav, &_metaData,    sizeof(metaDataSav));
     209      memcpy(&_metaData,   &metaDataSav,  sizeof(metaDataSav));
    210210      break;
    211211    }
     
    976976      epoSecGlo = epoSecGlo + gnumleap(date.year(), date.month(), date.day());
    977977    }
    978     if (_type == RTCMssr) {
     978    if (_type == RTCMssr || _type == RTCMnewssr) {
     979      // Same GLONASS epoch wire convention (UTC+3h) as RTCMssr
    979980      epoSecGlo = epoSecGlo - 3 * 3600 + gnumleap(date.year(), date.month(), date.day());
    980981    }
     
    997998    _lastTime.set(currentWeek, epoSecBds);
    998999  }
     1000  // Some message types (e.g. Metadata) carry no epoch field of their own,
     1001  // and none of the above found anything fresh to use either - fall back
     1002  // to the last known valid time rather than leaving _lastTime invalid
     1003  // (which would silently drop the message's output entirely).
     1004  else if (prevTime.valid()) {
     1005    _lastTime = prevTime;
     1006  }
    9991007
    10001008  if (_lastTime.valid()) {
Note: See TracChangeset for help on using the changeset viewer.