Changeset 2409 in ntrip for trunk/BNS

Timestamp:

Apr 12, 2010, 5:13:59 PM (14 years ago)

Author:

weber

Message:

* empty log message *

File:

• trunk/BNS/bnshelp.html (modified) (2 diffs)

trunk/BNS/bnshelp.html

@@ -256 +256 @@
 <p><a name="co"><h4>4.5. Clocks &amp; Orbits</h4></p>
 <p>
-BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in a SP3-like 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.
+BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in a SP3-like format and refered to APC. 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>
 
@@ -289 +289 @@
 </pre>
 </p>
-<p>
-Note that the '2nd order relativistic effect' is not used in BNS although it is required to provide it. If the relativistic effect is unavailable for you then you must at least send a dummy value. 
-</p>
+
 <p>
 In other words: The clocks in the ASCII stream from a real-time GNSS engine which feeds BNS must not contain the '2nd order relativistic effect'. Furthermore, BNS does not add this effect to the stream.