Changeset 8469 in ntrip for branches/BNC_2.12


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

minor changes

File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/BNC_2.12/src/bnchelp.html

    r8465 r8469  
    19991999<p>
    20002000<ul>
    2001 <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>
    2002 <ul>
    2003 <li>'CWPX_?' (General signal priorities valid for all GNSS)</li>
    2004 <li>'C:IQX I:ABCX' (System specific signal priorities for BDS and IRNSS)</li>
    2005 <li>'G:12&PWCSLXYN G:5&IQX R:12&PC R:3&IQX' (System and frequency specific signal priorities)</li>
    2006 </ul>
    2007 </p>
    2008 <p>
    2009 The default 'Signal priority' list is defined as follows:
    2010 <ul>
    2011  <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>
    2012 </ul>
    2013 </p>
    2014 <p>
     2001<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'.
    20152002<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>
    20162003</ul>
Note: See TracChangeset for help on using the changeset viewer.