Changeset 7482 in ntrip for trunk

Timestamp:

Oct 5, 2015, 10:02:01 AM (9 years ago)

Author:

weber

Message:

Typos corrected

File:

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

trunk/BNC/src/bnchelp.html

@@ -14 +14 @@
 
 <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.8.4 or any later version are installed. Please ensure that you always use the latest precompiled 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 PPP results 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.
+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.8.4 or any later version are installed. Please ensure that you always use the latest precompiled 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 PPP results using Google Map (GM) or OpenStreetMap (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>
@@ -179 +179 @@
 <li>Carry out real-time Precise Point Positioning to determine GNSS rover positions;</li>
 <li>Enable multi-station Precise Point Positioning for simultaneous processing of observations from a whole network of receivers;</li>
-<li>Plot positions derived via PPP from RTCM streams or RINEX files on maps from Google Map or Open StreetMap;</li>
+<li>Plot positions derived via PPP from RTCM streams or RINEX files on maps from Google Map or OpenStreetMap;</li>
 <li>Simultaneously process several Broadcast Correction streams to produce, encode and upload combined Broadcast Corrections;</li>
 <li>Read GNSS orbits and clocks in a plain ASCII format from an IP port. They can be produced by a real-time GNSS engine such as RTNET and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. BNC will then</li>
@@ -751 +751 @@
 </p>
 <p>
-The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various Ntrip Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received. The 'SSL Error' recorded in the 'Log' tab is caused by the fact that observation stream downloads from IGS and MGEX Broadcasters initiate the download of RINEX skeleton files from a HTTPS (TLS/SSL) website and BNC has been configured in this example to ignore SSL errors as shown in the preceding 'Network' panel sreenshot.
+The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various Ntrip Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received. The 'SSL Error' recorded in the 'Log' tab is caused by the fact that observation stream downloads from IGS and MGEX Broadcasters initiate the download of RINEX skeleton files from a HTTPS (TLS/SSL) website and BNC has been configured in this example to ignore SSL errors as shown in the preceding 'Network' panel screenshot.
 </p>
 
@@ -2547 +2547 @@
 </pre>
 <p>
-The default value for 'NMEA file' is an empty option field, meaning that BNC will not saved NMEA messages into a file.
+The default value for 'NMEA file' is an empty option field, meaning that BNC will not save NMEA messages into a file.
 </p>
 <p>
@@ -2663 +2663 @@
 <p><a name="pppnehsigma"><h4>3.13.2.2 Sigma North/East/Up - mandatory</h4></p>
 <p>
-Enter a sigmas in meters for the initial coordinate components. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with well known position - so-called Quick-Start mode.
+Enter a sigmas in meters for the initial coordinate components. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with well-known position - so-called Quick-Start mode.
 </p>
 
@@ -2833 +2833 @@
 <p><a name="ppptrackmap"><h4>3.13.4.3 Track Map - optional</h4></p>
 <p>
-You may like to track your rover position using Google Maps or Open StreetMap as a background map. Track maps can be produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files.
+You may like to track your rover position using Google Maps or OpenStreetMap as a background map. Track maps can be produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files.
 </p>
 <p>
@@ -2981 +2981 @@
 <p><a name="combiGLO"><h4>3.14.1.5 Use GLONASS - optional</h4></p>
 <p>
-You may tick the 'Use GLONASS' option in case you want to produce an GPS plus GLONASS combination and both systems are supported by the Broadcast Correction streams participating in the combination.
+You may tick the 'Use GLONASS' option in case you want to produce a GPS plus GLONASS combination and both systems are supported by the Broadcast Correction streams participating in the combination.
 </p>
 
@@ -3981 +3981 @@
 [Add] Considering that yaw angle restricted to -180 to +180 deg<br>
 [Mod] Read local RINEX skeleton files<br>
-[Add] Update intevall for VTEC in RTNET stream format<br>
+[Add] Update interval for VTEC in RTNET stream format<br>
 [Bug] SBAS IODN<br>
 [Bug] Galileo week number<br>
@@ -3989 +3989 @@
 [Mod] Renaming BDS first frequency from '1' to '2'<br>
 [Add] RINEX QC, receiver/antenna information editable<br>
-[Add] Switch to port 443 for skeleton file donwload from https website<br>
+[Add] Switch to port 443 for skeleton file download from https website<br>
 [Mod] Default observation types for RINEX v3 files<br>
 [Bug] RTCM v2 decoder<br>
@@ -4042 +4042 @@
 </p>
 <p>
-Source-table records of type NET contain the following data fields: 'identifiey', 'operator', 'authentication', 'fee', 'web-net', 'web-str', 'web-reg', 'misc'.
+Source-table records of type NET contain the following data fields: 'identifier', 'operator', 'authentication', 'fee', 'web-net', 'web-str', 'web-reg', 'misc'.
 </p>
 <p>
@@ -4396 +4396 @@
 <li>File 'PPPGoogleMaps.bnc'<br>
 The purpose of this configuration is to track BNC's point positioning
-solution using Google Maps or Open StreetMap as background. BNC reads a
+solution using Google Maps or OpenStreetMap as background. BNC reads a
 RINEX Observation file and a RINEX Navigation file to carry out a
 'Standard Point Positioning' solution in post-processing mode. Although