Changeset 7825 in ntrip
- Timestamp:
- Mar 8, 2016, 11:04:18 AM (9 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (49 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7824 r7825 170 170 2.15.5 <a href=#upsp3>SP3 File</a><br> 171 171 2.15.6 <a href=#uprinex>RNX File</a><br> 172 2.15.7 <a href=#upinter>Interval</a><br> 173 2.15.8 <a href=#upclksmpl>Sampling</a><br> 174 2.15.8.1 <a href=#upclkorb>Orbits</a><br> 175 2.15.8.2 <a href=#upclksp3>SP3</a><br> 176 2.15.8.3 <a href=#upclkrnx>RINEX</a><br> 177 2.15.9 <a href=#upcustom>Custom Trafo</a><br> 178 2.15.10 <a href=#upantex>ANTEX File</a><br> 172 2.15.7 <a href=#pidsidiod>PID, SID, IOD</a><br> 173 174 2.15.8 <a href=#upinter>Interval</a><br> 175 2.15.9 <a href=#upclksmpl>Sampling</a><br> 176 2.15.9.1 <a href=#upclkorb>Orbits</a><br> 177 2.15.9.2 <a href=#upclksp3>SP3</a><br> 178 2.15.9.3 <a href=#upclkrnx>RINEX</a><br> 179 2.15.10 <a href=#upcustom>Custom Trafo</a><br> 180 2.15.11 <a href=#upantex>ANTEX File</a><br> 179 181 2.16 <a href=#upeph><b>Upload Ephemeris</b></a><br> 180 182 2.16.1 <a href=#brdcserver>Host & Port</a><br> … … 257 259 <tr><td>26</td><td>Track of positions from BNC with Google Maps in background</td><td>2.13.4.3</td></tr> 258 260 <tr><td>27</td><td>Example for background map from Google Maps and OpenStreetMap (OSM) resources</td><td>2.13.4.3.1</td></tr> 259 <tr><td>28</td><td>BNC combining Broadcast Correction streams</td><td>2.14 .1.1</td></tr>260 <tr><td>29</td><td> BNC uploading the combined Broadcast Correction stream</td><td>2.14.1.1</td></tr>261 <tr><td>30</td><td> 'INTERNAL' PPP with BNC using combined Broadcast Correction stream</td><td>2.14.1.1</td></tr>262 <tr><td>31</td><td> Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'</td><td>2.15.3</td></tr>263 <tr><td>32</td><td>BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster</td><td>2.15.9</td></tr>261 <tr><td>28</td><td>BNC combining Broadcast Correction streams</td><td>2.14</td></tr> 262 <tr><td>29</td><td>INTERNAL' PPP with BNC using a combination of Broadcast Corrections</td><td>2.14</td></tr> 263 <tr><td>30</td><td>Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'</td><td>2.15.3</td></tr> 264 <tr><td>31</td><td>BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster</td><td>2.15.11</td></tr> 265 <tr><td>32</td><td>BNC uploading a combined Broadcast Correction stream</td><td>2.15.11</td></tr> 264 266 <tr><td>33</td><td>BNC producing Broadcast Ephemeris stream from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster</td><td>2.16.3</td></tr> 265 267 <tr><td>34</td><td>Bandwidth consumption of RTCM streams received by BNC</td><td>2.18.2</td></tr> … … 328 330 <p> 329 331 <b>Documentation</b><br><br> 330 BNC provides context-sensitive help (<i>What's This</i>) related to specific objects. It furthermore comes with the here presented documentation, available as part of the software and as a PDF file. Responsible for o nline and offline documentationand example configurations is Dr. Georg Weber [georg.weber@bkg.bund.de].332 BNC provides context-sensitive help (<i>What's This</i>) related to specific objects. It furthermore comes with the here presented documentation, available as part of the software and as a PDF file. Responsible for offline documentation as well as online documentation at <u>http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/src/bnchelp.html</u> and example configurations is Dr. Georg Weber [georg.weber@bkg.bund.de]. 331 333 </p> 332 334 … … 401 403 <li>Read GNSS orbits and clocks in a plain ASCII format from an IP port. They can be produced by a real-time GNSS engine such as RTNET and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. BNC will then</li> 402 404 <ul> 403 <li>Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and cross-trackcomponents;</li>405 <li>Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and out-of-plane components;</li> 404 406 <li>Upload Broadcast Corrections as an RTCM Version 3 stream to an Ntrip Broadcaster;</li> 405 407 <li>Refer the orbit and clock corrections to a specific reference system;</li> … … 603 605 <p> 604 606 Records of BNC's activities are shown in the 'Log' tab which is part of the 'Log' canvas. The bandwidth consumption per stream, the latency of incoming observations, and a PPP time series for coordinate displacements are also part of that canvas and shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs. 607 </p> 608 609 <p> 610 Configuration options are usually first set using BNC's Graphical User Interface (GUI), then saved in a configuration file. For routine operations in batch mode all of BNC's configuration options can be extracted from the configuration file and applied using the program's Command Line Interface (CLI). 605 611 </p> 606 612 … … 1147 1153 </p> 1148 1154 <p> 1149 The general documentation approach is to create a separate chapter for each processing option in a sequence which follows the layout of BNC's Graphical User Interface (GUI). The advantage is that searching for help by means of the Table of Contents is quite convenient.1155 The general documentation approach is to create a separate chapter for each processing option in a sequence which follows the layout of BNC's Graphical User Interface (GUI). The advantage is that searching for help by means of the document's Table of Contents is quite convenient. 1150 1156 1151 1157 </p> … … 1199 1205 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 do not know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.</p> 1200 1206 <p> 1201 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 Broadcaster s. If this is not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet.1207 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 Broadcaster you need to access. If this is not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet. 1202 1208 </p> 1203 1209 … … 1265 1271 <p><h4>2.3.3 <a name="genconf">Reread Configuration - optional</h4></p> 1266 1272 <p> 1267 When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that, you force the program to reread parts of its configuration in pre-defined intervals from thedisk. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in-between edited options become effective without interrupting uninvolved threads.1268 </p> 1269 1270 <p> 1271 Note that thefollowing configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data:1273 When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that, you force the program to reread parts of its configuration in pre-defined intervals from disk. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in-between edited options become effective without interrupting uninvolved threads. 1274 </p> 1275 1276 <p> 1277 Note that following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data: 1272 1278 </p> 1273 1279 <p> … … 1326 1332 1327 1333 <p> 1328 Please note that RTCM Version 3 messages 1084 for GLONASS observations do not contain the channel numbers. However, thesemessages can only be converted to RINEX when you add messages which include the channel numbers. This could be done by means of an additional stream carrying 1087 GLONASS observation messages or an additional stream carrying 1020 GLONASS ephemeris messages. You could also consider setting up a stream which contains both, the 1084 and the 1020 messages.1334 Please note that RTCM Version 3 messages 1084 for GLONASS observations do not contain the GLONASS channel numbers. These observation messages can only be converted to RINEX when you add messages which include the channel numbers. This could be done by means of an additional stream carrying 1087 GLONASS observation messages or an additional stream carrying 1020 GLONASS ephemeris messages. You could also consider setting up a stream which contains both, the 1084 and the 1020 messages. 1329 1335 </p> 1330 1336 <p> … … 1353 1359 </pre> 1354 1360 <p> 1355 If several streams show up with exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the filename leading e.g. to hourly RINEX Version 2 Observation files like</p>1361 If several streams show up with exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the filename, leading e.g. to hourly RINEX Version 2 Observation files like</p> 1356 1362 <pre> 1357 1363 BRUS{ddd}{h}_0.{yy}O … … 1372 1378 <p> 1373 1379 <table> 1374 <tr><td><b> Parameter</b></td><td><b> # Char.</b></td><td><b> Meaning</b></td></tr>1380 <tr><td><b>Filename Parameter </b></td><td><b> # Char.</b></td><td><b> Meaning</b></td></tr> 1375 1381 <tr><td>Name</td><td> 9</td><td> Site, station and country code</td></tr> 1376 1382 <tr><td>S</td><td> 1</td><td> Data source</td></tr> … … 1443 1449 <br>- ANTENNA: DELTA H/E/N 1444 1450 <br>- WAVELENGTH FACT L1/2 (RINEX Version 2) 1445 <br>- SYS / # / OBS TYPES (for RINEX Version 3 files, will be ignored when writingVersion 2 files)</li>1451 <br>- SYS / # / OBS TYPES (for RINEX Version 3 files, will be ignored in Version 2 files)</li> 1446 1452 <li>They may contain any other optional complete header record as defined in the RINEX documentation.</li> 1447 1453 <li>They should also contain an empty header record of type 1448 <br>- # / TYPES OF OBSERV (only RINEX Version 2, will be ignored when writing RINEXVersion 3 files)1454 <br>- # / TYPES OF OBSERV (only RINEX Version 2, will be ignored when in Version 3 files) 1449 1455 <br>BNC will include these lines in the final RINEX file header together with an additional 1450 1456 <br>- COMMENT … … 1491 1497 Tick check box 'Skeleton mandatory' in case you want that RINEX files are only produced when skeleton files are available for BNC. If no skeleton file is available for a particular source, then no RINEX observation file will be produced from the affected stream. 1492 1498 </p> 1493 <p>Note that a skeleton file contains RINEX header information such as receiver and antenna types. In case of stream conversion to RINEX Version 3, a skeleton file should also contain information on potentially available observation types. A missing skeleton file will therefore enforce BNC to only save a default set of RINEX 3 observation types.1499 <p>Note that a skeleton file contains RINEX header information such as receiver and antenna types. In case of stream conversion to RINEX Version 3, a skeleton file should also contain information on potentially available observation types. A missing skeleton file will force BNC to only save a default set of RINEX 3 observation types. 1494 1500 </p> 1495 1501 1496 1502 <p><h4>2.4.7 <a name="rnxscript">Script - optional</h4></p> 1497 1503 <p> 1498 Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that, specify the full path of thescript/batch file. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac OS X systems).1504 Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that, specify the full path to such script/batch file. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac OS X systems). 1499 1505 </p> 1500 1506 <p> … … 1515 1521 </p> 1516 1522 <p> 1517 The default 'Signal priority' list is an empty option string, meaning a priority sequence of 'CWPX_?' attributes when mapping RINEX 3 to RINEX 2. The meaning of this sequence of characters - take it as an example - is as follows:1523 Default 'Signal priority' list is an empty option string, meaning a priority sequence of 'CWPX_?' attributes when mapping RINEX 3 to RINEX 2. The meaning of this sequence of characters - take it as an example - is as follows: 1518 1524 <ul> 1519 1525 <li>Signals with attribute 'C' enjoy the highest priority. If such a Version 3 observation becomes available, it is presented as RINEX Version 2 observation if that is the format you wish to see. Observations with other attributes are being ignored.</li> … … 1554 1560 <p><h4>2.5 <a name="ephemeris">RINEX Ephemeris</h4></p> 1555 1561 <p> 1556 Broadcast Ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3 e.g. as message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (tentative, BDS/BeiDou). The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'.1562 Broadcast Ephemeris can be saved in RINEX Navigation files when received e.g. via RTCM Version 3 message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (BDS/BeiDou, tentative message number). The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'. 1557 1563 </p> 1558 1564 <p> … … 1579 1585 <p><h4>2.5.1 <a name="ephdir">Directory - optional</h4></p> 1580 1586 <p> 1581 Specify a path for saving Broadcast Ephemeris data asRINEX Navigation files. If the specified directory does not exist, BNC will not create RINEX Navigation files. Default value for Ephemeris 'Directory' is an empty option field, meaning that no RINEX Navigation files will be created.1587 Specify a path for saving Broadcast Ephemeris data in RINEX Navigation files. If the specified directory does not exist, BNC will not create RINEX Navigation files. Default value for Ephemeris 'Directory' is an empty option field, meaning that no RINEX Navigation files will be created. 1582 1588 </p> 1583 1589 … … 1592 1598 </p> 1593 1599 <p> 1594 The source code for BNC comes with an example Perl script 'test_tcpip_client.pl' that allows you to read BNC's ASCII ephemerisoutput from the IP port.1600 The source code for BNC comes with an example Perl script 'test_tcpip_client.pl' that allows you to read BNC's ephemeris ASCII output from the IP port. 1595 1601 </p> 1596 1602 … … 1615 1621 <p><h4>2.6 <a name="reqc">RINEX Editing & QC</h4></p> 1616 1622 <p> 1617 Besides stream conversion from RTCM to RINEX, BNC allows editing RINEX files or concatenate their content. RINEX Observation and Navigation files can be handled. BNC can also carry out a RINEX file Quality Check. In summary and besides Stream <u><b>T</b></u>ranslation this functionality in BNC covers1623 Besides stream conversion from RTCM to RINEX, BNC allows editing RINEX files or concatenate their content. RINEX Observation and Navigation files can be handled. BNC can also carry out a RINEX file Quality Check. In summary and besides Stream <u><b>T</b></u>ranslation, this functionality in BNC covers 1618 1624 <ul> 1619 1625 <li>File <u><b>E</b></u>diting and concatenation</li> … … 1627 1633 </ul> 1628 1634 </ul> 1629 and hence follows UNAVCO's famous TEQC program (see Estey and Meertens 1999). The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License with full GUI support and instantaneousgraphics output.1635 and hence follows UNAVCO's famous TEQC program (see Estey and Meertens 1999). The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License with full GUI support and graphics output. 1630 1636 </p> 1631 1637 … … 1644 1650 </p> 1645 1651 <p> 1646 When specifying several input files, BNC will concatenate their contents. In case of RINEX Observation input files with different observation type header records, BNC will output only one s pecific set of adjusted observation type records in the RINEX header, which fits to the whole file content.1652 When specifying several input files, BNC will concatenate their contents. In case of RINEX Observation input files with different observation type header records, BNC will output only one set of adjusted observation type records in the RINEX header, which fits to the whole file content. 1647 1653 </p> 1648 1654 <p> … … 1661 1667 1662 1668 <p> 1663 Note that logfiles from analyzing RINEX files may become quite large. Hence, BNC provides an option 'Summary only' to limit thislogfile content to some essential information in case 'Action' is set to 'Analyze'. The following is an example for a RINEX quality check analysis logfile:1669 Note that logfiles from analyzing RINEX files may become quite large. Hence, BNC provides an option 'Summary only' to limit logfile content to some essential information in case 'Action' is set to 'Analyze'. The following is an example for a RINEX quality check analysis logfile: 1664 1670 <pre> 1665 1671 QC Format Version : 1.0 … … 1961 1967 Parameter <keyName> stands for the name of an option contained in the configuration file and <keyValue> stands for the value you want to assign to it. This functionality may be helpful in the 'RINEX Editing & QC' context when running BNC on a routine basis for maintaining a RINEX file archive. 1962 1968 </p> 1963 The following example for a Linux platform calls BNC in 'no window' mode with a local configuration file 'rnx.conf' for concatenating four 15min RINEX files from station TLSE residing in the localdirectory to produce an hourly RINEX Version 3 file with 30 seconds sampling interval:1969 The following example for a Linux platform calls BNC in 'no window' mode with a local configuration file 'rnx.conf' for concatenating four 15min RINEX files from station TLSE residing in the working directory to produce an hourly RINEX Version 3 file with 30 seconds sampling interval: 1964 1970 </p> 1965 1971 <pre> … … 1969 1975 </pre> 1970 1976 <p> 1971 You may use asterisk '*' and/or question mark '?' wildcard characters as shown with the following globbing command line option to specify a selection of files in a localdirectory:1977 You may use asterisk '*' and/or question mark '?' wildcard characters as shown with the following globbing command line option to specify a selection of files in the working directory: 1972 1978 <pre> 1973 1979 --key reqcObsFile "tlse*" … … 2036 2042 <p><h4>2.7 <a name="sp3comp">SP3 Comparison</h4></p> 2037 2043 <p> 2038 BNC allows to compare the contents of two files containingGNSS orbit and clock data in SP3 format. SP3 ASCII files basically contain a list of records over a certain period of time. Each record carries a time tag, the XYZ position of the satellite's Center of Mass at that time and the corresponding satellite clock value. Both SP3 files may contain some records for different epochs. If so, then BNC only compares records for identical epochs. BNC accepts that a specific GNSS system or a specific satellite is only available from one of the SP3 files. Note that BNC does not interpolate orbits when comparing SP3 files.2044 BNC allows to compare the contents of two files with GNSS orbit and clock data in SP3 format. SP3 ASCII files basically contain a list of records over a certain period of time. Each record carries a time tag, the XYZ position of the satellite's Center of Mass at that time and the corresponding satellite clock value. Both SP3 files may contain some records for different epochs. If so, then BNC only compares records for identical epochs. BNC accepts that a specific GNSS system or a specific satellite is only available from one of the SP3 files. Note that BNC does not interpolate orbits when comparing SP3 files. 2039 2045 </p> 2040 2046 <p> … … 2044 2050 <p><h4>2.7.1 <a name="sp3input">Input SP3 Files - optional</h4></p> 2045 2051 <p> 2046 Specify the full path of two SP3 files separated by acomma.2052 Specify the full paths of two SP3 files, separate them by comma. 2047 2053 </p> 2048 2054 … … 2179 2185 </p> 2180 2186 <p> 2181 When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may be important to understand that they are not corrected for the conventional periodic relativistic effect. Chapter 10 of the IERS Conventions 2003 mentions that the conventional periodic relativistic correction to the satellite clock (to be added to the broadcast clock) is computed as dt = -2 (R * V) / c^2 where R * V is the scalar product of the satellite position and velocity and c is the speed of light. This can also be found in the GPS Interface Specification, IS-GPS-200, Revision D, 7 March 2006. 2182 </p> 2183 2184 <p> 2185 Orbit corrections are provided in along-track, cross-track and radial components. These components are defined in the Earth-centered, Earth-fixed reference frame of the Broadcast Ephemeris. For an observer in this frame, the along-track component is aligned in both direction and sign with the velocity vector, the cross-track component is perpendicular to the plane defined by the satellite position and velocity vectors, and the radial direction is perpendicular to the along track and cross-track ones. The three components form a right-handed orthogonal system. 2187 When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may be important to understand that they are not corrected for the conventional periodic relativistic effect. Chapter 10 of the IERS Conventions 2003 mentions that the conventional periodic relativistic correction to the satellite clock (to be added to the broadcast clock) is computed as 2188 </p> 2189 2190 <pre> 2191 dt = -2 (R * V) / c<sup>2</sup> 2192 </pre> 2193 2194 <p> 2195 where R * V is the scalar product of the satellite position and velocity and c is the speed of light. This can also be found in the GPS Interface Specification, IS-GPS-200, Revision D, 7 March 2006. 2196 </p> 2197 2198 <p> 2199 Orbit corrections are provided in along-track, out-of-plane and radial components. These components are defined in the Earth-Centered, Earth-Fixed reference frame of the Broadcast Ephemeris. For an observer in this frame, the along-track component is aligned in both direction and sign with the velocity vector, the out-of-plane component is perpendicular to the plane defined by the satellite position and velocity vectors, and the radial direction is perpendicular to the along track and out-of-plane ones. The three components form a right-handed orthogonal system. 2186 2200 </p> 2187 2201 … … 2270 2284 <li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li> 2271 2285 <li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li> 2272 <li> Cross-trackComponent of Orbit Correction to Broadcast Ephemeris [m]</li>2286 <li>Out-of-plane Component of Orbit Correction to Broadcast Ephemeris [m]</li> 2273 2287 <li>Velocity of Radial Component of Orbit Correction to Broadcast Ephemeris [m/s]</li> 2274 2288 <li>Velocity of Along-track Component of Orbit Correction to Broadcast Ephemeris [m/s]</li> 2275 <li>Velocity of Cross-trackComponent of Orbit Correction to Broadcast Ephemeris [m/s]</li>2289 <li>Velocity of Out-of-plane Component of Orbit Correction to Broadcast Ephemeris [m/s]</li> 2276 2290 </ul> 2277 2291 </p> … … 2630 2644 <p><h4>2.9.3 <a name="syncsample">Sampling - mandatory if 'File' or 'Port' is set</h4></p> 2631 2645 <p> 2632 Select thesynchronized observation output sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs. This is the default value.2646 Select a synchronized observation output sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs. This is the default value. 2633 2647 </p> 2634 2648 … … 2920 2934 <p><h4>2.13 <a name="pppclient">PPP Client</h4></p> 2921 2935 <p> 2922 BNC can derive coordinates for rover positions following the Precise Point Positioning (PPP) approach. It uses code or code plus phase data from one or more GNSS systems in ionosphere-free linear combinations P3, L3, or P3&L3. Besides pulling streams of observations from dual frequency GNSS receiver, this also2936 BNC can derive coordinates for rover positions following the Precise Point Positioning (PPP) approach. It uses code or code plus phase data from one or more GNSS systems in ionosphere-free linear combinations P3, L3, or P3&L3. Besides pulling streams of observations from a dual frequency GNSS receiver, this 2923 2937 <ul> 2924 2938 <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> (Caissy et al. 2012). Stream 'CLK11' on Ntrip Broadcaster 'products.igs-ip.net:2101' is an example.</li> 2925 2939 <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> 2926 2940 </ul> 2927 Note that Broadcast Ephemeris parameters pass througha plausibility check in BNC which allows to ignore incorrect or outdated ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile.2941 Note that Broadcast Ephemeris parameters pass a plausibility check in BNC which allows to ignore incorrect or outdated ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile. 2928 2942 </p> 2929 2943 … … 2983 2997 <p> 2984 2998 <u>Debugging</u><br> 2985 Note that for debugging purposes BNC's real-time PPP functionality can also be used offline. Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Example:2999 Note that for debugging purposes, BNC's real-time PPP functionality can also be used offline. Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Example: 2986 3000 <pre> 2987 3001 bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\RAW … … 3007 3021 </p> 3008 3022 <p> 3009 If you do not specify a 'Corrections stream' BNC will fall back from a PPP solution to a Single Point Positioning (SPP) solution.3023 If you do not specify a 'Corrections stream', BNC will fall back from a PPP solution to a Single Point Positioning (SPP) solution. 3010 3024 </p> 3011 3025 … … 3028 3042 <p><h4>2.13.1.7 <a name="pppmarkcoor">Coordinates File - optional </h4></p> 3029 3043 <p> 3030 Enter the full path to an ASCII file which specifies all streams or files from stationary or mobile receivers you possibly may want to process. Specifying a 'Coordinates file' is optional. If it exists, it should contain one record per stream or file with the following parameters separated by blank characters:3044 Enter the full path to an ASCII file which specifies all observation streams or files from stationary or mobile receivers you possibly may want to process. Specifying a 'Coordinates file' is optional. If it exists, it should contain one record per stream or file with the following parameters separated by blank characters: 3031 3045 </p> 3032 3046 <p> … … 3044 3058 'JPSREGANT_SD_E ' (no radome) 3045 3059 'LEIAT504 NONE' (no radome) 3046 'LEIAR25.R3 LEIT' (radome )</pre>3060 'LEIAR25.R3 LEIT' (radome is LEIT)</pre> 3047 3061 Leave antenna name blank if you do not want to correct observations for APC offsets and variations or if you do not know the antenna name.</li><br> 3048 3062 <li> … … 3094 3108 </pre> 3095 3109 <p> 3096 Note that the only mandatory parameters in this file are the 'Station' parameters in the first column, each standing for an observation stream's mountpoint or the 4-character station ID of a RINEX filename. The following shows further valid examples for records of a 'Coordinates file'.3110 Note again that the only mandatory parameters in this file are the 'Station' parameters in the first column, each standing for an observation stream's mountpoint or the 4-character station ID of a RINEX filename. The following shows further valid examples for records of a 'Coordinates file'. 3097 3111 </p> 3098 3112 … … 3266 3280 Depending on selected processing options you find 'GPS Time' stamps (yyyy-mm-dd_hh:mm:ss.sss) followed by 3267 3281 <ul> 3282 <li>SATNUM: Number of satellites per GNSS,</li> 3268 3283 <li>RES: Code and phase residuals for contributing GNSS systems in [m]<br>Given per satellite with cIF/lIF for ionosphere-free linear combination of code/phase observations,</li> 3269 3284 <li>CLK: Receiver clock errors in [m], </li> 3270 <li> AMB: L3 biases, also known as 'floated ambiguities'<br>Given per satellite with 'nEpo' = number of epochs since last ambiguity reset,3285 <li>TRP: A priori and correction values of tropospheric zenith delay in [m], 3271 3286 <li>OFFGLO: Time offset between GPS time and GLONASS time in [m], 3272 3287 <li>OFFGAL: Time offset between GPS time and Galileo time in [m], 3273 3288 <li>OFFBDS: Time offset between GPS time and BDS time in [m], 3274 <li> TRP: A priori and correction values of tropospheric zenith delay in [m],3275 <li>MOUNTPOINT: Here 'CUT07' with X /Y/Z position in [m] and dN/dE/dU in [m] for North, East, and Up displacements compared to a priori marker coordinates.</li>3289 <li>AMB: L3 biases, also known as 'floated ambiguities'<br>Given per satellite with 'nEpo' = number of epochs since last ambiguity reset, 3290 <li>MOUNTPOINT: Here 'CUT07' with XYZ position in [m] and dN/dE/dU in [m] for North, East, and Up displacements compared to a priori marker coordinates.</li> 3276 3291 </ul> 3277 3292 Estimated parameters are presented together with their formal errors as derived from the implemented filter. The PPP algorithm includes outlier and cycle slip detection. … … 3533 3548 3534 3549 <p> 3535 with 'z' being the zenith distance to the involved satellite can be applied instead of the simple weight function 'P = 1' .3550 with 'z' being the zenith distance to the involved satellite can be applied instead of the simple weight function 'P = 1' independent from satellite elevation angles. 3536 3551 </p> 3537 3552 <ul> … … 3572 3587 </p> 3573 3588 <p> 3574 This so-called Quick-Startoption allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the known position throughout the defined period. A value of '60' seconds is likely to be an appropriate choice for 'Seeding'. Default is an empty option field, meaning that you do not want BNC to start in Quick-Start mode.3589 This so-called <u>Quick-Start</u> option allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the known position throughout the defined period. A value of '60' seconds is likely to be an appropriate choice for 'Seeding'. Default is an empty option field, meaning that you do not want BNC to start in Quick-Start mode. 3575 3590 <p> 3576 3591 You may need to create your own reference coordinate beforehand through running BNC for an hour in normal mode before applying the 'Seeding' option. Do not forget to introduce realistic North/East/Up sigmas under panel 'PPP (2)' corresponding to the coordinate's precision. … … 3578 3593 3579 3594 <p> 3580 'Seeding' has also a function for bridging gaps in PPP solutions from failures caused e.g. by longer lasting outages. Should the time span between two consecutive solutions exceed the limit of 60 seconds (maximum solution gap, hard-wired), the algorithm fixes the latest derived coordinate for a period of 'Seeding' seconds. This option avoids time-consuming reconvergences and makes especially sense for stationarily operated receivers where convergence can be enforced because a good approximation for the receiver position is known.3595 'Seeding' has also a function for <u>bridging gaps</u> in PPP solutions from failures caused e.g. by longer lasting outages. Should the time span between two consecutive solutions exceed the limit of 60 seconds (maximum solution gap, hard-wired), the algorithm fixes the latest derived coordinate for a period of 'Seeding' seconds. This option avoids time-consuming reconvergences and makes especially sense for stationary operated receivers where convergence can be enforced because a good approximation for the receiver position is known. 3581 3596 </p> 3582 3597 … … 3598 3613 </p> 3599 3614 <p> 3600 Note that a PPP dicplacements time series makes only sense for a stationar ily operated receiver.3615 Note that a PPP dicplacements time series makes only sense for a stationary operated receiver. 3601 3616 </p> 3602 3617 … … 3653 3668 <p><h4>2.14 <a name="combi">Combine Corrections</h4></p> 3654 3669 <p> 3655 BNC allows processing several orbit and clock correction streams in real-time to produce, encode, upload and save a combination of Broadcast Corrections from various providers. All corrections must refer to satellite Antenna Phase Centers (APC). It is so far only the satellite clock corrections which are combined while orbit corrections in the combination product as well as the product update rates are just taken over from one of the incoming Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference imposes the potential to introduce some analysis inconsistencies. We may therefore eventually consider improvements on this approach. The clock combination can be based either on a plain 'Single-Epoch' or on a Kalman 'Filter' approach. 3656 </p> 3657 <p> 3658 In the Kalman Filter approach, satellite clocks estimated by individual Analyses Centers (ACs) are used as pseudo observations within the adjustment process. Each observation is modeled as a linear function (actually a simple sum) of three estimated parameters: AC specific offset, satellite specific offset common to all ACs, and the actual satellite clock correction, which represents the result of the combination. These three parameter types differ in their statistical properties. The satellite clock offsets are assumed to be static parameters while AC specific and satellite specific offsets are stochastic parameters with appropriate white noise. 3659 The solution is regularized by a set of minimal constraints. After a change of one of the three values 'SSR Provider ID', 'SSR Solution ID', or 'IOD SSR', the satellite clock offsets belonging to the corresponding analysis center are reset in the adjustment. 3670 BNC allows processing several orbit and clock correction streams in real-time to produce, encode, upload and save a combination of Broadcast Corrections from various providers. All corrections must refer to satellite Antenna Phase Centers (APC). It is so far only the satellite clock corrections which are combined by BNC while orbit corrections in the combination product as well as product update rates are just taken over from one of the incoming Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference imposes the potential to introduce some analysis inconsistencies. We may therefore eventually consider improvements on this approach. The clock combination can be based either on a plain 'Single-Epoch' or on a Kalman 'Filter' approach. 3671 </p> 3672 <p> 3673 In the Kalman Filter approach, satellite clocks estimated by individual Analyses Centers (ACs) are used as pseudo observations within the adjustment process. Each observation is modeled as a linear function (actually a simple sum) of three estimated parameters: AC specific offset, satellite specific offset common to all ACs, and the actual satellite clock correction, which represents the result of the combination. These three parameter types differ in their statistical properties. The satellite clock offsets are assumed to be static parameters while AC specific and satellite specific offsets are stochastic parameters affected by white noise. 3674 </p> 3675 <p> 3676 The solution is regularized by a set of minimal constraints. In case of a change of the 'SSR Provider ID', 'SSR Solution ID', or 'IOD SSR' (see section 'Upload Corrections'), the satellite clock offsets belonging to the corresponding analysis center are reset in the adjustment. 3660 3677 </p> 3661 3678 <p> … … 3665 3682 In view of IGS real-time products, the 'Combine Corrections' functionality has been integrated in BNC (Weber and Mervart 2010) because 3666 3683 <ul> 3667 <li>The software with its Graphic User Interface and widerange of supported Operating Systems represents a perfect platform to process many Broadcast Correction streams in parallel;</li>3684 <li>The software with its Graphic User Interface and range of supported Operating Systems represents a perfect platform to process many Broadcast Correction streams in parallel;</li> 3668 3685 <li>Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;</li> 3669 3686 <li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li> … … 3671 3688 <li>An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;</li> 3672 3689 <li>It enables a BNC PPP user to follow his own preference in combining streams from individual ACs for Precise Point Positioning;</li> 3673 <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 throughdirect application of the combined stream in a PPP solution even without prior upload to an Ntrip Broadcaster;</li>3690 <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 by direct application of the combined stream in a PPP solution even without prior upload to an Ntrip Broadcaster;</li> 3674 3691 <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> 3675 3692 </ul> … … 3705 3722 </p> 3706 3723 <p> 3707 Note that BNC can produce an internal PPP solution from combined Broadcast Corrections. For that you have to specify the keyword 'INTERNAL' as 'Corrections' mountpoint in the PPP (1) panel. 3708 </p> 3709 3710 <p><h4>2.14.1 <a name="combimounttab">Combine Corrections Table - optional</h4></p> 3711 <p> 3712 Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Correction mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the Antenna Phase Center (APC) related stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination. 3713 </p> 3714 <p> 3715 The sequence of entries in the 'Combine Corrections' table is not of importance. Note that the orbit information in the final combination stream is just copied from one of the incoming streams. The stream used for providing the orbits may vary over time: if the orbit-providing stream has an outage then BNC switches to the next remaining stream for getting hold of the orbit information.</p> 3716 <p> 3717 It is possible to specify only one Broadcast Ephemeris correction stream in the 'Combine Corrections' table. Instead of combining corrections from several sources, BNC will then merge the single corrections stream with Broadcast Ephemeris to save results in SP3 and/or Clock RINEX format when specified accordingly under the 'Upload Corrections' panel. Note that in such a BNC application you must not pull more than one Broadcast Ephemeris correction stream even if a second stream would provide the same corrections from a backup caster. 3718 </p> 3719 <p> 3720 Default is an empty 'Combine Corrections' table meaning that you do not want BNC to combine orbit and clock correction streams. 3721 </p> 3722 3723 <p><h4>2.14.1.1 <a name="combiadd">Add Row, Delete - optional</h4></p> 3724 <p> 3725 Hit 'Add Row' button to add another row to the 'Combine Corrections' table or hit the 'Delete' button to delete the highlighted row(s). 3726 </p> 3727 3728 <p> 3729 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. 3730 </p> 3731 3732 <br> 3724 The following screenshot shows an example setup of BNC when combining Broadcast Correction streams CLK11, CLK21, CLK91, and CLK80. 3725 </p> 3726 3733 3727 <p><img src="IMG/screenshot20.png"/></p> 3734 3728 <p><u>Figure 28:</u> BNC combining Broadcast Correction streams</p> 3735 3729 <p></p> 3736 <p> <img src="IMG/screenshot21.png"/></p>3737 <p><u>Figure 29:</u> BNC uploading the combined Broadcast Correction stream</p> 3738 < p></p>3730 <p> 3731 Note that BNC can produce an internal PPP solution from combined Broadcast Corrections. For that you have to specify the keyword 'INTERNAL' as 'Corrections stream' in the PPP (1) panel. The following example combines correction streams IGS01 and IGS02 and simultaneously carries out a PPP solution with observations from stream FFMJ1 to allow monitoring the quality of the combination product in the space domain. 3732 </p> 3739 3733 <p><img src="IMG/screenshot23.png"/></p> 3740 <p><u>Figure 30:</u> 'INTERNAL' PPP with BNC using combined Broadcast Correction stream</p> 3734 <p><u>Figure 29:</u> 'INTERNAL' PPP with BNC using a combination of Broadcast Corrections</p> 3735 3736 <p><h4>2.14.1 <a name="combimounttab">Combine Corrections Table - optional</h4></p> 3737 <p> 3738 Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Correction mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the Antenna Phase Center (APC) related correction stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination. 3739 </p> 3740 <p> 3741 The sequence of entries in the 'Combine Corrections' table is not of importance. Note that the orbit information in the final combination stream is just copied from one of the incoming streams. The stream used for providing the orbits may vary over time: if the orbit-providing stream has an outage then BNC switches to the next remaining stream for getting hold of the orbit information.</p> 3742 <p> 3743 It is possible to specify only one Broadcast Ephemeris correction stream in the 'Combine Corrections' table. Instead of combining corrections from several sources, BNC will then merge the single corrections stream with Broadcast Ephemeris to allow saving results in SP3 and/or Clock RINEX format when specified accordingly under the 'Upload Corrections' panel. Note that in such a BNC application you must not pull more than one Broadcast Ephemeris correction stream even if a second stream would provide the same corrections from a backup caster. 3744 </p> 3745 <p> 3746 Default is an empty 'Combine Corrections' table, meaning that you do not want BNC to combine orbit and clock correction streams. 3747 </p> 3748 3749 <p><h4>2.14.1.1 <a name="combiadd">Add Row, Delete - optional</h4></p> 3750 <p> 3751 Hit 'Add Row' button to add another row to the 'Combine Corrections' table or hit the 'Delete' button to delete the highlighted row(s). 3752 </p> 3741 3753 3742 3754 <p><h4>2.14.1.2 <a name="combimethod">Method - mandatory if 'Combine Corrections' table is populated</h4></p> … … 3761 3773 <p><h4>2.15 <a name="upclk">Upload Corrections</h4></p> 3762 3774 <p> 3763 BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and cross-trackcomponents if they are<ol type=a>3775 BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and out-of-plane components if they are<ol type=a> 3764 3776 <li> 3765 3777 either generated by BNC as a combination of several individual Broadcast Correction streams coming from an number of real-time Analysis Centers (ACs), see section 'Combine Corrections',</li> … … 3776 3788 <li>Calculate XYZ coordinates from Broadcast Ephemeris orbits. </li> 3777 3789 <li>Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS08 orbits. </li> 3778 <li>Transform these differences into radial, along-track and cross-trackcorrections to Broadcast Ephemeris orbits. </li>3790 <li>Transform these differences into radial, along-track and out-of-plane corrections to Broadcast Ephemeris orbits. </li> 3779 3791 <li>Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris clocks and IGS08 clocks. </li> 3780 3792 <li>Encode Broadcast Ephemeris orbit and clock corrections in RTCM Version 3 format. </li> … … 3873 3885 </p> 3874 3886 <p> 3875 When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may be important to understand that they are not corrected for the conventional periodic relativistic effect. Chapter 10 of the IERS Conventions 2003 mentions that the conventional periodic relativistic correction to the satellite clock (to be added to the broadcast clock) is computed as dt = -2 (R * V) / c^2 where R *V is the scalar product of the satellite position and velocity and c is the speed of light. This can also be found in the GPS Interface Specification, IS-GPS-200, Revision D, 7 March 2006. 3887 When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may be important to understand that they are not corrected for the conventional periodic relativistic effect. Chapter 10 of the IERS Conventions 2003 mentions that the conventional periodic relativistic correction to the satellite clock (to be added to the broadcast clock) is computed as 3888 <pre> 3889 dt = -2 (R * V) / c<sup>2</sup> 3890 </pre> 3891 where R *V is the scalar product of the satellite position and velocity and c is the speed of light. This can also be found in the GPS Interface Specification, IS-GPS-200, Revision D, 7 March 2006. 3876 3892 </p> 3877 3893 … … 4070 4086 4071 4087 <p><img src="IMG/screenshot38.png"/></p> 4072 <p><u>Figure 3 1:</u> Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'</p>4088 <p><u>Figure 30:</u> Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'</p> 4073 4089 4074 4090 <p><h4>2.15.4 <a name="upcom">Center of Mass - optional</h4></p> … … 4117 4133 </p> 4118 4134 4119 <p><h4>2.15.7 <a name="upinter">Interval - mandatory if 'Upload Table' entries specified</h4></p> 4135 <p><h4>2.15.7 <a name="pidsidiod">PID, SID, IOD - optional</h4></p> 4136 <p> 4137 When applying Broadcast Ephemeris corrections in a PPP algorithm or in a combination of several correction streams, it is important for the client software to receive information on the continuity of discontinuity of the stream contents. Here you can specify three ID's to describe the contents of your Broadcast Ephemeris correction stream when it is uploaded. 4138 <ul> 4139 <li>A 'SSR Provider ID' is issued by RTCM SC-104 on request to identify a SSR service (see e.g. <u>http://software.rtcm-ntrip.org/wiki/SSRProvider</u>). This ID is globally unique. Values vary in the range of 0-65535. Values in the range of 0-255 are reserved for experimental services.</li> 4140 <li>A provider may generate several Broadcast Ephemeris correction streams with different contents. The 'SSR Solution ID' indicates different SSR services of one SSR provider. Values vary in the range of 0-15.</li> 4141 <li>A change of the 'IOD SSR' is used to indicate a change in the SSR generating configuration, which may be relevant for the rover. Values vary in the range of 0-15.</li> 4142 </ul> 4143 </p> 4144 4145 <p><h4>2.15.8 <a name="upinter">Interval - mandatory if 'Upload Table' entries specified</h4></p> 4120 4146 <p> 4121 4147 Select the length of Clock RINEX files and SP3 Orbit files. The default value is 1 day. 4122 4148 </p> 4123 4149 4124 <p><h4>2.15. 8<a name="upclksmpl">Sampling</h4></p>4150 <p><h4>2.15.9 <a name="upclksmpl">Sampling</h4></p> 4125 4151 <p>BNC requires an orbit corrections sampling interval for the stream to be uploaded and sampling intervals for SP3 and Clock RINEX files. The outgoing stream's clock correction sampling interval follows that of incoming corrections and is therefore nothing to be specified here.</p> 4126 4152 4127 <p><h4>2.15. 8.1 <a name="upclkorb">Orbits (Orb) - mandatory if 'Upload Table' entries specified</h4></p>4153 <p><h4>2.15.9.1 <a name="upclkorb">Orbits (Orb) - mandatory if 'Upload Table' entries specified</h4></p> 4128 4154 <p>Select the stream's orbit correction sampling interval in seconds. A value of 60 sec may be appropriate.</p> 4129 4155 <p> A value of zero '0' tells BNC to upload all orbit correction samples coming in from the real-time GNSS engine along with the clock correction samples to produce combined orbit and clock corrections to Broadcast Ephemeris (1060 for GPS, 1066 for GLONASS). … … 4156 4182 <br> 4157 4183 Note that only when specifying a value of zero '0' (default) for 'Sampling Orb', BNC produces <u>combined</u> orbit and clock correction messages. 4158 <p><h4>2.15. 8.2 <a name="upclksp3">SP3 - mandatory if 'SP3 File' is specified</h4></p>4184 <p><h4>2.15.9.2 <a name="upclksp3">SP3 - mandatory if 'SP3 File' is specified</h4></p> 4159 4185 <p>Select the SP3 orbit file sampling interval in minutes. A value of 15 min may be appropriate. A value of zero '0' tells BNC to store all available samples into SP3 orbit files.</p> 4160 4186 4161 <p><h4>2.15. 8.3 <a name="upclkrnx">RINEX (RNX) - mandatory if 'RNX File' is specified</h4></p>4187 <p><h4>2.15.9.3 <a name="upclkrnx">RINEX (RNX) - mandatory if 'RNX File' is specified</h4></p> 4162 4188 <p>Select the Clock RINEX file sampling interval in seconds. A value of 10 sec may be appropriate. A value of zero '0' tells BNC to store all available samples into Clock RINEX files.</p> 4163 4189 4164 <p><h4>2.15. 9<a name="upcustom">Custom Trafo - optional if 'Upload Table' entries specified</h4></p>4190 <p><h4>2.15.10 <a name="upcustom">Custom Trafo - optional if 'Upload Table' entries specified</h4></p> 4165 4191 <p>Hit 'Custom Trafo' to specify your own 14 parameter Helmert Transformation instead of selecting a predefined transformation through 'System' button.</p> 4166 4192 4167 <p> 4168 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 and the Issue of Data SSR are set to 1. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'. 4193 <p><h4>2.15.11 <a name="upantex">ANTEX File - mandatory if 'SP3 File' is specified</h4></p> 4194 <p> 4195 IGS provides a file containing absolute phase center variations for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required here for referring the SP3 file content to the satellite's Center of Mass (CoM). If you do not specify an ANTEX file, the SP3 file will contain orbit information which is referred to Antenna Phase Center (APC) instead of CoM. 4196 </p> 4197 <p> 4198 The following screenshot shows the encoding and uploading of a stream of precise orbits and clocks coming from a real-time network 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 and the Issue of Data SSR are set to 1. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'. 4169 4199 </p> 4170 4200 <p><img src="IMG/screenshot26.png"/></p> 4171 <p><u>Figure 32:</u> BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster</p> 4172 4173 <p><h4>2.15.10 <a name="upantex">ANTEX File - mandatory if 'SP3 File' is specified</h4></p> 4174 <p> 4175 IGS provides a file containing absolute phase center variations for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required here for referring the SP3 file content to the satellite's Center of Mass (CoM). If you do not specify an ANTEX file, the SP3 file will contain orbit information which is referred to Antenna Phase Center (APC) instead of CoM. 4176 </p> 4201 <p><u>Figure 31:</u> BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster</p> 4202 <p> 4203 The following screenshot shows the encoding and uploading of several Broadcast Ephemeris correction streams combined from streams CLK11, CLK21, CLK80, and CLK91. Combined streams are uploaded to different Ntrip Broadcasters and referred to different reference systems. One of the uploaded streams is locally saved in SP3 and Clock RINEX format. Different SSR Provider IDs, SSR Solution IDs and Issue of Data IDs are specified. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'. 4204 </p> 4205 <p><img src="IMG/screenshot21.png"/></p> 4206 <p><u>Figure 32:</u> BNC uploading a combined Broadcast Correction stream</p> 4207 <p></p> 4177 4208 4178 4209 <p><h4>2.16 <a name="upeph">Upload Ephemeris</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.
