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


Ignore:
Timestamp:
Jul 31, 2026, 9:44:38 AM (2 months ago)
Author:
stuerze
Message:

RINEX version 2 files can be written now from skl files containing RINEX version 3/4 observation types too

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r10970 r10979  
    16911691<p>Note that a skeleton file contains RINEX header information such as receiver and antenna types. In case of stream conversion to RINEX Version 3, a skeleton file should also contain information on potentially available observation types. A missing skeleton file will force BNC to only save a default set of RINEX 3 observation types.
    16921692</p>
     1693<p>
     1694A skeleton file carrying only RINEX Version 2 style observation types (2-character codes, e.g. 'C1', 'L1') cannot supply the tracking-mode
     1695attribute a RINEX Version 3/4 header needs, so BNC will not use such a skeleton when producing Version 3/4 files. It is treated the same
     1696way as a missing skeleton: with 'Skeleton mandatory' ticked, no RINEX file is produced for the affected stream; otherwise BNC falls back
     1697to a default set of RINEX 3/4 observation types. Conversely, a skeleton carrying RINEX Version 3/4 style observation types
     1698(3-character codes) is always usable when producing RINEX Version 2 files, because the Version 3/4 codes can be unambiguously mapped
     1699down to Version 2 codes (see section 'Version 2').
     1700</p>
    16931701
    16941702<p><h4 id="sklDir">2.4.7 Skeleton Directory - optional</h4></p>
    … …  
    17181726However, this is not recommended, because such stream cannot be precisely mapped to RINEX Version 3
    17191727as the required information on tracking modes (observation attributes) is not part of RTCM Version 2.
     1728</p>
     1729<p>
     1730For the same reason, a RINEX header skeleton file that only carries RINEX Version 2 style observation types
     1731(2-character codes) cannot be used to build a RINEX Version 3/4 header. BNC ignores such a skeleton for that
     1732purpose and falls back to a default set of RINEX 3/4 observation types instead, see section 'Skeleton Mandatory'.
    17201733</p>
    17211734
Note: See TracChangeset for help on using the changeset viewer.