Index: /trunk/BNC/src/bnchelp.html
===================================================================
--- /trunk/BNC/src/bnchelp.html (revision 9184)
+++ /trunk/BNC/src/bnchelp.html (revision 9185)
@@ -107,7 +107,8 @@
2.4.5 Skeleton Extension
2.4.6 Skeleton Mandatory
- 2.4.7 Script
+ 2.4.7 Skeleton Directory
+ 2.4.8 Script
2.4.9 Version 3
- 2.4.8 Version 2
+ 2.4.10 Version 2
2.5 RINEX Ephemeris
2.5.1 Directory
@@ -210,5 +211,4 @@
2.14.1.3 Maximal Residuum
2.14.1.4 Sampling
- 2.14.1.5 Use GLONASS
2.15 Upload Corrections
2.15.1 Add, Delete Row
@@ -1426,32 +1426,5 @@
-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 (4-Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named
- -- FRAN{ddd}{h}.{yy}O - WETT{ddd}{h}.{yy}O --
-where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year. -
--If there is more than one stream with identical 4-Char 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 --
-If several streams show up with 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 e.g. to hourly RINEX Version 2 Observation files like
-- 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 e.g.
-- FRAN{ddd}{h}{mm}.{yy}O --
-where 'mm' is the starting minute within the hour. +The default for RINEX filenames in BNC follows the convention of RINEX Version 3. However, the software provides options to alternatively follow the filename convention of RINEX Version 2.
@@ -1482,4 +1455,35 @@ ++RINEX Version 2 filenames are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4-Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named
+ ++ FRAN{ddd}{h}.{yy}O + WETT{ddd}{h}.{yy}O ++
+where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year. +
++If there is more than one stream with identical 4-Char 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 ++
+If several streams show up with 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 e.g. to hourly RINEX Version 2 Observation files like
++ 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 e.g.
++ FRAN{ddd}{h}{mm}.{yy}O ++
+where 'mm' is the starting minute within the hour. +
+@@ -1512,10 +1516,10 @@
-When producing RINEX Observation files from mountpoints (examples) 'BRUX0', 'BRUX00BEL0', and 'WTZR_RTCM3', the following skeleton filenames would be accepted -
-- BRUX.skl (4 char corresponding to RINEX version 2) +When producing RINEX Observation files from mountpoints (examples) 'BRUX00BEL0', 'WTZR_RTCM3', and 'BRUX0', the following skeleton filenames would be accepted + +BRUX00BEL.skl (9 char corresponding to RINEX version 3) WTZR_RTCM.skl (9 char corresponding to RINEX version 3) + BRUX.skl (4 char corresponding to RINEX version 2)@@ -1587,5 +1591,11 @@
-2.4.7 Script - optional
+2.4.7 Skeleton Directory - optional
++Here you can specify the path, where local skeleton files are located. If no directory is specified, the path is assumed to where the RINEX Observation files will stored. +
+ + +2.4.8 Script - optional
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 to such script/batch file. 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). @@ -1598,5 +1608,5 @@
-2.4.8 Version 3 - optional
+2.4.9 Version 3 - optional
The default format for RINEX Observation files is RINEX Version 3. There is nothing to activate in addition to save RTCM Version 3 observation streams in RINEX Version 3 format. @@ -1607,5 +1617,5 @@
-2.4.9 Version 2 - optional
+2.4.10 Version 2 - optional
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 can be setup to produce data files in RINEX Version 2.11 format: @@ -1660,18 +1670,15 @@
+Regarding RINEX Version 3 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, BDS, and IRNSS gathered in one Navigation file. +
++The following is an example for a RINEX Version 3 Navigation filename. The file contains one day's data. 'MN' stands for 'Multi Constellation Navigation' data. +
+ BRDC00DEU_S_20121600000_01D_MN.rnx ++ + +For RINEX Version 2 Navigation files the last character is 'N' or 'G' for GPS or GLONASS ephemeris in two separate files. -
--Regarding RINEX Version 3 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, BDS, and IRNSS gathered in one Navigation file. -
--The following is an example for a RINEX Version 3 Navigation filename. The file contains one day's data. 'MN' stands for 'Multi Constellation Navigation' data. -
- BRDC00DEU_S_20121600000_01D_MN.rnx -- - --Note that streams dedicated to carry Broadcast Ephemeris messages in RTCM Version 3 format in high repetition rates are listed on http://igs.bkg.bund.de/ntrip/ephemeris.
@@ -3960,9 +3967,4 @@Specify a combination sampling interval. Orbit and clock corrections will be produced following that interval. A value of 10 sec may be an appropriate choice.
-2.14.1.5 Use GLONASS - optional
--You may tick the 'Use GLONASS' option in case you want to produce a GPS plus GLONASS combination and both systems are supported by the Broadcast Correction streams participating in the combination. -
-2.15 Upload Corrections
@@ -5107,4 +5109,5 @@ rnxSampl {File sampling rate [integer number of seconds: 0,5|10|15|20|25|30|35|40|45|50|55|60]} rnxSkel {RINEX skeleton file extension [character string]} + rnxSkelPath {Directory for local skeleton files [character string]}\n" rnxOnlyWithSKL {Using RINEX skeleton file is mandatory [integer number: 0=no,2=yes]} rnxScript {File upload script, full path [character string]} @@ -5247,5 +5250,4 @@ cmbMaxres {Clock outlier residuum threshold in meters [floating-point number] cmbSampl {Clock sampling rate [integer number of seconds: 10|20|30|40|50|60]} - cmbUseGlonass {Use GLONASS in combination [integer number: 0=no,2=yes] Upload Corrections Panel keys: