Changeset 7027 in ntrip
- Timestamp:
- Jul 8, 2015, 10:05:32 PM (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7025 r7027 460 460 3.13.3.2 <a href=#pppcodeobs>Code Observations</a><br> 461 461 3.13.3.3 <a href=#pppphaseobs>Phase Observations</a><br> 462 3.13.3.4 <a href=#pppeleweight>Elevation Depend ingWeighting</a><br>462 3.13.3.4 <a href=#pppeleweight>Elevation Dependent Weighting</a><br> 463 463 3.13.3.5 <a href=#pppminobs>Minimum Number of Observations</a><br> 464 464 3.13.3.6 <a href=#pppmineleva>Minimum Elevation</a><br> … … 2539 2539 2540 2540 <p><a name="pppOptions"><h4>3.13.3 PPP (3): Processing Options</h4></p> 2541 <p>BNC allows using various Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing specific sigmas for code and phase observations as well as for referencecoordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold.2542 </p> 2543 <p> 2544 The intention of this panel is to specify general processing options to be applied to all PPP threads carried outin one BNC job.2541 <p>BNC allows using various Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing specific sigmas for code and phase observations as well as for a-priory coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold. 2542 </p> 2543 <p> 2544 The intention of this panel is to specify general processing options to be applied to all PPP threads in one BNC job. 2545 2545 </p> 2546 2546 … … 2548 2548 <p> 2549 2549 <p> 2550 S elect on which kind of ionosphere-free Linear Combinations (LCs) of observations you want to base ambiguity resolutions. This implicitly defines the kind of GNSS observations you want to use. The selectionsis to be done per GNSS system ('GPS LCs', 'GLONASS LCs', 'Galileo LCs', 'BDS LCs').2550 Specify on which ionosphere-free Linear Combinations (LCs) of observations you want to base ambiguity resolutions. This implicitly defines the kind of GNSS observations you want to use. The specification is to be done per GNSS system ('GPS LCs', 'GLONASS LCs', 'Galileo LCs', 'BDS LCs'). 2551 2551 </p> 2552 2552 <p> … … 2565 2565 <p><a name="pppcodeobs"><h4>3.13.3.2 Code Observations - mandatory</h4></p> 2566 2566 </p> 2567 Enter a 'Sigma C1' for C1 code observations in meters. The higher the sigma you enter, the less the contribution of C1 code observations to a PPP solution based on a combination of code and phase data. 2.0is likely to be an appropriate choice.2567 Enter a 'Sigma C1' for C1 code observations in meters. The bigger the sigma you enter, the less the contribution of C1 code observations to a PPP solution based on a combination of code and phase data. '2.0' meters is likely to be an appropriate choice. 2568 2568 </p> 2569 2569 <p> … … 2574 2574 <p><a name="pppphaseobs"><h4>3.13.3.3 Phase Observations - mandatory</h4></p> 2575 2575 <p> 2576 Enter a 'Sigma L1' for L1 phase observations in meters. The higher the sigma you enter, the less the contribution of L1 phase observations to a PPP solutions based on a combination of code and phase data. 0.01is likely to be an appropriate choice.2576 Enter a 'Sigma L1' for L1 phase observations in meters. The bigger the sigma you enter, the less the contribution of L1 phase observations to a PPP solutions based on a combination of code and phase data. '0.01' meters is likely to be an appropriate choice. 2577 2577 </p> 2578 2578 <p> … … 2583 2583 As the convergence characteristic of a PPP solution can be influenced by the ratio of sigmas for code and phase, you may like to introduce sigmas which differ from the default values. 2584 2584 <ul> 2585 <li>Introducing a smaller sigma (higher accuracy) for code observations or a larger sigma for phase observations leads to better results shortly after program start. However, it may take more time till you finally get the best possible solution.</li> 2586 <li>Introducing a larger sigma (lower accuracy) for code observations or a smaller sigma for phase observations may lead to less accurate results shortly after program start and thus a prolonged period of convergence but could provide better positions in the long run.</li> 2587 </ul> 2588 </p> 2589 2590 <p><a name="pppeleweight"><h4>3.13.3.4 Elevation Depending Weighting - mandatory</h4></p> 2585 <li>Introducing a smaller sigma (higher accuracy) for code observations or a bigger sigma for phase observations leads to better results shortly after program start. However, it may take more time till you finally get the best possible solution.</li> 2586 <li>Introducing a bigger sigma (lower accuracy) for code observations or a smaller sigma for phase observations may lead to less accurate results shortly after program start and thus a prolonged period of convergence but could provide better positions in the long run.</li> 2587 </ul> 2588 </p> 2589 2590 <p><a name="pppeleweight"><h4>3.13.3.4 Elevation Dependent Weighting - mandatory</h4></p> 2591 <p> 2592 BNC allows elevation dependent weighting when processing GNSS observations. A weight function 2593 </p> 2594 2595 <p> P = cos² * z</p> 2596 2597 <p> 2598 with 'z' being the zenith distance to the involved satellites can be applied instead of the simple weight function 'P = 1'. 2599 </p> 2600 <ul> 2601 <li>Tick 'Ele Wgt Code' if you want Elevation Dependant Weighting for code observations.</li> 2602 <li>Tick 'Ele Wgt Phase' if you want Elevation Dependant Weighting for phase observations.</li> 2603 </ul> 2604 <p> 2605 Default is using the plain weight function 'P = 1' for code and phase observations. 2606 </p> 2591 2607 2592 2608 <p><a name="pppminobs"><h4>3.13.3.5 Minimum Number of Observations - mandatory</h4></p> … … 2596 2612 <p><a name="pppwaitclockcorr"><h4>3.13.3.7 Wait for Clock Corrections - optional</h4></p> 2597 2613 <p> 2598 Zero value (or 'no') for 'Wait for clock corr.' means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value means that epochs of data are buffered and the processing of each epoch is postponed till satellite clock corrections not older than 'Wait for clock corr ' are available. Specifying a value of half the update rate of the clock corrections (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.2599 </p> 2600 <p> 2601 Using observations in sync with the corrections can avoid a possible high frequency noise of PPP solutions. Such noise could result from processing observations regardless of how late after a clock correction they were received. Note that applying the ' Sync Corr' option significantly reduces the PPP computation effort for BNC.2614 Zero value (or 'no') for 'Wait for clock corr.' means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value means that epochs of data are buffered and the processing of each epoch is postponed till satellite clock corrections not older than 'Wait for clock corr.' are available. Specifying a value of half the update rate of the clock corrections (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. 2615 </p> 2616 <p> 2617 Using observations in sync with the corrections can avoid a possible high frequency noise of PPP solutions. Such noise could result from processing observations regardless of how late after a clock correction they were received. Note that applying the 'Wait for clock corr.' option significantly reduces the PPP computation effort for BNC. 2602 2618 </p> 2603 2619 <p> … … 2610 2626 </p> 2611 2627 <p> 2612 This so-called Quick-Start option allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the know position throughout the defined period. A value of 60is likely to be an appropriate choice for 'Seeding'. Default is an empty option field, meaning that you don't want BNC to start in Quick-Start mode.2628 This so-called Quick-Start 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 don't want BNC to start in Quick-Start mode. 2613 2629 <p> 2614 2630 You may need to create your own reference coordinate beforehand through running BNC for an hour in normal mode before applying the 'Seeding' option. Don't forget to introduce realistic North/East/Up sigmas under panel 'PPP (2)' according to the coordinate's precision. … … 2641 2657 <p><a name="ppptimeseries"><h4>3.13.4.1 PPP Plot - optional</h4></p> 2642 2658 <p> 2643 PPP time series of North (red), East (green) and Up (blue) displacements will be plotted under the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified, see 'Coordinates') or referred to the first estimated position n. The sliding PPP time series window will cover the period of the latest 5 minutes.2659 PPP time series of North (red), East (green) and Up (blue) displacements will be plotted under the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified, see 'Coordinates') or referred to the first estimated position. The sliding PPP time series window will cover the period of the latest 5 minutes. 2644 2660 </p> 2645 2661 <p> … … 2649 2665 <p><a name="pppaudioresp"><h4>3.13.4.2 Audio Response - optional</h4></p> 2650 2666 <p> 2651 For natural hazard prediction and monitoring it may be appropriate to generate audio alerts. For that you can specify an 'Audio response' threshold in meters. A beep is produced by BNC whenever a horizontal PPP coordinate component differs by more than the threshold value from the specified marker coordinate.2667 For natural hazard prediction and monitoring landslides it may be appropriate to generate audio alerts. For that you can specify an 'Audio response' threshold in meters. A beep is produced by BNC whenever a horizontal PPP coordinate component differs by more than the threshold value from the specified marker coordinate. 2652 2668 </p> 2653 2669 <p> … … 2661 2677 <p><a name="ppptrackmap"><h4>3.13.4.3 Track Map - optional</h4></p> 2662 2678 <p> 2663 You ma ke like to track your rover position using Google Maps or Open StreetMap asbackground map. Track maps can be produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files.2679 You may like to track your rover position using Google Maps or Open StreetMap as a background map. Track maps can be produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files. 2664 2680 </p> 2665 2681 <p> … … 2667 2683 </p> 2668 2684 <p> 2669 The 'Open Map' button opens a windows showing a map according to the s pecified 'Google/OSM' option.2685 The 'Open Map' button opens a windows showing a map according to the selected 'Google/OSM' option. 2670 2686 </p> 2671 2687 … … 2677 2693 <p><a name="pppdotprop"><h4>3.13.4.4 Dot-properties - mandatory before pushing 'Open Map'</h4></p> 2678 2694 <p> 2679 PPP tracks are presented on maps through plotting one colored dot per epoch.2695 PPP tracks are presented on maps through plotting one colored dot per observation epoch. 2680 2696 </p> 2681 2697
Note:
See TracChangeset
for help on using the changeset viewer.