Changeset 9185 in ntrip


Ignore:
Timestamp:
Oct 23, 2020, 9:52:19 PM (5 weeks ago)
Author:
stuerze
Message:
 
File:
1 edited

Legend:

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

    r9158 r9185  
    107107&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.5 <a href="#rnxskl">Skeleton Extension</a><br>
    108108&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.6 <a href="#sklMandat">Skeleton Mandatory</a><br>
    109 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.7 <a href="#rnxscript">Script</a><br>
     109&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.7 <a href="#sklDir">Skeleton Directory</a><br>
     110&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.8 <a href="#rnxscript">Script</a><br>
    110111&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.9 <a href="#rnxvers3">Version 3</a><br>
    111 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.8 <a href="#rnxvers2">Version 2</a><br>
     112&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.10 <a href="#rnxvers2">Version 2</a><br>
    112113&nbsp; &nbsp; &nbsp; 2.5 <a href="#ephemeris"><b>RINEX Ephemeris</b></a><br>
    113114&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.1 <a href="#ephdir">Directory</a><br>
     
    210211&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.3 <a href=#combimax>Maximal Residuum</a><br>
    211212&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.4 <a href=#combismpl>Sampling</a><br>
    212 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.5 <a href=#combiGLO>Use GLONASS</a><br>
    213213&nbsp; &nbsp; &nbsp; 2.15 <a href=#upclk><b>Upload Corrections</b></a><br>
    214214&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.1 <a href=#upadd>Add, Delete Row</a><br>
     
    14261426<p><h4 id="rnxname">2.4.1 RINEX Filenames</h4></p>
    14271427<p>
    1428 The default for RINEX filenames in BNC follows the convention of RINEX Version 2. However, the software provides options to alternatively follow the filename convention of RINEX Version 3. RINEX Version 2 filenames are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4-Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named</p>
    1429 
    1430 <pre>
    1431    FRAN{ddd}{h}.{yy}O
    1432    WETT{ddd}{h}.{yy}O
    1433 </pre>
    1434 <p>
    1435 where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year.
    1436 </p>
    1437 <p>
    1438 If there is more than one stream with identical 4-Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX filename. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Version 2 Observation files are named as</p>
    1439 <pre>
    1440    FRAN{ddd}{h}_KFURT.{yy}O
    1441    FRAN{ddd}{h}_CE.{yy}O
    1442 </pre>
    1443 <p>
    1444 If several streams show up with exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the filename, leading e.g. to hourly RINEX Version 2 Observation files like</p>
    1445 <pre>
    1446    BRUS{ddd}{h}_0.{yy}O
    1447    BRUS{ddd}{h}_1.{yy}O
    1448 </pre>
    1449 <p>
    1450 Note that RINEX Version 2 filenames for all intervals less than 1 hour follow the filename convention for 15 minutes RINEX Version 2 Observation files e.g.</p>
    1451 <pre>
    1452    FRAN{ddd}{h}{mm}.{yy}O
    1453 </pre>
    1454 <p>
    1455 where 'mm' is the starting minute within the hour.
     1428The default for RINEX filenames in BNC follows the convention of RINEX Version 3. However, the software provides options to alternatively follow the filename convention of RINEX Version 2.
    14561429</p>
    14571430
     
    14821455</p>
    14831456
     1457<p>
     1458RINEX Version 2 filenames are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4-Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named</p>
     1459
     1460<pre>
     1461   FRAN{ddd}{h}.{yy}O
     1462   WETT{ddd}{h}.{yy}O
     1463</pre>
     1464<p>
     1465where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year.
     1466</p>
     1467<p>
     1468If there is more than one stream with identical 4-Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX filename. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Version 2 Observation files are named as</p>
     1469<pre>
     1470   FRAN{ddd}{h}_KFURT.{yy}O
     1471   FRAN{ddd}{h}_CE.{yy}O
     1472</pre>
     1473<p>
     1474If several streams show up with exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the filename, leading e.g. to hourly RINEX Version 2 Observation files like</p>
     1475<pre>
     1476   BRUS{ddd}{h}_0.{yy}O
     1477   BRUS{ddd}{h}_1.{yy}O
     1478</pre>
     1479<p>
     1480Note that RINEX Version 2 filenames for all intervals less than 1 hour follow the filename convention for 15 minutes RINEX Version 2 Observation files e.g.</p>
     1481<pre>
     1482   FRAN{ddd}{h}{mm}.{yy}O
     1483</pre>
     1484<p>
     1485where 'mm' is the starting minute within the hour.
     1486</p>
     1487
    14841488<p><h4 id="rnxdir">2.4.2 Directory - optional</h4></p>
    14851489<p>
     
    15121516</p>
    15131517<p>
    1514 When producing RINEX Observation files from mountpoints (examples) 'BRUX0', 'BRUX00BEL0', and 'WTZR_RTCM3', the following skeleton filenames would be accepted
    1515 </p>
    1516 <pre>
    1517    BRUX.skl      (4 char corresponding to RINEX version 2)
     1518When producing RINEX Observation files from mountpoints (examples) 'BRUX00BEL0', 'WTZR_RTCM3', and 'BRUX0', the following skeleton filenames would be accepted
     1519</p>
     1520<pre>
    15181521   BRUX00BEL.skl (9 char corresponding to RINEX version 3)
    15191522   WTZR_RTCM.skl (9 char corresponding to RINEX version 3)
     1523   BRUX.skl      (4 char corresponding to RINEX version 2)
    15201524</pre>
    15211525<p>
     
    15871591</p>
    15881592
    1589 <p><h4 id="rnxscript">2.4.7 Script - optional</h4></p>
     1593<p><h4 id="sklMandat">2.4.7 Skeleton Directory - optional</h4></p>
     1594<p>
     1595Here you can specify the path, where local skeleton files are located. If no directory is specified, the path is assumed to where the RINEX Observation files will stored.
     1596</p>
     1597
     1598
     1599<p><h4 id="rnxscript">2.4.8 Script - optional</h4></p>
    15901600<p>
    15911601Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that, specify the full path to such script/batch file. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac OS X systems).
     
    15981608</p>
    15991609
    1600 <p><h4 id="rnxvers3">2.4.8 Version 3 - optional</h4></p>
     1610<p><h4 id="rnxvers3">2.4.9 Version 3 - optional</h4></p>
    16011611<p>
    16021612The 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.
     
    16071617</p>
    16081618
    1609 <p><h4 id="rnxvers2">2.4.9 Version 2 - optional</h4></p>
     1619<p><h4 id="rnxvers2">2.4.10 Version 2 - optional</h4></p>
    16101620<p>
    16111621GNSS 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:
     
    16601670</p>
    16611671<p>
     1672Regarding RINEX Version 3 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, BDS, and IRNSS gathered in one Navigation file.
     1673</p>
     1674<p>
     1675The following is an example for a RINEX Version 3 Navigation filename. The file contains one day's data. 'MN' stands for 'Multi Constellation Navigation' data.
     1676<pre>
     1677   BRDC00DEU_S_20121600000_01D_MN.rnx
     1678</pre>
     1679</p>
     1680
     1681<p>
    16621682For RINEX Version 2 Navigation files the last character is 'N' or 'G' for GPS or GLONASS ephemeris in two separate files.
    1663 </p>
    1664 <p>
    1665 Regarding RINEX Version 3 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, BDS, and IRNSS gathered in one Navigation file.
    1666 </p>
    1667 <p>
    1668 The following is an example for a RINEX Version 3 Navigation filename. The file contains one day's data. 'MN' stands for 'Multi Constellation Navigation' data.
    1669 <pre>
    1670    BRDC00DEU_S_20121600000_01D_MN.rnx
    1671 </pre>
    1672 </p>
    1673 
    1674 <p>
    1675 Note that streams dedicated to carry Broadcast Ephemeris messages in RTCM Version 3 format in high repetition rates are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>.
    16761683</p>
    16771684
     
    39603967<p>Specify a combination sampling interval. Orbit and clock corrections will be produced following that interval. A value of 10 sec may be an appropriate choice.</p>
    39613968
    3962 <p><h4 id="combiGLO">2.14.1.5 Use GLONASS - optional</h4></p>
    3963 <p>
    3964 You may tick the 'Use GLONASS' option in case you want to produce a GPS plus GLONASS combination and both systems are supported by the Broadcast Correction streams participating in the combination.
    3965 </p>
    3966 
    39673969<p><h4 id="upclk">2.15 Upload Corrections</h4></p>
    39683970<p>
     
    51075109   rnxSampl       {File sampling rate [integer number of seconds: 0,5|10|15|20|25|30|35|40|45|50|55|60]}
    51085110   rnxSkel        {RINEX skeleton file extension [character string]}
     5111   rnxSkelPath    {Directory for local skeleton files [character string]}\n"
    51095112   rnxOnlyWithSKL {Using RINEX skeleton file is mandatory [integer number: 0=no,2=yes]}
    51105113   rnxScript      {File upload script, full path [character string]}
     
    52475250   cmbMaxres       {Clock outlier residuum threshold in meters [floating-point number]
    52485251   cmbSampl        {Clock sampling rate [integer number of seconds: 10|20|30|40|50|60]}
    5249    cmbUseGlonass   {Use GLONASS in combination [integer number: 0=no,2=yes]
    52505252
    52515253<b>Upload Corrections Panel keys:</b>
Note: See TracChangeset for help on using the changeset viewer.