Changeset 1289 in ntrip

Timestamp:

Dec 8, 2008, 2:30:13 PM (15 years ago)

Author:

weber

Message:

* empty log message *

Location:

trunk

Files:

• BNC/bnchelp.html (modified) (1 diff)
• BNS/bnshelp.html (modified) (1 diff)

trunk/BNC/bnchelp.html

@@ -642 +642 @@
 </ul>
 <p>
-Note that in RTCM Version 2.x the message types 18 and 19 carry only the observables of one frequence. Hence it needs two type 18 and 19 messages to transport the observations from dual frequency receivers.
+Note that in RTCM Version 2.x the message types 18 and 19 carry only the observables of one frequence. Hence it needs two type 18 and 19 messages per epoch to transport the observations from dual frequency receivers.
 </p>
 <p>

trunk/BNS/bnshelp.html

@@ -220 +220 @@
 <p><a name="co"><h4>4.6. Clocks & Orbits</h4></p>
 <p>
-BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in SP3 format. They can be provided by a real-time GNSS engine such as RTNet. In contrast to SP3, the incoming clocks must have been corrected for the 2nd-order relativistic effect. This is a priodic time correction defined as -2 (R * V) / c^2 and includes the scalar product of satallite position and velocity divided by the speed of light raised to the second power.
-</p>
-
-<p>
-The sampling rate should not be much greater than 10 sec. Note that otherwise in IP streaming involved tools on the NTRIP Broadcaster or client side may respond with a timeout.
+BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in SP3 format. They can be provided by a real-time GNSS engine such as RTNet. The sampling rate should not be much greater than 10 sec. Note that otherwise in IP streaming involved tools on the NTRIP Broadcaster or client side may respond with a timeout.
 </p>