Changeset 456 in ntrip for trunk/BNC/bnchelp.html

Timestamp:

Apr 26, 2007, 2:57:43 PM (18 years ago)

Author:

weber

Message:

* empty log message *

File:

• trunk/BNC/bnchelp.html (modified) (1 diff)

trunk/BNC/bnchelp.html

@@ -366 +366 @@
 </li>
 <li>
-BNC allows to by-pass its stream decoding and conversion algorithms, leave whatever is received untouched and save it in daily named files. To activate this functionality you need to enter the decoder string 'ZERO'. The generated file names are build from the characters of the affected mountpoints plus the two-digit numbers for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and runnign BNC on March 29, 2007 to save incoming data untouched in a file would lead to a file name WTZZ0_070329.
+BNC allows to by-pass its stream decoding and conversion algorithms, leave whatever is received untouched and save it in daily named files. To activate this functionality you need to enter the decoder string 'ZERO'. The generated file names are build from the characters of the affected mountpoints plus the two-digit numbers for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 to save incoming data untouched in a file would lead to a file name WTZZ0_070329.
 </li>
 <li>
 BNC allows to retrieve streams from virtual reference stations. For accessing these streams, an approximate rover position is required to be send in NMEA format to the NTRIP broadcaster. In return, an individual user-specific data stream is generated, usually by a network RTK software. This stream is tailored exactly to the latitude and longitude shown in the 'lat' and 'long' columns under 'Mountpoints'. Whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA string is indicated by 'yes' in column 'nmea' under 'Mountpoints' as well as 'yes' in column 'nmea' of the affected source-table. 
-<br>Default values for 'lat' and 'long' are taken from the source-table. You may change these values (first double-click, then edit fields 'lat' and/or 'long', then hit Enter) according to your needs. The position has to be introduced in northern latitude degrees (example for northern hemisphere: 52.436, example for eastern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Editing the 'lat' and 'long' values under 'Mountpoints' is only possible for streams that show 'yes' in column 'nmea'. The position must point to a location within the service area of the affected RTK network. RINEX files generated from these streams contain an additional COMMENT line in the header beginning with 'NMEA' to mention the 'lat' and 'long' values introduced.
+<br>Default values for 'lat' and 'long' are taken from the source-table. You may change these values (first double-click, then edit fields 'lat' and/or 'long', then hit Enter) according to your needs. The position has to be introduced in northern latitude degrees (example for northern hemisphere: 52.436, example for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Editing the 'lat' and 'long' values under 'Mountpoints' is only possible for streams that show 'yes' in column 'nmea'. The position must point to a location within the service area of the affected RTK network. RINEX files generated from these streams contain an additional COMMENT line in the header beginning with 'NMEA' to mention the 'lat' and 'long' values introduced.
 <br>Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner.
 </li>