Changeset 2533 in ntrip for trunk/BNC/bnchelp.html


Ignore:
Timestamp:
Aug 4, 2010, 9:06:36 AM (14 years ago)
Author:
weber
Message:

New internal format for saving raw data, new version 2.3

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r2516 r2533  
    286286<p><a name="rawout"><h4>3.3.5 Raw Output File - optional</h4></p>
    287287<p>
    288 BNC can save all data coming in through various streams in the received order and format together in one single file. This is of importance i.e. when using the PPP option in offline mode where the contents of different streams carrying observations, orbit/clock correctors, and broadcast ephemeris are to be read from one file.
     288BNC can save all data coming in through various streams in the received order and format together in one single file. This is of importance i.e. when using the PPP option in offline mode where the contents of different streams carrying observations, orbit/clock correctors, and broadcast ephemeris are to be read from one file. Data will be saved in blocks in the received format seperated by ASCII records like (example):
     289<pre>
     2902010-08-03T18:05:28 RTCM3EPH RTCM_3 67
     291</pre>
     292This example block header tells you that 67 bytes are saved in the data block following this record. The information in this block is encoded in RTCM Version 3.x format, comes from Mountpoint RTCM3EPH and was received at 18:05:29 UTC on 2010-08-03. BNC adds its own time stamps because a complete time reference may not be provided for all incoming observations and epochs.
    289293</p>
    290294<p>
     
    10651069
    10661070<p>
    1067 bnc.exe --conf c:\temp\BNC.ppp --file c:\temp\FFMJ1 --date 2010-03-27 --time 06:58:00 --format RTCM_3
     1071bnc.exe --conf c:\temp\BNC.ppp --file c:\temp\FFMJ1 --format RTCM_3
    10681072</p>
    10691073
     
    14241428<p><a name="post"><h4>3.15.2 Offline Mode - optional</h4></p>
    14251429<p>
    1426 Although BNC is primarily a real-time online tool, it can be run in offline mode to read data from a file for post-processing purposes. Enter the following four command line options for that:
    1427 </p>
    1428 <p>
    1429 <ul>
    1430 <li>'--file &lt;<u>inputFileName</u>&gt;' to enter the full path to an input file containing data in RTCM Version 2.x, or Version 3.x, or RTIGS/SOC format.</li>
     1430Although BNC is primarily a real-time online tool, it can be run in offline mode to read data from a previously saved file for post-processing purposes. Enter the following command line options for that:
     1431</p>
     1432<p>
     1433<ul>
     1434<li>'--file &lt;<u>inputFileName</u>&gt;' to enter the full path to an input file containing data previously saved by BNC.</li>
    14311435<li>'--format &lt;<u>format</u>&gt;' to enter one of the file format describing strings 'RTCM_2', 'RTCM_3' or 'RTIGS'.</li>
    1432 <li>'--date YYYY-MM-DD' to enter a date for the first epoch.</li>
    1433 <li>'--time HH:MM:SS' to enter a time for the first epoch.</li>
    14341436</ul>
    14351437<p>
    14361438Example:<br><br>
    1437 ./bnc --file FFMJ.dat --format RTCM_3 --date 2008-10-27 --time 23:12:56
    1438 </p>
    1439 <p>
    1440 Note that it is necessary to define a date and time for the first epoch because RTCM streams do not contain complete time stamps as needed i.e. for RINEX files or for PPP in post-processing mode. Note further that when running BNC in offline mode, it will use options for file saving, interval, sampling etc. from its configuration file.
     1439./bnc --file FFMJ.dat --format RTCM_3
     1440</p>
     1441<p>
     1442Note that when running BNC in offline mode, it will use options for file saving, interval, sampling, PPP etc. from its configuration file.
    14411443</p>
    14421444
     
    16011603
    16021604<tr>
    1603 <td>June 2010 &nbsp;</td><td>Version 2.1 &nbsp;</td>
     1605<td>Jun 2010 &nbsp;</td><td>Version 2.1 &nbsp;</td>
    16041606<td>[Bug] SSR GLONASS message generation<br> [Add] PPP in post-processing mode<br> [Mod] Update of SSR messages following draft dated 2010-04-12<br> [Mod] Generating error message when observation epoch is wrong</td>
    16051607</tr>
    16061608
    16071609<tr>
    1608 <td>July 2010 &nbsp;</td><td>Version 2.2 &nbsp;</td>
     1610<td>Jul 2010 &nbsp;</td><td>Version 2.2 &nbsp;</td>
    16091611<td>[Bug] GLONASS ephemeris time</td>
    16101612</tr>
     1613
     1614<tr>
     1615<td>Aug 2010 &nbsp;</td><td>Version 2.3 &nbsp;</td>
     1616<td>[Mod] Internal format for saving raw streams</td>
     1617</tr>
     1618
    16111619
    16121620</table>
Note: See TracChangeset for help on using the changeset viewer.