Index: trunk/BNC/src/bnchelp.html
===================================================================
--- trunk/BNC/src/bnchelp.html (revision 6977)
+++ trunk/BNC/src/bnchelp.html (revision 6978)
@@ -1376,12 +1376,12 @@
-BNC's Broadcast Correction files contain blocks of records in plain ASCII format. Each block covers information about one sprecific topic and starts with an epoch record with special character '>' being its first character (as we have it in RINEX Version 3).
-
-
-The epoch record of a Broadcast Corrections block
-
-
-
-The leading epoch record of each block in a Broadcast Corrections file contains 10 parameters. Example:
+BNC's Broadcast Correction files contain blocks of records in plain ASCII format. Each block covers information about one sprecific topic and starts with an 'Epoch Record'.
+
+
+The 'Epoch Record' of a Broadcast Corrections block
+
+
+
+The leading 'Epoch Record' of each block in a Broadcast Corrections file contains 11 parameters. Example:
@@ -1391,5 +1391,6 @@
Their meaning is as follows:
-
+
+- Special character '>' is the first character in each 'Epoch Record' (as we have it in RINEX Version 3)
- SSR message or topic descriptor, valid descriptors are:
ORBIT, CLOCK, CODE_BIAS, PHASE_BIAS, or VTEC
- Year, GPS time
@@ -1420,5 +1421,5 @@
- Number of following records in this block
- Mountpoint, source/stream indicator
-
+
Each of the following 'satellite records' in such a block carries information for one specific satellite. Undefined parameters in the 'satellite records' could be set to zero "0.000".
@@ -1528,11 +1529,20 @@
The second record in this block provides the following consistency information:
-- Dispersive bias consistency indicator
-- MW consistency indicator
+
+- Dispersive bias consistency indicatory
+0 − phase biases valid for non-dispersive signal only
+1 − phase biases maintain consistency between non-dispersive and all original dispersive phase signals
+
+
+- MW consistency indicator
+0 − code and phase biases are independently derived
+1 − consistency between code and phase biases is maintained for the MW combinations
+
+
Following records provide satellite specific information:
- GNSS Indicator and Satellite Vehicle Pseudo Random Number
-- Yaw angle [°], restricted to be in [0°, 360°]
+- Yaw angle [°], restricted to [0°... 360°]
- Yaw rate [°/s]
- Number of phase biases in this record, succeeded by phase specific information:
@@ -2042,5 +2052,5 @@
3.13. PPP Client
-BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a dual frequency receiver, this also
+BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data from one or more GNSS systems in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a dual frequency GNSS receiver, this also
- requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of RTCM Version 3 'State Space Representation' (SSR) messages. Note that for BNC these Broadcast Corrections need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on http://igs.bkg.bund.de/ntrip/orbits. Stream 'CLK11' on NTRIP Broadcaster 'products.igs-ip.net:2101' is an example.
@@ -2053,5 +2063,5 @@
-Figure 20: Precise Point Positioning with BNC, PPP Panel 1.
+Figure 20: Real-time Precise Point Positioning with BNC, PPP Panel 1.
