- Timestamp:
- Jun 15, 2015, 1:44:25 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r6895 r6902 657 657 </p> 658 658 <p> 659 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.659 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. 660 660 </p> 661 661 … … 712 712 <p><a name="rnxskl"><h4>3.4.5 Skeleton Extension - optional</h4></p> 713 713 <p> 714 Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. A HTTP link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <u>http://www.epncb.oma.be:80/stations/log/skl/brus.skl</u> for an example of a public RINEX header skeleton file for the Brussels EPN station.714 Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. A HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <u>http://www.epncb.oma.be:80/stations/log/skl/brus.skl</u> for an example of a public RINEX header skeleton file for the Brussels EPN station. 715 715 </p> 716 716 <p> … … 767 767 <p> 768 768 <pre> 769 OBSERVATION DATA M (M ixed) RINEX VERSION / TYPE770 DUND MARKER NAME 771 5 0212M003 MARKER NUMBER772 4635120796 TRIMBLE NETR9 1.15 REC # / TYPE / VERS 773 12626150 TRM41249.00 NONE ANT # / TYPE 774 - 4388121.1700 726671.0500 -4556535.6300 APPROX POSITION XYZ775 0.00 20 0.0000 0.0000 ANTENNA: DELTA H/E/N776 GeoNet Reception GNS OBSERVER / AGENCY 777 G 28 21C L1C D1C S1C C1W L1W D1W S1W C5X L5X D5X S5X C2WSYS / # / OBS TYPES778 L2W D2W S2W C2X L2X D2X S2XSYS / # / OBS TYPES779 R 16 C1C L1C D1C S1C C1P L1P D1P S1P C2P L2P D2P S2P C2CSYS / # / OBS TYPES780 L2C D2C S2CSYS / # / OBS TYPES781 S 12 C1C L1C D1C S1C C1W L1W D1W S1W C5I L5I D5I S5ISYS / # / OBS TYPES782 E 8 C1 L1 D1 S1 C5 L5 D5 S5SYS / # / OBS TYPES783 C 4 C2I L2I D2I S2ISYS / # / OBS TYPES784 J 12 C1C L1C D1C S1C C2 L2 D2 S2 C5 L5 D5 S5 SYS / # / OBS TYPES 785 PORTIONS OF THIS HEADER GENERATED BY BKG FROM COMMENT 786 SITELOG dund_20070806.log COMMENT 769 OBSERVATION DATA M (MIXED) RINEX VERSION / TYPE 770 CUT0 MARKER NAME 771 59945M001 MARKER NUMBER 772 5023K67889 TRIMBLE NETR9 5.01 REC # / TYPE / VERS 773 4928353386 TRM59800.00 SCIS ANT # / TYPE 774 -2364337.2699 4870285.5624 -3360809.8398 APPROX POSITION XYZ 775 0.0000 0.0000 0.0000 ANTENNA: DELTA H/E/N 776 gnss@curtin.edu.au CUT OBSERVER / AGENCY 777 C 10 C1I L1I D1I S1I C6I L6I S6I C7I L7I S7I SYS / # / OBS TYPES 778 E 13 C1X L1X D1X S1X C5X L5X S5X C7X L7X S7X C8X L8X S8X SYS / # / OBS TYPES 779 G 13 C1C L1C D1C S1C C2W L2W S2W C2X L2X S2X C5X L5X S5X SYS / # / OBS TYPES 780 J 19 C1C L1C D1C S1C C1X L1X S1X C1Z L1Z S1Z C2X L2X S2X SYS / # / OBS TYPES 781 C5X L5X S5X C6L L6L S6L SYS / # / OBS TYPES 782 R 13 C1C L1C D1C S1C C1P L1P S1P C2C L2C S2C C2P L2P S2P SYS / # / OBS TYPES 783 S 7 C1C L1C D1C S1C C5I L5I S5I SYS / # / OBS TYPES 784 PORTIONS OF THIS HEADER GENERATED BY THE IGS CB FROM COMMENT 785 SITELOG cut0_20150507.log COMMENT 786 END OF HEADER 787 787 </pre> 788 788 <p> … … 797 797 <p><a name="rnxscript"><h4>3.4.7 Script - optional</h4></p> 798 798 <p> 799 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 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). 800 800 </p> 801 801 <p> … … 830 830 <p><a name="rnxvers3"><h4>3.4.9 Version 3 - optional</h4></p> 831 831 <p> 832 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. 832 The default format for RINEX Observation files is RINEX Version 2.11. Select RINEX 'Version 3' if you would like to save RTCM Version 3 observation streams in RINEX Version 3 format. 833 </p> 834 835 <p> 836 Note that it is possible to force a RTCM Version 2 stream to be saved in RINEX Version 3 file format. However, this is not recommended because such stream can not be precisely mapped to RINEX Version 3 as the required information on tracking modes is no part of RTCM Version 2. 833 837 </p> 834 838
Note:
See TracChangeset
for help on using the changeset viewer.