Changeset 4201 in ntrip
- Timestamp:
- May 22, 2012, 8:46:45 AM (12 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (20 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r4197 r4201 3 3 4 4 <p> 5 The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing real-time GNSS data streams from NTRIP Broadcasters like5 The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing real-time GNSS data streams. It has been developed within the framework of the IAG subcommission 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 6 6 </p> 7 7 <p> … … 11 11 <u>http://mgex.igs-ip.net/home</u>. 12 12 </p> 13 <p> 14 Although actually meant as a real-time tool, it comes with some limited Post Processing functionality. 15 </p> 16 17 <p> 18 BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of the IAG subcommission for Europe (EUREF) and the International GNSS Service (IGS). 19 </p> 20 21 <p> 22 BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive <u>http://software.rtcm-ntrip.org/svn/trunk/BNC.</u> Binaries for BNC are available for Windows, 32-bit Linux, 64-bit Linux (compiled under -m32 32-bit compatibility mode), Solaris, and Mac systems. We used the MinGW Version 4.4.0 compiler to create the Windows binary. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.7.3 are installed. 23 </p> 24 25 <p> 26 Please ensure that you have installed the latest version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u>. Feel free to send us comments, suggestions, or bug reports to [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]. 13 14 <p> 15 BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive <u>http://software.rtcm-ntrip.org/svn/trunk/BNC.</u> Binaries for BNC are available for Windows, 32-bit Linux, 64-bit Linux (compiled under -m32 32-bit compatibility mode), Solaris, and Mac systems. We used the MinGW Version 4.4.0 compiler to create the Windows binary. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.7.3 are installed. Please ensure that you have installed the latest version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u> and feel free to send us your comments, suggestions or bug reports. 27 16 </p> 28 17 … … 37 26 <p> 38 27 <b><a name="authors">Authors</b><br> 39 The BKG Ntrip Client (BNC) Qt Graphic User Interface (GUI) has been developed for the Federal Agency for Cartography and Geodesy (BKG) by 40 </p> 41 <p> 28 The BKG Ntrip Client (BNC) and its Qt Graphic User Interface (GUI) has been developed for 29 </p> 30 <p> 31 Federal Agency for Cartography and Geodesy (BKG)<br> 32 Georg Weber<br> 33 Department of Geodesy<br> 34 Frankfurt, Germany<br> 35 [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de] 36 </p> 37 38 <p> 39 by 40 </p> 41 42 <p> 43 Czech Technical University (CTU)<br> 42 44 Leos Mervart<br> 43 Czech Technical University (CTU)<br>44 45 Department of Geodesy<br> 45 46 Prague, Czech Republic … … 52 53 </ul> 53 54 </p> 54 <p>55 Georg Weber<br>56 Federal Agency for Cartography and Geodesy (BKG)<br>57 Department of Geodesy<br>58 Frankfurt, Germany<br>59 [euref-ip@bkg.bund.de] or<br>60 [igs-ip@bkg.bund.de]61 55 </p> 62 56 … … 1370 1364 1371 1365 <p> 1372 Note that BNC's 'PPP' option can also be used offline either for for debugging or for Post Processing purposes.1366 Note that for debugging or Post Processing purposes BNC's 'PPP' functionality option can also be used offline. 1373 1367 <ul> 1374 1368 <li> … … 1386 1380 <ul> 1387 1381 <li>BNC does correct for Solid Earth Tides and Phase Windup.</li> 1388 <li>Satellite Antenna Phase Center Offsets are not corrected because applied orbit/clock corrections are referred to the satellite's antenna phase center.</li>1389 <li>Satellite Antenna Phase Center Variations are neglected because this is a small effect usually less than 2 centimeters.</li>1382 <li>Satellite antenna phase center offsets are not corrected because applied orbit/clock corrections are referred to the satellite's antenna phase center.</li> 1383 <li>Satellite antenna phase center variations are neglected because this is a small effect usually less than 2 centimeters.</li> 1390 1384 <li>Observations can be corrected for a Receiver Antenna Offset. Depending on whether or not this correction is applied, the estimated position is either that of the receiver's antenna phase center or that of the receiver's Antenna Reference Point.</li> 1391 <li>Receiver Antenna Phase Center Variations are not included in the model. The bias caused by this neglect depends on the receiver antenna type. For most antennas it is smaller than a few centimeters.</li>1385 <li>Receiver antenna phase center variations are not included in the model. The bias caused by this neglect depends on the receiver antenna type. For most antennas it is smaller than a few centimeters.</li> 1392 1386 <li>Ocean and atmospheric loading is neglected. Atmospheric loading is pretty small. Ocean loading is usually also a small effect but may reach up to about 10 centimeters for coastal stations.</li> 1393 1387 <li>Rotational deformation due to polar motion (Polar Tides) is not corrected because this is a small effect usually less than 2 centimeters.</li> … … 1397 1391 <p><a name="pppmode"><h4>3.12.1 Mode & Mountpoints - optional</h4></p> 1398 1392 <p> 1399 Specify the Point Positioning mode you want to apply and the mountpoints for observations and Broadcast Corrections. Options are 'Realtime-PPP', 'Realtime-SPP', and 'Post-Processing'.1393 Specify the Point Positioning mode you want to apply and the mountpoints for observations and Broadcast Corrections. 1400 1394 </p> 1401 1395 1402 1396 <p><a name="pppmodus"><h4>3.12.1.1 Mode - optional</h4></p> 1403 <p>Choose between plain Single Point Positioning (SPP) and Precise Point Positioning (PPP) in 'Realtime' or 'Post-Processing' mode.</p> 1397 <p> 1398 Choose between plain Single Point Positioning (SPP) and Precise Point Positioning (PPP) in 'Realtime' or 'Post-Processing' mode. Options are 'Realtime-PPP', 'Realtime-SPP', and 'Post-Processing'. 1399 </p> 1404 1400 1405 1401 <p><a name="pppobsmount"><h4>3.12.1.2 Obs Mountpoint - optional</h4></p> … … 1415 1411 <p><a name="pppxyz"><h4>3.12.2 Marker Coordinates - optional</h4></p> 1416 1412 <p> 1417 Enter the reference coordinate components X,Y,Z of the receiver's position in meters if known. This option makes only sense for static observations. Default are empty option fields, meaning that the antenna's XYZ position is unknown.1413 Enter the reference coordinate XYZ of the receiver's position in meters if known. This option makes only sense for static observations. Default are empty option fields, meaning that the antenna's XYZ position is unknown. 1418 1414 </p> 1419 1415 <p> … … 1429 1425 <p><a name="pppneu"><h4>3.12.3 Antenna Excentricity - optional</h4></p> 1430 1426 <p> 1431 You may like to specify North, East and Up components of an antenna eccentricity which is the difference between a nearby marker position and the antenna phase center. If you do so BNC will produce coordinates referring to the marker position and not referring to the antenna phase center. .1427 You may like to specify North, East and Up components of an antenna eccentricity which is the difference between a nearby marker position and the antenna phase center. If you do so BNC will produce coordinates referring to the marker position and not referring to the antenna phase center. 1432 1428 </p> 1433 1429 1434 1430 <p><a name="pppoutput"><h4>3.12.4 NMEA & Plot Output - optional</h4></p> 1435 1431 <p> 1436 BNC allows to output results from Precise Point Positioning in NMEA format. It can also plot a time series of North, East and UP displacements of coordinate components.1432 BNC allows to output results from Precise Point Positioning in NMEA format. It can also plot a time series of North, East and UP displacements. 1437 1433 </p> 1438 1434 … … 1449 1445 </p> 1450 1446 <p> 1451 Note that Tomoji Takasu has written a program called RTKPlot for visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA output of BNC's 'PPP Client'option.1447 Note that Tomoji Takasu has written a program called RTKPlot for visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA file and port output of BNC's 'PPP' client option. 1452 1448 </p> 1453 1449 … … 1457 1453 </p> 1458 1454 <p> 1459 NASA's 'World Wind' software (see <u>http://worldwindcentral.com/wiki/NASA_World_Wind_Download</u>) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from <u>http://worldwindcentral.com/wiki/GPS_Tracker</u> for that. The 'Word Wind' is not meant for showing centimeter level details.1455 NASA's 'World Wind' software (see <u>http://worldwindcentral.com/wiki/NASA_World_Wind_Download</u>) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from <u>http://worldwindcentral.com/wiki/GPS_Tracker</u> for that. The 'Word Wind' map resolution is not meant for showing centimeter level details. 1460 1456 </p> 1461 1457 … … 1469 1465 1470 1466 <p><a name="ppppost"><h4>3.12.5 Post Processing - optional</h4></p> 1471 <p>When in 'Post-Processing mode<ul><li>specifying a RINEX Observation, a RINEX Navigation and a Broadcast Corrections file leads to a PPP solution.</li><li>specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Corrections file leads to a SPP solution.</ul></p> 1472 <p>BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats. Files carrying Broadcast Corrections must have the format produced by BNC in the 'Broadcast Corrections' tab. 1467 <p>When in 'Post-Processing' mode 1468 <ul> 1469 <li>specifying a RINEX Observation, a RINEX Navigation and a Broadcast Corrections file leads to a PPP solution.</li> 1470 <li>specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Corrections file leads to a SPP solution.</li> 1471 </ul> 1472 </p> 1473 <p>BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats. Files carrying Broadcast Corrections must have the format produced by BNC through the 'Broadcast Corrections' tab. 1473 1474 <p> 1474 1475 Post Processing PPP results can be saved in a specific output file. … … 1529 1530 </p> 1530 1531 <p> 1531 By default BNC does not estimate troposphere parameters. Tick 'Estimate tropo' to estimate troposphere parameters together with the coordinates and save T_apr and dT in BNC's log file.1532 By default BNC does not estimate troposphere parameters. Tick 'Estimate tropo' to estimate troposphere parameters together with the coordinates and save T_apr and dT/cos(z) in BNC's log file. 1532 1533 </p> 1533 1534 … … 1544 1545 <p><a name="pppsync"><h4>3.12.7.5 Sync Corr - optional</h4></p> 1545 1546 <p> 1546 Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'Sync Corr' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'Sync Corr' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of the update rate.1547 Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'Sync Corr' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'Sync Corr' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of half of the update rate. 1547 1548 </p> 1548 1549 <p> … … 1555 1556 <p><a name="pppaverage"><h4>3.12.7.6 Averaging - optional if XYZ is set</h4></p> 1556 1557 <p> 1557 Enter the length of a sliding time window in minutes. BNC will continuously output moving average values nsand their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenit path delays are bias reduced while RMS values for Nort/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's log file and 'Log' section while averaged values for NEU displacements and their RMS are marked with string "AVE-NEU" and averaged values for the tropospheric delays and their RMS are marked with string "AVE-TRP". Example:1558 Enter the length of a sliding time window in minutes. BNC will continuously output moving average values and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenit path delays are bias reduced while RMS values for Nort/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's log file and 'Log' section while averaged values for NEU displacements and their RMS are marked with string "AVE-NEU" and averaged values for the tropospheric delays and their RMS are marked with string "AVE-TRP". Example: 1558 1559 </p> 1559 1560 <pre> … … 1760 1761 Then, epoch by epoch: 1761 1762 <ul> 1762 <li>Continuously receive the best available clock and orbit estimates for all satellites in X ,Y,Z Earth-Centered-Earth-Fixed IGS08 reference system. Receive them every epoch in plain ASCII format as provided by a real-time GNSS engine such as RTNet or generate them following a combination approach. </li>1763 <li>Calculate X ,Y,Z coordinates from Broadcast Ephemeris orbits. </li>1763 <li>Continuously receive the best available clock and orbit estimates for all satellites in XYZ Earth-Centered-Earth-Fixed IGS08 reference system. Receive them every epoch in plain ASCII format as provided by a real-time GNSS engine such as RTNet or generate them following a combination approach. </li> 1764 <li>Calculate XYZ coordinates from Broadcast Ephemeris orbits. </li> 1764 1765 <li>Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS08 orbits. </li> 1765 1766 <li>Transform these differences into radial, along-track and cross-track corrections to Broadcast Ephemeris orbits. </li> … … 1788 1789 <ul> 1789 1790 <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li> 1790 <li>X ,Y,Z coordinates in Earth-Centered-Earth-Fixed system [km] at epoch T</li>1791 <li>XYZ coordinates in Earth-Centered-Earth-Fixed system [km] at epoch T</li> 1791 1792 <li>Satellite clock error [microsecond]</li> 1792 1793 <li>Conventional periodic relativistic effect [microsecond]</li> … … 1795 1796 <li>Differential Code Bias P1P2 [m]</li> 1796 1797 <li>Time increment dT [second]</li> 1797 <li>X ,Y,Z coordinates in Earth-Centered-Earth-Fixed system [km] at epoch T+dT</li>1798 <li>XYZ coordinates in Earth-Centered-Earth-Fixed system [km] at epoch T+dT</li> 1798 1799 </ul> 1799 1800 </p> … … 2007 2008 </p> 2008 2009 <p> 2009 As an SP3 file contents should be referred to the satellites Center of Mass (CoM) while Broadcast Corrections are referred to the satellites A ntenna Phase Center (APC), an offset has to be applied which is available from an IGS ANTEX file (see section 'ANTEX File'). You should therefore specify the 'ANTEX File' path under tab 'PPP (2)' if you want to save the stream contents in SP3 format. If you don't specify an 'ANTEX File' path there, the SP3 file contents will be referred to the satellites APCs.2010 As an SP3 file contents should be referred to the satellites Center of Mass (CoM) while Broadcast Corrections are referred to the satellites APC, an offset has to be applied which is available from an IGS ANTEX file (see section 'ANTEX File'). You should therefore specify the 'ANTEX File' path under tab 'PPP (2)' if you want to save the stream contents in SP3 format. If you don't specify an 'ANTEX File' path there, the SP3 file contents will be referred to the satellites APCs. 2010 2011 </p> 2011 2012 <p> … … 2730 2731 </p> 2731 2732 <p> 2732 Some BNC options require Antenna Phase Center variations as made available from IGS through so-called ANTEX files in directory <u>ftp://igs.org/pub/station/general</u>. An example ANTEX file is also part of the BNC package for convenience.2733 Some BNC options require antenna phase center variations as made available from IGS through so-called ANTEX files in directory <u>ftp://igs.org/pub/station/general</u>. An example ANTEX file is also part of the BNC package for convenience. 2733 2734 </p> 2734 2735 <p>
Note:
See TracChangeset
for help on using the changeset viewer.
