Changeset 6584 in ntrip for trunk/BNC

Timestamp:

Feb 6, 2015, 3:59:06 PM (10 years ago)

Author:

weber

Message:

Documentation completed

File:

• trunk/BNC/src/bnchelp.html (modified) (2 diffs)

trunk/BNC/src/bnchelp.html

@@ -541 +541 @@
 
 <p>
-Please note that RTCM Version 3 messages 1084 for GLONASS observations don't contain the channel numbers. Hence these messages can only be converted to RINEX when you pull in addition another stream which includes them. It could be a stream carrying 1087 GLONASS observation messages or 1020 GLONASS ephemeris messages.
+Please note that RTCM Version 3 messages 1084 for GLONASS observations don't contain the channel numbers. However, these messages can only be converted to RINEX when you add messages which include the channel numbers. This could be done though an additional stream carrying 1087 GLONASS observation messages or an additional stream carrying 1020 GLONASS ephemeris messages. You could also consider setting up a streams which contains both, the 1084 and the 1020 messages.
 </p>
 <p>
@@ -1542 +1542 @@
 
 <p>
-Please note further that RTCM Version 3 message types 1084 for GLONASS don't contain GLONASS channel numbers. Hence observations from these messages can only be decoded when you pull in addition another stream which includes the channels. It could be a stream carrying 1087 GLONASS observation messages or 1020 GLONASS ephemeris messages.
+Please note further that RTCM Version 3 message types 1084 for GLONASS don't contain GLONASS channel numbers. Observations from these messages can only be decoded when you include 1020 GLONASS ephemeris messages to your stream which contain the channels. You could also consider adding a second stream carrying 1087 GLONASS observation messages or 1020 GLONASS ephemeris messages as both contain the GLONASS channel numbers.
 </p>
 <p>