Changeset 6905 in ntrip

Timestamp:

Jun 15, 2015, 3:05:22 PM (9 years ago)

Author:

weber

Message:

Documentation completed

File:

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

trunk/BNC/src/bnchelp.html

@@ -808 +808 @@
 <p><a name="rnxvers2"><h4>3.4.8 Version 2 - optional</h4></p>
 <p>
-GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program is required to produce data in RINEX Version 2 format: 
+GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program is explicitly required to produce data in RINEX Version 2 format: 
 <ol type=1>
 <li>When saving the contents of incoming observation streams in RINEX Version 2 files as described in this section.</li>
@@ -820 +820 @@
 <li>Signals with attribute 'C' enjoy the highest priority. If such a Version 3 observation becomes available it is presented as RINEX Version 2 observation if that is the format you wish to see. Observations with other attributes are ignored.</li>
 <li>If no signal with 'C' attribute is available but we have an observation with 'W' attribute, BNC presents that one as RINEX Version 2 observation and ignores all observations with other attributes. The same applies mutatis mutandis to observations with P and X attributes.</li>
-<li>If no signal with 'C', 'W', 'P', or 'X' attribute is availalbe but a signal with undefined generation attribute (underscore character, '_') exists, BNC presents that one as RINEX Version 2 observation.</li>
+<li>If no signal with 'C', 'W', 'P', or 'X' attribute is availalbe but a signal with undefined generation attribute (underscore character, '_') exists, BNC presents that one as RINEX Version 2 observation. Note that observation attributes should actually always be available in RINEX Version 3. Hence the underscore character makes only sense in a few very special cases.</li>
 <li>If no signal with 'C', 'W', 'P', 'X', or '_' generation attribute exists then the question mark '?' tells BNC to present the first of any other appearing signal as RINEX Version 2 observation.</li>
 </ul>
@@ -857 +857 @@
 <p><a name="ephint"><h4>3.5.2 Interval - mandatory if 'Directory' is set</h4></p>
 <p>
-Select the length of the RINEX Navigation file generated. The default value is 1 day.
+Select the length of RINEX Navigation files. The default value is '1 day'.
 </p>
 
@@ -870 +870 @@
 <p><a name="ephvers"><h4>3.5.4 Version - optional</h4></p>
 <p>
-Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris in RINEX Version 3 format.
+Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris data in RINEX Version 3 format.
 </p>
 <p>