Changeset 962 in ntrip for trunk/BNC/bnchelp.html
- Timestamp:
- Jul 23, 2008, 6:52:56 PM (17 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (13 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r955 r962 4 4 The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding and converting real-time GNSS data streams from NTRIP broadcasters like <u>http://www.euref-ip.net/home</u> or <u>http://www.igs-ip.net/home</u>. 5 5 </p> 6 6 7 <p> 7 8 BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of EUREF's Real-time GNSS Project (EUREF-IP, IP for Internet Protocol) and the Real-Time IGS Pilot Project (RTIGS). 8 9 </p> 10 9 11 <p> 10 12 BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, 32-bit Linux, 64-bit Linux (compiled using option -m32), Solaris, and Mac systems. We used the MinGW Version 5.3.1 compiler to create the Windows binary. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.3.2 are installed. 11 13 </p> 14 15 <p> 16 Please ensure that you have installed the latest version of BNC available from <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u>. We are continuously working on the program and would appreciate if you could send any comments, suggestions, or bug reports to [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]. 17 </p> 18 12 19 <h3>Contents</h3> 13 20 <p> … … 30 37 <li>generate high-rate RINEX Observation and Navigation files to support near real-time GNSS post-processing applications, and/or</li> 31 38 <li>generate ephemeris and synchronized observations epoch by epoch through an IP port to support real-time GNSS engines, and/or</li> 39 <li>generate clock and orbit corrections to broadcast ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers, and/or</li> 32 40 <li>monitor the performance of a network of real-time GNSS reference stations to generate advisory notes.</li> 33 41 </ul> … … 39 47 <ul> 40 48 <li>RTCM Version 2.x containing message types 18 and 19 (GPS and GLONASS), </li> 41 <li>RTCM Version 3.x containing message types 1002 (GPS, SBAS) or 1004 (GPS), 1010 or 1012 (GLONASS), 1019 or 1020 (broadcast ephemeris) </li>49 <li>RTCM Version 3.x containing message types 1002 (GPS, SBAS) or 1004 (GPS), 1010 or 1012 (GLONASS), 1019 or 1020 (broadcast ephemeris), 4056 and 4057 (tentative messages for orbit and clock corrections to broadcast ephemeris)</li> 42 50 <li>RTIGS containing GPS record types 200 (observations) and 300 (ephemeris).</li> 43 51 </ul> … … 692 700 </p> 693 701 <p> 694 Please ensure that you have installed the latest version of BNC available from <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u>. We are continuously working on the program and would appreciate if you could send any comments, suggestions, or bug reports to:695 </p>696 <p>697 702 Georg Weber<br> 698 703 Federal Agency for Cartography and Geodesy (BKG)<br> 699 704 Frankfurt, Germany<br> 700 euref-ip@bkg.bund.de or igs-ip@bkg.bund.de 705 [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de] 701 706 </p> 702 707 <p> … … 711 716 <p> 712 717 8.1. <a href=#history>History</a><br> 713 8.2. <a href=#ntrip>NTRIP</a><br> 714 8.2.1 <a href=#source>Source-table</a><br> 715 8.3. <a href=#rtcm>RTCM</a><br> 716 8.3.1 RTCM <a href=#rtcm2> Version 2.x</a><br> 717 8.3.2 RTCM <a href=#rtcm3> Version 3.x</a><br> 718 8.4. <a href=#rtigs>RTIGS</a><br> 719 8.4.1 <a href=#soc>SOC</a><br> 720 8.5. <a href=#config>Config File</a><br> 721 8.6. <a href=#links>Links</a><br> 718 8.2. <a href=#rtcm>RTCM</a><br> 719 8.2.1 <a href=#ntrip>NTRIP</a><br> 720 8.2.2 RTCM <a href=#rtcm2>Version 2.x</a><br> 721 8.2.3 RTCM <a href=#rtcm3>Version 3.x</a><br> 722 8.3. <a href=#rtigs>RTIGS</a><br> 723 8.3.1 <a href=#soc>SOC</a><br> 724 8.4. <a href=#config>Config File</a><br> 725 8.5. <a href=#links>Links</a><br> 722 726 </p> 723 727 … … 735 739 </p> 736 740 737 <p><a name="ntrip"><h4>8.2. NTRIP</h4></p> 741 <p><a name="rtcm"><h4>8.2. RTCM</h4></p> 742 743 <p> 744 The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional and educational organization. Special Committees provide a forum in which governmental and non-governmental members work together to develop technical standards and consensus recommendations in regard to issues of particular concern. RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication systems. The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards. Topics concerning Differential Global Navigation Satellite Systems (DGNSS) are handled by the Special Committee SC 104. 745 <p> 746 Personal copies of RTCM Recommended Standards can be ordered through <u>http://www.rtcm.org/orderinfo.php</u>. 747 </p> 748 749 <p><a name="ntrip"><h4>8.2.1 NTRIP</h4></p> 738 750 739 751 <p> … … 760 772 </p> 761 773 762 <p><a name="source"><h4>8.2.1 Source-table</h4></p>763 764 774 <p> 765 775 The NTRIP broadcaster maintains a source-table containing information on available NTRIP streams, networks of NTRIP streams and NTRIP broadcasters. The source-table is sent to an NTRIP client on request. Source-table records are dedicated to one of the following: Data Streams (record type STR), Casters (record type CAS), or Networks of streams (record type NET). … … 776 786 </p> 777 787 778 <p><a name="rtcm"><h4>8.3. RTCM</h4></p> 779 780 <p> 781 The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional and educational organization. Special Committees provide a forum in which governmental and non-governmental members work together to develop technical standards and consensus recommendations in regard to issues of particular concern. RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication systems. The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards. Topics concerning Differential Global Navigation Satellite Systems (DGNSS) are handled by the Special Committee SC 104. 782 <p> 783 Personal copies of RTCM Recommended Standards can be ordered through <u>http://www.rtcm.org/orderinfo.php</u>. 784 </p> 785 786 <p><a name="rtcm2"><h4>8.3.1 RTCM Version 2.x</h4></p> 788 789 <p><a name="rtcm2"><h4>8.2.2 RTCM Version 2.x</h4></p> 787 790 <p> 788 791 Transmitting GNSS carrier phase data can be done through RTCM Version 2.x messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are: … … 822 825 </ul> 823 826 824 <p><a name="rtcm3"><h4>8. 3.2RTCM Version 3.x</h4></p>827 <p><a name="rtcm3"><h4>8.2.3 RTCM Version 3.x</h4></p> 825 828 <p> 826 829 RTCM Version 3.x has been developed as a more efficient alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3.x standard is intended to correct these weaknesses. … … 850 853 </ul> 851 854 852 <p><a name="rtigs"><h4>8. 4. RTIGS</h4></p>855 <p><a name="rtigs"><h4>8.3. RTIGS</h4></p> 853 856 <p> 854 857 RTIGS stands for a data format and transport protocol for GPS observations. It was defined by the Real-Time IGS Working Group (RTIGS WG). Its definition is based on the SOC format. Every RTIGS record has one of the following numbers: … … 903 906 </p> 904 907 905 <p><a name="soc"><h4>8. 4.1 SOC</h4></p>908 <p><a name="soc"><h4>8.3.1 SOC</h4></p> 906 909 <p> 907 910 The SOC format has been designed in July 1999 by the Jet Propulsion Laboratory (JPL) and the California Institute of Technology (CalTech) to transport 1Hz GPS data with minimal bandwidth over the open Internet. SOC follows the 'little-endian' byte order meaning that the low-order byte of a number is stored in memory at the lowest address, and the high-order byte at the highest address. Because the transport layer is UDP, the format does not include sync bits, a checksum, or cyclic redundancy checksum (CRC). SOC allows to transport the GPS observable CA, P1, P2, L1, and L2, efficiently compressed down to 14 bytes with 1 mm range resolution and 0.02 mm phase resolution. SOC contains epochs for cycle slips, a stand-alone time-tag per epoch, a minimum representation of the receiver's clock solution, 3 SNR numbers, a unique site id, a modulo 12 hour sequence number and flags for receiver type and GPS health. SOC's simple structure comprises an 8 byte header, a 9 byte overhead for timetag, number of gps, etc., plus 21 data bytes per gps. … … 912 915 <p> 913 916 </p> 914 <p><a name="config"><h4>8. 5. Config File</h4></p>917 <p><a name="config"><h4>8.4. Config File</h4></p> 915 918 <p> 916 919 The following is an example for the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the retrieval of stream ACOR0 form www.euref-ip.net and FFMJ3 from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' : … … 949 952 </p> 950 953 951 <p><a name="links"><h3>8. 6Links</h3></p>954 <p><a name="links"><h3>8.5 Links</h3></p> 952 955 <table> 953 956 <tr></tr>
Note:
See TracChangeset
for help on using the changeset viewer.
