Changeset 7778 in ntrip for trunk


Ignore:
Timestamp:
Feb 16, 2016, 10:03:14 AM (3 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

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

    r7776 r7778  
    275275<tr><td><b>Tab.&nbsp;&nbsp;</b></td><td><b>Title</b></td><td><b>Chapter</b></td></tr>
    276276<tr><td>1</td><td>Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</td><td>1.2</td></tr>
    277 <tr><td>2</td><td>Contents and format of synchronized output of observations via IP port for feeding a GNSS engine</td><td>2.9</td></tr>
     277<tr><td>2</td><td>Contents and format of synchronized output of observations feeding a GNSS engine</td><td>2.9</td></tr>
    278278</table>
    279279</p>
     
    24932493
    24942494<p><h4>2.9 <a name="syncout">Feed Engine</h4></p>
    2495 <p>
    2496 BNC can produce synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. Observations can be streamed out through an IP port and/or saved in a local file. The output is always in plain ASCII format and sorted per incoming stream.
    2497 </p>
    2498 <p>
    2499 Each epoch in the 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 ID. Observation types are specified by the 3-character observation code defined in RINEX Version 3. 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.
    2500 </p>
    2501 
    2502 <p>
    2503 The following table describes the format of BNC's synchronized output of GNSS observations via IP port which consists of 'Epoch Records' and 'Observation Records'. Each Epoch Record is followed by one or more Observation Records. The Observation Record is repeated for each satellite having been observed in the current epoch. The length of an Observation Record is given by the number of observation types for this satellite. Specifications for satellite number, code, phase, doppler and signal strenght information follow definitions presented in the RINEX Version 3.03 documentation.
    2504 </p>
    2505 
    2506 <p><u>Table 2:</u> Contents and format of synchronized output of observations via IP port for feeding a GNSS engine</p>
     2495
     2496<p>
     2497BNC can produce synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. Observations can be streamed out through an IP port and/or saved in a local file. The output is always in the same plain ASCII format and sorted per incoming stream.
     2498</p>
     2499
     2500<p>
     2501Each 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.
     2502</p>
     2503
     2504<p>
     2505The following table describes the format of BNC's synchronized output of GNSS observations which consists of 'Epoch Records' and 'Observation Records'. Each Epoch Record is followed by one or more Observation Records. The Observation Record is repeated for each satellite having been observed in the current epoch. The length of an Observation Record is given by the number of observation types for this satellite.
     2506</p>
     2507
     2508<p><u>Table 2:</u> Contents and format of synchronized output of observations feeding a GNSS engine</p>
    25072509<p>
    25082510<table>
Note: See TracChangeset for help on using the changeset viewer.