Changeset 6853 in ntrip


Ignore:
Timestamp:
May 26, 2015, 4:43:47 PM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r6852 r6853  
    77<li><u>http://www.euref-ip.net/home</u>,</li>
    88<li><u>http://www.igs-ip.net/home</u>,</li>
    9 <li><u>http://products.igs-ip.net/home</u>, or</li>
     9<li><u>http://products.igs-ip.net/home</u>,</li>
    1010<li><u>http://mgex.igs-ip.net/home</u>. </li>
    1111</ul>
    … …  
    1313
    1414<p>
    15 BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive <u>http://software.rtcm-ntrip.org/svn/trunk/BNC.</u> Binaries for BNC are available for Windows, Linux, and Mac OS X systems. We used the MinGW Version 4.4.0 compiler to create the Windows binaries. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.7.3 or any later version are installed. Please ensure that you always use the latest version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u>. Note that static and shared builds of BNC are made available. A <u>static</u> build would be sufficient in case you don't want BNC to trace positions using Google Map (GM) or Open StreetMap (OSM). However, GM/OSM usage requires the QtWebKit library which can only be part of BNC builds from <u>shared</u> libraries. Using a shared library BNC build requires that you first install your own shared Qt library. The 'README.txt' file which comes with the BNC source code describes how to install Qt on Windows, Linux and Mac systems.
    16 </p>
    17 <p>
    18 Feel free to send us your comments, suggestions or bug reports. Your contribution would be appreciated.
     15BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive <u>http://software.rtcm-ntrip.org/svn/trunk/BNC.</u> Binaries for BNC are available for Windows, Linux, and Mac OS X systems. We used the MinGW Version 4.4.0 compiler to create the Windows binaries. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.8.4 or any later version are installed. Please ensure that you always use the latest precompiled version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u>. Note that static and shared builds of BNC are made available. A <u>static</u> build would be sufficient in case you don't want BNC to trace PPP results using Google Map (GM) or Open StreetMap (OSM). However, GM/OSM usage requires the QtWebKit library which can only be part of BNC builds from <u>shared</u> libraries. Using a shared library BNC build requires that you first install your own shared Qt library. The 'README.txt' file which comes with the BNC source code describes how to install Qt on Windows, Linux and Mac systems.
     16</p>
     17<p>
     18Feel free to send us comments, suggestions or bug reports. Your contribution would be appreciated.
    1919</p>
    2020
    … …  
    2929<p>
    3030<b><a name="authors">Authors</b><br>
    31 The BKG Ntrip Client (BNC) and its Qt graphic user interface has been developed for
     31The BKG Ntrip Client (BNC) and its Qt Graphical User Interface (GUI) has been developed for
    3232</p>
    3333<p>
    3434Federal Agency for Cartography and Geodesy (BKG)<br>
    35 c/o Georg Weber<br>
     35c/o Dr. Georg Weber<br>
    3636Department of Geodesy<br>
    3737Frankfurt, Germany<br>
    … …  
    4040
    4141<p>
    42 BNC has been written by
    43 </p>
    44 
    45 <p>
    46 Leos Mervart<br>
     42BNC was written by
     43</p>
     44
     45<p>
     46Prof. Dr. Leos Mervart<br>
    4747Czech Technical University (CTU)<br>
    4848Department of Geodesy<br>
    4949Prague, Czech Republic
    5050</p>
     51
     52<p>
     53While work on BNC startet in June 2005, Prof. Mervart's sole responsibility for the progam code and concept lasted till February 2015. Since March 2015 the expert in charge for further develoments is
     54</p>
     55
     56<p>
     57Dipl.-Ing. Andrea St&uuml;rze<br>
     58Federal Agency for Cartography and Geodesy (BKG)<br>
     59Department of Geodesy<br>
     60Section Navigation<br>
     61Frankfurt, Germany<br>
     62[andrea.stuerze@bkg.bund.de]
     63</p>
     64
    5165<p>
    5266BNC includes the following GNU GPL software components:
    … …  
    5771</p>
    5872<p>
    59 Note that some figures presented in this documentation show screenshots from earlier versions of BNC. If so then there is either no relevant change compared to the current appearance of BNC or no change at all.
     73Note that some figures presented in this documentation show screenshots from earlier versions of BNC. If so then there is either no relevant change compared to the current appearance of the program or no change at all.
    6074</p>
    6175
    … …  
    6478<ul>
    6579<li>
    66 Thomas Yan, Australian NSW Land and Property Information, proofread earlier versions of BNC's Help Contents. He also provides builds of BNC for Mac OS X systems.
     80Thomas Yan, Australian NSW Land and Property Information, proofread earlier versions of BNC's Help Contents. Up to Version 2.11 he also provides builds of BNC for Mac OS X systems.
    6781</li>
    6882<li>
    … …  
    97111<li>Retrieve real-time GNSS data streams via TCP directly from an IP address without using the NTRIP transport protocol;</li>
    98112<li>Retrieve real-time GNSS data streams from a local UDP or serial port without using the NTRIP transport protocol;</li>
     113<li>Plot stream distribution map from NTRIP Broadcaster source-tables;</li>
    99114<li>Generate RINEX Observation and Navigation files to support near real-time GNSS Post Processing applications;</li>
     115<li>Edit or concatenate RINEX files or carry out RINEX Quality Checks (QC);</li>
     116<li>Convert RINEX Version 2 to RINEX Version 3 and vice versa;</li>
     117<li>Compare SP3 files containing satellite orbit and clock data;</li>
     118<li>Generate orbit and clock corrections to Broadcast Ephemeris through an IP port to</li>
     119<ul>
     120<li>support real-time Precise Point Positioning on GNSS rovers;</li>
     121<li>support the (outside) combination of such streams as coming simultaneously from various correction providers;</li>
     122</ul>
    100123<li>Generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port to support real-time GNSS network engines;</li>
    101 <li>Generate orbit and clock corrections to Broadcast Ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers;</li>
    102 <li>Generate synchronized or unsynchronized orbit and clock corrections to Broadcast Ephemeris epoch by epoch through an IP port to support the (outside) combination of such streams as coming simultaneously from various correction providers;</li>
     124<li>Feed a stream into a GNSS receiver via serial communication link;</li>
    103125<li>Monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of outages or corrupted streams;</li>
    104 <li>Scan RTCM streams for incoming antenna information as well as observation types and message types and their repetition rates;</li>
    105 <li>Feed a stream into a GNSS receiver via serial communication link;</li>
    106 <li>Carry out real-time Precise Point Positioning to determine a GNSS rover position;</li>
     126<li>Scan RTCM streams for incoming antenna information as well as observation types and message types and their repetition rates and latencies;</li>
     127<li>Carry out real-time Precise Point Positioning to determine GNSS rover positions;</li>
     128<li>Plot positions derived via PPP from RTCM streams or RINEX files on maps from Google Map or Open StreetMap;</li>
    107129<li>Simultaneously process several Broadcast Correction streams to produce, encode and upload combined Broadcast Corrections;</li>
    108 <li>Upload a Broadcast Ephemeris stream in RTCM Version 3 format;</li>
    109130<li>Read GNSS orbits and clocks in a plain ASCII format from an IP port. They can be produced by a real-time GNSS engine such as RTNET and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. BNC will then</li>
    110131<ul>
    … …  
    115136<li>Log the Broadcast Corrections as SP3 files for further processing using other tools than BNC;</li>
    116137</ul>
    117 <li>Edit or concatenate RINEX files or check their quality;</li>
    118 <li>Plot stream distribution map from NTRIP Broadcaster source-tables;</li>
    119 <li>Plot positions derived from RTCM streams or RINEX files on maps from Google Map or Open StreetMap.</li>
     138<li>Upload a Broadcast Ephemeris stream in RTCM Version 3 format;</li>
    120139</ul>
    121140</p>
    … …  
    140159<p><a name="suppGNSS"><h3>1.1 Supported Systems</h3></p>
    141160<p>
    142 BNC is continuously completed in order to support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are so far supported by particular applications when using the latest BNC version. Applications fields named here are:
     161BNC is permanently completed to finally support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are so far supported by particular applications when using the latest BNC version. Application areas named here are:
    143162<ul>
    144163<li>Decoding of RTCM or RTNET streams</li>
    … …  
    147166<li>Upload of SSR and ephemeris messages</li>
    148167<li>PPP (Precise Point Positioning)</li>
    149 <li>Combination/merging of SSR or ephemeris messages from various real-time sources</li>
    150 </ul>
    151 The table mentions if the message implementation in BNC could so far only be based on a 'RTCM Proposal'.
    152 </p>
    153 <p><u>Table:</u> Status of RTCM Version 3 message implementation in BNC supporting various GNSS systems</p>
     168<li>Combining/merging SSR or ephemeris messages from various real-time sources</li>
     169</ul>
     170The table mentions if a message implementation in BNC could so far only be based on a 'RTCM Proposal'.
     171</p>
     172<p><u>Table:</u> Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</p>
    154173
    155174<p></p>
    156175<table border="1" rules="rows" frame="box" bgcolor="#FFF5EE" style="font-size:13">
    157176
    158 <tr><td><b>Message<br>Type #</b></td> <td><b>Description</b></td> <td><b>System</b></td> <td><b>RTCM<br>Proposal&nbsp;</b></td> <td><b>Decoding&nbsp;</b></td> <td><b>&nbsp;RINEX/&nbsp;<br>&nbsp;SP3</b></td> <td><b>Encoding&nbsp;</b></td> <td><b>Upload&nbsp;</b></td> <td><b>&nbsp;PPP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b></td> <td><b>Combin.&nbsp;</b></td> </tr>
    159 
    160 <tr> <td><b><br>General</b></td> <td></td> <td></td> <td></td> <td></td> <td></td> <td></td> </tr>
     177<tr><td><b>Message<br>Type #</b></td> <td><b>Description</b></td> <td><b>GNSS<br>System</b></td> <td><b>RTCM<br>Proposal&nbsp;</b></td> <td><b>Decoding&nbsp;</b></td> <td><b>&nbsp;RINEX/&nbsp;<br>&nbsp;SP3</b></td> <td><b>Encoding&nbsp;</b></td> <td><b>Upload&nbsp;</b></td> <td><b>&nbsp;PPP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b></td> <td><b>Combin.&nbsp;</b></td> </tr>
     178
     179<tr> <td><b><br>General</b></td> <td></td>             <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    161180<tr> <td>1005,1006</td> <td>Station</td>               <td> </td>             <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    162181<tr> <td>1007,1008</td> <td>Antenna</td>               <td> </td>             <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    … …  
    164183<tr> <td>1013</td>      <td>System Parameters</td>     <td> </td>             <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    165184
    166 <tr> <td><b><br>Navigation</b></td> <td></td> <td></td> <td></td> <td></td> <td></td> <td></td> </tr>
     185<tr> <td><b><br>Navigation</b></td> <td></td>          <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    167186<tr> <td>1019</td> <td>Ephemeris</td>                  <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
    168187<tr> <td>1020</td> <td>Ephemeris</td>                  <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
    … …  
    173192<tr> <td>63</td>   <td>Ephemeris</td>                  <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td> </td> </tr>
    174193
    175 <tr> <td><b><br>Observation</b></td> <td></td> <td></td> <td></td> <td></td> <td></td> <td></td> </tr>
     194<tr> <td><b><br>Observation</b></td> <td></td>         <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    176195<tr> <td>1001-4</td>  <td>Conventional Messages</td>   <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
    177196<tr> <td>1009-12</td> <td>Conventional Messages</td>   <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
    178197
    179 <tr> <td><b><br>Observation</b></td> <td></td> <td></td> <td></td> <td></td> <td></td> <td></td> </tr>
     198<tr> <td><b><br>Observation</b></td> <td></td>         <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    180199<tr> <td>1071-77</td> <td>Multiple Signal Message</td> <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
    181200<tr> <td>1081-87</td> <td>Multiple Signal Message</td> <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
    … …  
    185204<tr> <td>1121-27</td> <td>Multiple Signal Message</td> <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    186205
    187 <tr> <td><b><br>SSR I</b></td> <td></td> <td></td> <td></td> <td></td> <td></td> <td></td> </tr>
     206<tr> <td><b><br>SSR I</b></td> <td></td>               <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    188207<tr> <td>1057</td> <td>Orbit Corrections</td>          <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
    189208<tr> <td>1063</td> <td>Orbit Corrections</td>          <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
    … …  
    221240<tr> <td>1261</td> <td>Comb. Orbits & Clocks</td>      <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td> </td> </tr>
    222241
    223 <tr> <td><b><br>SSR II</b></td> <td></td> <td></td> <td></td> <td></td> <td></td> <td></td> </tr>
     242<tr> <td><b><br>SSR II</b></td> <td></td>               <td></td>             <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    224243<tr> <td>1264</td> <td>VTEC</td>                       <td> </td>             <td>x</td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
    225244<tr> <td>1265</td> <td>Phase Biases</td>               <td>GPS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td> </td> </tr>
Note: See TracChangeset for help on using the changeset viewer.