Changeset 4135 in ntrip


Ignore:
Timestamp:
May 7, 2012, 12:03:46 AM (13 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r4134 r4135  
    1818</p>
    1919
    20 <h3>Contents</h3>
    21 <p>
    22 <h4>
     20<p><b>Contents</b><br>
    2321<a href=#purpose>1. Purpose</a><br>
    2422<a href=#resources>2. Modes &amp; Resources</a><br>
    … …  
    2624<a href=#optsettings>4. Settings</a><br>
    2725<a href=#limits>5. Limitations &amp; Known Bugs</a><br>
    28 <a href=#authors>6. Authors</a><br>
    29 <a href=#annex>7. Annex</a><br>
    30 </h4>
     26<a href=#annex>6. Annex</a><br>
     27</p>
     28
     29<p>
     30<b><a name="authors">Authors</b><br>
     31The 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 Geodesy. BNC includes the following GNU GPL software components:
     32<ul>
     33<li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen</li>
     34<li> RTCM 3 decoder for standard messages and a RTCM 3 encoder & decoder for SSR messages, both written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld</li>
     35</ul>
     36</p>
     37<p>
     38Georg Weber<br>
     39Federal Agency for Cartography and Geodesy (BKG)<br>
     40Frankfurt, Germany<br>
     41[euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]
     42</p>
     43
     44<p>
     45<b>Acknowledgements</b><br>
     46BNC's Help Contents has been proofread by Thomas Yan, University of New South Wales, Australia.<br>
     47Scott Glazier, OmniSTAR Australia has been helpful in finding BNC's bugs.<br>
     48James Perlt, BKG, helped fixing bugs and redesigned BNC's main window.<br>
     49Andre Hauschild, German Space Operations Center, DLR, revised the RTCM Version 2 decoder.<br>
     50Zdenek Lukes, Czech Technical University Prague, Department of Geodesy, extended the RTCM Version 2 decoder to handle message types 3, 20, 21, and 22 and added loss of lock indicator.<br>
     51Jan Dousa, Geodetic Observatory Pecny, Czech Republic, provided a tool for drawing stream distribution maps and also helped with fixing bugs.<br>
     52Denis Laurichesse, Centre National d'Etudes Spatiales (CNES), suggested synchronizing observations and clock corrections to reduce high frequency noise in PPP solutions.
    3153</p>
    3254
    … …  
    23332355Once BNC has been started, many of its configuration options cannot be changed as long as it is stopped. See chapter 'Reread Configuration' for on-the-fly configuration exceptions.
    23342356</li>
    2335 
    2336 </ul>
    2337 <p><a name="authors"><h3>6. Authors</h3></p>
    2338 <p>
    2339 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 Geodesy. BNC includes the following GNU GPL software components:
    2340 <ul>
    2341 <li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen</li>
    2342 <li> RTCM 3 decoder, written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld</li>
    2343 </ul>
    2344 </p>
    2345 <p>
    2346 Georg Weber<br>
    2347 Federal Agency for Cartography and Geodesy (BKG)<br>
    2348 Frankfurt, Germany<br>
    2349 [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]
    2350 </p>
    2351 <p>
    2352 <b>Acknowledgements</b><br>
    2353 BNC's Help Contents has been proofread by Thomas Yan, University of New South Wales, Australia.<br>
    2354 Scott Glazier, OmniSTAR Australia has been helpful in finding BNC's bugs.<br>
    2355 James Perlt, BKG, helped fixing bugs and redesigned BNC's main window.<br>
    2356 Andre Hauschild, German Space Operations Center, DLR, revised the RTCM Version 2 decoder.<br>
    2357 Zdenek Lukes, Czech Technical University Prague, Department of Geodesy, extended the RTCM Version 2 decoder to handle message types 3, 20, 21, and 22 and added loss of lock indicator.<br>
    2358 Jan Dousa, Geodetic Observatory Pecny, Czech Republic, provided a tool for drawing stream distribution maps and also helped with fixing bugs.<br>
    2359 Denis Laurichesse, Centre National d'Etudes Spatiales (CNES), suggested synchronizing observations and clock corrections to reduce high frequency noise in PPP solutions.
    2360 </p>
    2361 
    2362 <p><a name="annex"><h3>7. Annex</h3></p>
    2363 <p>
    2364 7.1. <a href=#history>Revision History</a><br>
    2365 7.2. <a href=#rtcm>RTCM</a><br>
    2366 &nbsp; &nbsp; &nbsp; 7.2.1 NTRIP <a href=#ntrip1>Version 1</a><br>
    2367 &nbsp; &nbsp; &nbsp; 7.2.2 NTRIP <a href=#ntrip2>Version 2</a><br>
    2368 &nbsp; &nbsp; &nbsp; 7.2.3 RTCM <a href=#rtcm2>Version 2</a><br>
    2369 &nbsp; &nbsp; &nbsp; 7.2.4 RTCM <a href=#rtcm3>Version 3</a><br>
    2370 7.3. <a href=#config>Configuration Example</a><br>
    2371 7.4. <a href=#links>Links</a><br>
    2372 </p>
    2373 
    2374 <p><a name=history><h4>7.1 Revision History</h3></p>
     2357</ul>
     2358
     2359<p><a name="annex"><h3>6. Annex</h3></p>
     2360<p>
     23616.1. <a href=#history>Revision History</a><br>
     23626.2. <a href=#rtcm>RTCM</a><br>
     2363&nbsp; &nbsp; &nbsp; 6.2.1 NTRIP <a href=#ntrip1>Version 1</a><br>
     2364&nbsp; &nbsp; &nbsp; 6.2.2 NTRIP <a href=#ntrip2>Version 2</a><br>
     2365&nbsp; &nbsp; &nbsp; 6.2.3 RTCM <a href=#rtcm2>Version 2</a><br>
     2366&nbsp; &nbsp; &nbsp; 6.2.4 RTCM <a href=#rtcm3>Version 3</a><br>
     23676.3. <a href=#config>Configuration Example</a><br>
     23686.4. <a href=#links>Links</a><br>
     2369</p>
     2370
     2371<p><a name=history><h4>6.1 Revision History</h3></p>
    23752372<table>
    23762373<tr></tr>
    … …  
    24692466</p>
    24702467
    2471 <p><a name="rtcm"><h4>7.2. RTCM</h4></p>
     2468<p><a name="rtcm"><h4>6.2. RTCM</h4></p>
    24722469
    24732470<p>
    … …  
    24772474</p>
    24782475
    2479 <p><a name="ntrip1"><h4>7.2.1 NTRIP Version 1</h4></p>
     2476<p><a name="ntrip1"><h4>6.2.1 NTRIP Version 1</h4></p>
    24802477
    24812478<p>
    … …  
    25162513</p>
    25172514
    2518 <p><a name="ntrip2"><h4>7.2.2 NTRIP Version 2</h4></p>
     2515<p><a name="ntrip2"><h4>6.2.2 NTRIP Version 2</h4></p>
    25192516
    25202517<p>
    … …  
    25342531</p>
    25352532
    2536 <p><a name="rtcm2"><h4>7.2.3 RTCM Version 2</h4></p>
     2533<p><a name="rtcm2"><h4>6.2.3 RTCM Version 2</h4></p>
    25372534<p>
    25382535Transmitting GNSS carrier phase data can be done through RTCM Version 2 messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are:
    … …  
    25722569</ul>
    25732570
    2574 <p><a name="rtcm3"><h4>7.2.4 RTCM Version 3</h4></p>
     2571<p><a name="rtcm3"><h4>6.2.4 RTCM Version 3</h4></p>
    25752572<p>
    25762573RTCM Version 3 has been developed as a more efficient alternative to RTCM Version 2. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3 standard is intended to correct these weaknesses.
    … …  
    26462643</p>
    26472644
    2648 <p><a name="config"><h4>7.3. Configuration Example</h4></p>
     2645<p><a name="config"><h4>6.3. Configuration Example</h4></p>
    26492646<p>
    26502647The following table's left column is an example for the contents of a configuration file 'BNC.ini'. It enables the retrieval of an observations stream via NTRIP for the generation of 15 min RINEX files:
    … …  
    28072804</p>
    28082805
    2809 <p><a name="links"><h4>7.4 Links</h3></p>
     2806<p><a name="links"><h4>6.4 Links</h3></p>
    28102807<table>
    28112808<tr></tr>
Note: See TracChangeset for help on using the changeset viewer.