Changeset 7226 in ntrip


Ignore:
Timestamp:
Aug 18, 2015, 10:37:01 AM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r7216 r7226  
    44
    55<p>
    6 The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing or analyzing real-time GNSS data streams applying the 'Networked Transport of RTCM via Internet Protocol' (Ntrip) standard. It has been developed within the framework of the IAG sub-commission for Europe (EUREF) and the International GNSS Service (IGS). Although meant as a real-time tool, it comes with some Post Processing functionality. You may like to use it for data coming from NTRIP Broadcasters like
     6The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing or analyzing real-time GNSS data streams applying the 'Networked Transport of RTCM via Internet Protocol' (Ntrip) standard. It has been developed within the framework of the IAG sub-commission for Europe (EUREF) and the International GNSS Service (IGS). Although meant as a real-time tool, it comes with some Post Processing functionality. You may like to use it for data coming from Ntrip Broadcasters like
    77<ul>
    88<li><u>http://www.euref-ip.net/home</u>,</li>
    … …  
    4444
    4545<p>
    46 Prof. Mervart started working on BNC in June 2005. His sole responsibility for writing the program code ended February 2015. Since March 2015 the expert in charge at BKG for further BNC programming is Dipl.-Ing. Andrea St&uuml;rze [andrea.stuerze@bkg.bund.de].
     46Prof. Mervart started working on BNC in 2005. His sole responsibility for writing the program code ended February 2015. Since March 2015 the expert in charge at BKG for further BNC programming is Dipl.-Ing. Andrea St&uuml;rze [andrea.stuerze@bkg.bund.de].
    4747</p>
    4848
    … …  
    112112<tr><td>7</td><td>BNC's 'Network' panel configured to ignore eventually occurring SSL error messages</td><td>3.2.2</td></tr>
    113113<tr><td>8</td><td>BNC translating incoming streams to 15 min RINEX Version 3 files</td><td>3.4</td></tr>
    114 <tr><td>9</td><td>Example for 'RINEX Editing Options' window</td><td>3.6.7</td></tr>
    115 <tr><td>10</td><td>Example for RINEX file concatenation with BNC</td><td>3.6.7</td></tr>
    116 <tr><td>11</td><td>Example for creating RINEX quality check analysis graphics output with BNC</td><td>3.6.7</td></tr>
    117 <tr><td>12</td><td>Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC</td><td>3.6.7</td></tr>
    118 <tr><td>13</td><td>Sky plot examples for multipath, part of RINEX quality check analysis with BNC</td><td>3.6.7</td></tr>
    119 <tr><td>14</td><td>Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC</td><td>3.6.7</td></tr>
    120 <tr><td>15</td><td>BNC configuration example for comparing two SP3 files with satellite orbit and clock data</td><td>3.7.3</td></tr>
    121 <tr><td>16</td><td>BNC configuration example for pulling, saving and output of Broadcast Corrections</td><td>3.8.3</td></tr>
    122 <tr><td>17</td><td>Synchronized BNC output via IP port to feed a GNSS real-time engine</td><td>3.9</td></tr>
    123 <tr><td>18</td><td>Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams</td><td>3.10</td></tr>
    124 <tr><td>19</td><td>BNC pulling a VRS stream to feed a serial connected RTK rover</td><td>3.10</td></tr>
    125 <tr><td>20</td><td>RTCM message numbers, latencies and observation types</td><td>3.12</td></tr>
    126 <tr><td>21</td><td>Real-time Precise Point Positioning with BNC, PPP Panel 1</td><td>3.13.1</td></tr>
    127 <tr><td>22</td><td>Precise Point Positioning with BNC, PPP Panel 2</td><td>3.13.2</td></tr>
    128 <tr><td>23</td><td>Precise Point Positioning with BNC, PPP Panel 3</td><td>3.13.3</td></tr>
    129 <tr><td>24</td><td>BNC in 'Quick-Start' mode (PPP, Panel 2)</td><td>3.13.3.8</td></tr>
    130 <tr><td>25</td><td>Track of positions from BNC with Google Maps in the background</td><td>3.13.4.3</td></tr>
    131 <tr><td>26</td><td>Example for a background map from Google Maps and OpenStreetMap (OSM) resources</td><td>3.13.4.3.1</td></tr>
    132 <tr><td>27</td><td>BNC combining Broadcast Correction streams</td><td>3.14.1.1</td></tr>
    133 <tr><td>28</td><td>BNC uploading the combined Broadcast Corrections stream</td><td>3.14.1.1</td></tr>
    134 <tr><td>29</td><td>'INTERNAL' PPP with BNC using combined Broadcast Corrections stream</td><td>3.14.1.1</td></tr>
    135 <tr><td>30</td><td>Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'</td><td>3.15.3</td></tr>
    136 <tr><td>31</td><td>Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster</td><td>3.15.9</td></tr>
    137 <tr><td>32</td><td>Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster</td><td>3.16.3</td></tr>
    138 <tr><td>33</td><td>Bandwidth consumption of incoming streams</td><td>3.18.2</td></tr>
    139 <tr><td>34</td><td>Latency of incoming streams</td><td>3.18.3</td></tr>
    140 <tr><td>35</td><td>Time series plot of PPP session</td><td>3.18.4</td></tr>
    141 <tr><td>36</td><td>Steam input communication links</td><td>3.19</td></tr>
    142 <tr><td>37</td><td>Casters table</td><td>3.19.1.1.2</td></tr>
    143 <tr><td>38</td><td>Broadcaster source-table</td><td>3.19.1.1.4</td></tr>
    144 <tr><td>39</td><td>Stream distribution map derived from NTRIP Broadcaster source-table</td><td>3.19.1.1.6</td></tr>
    145 <tr><td>40</td><td>BNC setup for pulling a stream via serial port</td><td>3.19.1.4</td></tr>
     114<tr><td>9</td><td>Converting Broadcast Ephemeris stream to RINEX Version 3 Navigation file</td><td>3.5.5</td></tr>
     115<tr><td>10</td><td>Example for 'RINEX Editing Options' window</td><td>3.6.7</td></tr>
     116<tr><td>11</td><td>Example for RINEX file concatenation with BNC</td><td>3.6.7</td></tr>
     117<tr><td>12</td><td>Example for creating RINEX quality check analysis graphics output with BNC</td><td>3.6.7</td></tr>
     118<tr><td>13</td><td>Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC</td><td>3.6.7</td></tr>
     119<tr><td>14</td><td>Sky plot examples for multipath, part of RINEX quality check analysis with BNC</td><td>3.6.7</td></tr>
     120<tr><td>15</td><td>Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC</td><td>3.6.7</td></tr>
     121<tr><td>16</td><td>BNC configuration example for comparing two SP3 files with satellite orbit and clock data</td><td>3.7.3</td></tr>
     122<tr><td>17</td><td>BNC configuration example for pulling, saving and output of Broadcast Corrections</td><td>3.8.3</td></tr>
     123<tr><td>18</td><td>Synchronized BNC output via IP port to feed a GNSS real-time engine</td><td>3.9</td></tr>
     124<tr><td>19</td><td>Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams</td><td>3.10</td></tr>
     125<tr><td>20</td><td>BNC pulling a VRS stream to feed a serial connected RTK rover</td><td>3.10</td></tr>
     126<tr><td>21</td><td>RTCM message numbers, latencies and observation types</td><td>3.12</td></tr>
     127<tr><td>22</td><td>Real-time Precise Point Positioning with BNC, PPP Panel 1</td><td>3.13.1</td></tr>
     128<tr><td>23</td><td>Precise Point Positioning with BNC, PPP Panel 2</td><td>3.13.2</td></tr>
     129<tr><td>24</td><td>Precise Point Positioning with BNC, PPP Panel 3</td><td>3.13.3</td></tr>
     130<tr><td>25</td><td>BNC in 'Quick-Start' mode (PPP, Panel 2)</td><td>3.13.3.8</td></tr>
     131<tr><td>26</td><td>Track of positions from BNC with Google Maps in the background</td><td>3.13.4.3</td></tr>
     132<tr><td>27</td><td>Example for a background map from Google Maps and OpenStreetMap (OSM) resources</td><td>3.13.4.3.1</td></tr>
     133<tr><td>28</td><td>BNC combining Broadcast Correction streams</td><td>3.14.1.1</td></tr>
     134<tr><td>29</td><td>BNC uploading the combined Broadcast Corrections stream</td><td>3.14.1.1</td></tr>
     135<tr><td>30</td><td>'INTERNAL' PPP with BNC using combined Broadcast Corrections stream</td><td>3.14.1.1</td></tr>
     136<tr><td>31</td><td>Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'</td><td>3.15.3</td></tr>
     137<tr><td>32</td><td>Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster</td><td>3.15.9</td></tr>
     138<tr><td>33</td><td>Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an Ntrip Broadcaster</td><td>3.16.3</td></tr>
     139<tr><td>34</td><td>Bandwidth consumption of incoming streams</td><td>3.18.2</td></tr>
     140<tr><td>35</td><td>Latency of incoming streams</td><td>3.18.3</td></tr>
     141<tr><td>36</td><td>Time series plot of PPP session</td><td>3.18.4</td></tr>
     142<tr><td>37</td><td>Steam input communication links</td><td>3.19</td></tr>
     143<tr><td>38</td><td>Casters table</td><td>3.19.1.1.2</td></tr>
     144<tr><td>39</td><td>Broadcaster source-table</td><td>3.19.1.1.4</td></tr>
     145<tr><td>40</td><td>Stream distribution map derived from Ntrip Broadcaster source-table</td><td>3.19.1.1.6</td></tr>
     146<tr><td>41</td><td>BNC setup for pulling a stream via serial port</td><td>3.19.1.4</td></tr>
    146147</table>
    147148</p>
    … …  
    159160<p> The purpose of BNC is to
    160161<ul>
    161 <li>Retrieve real-time GNSS data streams available through NTRIP transport protocol;</li>
    162 <li>Retrieve real-time GNSS data streams via TCP directly from an IP address without using the NTRIP transport protocol;</li>
    163 <li>Retrieve real-time GNSS data streams from a local UDP or serial port without using the NTRIP transport protocol;</li>
    164 <li>Plot stream distribution map from NTRIP Broadcaster source-tables;</li>
     162<li>Retrieve real-time GNSS data streams available through Ntrip transport protocol;</li>
     163<li>Retrieve real-time GNSS data streams via TCP directly from an IP address without using the Ntrip transport protocol;</li>
     164<li>Retrieve real-time GNSS data streams from a local UDP or serial port without using the Ntrip transport protocol;</li>
     165<li>Plot stream distribution map from Ntrip Broadcaster source-tables;</li>
    165166<li>Generate RINEX Observation and Navigation files to support near real-time GNSS Post Processing applications;</li>
    166167<li>Edit or concatenate RINEX files or carry out RINEX Quality Checks (QC);</li>
    … …  
    183184<ul>
    184185<li>Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and cross-track components;</li>
    185 <li>Upload Broadcast Corrections as an RTCM Version 3 stream to an NTRIP Broadcaster;</li>
     186<li>Upload Broadcast Corrections as an RTCM Version 3 stream to an Ntrip Broadcaster;</li>
    186187<li>Refer the orbit and clock corrections to a specific reference system;</li>
    187188<li>Log the Broadcast Corrections as Clock RINEX files for further processing using other tools than BNC;</li>
    … …  
    309310</p>
    310311<p>
    311  The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an NTRIP Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to disseminate the combination product while saving results in SP3 and Clock RINEX files.
     312 The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an Ntrip Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to disseminate the combination product while saving results in SP3 and Clock RINEX files.
    312313</p>
    313314<p><img src="IMG/screenshot10.png"/></p>
    … …  
    344345<li>Requires access to the Internet with a minimum of about 2 to 6 kbits/sec per stream depending on the stream format and the number of visible satellites. You need to make sure that the connection can sustain the required bandwidth;</li>
    345346<li>Requires the clock of the host computer to be properly synchronized;</li>
    346 <li>Has the capacity to retrieve hundreds of GNSS data streams simultaneously. Please be aware that such usage may incur a heavy load on the NTRIP Broadcaster side depending on the number of streams requested. We recommend limiting the number of streams where possible to avoid unnecessary workload.</li>
     347<li>Has the capacity to retrieve hundreds of GNSS data streams simultaneously. Please be aware that such usage may incur a heavy load on the Ntrip Broadcaster side depending on the number of streams requested. We recommend limiting the number of streams where possible to avoid unnecessary workload.</li>
    347348</ul>
    348349</p>
    … …  
    571572&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.19.1.1.3 <a href=#streamuser>User and Password</a><br>
    572573&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.19.1.1.4 <a href=#gettable>Get Table</a><br>
    573 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.19.1.1.5 <a href=#ntripv>NTRIP Version</a><br>
     574&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.19.1.1.5 <a href=#ntripv>Ntrip Version</a><br>
    574575&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.19.1.1.6 <a href=#castermap>Map</a><br>
    575576&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.19.1.2 <a href=#streamip>Add Stream - Coming from TCP/IP Port</a><br>
    … …  
    633634<p><a name="network"><h4>3.2. Network</h4></p>
    634635<p>
    635 You may need to specify a proxy when running BNC in a protected network. You may also like to use the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure NTRIP communication over the Internet.
     636You may need to specify a proxy when running BNC in a protected network. You may also like to use the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure Ntrip communication over the Internet.
    636637</p>
    637638<p><a name="proxy"><h4>3.2.1 Proxy - Usage in a protected LAN</h4></p>
    … …  
    639640If you are running BNC within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.</p>
    640641<p>
    641 Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the NTRIP Broadcasters. If these are not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet.
     642Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the Ntrip Broadcasters. If these are not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet.
    642643</p>
    643644
    644645<p><a name="ssl"><h4>3.2.2 SSL - Transport Layer Security</h4></p>
    645 <p>Communication with an NTRIP Broadcaster over Secure Sockets Layer (SSL) as well as the download of RINEX skeleton files when available from HTTPS websites require the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known NTRIP Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved NTRIP Broadcaster. </p>
    646 <p>SSL communication may involve queries coming from the NTRIP Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab as follows:
     646<p>Communication with an Ntrip Broadcaster over Secure Sockets Layer (SSL) as well as the download of RINEX skeleton files when available from HTTPS websites require the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known Ntrip Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved Ntrip Broadcaster. </p>
     647<p>SSL communication may involve queries coming from the Ntrip Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab as follows:
    647648<pre>
    648649SSL Error
    … …  
    669670<p><a name="genlog"><h4>3.3.1 Logfile - optional</h4></p>
    670671<p>
    671 Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' carrying the current date. This leads to series of daily logfiles when running BNC continuously for extended. Message logs cover the communication status between BNC and the NTRIP Broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a file.
     672Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' carrying the current date. This leads to series of daily logfiles when running BNC continuously for extended. Message logs cover the communication status between BNC and the Ntrip Broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a file.
    672673</p>
    673674<p>
    … …  
    750751</p>
    751752<p>
    752 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. The 'SSL Error' recorded in the 'Log' tab is caused by the fact that observation stream downloads from IGS and MGEX Broadcasters initiate the download of RINEX skeleton files from a HTTPS (TLS/SSL) website and BNC has been configured in this example to ignore SSL errors as shown in the preceding 'Network' panel sreenshot.
     753The 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. The 'SSL Error' recorded in the 'Log' tab is caused by the fact that observation stream downloads from IGS and MGEX Broadcasters initiate the download of RINEX skeleton files from a HTTPS (TLS/SSL) website and BNC has been configured in this example to ignore SSL errors as shown in the preceding 'Network' panel sreenshot.
    753754</p>
    754755
    … …  
    19041905
    19051906<p>
    1906 The following figure shows the screenshot of a BNC configuration where a number of streams is pulled from different NTRIP Broadcasters to feed a GNSS engine via IP port output.
     1907The following figure shows the screenshot of a BNC configuration where a number of streams is pulled from different Ntrip Broadcasters to feed a GNSS engine via IP port output.
    19071908</p>
    19081909<p><img src="IMG/screenshot12.png"/></p>
    … …  
    19521953
    19531954<p>
    1954 The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an NTRIP Broadcaster to feed a serial connected RTK rover.
     1955The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an Ntrip Broadcaster to feed a serial connected RTK rover.
    19551956</p>
    19561957
    … …  
    20092010
    20102011<p><a name="serauto"><h4>3.10.8 NMEA - mandatory if 'Mountpoint' is set</h4></p>
    2011 <p>The 'NMEA' option supports the so-called 'Virtual Reference Station' (VRS) concept which requires the receiver to send approximate position information to the NTRIP Broadcaster. Select 'no' if you don't want BNC to forward or upload any NMEA message to the NTRIP broadcaster in support of VRS.
    2012 </p>
    2013 <p>Select 'Auto' to automatically forward NMEA messages of type GGA from your serial connected receiver to the NTRIP broadcaster and/or save them in a file.
    2014 </p>
    2015 <p>Select 'Manual GPGGA' or 'Manual GNGGA' if you want BNC to produce and upload GPGGA or GNGGA NMEA messages to the NTRIP broadcaster because your serial connected receiver doesn't generate these messages. A Talker ID 'GP' preceding the GGA string stands for GPS solutions while a Talker ID 'GN' stands for multi constellation solutions.
    2016 </p>
    2017 <p>Note that selecting 'Auto' or 'Manual' works only for VRS streams which show up under the 'Streams' canvas on BNC's main window with 'nmea' stream attribute set to 'yes'. This attribute is either extracted from the NTRIP broadcaster's source-table or introduced by the user through editing the BNC configuration file.
     2012<p>The 'NMEA' option supports the so-called 'Virtual Reference Station' (VRS) concept which requires the receiver to send approximate position information to the Ntrip Broadcaster. Select 'no' if you don't want BNC to forward or upload any NMEA message to the Ntrip broadcaster in support of VRS.
     2013</p>
     2014<p>Select 'Auto' to automatically forward NMEA messages of type GGA from your serial connected receiver to the Ntrip broadcaster and/or save them in a file.
     2015</p>
     2016<p>Select 'Manual GPGGA' or 'Manual GNGGA' if you want BNC to produce and upload GPGGA or GNGGA NMEA messages to the Ntrip broadcaster because your serial connected receiver doesn't generate these messages. A Talker ID 'GP' preceding the GGA string stands for GPS solutions while a Talker ID 'GN' stands for multi constellation solutions.
     2017</p>
     2018<p>Note that selecting 'Auto' or 'Manual' works only for VRS streams which show up under the 'Streams' canvas on BNC's main window with 'nmea' stream attribute set to 'yes'. This attribute is either extracted from the Ntrip broadcaster's source-table or introduced by the user through editing the BNC configuration file.
    20182019</p>
    20192020
    … …  
    20232024<p><a name="serheight"><h4>3.10.10 Height - mandatory if 'NMEA' is set to 'Manual'</h4></p>
    20242025<p>
    2025 Specify an approximate 'Height' above mean sea level in meters for the reference station introduced through 'Mountpoint'. Together with the latitude and longitude from the NTRIP broadcaster source-table the height information is used to build GGA messages to be sent to the NTRIP broadcaster.
     2026Specify an approximate 'Height' above mean sea level in meters for the reference station introduced through 'Mountpoint'. Together with the latitude and longitude from the Ntrip broadcaster source-table the height information is used to build GGA messages to be sent to the Ntrip broadcaster.
    20262027</p>
    20272028<p>For adjusting latitude and longitude values of a VRS stream given in the 'Streams' canvas you can double click the latitude/longitude data fields, specify appropriate values and then hit Enter.
    … …  
    21532154<p><a name="miscscan"><h4>3.12.3 Scan RTCM - optional</h4></p>
    21542155<p>
    2155 When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about RTCM message types and observation types. As reliable information concerning stream contents should be available i.e. for NTRIP Broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. Contained observation types are also printed because such information is required a priori for the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files. The idea for this option arose from 'inspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker.
     2156When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about RTCM message types and observation types. As reliable information concerning stream contents should be available i.e. for Ntrip Broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. Contained observation types are also printed because such information is required a priori for the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files. The idea for this option arose from 'inspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker.
    21562157</p>
    21572158<p>
    … …  
    22022203BNC can derive coordinates for rover positions following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data from one or more GNSS systems in ionosphere-free linear combinations P3 or L3. Besides pulling streams of observations from dual frequency GNSS receiver, this also
    22032204<ul>
    2204 <li>Requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of RTCM Version 3 'State Space Representation' (SSR) messages. Note that for BNC these Broadcast Corrections need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream 'CLK11' on NTRIP Broadcaster 'products.igs-ip.net:2101' is an example.</li>
     2205<li>Requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of RTCM Version 3 'State Space Representation' (SSR) messages. Note that for BNC these Broadcast Corrections need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream 'CLK11' on Ntrip Broadcaster 'products.igs-ip.net:2101' is an example.</li>
    22052206<li>May require pulling a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020, 1043, 1044, 1045, 1046 and 63 (tentative). This becomes a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at very low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream 'RTCM3EPH' on caster 'products.igs-ip.net:2101' is an example.</li>
    22062207</ul>
    … …  
    28712872<li>Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;</li>
    28722873<li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li>
    2873 <li>A Combination Center (CC) can operate BNC to globally disseminate a combination product via NTRIP broadcast;</li>
     2874<li>A Combination Center (CC) can operate BNC to globally disseminate a combination product via Ntrip broadcast;</li>
    28742875<li>An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;</li>
    28752876<li>It enables a BNC PPP user to follow his own preference in combining streams from individual ACs for Precise Point Positioning;</li>
    2876 <li>It allows an instantaneous quality control of the combination process not only in the time domain but also in the space domain; this can be done through direct application of the combined stream in a PPP solution even without prior upload to an NTRIP Broadcaster;</li>
     2877<li>It allows an instantaneous quality control of the combination process not only in the time domain but also in the space domain; this can be done through direct application of the combined stream in a PPP solution even without prior upload to an Ntrip Broadcaster;</li>
    28772878<li>It provides the means to output SP3 and Clock RINEX files containing precise orbit and clock information for further processing using other tools than BNC.</li>
    28782879</ul>
    … …  
    29332934
    29342935<p>
    2935 The following screenshots describe an example setup of BNC when combining Broadcast Correction streams and uploading them to an NTRIP Broadcaster. Note that this application requires specifying options under panels 'Combine Corrections' and 'Upload Corrections'. The example uses the combination product to simultaneously carry out an 'INTERNAL' PPP solution which allows monitoring the quality of the combination product in the space domain.
     2936The following screenshots describe an example setup of BNC when combining Broadcast Correction streams and uploading them to an Ntrip Broadcaster. Note that this application requires specifying options under panels 'Combine Corrections' and 'Upload Corrections'. The example uses the combination product to simultaneously carry out an 'INTERNAL' PPP solution which allows monitoring the quality of the combination product in the space domain.
    29362937</p>
    29372938
    … …  
    29732974or generated by BNC while the program receives an ASCII stream of precise satellite orbits and clocks via IP port from a connected real-time GNSS engine. Such a stream would be expected in a plain ASCII format and the associated 'decoder' string would have to be 'RTNET', see format description below. </li>
    29742975</ol>
    2975 The procedure taken by BNC to generate the orbit and clock corrections to Broadcast Ephemeris and upload them to an NTRIP Broadcaster is as follow:
     2976The procedure taken by BNC to generate the orbit and clock corrections to Broadcast Ephemeris and upload them to an Ntrip Broadcaster is as follow:
    29762977<ul>
    29772978<li>Continuously receive up-to-date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites. Read new Broadcast Ephemeris immediately whenever they become available. This information may come via a stream of RTCM messages generated from another BNC instance.</li>
    … …  
    29852986<li>Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris clocks and IGS08 clocks. </li>
    29862987<li>Encode Broadcast Ephemeris orbit and clock corrections in RTCM Version 3 format. </li>
    2987 <li>Upload Broadcast Corrections stream to NTRIP Broadcaster. </li>
     2988<li>Upload Broadcast Corrections stream to Ntrip Broadcaster. </li>
    29882989</ul>
    29892990<p>
    … …  
    29942995</p>
    29952996<p>
    2996 The usual handling of BNC when uploading a stream with Broadcast Corrections is that you first specify Broadcast Ephemeris and Broadcast Correction streams. You then specify an NTRIP Broadcaster for stream upload before you start the program.
     2997The usual handling of BNC when uploading a stream with Broadcast Corrections is that you first specify Broadcast Ephemeris and Broadcast Correction streams. You then specify an Ntrip Broadcaster for stream upload before you start the program.
    29972998</p>
    29982999<p>
    29993000<u>'RTNET' Stream Format</u><br>
    3000 When uploading an SSR stream generated according to b. then BNC requires precise GNSS orbits and clocks in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific ASCII format named 'RTNET' because the data may come from a real-time engine such as RTNET. The sampling interval for data transmission should not exceed 15 sec. Note that otherwise tools involved in IP streaming such as NTRIP Broadcasters or NTRIP Clients may respond with a timeout.
     3001When uploading an SSR stream generated according to b. then BNC requires precise GNSS orbits and clocks in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific ASCII format named 'RTNET' because the data may come from a real-time engine such as RTNET. The sampling interval for data transmission should not exceed 15 sec. Note that otherwise tools involved in IP streaming such as Ntrip Broadcasters or Ntrip Clients may respond with a timeout.
    30013002</p>
    30023003<p>
    … …  
    30773078</p>
    30783079<p>
    3079 Having an empty 'Upload Table' is default and means that you don't want BNC to upload orbit and clock correction streams to any NTRIP Broadcaster.
     3080Having an empty 'Upload Table' is default and means that you don't want BNC to upload orbit and clock correction streams to any Ntrip Broadcaster.
    30803081</p>
    30813082
    30823083<p><a name="uphost"><h4>3.15.2 Host, Port, Mountpoint, Password - optional</h4></p>
    30833084
    3084 <p>Specify the domain name or IP number of an NTRIP Broadcaster for uploading the stream. Furthermore, specify the caster's listening IP port, an upload mountpoint and an upload password. Note that NTRIP Broadcasters are often configured to provide access through more than one port, usually ports 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
    3085 </p>
    3086 <p>
    3087 BNC uploads a stream to the NNTRIP Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify here the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.</p>
    3088 <p>The stream upload may be protected through an upload 'Password'. Enter the password you received from the NTRIP Broadcaster operator along with the mountpoint(s).</p>
    3089 <p>
    3090 If 'Host', 'Port', 'Mountpoint' and 'Password' are set, the stream will be encoded in RTCM's 'State Space Representation' (SSR) messages and uploaded to the specified broadcaster following the NTRIP Version 1 transport protocol.
     3085<p>Specify the domain name or IP number of an Ntrip Broadcaster for uploading the stream. Furthermore, specify the caster's listening IP port, an upload mountpoint and an upload password. Note that Ntrip Broadcasters are often configured to provide access through more than one port, usually ports 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
     3086</p>
     3087<p>
     3088BNC uploads a stream to the Ntrip Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify here the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.</p>
     3089<p>The stream upload may be protected through an upload 'Password'. Enter the password you received from the Ntrip Broadcaster operator along with the mountpoint(s).</p>
     3090<p>
     3091If 'Host', 'Port', 'Mountpoint' and 'Password' are set, the stream will be encoded in RTCM's 'State Space Representation' (SSR) messages and uploaded to the specified broadcaster following the Ntrip Version 1 transport protocol.
    30913092</p>
    30923093
    30933094<p><a name="upsystem"><h4>3.15.3 System - mandatory if 'Host' is set</h4></p>
    30943095<p>
    3095 BNC allows configuring several Broadcast Correction streams for upload so that they refer to different reference systems and different NTRIP Broadcasters. You may use this functionality for parallel support of a backup NTRIP Broadcaster or for simultaneous support of various regional reference systems. Available options for transforming orbit and clock corrections to specific target reference systems are
     3096BNC allows configuring several Broadcast Correction streams for upload so that they refer to different reference systems and different Ntrip Broadcasters. You may use this functionality for parallel support of a backup Ntrip Broadcaster or for simultaneous support of various regional reference systems. Available options for transforming orbit and clock corrections to specific target reference systems are
    30963097<p>
    30973098<ul>
    … …  
    33533354
    33543355<p>
    3355 The following screenshot shows the encoding and uploading of a stream of precise orbits and clocks coming from a real-time engine in 'RTNET' ASCII format. The stream is uploaded to NTRIP Broadcaster 'products.igs-ip.net'. It is referred to APC and IGS08. Uploaded data are locally saved in SP3 and Clock RINEX format. The SSR Provider ID is set to 3. The SSR Solution ID is and the Issue of Data SSR are set to 1. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'.
     3356The following screenshot shows the encoding and uploading of a stream of precise orbits and clocks coming from a real-time engine in 'RTNET' ASCII format. The stream is uploaded to Ntrip Broadcaster 'products.igs-ip.net'. It is referred to APC and IGS08. Uploaded data are locally saved in SP3 and Clock RINEX format. The SSR Provider ID is set to 3. The SSR Solution ID is and the Issue of Data SSR are set to 1. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'.
    33563357</p>
    33573358<p><img src="IMG/screenshot26.png"/></p>
    3358 <p><u>Figure 32:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p>
     3359<p><u>Figure 32:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster.</p>
    33593360
    33603361<p><a name="upantex"><h4>3.15.10 ANTEX File - mantatory if 'SP3 File' is specified</h4></p>
    … …  
    33653366<p><a name="upeph"><h4>3.16. Upload Ephemeris</h4></p>
    33663367<p>
    3367 BNC can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an NTRIP Broadcaster.
     3368BNC can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an Ntrip Broadcaster.
    33683369</p>
    33693370
    33703371<p><a name="brdcserver"><h4>3.16.1 Host &amp; Port - optional</h4></p>
    33713372<p>
    3372 Specify the 'Host' IP number or URL of an NTRIP Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris.
    3373 </p>
    3374 <p>
    3375 Enter the NTRIP Broadcaster's IP 'Port' number for stream upload. Note that NTRIP Broadcasters are often configured to provide access through more than one port, usually ports 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
     3373Specify the 'Host' IP number or URL of an Ntrip Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris.
     3374</p>
     3375<p>
     3376Enter the Ntrip Broadcaster's IP 'Port' number for stream upload. Note that Ntrip Broadcasters are often configured to provide access through more than one port, usually ports 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
    33763377</p>
    33773378
    33783379<p><a name="brdcmount"><h4>3.16.2 Mountpoint &amp; Password - mandatory if 'Host' is set</h4></p>
    33793380<p>
    3380 BNC uploads a stream to the NTRIP Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.</p>
    3381 <p>The stream upload may be protected through an upload 'Password'. Enter the password you received from the NTRIP Broadcaster operator along with the mountpoint.</p>
     3381BNC uploads a stream to the Ntrip Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.</p>
     3382<p>The stream upload may be protected through an upload 'Password'. Enter the password you received from the Ntrip Broadcaster operator along with the mountpoint.</p>
    33823383</p>
    33833384
    … …  
    33873388
    33883389<p><img src="IMG/screenshot28.png"/></p>
    3389 <p><u>Figure 33:</u> Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster.</p>
     3390<p><u>Figure 33:</u> Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an Ntrip Broadcaster.</p>
    33903391
    33913392<p><a name="streams"><h4>3.17. Streams</h4></p>
    33923393<p>
    3393 Each stream on an NTRIP Broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An NTRIP Client like BNC accesses the desired stream by referring to its mountpoint. Information about streams and their mountpoints is available through the source-table maintained by the NTRIP Broadcaster.
    3394 </p>
    3395 
    3396 <p>
    3397 Streams selected for retrieval are listed under the 'Streams' canvas on BNC's main window. The list provides the following information either extracted from source-table(s) produced by the NTRIP Broadcasters or introduced by BNC's user:
     3394Each stream on an Ntrip Broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An Ntrip Client like BNC accesses the desired stream by referring to its mountpoint. Information about streams and their mountpoints is available through the source-table maintained by the Ntrip Broadcaster.
     3395</p>
     3396
     3397<p>
     3398Streams selected for retrieval are listed under the 'Streams' canvas on BNC's main window. The list provides the following information either extracted from source-table(s) produced by the Ntrip Broadcasters or introduced by BNC's user:
    33983399</p>
    33993400<p>
    34003401<table>
    3401 <tr><td>'resource loader'&nbsp; </td><td>NTRIP Broadcaster URL and port, or<br>TCP/IP host and port, or<br>UDP port, or<br>Serial input port specification.</td></tr>
    3402 <tr><td>'mountpoint' &nbsp;</td><td>Mountpoint introduced by NTRIP Broadcaster, or<br>Mountpoint introduced by BNC's user.</td></tr>
     3402<tr><td>'resource loader'&nbsp; </td><td>Ntrip Broadcaster URL and port, or<br>TCP/IP host and port, or<br>UDP port, or<br>Serial input port specification.</td></tr>
     3403<tr><td>'mountpoint' &nbsp;</td><td>Mountpoint introduced by Ntrip Broadcaster, or<br>Mountpoint introduced by BNC's user.</td></tr>
    34033404<tr><td>'decoder' &nbsp;</td><td>Name of decoder used to handle the incoming stream content according to its format; editable.</td></tr>
    34043405<tr><td>'lat' &nbsp;</td><td>Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.</td></tr>
    34053406<tr><td>'long' &nbsp;</td><td>Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.</td></tr>
    34063407<tr><td>'nmea' &nbsp;</td><td>Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'.</td></tr>
    3407 <tr><td>'ntrip' &nbsp;</td><td>Selected NTRIP transport protocol version (1, 2, 2s, R, or U), or<br>'N' for TCP/IP streams without NTRIP, or<br>'UN' for UDP streams without NTRIP, or<br>'S' for serial input streams without NTRIP.</td></tr>
     3408<tr><td>'ntrip' &nbsp;</td><td>Selected Ntrip transport protocol version (1, 2, 2s, R, or U), or<br>'N' for TCP/IP streams without Ntrip, or<br>'UN' for UDP streams without Ntrip, or<br>'S' for serial input streams without Ntrip.</td></tr>
    34083409<tr><td>'bytes' &nbsp;</td><td>Number of bytes received.
    34093410</table>
    … …  
    34193420</li>
    34203421<li>
    3421 BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the NTRIP Broadcaster. In return, a user-specific data stream is generated, typically by Network-RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the NTRIP Broadcaster via NMEA-GGA messages.
     3422BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the Ntrip Broadcaster. In return, a user-specific data stream is generated, typically by Network-RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the Ntrip Broadcaster via NMEA-GGA messages.
    34223423<br>If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used.
    3423 <br>Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner when not using the NTRIP Version 2 transport protocol.
     3424<br>Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner when not using the Ntrip Version 2 transport protocol.
    34243425</li>
    34253426</ul>
    … …  
    34823483<p><a name="streamadd"><h4>3.19.1 Add Stream</h4></p>
    34833484<p>
    3484 Button 'Add Stream' allows you to pull streams either from a NTRIP Broadcaster or from a TCP/IP port, UPD port, or serial port.
     3485Button 'Add Stream' allows you to pull streams either from a Ntrip Broadcaster or from a TCP/IP port, UPD port, or serial port.
    34853486</p>
    34863487
    … …  
    34883489
    34893490<p>
    3490 Button 'Add Stream' &gt; 'Coming from Caster' then opens a window that allows user to select data streams from an NTRIP Broadcaster according to their mountpoints and show a distribution map of offered streams.
     3491Button 'Add Stream' &gt; 'Coming from Caster' then opens a window that allows user to select data streams from an Ntrip Broadcaster according to their mountpoints and show a distribution map of offered streams.
    34913492</p>
    34923493
    34933494<p><a name="streamhost"><h4>3.19.1.1.1 Caster Host and Port - mandatory</h4></p>
    34943495<p>
    3495 Enter the NTRIP Broadcaster host IP and port number. Note that EUREF and IGS operate NTRIP Broadcasters at <u>http://www.euref-ip.net/home</u>, <u>http://www.igs-ip.net/home</u>, <u>http://www.products.igs-ip.net/home</u> and <u>http://mgex.igs-ip.net/home</u>.
     3496Enter the Ntrip Broadcaster host IP and port number. Note that EUREF and IGS operate Ntrip Broadcasters at <u>http://www.euref-ip.net/home</u>, <u>http://www.igs-ip.net/home</u>, <u>http://www.products.igs-ip.net/home</u> and <u>http://mgex.igs-ip.net/home</u>.
    34963497</p>
    34973498
    34983499<p><a name="streamtable"><h4>3.19.1.1.2 Casters Table - optional</h4></p>
    34993500<p>
    3500 It may be that you are not sure about your NTRIP Broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at <u>www.rtcm-ntrip.org/home</u>. A window opens which allows selecting a broadcaster for stream retrieval, see figure below.
     3501It may be that you are not sure about your Ntrip Broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at <u>www.rtcm-ntrip.org/home</u>. A window opens which allows selecting a broadcaster for stream retrieval, see figure below.
    35013502</p>
    35023503</p>
    … …  
    35073508<p><a name="streamuser"><h4>3.19.1.1.3 User and Password - mandatory for protected streams</h4></p>
    35083509<p>
    3509 Streams on NTRIP Broadcasters may be protected. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per NTRIP Broadcaster through a registration procedure. Register through <u>http://register.rtcm-ntrip.org</u> for access to protected streams from EUREF and IGS.
     3510Streams on Ntrip Broadcasters may be protected. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per Ntrip Broadcaster through a registration procedure. Register through <u>http://register.rtcm-ntrip.org</u> for access to protected streams from EUREF and IGS.
    35103511</p>
    35113512
    35123513<p><a name="gettable"><h4>3.19.1.1.4 Get Table</h4></p>
    35133514<p>
    3514 Use the 'Get Table' button to download the source-table from the NTRIP Broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2, RTCM Version 3, or RTNET format. For access to observations, Broadcast Ephemeris and Broadcast Corrections in RTCM format streams must contain a selection of appropriate message types as listed in the Annex, cf. data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3 streams containing message types 1019 (GPS) and 1020 (GLONASS) and 1043 (SBAS) and 1044 (QZSS) and 1045, 1046 (Galileo) and 63 (tentative, BDS/BeiDou) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table.
     3515Use the 'Get Table' button to download the source-table from the Ntrip Broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2, RTCM Version 3, or RTNET format. For access to observations, Broadcast Ephemeris and Broadcast Corrections in RTCM format streams must contain a selection of appropriate message types as listed in the Annex, cf. data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3 streams containing message types 1019 (GPS) and 1020 (GLONASS) and 1043 (SBAS) and 1044 (QZSS) and 1045, 1046 (Galileo) and 63 (tentative, BDS/BeiDou) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table.
    35153516</p>
    35163517<p>
    … …  
    35233524<p><u>Figure 39:</u> Broadcaster source-table.</p>
    35243525
    3525 <p><a name="ntripv"><h4>3.19.1.1.5 NTRIP Version - mandatory</h4></p>
    3526 <p>
    3527 Some limitations and deficiencies of the NTRIP Version 1 stream transport protocol are solved in NTRIP Version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are:
     3526<p><a name="ntripv"><h4>3.19.1.1.5 Ntrip Version - mandatory</h4></p>
     3527<p>
     3528Some limitations and deficiencies of the Ntrip Version 1 stream transport protocol are solved in Ntrip Version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are:
    35283529</p>
    35293530
    … …  
    35323533<tr></tr>
    35333534<tr><td><b>Option &nbsp;  &nbsp; </b></td><td><b>Meaning</b></td></tr>
    3534 <tr><td>&nbsp; &nbsp; 1</td><td>NTRIP Version 1, TCP/IP</td></tr>
    3535 <tr><td>&nbsp; &nbsp; 2</td><td>NTRIP Version 2 in TCP/IP mode</td></tr>
    3536 <tr><td>&nbsp; &nbsp; 2s</td><td>NTRIP Version 2 in TCP/IP mode via SSL</td></tr>
    3537 <tr><td>&nbsp; &nbsp; R</td><td>NTRIP Version 2 in RTSP/RTP mode</td></tr>
    3538 <tr><td>&nbsp; &nbsp; U</td><td>NTRIP Version 2 in UDP mode</td></tr>
     3535<tr><td>&nbsp; &nbsp; 1</td><td>Ntrip Version 1, TCP/IP</td></tr>
     3536<tr><td>&nbsp; &nbsp; 2</td><td>Ntrip Version 2 in TCP/IP mode</td></tr>
     3537<tr><td>&nbsp; &nbsp; 2s</td><td>Ntrip Version 2 in TCP/IP mode via SSL</td></tr>
     3538<tr><td>&nbsp; &nbsp; R</td><td>Ntrip Version 2 in RTSP/RTP mode</td></tr>
     3539<tr><td>&nbsp; &nbsp; U</td><td>Ntrip Version 2 in UDP mode</td></tr>
    35393540</table>
    35403541</p>
    35413542
    35423543<p>
    3543 If NTRIP Version 2 is supported by the broadcaster:
     3544If Ntrip Version 2 is supported by the broadcaster:
    35443545</p>
    35453546<ul>
    35463547<li>Try using option '2' if your streams are otherwise blocked by a proxy server operated in front of BNC.</li>
    3547 <li>When using NTRIP Version 2 via SSL (option '2s') you need to specify the appropriate 'Caster port' for that. It's usually port number 443. Clarify 'SSL' options offered in panel 'Network'.</li>
     3548<li>When using Ntrip Version 2 via SSL (option '2s') you need to specify the appropriate 'Caster port' for that. It's usually port number 443. Clarify 'SSL' options offered in panel 'Network'.</li>
    35483549<li>Option 'R' or 'U' may be selected if latency is more important than completeness for your application. Note that the latency reduction is likely to be in the order of 0.5 sec or less. Note further that options 'R' (RTSP/RTP mode) and 'U' (UDP mode) are not accepted by proxy servers and a mobile Internet Service Provider may not support it.</li>
    35493550</ul>
    35503551<p>
    3551 Select option '1' if you are not sure whether the broadcaster supports NTRIP Version 2.</li>
     3552Select option '1' if you are not sure whether the broadcaster supports Ntrip Version 2.</li>
    35523553</p>
    35533554
    … …  
    35583559
    35593560<p><img src="IMG/screenshot24.png"/></p>
    3560 <p><u>Figure 40:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p>
     3561<p><u>Figure 40:</u> Stream distribution map derived from Ntrip Broadcaster source-table.</p>
    35613562
    35623563<p><a name="streamip"><h4>3.19.1.2 Add Stream - Coming from TCP/IP Port</h4></p>
    35633564<p>
    3564 Button 'Add Stream' &gt; 'Coming from TCP/IP Port' allows to retrieve streams via TCP directly from an IP address without using the NTRIP transport protocol. For that you:
     3565Button 'Add Stream' &gt; 'Coming from TCP/IP Port' allows to retrieve streams via TCP directly from an IP address without using the Ntrip transport protocol. For that you:
    35653566<ul>
    35663567<li>Enter the IP address of the stream providing host.</li>
    … …  
    35733574</p>
    35743575<p>
    3575 Streams directly received from a TCP/IP port show up with an 'N' for 'No NTRIP' in the 'Streams' canvas on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
     3576Streams directly received from a TCP/IP port show up with an 'N' for 'No Ntrip' in the 'Streams' canvas on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
    35763577<p>
    35773578</p>
    … …  
    35813582<p><a name="streamudp"><h4>3.19.1.3 Add Stream - Coming from UDP Port</h4></p>
    35823583<p>
    3583 Button 'Add Stream' &gt; 'Coming from UDP Port' allows to pick up streams arriving directly at one of the local host's UDP ports without using the NTRIP transport protocol. For that you:
     3584Button 'Add Stream' &gt; 'Coming from UDP Port' allows to pick up streams arriving directly at one of the local host's UDP ports without using the Ntrip transport protocol. For that you:
    35843585<ul>
    35853586<li>Enter the local port number where the UDP stream arrives.</li>
    … …  
    35913592</p>
    35923593<p>
    3593 Streams directly received at a UDP port show up with a 'UN' for 'UDP, No NTRIP' in the 'Streams' canvas section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
     3594Streams directly received at a UDP port show up with a 'UN' for 'UDP, No Ntrip' in the 'Streams' canvas section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
    35943595<p>
    35953596
    35963597<p><a name="streamser"><h4>3.19.1.4 Add Stream - Coming from Serial Port</h4></p>
    35973598<p>
    3598 Button 'Add Stream' &gt; 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the NTRIP transport protocol. For that you:
     3599Button 'Add Stream' &gt; 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the Ntrip transport protocol. For that you:
    35993600<ul>
    36003601<li>Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ</li>
    … …  
    36253626
    36263627<p>
    3627 Streams received from a serial connected GNSS receiver show up with an 'S' (for <u>S</u>erial Port, no NTRIP) in the 'Streams' canvas section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
     3628Streams received from a serial connected GNSS receiver show up with an 'S' (for <u>S</u>erial Port, no Ntrip) in the 'Streams' canvas section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
    36283629<p>
    36293630
    … …  
    37543755</li>
    37553756<li>
    3756 BNC's 'Get Table' function only shows the STR records of a source-table. You can use an Internet browser to download the full source-table contents of any NTRIP Broadcaster by simply entering its URL in the form of <u>http://host:port</u>. Data field number 8 in the NET records may provide information about where to register for an NTRIP Broadcaster account.
     3757BNC's 'Get Table' function only shows the STR records of a source-table. You can use an Internet browser to download the full source-table contents of any Ntrip Broadcaster by simply entering its URL in the form of <u>http://host:port</u>. Data field number 8 in the NET records may provide information about where to register for an Ntrip Broadcaster account.
    37573758</li>
    37583759<li>
    3759 EUREF as well as IGS adhere to an open data policy. Streams are made available through NTRIP Broadcasters at <u>www.euref-ip.net</u>, <u>www.igs-ip.net</u>, <u>products.igs-ip.net</u>, and <u>mgex.igs-ip.net</u> free of charge to anyone for any purpose. There is no indication up until now how many users will need to be supported simultaneously. The given situation may develop in such a way that it might become difficult to serve all registered users at the same times. In cases where limited resources on the NTRIP Broadcaster side (software restrictions, bandwidth limitation etc.) dictates, first priority in stream provision will be given to stream providers followed by re-broadcasting activities and real-time analysis centers while access to others might be temporarily denied.
     3760EUREF as well as IGS adhere to an open data policy. Streams are made available through Ntrip Broadcasters at <u>www.euref-ip.net</u>, <u>www.igs-ip.net</u>, <u>products.igs-ip.net</u>, and <u>mgex.igs-ip.net</u> free of charge to anyone for any purpose. There is no indication up until now how many users will need to be supported simultaneously. The given situation may develop in such a way that it might become difficult to serve all registered users at the same times. In cases where limited resources on the Ntrip Broadcaster side (software restrictions, bandwidth limitation etc.) dictates, first priority in stream provision will be given to stream providers followed by re-broadcasting activities and real-time analysis centers while access to others might be temporarily denied.
    37603761</li>
    37613762<li>
    … …  
    377237735.1. <a href=#history>Revision History</a><br>
    377337745.2. <a href=#rtcm>RTCM</a><br>
    3774 &nbsp; &nbsp; &nbsp; 5.2.1 NTRIP <a href=#ntrip1>Version 1</a><br>
    3775 &nbsp; &nbsp; &nbsp; 5.2.2 NTRIP <a href=#ntrip2>Version 2</a><br>
     3775&nbsp; &nbsp; &nbsp; 5.2.1 Ntrip <a href=#ntrip1>Version 1</a><br>
     3776&nbsp; &nbsp; &nbsp; 5.2.2 Ntrip <a href=#ntrip2>Version 2</a><br>
    37763777&nbsp; &nbsp; &nbsp; 5.2.3 RTCM <a href=#rtcm2>Version 2</a><br>
    37773778&nbsp; &nbsp; &nbsp; 5.2.4 RTCM <a href=#rtcm3>Version 3</a><br>
    … …  
    38263827<tr>
    38273828<td>Nov 2009 &nbsp;</td><td>Version 1.7 &nbsp;</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 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<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>
    38293830</tr>
    38303831
    … …  
    38663867<tr>
    38673868<td>Apr 2011 &nbsp;</td><td>Version 2.6 &nbsp;</td>
    3868 <td>[Add] Complete integration of BNS in BNC<br> [Add] SP3 and Clock RINEX output<br> [Add] PPP in Post Processing Mode<br> [Add] Some RINEX editing & QC functionality<br> [Add] Threshold for orbit outliers in combination solution<br> [Add] Real-time engine becomes orbit/clock server instead of client<br> [Mod] 'EOE' added to orbit/clock stream from engine<br> [Add] Correction for antenna eccentricities<br> [Add] Quick start mode for PPP<br> [Mod] Design of format for feeding engine changed to follow RINEX v3<br> [Mod] Implementation of SSR message encoding modified according to standard<br> [Add] SSL/TLS Support of NTRIP Version 2<br> [Mod] Switch to Qt version 4.7.3<br> [Add] RINEX editing, concatenation and quality check<br> [Add] Reading all configuration options from command line<br> [Mod] RTCM v3 Galileo Broadcast Ephemeris message 1045<br> [Mod] Change default configuration file suffix from 'ini' to 'bnc'<br> [Add] Specific rates for orbits and clocks in streams and SP3/RNX files</td>
     3869<td>[Add] Complete integration of BNS in BNC<br> [Add] SP3 and Clock RINEX output<br> [Add] PPP in Post Processing Mode<br> [Add] Some RINEX editing & QC functionality<br> [Add] Threshold for orbit outliers in combination solution<br> [Add] Real-time engine becomes orbit/clock server instead of client<br> [Mod] 'EOE' added to orbit/clock stream from engine<br> [Add] Correction for antenna eccentricities<br> [Add] Quick start mode for PPP<br> [Mod] Design of format for feeding engine changed to follow RINEX v3<br> [Mod] Implementation of SSR message encoding modified according to standard<br> [Add] SSL/TLS Support of Ntrip Version 2<br> [Mod] Switch to Qt version 4.7.3<br> [Add] RINEX editing, concatenation and quality check<br> [Add] Reading all configuration options from command line<br> [Mod] RTCM v3 Galileo Broadcast Ephemeris message 1045<br> [Mod] Change default configuration file suffix from 'ini' to 'bnc'<br> [Add] Specific rates for orbits and clocks in streams and SP3/RNX files</td>
    38693870</tr>
    38703871
    … …  
    38763877<tr>
    38773878<td>Sep 2012 &nbsp;</td><td>Version 2.7 &nbsp;</td>
    3878 <td>[Bug] Bug in L5 decoding fixed<br> [Bug] Bug in on-the-fly configuration fixed<br> [Add] Clock RINEX file header extended<br> [Add] Decoding/converting BeiDou and QZSS added<br> [Add] Work on RINEX v2 and v3 quality check started<br> [Mod] Source code completely re-arranged<br> [Add] QWT and QWTPOLAR graphics libraries added<br> [Add] RINEX QC through multipath analysis sky plot<br> [Add] RINEX QC through signal-to-noise ratio sky plot<br> [Add] RINEX QC through satellite availability plot<br> [Add] RINEX QC through satellite elevation plot<br> [Add RINEX QC through PDOP plot<br> [Bug] Short periodic outages in PPP time series when 'Sync Corr' set to zero<br> |Add] Log observation types contained in RTCM Version 3 MSM streams<br> [Add] Reading RINEX v3 observation type header records from RINEX skeleton files<br> [Add] Logfile for RINEX file editing and concatenation<br>[Add] Save PNG plot files on disk<br> [Mod] Plot stream distribution map from NTRIP Broadcaster source-table<br> [Add] Plot stream distribution map from selected sources<br> [Add] Version 2.7 published</td>
     3879<td>[Bug] Bug in L5 decoding fixed<br> [Bug] Bug in on-the-fly configuration fixed<br> [Add] Clock RINEX file header extended<br> [Add] Decoding/converting BeiDou and QZSS added<br> [Add] Work on RINEX v2 and v3 quality check started<br> [Mod] Source code completely re-arranged<br> [Add] QWT and QWTPOLAR graphics libraries added<br> [Add] RINEX QC through multipath analysis sky plot<br> [Add] RINEX QC through signal-to-noise ratio sky plot<br> [Add] RINEX QC through satellite availability plot<br> [Add] RINEX QC through satellite elevation plot<br> [Add RINEX QC through PDOP plot<br> [Bug] Short periodic outages in PPP time series when 'Sync Corr' set to zero<br> |Add] Log observation types contained in RTCM Version 3 MSM streams<br> [Add] Reading RINEX v3 observation type header records from RINEX skeleton files<br> [Add] Logfile for RINEX file editing and concatenation<br>[Add] Save PNG plot files on disk<br> [Mod] Plot stream distribution map from Ntrip Broadcaster source-table<br> [Add] Plot stream distribution map from selected sources<br> [Add] Version 2.7 published</td>
    38793880</tr>
    38803881
    … …  
    39173918[Add] RTCM v3 SBAS Broadcast Ephemeris message 1043<br>
    39183919[Add] RTCM v3 BDS Broadcast Ephemeris message 63 (tentative)<br>
    3919 [Bug] VRS support in sending NMEA in Auto/Manual mode to NTRIP Broadcaster<br>
    3920 [Add] Forwarding NMEA GNGGA to NTRIP Broadcaster<br>
     3920[Bug] VRS support in sending NMEA in Auto/Manual mode to Ntrip Broadcaster<br>
     3921[Add] Forwarding NMEA GNGGA to Ntrip Broadcaster<br>
    39213922[Bug] Stream failure/recovery reports<br>
    39223923[Add] Compute IODs from CRC over broadcast ephemeris and clock parameters<br>
    … …  
    39493950[Add] SINEX Troposphere file output<br>
    39503951[Add] String for Operating System in logfile output<br>
     3952[Add] Full integration of 'rtcm3torinex'<br>
    39513953</td>
    39523954</tr>
    … …  
    39633965</p>
    39643966
    3965 <p><a name="ntrip1"><h4>5.2.1 NTRIP Version 1</h4></p>
    3966 
    3967 <p>
    3968 'Networked Transport of RTCM via Internet Protocol' Version 1.0 (NTRIP) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. NTRIP is a generic, stateless protocol based on the Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.
    3969 </p>
    3970 
    3971 <p>
    3972 NTRIP Version 1 is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA, or receiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.
    3973 </p>
    3974 
    3975 <p>
    3976 NTRIP is implemented in three system software components: NTRIP Clients, NTRIP Servers and NTRIP Broadcasters. The NTRIP Broadcaster is the actual HTTP server program whereas NTRIP Client and NTRIP Server are acting as HTTP clients.
    3977 </p>
    3978 
    3979 <p>
    3980 NTRIP is an open none-proprietary protocol. Major characteristics of NTRIP's dissemination technique are:
     3967<p><a name="ntrip1"><h4>5.2.1 Ntrip Version 1</h4></p>
     3968
     3969<p>
     3970'Networked Transport of RTCM via Internet Protocol' Version 1.0 (Ntrip) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. Ntrip is a generic, stateless protocol based on the Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.
     3971</p>
     3972
     3973<p>
     3974Ntrip Version 1 is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA, or receiver connections to a broadcasting host. Ntrip supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.
     3975</p>
     3976
     3977<p>
     3978Ntrip is implemented in three system software components: Ntrip Clients, Ntrip Servers and Ntrip Broadcasters. The Ntrip Broadcaster is the actual HTTP server program whereas Ntrip Client and Ntrip Server are acting as HTTP clients.
     3979</p>
     3980
     3981<p>
     3982Ntrip is an open none-proprietary protocol. Major characteristics of Ntrip's dissemination technique are:
    39813983<ul>
    39823984<li>Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and server platform resources available;</li>
    … …  
    39893991
    39903992<p>
    3991 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).
     3993The 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).
    39923994</p>
    39933995
    … …  
    40024004</p>
    40034005
    4004 <p><a name="ntrip2"><h4>5.2.2 NTRIP Version 2</h4></p>
    4005 
    4006 <p>
    4007 The major changes of NTRIP Version 2 compared to Version 1.0 are:
     4006<p><a name="ntrip2"><h4>5.2.2 Ntrip Version 2</h4></p>
     4007
     4008<p>
     4009The major changes of Ntrip Version 2 compared to Version 1.0 are:
    40084010</p>
    40094011
    … …  
    40174019</ul>
    40184020
    4019 <p>NTRIP Version 2 allows to either communicating in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas Version 1 is limited to TCP/IP only. It furthermore allows using the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure NTRIP communication over the Internet.
     4021<p>Ntrip Version 2 allows to either communicating in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas Version 1 is limited to TCP/IP only. It furthermore allows using the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure Ntrip communication over the Internet.
    40204022</p>
    40214023
    … …  
    43074309The purpose of this configuration is to feed a real-time GNSS engine with
    43084310observations from a remote reference stations. The configuration pulls a single
    4309 stream from an NTRIP Broadcasters. It would of course be possible to pull
     4311stream from an Ntrip Broadcasters. It would of course be possible to pull
    43104312several streams from different casters. Incoming observations are decoded,
    43114313synchronized and output through a local IP port and saved into a file. Failure
    … …  
    43864388<li>File 'Upload.bnc'<br>
    43874389The purpose of this configuration is to upload orbits and clocks from a
    4388 real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads
     4390real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads
    43894391precise orbits and clocks in RTNET format. It also reads a stream carrying
    43904392Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast
    43914393Corrections and encodes them in RTCM Version 3 SSR messages to upload them to
    4392 an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite
     4394an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satellite
    43934395Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format
    43944396and clocks in Clock RINEX format.
    … …  
    44054407<li>File 'Combi.bnc'<br>
    44064408The purpose of this configuration is to pull several streams carrying Broadcast
    4407 Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to
     4409Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to
    44084410produce a combined Broadcast Corrections stream. BNC encodes the combination
    44094411product in RTCM Version 3 SSR messages and uploads that to an Ntrip
    … …  
    46444646<tr><td><br><b>Add Stream</b></td><td><br><b>Meaning</b></td></tr>
    46454647<tr><td>mountPoints</td><td>Add stream coming from ...</td></tr>
    4646 <tr><td>ntripVersion</td><td>NTRIP Version</td></tr>
     4648<tr><td>ntripVersion</td><td>Ntrip Version</td></tr>
    46474649</table>
    46484650</p>
    … …  
    46674669<tr></tr>
    46684670<tr><td><b>Links</b></td></tr>
    4669 <tr><td>NTRIP &nbsp;</td><td><u>http://igs.bkg.bund.de/ntrip/index</u></td></tr>
    4670 <tr><td>EUREF-IP NTRIP Broadcaster &nbsp;</td><td><u>http://www.euref-ip.net/home</u></td></tr>
    4671 <tr><td>IGS-IP NTRIP Broadcaster &nbsp;</td><td><u>http://www.igs-ip.net/home</u></td></tr>
    4672 <tr><td>IGS products NTRIP Broadcaster &nbsp;</td><td><u>http://products.igs-ip.net/home</u></td></tr>
    4673 <tr><td>IGS M-GEX NTRIP Broadcaster &nbsp;</td><td><u>http://mgex.igs-ip.net/home</u></td></tr>
    4674 <tr><td>IGS Central Bureau NTRIP Broadcaster &nbsp;</td><td><u>http://rt.igs.org</u></td></tr>
     4671<tr><td>Ntrip &nbsp;</td><td><u>http://igs.bkg.bund.de/ntrip/index</u></td></tr>
     4672<tr><td>EUREF-IP Ntrip Broadcaster &nbsp;</td><td><u>http://www.euref-ip.net/home</u></td></tr>
     4673<tr><td>IGS-IP Ntrip Broadcaster &nbsp;</td><td><u>http://www.igs-ip.net/home</u></td></tr>
     4674<tr><td>IGS products Ntrip Broadcaster &nbsp;</td><td><u>http://products.igs-ip.net/home</u></td></tr>
     4675<tr><td>IGS M-GEX Ntrip Broadcaster &nbsp;</td><td><u>http://mgex.igs-ip.net/home</u></td></tr>
     4676<tr><td>IGS Central Bureau Ntrip Broadcaster &nbsp;</td><td><u>http://rt.igs.org</u></td></tr>
    46754677<tr><td>IGS Real-time Service &nbsp;</td><td><u>http://rts.igs.org</u></td></tr>
    46764678<tr><td>Distribution of IGS-IP streams &nbsp;</td><td><u>http://www.igs.oma.be/real_time/</u></td></tr>
    46774679<tr><td>Completeness and latency of IGS-IP data &nbsp;</td><td><u>http://www.igs.oma.be/highrate/</u></td></tr>
    4678 <tr><td>NTRIP Broadcaster overview &nbsp;</td><td><u>http://www.rtcm-ntrip.org/home</u></td></tr>
    4679 <tr><td>NTRIP Open Source software code &nbsp;</td><td><u>http://software.rtcm-ntrip.org</u></td></tr>
     4680<tr><td>Ntrip Broadcaster overview &nbsp;</td><td><u>http://www.rtcm-ntrip.org/home</u></td></tr>
     4681<tr><td>Ntrip Open Source software code &nbsp;</td><td><u>http://software.rtcm-ntrip.org</u></td></tr>
    46804682<tr><td>EUREF-IP Project &nbsp;</td><td><u>http://www.epncb.oma.be/euref_IP</u></td></tr>
    46814683<tr><td>Real-time IGS Pilot Project &nbsp;</td><td><u>http://www.rtigs.net/pilot</u></td></tr>
    … …  
    46914693<tr><td>Weber, G., D. Dettmering, H. Gebhard and R. Kalafus </td><td>Networked Transport of RTCM via Internet Protocol (Ntrip), IP-Streaming for Real-Time GNSS Applications, ION GNSS 2005.</td></tr>
    46924694
    4693 <tr><td>Weber, G, L. Mervart, Z. Lukes, C. Rocken and J. Dousa </td><td>Real-time Clock and Orbit Corrections for Improved Point Positioning via NTRIP, ION GNSS 2007.</td></tr>
     4695<tr><td>Weber, G, L. Mervart, Z. Lukes, C. Rocken and J. Dousa </td><td>Real-time Clock and Orbit Corrections for Improved Point Positioning via Ntrip, ION GNSS 2007.</td></tr>
    46944696
    46954697<tr><td>Mervart, L., Z. Lukes, C. Rocken and T. Iwabuchi </td><td>Precise Point Positioning With Ambiguity Resolution in Real-Time, ION GNSS 2008.</td></tr>
Note: See TracChangeset for help on using the changeset viewer.