Changeset 5582 in ntrip

Timestamp:

Nov 27, 2013, 11:03:48 AM (11 years ago)

Author:

weber

Message:

Documentation completed

File:

• trunk/BNC/src/bnchelp.html (modified) (10 diffs)

trunk/BNC/src/bnchelp.html

@@ -13 +13 @@
 
 <p>
-BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive <u>http://software.rtcm-ntrip.org/svn/trunk/BNC.</u> Binaries for BNC are available for Windows, Linux, and Mac OS X systems. We used the MinGW Version 4.4.0 compiler to create the Windows binaries. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.7.3 or any later version are installed. Please ensure that you allways use the latest version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u>. Note that static and shared builds of BNC are made available. A <u>static</u> build would be sufficient in case you don't want BNC to trace positions using Google Map (GM) or Open StreetMap (OSM). However, GM/OSM usage requires the QtWebKit library which can only be part of BNC builds from <u>shared</u> libraries. Using a shared libray BNC build requires that you first install your own shared Qt library. The 'README.txt' file which comes with the BNC source code describes how to install Qt on Windows, Linux and Mac systems.
+BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive <u>http://software.rtcm-ntrip.org/svn/trunk/BNC.</u> Binaries for BNC are available for Windows, Linux, and Mac OS X systems. We used the MinGW Version 4.4.0 compiler to create the Windows binaries. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.7.3 or any later version are installed. Please ensure that you always use the latest version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u>. Note that static and shared builds of BNC are made available. A <u>static</u> build would be sufficient in case you don't want BNC to trace positions using Google Map (GM) or Open StreetMap (OSM). However, GM/OSM usage requires the QtWebKit library which can only be part of BNC builds from <u>shared</u> libraries. Using a shared library BNC build requires that you first install your own shared Qt library. The 'README.txt' file which comes with the BNC source code describes how to install Qt on Windows, Linux and Mac systems.
 </p>
 <p>
@@ -748 +748 @@
 <p><a name="reqcgnss"><h4>3.6.2 Sky Plots - mandatory if 'Action' is set to 'Analyze'</h4></p>
 
-<p>Once the 'Analyze' action is selected, you have to specify the GNSS system(s) whoes observations you want to analyze for multipath and signal-to-noise ratio sky plots. Possible options are 'ALL', 'GPS', 'GLONASS', and 'Galileo'. Default is 'ALL', meaning that observations from all GNSS will be analyzed.
+<p>Once the 'Analyze' action is selected, you have to specify the GNSS system(s) whose observations you want to analyze for multipath and signal-to-noise ratio sky plots. Possible options are 'ALL', 'GPS', 'GLONASS', and 'Galileo'. Default is 'ALL', meaning that observations from all GNSS will be analyzed.
 </p>
 
@@ -866 +866 @@
 
 <p>
-The following is a list of available keynames for '<u>R</u>INEX <u>E</u>diting & <u>QC</u>' (short: REQC, pronounced 'rek') options and their meaning, cf. section 'Configuration Examples':
+The following is a list of available key names for '<u>R</u>INEX <u>E</u>diting & <u>QC</u>' (short: REQC, pronounced 'rek') options and their meaning, cf. section 'Configuration Examples':
 </p>
 
@@ -880 +880 @@
 <tr><td>reqcOutLogFile</td><td>Logfile</td></tr>
 <tr><td>reqcPlotDir</td><td>Plot file directory</td></tr>
-<tr><td>reqcSkyPlotSystem</td><td>GNSS system spedificaion</td></tr>
+<tr><td>reqcSkyPlotSystem</td><td>GNSS system specification</td></tr>
 <tr><td>reqcRnxVersion</td><td>RINEX version of emerging new file</td></tr>
 <tr><td>reqcSampling</td><td>Sampling interval of emerging new RINEX file</td></tr>
@@ -1690 +1690 @@
 <p>When in 'Post-Processing' mode
 <ul>
-<li>specifying a RINEX Observation, a RINEX Navigation and a Broadcast Corrections file leads to a PPP solution.</li>
-<li>specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Corrections file leads to a SPP solution.</li>
+<li>Specifying a RINEX Observation, a RINEX Navigation and a Broadcast Corrections file leads to a PPP solution.</li>
+<li>Specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Corrections file leads to a SPP solution.</li>
 </ul>
 </p>
@@ -2151 +2151 @@
 </p>
 <p>
-From a theoretical point of view this kind of approximation leads to inconsistencies between orbits and clocks and is therefore not allowed. However, it has been proved that resulting errors in Precise Point Positioning are on millimeter level for horizontal components and below the one centimeter for height components. The Australian GDA94 transformation with its comparatively large scale parameter is an exception in this as descrepancies may reach up to two centimeters there.
+From a theoretical point of view this kind of approximation leads to inconsistencies between orbits and clocks and is therefore not allowed. However, it has been proved that resulting errors in Precise Point Positioning are on millimeter level for horizontal components and below the one centimeter for height components. The Australian GDA94 transformation with its comparatively large scale parameter is an exception in this as discrepancies may reach up to two centimeters there.
 </p>
 
@@ -2182 +2182 @@
 
 <p>
-<u>NAD83:</u> Formulas for the transformation 'ITRF2008-&gt;NAD83' are taken from from 'Chris Pearson, Richard Snay 2013: Introducing HTDP 3.1 to transform coordinates across time and spatial reference frames', GPS Solutions, January 2013, Volume 17, Issue 1, pp 1-15.
+<u>NAD83:</u> Formulas for the transformation 'ITRF2008-&gt;NAD83' are taken from 'Chris Pearson, Richard Snay 2013: Introducing HTDP 3.1 to transform coordinates across time and spatial reference frames', GPS Solutions, January 2013, Volume 17, Issue 1, pp 1-15.
 </p>
 <p>
@@ -2880 +2880 @@
 <tr>
 <td>Jul 2013 &nbsp;</td><td>Version 2.9 &nbsp;</td>
-<td>[Add] Started work on new version in Mar 2013<br>[Bug] SSR stream upload buffering disabled<br>[Mod] Format for feeding a connected GNSS engine<br>[Mod] RTNET format for receiving data from a connected GNSS engine<br>[Add] Include Galileo in SPP<br>[Add] RINEX QC multipath an SNR skyplots for GLONASS and Galileo<br>[Add] Bias estimation for GLONASS clocks in PPP<br>[Add] Trace positions on GM or OSM maps<br>[Add] Version 2.9 published</td>
+<td>[Add] Started work on new version in Mar 2013<br>[Bug] SSR stream upload buffering disabled<br>[Mod] Format for feeding a connected GNSS engine<br>[Mod] RTNET format for receiving data from a connected GNSS engine<br>[Add] Include Galileo in SPP<br>[Add] RINEX QC multipath an SNR sky plots for GLONASS and Galileo<br>[Add] Bias estimation for GLONASS clocks in PPP<br>[Add] Trace positions on GM or OSM maps<br>[Add] Version 2.9 published</td>
 </tr>
 
@@ -2953 +2953 @@
 </ul>
 
-<p>NTRIP Version 2 allows to either communicate in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas Version 1 is limited to TCP/IP only. It furthermore allows using the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure NTRIP communication over the Internet.
+<p>NTRIP Version 2 allows to either communicating in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas Version 1 is limited to TCP/IP only. It furthermore allows using the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure NTRIP communication over the Internet.
 </p>
 
@@ -3360 +3360 @@
 <tr><td>reqcRunBy=</td><td>Reqc: Operators name</td></tr>
 <tr><td>reqcSampling=</td><td>Reqc: RINEX sampling</td></tr>
-<tr><td>reqcSkyPlotSystem=</td><td>Reqc: GNSS system spedificaion</td></tr>
+<tr><td>reqcSkyPlotSystem=</td><td>Reqc: GNSS system specification</td></tr>
 <tr><td>reqcStartDateTime=</td><td>Reqc: Start time</td></tr>