-As a default, configuration files for running BNC on Unix/Linux/Mac OS X systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration file name is 'BNC.bnc'.
--The default file name 'BNC.bnc' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag & Drop a configuration file icon to start BNC (not on Mac OS X systems). Some configuration options can be changed on-the-fly. See annexed 'Configuration Examples' for a complete set of configuration options. It is also possible to start and configure BNC via command line. +As a default, configuration files for running BNC on Unix/Linux/Mac OS X systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration filename is 'BNC.bnc'.
++The default filename 'BNC.bnc' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag & Drop a configuration file icon to start BNC (not on Mac OS X systems). Some configuration options can be changed on-the-fly. See annexed 'Configuration Examples' for a complete set of configuration options. It is also possible to start and configure BNC via command line.
@@ -427,5 +427,5 @@ 3.3.5. Raw Output FileFigure 8: BNC translating incoming observation streams to 15 min RINEX Version 3 Observation files.
- --The default for RINEX file names in BNC follows the convention of RINEX Version 2. However, the software provides options to alternatively follow the file name convention of RINEX Version 3. RINEX Version 2 file names are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named
+ ++The default for RINEX filenames in BNC follows the convention of RINEX Version 2. However, the software provides options to alternatively follow the filename convention of RINEX Version 3. RINEX Version 2 filenames are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named
@@ -768,5 +768,5 @@-If there is more than one stream with identical 4Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX file name. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Version 2 Observation files are named as
+If there is more than one stream with identical 4Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX filename. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Version 2 Observation files are named asFRAN{ddd}{h}_KFURT.{yy}O @@ -774,5 +774,5 @@-If several streams show exactly the same mountpoint name (example: BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net), BNC adds an integer number to the file name leading i.e. to hourly RINEX Version 2 Observation files like
+If several streams show exactly the same mountpoint name (example: BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net), BNC adds an integer number to the filename leading i.e. to hourly RINEX Version 2 Observation files likeBRUS{ddd}{h}_0.{yy}O @@ -780,5 +780,5 @@-Note that RINEX Version 2 file names for all intervals less than 1 hour follow the file name convention for 15 minutes RINEX Version 2 Observation files i.e.
+Note that RINEX Version 2 filenames for all intervals less than 1 hour follow the filename convention for 15 minutes RINEX Version 2 Observation files i.e.FRAN{ddd}{h}{mm}.{yy}O @@ -789,5 +789,5 @@-In case of RINEX Version 3 file names, the following convention holds: +In case of RINEX Version 3 filenames, the following convention holds:
@@ -805,5 +805,5 @@
-Example for Mixed RINEX Version 3 GNSS observation file name, file containing 1 hour of data, one observation every second, 'MO' standing for 'Mixed Observations': +Example for Mixed RINEX Version 3 GNSS observation filename, file containing 1 hour of data, one observation every second, 'MO' standing for 'Mixed Observations':
ALGO00CAN_R_20121601000_01H_01S_MO.rnx @@ -811,5 +811,5 @@-Note that file name details are produced from the streams mountpoint as well as corresponding BNC settings and meta data from the Ntrip Broadcaster source-table. +Note that filename details are produced from the streams mountpoint as well as corresponding BNC settings and meta data from the Ntrip Broadcaster source-table.
@@ -837,5 +837,5 @@-When producing RINEX Observation files from mountpoints (examples) 'BRUS0', 'FRANKFURT'; and 'WETTZELL' the following skeleton file names would be accepted +When producing RINEX Observation files from mountpoints (examples) 'BRUS0', 'FRANKFURT'; and 'WETTZELL' the following skeleton filenames would be accepted
@@ -956,14 +956,14 @@ --
3.4.10 Version 3 File Names - optional
-Tick check box 'Version 3 file names' to let BNC create so-called extended file names following the RINEX Version 3 standard. -
-Default is an empty check box, meaning to still use file names following the RINEX Version 2 standard although the file contents is saved in RINEX Version 3 format. +
+
3.4.10 Version 3 Filenames - optional
+Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. +
+Default is an empty check box, meaning to still use filenames following the RINEX Version 2 standard although the file contents is saved in RINEX Version 3 format.
-Broadcast Ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3 e.g. as message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (tentative, BDS/BeiDou). The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'BRDC'. +Broadcast Ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3 e.g. as message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (tentative, BDS/BeiDou). The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'.
@@ -974,5 +974,5 @@
-The following is an example for a RINEX Version 3 Navigation file name. The file contains one days data. 'MN' stands for 'Multi Constellation Navigation' data. +The following is an example for a RINEX Version 3 Navigation filename. The file contains one days data. 'MN' stands for 'Multi Constellation Navigation' data.
BRDC00DEU_S_20121600000_01D_MN.rnx @@ -1010,9 +1010,9 @@ --
3.5.5 Version 3 File Names - optional
-Tick check box 'Version 3 file names' to let BNC create so-called extended file names following the RINEX Version 3 standard. -
-Default is an empty check box, meaning to still use file names following the RINEX Version 2 standard although the file contents is saved in RINEX Version 3 format. +
+
3.5.5 Version 3 Filenames - optional
+Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. +
+Default is an empty check box, meaning to still use filenames following the RINEX Version 2 standard although the file contents is saved in RINEX Version 3 format.
@@ -1232,5 +1232,5 @@
3.6.6 Directory for Plots - optional if 'Action' is set to 'Analyze'
-If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. File names will be composed from the RINEX input file name(s) plus suffix 'PNG' to indicate the plot file format in use. Default is an empty option field, meaning that plots will not be saved on disk. +If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. Filenames will be composed from the RINEX input filename(s) plus suffix 'PNG' to indicate the plot file format in use. Default is an empty option field, meaning that plots will not be saved on disk.
@@ -1520,5 +1520,5 @@-While we have a plain ASCII standard for saving broadcast ephemeris in RINEX Navigation files, we don't have an equivalent standard for corrections to broadcast ephemeris. Hence BNC saves Broadcast Correction files following its own format definition. The file name convention for Broadcast Correction files follows the convention for RINEX Version 2 files except for the last character of the file name suffix which is set to 'C'. +While we have a plain ASCII standard for saving broadcast ephemeris in RINEX Navigation files, we don't have an equivalent standard for corrections to broadcast ephemeris. Hence BNC saves Broadcast Correction files following its own format definition. The filename convention for Broadcast Correction files follows the convention for RINEX Version 2 files except for the last character of the filename suffix which is set to 'C'.
@@ -2369,5 +2369,5 @@-Note that the only mandatory parameters in this file are the 'Station' parameters, each standing for an observation stream's mountpoint or the 4-character station ID of a RINEX file name. The following shows further valid examples for records of a 'Coordinates' file. +Note that the only mandatory parameters in this file are the 'Station' parameters, each standing for an observation stream's mountpoint or the 4-character station ID of a RINEX filename. The following shows further valid examples for records of a 'Coordinates' file.
@@ -3275,5 +3275,5 @@ -Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system:
+
/home/user/BNC${GPSWD}.sp3
Note that '${GPSWD}' produces the GPS Week and Day number in the file name.Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system:
/home/user/BNC${GPSWD}.sp3
Note that '${GPSWD}' produces the GPS Week and Day number in the filename.Default is an empty option field, meaning that you don't want BNC to save the uploaded stream contents in daily SP3 files. @@ -3283,5 +3283,5 @@
-The file names for the daily SP3 files follow the convention for SP3 file names. The first three characters of each file name are set to 'BNC'. Note that clocks in the SP3 orbit files are not corrected for the conventional periodic relativistic effect. +The filenames for the daily SP3 files follow the convention for SP3 filenames. The first three characters of each filename are set to 'BNC'. Note that clocks in the SP3 orbit files are not corrected for the conventional periodic relativistic effect.
@@ -3298,5 +3298,5 @@
-Specify a path for saving the generated clock corrections as Clock RINEX files. If the specified directory does not exist, BNC will not create Clock RINEX files. The following is a path example for a Linux system:
/home/user/BNC${GPSWD}.clk
Note that '${GPSWD}' produces the GPS Week and Day number in the file name. +Specify a path for saving the generated clock corrections as Clock RINEX files. If the specified directory does not exist, BNC will not create Clock RINEX files. The following is a path example for a Linux system:
/home/user/BNC${GPSWD}.clk
Note that '${GPSWD}' produces the GPS Week and Day number in the filename.@@ -3416,5 +3416,5 @@
-Command line options are available to run BNC in 'no window' mode or let it read data offline from one or several files for debugging or Post Processing purposes. BNC will then use processing options from the involved configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNC.bnc'. +Command line options are available to run BNC in 'no window' mode or let it read data offline from one or several files for debugging or Post Processing purposes. BNC will then use processing options from the involved configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration filename instead of using the default name 'BNC.bnc'.
@@ -3711,5 +3711,5 @@3.20.3 Configuration File - optional
@@ -3826,5 +3826,5 @@
-Although it's not a must, we suggest that you always create BNC configuration files with the file name extension '.bnc'. -
- --We furthermore suggest for convenience reasons that you configure your system to automatically start BNC when you double-click a file with the file name extension '.bnc'. The following describes what to do on Windows systems to associate the BNC program to such configuration files: +Although it's not a must, we suggest that you always create BNC configuration files with the filename extension '.bnc'. +
+ ++We furthermore suggest for convenience reasons that you configure your system to automatically start BNC when you double-click a file with the filename extension '.bnc'. The following describes what to do on Windows systems to associate the BNC program to such configuration files:
@@ -4444,5 +4444,5 @@-The following table shows a list of options contained in BNC's configuration files (default file name: BNC.bnc). +The following table shows a list of options contained in BNC's configuration files (default filename: BNC.bnc).
@@ -4478,5 +4478,5 @@