Changes between Version 27 and Version 28 of NDF

Timestamp:

Nov 2, 2018, 8:41:53 AM (5 years ago)

Author:

stoecker

Comment:

Some more text for ephemeris usage

NDF

@@ -91 +91 @@
 RTCM3 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.
 
-The 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).
+The 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.
 Advantages of this approach:
  * Receivers already must support the frame format, so data decoding is no longer special for RTCM messages, but can use already existing algorithms
@@ -98 +98 @@
  * Unique structure for all satellite systems and signal types (even private services, ...)
  * New signals, adhering to an existing GNSS standard, but containing different data (e.g. new augmentation signals or pseudolites) can directly employ this standard
+
+== Implementation
+
+* For ephemeris usage set "Reserved field" to 1.
+* Only one satellite is allowed per message.
+* Complete matching and valid frames for one ephemeris set must be included in correct order:
+ * GPS C/A : Subframes 1 to 3
+ * GLONASS : Frame 1-5
+ * IRNSS : Subframes 1 and 2
+ * SBAS : Message 9