Changeset 212 in ntrip
- Timestamp:
- Oct 6, 2006, 4:30:27 PM (18 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r211 r212 53 53 B - 4.3. <a href=#binary>Port for Binary Output</a><br> 54 54 B - 5. <a href=#rinex>RINEX</a><br> 55 B - 5.1. <a href=#rnxpath>RINEX Directory Path</a><br>55 B - 5.1. <a href=#rnxpath>RINEX Directory</a><br> 56 56 B - 5.2. <a href=#rnxscript>RINEX Script</a><br> 57 57 B - 5.3. <a href=#rnxinterval>RINEX File Interval</a><br> … … 189 189 190 190 <a name="rnxpath"> 191 <p><h4>B - 5.1 RINEX Directory Path- optional</h4></p>192 <p> 193 Enter a path for saving the RINEX files in a directory. If this directory does not exist, BNC will not create RINEX files. Default value for 'RINEX directory path' is an empty option field, meaning that streams are not converted to RINEX.191 <p><h4>B - 5.1 RINEX Directory - optional</h4></p> 192 <p> 193 Enter a path for saving the RINEX files in a directory. If this directory does not exist, BNC will not create RINEX files. Default value for 'RINEX directory' is an empty option field, meaning that streams are not converted to RINEX. 194 194 </p> 195 195 … … 201 201 202 202 <a name="rnxinterval"> 203 <p><h4>B - 5.3 RINEX File Interval - mandatory if 'RINEX directory path' set</h4></p>203 <p><h4>B - 5.3 RINEX File Interval - mandatory if 'RINEX directory' set</h4></p> 204 204 <p> 205 205 Select the interval for RINEX file generation. Default for 'RINEX file interval' is 15 minutes. … … 207 207 208 208 <a name="rnxsample"> 209 <p><h4>B - 5.4 RINEX Sampling - mandatory if 'RINEX directory path' set </h4></p>209 <p><h4>B - 5.4 RINEX Sampling - mandatory if 'RINEX directory' set </h4></p> 210 210 <p> 211 211 Select the RINEX sample interval in seconds. Zero '0' stands for converting all incoming epochs to RINEX. Default for RINEX 'Sampling' is '0'. … … 215 215 <p><h4>B - 5.5 RINEX Skeleton Extension - optional</h4></p> 216 216 <p> 217 BNC lets you introduce RINEX header skeleton files that contain the header records you would like to see instead of a default header. You may like to derive RINEX skeleton files from the information given in sitelogs. A file in the 'RINEX directory path' with the 'RINEX skeleton extension' is understood by BNC as a RINEX header skeleton file for the affected stream.217 BNC lets you introduce RINEX header skeleton files that contain the header records you would like to see instead of a default header. You may like to derive RINEX skeleton files from the information given in sitelogs. A file in the 'RINEX directory' with the 'RINEX skeleton extension' is understood by BNC as a RINEX header skeleton file for the affected stream. 218 218 </p> 219 219 <p> … … 344 344 The BKG Ntrip Client (BNC) Qt Graphic User Interface (GUI) has been developed for the Federal Agency for Cartography and Geodesy (BKG) by Leos Mervart, Czech Technical University Prague, Department of Advanced Geodesy. BNC integrates the following GNU GPL software components: 345 345 <ul> 346 <li> RTCM 2.x decoder, written by John Sager with contributions from Carsten Becker, German Aerospace Center, DLR, Neustrelitz</li>346 <li> RTCM 2.x decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, with contributions from Leos Mervart</li> 347 347 <li> RTCM 3 decoder, written for BKG by Dirk Stoecker, Euronik GmbH, Schoenefeld</li> 348 348 <li> RTIGS decoder, written by Ken MacLeod, Natural Resources Canada, NRCan</li> … … 483 483 <li>Tpye 1001, GPS L1 code and phase.</li> 484 484 <li>Type 1002, GPS L1 code and phase and ambiguities and carrier to noise ratio.</li> 485 <li>Type 1003, GPS L1 and L 1code and phase.</li>485 <li>Type 1003, GPS L1 and L2 code and phase.</li> 486 486 <li>Type 1004, GPS L1 and L2 code and phase and ambiguities and carrier to noise ratio.</li> 487 487 <li>Type 1005, Station coordinates XZY for antenna reference point.</li> … … 491 491 <li>Type 1009, GLONASS L1 code and phase.</li> 492 492 <li>Type 1010, GLONASS L1 code and phase and ambiguities and carrier to noise ratio.</li> 493 <li>Type 1011, GLONASS L1 and L 1code and phase.</li>493 <li>Type 1011, GLONASS L1 and L2 code and phase.</li> 494 494 <li>Type 1012, GLONASS L1 and L2 code and phase and ambiguities and carrier to noise ratio.</li> 495 495 <li>Type 1013, Modified julian date, leap second, configured message types and interval.</li> … … 510 510 <p><h4>F - 3.1 SOC</h4></p> 511 511 <p> 512 Input from Ken? 513 </p> 514 <p> 515 </p> 516 512 The SOC format has been designed in July 1999 by the Jet Propulsion Laboratory (JPL) and the California Institute of Technology (CalTech) to transport 1Hz GPS data with minimal bandwidth over the open Internet. SOC follows the 'little-endian' byte order meaning that the low-order byte of a number is stored in memory at the lowest address, and the high-order byte at the highest address. (The little end comes first.) Because the transport layer is UDP, the format does not include sync bits, a checksum or cyclic redundancy checksum (CRC). SOC allows to transport the GPS observable CA, P1, P2, L1, and L2, efficiently compressed down to 14 bytes with 1 mm range resolution and 0.02 mm phase resolution. SOC contains epochs for cycle slips, a stand-alone time-tag per epoch, a minimum representation of the receiver's clock solution, 3 SNR numbers, a unique site id, a modulo 12 hour sequence number and flags for receiver type and GPS health. SOC's simple structure comprises an 8 byte header, a 9 byte overhead for timetag, number of gps, etc., plus 21 data bytes per gps. 513 </p> 514 <p> 515 Visit <u>http://gipsy.jpl.nasa.gov/igdg/papers/SOC_FORMAT.ppt</u> for further details. 516 </p> 517 <p> 518 </p> 519
Note:
See TracChangeset
for help on using the changeset viewer.
