- Timestamp:
- Nov 4, 2007, 11:55:14 PM (17 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (19 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r476 r564 5 5 </p> 6 6 <p> 7 BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of the EUREF-IP Pilot Project (EUREF-IP, IP for Internet Protocol) and the Real-Time IGS Working Group (RTIGS WG).8 </p> 9 <p> 10 BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, 32-bit Linux, 64-bit Linux (compiled using option -m32), and Solaris systems. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.2.3are installed.7 BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of EUREF's Real-time GNSS Project (EUREF-IP, IP for Internet Protocol) and the Real-Time IGS Pilot Project (RTIGS). 8 </p> 9 <p> 10 BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, 32-bit Linux, 64-bit Linux (compiled using option -m32), Solaris, and MAC systems. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.3.2 are installed. 11 11 <table> 12 12 <tr></tr> … … 17 17 <tr><td>May 2007 </td><td>Version 1.3 </td><td>Source code published. 18 18 <tr><td>Jul 2007 </td><td>Version 1.4 </td><td>[Bug] Skip messages from proxy server<br> [Bug] Call RINEX script through 'nohup'</td></tr> 19 <tr><td>Nov 2007 </td><td>Version 1.5 </td><td>[Add] Save Ephemeris from RTCM Version 3 streams<br> [Add] Upgrade to Qt Version 4.3.2<br> [Add] Optional RINEX v3 output<br> [Add] SBAS support</td></tr> 19 20 </table> 20 21 </p> … … 37 38 <ul> 38 39 <li>retrieve real-time GNSS data streams available through NTRIP transport protocol,</li> 39 <li>generate high-rate RINEX files to support near real-time GNSS post-processing applications, and/or</li>40 <li>generate high-rate RINEX Observation and Navigation files to support near real-time GNSS post-processing applications, and/or</li> 40 41 <li>output synchronize observations epoch by epoch through an IP port to support real-time GNSS engines.</li> 41 42 </ul> … … 47 48 <ul> 48 49 <li>RTCM Version 2.x format containing message types 18 and 19 (GPS and GLONASS), </li> 49 <li>RTCM Version 3 format containing message types 1002 or 1004 (GPS), and 1010 or 1012 (GLONASS),</li>50 <li>RTCM Version 3 format containing message types 1002 (GPS, SBAS) or 1004 (GPS), and 1010 or 1012 (GLONASS), </li> 50 51 <li>RTIGS format (only GPS).</li> 51 52 </ul> 53 BNC also handles RTCM Version 3 message types 1019 and 1029 carrying Broadcast Ephemeris data. 52 54 Furthermore, BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. 53 55 </p> … … 71 73 B - 5.1. <a href=#rnxname>RINEX File Names</a><br> 72 74 B - 5.2. <a href=#rnxpath>RINEX Directory</a><br> 73 B - 5.3. <a href=#rnxscript>RINEX Script</a><br> 74 B - 5.4. <a href=#rnxinterval>RINEX File Interval</a><br> 75 B - 5.5. <a href=#rnxsample>RINEX Sampling</a><br> 76 B - 5.6. <a href=#rnxskeleton>RINEX Skeleton Extension</a><br> 77 B - 5.7. <a href=#rnxappend>Append Files</a><br> 78 B - 6. <a href=#mountpoints>Mountpoints</a><br> 79 B - 6.1. <a href=#AddMounts>Add Mountpoints</a><br> 80 B - 6.2. <a href=#HostPort>Broadcaster Host and Port</a><br> 81 B - 6.3. <a href=#account>Broadcaster User and Password</a><br> 82 B - 6.4. <a href=#GetTable>Get Table</a><br> 83 B - 6.5. <a href=#delete>Delete Mountpoints</a><br> 84 B - 6.6. <a href=#edit>Edit Mountpoints</a><br> 85 B - 7. <a href=#log>Log</a><br> 86 B - 8. <a href=#start>Start</a><br> 87 B - 9. <a href=#stop>Stop</a><br> 88 B - 10. <a href=#nw>No Window</a> 75 B - 5.3. <a href=#rnxversion>RINEX Version</a><br> 76 B - 5.4. <a href=#rnxscript>RINEX Script</a><br> 77 B - 5.5. <a href=#rnxinterval>RINEX File Interval</a><br> 78 B - 5.6. <a href=#rnxsample>RINEX Sampling</a><br> 79 B - 5.7. <a href=#rnxskeleton>RINEX Skeleton Extension</a><br> 80 B - 5.8. <a href=#rnxappend>Append Files</a><br> 81 B - 6. <a href=#mountpoints>Ephemeris</a><br> 82 B - 6.1. <a href=#ephpath>Ephemeris Directory</a><br> 83 B - 6.2. <a href=#ephvers>RINEX Version</a><br> 84 B - 6.3. <a href=#ephinterval>Ephemeris File Interval</a><br> 85 B - 7. <a href=#mountpoints>Mountpoints</a><br> 86 B - 7.1. <a href=#AddMounts>Add Mountpoints</a><br> 87 B - 7.2. <a href=#HostPort>Broadcaster Host and Port</a><br> 88 B - 7.3. <a href=#account>Broadcaster User and Password</a><br> 89 B - 7.4. <a href=#GetTable>Get Table</a><br> 90 B - 7.5. <a href=#delete>Delete Mountpoints</a><br> 91 B - 7.6. <a href=#edit>Edit Mountpoints</a><br> 92 B - 8. <a href=#log>Log</a><br> 93 B - 9. <a href=#start>Start</a><br> 94 B - 10. <a href=#stop>Stop</a><br> 95 B - 11. <a href=#nw>No Window</a> 89 96 </p> 90 97 … … 148 155 </p> 149 156 <p> 150 Note that 'Wait for full epoch' does not influence the RINEX file contents. Observations received later than 'Wait for full epoch' seconds will still be included in the RINEXfiles.157 Note that 'Wait for full epoch' does not influence the RINEX Observation file contents. Observations received later than 'Wait for full epoch' seconds will still be included in the RINEX Observation files. 151 158 </p> 152 159 … … 205 212 <p><a name="rinex"><h4>B - 5. RINEX</h4></p> 206 213 <p> 207 Observations will be converted to RINEX Version 2.11 if they come in either RTCM Version 2.x, RTCM Version 3, or RTIGS format. BNC's RINEX observation files generally contain C1, C2, P1, P2, L1, L2, S1, and S2 observations. In case an observation is unavailable, its value is set to zero '0.000'. Note that even if a RINEX file does not contain GLONASS data, the 'RINEX TYPE' field in the RINEXfile header may be set to 'M (MIXED)'.214 Observations will be converted to RINEX if they come in either RTCM Version 2.x, RTCM Version 3, or RTIGS format. BNC's RINEX Observation files generally contain C1, C2, P1, P2, L1, L2, S1, and S2 observations. In case an observation is unavailable, its value is set to zero '0.000'. Note that even if a RINEX Observation file does not contain GLONASS or SBAS data, the 'RINEX TYPE' field in the RINEX Observation file header may be set to 'M (MIXED)'. 208 215 </p> 209 216 <p><a name="rnxname"><h4>B - 5.1 RINEX File Names</h4></p> 210 217 <p> 211 RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID) while omitting the residual part of the mountpoint string. Thus, retrieving data from mountpoints FRANKFURT and WETTZELL leads to hourly RINEX observation files named</p>218 RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID) while omitting the residual part of the mountpoint string. Thus, retrieving data from mountpoints FRANKFURT and WETTZELL leads to hourly RINEX Observation files named</p> 212 219 <p> 213 220 FRAN{ddd}{h}.{yy}O<br> … … 218 225 </p> 219 226 <p> 220 For those streams that show mountpoints with an identical 4Char Station ID (same first 4 characters), the mountpoint strings are split into two sub-strings and both become part of the RINEX file name. Example: When simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX observation file names are defined as</p>227 For those streams that show mountpoints with an identical 4Char Station ID (same first 4 characters), the mountpoint strings are split into two sub-strings and both become part of the RINEX file name. Example: When simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Observation file names are defined as</p> 221 228 <p> 222 229 FRAN{ddd}{h}_KFURT.{yy}O<br> … … 224 231 </p> 225 232 <p> 226 If several streams show exactly the same mountpoint (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 file name leading i.e. to hourly RINEX observation files like</p>233 If several streams show exactly the same mountpoint (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 file name leading i.e. to hourly RINEX Observation files like</p> 227 234 <p> 228 235 BRUS{ddd}{h}_0.{yy}O<br> … … 230 237 </p> 231 238 <p> 232 Note that RINEX file names for all intervals less than 1 hour follow the file name convention for 15 minutes RINEX observation files i.e.</p>239 Note that RINEX file names for all intervals less than 1 hour follow the file name convention for 15 minutes RINEX Observation files i.e.</p> 233 240 <p> 234 241 FRAN{ddd}{h}{mm}.{yy}O … … 240 247 <p><a name="rnxpath"><h4>B - 5.2 RINEX Directory - optional</h4></p> 241 248 <p> 242 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. 243 </p> 244 245 <p><a name="rnxscript"><h4>B - 5.3 RINEX Script - optional</h4></p> 246 <p> 247 Whenever a RINEX file is saved, you may like to compress, copy or upload it immediately via FTP. For that you enter the full path of a script or batch file which is then called to carry out these operations. The RINEX file path will be passed to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux systems). 249 Enter a path for saving the RINEX Observation files in a directory. If this directory does not exist, BNC will not create RINEX Observation files. Default value for 'RINEX directory' is an empty option field, meaning that streams are not converted to RINEX. 250 </p> 251 252 <p><a name="rnxversion"><h4>B - 5.3 RINEX Version - optional</h4></p> 253 <p> 254 Default format for RINEX Observation files is RINEX Version 2.11. Select 'RINEX v3' if you want to save observations in RINEX Version 3 format. 255 </p> 256 257 <p><a name="rnxscript"><h4>B - 5.4 RINEX Script - optional</h4></p> 258 <p> 259 Whenever a RINEX Observation file is saved, you may like to compress, copy or upload it immediately via FTP. For that you enter the full path of a script or batch file which is then called to carry out these operations. The RINEX Observation file path will be passed to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux systems). 248 260 </p> 249 261 <p> 250 The triggering event for calling the script or batch file is the end of a RINEX file interval. If that is superposed by a stream outage, the triggering event is the stream reconnect. 251 </p> 252 253 <p><a name="rnxinterval"><h4>B - 5.4 RINEX File Interval - mandatory if 'RINEX directory' set</h4></p> 254 <p> 255 Select the interval for the RINEX file generation. Default for 'RINEX file interval' is 15 minutes. 256 </p> 257 258 <p><a name="rnxsample"><h4>B - 5.5 RINEX Sampling - mandatory if 'RINEX directory' set </h4></p> 259 <p> 260 Select the RINEX sample interval in seconds. Zero '0' stands for converting all incoming epochs to RINEX. Default for RINEX 'Sampling' is '0'. 261 </p> 262 263 <p><a name="rnxskeleton"><h4>B - 5.6 RINEX Skeleton Extension - optional</h4></p> 264 <p> 265 Whenever BNC starts generating RINEX 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. An 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 for a public RINEX header skeleton file concerning the EPN station Brussels. 262 The triggering event for calling the script or batch file is the end of a RINEX Observation 'File interval'. If that is superposed by a stream outage, the triggering event is the stream reconnect. 263 </p> 264 <p> 265 As an alternative to initiating file uploads through BNC, you may like to call an upload script or bach file through your crontable (independant from BNC) once every 2 or 3 minutes after the end of each RINEX 'File interval'. 266 </p> 267 268 <p><a name="rnxinterval"><h4>B - 5.5 RINEX File Interval - mandatory if 'RINEX directory' set</h4></p> 269 <p> 270 Select the interval for the RINEX Observation file generation. Default for RINEX 'File interval' is 15 minutes. 271 </p> 272 273 <p><a name="rnxsample"><h4>B - 5.6 RINEX Sampling - mandatory if 'RINEX directory' set </h4></p> 274 <p> 275 Select the RINEX Observation sample interval in seconds. Zero '0' stands for converting all incoming epochs to RINEX. Default for RINEX 'Sampling' is '0'. 276 </p> 277 278 <p><a name="rnxskeleton"><h4>B - 5.7 RINEX Skeleton Extension - optional</h4></p> 279 <p> 280 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. An 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 for a public RINEX header skeleton file concerning the EPN station Brussels. 266 281 </p> 267 282 <p> … … 312 327 <p> 313 328 314 <p><a name="rnxappend"><h4>B - 5.7 Append Files</h4></p> 315 <p> 316 When starting BNC, new RINEX files are created by default. Probably existing files will be overwritten. However, it may be desirable to append observations to already existing RINEX files following a restart of BNC after an intentional 'Stop', a system crash or a crash of BNC. Hit 'Append files' to continue with already existing files and thus save what has been recorded so far. Note that option 'Append files' also concerns the 'ASCII output file' and the 'Log' file. 317 </p> 318 <p><a name="mountpoints"><h4>B - 6. Mountpoints</h4></p> 329 <p><a name="rnxappend"><h4>B - 5.8 Append Files</h4></p> 330 <p> 331 When starting BNC, new RINEX Observation files are created by default. Probably existing files will be overwritten. However, it may be desirable to append observations (and ephemeris) to already existing RINEX files following a restart of BNC after an intentional 'Stop', a system crash or a crash of BNC. Hit 'Append files' to continue with already existing files and thus save what has been recorded so far. Note that option 'Append files' also concerns RINEX Navigation files, the 'ASCII output file' and the 'Log' file. 332 </p> 333 <p><a name="mountpoints"><h4>B - 6. Ephemeris</h4></p> 334 <p> 335 Broadcast Ephemeris can be saved in RINEX Navigation files if received in RTCM Version 3 as message types 1019 (GPS) and 1020 (GLONASS). The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'GPS_' and 'GLO_' for RINEX Version 2.11 Navigation files and 'MIX_' for RINEX Version 3 Navigation files. 336 </p> 337 338 <p><a name="ephpath"><h4>B - 6.1 Ephemeris Directory - optional</h4></p> 339 <p> 340 Enter a path for saving Broadcast Ephemeris data as RINEX Navigation files in a directory. If this directory does not exist, BNC will not create RINEX Naviggation files. Default value for 'Ephemeris directory' is an empty option field, meaning that no RINEX Navigation files are created. 341 </p> 342 343 <p><a name="ephvers"><h4>B - 6.2 RINEX Version - optional</h4></p> 344 <p> 345 Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 2.11. Select 'RINEX v3' if you want to save the ephemeris in RINEX Version 3 format. 346 </p> 347 348 <p><a name="ephinterval"><h4>B - 6.3 Ephemeris Interval - mandatory if 'Ephemeris directory' set</h4></p> 349 <p> 350 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. 351 Default for Ephemeris 'File interval' is 1 day. 352 </p> 353 354 <p><a name="mountpoints"><h4>B - 7. Mountpoints</h4></p> 319 355 <p> 320 356 Each stream on an NTRIP broadcaster is defined through a unique source ID called mountpoint. An NTRIP client like BNC can access the data of a desired stream by its mountpoint. Information about mountpoints is available through the source-table maintained by the NTRIP broadcaster. Note that mountpoints could show up in BNC more than once when retrieving streams from several NTRIP broadcasters. … … 333 369 </table> 334 370 335 <p><a name="AddMounts"><h4>B - 6.1 Add Mountpoints</h4></p>371 <p><a name="AddMounts"><h4>B - 7.1 Add Mountpoints</h4></p> 336 372 <p> 337 373 Button 'Add Mountpoints' opens a window that allows you to select data streams from an NTRIP broadcaster by their mountpoints. 338 374 </p> 339 375 340 <p><a name="HostPort"><h4>B - 6.2 Broadcaster Host and Port - mandatory</h4></p>376 <p><a name="HostPort"><h4>B - 7.2 Broadcaster Host and Port - mandatory</h4></p> 341 377 <p> 342 378 Enter the NTRIP broadcaster host IP and port number. <u>http://www.rtcm-ntrip.org/home</u> provides information about known NTRIP broadcaster installations. Note that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u>. 343 379 </p> 344 380 345 <p><a name="account"><h4>B - 6.3 Broadcaster User and Password - mandatory for protected streams</h4></p>381 <p><a name="account"><h4>B - 7.3 Broadcaster User and Password - mandatory for protected streams</h4></p> 346 382 <p> 347 383 Streams on NTRIP broadcasters may be protected by password. Enter a valid 'User' ID and 'Password' for access to protected NTRIP broadcaster streams. Accounts are usually provided per NTRIP broadcaster through a registration procedure. Register through <u>http://igs.bkg.bund.de/index_ntrip_reg.htm</u> for access to protected streams on <u>www.euref-ip.net</u> and <u>www.igs-ip.net</u>. 348 384 </p> 349 385 350 <p><a name="GetTable"><h4>B - 6.4 Get Table</h4></p>351 <p> 352 Hit button 'Get Table' to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM 2.x, RTCM 3, or RTIGS format. RTCM 2.x streams must contain message types 18 and 19 while RTCM 3 streams must contain GPS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Select your streams line by line, use +Shift and +Ctrl when necessary.386 <p><a name="GetTable"><h4>B - 7.4 Get Table</h4></p> 387 <p> 388 Hit button 'Get Table' to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM 2.x, RTCM 3, or RTIGS format. RTCM 2.x streams must contain message types 18 and 19 while RTCM 3 streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that RINEX Navigation files containing Broadcast Ephemeris need RTCM 3 streams containing message types 1019 (GPS) and 1020 (GLONASS). Select your streams line by line, use +Shift and +Ctrl when necessary. 353 389 </p> 354 390 <p> … … 359 395 </p> 360 396 361 <p><a name="delete"><h4>B - 6.5 Delete Mountpoints</h4></p>397 <p><a name="delete"><h4>B - 7.5 Delete Mountpoints</h4></p> 362 398 <p> 363 399 To delete a stream shown under 'Mountpoints' in the main window, select it by mouse click and hit 'Delete Mountpoints'. For a simultaneous deletion of several streams highlight them using +Shift and +Ctrl.</p> 364 400 365 <p><a name="edit"><h4>B - 6.6 Edit Mountpoints</h4></p>401 <p><a name="edit"><h4>B - 7.6 Edit Mountpoints</h4></p> 366 402 <ul> 367 403 <li> … … 378 414 </ul> 379 415 380 <p><a name="log"><h4>B - 7. Log - optional</h4></p>416 <p><a name="log"><h4>B - 8. Log - optional</h4></p> 381 417 <p> 382 418 BNC comments its activities in the 'Log' section on the main windows. Comments can be saved in a file when entering a full path for a 'Log' file. Information is given on the communication between BNC and the NTRIP broadcaster as well as on problems that may occur concerning communication link, stream availability, stream delay, stream conversion etc. Default value for 'Log' is an empty option field, meaning that BNC comments are not saved in a file. 383 419 </p> 384 420 385 <p><a name="start"><h4>B - 8. Start</h4></p>421 <p><a name="start"><h4>B - 9. Start</h4></p> 386 422 <p> 387 423 Hit 'Start' to start retrieving, decoding, and converting GNSS data streams in real-time. Note that 'Start' generally forces BNC to begin with fresh RINEX files and thus overwrite probably existing files when necessary unless option 'Append files' is set. 388 424 </p> 389 425 390 <p><a name="stop"><h4>B - 9. Stop</h4></p>426 <p><a name="stop"><h4>B - 10. Stop</h4></p> 391 427 <p> 392 428 Hit the 'Stop' button in order to stop BNC. 393 429 </p> 394 430 395 <p><a name="nw"><h4>B - 1 0. No Window - optional</h4></p>431 <p><a name="nw"><h4>B - 11. No Window - optional</h4></p> 396 432 <p> 397 433 You can use BNC on all systems in batch mode with the command line option '-nw'. BNC then runs in 'no window' mode, reading options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Client.conf (Unix/Linux) or from the register BNC_NTRIP_Client (Windows). … … 406 442 </li> 407 443 <li> 408 So far BNC only handles GPS and GLONASS data while ignoring Galileo.444 So far BNC only handles GPS, SBAS and GLONASS data while ignoring Galileo. 409 445 </li> 410 446 <li> … … 436 472 <ul> 437 473 <li> RTCM 2.x decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen</li> 438 <li> RTCM 3 decoder, written for BKG by Dirk Stoecker, EuronikGmbH, Schoenefeld</li>474 <li> RTCM 3 decoder, written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld</li> 439 475 <li> RTIGS decoder, written by Ken MacLeod, Natural Resources, Canada.</li> 440 476 </ul> … … 582 618 <li>Type 1013, Modified julian date, leap second, configured message types and interval.</li> 583 619 <li>Type 1014 and 1017, Network RTK (MAK) messages (under development).</li> 584 <li>Type 1019, GPS Ephemeris (under development).</li>585 <li>Type 1020, GLONASS Ephemeris (under development).</li>620 <li>Type 1019, GPS Ephemeris.</li> 621 <li>Type 1020, GLONASS Ephemeris.</li> 586 622 <li>Type 4088 and 4095, Proprietary messages (under development). 587 623 </li> … … 652 688 <p><a name="config"><h4>F - 4. Config File</h4></p> 653 689 <p> 654 The following is an example for the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the retrieval of stream HOE20 form www.euref-ip.net and GOPE0from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' :690 The following is an example for the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the retrieval of stream ACOR0 form www.euref-ip.net and FFMJ3 from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' : 655 691 <pre> 656 692 [General] 657 casterHost= 658 casterPassword= 659 casterPort= 660 casterUser= 661 font="Sans Serif,8,-1,5,50,0,0,0,0,0" 662 logFile=${HOME}/bnc.log 663 mountPoints=//user:password@www.euref-ip.net:80/HOE20 RTCM_3.0 54.76 8.29 no, //user:password@www.igs-ip.net:80/GOPE0 RTCM_2.2 49.91 14.79 no 664 outFile= 665 outPort= 666 proxyHost=proxy.bkg.de 667 proxyPort=8000 693 casterHost=www.euref-ip.net 694 casterPassword=pass 695 casterPort=80 696 casterUser=user 697 ephIntr=1 day 698 ephPath=/home/user/rinex 699 ephV3=2 700 logFile=/home/user/log.txt 701 mountPoints=//user:pass@www.euref-ip.net:80/ACOR0 RTCM_2.3 43.36 351.60 no, //user:pass@www.igs-ip.net:80/FFMJ3 RTCM_3.0 41.58 1.40 no 702 outFile=/home/user/ascii 703 outPort=2101 704 proxyHost=proxyhost 705 proxyPort=8001 668 706 rnxAppend=2 669 707 rnxIntr=15 min 670 rnxPath= ${HOME}/rinex708 rnxPath=/home/weber/rinex 671 709 rnxSampl=0 672 rnxScript= ${HOME}/up2archive710 rnxScript=/home/weber/up2archive 673 711 rnxSkel=SKL 712 rnxV3=2 674 713 waitTime=5 675 714 </pre>
Note:
See TracChangeset
for help on using the changeset viewer.
