Changeset 7472 in ntrip for trunk


Ignore:
Timestamp:
Sep 28, 2015, 8:38:45 AM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r7416 r7472  
    946946
    947947<p>
    948 Signal priorities can be specified as equal for all systems or system specific. The following are example priority strings:</li>
     948Signal priorities can be specified either as equal for all systems or system specific. The following are example priority strings:</li>
    949949<ul>
    950950<li>CWPX_? (Same signal priorities valid for all systems)</li>
    … …  
    12551255<p>
    12561256<ul>
    1257 <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 can't 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 as equal for all systems or system specifics. The following are example priority strings:</li>
     1257<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 can't 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 specifics. The following are example priority strings:</li>
    12581258<ul>
    12591259<li>CWPX_? (Same signal priorities valid for all systems)</li>
Note: See TracChangeset for help on using the changeset viewer.