Changeset 4472 in ntrip for trunk/BNC


Ignore:
Timestamp:
Aug 3, 2012, 11:38:28 AM (12 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r4471 r4472  
    430430<p><a name="rinex"><h4>3.4. RINEX Observations</h4></p>
    431431<p>
    432 Observations will be converted to RINEX if they come in either RTCM Version 2 or RTCM Version 3 format. Depending on the RINEX version and incoming RTCM message types, the files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and COMPASS. In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system.
    433 </p>
     432Observations will be converted to RINEX if they come in either RTCM Version 2 or RTCM Version 3 format. Depending on the RINEX version and incoming RTCM message types, files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and COMPASS. In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system.
     433</p>
     434<p>
     435It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available.
     436</p>
    434437
    435438<p>
    … …  
    439442<p><u>Figure 6:</u> BNC translating incoming streams to 15 min RINEX Version 3 files.</p>
    440443
    441 <p>
    442 Converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header BNC simply introduces all observation types defined in the Version 2 standard and later reports "0" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The intended solution for BNC is to start with RINEX Version 3 observation type records read from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available.
    443 </p>
    444444
    445445<p><a name="rnxname"><h4>3.4.1 RINEX File Names</h4></p>
    … …  
    491491<p><a name="rnxskl"><h4>3.4.5 Skeleton Extension - optional</h4></p>
    492492<p>
    493 Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. A HTTP link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <u>http://www.epncb.oma.be:80/stations/log/skl/brus.skl</u> for an example of a public RINEX Version 2 header skeleton file for the Brussels EPN station.
    494 </p>
    495 <p>
    496 However, sometimes public RINEX header skeleton files are not available, thair contents is not up to date, or you need to put additional/optional records in the RINEX header. For that BNC allows using personal skeleton files that contain the header records you would like to include. You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the RINEX Observations 'Directory' with a 'Skeleton extension' suffix is interpreted by BNC as a personal RINEX header skeleton file for the corresponding stream.
     493Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. A HTTP link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <u>http://www.epncb.oma.be:80/stations/log/skl/brus.skl</u> for an example of a public RINEX header skeleton file for the Brussels EPN station.
     494</p>
     495<p>
     496However, sometimes public RINEX header skeleton files are not available, their contents is not up to date, or you need to put additional/optional records in the RINEX header. For that BNC allows using personal skeleton files that contain the header records you would like to include. You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the RINEX Observations 'Directory' with a 'Skeleton extension' suffix is interpreted by BNC as a personal RINEX header skeleton file for the corresponding stream.
    497497</p>
    498498<p>
    … …  
    512512<li>If such a file exists in the 'RINEX directory', the corresponding public RINEX header skeleton file is ignored. The RINEX header is generated solely from the contents of the personal skeleton.</li>
    513513<li>Personal skeletons should contain a complete first header record of type
    514 <br>- &nbsp; RINEX VERSION / TYPE<br>
    515 Note the small differences mentioned below with regards to RINEX Version 2 and RINEX Version 2 skeletons.</li>
     514<br>- &nbsp; RINEX VERSION / TYPE<br></li>
    516515<li>They should then contain an empty header record of type
    517516<br>- &nbsp; PGM / RUN BY / DATE<br>
    … …  
    525524<br>- &nbsp; ANTENNA: DELTA H/E/N
    526525<br>- &nbsp; WAVELENGTH FACT L1/2 (RINEX Version 2)</li>
     526<br>- &nbsp; SYS / # / OBS TYPES (RINEX Version 3)</li>
    527527<li>They may contain any other optional complete header record as defined in the RINEX documentation.</li>
    528528<li>They should then contain empty header records of type
    529529<br>- &nbsp; # / TYPES OF OBSERV (RINEX Version 2)
    530 <br>- &nbsp; SYS/ # / OBS TYPES (RINEX Version 3)
    531530<br>- &nbsp; TIME OF FIRST OBS
    532531<br>BNC will include these lines in the final RINEX file header together with an additional
    … …  
    540539</p>
    541540<p>
    542 The following is a skeleton example for a RINEX Version 2 file:
     541The following is a skeleton example for a RINEX file:
    543542</p>
    544543<p>
    545544<pre>
    546                     OBSERVATION DATA    G (GPS)             RINEX VERSION / TYPE
     545                    OBSERVATION DATA    M (Mixed)           RINEX VERSION / TYPE
    547546DUND                                                        MARKER NAME
    54854750212M003                                                   MARKER NUMBER
    549 4635120796          TRIMBLE NETRS       1.15                REC # / TYPE / VERS
     5484635120796          TRIMBLE NETR9       1.15                REC # / TYPE / VERS
    55054912626150            TRM41249.00     NONE                    ANT # / TYPE
    551550 -4388121.1700   726671.0500 -4556535.6300                  APPROX POSITION XYZ
    552551        0.0020        0.0000        0.0000                  ANTENNA: DELTA H/E/N
    553552GeoNet Reception    GNS                                     OBSERVER / AGENCY
     553G   28 21C L1C D1C S1C C1W L1W D1W S1W C5X L5X D5X S5X C2W  SYS / # / OBS TYPES
     554       L2W D2W S2W C2X L2X D2X S2X                          SYS / # / OBS TYPES
     555R   16 C1C L1C D1C S1C C1P L1P D1P S1P C2P L2P D2P S2P C2C  SYS / # / OBS TYPES
     556       L2C D2C S2C                                          SYS / # / OBS TYPES
     557S   12 C1C L1C D1C S1C C1W L1W D1W S1W C5I L5I D5I S5I      SYS / # / OBS TYPES
     558E    8 C1  L1  D1  S1  C5  L5  D5  S5                       SYS / # / OBS TYPES
     559C    4 C2I L2I D2I S2I                                      SYS / # / OBS TYPES
     560J   12 C1C L1C D1C S1C C2  L2  D2  S2  C5  L5  D5  S5       SYS / # / OBS TYPES
    554561PORTIONS OF THIS HEADER GENERATED BY BKG FROM               COMMENT
    555562SITELOG dund_20070806.log                                   COMMENT
    … …  
    25552562<tr>
    25562563<td>Aug 2012 &nbsp;</td><td>Version 2.7 &nbsp;</td>
    2557 <td>[Bug] Bug in L5 decoding fixed<br> [Bug] Bug in on-the-fly configuration fixed<br> [Add] Clock RINEX file header extended<br> [Add] Decoding/converting COMPASS and QZSS added<br> [Add] Work on RINEX v2 and v3 quality check started<br> [Mod] Source code completely re-arranged<br> [Add] QWT and QWTPOLAR graphics libraries added<br> [Add] RINEX v2 and v3 quality check through multipath analysis and sky plot<br> [Bug] Short periodic outages in PPP time series when operated when 'Sync Corr' set to zero<br> [Add] Version 2.7 published</td>
     2564<td>[Bug] Bug in L5 decoding fixed<br> [Bug] Bug in on-the-fly configuration fixed<br> [Add] Clock RINEX file header extended<br> [Add] Decoding/converting COMPASS and QZSS added<br> [Add] Work on RINEX v2 and v3 quality check started<br> [Mod] Source code completely re-arranged<br> [Add] QWT and QWTPOLAR graphics libraries added<br> [Add] RINEX v2 and v3 quality check through multipath analysis and sky plot<br> [Bug] Short periodic outages in PPP time series when operated when 'Sync Corr' set to zero<br> [Add] Reading RINEX v3 Observation Type header records from RINEX skeleton files<br> [Add] Save PNG plot files on disk<br> [Add] Version 2.7 published</td>
    25582565</tr>
    25592566
    … …  
    26932700
    26942701<p>
     2702The following is proposed Galileo Navigation Message under discussion for standardization:
     2703<ul>
     2704<li>Type 1045, Galileo ephemeris.</li>
     2705</ul>
     2706</p>
     2707
     2708<p>
    26952709The following are so-called 'State Space Representation' (SSR) messages:
    26962710<ul>
    … …  
    27102724</p>
    27112725
     2726
    27122727<p>
    27132728The following are proposed 'Multiple Signal Messages' (MSM) under discussion for standardization:
    27142729<ul>
    2715 <li>Type 1045, Galileo ephemeris.</li>
    27162730<li>Type 1071, Compact GPS pseudo-ranges</li>
    27172731<li>Type 1072, Compact GPS carrier phases</li>
    … …  
    27202734<li>Type 1075, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength</li>
    27212735<li>Type 1076, Full GPS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    2722 <li>Type 1077, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br></li>
     2736<li>Type 1077, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
    27232737<li>Type 1081, Compact GLONASS pseudo-ranges</li>
    27242738<li>Type 1082, Compact GLONASS carrier phases</li>
    … …  
    27272741<li>Type 1085, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength</li>
    27282742<li>Type 1086, Full GLONASS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    2729 <li>Type 1087, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br></li>
     2743<li>Type 1087, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
    27302744<li>Type 1091, Compact Galileo pseudo-ranges</li>
    27312745<li>Type 1092, Compact Galileo carrier phases</li>
    … …  
    27342748<li>Type 1095, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength</li>
    27352749<li>Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    2736 <li>Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br></li>
     2750<li>Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
    27372751<li>Type 4021, Compact SBAS pseudo-ranges</li>
    27382752<li>Type 4022, Compact SBAS carrier phases</li>
    … …  
    27412755<li>Type 4025, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength</li>
    27422756<li>Type 4026, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    2743 <li>Type 4027, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)</li>
     2757<li>Type 4027, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
    27442758<li>Type 4031, Compact QZSS pseudo-ranges</li>
    27452759<li>Type 4032, Compact QZSS carrier phases</li>
Note: See TracChangeset for help on using the changeset viewer.