Changeset 7683 in ntrip for trunk

Timestamp:

Jan 12, 2016, 3:38:14 PM (11 years ago)

Author:

weber

Message:

Documentation completed

File:

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

trunk/BNC/src/bnchelp.html

@@ -707 +707 @@
 
 <li>File 'RinexObs.bnc'<br>
-The purpose of this configuration is showing how to convert RTCM streams to 
+Purpose: Convert RTCM streams to 
 RINEX Observation files. The configuration pulls streams from Ntrip 
 Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3 
@@ -715 +715 @@
 
 <li>File 'RinexEph.bnc'<br>
-The purpose of this configuration is showing how to convert a RTCM stream 
-carrying navigation messages to a RINEX Navigation file. The configuration 
+Purpose: Convert a RTCM stream 
+carrying navigation messages to RINEX Navigation files. The configuration
 pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the 
-real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation 
+real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation 
 files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time 
 Broadcast Ephemeris resources. 
@@ -724 +724 @@
 
 <li>File 'BrdcCorr.bnc'<br>
-The purpose of this configuration is to save Broadcast Corrections from RTCM 
+Purpose: Save Broadcast Corrections from RTCM 
 SSR messages in a plain ASCII format as hourly files. See 
 http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF 
@@ -731 +731 @@
 
 <li>File 'RinexConcat.bnc'<br>
-The purpose of this configuration is to concatenate RINEX Version 3 files to 
-produce a concatenated file and edit the marker name in the file header. The 
+Purpose: Concatenate several RINEX Version 3 files to 
+produce one concatenated file and edit the marker name in the file header. The 
 sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the 
 documentation for examples on how to call BNC from command line in 'no window' 
@@ -739 +739 @@
 
 <li>File 'RinexQC.bnc'<br>
-The purpose of this configuration is to check the quality of a RINEX Version 3 
-file through a multipath analysis. Results are saved on disk in terms of a 
+Purpose: Check the quality of a RINEX Version 3 
+file by means of a multipath analysis. Results are saved on disk in terms of a 
 plot in PNG format. See section 'RINEX Editing & QC' in the documentation for 
 examples on how to call BNC from command line in 'no window' mode for RINEX 
@@ -747 +747 @@
 
 <li>File 'RTK.bnc'<br>
-The purpose of this configuration is to feed a serial connected receiver with 
+Purpose: Feed a serial connected receiver with 
 observations from a reference station for conventional RTK. The stream is 
 scanned for RTCM messages. Message type numbers and latencies of incoming 
@@ -754 +754 @@
 
 <li>File 'FeedEngine.bnc'<br>
-The purpose of this configuration is to feed a real-time GNSS engine with 
+Purpose: Feed a real-time GNSS engine with 
 observations from remote reference stations. The configuration pulls a single 
 stream from an Ntrip Broadcaster. It would of course be possible to pull 
@@ -763 +763 @@
 
 <li>File 'PPP.bnc'<br>
-The purpose of this configuration is Precise Point Positioning from 
+Purpose: Precise Point Positioning from 
 observations of a rover receiver. The configuration reads RTCM Version 3 
 observations, a Broadcast Ephemeris stream and a stream with Broadcast 
@@ -770 +770 @@
 
 <li>File 'PPPNet.bnc'<br>
-The purpose of this configuration is to demonstrate simultaneous Precise 
-Point Positioning for several rovers or several receivers from a network of 
+Purpose: Precise 
+Point Positioning for several rovers or receivers from a network of 
 reference stations in one BNC job. The possible maximum number of PPP solutions 
 per job depends on the processing power of the hosting computer. This example 
@@ -780 +780 @@
 
 <li>File 'PPPQuickStart.bnc'<br>
-The purpose of this configuration is Precise Point Positioning in Quick-Start 
+Purpose: Precise Point Positioning in Quick-Start 
 mode from observations of a static receiver with precisely known position. The 
 configuration reads RTCM Version 3 observations, Broadcast Corrections and a 
@@ -789 +789 @@
 
 <li>File 'PPPPostProc.bnc'<br>
-The purpose of this configuration is Precise Point Positioning in post 
+Purpose: Precise Point Positioning in post 
 processing mode. BNC reads RINEX Version 3 Observation and 3 Navigation files 
 and a Broadcast Correction file. PPP processing options are set to support 
@@ -798 +798 @@
 
 <li>File 'PPPGoogleMaps.bnc'<br>
-The purpose of this configuration is to track BNC's point positioning
+Purpose: Track BNC's point positioning
 solution using Google Maps or OpenStreetMap as background. BNC reads a
 RINEX Observation file and a RINEX Navigation file to carry out a
@@ -809 +809 @@
 
 <li>File 'SPPQuickStartGal.bnc'<br>
-The purpose of this configuration is Single Point Positioning in Quick-Start 
-mode from observations of a static receiver with precisely known position. The 
-configuration uses GPS, GLONASS and Galileo observations and a Broadcast 
+Purpose: Single Point Positioning in Quick-Start mode from observations of a static 
+receiver with precisely known position.
+The configuration uses GPS, GLONASS and Galileo observations and a Broadcast 
 Ephemeris stream. 
 </li><br>
 
 <li>File 'SaveSp3.bnc'<br>
-The purpose of this configuration is to produce SP3 files from a Broadcast 
+Purpose: Produces SP3 files from a Broadcast 
 Ephemeris stream and a Broadcast Correction stream. The Broadcast Correction 
 stream is formally introduced in BNC's 'Combine Corrections' table. Note that 
@@ -824 +824 @@
 
 <li>File 'Sp3ETRF2000PPP.bnc'<br>
-The purpose of this configuration is to produce SP3 files from a Broadcast 
+Purpose: Produce SP3 files from a Broadcast 
 Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The 
 Broadcast Correction stream is formally introduced in BNC's 'Combine 
-Corrections' table. This leads to a SP3 file containing orbits referred also 
+Corrections' table. The configuration leads to a SP3 file containing orbits referred also 
 to ETRF2000. Pulling in addition observations from a reference station at 
 precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution 
-with ETRF2000 reference coordinates. 
+with a known ETRF2000 reference coordinate. 
 </li><br>
 
 <li>File 'Upload.bnc'<br>
-The purpose of this configuration is to upload orbits and clocks from a 
+Purpose: Upload orbits and clocks from a 
 real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads 
 precise orbits and clocks in RTNET format. It also reads a stream carrying 
@@ -845 +845 @@
 
 <li>File 'Combi.bnc'<br>
-The purpose of this configuration is to pull several streams carrying Broadcast 
+Purpose: Pull several streams carrying Broadcast 
 Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to 
 produce a combined Broadcast Correction stream. BNC encodes the combination 
@@ -855 +855 @@
 
 <li>File 'CombiPPP.bnc'<br>
-This configuration equals the 'Combi.bnc' configuration. However, the combined 
+Purpose: This configuration equals the 'Combi.bnc' configuration. However, the combined 
 Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions 
 based on observations from a static reference station with known precise 
@@ -863 +863 @@
 
 <li>File 'UploadEph.bnc'<br>
-The purpose of this configuration is to pull a number of streams from reference 
+Purpose: Pull a number of streams from reference 
 stations to get hold of contained Broadcast Ephemeris messages. These are 
 encoded then in a RTCM Version 3 stream with the sole purpose of providing 
@@ -870 +870 @@
 
 <li>File 'CompareSp3.bnc'<br>
-The purpose of this configuration is to compare two SP3 files to calculate 
+Purpose: Compare two SP3 files to calculate 
 RMS values from orbit and clock differences. GPS satellite G05 and GLONASS 
 satellite R18 are excluded from this comparison. Comparison results are saved 
@@ -877 +877 @@
 
 <li>File 'Empty.bnc'<br>
-The purpose of this example is to provide an empty configuration file for BNC
-which only contains default settings.
+Purpose: Provide an empty example configuration file for
+BNC which only contains the default settings.
 </li>