-Federal Agency for Cartography and Geodesy (BKG)
-c/o Dr. Axel Rülke
-Department of Geodesy, Section Navigation
-Frankfurt, Germany
-[axel.ruelke@bkg.bund.de]
-
+
+ Federal Agency for Cartography and Geodesy (BKG) + c/o Dr. Axel Rülke + Department of Geodesy, Section Navigation + Frankfurt, Germany + [axel.ruelke@bkg.bund.de] ++ The software has been written by - - -
-Prof. Dr. Leos Mervart
-Czech Technical University (CTU)
-Department of Geodesy
-Prague, Czech Republic
+
+
+ Prof. Dr. Leos Mervart + Czech Technical University (CTU) + Department of Geodesy + Prague, Czech Republic +@@ -592,5 +592,5 @@
SSL communication may involve queries coming from the Ntrip Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab as follows:
-SSL Error -Server Certificate Issued by: -GNSS Data Center -BKG (Bundesamt fuer Geodaesie und Kartographie) -Cannot be verified - -The issuer certificate of a locally looked up certificate could not be found -The root CA certificate is not trusted for this purpose -No certificates could be verified + SSL Error + Server Certificate Issued by: + GNSS Data Center + BKG (Bundesamt fuer Geodaesie und Kartographie) + Cannot be verified + + The issuer certificate of a locally looked up certificate could not be found + The root CA certificate is not trusted for this purpose + No certificates could be verifiedTick 'Ignore SSL authorization errors' if you generally trust the server and don't want to be bothered with this. Note that SSL communication is usually done over port 443. @@ -1006,5 +1006,5 @@
-See BNC's command line option -nw for an auto-start of BNC in 'no window' mode. +See BNC's command line option '-nw' for an auto-start of BNC in 'no window' mode.
@@ -1016,5 +1016,5 @@ Data will be saved in blocks in the received format separated by ASCII time stamps like (example):-2010-08-03T18:05:28 RTCM3EPH RTCM_3 67 + 2010-08-03T18:05:28 RTCM3EPH RTCM_3 67@@ -1057,6 +1057,6 @@
-FRAN{ddd}{h}.{yy}O
-WETT{ddd}{h}.{yy}O
+ FRAN{ddd}{h}.{yy}O
+ WETT{ddd}{h}.{yy}O
@@ -1066,17 +1066,17 @@ 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 as
-FRAN{ddd}{h}_KFURT.{yy}O
-FRAN{ddd}{h}_CE.{yy}O
+ FRAN{ddd}{h}_KFURT.{yy}O
+ FRAN{ddd}{h}_CE.{yy}O
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 like
-BRUS{ddd}{h}_0.{yy}O
-BRUS{ddd}{h}_1.{yy}O
+ BRUS{ddd}{h}_0.{yy}O
+ BRUS{ddd}{h}_1.{yy}O
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
+ FRAN{ddd}{h}{mm}.{yy}O
@@ -1103,5 +1103,5 @@ 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 + ALGO00CAN_R_20121601000_01H_01S_MO.rnx@@ -1136,7 +1136,7 @@
-BRUS.skl -FRAN.skl -WETT.skl + BRUS.skl + FRAN.skl + WETT.skl
@@ -1281,5 +1281,5 @@ 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 + BRDC00DEU_S_20121600000_01D_MN.rnx@@ -1514,5 +1514,4 @@ > 2015 06 15 00 00 30.0000000 39 0.6 ... - @@ -1601,7 +1600,7 @@ BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged, see section on 'Command Line Options'. The syntax for that looks as follows -
---key <keyName> <keyValue> -
++ --key <keyName> <keyValue> +
where <keyName> stands for the name of an option contained in the configuration file and <keyValue> stands for the value you want to assign to it. This functionality may be helpful in the 'RINEX Editing & QC' context when running BNC on a routine basis for maintaining a RINEX file archive. @@ -1609,24 +1608,26 @@ The following example for a Linux platform calls BNC in 'no window' mode with a local configuration file 'rnx.conf' for concatenating four 15min RINEX files from station TLSE residing in the local directory to produce an hourly RINEX Version 3 file with 30 seconds sampling interval:
--./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key reqcOutObsFile tlse119b.12o --key reqcRnxVersion 3 --key reqcSampling 30 -
++ ./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key reqcOutObsFile tlse119b.12o --key reqcRnxVersion 3 --key reqcSampling 30 +
You may use asterisk '*' and/or question mark '?' wildcard characters as shown with the following globbing command line option to specify a selection of files in a local directory: -
-
---key reqcObsFile "tlse*"
-or:
---key reqcObsFile tlse\*
+
+ --key reqcObsFile "tlse*" +or: + --key reqcObsFile tlse\* +
The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no configuration options previously saved on disc are used:
--/home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key reqcPlotDir /home/user --nw -
- -The following Linux command line produces the same RINEX QC plots in interactive autoStart mode:
--/home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key --key startTab 4 --key autoStart 2 +
+ /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key reqcPlotDir /home/user --nw ++ +
The following Linux command line produces the same RINEX QC plots in interactive autoStart mode: +
++ /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key --key startTab 4 --key autoStart 2 +@@ -2284,11 +2285,11 @@
-Windows: COM1, COM2 -Linux: /dev/ttyS0, /dev/ttyS1 -FreeBSD: /dev/ttyd0, /dev/ttyd1 -Digital Unix: /dev/tty01, /dev/tty02 -HP-UX: /dev/tty1p0, /dev/tty2p0 -SGI/IRIX: /dev/ttyf1, /dev/ttyf2 -SunOS/Solaris: /dev/ttya, /dev/ttyb + Windows: COM1, COM2 + Linux: /dev/ttyS0, /dev/ttyS1 + FreeBSD: /dev/ttyd0, /dev/ttyd1 + Digital Unix: /dev/tty01, /dev/tty02 + HP-UX: /dev/tty1p0, /dev/tty2p0 + SGI/IRIX: /dev/ttyf1, /dev/ttyf2 + SunOS/Solaris: /dev/ttya, /dev/ttyb
@@ -2396,6 +2397,6 @@ Examples for command line parameter strings passed on to the advisory 'Script' are:
-FFMJ0 Begin_Outage 08-02-21 09:25:59 -FFMJ0 End_Outage 08-02-21 11:36:02 Begin was 08-02-21 09:25:59 + FFMJ0 Begin_Outage 08-02-21 09:25:59 + FFMJ0 End_Outage 08-02-21 11:36:02 Begin was 08-02-21 09:25:59@@ -2404,13 +2405,13 @@
-#!/bin/bash -sleep $((60*RANDOM/32767)) -cat > mail.txt <<EOF -Advisory Note to BNC User, -Please note the following advisory received from BNC. -Stream: $* -Regards, BNC -EOF -mail -s "NABU: $1" email@address < mail.txt + #!/bin/bash + sleep $((60*RANDOM/32767)) + cat > mail.txt <<EOF + Advisory Note to BNC User, + Please note the following advisory received from BNC. + Stream: $* + Regards, BNC + EOF + mail -s "NABU: $1" email@address < mail.txt@@ -2577,6 +2578,8 @@
Debugging
-Note that for debugging purposes BNC's real-time PPP functionality can also be used offline. Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Example:
-bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\RAW
+Note that for debugging purposes BNC's real-time PPP functionality can also be used offline. Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Example:
+
+ bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\RAW +Such a file (here: 'RAW') must be saved beforehand using BNC's 'Raw output file' option. @@ -2728,5 +2731,5 @@
-/Users/pppDir/PPP_${STATION}_${DATE}.log
+ /Users/pppDir/PPP_${STATION}_${DATE}.log
@@ -2807,5 +2810,5 @@
-/Users/pppDir/PPP_${STATION}_${DATE}.nmea
+ /Users/pppDir/PPP_${STATION}_${DATE}.nmea
@@ -2852,5 +2855,5 @@ BNC estimates the tropospheric delay according to equation
-T(z) = T_apr(z) + dT / cos(z) + T(z) = T_apr(z) + dT / cos(z)where T_apr is the a priori tropospheric delay derived from Saastamoinen model. @@ -2860,5 +2863,5 @@ You can specify the full path to daily SINEX Troposphere files to save troposphere parameters on disk, see https://igscb.jpl.nasa.gov/igscb/data/format/sinex_tropo.txt for a documentation of the file format. Example:
-/Users/pppDir/PPP_${STATION}${DOY}_${YY}.zpd
+ /Users/pppDir/PPP_${STATION}${DOY}_${YY}.zpd
In this '${STATION}' stands for the observation's mountpoint or RINEX file, '${DOY}' for the Day Of Year, and '${YY}' for the year. For a RINEX observations file 'CUT0' it would lead to a troposphere file named 'PPP_CUT01810.15.zpd' with the following contents (example):
@@ -3102,7 +3105,4 @@
Figure 25: BNC in 'Quick-Start' mode (PPP, Panel 2)
-2.13.3.NN Averaging - optional if XYZ is set
2.13.3.NN Maximal Solution Gap - optional if Quick-Start is set
@@ -3425,5 +3425,5 @@
-dC = (s - 1) / s * ρ / c + dC = (s - 1) / s * ρ / c
@@ -3612,5 +3612,9 @@
-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.
+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.
@@ -3986,12 +3990,12 @@
-Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging purposes. 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'. -
--In addition to reading processing options from the involved configuration file, BNC can optionally read all configuration options from command line. Running BNC with command line option 'help' +Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging purposes. It is also possible to introduce a specific configuration filename instead of using the default filename 'BNC.bnc'. The self-explaining contents of the configuration file can easily be edited. +
++In addition to reading processing options from the involved configuration file, BNC can optionally read any configuration option from command line. Running BNC with command line option 'help'
Example:
-bnc.exe --help
+ bnc.exe --help
@@ -3999,5 +4003,23 @@
-2.20.1 No Window Mode - optional
+Command line option '--version' lets BNC print its version number. +
+
+Example:
+ bnc.exe --version
+
+On systems which support graphics command line option '--display' forces BNC to present the BNC window on the specified display. +
+
+Example:
+ bnc.exe --display localhost:10.0
+
2.20.3 No Window Mode - optional
Apart from its regular windows mode, BNC can be started on all systems as a batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. @@ -4005,5 +4027,5 @@
Example:
-bnc.exe --nw
+ bnc.exe --nw
@@ -4017,30 +4039,30 @@
-#!/bin/bash - -# Save string localhost -echo "localhost" > /home/user/hosts - -# Start virtual X-Server, save process ID -/usr/bin/Xvfb :29 -auth /home/user/hosts -screen 0 1280x1024x8 & -psID=`echo $!` - -# Run BNC application with defined display variable -/home/user/BNC/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile ons12090.12o --key reqcNavFile brdc2090.12p --key reqcOutLogFile multi.txt --key reqcPlotDir /home/user --display localhost:29 --nw - -# BNC done, kill X-server process -kill $psID -- - + #!/bin/bash + + # Save string localhost + echo "localhost" > /home/user/hosts + + # Start virtual X-Server, save process ID + /usr/bin/Xvfb :29 -auth /home/user/hosts -screen 0 1280x1024x8 & + psID=`echo $!` + + # Run BNC application with defined display variable + /home/user/BNC/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile ons12090.12o --key reqcNavFile brdc2090.12p --key reqcOutLogFile multi.txt --key reqcPlotDir /home/user --display localhost:29 --nw + + # BNC done, kill X-server process + kill $psID + + +
Although BNC is primarily a real-time online tool, for debugging purposes it can be run offline to read data from a file previously saved through option 'Raw output file'. Enter the following command line option for that
---file <inputFileName> + --file <inputFileName>
and specify the full path to an input file containing previously saved data. Example:@@ -4050,10 +4072,10 @@
-2.20.3 Configuration File - optional
2.20.5 Configuration File - optional
Example:
-./bnc --conf MyConfig.bnc
+ ./bnc --conf MyConfig.bnc
@@ -4061,10 +4083,10 @@
-2.20.4 Configuration Options - optional
2.20.6 Configuration Options - optional
BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged. The command line syntax for that looks as follows
---key <keyName> <keyValue> + --key <keyName> <keyValue>
@@ -4072,11 +4094,25 @@
-bnc --nw --conf <confFileName> --key <keyName1> <keyValue1> --key <keyName2> <keyValue2> ... -
--Example: -
--./bnc --conf CONFIG.bnc --key proxyPort 8001 --key rnxIntr "1 day" + bnc --nw --conf <confFileName> --key <keyName1> <keyValue1> --key <keyName2> <keyValue2> ... +
++Configuration options which are part of the configuration files PPP section must be prefixed by 'PPP/'. As an example, option 'minObs' from the PPP section of the BNC configuration file would be specified as 'PPP/minObs' on a command line. +
++Values for configuration options can be introduced via command line exactly as they show up in the configuration file. However, any value containing one or more blank characters must be enclosed by quotation marks when specified on the command line. +
++Example command lines: +
+
+ (1) /Applications/bnc.app/Contents/MacOS/bnc -- version
+ (2) ./bnc --conf CONFIG.bnc --key proxyPort 8001 --key rnxIntr "1 day"
+ (3) D:\BKG\bnc.exe --conf C:\Users\weber\Desktop\BNC.bnc --file C:\Users\weber\Desktop\rawfile
+ (4) /home/weber/bin/bnc --conf /home/weber/MyConfigFile.bnc
+ (5) bnc --conf /Users/weber/.config/BKG/BNC.bnc -nw
+ (6) bnc --conf /dev/null --key startTab 4 --key reqcAction Edit/Concatenate --key reqcObsFile AGAR.15O --key reqcOutObsFile AGAR_X.15O --key reqcRnxVersion 2 --key reqcSampling 30 --key reqcV2Priority CWPX_?
+ (7) bnc --key mountPoints "//user:pass@mgex.igs-ip.net:2101/CUT07 RTCM_3.0 ETH 9.03 38.74 no 2;//user:pass@www.igs-ip.net:2101/FFMJ1 RTCM_3.1 DEU 50.09 8.66 no 2"
+ (8) bnc --key cmbStreams "CLK11 BKG 1.0;CLK93 CNES 1.0"
+ (9) bnc --key PPP/staTable "FFMJ1,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7777;CUT07,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7778"