Changeset 7834 in ntrip for trunk


Ignore:
Timestamp:
Mar 14, 2016, 2:17:40 PM (3 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

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

    r7830 r7834  
    25232523
    25242524<p>
    2525 Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the GPS Week. Following lines begin with the mountpoint string of the stream which provides the observations followed by a satellite number. Specifications for satellite number, code, phase, doppler and signal strength data follow definitions presented in the RINEX Version 3 documentation. In case of phase observations a Slip Count is added which is put to '-1' if it is not set. The end of an epoch is indicated by an empty line.
     2525Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the GPS Week. Following lines begin with the mountpoint string of the stream which provides the observations followed by a satellite number. Specifications for satellite number, code, phase, Doppler and signal strength data follow definitions presented in the RINEX Version 3 documentation. In case of phase observations, a 'Lock Time Indicator' is added. The end of an epoch is indicated by an empty line.
     2526</p>
     2527
     2528<p>
     2529A valid 'Lock Time Indicator' is only presented for observations from RTCM Version 3 streams. The parameter provides a measure of the amount of time that has elapsed during which the receiver has maintained continuous lock on that satellite signal. If a cycle slip occurs during the previous measurement cycle, the lock indicator will be reset to Zero. In case of observations from RTCM Version 2 streams, the 'Lock Time Indicator' is set to '-1'.
    25262530</p>
    25272531
     
    25562560<tr><td>Observation Code</td><td><b>L</b>1C</td><td>1X,A3</td></tr>
    25572561<tr><td>Carrier Phase Observation</td><td>133446552.870</td><td>1X,F14.3</td></tr>
    2558 <tr><td>Slip Count</td><td>127</td><td>1X,I4</td></tr>
     2562<tr><td>Lock Time Indicator</td><td>11</td><td>1X,I4</td></tr>
    25592563
    25602564<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
     
    25712575
    25722576</table>
    2573 </p>
    2574 
    2575 <p>Note on 'Slip Count':<br>
    2576 It is the current understanding of BNC's authors that different Slip Counts could be referred to different phase measurements (e.g. L1C and L1P). The 'loss-of-lock' flags in RINEX are an example for making such kind of information available per phase measurement. However, it looks like we do have only one Slip Count in RTCM Version 3 for all phase measurements. As it could be that a receiver generates different Slip Counts for different phase measurements, we output one Slip Count per phase measurement to a listening real-time GNSS network engine.
    25772577</p>
    25782578
Note: See TracChangeset for help on using the changeset viewer.