- Timestamp:
- Aug 18, 2015, 10:37:01 AM (9 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (55 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7216 r7226 4 4 5 5 <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 N TRIPBroadcasters like6 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 7 7 <ul> 8 8 <li><u>http://www.euref-ip.net/home</u>,</li> … … 44 44 45 45 <p> 46 Prof. Mervart started working on BNC in June2005. 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ürze [andrea.stuerze@bkg.bund.de].46 Prof. 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ürze [andrea.stuerze@bkg.bund.de]. 47 47 </p> 48 48 … … 112 112 <tr><td>7</td><td>BNC's 'Network' panel configured to ignore eventually occurring SSL error messages</td><td>3.2.2</td></tr> 113 113 <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> 146 147 </table> 147 148 </p> … … 159 160 <p> The purpose of BNC is to 160 161 <ul> 161 <li>Retrieve real-time GNSS data streams available through N TRIPtransport protocol;</li>162 <li>Retrieve real-time GNSS data streams via TCP directly from an IP address without using the N TRIPtransport protocol;</li>163 <li>Retrieve real-time GNSS data streams from a local UDP or serial port without using the N TRIPtransport protocol;</li>164 <li>Plot stream distribution map from N TRIPBroadcaster 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> 165 166 <li>Generate RINEX Observation and Navigation files to support near real-time GNSS Post Processing applications;</li> 166 167 <li>Edit or concatenate RINEX files or carry out RINEX Quality Checks (QC);</li> … … 183 184 <ul> 184 185 <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 N TRIPBroadcaster;</li>186 <li>Upload Broadcast Corrections as an RTCM Version 3 stream to an Ntrip Broadcaster;</li> 186 187 <li>Refer the orbit and clock corrections to a specific reference system;</li> 187 188 <li>Log the Broadcast Corrections as Clock RINEX files for further processing using other tools than BNC;</li> … … 309 310 </p> 310 311 <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 N TRIPBroadcaster. 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. 312 313 </p> 313 314 <p><img src="IMG/screenshot10.png"/></p> … … 344 345 <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> 345 346 <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 N TRIPBroadcaster 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> 347 348 </ul> 348 349 </p> … … 571 572 3.19.1.1.3 <a href=#streamuser>User and Password</a><br> 572 573 3.19.1.1.4 <a href=#gettable>Get Table</a><br> 573 3.19.1.1.5 <a href=#ntripv>N TRIPVersion</a><br>574 3.19.1.1.5 <a href=#ntripv>Ntrip Version</a><br> 574 575 3.19.1.1.6 <a href=#castermap>Map</a><br> 575 576 3.19.1.2 <a href=#streamip>Add Stream - Coming from TCP/IP Port</a><br> … … 633 634 <p><a name="network"><h4>3.2. Network</h4></p> 634 635 <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 N TRIPcommunication over the Internet.636 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. 636 637 </p> 637 638 <p><a name="proxy"><h4>3.2.1 Proxy - Usage in a protected LAN</h4></p> … … 639 640 If 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> 640 641 <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 N TRIPBroadcasters. If these are not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet.642 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. 642 643 </p> 643 644 644 645 <p><a name="ssl"><h4>3.2.2 SSL - Transport Layer Security</h4></p> 645 <p>Communication with an N TRIP 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 NTRIPBroadcaster. </p>646 <p>SSL communication may involve queries coming from the N TRIPBroadcaster 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: 647 648 <pre> 648 649 SSL Error … … 669 670 <p><a name="genlog"><h4>3.3.1 Logfile - optional</h4></p> 670 671 <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 N TRIPBroadcaster 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.672 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. 672 673 </p> 673 674 <p> … … 750 751 </p> 751 752 <p> 752 The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various N TRIPBroadcasters 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.753 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. 753 754 </p> 754 755 … … 1904 1905 1905 1906 <p> 1906 The following figure shows the screenshot of a BNC configuration where a number of streams is pulled from different N TRIPBroadcasters to feed a GNSS engine via IP port output.1907 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. 1907 1908 </p> 1908 1909 <p><img src="IMG/screenshot12.png"/></p> … … 1952 1953 1953 1954 <p> 1954 The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an N TRIPBroadcaster to feed a serial connected RTK rover.1955 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. 1955 1956 </p> 1956 1957 … … 2009 2010 2010 2011 <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 N TRIP Broadcaster. Select 'no' if you don't want BNC to forward or upload any NMEA message to the NTRIPbroadcaster 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 N TRIPbroadcaster 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 N TRIPbroadcaster 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 N TRIPbroadcaster'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. 2018 2019 </p> 2019 2020 … … 2023 2024 <p><a name="serheight"><h4>3.10.10 Height - mandatory if 'NMEA' is set to 'Manual'</h4></p> 2024 2025 <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 N TRIP broadcaster source-table the height information is used to build GGA messages to be sent to the NTRIPbroadcaster.2026 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. 2026 2027 </p> 2027 2028 <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. … … 2153 2154 <p><a name="miscscan"><h4>3.12.3 Scan RTCM - optional</h4></p> 2154 2155 <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 N TRIPBroadcaster 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.2156 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. 2156 2157 </p> 2157 2158 <p> … … 2202 2203 BNC 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 2203 2204 <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 N TRIPBroadcaster '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> 2205 2206 <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> 2206 2207 </ul> … … 2871 2872 <li>Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;</li> 2872 2873 <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 N TRIPbroadcast;</li>2874 <li>A Combination Center (CC) can operate BNC to globally disseminate a combination product via Ntrip broadcast;</li> 2874 2875 <li>An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;</li> 2875 2876 <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 N TRIPBroadcaster;</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> 2877 2878 <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> 2878 2879 </ul> … … 2933 2934 2934 2935 <p> 2935 The following screenshots describe an example setup of BNC when combining Broadcast Correction streams and uploading them to an N TRIPBroadcaster. 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.2936 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. 2936 2937 </p> 2937 2938 … … 2973 2974 or 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> 2974 2975 </ol> 2975 The procedure taken by BNC to generate the orbit and clock corrections to Broadcast Ephemeris and upload them to an N TRIPBroadcaster is as follow:2976 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: 2976 2977 <ul> 2977 2978 <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> … … 2985 2986 <li>Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris clocks and IGS08 clocks. </li> 2986 2987 <li>Encode Broadcast Ephemeris orbit and clock corrections in RTCM Version 3 format. </li> 2987 <li>Upload Broadcast Corrections stream to N TRIPBroadcaster. </li>2988 <li>Upload Broadcast Corrections stream to Ntrip Broadcaster. </li> 2988 2989 </ul> 2989 2990 <p> … … 2994 2995 </p> 2995 2996 <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 N TRIPBroadcaster for stream upload before you start the program.2997 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. 2997 2998 </p> 2998 2999 <p> 2999 3000 <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 N TRIP Broadcasters or NTRIPClients may respond with a timeout.3001 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. 3001 3002 </p> 3002 3003 <p> … … 3077 3078 </p> 3078 3079 <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 N TRIPBroadcaster.3080 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. 3080 3081 </p> 3081 3082 3082 3083 <p><a name="uphost"><h4>3.15.2 Host, Port, Mountpoint, Password - optional</h4></p> 3083 3084 3084 <p>Specify the domain name or IP number of an N TRIP Broadcaster for uploading the stream. Furthermore, specify the caster's listening IP port, an upload mountpoint and an upload password. Note that NTRIPBroadcasters 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 N NTRIPBroadcaster 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 N TRIPBroadcaster 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 N TRIPVersion 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> 3088 BNC 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> 3091 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. 3091 3092 </p> 3092 3093 3093 3094 <p><a name="upsystem"><h4>3.15.3 System - mandatory if 'Host' is set</h4></p> 3094 3095 <p> 3095 BNC allows configuring several Broadcast Correction streams for upload so that they refer to different reference systems and different N TRIP Broadcasters. You may use this functionality for parallel support of a backup NTRIPBroadcaster or for simultaneous support of various regional reference systems. Available options for transforming orbit and clock corrections to specific target reference systems are3096 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 3096 3097 <p> 3097 3098 <ul> … … 3353 3354 3354 3355 <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 N TRIPBroadcaster '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'.3356 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'. 3356 3357 </p> 3357 3358 <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 N TRIPBroadcaster.</p>3359 <p><u>Figure 32:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster.</p> 3359 3360 3360 3361 <p><a name="upantex"><h4>3.15.10 ANTEX File - mantatory if 'SP3 File' is specified</h4></p> … … 3365 3366 <p><a name="upeph"><h4>3.16. Upload Ephemeris</h4></p> 3366 3367 <p> 3367 BNC can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an N TRIPBroadcaster.3368 BNC can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an Ntrip Broadcaster. 3368 3369 </p> 3369 3370 3370 3371 <p><a name="brdcserver"><h4>3.16.1 Host & Port - optional</h4></p> 3371 3372 <p> 3372 Specify the 'Host' IP number or URL of an N TRIPBroadcaster 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 N TRIP Broadcaster's IP 'Port' number for stream upload. Note that NTRIPBroadcasters 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).3373 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. 3374 </p> 3375 <p> 3376 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). 3376 3377 </p> 3377 3378 3378 3379 <p><a name="brdcmount"><h4>3.16.2 Mountpoint & Password - mandatory if 'Host' is set</h4></p> 3379 3380 <p> 3380 BNC uploads a stream to the N TRIPBroadcaster 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 N TRIPBroadcaster operator along with the mountpoint.</p>3381 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> 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> 3382 3383 </p> 3383 3384 … … 3387 3388 3388 3389 <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 N TRIPBroadcaster.</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> 3390 3391 3391 3392 <p><a name="streams"><h4>3.17. Streams</h4></p> 3392 3393 <p> 3393 Each stream on an N TRIP 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 NTRIPBroadcaster.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 N TRIPBroadcasters or introduced by BNC's user:3394 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. 3395 </p> 3396 3397 <p> 3398 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: 3398 3399 </p> 3399 3400 <p> 3400 3401 <table> 3401 <tr><td>'resource loader' </td><td>N TRIPBroadcaster 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' </td><td>Mountpoint introduced by N TRIPBroadcaster, or<br>Mountpoint introduced by BNC's user.</td></tr>3402 <tr><td>'resource loader' </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' </td><td>Mountpoint introduced by Ntrip Broadcaster, or<br>Mountpoint introduced by BNC's user.</td></tr> 3403 3404 <tr><td>'decoder' </td><td>Name of decoder used to handle the incoming stream content according to its format; editable.</td></tr> 3404 3405 <tr><td>'lat' </td><td>Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.</td></tr> 3405 3406 <tr><td>'long' </td><td>Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.</td></tr> 3406 3407 <tr><td>'nmea' </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' </td><td>Selected N TRIP 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' </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 3409 <tr><td>'bytes' </td><td>Number of bytes received. 3409 3410 </table> … … 3419 3420 </li> 3420 3421 <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 N TRIP 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 NTRIPBroadcaster via NMEA-GGA messages.3422 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. 3422 3423 <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 N TRIPVersion 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. 3424 3425 </li> 3425 3426 </ul> … … 3482 3483 <p><a name="streamadd"><h4>3.19.1 Add Stream</h4></p> 3483 3484 <p> 3484 Button 'Add Stream' allows you to pull streams either from a N TRIPBroadcaster or from a TCP/IP port, UPD port, or serial port.3485 Button 'Add Stream' allows you to pull streams either from a Ntrip Broadcaster or from a TCP/IP port, UPD port, or serial port. 3485 3486 </p> 3486 3487 … … 3488 3489 3489 3490 <p> 3490 Button 'Add Stream' > 'Coming from Caster' then opens a window that allows user to select data streams from an N TRIPBroadcaster according to their mountpoints and show a distribution map of offered streams.3491 Button 'Add Stream' > '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. 3491 3492 </p> 3492 3493 3493 3494 <p><a name="streamhost"><h4>3.19.1.1.1 Caster Host and Port - mandatory</h4></p> 3494 3495 <p> 3495 Enter the N TRIP Broadcaster host IP and port number. Note that EUREF and IGS operate NTRIPBroadcasters 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>.3496 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>. 3496 3497 </p> 3497 3498 3498 3499 <p><a name="streamtable"><h4>3.19.1.1.2 Casters Table - optional</h4></p> 3499 3500 <p> 3500 It may be that you are not sure about your N TRIPBroadcasters 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.3501 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. 3501 3502 </p> 3502 3503 </p> … … 3507 3508 <p><a name="streamuser"><h4>3.19.1.1.3 User and Password - mandatory for protected streams</h4></p> 3508 3509 <p> 3509 Streams on N TRIP Broadcasters may be protected. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per NTRIPBroadcaster through a registration procedure. Register through <u>http://register.rtcm-ntrip.org</u> for access to protected streams from EUREF and IGS.3510 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. 3510 3511 </p> 3511 3512 3512 3513 <p><a name="gettable"><h4>3.19.1.1.4 Get Table</h4></p> 3513 3514 <p> 3514 Use the 'Get Table' button to download the source-table from the N TRIPBroadcaster. 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.3515 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. 3515 3516 </p> 3516 3517 <p> … … 3523 3524 <p><u>Figure 39:</u> Broadcaster source-table.</p> 3524 3525 3525 <p><a name="ntripv"><h4>3.19.1.1.5 N TRIPVersion - mandatory</h4></p>3526 <p> 3527 Some limitations and deficiencies of the N TRIP Version 1 stream transport protocol are solved in NTRIPVersion 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> 3528 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: 3528 3529 </p> 3529 3530 … … 3532 3533 <tr></tr> 3533 3534 <tr><td><b>Option </b></td><td><b>Meaning</b></td></tr> 3534 <tr><td> 1</td><td>N TRIPVersion 1, TCP/IP</td></tr>3535 <tr><td> 2</td><td>N TRIPVersion 2 in TCP/IP mode</td></tr>3536 <tr><td> 2s</td><td>N TRIPVersion 2 in TCP/IP mode via SSL</td></tr>3537 <tr><td> R</td><td>N TRIPVersion 2 in RTSP/RTP mode</td></tr>3538 <tr><td> U</td><td>N TRIPVersion 2 in UDP mode</td></tr>3535 <tr><td> 1</td><td>Ntrip Version 1, TCP/IP</td></tr> 3536 <tr><td> 2</td><td>Ntrip Version 2 in TCP/IP mode</td></tr> 3537 <tr><td> 2s</td><td>Ntrip Version 2 in TCP/IP mode via SSL</td></tr> 3538 <tr><td> R</td><td>Ntrip Version 2 in RTSP/RTP mode</td></tr> 3539 <tr><td> U</td><td>Ntrip Version 2 in UDP mode</td></tr> 3539 3540 </table> 3540 3541 </p> 3541 3542 3542 3543 <p> 3543 If N TRIPVersion 2 is supported by the broadcaster:3544 If Ntrip Version 2 is supported by the broadcaster: 3544 3545 </p> 3545 3546 <ul> 3546 3547 <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 N TRIPVersion 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> 3548 3549 <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> 3549 3550 </ul> 3550 3551 <p> 3551 Select option '1' if you are not sure whether the broadcaster supports N TRIPVersion 2.</li>3552 Select option '1' if you are not sure whether the broadcaster supports Ntrip Version 2.</li> 3552 3553 </p> 3553 3554 … … 3558 3559 3559 3560 <p><img src="IMG/screenshot24.png"/></p> 3560 <p><u>Figure 40:</u> Stream distribution map derived from N TRIPBroadcaster source-table.</p>3561 <p><u>Figure 40:</u> Stream distribution map derived from Ntrip Broadcaster source-table.</p> 3561 3562 3562 3563 <p><a name="streamip"><h4>3.19.1.2 Add Stream - Coming from TCP/IP Port</h4></p> 3563 3564 <p> 3564 Button 'Add Stream' > 'Coming from TCP/IP Port' allows to retrieve streams via TCP directly from an IP address without using the N TRIPtransport protocol. For that you:3565 Button 'Add Stream' > '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: 3565 3566 <ul> 3566 3567 <li>Enter the IP address of the stream providing host.</li> … … 3573 3574 </p> 3574 3575 <p> 3575 Streams directly received from a TCP/IP port show up with an 'N' for 'No N TRIP' in the 'Streams' canvas on BNC's main window. Latitude and longitude are to be entered just for informal reasons.3576 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. 3576 3577 <p> 3577 3578 </p> … … 3581 3582 <p><a name="streamudp"><h4>3.19.1.3 Add Stream - Coming from UDP Port</h4></p> 3582 3583 <p> 3583 Button 'Add Stream' > 'Coming from UDP Port' allows to pick up streams arriving directly at one of the local host's UDP ports without using the N TRIPtransport protocol. For that you:3584 Button 'Add Stream' > '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: 3584 3585 <ul> 3585 3586 <li>Enter the local port number where the UDP stream arrives.</li> … … 3591 3592 </p> 3592 3593 <p> 3593 Streams directly received at a UDP port show up with a 'UN' for 'UDP, No N TRIP' in the 'Streams' canvas section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.3594 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. 3594 3595 <p> 3595 3596 3596 3597 <p><a name="streamser"><h4>3.19.1.4 Add Stream - Coming from Serial Port</h4></p> 3597 3598 <p> 3598 Button 'Add Stream' > 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the N TRIPtransport protocol. For that you:3599 Button 'Add Stream' > 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the Ntrip transport protocol. For that you: 3599 3600 <ul> 3600 3601 <li>Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ</li> … … 3625 3626 3626 3627 <p> 3627 Streams received from a serial connected GNSS receiver show up with an 'S' (for <u>S</u>erial Port, no N TRIP) in the 'Streams' canvas section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.3628 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. 3628 3629 <p> 3629 3630 … … 3754 3755 </li> 3755 3756 <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 N TRIP 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 NTRIPBroadcaster account.3757 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. 3757 3758 </li> 3758 3759 <li> 3759 EUREF as well as IGS adhere to an open data policy. Streams are made available through N TRIP 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 NTRIPBroadcaster 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.3760 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. 3760 3761 </li> 3761 3762 <li> … … 3772 3773 5.1. <a href=#history>Revision History</a><br> 3773 3774 5.2. <a href=#rtcm>RTCM</a><br> 3774 5.2.1 N TRIP<a href=#ntrip1>Version 1</a><br>3775 5.2.2 N TRIP<a href=#ntrip2>Version 2</a><br>3775 5.2.1 Ntrip <a href=#ntrip1>Version 1</a><br> 3776 5.2.2 Ntrip <a href=#ntrip2>Version 2</a><br> 3776 3777 5.2.3 RTCM <a href=#rtcm2>Version 2</a><br> 3777 3778 5.2.4 RTCM <a href=#rtcm3>Version 3</a><br> … … 3826 3827 <tr> 3827 3828 <td>Nov 2009 </td><td>Version 1.7 </td> 3828 <td>[Bug] RINEX Navigation file format<br> [Add] Upgrade to Qt Version 4.5.2<br> [Add] Support of N TRIP 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 NTRIPtransport 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> 3829 3830 </tr> 3830 3831 … … 3866 3867 <tr> 3867 3868 <td>Apr 2011 </td><td>Version 2.6 </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 N TRIPVersion 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> 3869 3870 </tr> 3870 3871 … … 3876 3877 <tr> 3877 3878 <td>Sep 2012 </td><td>Version 2.7 </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 N TRIPBroadcaster 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> 3879 3880 </tr> 3880 3881 … … 3917 3918 [Add] RTCM v3 SBAS Broadcast Ephemeris message 1043<br> 3918 3919 [Add] RTCM v3 BDS Broadcast Ephemeris message 63 (tentative)<br> 3919 [Bug] VRS support in sending NMEA in Auto/Manual mode to N TRIPBroadcaster<br>3920 [Add] Forwarding NMEA GNGGA to N TRIPBroadcaster<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> 3921 3922 [Bug] Stream failure/recovery reports<br> 3922 3923 [Add] Compute IODs from CRC over broadcast ephemeris and clock parameters<br> … … 3949 3950 [Add] SINEX Troposphere file output<br> 3950 3951 [Add] String for Operating System in logfile output<br> 3952 [Add] Full integration of 'rtcm3torinex'<br> 3951 3953 </td> 3952 3954 </tr> … … 3963 3965 </p> 3964 3966 3965 <p><a name="ntrip1"><h4>5.2.1 N TRIPVersion 1</h4></p>3966 3967 <p> 3968 'Networked Transport of RTCM via Internet Protocol' Version 1.0 (N TRIP) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. NTRIPis 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 N TRIP 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. NTRIPsupports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.3973 </p> 3974 3975 <p> 3976 N TRIP 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 NTRIPServer are acting as HTTP clients.3977 </p> 3978 3979 <p> 3980 N TRIP 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> 3974 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. 3975 </p> 3976 3977 <p> 3978 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. 3979 </p> 3980 3981 <p> 3982 Ntrip is an open none-proprietary protocol. Major characteristics of Ntrip's dissemination technique are: 3981 3983 <ul> 3982 3984 <li>Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and server platform resources available;</li> … … 3989 3991 3990 3992 <p> 3991 The N TRIP 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 NTRIPClient 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).3993 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). 3992 3994 </p> 3993 3995 … … 4002 4004 </p> 4003 4005 4004 <p><a name="ntrip2"><h4>5.2.2 N TRIPVersion 2</h4></p>4005 4006 <p> 4007 The major changes of N TRIPVersion 2 compared to Version 1.0 are:4006 <p><a name="ntrip2"><h4>5.2.2 Ntrip Version 2</h4></p> 4007 4008 <p> 4009 The major changes of Ntrip Version 2 compared to Version 1.0 are: 4008 4010 </p> 4009 4011 … … 4017 4019 </ul> 4018 4020 4019 <p>N TRIP 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 NTRIPcommunication 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. 4020 4022 </p> 4021 4023 … … 4307 4309 The purpose of this configuration is to feed a real-time GNSS engine with 4308 4310 observations from a remote reference stations. The configuration pulls a single 4309 stream from an N TRIPBroadcasters. It would of course be possible to pull4311 stream from an Ntrip Broadcasters. It would of course be possible to pull 4310 4312 several streams from different casters. Incoming observations are decoded, 4311 4313 synchronized and output through a local IP port and saved into a file. Failure … … 4386 4388 <li>File 'Upload.bnc'<br> 4387 4389 The purpose of this configuration is to upload orbits and clocks from a 4388 real-time GNSS engine to an N TRIPBroadcaster. For that the configuration reads4390 real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads 4389 4391 precise orbits and clocks in RTNET format. It also reads a stream carrying 4390 4392 Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast 4391 4393 Corrections and encodes them in RTCM Version 3 SSR messages to upload them to 4392 an N TRIPBroadcaster. The Broadcast Corrections stream is referred to satellite4394 an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satellite 4393 4395 Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format 4394 4396 and clocks in Clock RINEX format. … … 4405 4407 <li>File 'Combi.bnc'<br> 4406 4408 The purpose of this configuration is to pull several streams carrying Broadcast 4407 Corrections and a Broadcast Ephemeris stream from an N TRIPBroadcaster to4409 Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to 4408 4410 produce a combined Broadcast Corrections stream. BNC encodes the combination 4409 4411 product in RTCM Version 3 SSR messages and uploads that to an Ntrip … … 4644 4646 <tr><td><br><b>Add Stream</b></td><td><br><b>Meaning</b></td></tr> 4645 4647 <tr><td>mountPoints</td><td>Add stream coming from ...</td></tr> 4646 <tr><td>ntripVersion</td><td>N TRIPVersion</td></tr>4648 <tr><td>ntripVersion</td><td>Ntrip Version</td></tr> 4647 4649 </table> 4648 4650 </p> … … 4667 4669 <tr></tr> 4668 4670 <tr><td><b>Links</b></td></tr> 4669 <tr><td>N TRIP </td><td><u>http://igs.bkg.bund.de/ntrip/index</u></td></tr>4670 <tr><td>EUREF-IP N TRIPBroadcaster </td><td><u>http://www.euref-ip.net/home</u></td></tr>4671 <tr><td>IGS-IP N TRIPBroadcaster </td><td><u>http://www.igs-ip.net/home</u></td></tr>4672 <tr><td>IGS products N TRIPBroadcaster </td><td><u>http://products.igs-ip.net/home</u></td></tr>4673 <tr><td>IGS M-GEX N TRIPBroadcaster </td><td><u>http://mgex.igs-ip.net/home</u></td></tr>4674 <tr><td>IGS Central Bureau N TRIPBroadcaster </td><td><u>http://rt.igs.org</u></td></tr>4671 <tr><td>Ntrip </td><td><u>http://igs.bkg.bund.de/ntrip/index</u></td></tr> 4672 <tr><td>EUREF-IP Ntrip Broadcaster </td><td><u>http://www.euref-ip.net/home</u></td></tr> 4673 <tr><td>IGS-IP Ntrip Broadcaster </td><td><u>http://www.igs-ip.net/home</u></td></tr> 4674 <tr><td>IGS products Ntrip Broadcaster </td><td><u>http://products.igs-ip.net/home</u></td></tr> 4675 <tr><td>IGS M-GEX Ntrip Broadcaster </td><td><u>http://mgex.igs-ip.net/home</u></td></tr> 4676 <tr><td>IGS Central Bureau Ntrip Broadcaster </td><td><u>http://rt.igs.org</u></td></tr> 4675 4677 <tr><td>IGS Real-time Service </td><td><u>http://rts.igs.org</u></td></tr> 4676 4678 <tr><td>Distribution of IGS-IP streams </td><td><u>http://www.igs.oma.be/real_time/</u></td></tr> 4677 4679 <tr><td>Completeness and latency of IGS-IP data </td><td><u>http://www.igs.oma.be/highrate/</u></td></tr> 4678 <tr><td>N TRIPBroadcaster overview </td><td><u>http://www.rtcm-ntrip.org/home</u></td></tr>4679 <tr><td>N TRIPOpen Source software code </td><td><u>http://software.rtcm-ntrip.org</u></td></tr>4680 <tr><td>Ntrip Broadcaster overview </td><td><u>http://www.rtcm-ntrip.org/home</u></td></tr> 4681 <tr><td>Ntrip Open Source software code </td><td><u>http://software.rtcm-ntrip.org</u></td></tr> 4680 4682 <tr><td>EUREF-IP Project </td><td><u>http://www.epncb.oma.be/euref_IP</u></td></tr> 4681 4683 <tr><td>Real-time IGS Pilot Project </td><td><u>http://www.rtigs.net/pilot</u></td></tr> … … 4691 4693 <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> 4692 4694 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 N TRIP, 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> 4694 4696 4695 4697 <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.
