Changeset 6858 in ntrip for trunk/BNC

Timestamp:

May 28, 2015, 12:30:52 PM (9 years ago)

Author:

stuerze

Message:

documentation completed

File:

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

trunk/BNC/src/bnchelp.html

@@ -2346 +2346 @@
 </p>
 <p>
-Below you find an example for the 'RTNET' ASCII format coming from a real-time GNSS engine. Each epoch begins with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite:
-</p>
+Below you find an example for the 'RTNET' ASCII format coming from a real-time GNSS engine. Each epoch begins with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records can provide 
+</p>
+<p>
+<li>satellite specific parameters </li>
+</p>
+<ul>
+A set of parameters can be defined for each satellite as follows:
 <p>
 &lt;SatelliteID&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; ...
@@ -2353 +2358 @@
 </p>
 <p>
-The following keys and values are currently specified in BNC:
+The following satellite specific keys and values are currently specified in BNC:
 </p>
 <table>
@@ -2367 +2372 @@
 </table>
 </p>
-
+</ul>
+<li> non-satellite specific parameters
+<ul>
+The following non-satellite specific keys and values are currently specified in BNC:
+</p>
+<table>
+<tr><td><i>Key&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</i></td><td><i>Values</i></td></tr>
+<tr><td>IND</td><td>followed by Dispersive Bias Consistency Indicator and MW Consitency Indicator</td></tr>
+<tr><td>VTEC</td><td>followed by Update Interval and Number of Ionospheric Layers</td></tr>
+</table>
+</p>
+If the key VTEC is specified, a data set for each layer contains within its first line the Layers Number, followed by Maximum Degree, Maximum Order and Layer Hight. After that the respective Spherical Harmonic Coefficients follow.
+</ul>
 <p>
 Because each keyword is associated to a certain number of values, an 'old' BNC could be operated with an incoming 'new' RTNET stream containing so far unknown keys - they would just be skipped in BNC.