Changeset 7216 in ntrip for trunk/BNC/src/bnchelp.html
- Timestamp:
- Aug 18, 2015, 9:31:46 AM (9 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (32 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7214 r7216 370 370 <p><a name="optconfig"><h3>2.1 Configuration Management</h3></p> 371 371 <p> 372 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 373 <p> 374 The default file 372 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'.</p> 373 <p> 374 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. 375 375 </p> 376 376 … … 427 427 3.3.5. <a href=#rawout>Raw Output File</a><br> 428 428 3.4. <a href=#rinex>RINEX Observations</a><br> 429 3.4.1. <a href=#rnxname>File Names</a><br>429 3.4.1. <a href=#rnxname>Filenames</a><br> 430 430 3.4.2. <a href=#rnxdir>Directory</a><br> 431 431 3.4.3. <a href=#rnxinterval>File Interval</a><br> … … 436 436 3.4.8. <a href=#rnxvers2>Version 2</a><br> 437 437 3.4.9. <a href=#rnxvers3>Version 3</a><br> 438 3.4.10. <a href=#rnxvers3File>Version 3 File Names</a><br>438 3.4.10. <a href=#rnxvers3File>Version 3 Filenames</a><br> 439 439 3.5. <a href=#ephemeris>RINEX Ephemeris</a><br> 440 440 3.5.1. <a href=#ephdir>Directory</a><br> … … 442 442 3.5.3. <a href=#ephport>Port</a><br> 443 443 3.5.4. <a href=#ephvers>Version</a><br> 444 3.5.5. <a href=#ephversFile>Version 3 File Names</a><br>444 3.5.5. <a href=#ephversFile>Version 3 Filenames</a><br> 445 445 3.6. <a href=#reqc>RINEX Editing & QC</a><br> 446 446 3.6.1 <a href=#reqcact>Action</a><br> … … 756 756 <p><u>Figure 8:</u> BNC translating incoming observation streams to 15 min RINEX Version 3 Observation files.</p> 757 757 758 <p><a name="rnxname"><h4>3.4.1 RINEX File Names</h4></p>759 <p> 760 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 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</p>758 <p><a name="rnxname"><h4>3.4.1 RINEX Filenames</h4></p> 759 <p> 760 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</p> 761 761 762 762 <pre> … … 768 768 </p> 769 769 <p> 770 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 770 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</p> 771 771 <pre> 772 772 FRAN{ddd}{h}_KFURT.{yy}O … … 774 774 </pre> 775 775 <p> 776 If several streams show exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the file 776 If several streams show exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the filename leading i.e. to hourly RINEX Version 2 Observation files like</p> 777 777 <pre> 778 778 BRUS{ddd}{h}_0.{yy}O … … 780 780 </pre> 781 781 <p> 782 Note that RINEX Version 2 file names for all intervals less than 1 hour follow the filename convention for 15 minutes RINEX Version 2 Observation files i.e.</p>782 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.</p> 783 783 <pre> 784 784 FRAN{ddd}{h}{mm}.{yy}O … … 789 789 790 790 <p> 791 In case of RINEX Version 3 file 791 In case of RINEX Version 3 filenames, the following convention holds: 792 792 793 793 <p> … … 805 805 </p> 806 806 <p> 807 Example for Mixed RINEX Version 3 GNSS observation file 807 Example for Mixed RINEX Version 3 GNSS observation filename, file containing 1 hour of data, one observation every second, 'MO' standing for 'Mixed Observations': 808 808 <pre> 809 809 ALGO00CAN_R_20121601000_01H_01S_MO.rnx … … 811 811 </p> 812 812 <p> 813 Note that file 813 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. 814 814 </p> 815 815 … … 837 837 </p> 838 838 <p> 839 When producing RINEX Observation files from mountpoints (examples) 'BRUS0', 'FRANKFURT'; and 'WETTZELL' the following skeleton file 839 When producing RINEX Observation files from mountpoints (examples) 'BRUS0', 'FRANKFURT'; and 'WETTZELL' the following skeleton filenames would be accepted 840 840 </p> 841 841 <pre> … … 956 956 </p> 957 957 958 <p><a name="rnxvers3File"><h4>3.4.10 Version 3 File Names - optional</h4></p>959 <p> 960 Tick check box 'Version 3 file names' to let BNC create so-called extended filenames following the RINEX Version 3 standard.961 </p> 962 <p>Default is an empty check box, meaning to still use file 958 <p><a name="rnxvers3File"><h4>3.4.10 Version 3 Filenames - optional</h4></p> 959 <p> 960 Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. 961 </p> 962 <p>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. 963 963 </p> 964 964 965 965 <p><a name="ephemeris"><h4>3.5. RINEX Ephemeris</h4></p> 966 966 <p> 967 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'.967 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'. 968 968 </p> 969 969 <p> … … 974 974 </p> 975 975 <p> 976 The following is an example for a RINEX Version 3 Navigation file 976 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. 977 977 <pre> 978 978 BRDC00DEU_S_20121600000_01D_MN.rnx … … 1010 1010 </p> 1011 1011 1012 <p><a name="ephversFile"><h4>3.5.5 Version 3 File Names - optional</h4></p>1013 <p> 1014 Tick check box 'Version 3 file names' to let BNC create so-called extended filenames following the RINEX Version 3 standard.1015 </p> 1016 <p>Default is an empty check box, meaning to still use file 1012 <p><a name="ephversFile"><h4>3.5.5 Version 3 Filenames - optional</h4></p> 1013 <p> 1014 Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. 1015 </p> 1016 <p>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. 1017 1017 </p> 1018 1018 … … 1232 1232 <p><a name="reqcdir"><h4>3.6.6 Directory for Plots - optional if 'Action' is set to 'Analyze'</h4></p> 1233 1233 <p> 1234 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 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.1234 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. 1235 1235 </p> 1236 1236 … … 1520 1520 1521 1521 <p> 1522 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 filename suffix which is set to 'C'.1522 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'. 1523 1523 </p> 1524 1524 … … 2369 2369 </pre> 2370 2370 <p> 2371 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 2371 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. 2372 2372 </p> 2373 2373 … … 3275 3275 3276 3276 <p><a name="upsp3"><h4>3.15.5 SP3 File - optional</h4></p> 3277 <p>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:<br>/home/user/BNC${GPSWD}.sp3<br>Note that '${GPSWD}' produces the GPS Week and Day number in the file 3277 <p>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:<br>/home/user/BNC${GPSWD}.sp3<br>Note that '${GPSWD}' produces the GPS Week and Day number in the filename.</p> 3278 3278 <p> 3279 3279 Default is an empty option field, meaning that you don't want BNC to save the uploaded stream contents in daily SP3 files. … … 3283 3283 </p> 3284 3284 <p> 3285 The file names for the daily SP3 files follow the convention for SP3 file names. 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.3285 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. 3286 3286 </p> 3287 3287 <p> … … 3298 3298 </p> 3299 3299 <p> 3300 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:<br>/home/user/BNC${GPSWD}.clk<br>Note that '${GPSWD}' produces the GPS Week and Day number in the file 3300 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:<br>/home/user/BNC${GPSWD}.clk<br>Note that '${GPSWD}' produces the GPS Week and Day number in the filename. 3301 3301 </p> 3302 3302 <p> … … 3416 3416 </li> 3417 3417 <li> 3418 In case you need to log the raw data as is, BNC allows users to by-pass its decoders and directly save the input in daily logfiles. To do this, specify the decoder string as 'ZERO'. The generated file 3418 In case you need to log the raw data as is, BNC allows users to by-pass its decoders and directly save the input in daily logfiles. To do this, specify the decoder string as 'ZERO'. The generated filenames are created from the characters of the streams mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save the raw data in a file named WTZZ0_070329. 3419 3419 </li> 3420 3420 <li> … … 3656 3656 <p><a name="cmd"><h4>3.20. Command Line Options</h4></p> 3657 3657 <p> 3658 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 3658 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'. 3659 3659 </p> 3660 3660 … … 3711 3711 3712 3712 <p><a name="conffile"><h4>3.20.3 Configuration File - optional</h4></p> 3713 The default configuration file name is 'BNC.bnc'. You may change this name at startup time using the command line option '--conf <<u>confFileName</u>>'. This allows running several BNC jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> stands either for the full path to a configuration file or just for a filename. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNC is started.3713 The default configuration filename is 'BNC.bnc'. You may change this name at startup time using the command line option '--conf <<u>confFileName</u>>'. This allows running several BNC jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> stands either for the full path to a configuration file or just for a filename. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNC is started. 3714 3714 </p> 3715 3715 <p> … … 3826 3826 <tr> 3827 3827 <td>Nov 2009 </td><td>Version 1.7 </td> 3828 <td>[Bug] RINEX Navigation file format<br> [Add] Upgrade to Qt Version 4.5.2<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port<br> [Add] Show broadcaster table from www.rtcm-ntrip.org<br> [Add] Enable/disable panel widgets<br> [Add] User defined configuration file 3828 <td>[Bug] RINEX Navigation file format<br> [Add] Upgrade to Qt Version 4.5.2<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port<br> [Add] Show broadcaster table from www.rtcm-ntrip.org<br> [Add] Enable/disable panel widgets<br> [Add] User defined configuration filename<br> [Mod] Switch to configuration files in ini-Format<br> [Add] Daily logfile rotation<br> [Add] Read from TCP/IP port, by-pass NTRIP transport protocol<br> [Add] Save NMEA messages coming from rover<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Read from serial port, by-pass NTRIP transport protocol<br> [Mod] Update of SSR messages following RTCM 091-2009-SC104-542<br> [Add] Read from UPD port, by-pass NTRIP transport protocol<br> [Mod] Output format of Broadcast Corrections<br> [Add] Throughput plot<br> [Add] Latency plot</td> 3829 3829 </tr> 3830 3830 … … 3891 3891 <tr> 3892 3892 <td>Dec 2013 </td><td>Version 2.10 </td> 3893 <td>[Add] Started work on new version in Aug 2013<br>[Bug] Clock RINEX und SP3 file generation on Windows systems<br>[Bug] Broadcast Ephemeris generation<br>[Add] Transformation ITRF2008 to NAD83 and DREF91<br>[Add] CodeBias added to RTNET stream format<br>[Bug] GPS L2 in 'Feed Engine' output<br>[Mod] Made C1 in BeiDou default observation type instead of C2<br>[Add] Feed engine output sorted per stream<br>[Add] Feed engine output file 3893 <td>[Add] Started work on new version in Aug 2013<br>[Bug] Clock RINEX und SP3 file generation on Windows systems<br>[Bug] Broadcast Ephemeris generation<br>[Add] Transformation ITRF2008 to NAD83 and DREF91<br>[Add] CodeBias added to RTNET stream format<br>[Bug] GPS L2 in 'Feed Engine' output<br>[Mod] Made C1 in BeiDou default observation type instead of C2<br>[Add] Feed engine output sorted per stream<br>[Add] Feed engine output filename change on-the-fly<br>[Add] 'Append files' option for RINEX observation files<br>[Mod] Broadcast Corrections ASCII file output for message 1058 & 1064 modified<br>[Bug] GPS L2 phase data in RINEX2<br>[Bug] GLONASS frequency numbers<br>[Add] RTCM v3 Galileo Broadcast Ephemeris message 1046<br>[Add] Reset ambiguities in PPP when orbit/clock correction IDs change<br>[Add] Satellite clock offsets are reset in adjustment for combination when orbit/clock correction IDs change<br>[Add] Version 2.10 published</td> 3894 3894 </tr> 3895 3895 … … 4216 4216 </ul> 4217 4217 <p> 4218 Although it's not a must, we suggest that you always create BNC configuration files with the file 4219 </p> 4220 4221 <p> 4222 We furthermore suggest for convenience reasons that you configure your system to automatically start BNC when you double-click a file with the file 4218 Although it's not a must, we suggest that you always create BNC configuration files with the filename extension '.bnc'. 4219 </p> 4220 4221 <p> 4222 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: 4223 4223 </p> 4224 4224 … … 4444 4444 4445 4445 <p> 4446 The following table shows a list of options contained in BNC's configuration files (default file 4446 The following table shows a list of options contained in BNC's configuration files (default filename: BNC.bnc). 4447 4447 </p> 4448 4448 … … 4478 4478 <tr><td>rnxV2Priority</td><td>Signal priority</td></tr> 4479 4479 <tr><td>rnxV3</td><td>Version 3</td></tr> 4480 <tr><td>rnxV3filenames</td><td>Version 3 file 4480 <tr><td>rnxV3filenames</td><td>Version 3 filenames</td></tr> 4481 4481 4482 4482 <tr><td><br><b>RINEX Ephemeris Panel</b></td><td><br><b>Meaning</b></td></tr> … … 4485 4485 <tr><td>outEphPort</td><td>Port</td></tr> 4486 4486 <tr><td>ephV3</td><td>Version 3</td></tr> 4487 <tr><td>ephV3filenames</td><td>Version 3 file 4487 <tr><td>ephV3filenames</td><td>Version 3 filenames</td></tr> 4488 4488 4489 4489 <tr><td><br><b>RINEX Editing and QC Panel</b></td><td><br><b>Meaning</b></td></tr> … … 4548 4548 <tr><td>serialStopBits</td><td>Stop bits</td></tr> 4549 4549 <tr><td>serialAutoNMEA</td><td>NMEA</td></tr> 4550 <tr><td>serialFileNMEA</td><td>NMEA file 4550 <tr><td>serialFileNMEA</td><td>NMEA filename</td></tr> 4551 4551 <tr><td>serialHeightNMEA</td><td>Height</td></tr> 4552 4552 … … 4573 4573 <tr><td>antexFile</td><td>ANTEX file</td></tr> 4574 4574 <tr><td>nmeaFile</td><td>NMEA output file</td></tr> 4575 <tr><td>snxtroFile</td><td>SINEX troposphere output file 4575 <tr><td>snxtroFile</td><td>SINEX troposphere output filename</td></tr> 4576 4576 <tr><td>snxtroSampl</td><td>SINEX troposphere sampling rage</td></tr> 4577 4577
Note:
See TracChangeset
for help on using the changeset viewer.
