Changeset 4507 in ntrip for trunk/BNC/src/bnchelp.html


Ignore:
Timestamp:
Aug 13, 2012, 9:44:18 AM (12 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

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

    r4499 r4507  
    104104<li>RTNET, a plain ASCII format defined within BNC to receive orbits and clock from a serving GNSS engine.
    105105</ul>
     106Note that up to now basic QZSS support follows a draft for RTCM MSM messages agreed by JAXA, BKG and DLR. Support of certain extra QZSS messages and support of  COMPASS so far only follows an internal agreement between BKG and DLR.
     107</p>
     108<p>
    106109Furthermore, BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files.
    107110</p>
     
    437440</p>
    438441<p>
    439 It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available or it does not contain the required information.
    440 </p>
     442It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available or it does not contain the required information. The 'Default selection of observation types specified' for a RINEX Version 3 file would be as follows:
     443</p>
     444<pre>
     445C   12 C2  L2  D2  S2  C6  L6  D6  S6  C7  L7  D7  S7       SYS / # / OBS TYPES
     446E   20 C1  L1  D1  S1  C5  L5  D5  S5  C6  L6  D6  S6  C7   SYS / # / OBS TYPES
     447       L7  D7  S7  C8  L8  D8  S8                           SYS / # / OBS TYPES
     448G   20 C1C L1C D1C S1C C1P L1P D1P S1P C2C L2C D2C S2C C2P  SYS / # / OBS TYPES
     449       L2P D2P S2P C5  D5  L5  S5                           SYS / # / OBS TYPES
     450J   16 C1  L1  D1  S1  C2  L2  D2  S2  C5  L5  D5  S5  C6   SYS / # / OBS TYPES
     451       D6  L6  S6                                           SYS / # / OBS TYPES
     452R   16 C1C L1C D1C S1C C1P L1P D1P S1P C2C L2C D2C S2C C2P  SYS / # / OBS TYPES
     453       L2P D2P S2P                                          SYS / # / OBS TYPES
     454S    8 C1  L1  D1  S1  C5  L5  D5  S5                       SYS / # / OBS TYPES
     455</pre>
    441456
    442457<p>
Note: See TracChangeset for help on using the changeset viewer.