Changeset 8468 in ntrip for trunk/BNC


Ignore:
Timestamp:
Sep 4, 2018, 9:08:47 AM (6 years ago)
Author:
stuerze
Message:

minor changes

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r8466 r8468  
    20742074<p>
    20752075<ul>
    2076   <li>The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting <b>RINEX Version 3 to Version 2</b> Observation files, BNC is forced to somehow map signals with attributes to signals without attributes although this cannot be done in one-to-one correspondence. Hence we introduce a 'Version 2 Signal Priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2, see details in section 'RINEX Observations/Version 2'. Signal priorities can be specified as equal for all systems, as system specific or as system and frequency specific. For example:</li>
    2077   <ul>
    2078     <li>'CWPX_?' (General signal priorities valid for all GNSS)</li>
    2079     <li>'C:IQX I:ABCX' (System specific signal priorities for BDS and IRNSS)</li>
    2080     <li>'G:12&PWCSLXYN G:5&IQX R:12&PC R:3&IQX' (System and frequency specific signal priorities)</li>
    2081   </ul>
    2082   </p>
    2083   <p>
    2084   The default 'Signal priority' list is defined as follows:
    2085   <ul>
    2086     <li>'G:12&PWCSLXYN_ G:5&IQX_ R:12&PC_ R:3&IQX_ E:16&BCX_ E:578&IQX_ J:1&SLXCZ_ J:26&SLX_ J:5&IQX_ C:IQX_ I:ABCX_ S:1&C_ S:5&IQX_'</li>
    2087   </ul>
    2088   </p>
    2089   <p>
     2076  <li>The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting <b>RINEX Version 3 to Version 2</b> Observation files, BNC is forced to somehow map signals with attributes to signals without attributes although this cannot be done in one-to-one correspondence. Hence we introduce a 'Version 2 Signal Priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2, see details in section 'RINEX Observations/Version 2'.
    20902077  <li>When converting <b>RINEX Version 2 to Version 3</b> Observation files, the tracking mode or channel information in the (last character out of the 3-character) observation code is left blank if unknown. This is a compromise, knowing that it is not in accordance with the RINEX Version 3 documentation.</li>
    20912078</ul>
Note: See TracChangeset for help on using the changeset viewer.