Changeset 4976 in ntrip


Ignore:
Timestamp:
Mar 9, 2013, 6:49:15 PM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r4969 r4976  
    873873</p>
    874874<p>
    875 RTCM has developed Version 3 messages to transport satellite orbit and clock corrections in real-time. The current set of SSR messages concerns:
     875RTCM has developed Version 3 messages to transport satellite orbit and clock corrections in real-time. Note that corrections refer to satellite Antenna Phase Centers (APC). The current set of SSR messages concerns:
    876876<ul>
    877877<li>Orbit corrections to Broadcast Ephemeris</li>
     
    15621562<p><a name="pppcorrmount"><h4>3.12.1.3 Corr Mountpoint - optional</h4></p>
    15631563<p>
    1564 Specify a Broadcast Ephemeris 'Corrections Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to correct your positioning solution accordingly.
     1564Specify a Broadcast Ephemeris 'Corrections Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to correct your positioning solution accordingly. Not that the stream's corrections must refer to the satellite Antenna Phase Center (APC).
    15651565</p>
    15661566
     
    17891789<p><a name="combi"><h4>3.13. Combine Corrections</h4></p>
    17901790<p>
    1791 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. 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 has the possibility 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.
     1791BNC 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 has the possibility 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.
    17921792</p>
    17931793<p>
     
    18501850<p><a name="combimounttab"><h4>3.13.1 Combine Corrections Table - optional</h4></p>
    18511851<p>
    1852 Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Corrections 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 stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination. The stream processing can already be started with only one corrections stream configured for combination.
     1852Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Corrections 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. The stream processing can already be started with only one corrections stream configured for combination.
    18531853</p>
    18541854<p>
Note: See TracChangeset for help on using the changeset viewer.