Changes between Version 26 and Version 27 of NDF


Ignore:
Timestamp:
Sep 26, 2018, 10:02:48 AM (7 years ago)
Author:
stoecker
Comment:

No longer planned, but real

Legend:

Unmodified
Added
Removed
Modified

  • TabularUnified NDF

    v26 v27  
    8989= NDF as ephemeris transport =
    9090
    91 RTCM3 already has a set of navigational data messages like 1019 (GPS), 1020 (GLONASS) or planned messages like 1044 (QZSS) 1045, 1046 (Galileo). With the additional satellite systems more and more navigation messages become necessary and also the existing system navigation messages are changing and thus additional formats are required.
     91RTCM3 already has a set of navigational data messages like 1019 (GPS), 1020 (GLONASS), 1042 (BDS), 1044 (QZSS) 1045, 1046 (Galileo). With the additional satellite systems more and more navigation messages become necessary and also the existing system navigation messages are changing and thus additional formats are required.
    9292
    9393The above message structure allows to use this message also as a replacement or enhancement of existing ephemeris messages simply by filling the message not with the real-time stream, but with all frames necessary to for an ephemeris set (e.g. for GPS C/A this would be subframes 1 to 3).