-This chapter describes how to set the BNC program options. It explains the top menu bar, the processing options, the 'Streams' and 'Log' sections, and the bottom menu bar. +This chapter describes how to set the BNC program options. It explains the 'Top Menu Bar', the 'Settings Canvas' with the processing options, the 'Streams Canvas' and 'Log Canvas', and the 'Bottom Menu Bar'.
@@ -381,7 +381,8 @@
3.4.4. Sampling
3.4.5. Skeleton Extension
- 3.4.6. Script
- 3.4.7. Version
- 3.4.8. Version
+ 3.4.6. Skeleton Mandatory
+ 3.4.7. Script
+ 3.4.8. Version 2
+ 3.4.9. Version 3
3.5. RINEX Ephemeris
3.5.1. Directory
@@ -639,17 +640,15 @@
-It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available or does not contain the required information. The following is a default selection of observation types specified for a RINEX Version 3 file: +It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension' and 'Skeleton Mandatory') and switch to a default selection of observation types when such skeleton file is not available or does not contain the required information. The following is a default selection of observation types specified for a RINEX Version 3 file:
-C 12 C2 L2 D2 S2 C6 L6 D6 S6 C7 L7 D7 S7 SYS / # / OBS TYPES -E 20 C1 L1 D1 S1 C5 L5 D5 S5 C6 L6 D6 S6 C7 SYS / # / OBS TYPES - L7 D7 S7 C8 L8 D8 S8 SYS / # / OBS TYPES -G 20 C1C L1C D1C S1C C1P L1P D1P S1P C2C L2C D2C S2C C2P SYS / # / OBS TYPES - L2P D2P S2P C5 D5 L5 S5 SYS / # / OBS TYPES -J 16 C1 L1 D1 S1 C2 L2 D2 S2 C5 L5 D5 S5 C6 SYS / # / OBS TYPES - D6 L6 S6 SYS / # / OBS TYPES -R 16 C1C L1C D1C S1C C1P L1P D1P S1P C2C L2C D2C S2C C2P SYS / # / OBS TYPES - L2P D2P S2P SYS / # / OBS TYPES -S 8 C1 L1 D1 S1 C5 L5 D5 S5 SYS / # / OBS TYPES +C 9 C2I L2I S2I C6I L6I S6I C7I L7I S7I SYS / # / OBS TYPES +E 12 C1X L1X SX1 C5X L5X SX5 C7X L7X SX7 C8X L8X SX8 SYS / # / OBS TYPES +G 15 C1C L1C S1C C1W L1W S1W C2X L2X S2X C2W L2W S2W C5X SYS / # / OBS TYPES + L5X S5X SYS / # / OBS TYPES +J 15 C1C L1C S1C C1W L1W S1W C2X L2X S2X C2W L2W S2W C5X SYS / # / OBS TYPES + L5X S5X SYS / # / OBS TYPES +R 6 C1C L1C S1C C2P L2P S2P SYS / # / OBS TYPES +S 9 C1C L1C S1C C5I L5I S5I C5Q L5Q S5Q SYS / # / OBS TYPES@@ -658,6 +657,7 @@
-The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various NTRIP Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received. -
+The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various NTRIP Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received. Note that one RTCM Version 2 stream in this example is forced to be saved in RINEX Version 3 format. Although it is possible to do this it is not recommended because RTCM Version 2 streams can not be precisely mapped to this file format, see Section 'Version 2' below for details. + +
Figure 7: BNC translating incoming streams to 15 min RINEX Version 3 files.
@@ -788,5 +788,12 @@-
+3.4.6 Skeleton Mandatory - optional
+Tick check box 'Skeleton mandatory' in case you want that RINEX files are only produced if skeleton files are available for BNC. If no skeleton file is available for a particular source then no RINEX observation file will be produced from the affected stream. +
+Note that a skeleton file contains RINEX header information such as receiver and antenna types. In case of stream conversion to RINEX Version 3 a skeleton file should also contain information on potentially available observation types. A missing skeleton file will therefore enforce BNC to only save a default set of RINEX 3 observation types. +
+ +Whenever a RINEX Observation file is saved, you might want to compress copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that, specify the full path of the script/batch file here. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac OS X systems). @@ -799,7 +806,7 @@
- --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 processing and default output 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 required to produce data in RINEX Version 2 format:
The default format for RINEX Observation files is RINEX Version 2.11. Select 'Version 3' if you would like to save observations in RINEX Version 3 format.