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


Ignore:
Timestamp:
Oct 1, 2020, 3:19:04 PM (4 years ago)
Author:
stuerze
Message:

the default RINEX version in BNC is changed from version 2 to verision 3

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r9155 r9158  
    3030<p>
    3131<h4>Authors</h4>
    32 Georg Weber<sup>(1)</sup>, Leo&scaron; Mervart<sup>(2)</sup>, Andrea St&uuml;rze<sup>(1)</sup>, Axel R&uuml;lke<sup>(1)</sup>, Dirk St&ouml;cker<sup>(3)</sup><br><br>
     32Georg Weber<sup>(1)</sup>, Leo&scaron; Mervart<sup>(2)</sup>, Andrea St&uuml;rze<sup>(1)</sup>, Dirk St&ouml;cker<sup>(3)</sup><br><br>
    3333
    3434<sup>(1) Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany</sup><br>
    … …  
    108108&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.6 <a href="#sklMandat">Skeleton Mandatory</a><br>
    109109&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.7 <a href="#rnxscript">Script</a><br>
     110&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.9 <a href="#rnxvers3">Version 3</a><br>
    110111&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.8 <a href="#rnxvers2">Version 2</a><br>
    111 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.9 <a href="#rnxvers3">Version 3</a><br>
    112 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.10 <a href="#rnxvers3File">Version 3 Filenames</a><br>
    113112&nbsp; &nbsp; &nbsp; 2.5 <a href="#ephemeris"><b>RINEX Ephemeris</b></a><br>
    114113&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.1 <a href="#ephdir">Directory</a><br>
    … …  
    116115&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.3 <a href="#ephport">Port</a><br>
    117116&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.4 <a href="#ephvers">Version</a><br>
    118 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.5 <a href="#ephversFile">Version 3 Filenames</a><br>
    119117&nbsp; &nbsp; &nbsp; 2.6 <a href="#reqc"><b>RINEX Editing & QC</b></a><br>
    120118&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.1 <a href="#reqcact">Action</a><br>
    … …  
    16001598</p>
    16011599
    1602 <p><h4 id="rnxvers2">2.4.8 Version 2 - optional</h4></p>
    1603 <p>
    1604 GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program is explicitly required to produce data files in RINEX Version 2 format:
     1600<p><h4 id="rnxvers3">2.4.8 Version 3 - optional</h4></p>
     1601<p>
     1602The default format for RINEX Observation files is RINEX Version 3. There is nothing to activate in addition to save RTCM Version 3 observation streams in RINEX Version 3 format.
     1603</p>
     1604
     1605<p>
     1606Note, that it is possible to force an RTCM Version 2 stream to be saved in RINEX Version 3 file format. However, this is not recommended, because such stream cannot be precisely mapped to RINEX Version 3 as the required information on tracking modes (observation attributes) is not part of RTCM Version 2.
     1607</p>
     1608
     1609<p><h4 id="rnxvers2">2.4.9 Version 2 - optional</h4></p>
     1610<p>
     1611GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program can be setup to produce data files in RINEX Version 2.11 format:
    16051612<ol type="1">
    16061613<li>When saving the content of incoming observation streams in RINEX Version 2 files as described in this section.</li>
    16071614<li>When editing or concatenating RINEX 3 files to save them in Version 2 format, see section on 'RINEX Editing & QC'.</li>
    16081615</ol>
    1609 As the Version 2 format ignores signal generation attributes, BNC is forced to somehow map RINEX Version 3 to RINEX Version 2 although this cannot be done in one-to-one correspondence. Hence we introduce a 'Signal priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2.
     1616Select RINEX 'Version 2' if you would like to save RTCM Version 3 observation streams in RINEX Version 2 format. As the Version 2 format ignores signal generation attributes, BNC is forced to somehow map RINEX Version 3 to RINEX Version 2 although this cannot be done in one-to-one correspondence. Hence we introduce a 'Signal priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2.
    16101617</p>
    16111618<p>
    … …  
    16361643</p>
    16371644
    1638 <p><h4 id="rnxvers3">2.4.9 Version 3 - optional</h4></p>
    1639 <p>
    1640 The default format for RINEX Observation files is RINEX Version 2.11. Select RINEX 'Version 3' if you would like to save RTCM Version 3 observation streams in RINEX Version 3.03 format.
    1641 </p>
    1642 
    1643 <p>
    1644 Note that it is possible to force an RTCM Version 2 stream to be saved in RINEX Version 3 file format. However, this is not recommended because such stream cannot be precisely mapped to RINEX Version 3 as the required information on tracking modes (observation attributes) is not part of RTCM Version 2.
    1645 </p>
    1646 
    1647 <p><h4 id="rnxvers3File">2.4.10 Version 3 Filenames - optional</h4></p>
    1648 <p>
    1649 Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard.
    1650 </p>
    1651 <p>Default is an empty check box, meaning to still use filenames following the RINEX Version 2 standard although the file content is saved in RINEX Version 3 format.
    1652 </p>
    1653 
    16541645<p><h4 id="ephemeris">2.5 RINEX Ephemeris</h4></p>
    16551646<p>
    1656 Broadcast Ephemeris can be saved in RINEX Navigation files when received e.g. via RTCM Version 3 message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (BDS/BeiDou, tentative message number). The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'.
     1647Broadcast Ephemeris can be saved in RINEX Navigation files when received e.g. via RTCM Version 3 message types:
     1648<ul>
     1649<li> 1019 (GPS) or </li>
     1650<li> 1020 (GLONASS) or </li>
     1651<li> 1044 (QZSS) or </li>
     1652<li> 1043 (SBAS) or </li>
     1653<li> 1045 (Galileo F/NAV) or </li>
     1654<li> 1046 (Galileo I/NAV) or </li>
     1655<li> 1042 (BDS/BeiDou) or </li>
     1656<li> 1041 (IRNSS). </li>
     1657</ul>
     1658</p>
     1659 <p> The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'.
    16571660</p>
    16581661<p>
    … …  
    16601663</p>
    16611664<p>
    1662 Regarding RINEX Version 3 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, and BDS gathered in one Navigation file.
     1665Regarding RINEX Version 3 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, BDS, and IRNSS gathered in one Navigation file.
    16631666</p>
    16641667<p>
    … …  
    16971700<p><h4 id="ephvers">2.5.4 Version - optional</h4></p>
    16981701<p>
    1699 Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris data in RINEX Version 3.03 format.
    1700 </p>
    1701 <p>
    1702 Note that this does not concern the Broadcast Ephemeris output through IP port, which is always in RINEX Version 3.03 format.
    1703 </p>
    1704 
    1705 <p><h4 id="ephversFile">2.5.5 Version 3 Filenames - optional</h4></p>
    1706 <p>
    1707 Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard.
    1708 </p>
    1709 <p>Default is an empty check box, meaning to still use filenames following the RINEX Version 2 standard although the file content is saved in RINEX Version 3 format.
    1710 </p>
    1711 
    1712 <p><img src="IMG/screenshot42.png"/></p>
    1713 <p>Figure 9: BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files</p>
     1702Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 3. Select 'Version 2' if you want to save the ephemeris data in RINEX Version 2.11 format.
     1703</p>
     1704<p>
     1705Note that this does not concern the Broadcast Ephemeris output through IP port, which is always in RINEX Version 3 format.
     1706</p>
    17141707
    17151708<p><h4 id="reqc">2.6 RINEX Editing & QC</h4></p>
    … …  
    17451738<p>
    17461739When specifying several input files, BNC will concatenate their contents. In case of RINEX Observation input files with different observation type header records, BNC will output only one set of adjusted observation type records in the RINEX header which fits to the whole file content.
    1747 </p>
    1748 <p>
    1749 Note that you may specify several RINEX Version 2 Navigation files for GPS and GLONASS.
    17501740</p>
    17511741
    … …  
    51205110   rnxScript      {File upload script, full path [character string]}
    51215111   rnxV2Priority  {Priority of signal attributes [character string, list separated by blank character, example: G:CWPX_? R:CP]}
    5122    rnxV3          {Produce version 3 file content [integer number: 0=no,2=yes]}
    5123    rnxV3filenames {Produce version 3 filenames [integer number: 0=no,2=yes]}
     5112   rnxV2          {Produce version 2 file content [integer number: 0=no,2=yes]}
    51245113
    51255114<b>RINEX Ephemeris Panel keys:</b>
    … …  
    51275116   ephIntr        {File interval [character string: 1 min|2 min|5 min|10 min|15 min|30 min|1 hour|1 day]}
    51285117   ephOutPort     {Output port [integer number]}
    5129    ephV3          {Produce version 3 file content [integer number: 0=no,2=yes]}
    5130    ephV3filenames {Produce version 3 filenames [integer number: 0=no,2=yes]}
     5118   ephV2          {Produce version 2 file content [integer number: 0=no,2=yes]}
    51315119
    51325120<b>RINEX Editing and QC Panel keys:</b>
    … …  
    52155203   PPP/antexFile   {ANTEX file, full path [character string]}
    52165204   PPP/crdFile     {Coordinates file, full path [character string]}
    5217    PPP/v3filenames {Produce version 3 filenames, [integer number: 0=no,2=yes]}
     5205   PPP/v2filenames {Produce version 2 filenames, [integer number: 0=no,2=yes]}
    52185206   PPP/logPath     {Directory for PPP log files [character string]}
    52195207   PPP/nmeaPath    {Directory for NMEA output files [character string]}
Note: See TracChangeset for help on using the changeset viewer.