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


Ignore:
Timestamp:
Sep 5, 2016, 12:00:32 PM (8 years ago)
Author:
stuerze
Message:

information regarding RINEX version 3 to RINEX version 2 signal priorities that can be used for RINEX Editing and Concatination is updated

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r8020 r8031  
    19301930<p>
    19311931<ul>
    1932 <li>The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting <u>RINEX Version 3 to Version 2</u> 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'. The default 'Version 2 Signal Priority' list of observation attributes when mapping RINEX Version 3 to Version 2 is 'CWPX_?'. Signal priorities can be specified either as equal for all systems or system specific. The following are example priority strings:</li>
    1933 <ul>
    1934 <li>CWPX_? (Same signal priorities valid for all systems)</li>
    1935 <li>G:CWPX_? R:PCX_? E:CPX_? (Specific signal priorities for GPS, GLONASS and Galileo system)</li><br>
    1936 </ul>
     1932<li>The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting <u>RINEX Version 3 to Version 2</u> 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>
     1933<ul>
     1934<li>'CWPX_?' (General signal priorities valid for all GNSS)</li>
     1935<li>'C:IQX I:ABCX' (System specific signal priorities for BDS and IRNSS)</li>
     1936<li>'G:12&PWCSLXYN G:5&IQX R:12&PC R:3&IQX' (System and frequency specific signal priorities)</li>
     1937</ul>
     1938</p>
     1939<p>
     1940The default 'Signal priority' list is defined as follows:
     1941<ul>
     1942 <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>
     1943</ul>
     1944</p>
     1945<p>
    19371946<li>When converting <u>RINEX Version 2 to Version 3</u> 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>
    19381947</ul>
Note: See TracChangeset for help on using the changeset viewer.