Changeset 7020 in ntrip for trunk/BNC/src/bnchelp.html
- Timestamp:
- Jul 7, 2015, 8:20:23 PM (10 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7019 r7020 450 450 3.13.1.10.1 <a href=#pppsnxtrosampl>Sampling</a><br> 451 451 3.13.2 <a href=#pppStation>PPP (2): Processed Stations</a><br> 452 3.13.2.1 <a href=#pppnehsigma>Sigma North/East/Height</a><br> 453 3.13.2.2 <a href=#pppnehnoise>Noise North/East/Height</a><br> 454 3.13.2.3 <a href=#ppptropsigma>Tropo Sigma</a><br> 455 3.13.2.4 <a href=#ppptropnoise>Tropo Noise</a><br> 456 3.13.2.5 <a href=#pppnmeaport>NMEA Port</a><br> 452 3.13.2.1 <a href=#pppstation>Station</a><br> 453 3.13.2.2 <a href=#pppnehsigma>Sigma North/East/Up</a><br> 454 3.13.2.3 <a href=#pppnehnoise>Noise North/East/Up</a><br> 455 3.13.2.4 <a href=#ppptropsigma>Tropo Sigma</a><br> 456 3.13.2.5 <a href=#ppptropnoise>Tropo Noise</a><br> 457 3.13.2.6 <a href=#pppnmeaport>NMEA Port</a><br> 457 458 3.13.3 <a href=#pppOptions>PPP (3): Processing Options</a><br> 458 459 3.13.3.1 <a href=#ppplinecombi>Linear Combinations</a><br> … … 1243 1244 <p><a name="sp3comp"><h4>3.7. SP3 Comparison</h4></p> 1244 1245 <p> 1245 BNC allows to compare the contents of two files containing 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 X ,Y,Z 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.1246 BNC allows to compare the contents of two files containing 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. 1246 1247 </p> 1247 1248 <p> … … 2177 2178 </ul> 2178 2179 Having this parameter first in each record is mandatory. BNC can carry out PPP solutions only for streams or files specified here.</li><br> 2179 <li>Only for static observations from a stationary receiver:<br>Approximate a-priori X ,Y,Z coordinate [m] of the station's marker; specify '0.0 0.0 0.0' if unknown or when observations come from a mobile receiver.</li><br>2180 <li>Only for static observations from a stationary receiver:<br>Approximate a-priori XYZ coordinate [m] of the station's marker; specify '0.0 0.0 0.0' if unknown or when observations come from a mobile receiver.</li><br> 2180 2181 <li>Nort, East and Up component [m] of antenna excentricity which is the difference between Antenna Reference Point (ARP) and a nearby marker position; when specifying the antenna excentricity BNC will produce coordinates referring to the marker position and not referring to ARP; specify '0.0 0.0 0.0' if excentricity is unknown or the ARP itself is understood as the marker.</li><br> 2181 2182 <li>Receiver's antenna name as defined in your ANTEX file (see below); Observations will be corrected for the Antenna Phase Center (APC) offsets and variations which may result in a reduction of a few centimeters at max; the specified name must consist of 20 characters; add trailing blanks if the antenna name has less than 20 characters; examples:<br><pre> … … 2275 2276 </p> 2276 2277 <p> 2277 Each row reports the PPP result of one epoch. It begins with a UTC time stamp (yy-mm-dd hh:mm:ss) which tells us when the result was produced. A second time stamp (yyyy-mm-dd_hh:mm:ss) describes the PPP's epoch in 'GPS Time'. It is followed by the derived X ,Y,Z position in [m], its North, East and Up displacement compared to an introduced a-priory coordinate and the estimated tropospheric delay [m] (model plus correction).2278 Each row reports the PPP result of one epoch. It begins with a UTC time stamp (yy-mm-dd hh:mm:ss) which tells us when the result was produced. A second time stamp (yyyy-mm-dd_hh:mm:ss) describes the PPP's epoch in 'GPS Time'. It is followed by the derived XYZ position in [m], its North, East and Up displacement compared to an introduced a-priory coordinate and the estimated tropospheric delay [m] (model plus correction). 2278 2279 </p> 2279 2280 <p> … … 2339 2340 <li>OGG: Time offset between GPS time and Galileo time in [m], 2340 2341 <li>TRP: A-priori and correction values of tropospheric zenith delay in [m], 2341 <li>MOUNTPOINT: Here 'CUT07' with X ,Y,Z position in [m] and dN/dE/dU in [m] for North, East, and Up displacements comparted to a-priory marker coordinates.</li>2342 <li>MOUNTPOINT: Here 'CUT07' with XYZ position in [m] and dN/dE/dU in [m] for North, East, and Up displacements comparted to a-priory marker coordinates.</li> 2342 2343 </ul> 2343 2344 Estimated parameters are presented together with their formal errors as derived from the implemented filter. The PPP algorithm includes outlier and cycle slip detection. … … 2413 2414 /Users/pppDir/PPP_${STATION}${DOY}_${YY}.zpd 2414 2415 </pre> 2415 In this '${STATION}' stands for the observation's mountpoint or RINEX file, '${DOY}' for the Day Of Year, and '${YY} for the year. For a RINEX observations file 'CUT0' it would lead to a logfile named 'PPP_CUT01810.15.zpdwith the following contents (example):2416 In this '${STATION}' stands for the observation's mountpoint or RINEX file, '${DOY}' for the Day Of Year, and '${YY}' for the year. For a RINEX observations file 'CUT0' it would lead to a troposphere file named 'PPP_CUT01810.15.zpd' with the following contents (example): 2416 2417 </p> 2417 2418 … … 2479 2480 </p> 2480 2481 2481 <p><a name="pppsnxtrosampl"><h4>3.13.1.10.1 Sampling - optionalif 'SINEX TRO File' is set</h4></p>2482 <p> 2483 Select a 'Sampling' rate for saving troposphere parameters.2484 </p> 2485 <p> 2486 Default 'Sampling' rate is '0', meaning that a ny estimated troposphere parameterwill be save on disk.2482 <p><a name="pppsnxtrosampl"><h4>3.13.1.10.1 Sampling - mandatory if 'SINEX TRO File' is set</h4></p> 2483 <p> 2484 Select a 'Sampling' rate in seconds for saving troposphere parameters. 2485 </p> 2486 <p> 2487 Default 'Sampling' rate is '0', meaning that all troposphere estimates will be save on disk. 2487 2488 </p> 2488 2489 2489 2490 <p><a name="pppStation"><h4>3.13.2 PPP (2): Processed Stations</h4></p> 2490 2491 2491 <p><a name="pppnehsigma"><h4>3.13.2.1 Sigma North/East/Height - mandatory</h4></p> 2492 <p> 2493 Enter a sigma in meters for the initial XYZ coordinate. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode. 2494 </p> 2495 2496 <p><a name="pppnehnoise"><h4>3.13.2.2 Noise North/East/Height - mandatory</h4></p> 2497 <p> 2498 Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate when considering possible sudden movements of a rover. 2499 </p> 2500 2501 <p><a name="ppptropsigma"><h4>3.13.2.3 Tropo Sigma - mandatory if 'Estimate tropo' is set</h4></p> 2492 <p> 2493 This panel allows to enter parameters specific to each PPP process. Individual sigmas for a-priori coordinates and a noise for coordinate variations over time can be introduced. Furthermore, a sigma for model based troposphere estimates and the corresponding noise for troposphere variations can be specified. Finally, local IP ports can be defined for output of NMEA streams carrying PPP results. 2494 </p> 2495 2496 <p><a name="pppstation"><h4>3.13.2.1 Station - mandatory</h4></p> 2497 2498 2499 <p><a name="pppnehsigma"><h4>3.13.2.2 Sigma North/East/Up - mandatory</h4></p> 2500 <p> 2501 Enter a sigmas in meters for the initial coordinate compoments. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known position - so-called Quick-Start mode. 2502 </p> 2503 2504 <p><a name="pppnehnoise"><h4>3.13.2.3 Noise North/East/Up - mandatory</h4></p> 2505 <p> 2506 Enter a sigma in meters for the 'White Noise' of estimated coordinate components. A value of 100.0 (default) may be appropriate when considering possible sudden movements of a rover. 2507 </p> 2508 2509 <p><a name="ppptropsigma"><h4>3.13.2.4 Tropo Sigma - mandatory</h4></p> 2502 2510 <p> 2503 2511 Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice. 2504 2512 </p> 2505 2513 2506 <p><a name="ppptropnoise"><h4>3.13.2. 4 Tropo Noise - mandatory if 'Estimate tropo' is set</h4></p>2514 <p><a name="ppptropnoise"><h4>3.13.2.5 Tropo Noise - mandatory</h4></p> 2507 2515 <p> 2508 2516 Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour. 2509 2517 </p> 2510 2518 2511 <p><a name="pppnmeaport"><h4>3.13.2. 5NMEA Port - optional</h4></p>2519 <p><a name="pppnmeaport"><h4>3.13.2.6 NMEA Port - optional</h4></p> 2512 2520 Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same. 2513 2521 </p>
Note:
See TracChangeset
for help on using the changeset viewer.
