Changeset 7686 in ntrip for trunk/BNC/Example_Configs


Ignore:
Timestamp:
Jan 14, 2016, 3:25:07 PM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/Example_Configs/00_Readme.txt

    r7590 r7686  
    7373exceptions because they require an input stream from a connected network engine.
    7474
    75 1.  File 'RinexObs.bnc'
    76 The purpose of this configuration is showing how to convert RTCM streams to
    77 RINEX Observation files. The configuration pulls streams from Ntrip
    78 Broadcasters using Ntrip version 1 to generate 15min 1Hz RINEX Version 3
    79 Observation files. See http://igs.bkg.bund.de/ntrip/observations for
    80 observation stream resources.
    81 
    82 2.  File 'RinexEph.bnc'
    83 The purpose of this configuration is showing how to convert a RTCM stream
    84 carrying navigation messages to a RINEX Navigation files. The configuration
    85 pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the
    86 real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation
    87 files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time
    88 Broadcast Ephemeris resources.
    89 
    90 3.  File 'BrdcCorr.bnc'
    91 The purpose of this configuration is to save Broadcast Corrections from
    92 RTCM SSR messages in a plain ASCII format as hourly files. See
    93 http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF
    94 orbit/clock products.
    95 
    96 4.  File 'RinexConcat.bnc'
    97 The purpose of this configuration is to concatenate RINEX Version 3 files
    98 to produce a concatenated file and edit the marker name in the file header. The
    99 sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the
    100 documentation for examples on how to call BNC from command line in 'no window'
    101 mode for RINEX file editing, concatenation and quality checks.
    102 
    103 5.  File 'RinexQC.bnc'
    104 The purpose of this configuration is to check the quality of a RINEX
    105 Version 3 file through a multipath analysis. The results are saved on disk in
    106 terms of a plot in PNG format. See section 'RINEX Editing & QC' in the
    107 documentation for examples on how to call BNC from command line in 'no window'
    108 mode for RINEX file editing, concatenation and quality checks.
    109 
    110 6.  File 'RTK.bnc'
    111 The purpose of this configuration is to feed a serial connected receiver
    112 with observations from a reference station for conventional RTK. The stream is
    113 scanned for RTCM messages. Message type numbers and latencies of incoming
    114 observation are reported in BNC's logfile.
    115 
    116 7.  File 'FeedEngine.bnc'
    117 The purpose of this configuration is to feed a real-time GNSS engine with
    118 observations from a remote reference stations. The configuration pulls a single
    119 stream from an Ntrip Broadcasters. It would of course be possible to pull
    120 several streams from different casters. Incoming observations are decoded,
    121 synchronized and output through a local IP port and saved into a file. Failure
    122 and recovery thresholds are specified to inform about outages.
    123 
    124 8.  File 'PPP.bnc'
    125 The purpose of this configuration is Precise Point Positioning from
    126 observations of a rover receiver. The configuration reads RTCM Version 3
    127 observations, a Broadcast Ephemeris stream and a stream with Broadcast
    128 Corrections. Positions are saved in the logfile.
    129 
    130 9.  File 'PPPNet.bnc'
    131 The purpose of this configuration is to demonstrate simultaneous Precise
    132 Point Positioning for several rovers or several receivers from a network of
    133 reference stations in one BNC job. The possible maximum number of PPP solutions
    134 per job depends on the processing power of the hosting computer. This example
    135 configuration reads two RTCM Version 3 observation streams, a Broadcast
    136 Ephemeris stream and a stream with Broadcast Corrections. PPP Results for the
    137 two stations are saved in PPP logfiles.
     751. File 'RinexObs.bnc'
     76Purpose: Convert RTCM streams to RINEX Observation files. The configuration
     77pulls streams from Ntrip Broadcasters using Ntrip Version 1 to generate 15min
     781Hz RINEX Version 3 Observation files. See
     79http://igs.bkg.bund.de/ntrip/observations for observation stream resources.
     80
     812. File 'RinexEph.bnc'
     82Purpose: Convert a RTCM stream with navigation messages to RINEX Navigation
     83files. The configuration pulls a RTCM Version 3 stream with Broadcast Ephemeris
     84coming from the real-time EUREF and IGS networks and saves hourly RINEX Version
     853 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further
     86real-time Broadcast Ephemeris resources.
     87
     883. File 'BrdcCorr.bnc'
     89Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain
     90ASCII files. See http://igs.bkg.bund.de/ntrip/orbits for various real-time IGS
     91or EUREF orbit/clock correction products.
     92
     934. File 'RinexConcat.bnc'
     94Purpose: Concatenate several RINEX Version 3 files to produce one compiled file
     95and edit the marker name in the file header. The sampling interval is set to 30
     96seconds. See section 'RINEX Editing & QC' in the documentation for examples on
     97how to call BNC from command line in 'no window' mode for RINEX file editing,
     98concatenation and quality check.
     99
     1005. File 'RinexQC.bnc'
     101Purpose: Check the quality of a RINEX Version 3 file by means of a multipath
     102analysis. Results are saved on disk in terms of a plot in PNG format. See
     103section 'RINEX Editing & QC' in the documentation for examples on how to call
     104BNC from command line in 'no window' mode for RINEX file editing, concatenation
     105and quality check.
     106
     1076. File 'RTK.bnc'
     108Purpose: Feed a serial connected receiver with observations from a nearby
     109reference station for conventional RTK. The stream is scanned for RTCM
     110messages. Message type numbers and latencies of incoming observations are
     111reported in BNC's logfile.
     112
     1137. File 'FeedEngine.bnc'
     114Purpose: Feed a real-time GNSS engine with observations from remote reference
     115stations. The configuration pulls a single stream from an Ntrip Broadcaster.
     116You could also pull several streams from different casters. Incoming
     117observations are decoded, synchronized, output through a local IP port and also
     118saved into a file. Failure and recovery thresholds are specified to inform
     119about outages.
     120
     1218. File 'PPP.bnc'
     122Purpose: Precise Point Positioning from observations of a rover receiver. The
     123configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
     124and a stream with Broadcast Corrections. Positions are saved in the logfile.
     125
     1269. File 'PPPNet.bnc'
     127Purpose: Precise Point Positioning for several rovers or receivers from an
     128entire network of reference stations in one BNC job. The possible maximum
     129number of PPP solutions per job depends on the processing power of the hosting
     130computer. This example configuration reads two RTCM Version 3 observation
     131streams, a Broadcast Ephemeris stream and a stream with Broadcast Corrections.
     132PPP Results for the two stations are saved in PPP logfiles.
    138133
    13913410. File 'PPPQuickStart.bnc'
    140 The purpose of this configuration is Precise Point Positioning in
    141 Quick-Start mode from observations of a static receiver with precisely known
    142 position. The configuration reads RTCM Version 3 observations, Broadcast
    143 Corrections and a Broadcast Ephemeris stream. Positions are saved in NMEA
    144 format on disc. Positions are also output through IP port for real-time
    145 visualization with tools like RTKPLOT. Positions are also saved in the logfile.
     135Purpose: Precise Point Positioning in Quick-Start mode from observations of a
     136static receiver with precisely known position. The configuration reads RTCM
     137Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream.
     138Positions are saved in NMEA format on disc. They are also output through IP
     139port for real-time visualization with tools like RTKPLOT. Positions are saved
     140in the logfile.
    146141
    14714211. File 'PPPPostProc.bnc'
    148 The purpose of this configuration is Precise Point Positioning in Post
    149 Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation
    150 files and a Broadcast Corrections file. PPP processing options are set to
    151 support the Quick-Start mode. The output is saved in a specific Post Processing
    152 logfile and contains the coordinates derived over time following the
    153 implemented PPP filter algorithm.
     143Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX
     144Version 3 Observation and 3 Navigation files and a Broadcast Correction file.
     145PPP processing options are set to support the Quick-Start mode. The output is
     146saved in a specific post processing logfile and contains coordinates derived
     147over time following the implemented PPP filter algorithm.
    154148
    15514912. File 'PPPGoogleMaps.bnc'
    156 The purpose of this configuration is to track BNC's point positioning
    157 solution using Google Maps or OpenStreetMap as background. BNC reads a RINEX
    158 Observation file and a RINEX Navigation file to carry out a 'Standard Point
    159 Positioning' solution in post-processing mode. Although this is not a real-time
    160 application it requires the BNC host to be connected to the Internet. Specify a
    161 computation speed, then hit button 'Open Map' to open the track map, then hit
    162 'Start' to visualize receiver positions on top of GM/OSM maps.
     150Purpose: Track BNC's point positioning solutions using Google Maps or
     151OpenStreetMap as background. BNC reads a RINEX Observation file and a RINEX
     152Navigation file to carry out a 'Standard Point Positioning' solution in post
     153processing mode. Although this is not a real-time application it requires the
     154BNC host to be connected to the Internet. Specify a computation speed, then hit
     155button 'Open Map' to open the track map, then hit 'Start' to visualize receiver
     156positions on top of GM/OSM maps.
    163157
    16415813. File 'SPPQuickStartGal.bnc'
    165 The purpose of this configuration is Single Point Positioning in
    166 Quick-Start mode from observations of a static receiver with precisely known
    167 position. The configuration uses GPS, GLONASS and Galileo observations and a
    168 Broadcast Ephemeris stream.
     159Purpose: Single Point Positioning in Quick-Start mode from observations of a
     160static receiver with quite precisely known position. The configuration uses
     161GPS, GLONASS and Galileo observations and a Broadcast Ephemeris stream.
    169162
    17016314. File 'SaveSp3.bnc'
    171 The purpose of this configuration is to produce SP3 files from a Broadcast
    172 Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections
    173 stream is formally introduced in BNC's 'Combine Corrections' table. Note that
    174 producing SP3 requires an ANTEX file because SP3 file contents should be
    175 referred to CoM.
     164Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast
     165Correction stream. The Broadcast Correction stream is formally introduced in
     166BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX
     167file because SP3 file content should be referred to CoM.
    176168
    17716915. File 'Sp3ETRF2000PPP.bnc'
    178 The purpose of this configuration is to produce SP3 files from a Broadcast
    179 Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The
    180 Broadcast Corrections stream is formally introduced in BNC's 'Combine
    181 Corrections' table. This leads to an SP3 file containing orbits referred also
    182 to ETRF2000. Pulling in addition observations from a reference station at
    183 precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution
    184 with ETRF2000 reference coordinates.
     170Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream
     171carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is
     172formally introduced in BNC's 'Combine Corrections' table. The configuration
     173leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in
     174addition observations from a reference station at precisely known ETRF2000
     175position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000
     176reference coordinate.
    185177
    18617816. File 'Upload.bnc'
    187 The purpose of this configuration is to upload orbits and clocks from a
    188 real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads
    189 precise orbits and clocks in RTNET format. It also reads a stream carrying
    190 Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast
    191 Corrections and encodes them in RTCM Version 3 SSR messages to upload them to
    192 an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satellite
    193 Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format
    194 and clocks in Clock RINEX format.
     179Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip
     180Broadcaster. For that the configuration reads precise orbits and clocks in
     181RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts
     182the orbits and clocks into Broadcast Corrections and encodes them to RTCM
     183Version 3 SSR messages to finally upload them to an Ntrip Broadcaster. The
     184Broadcast Correction stream is referred to satellite Antenna Phase Center (APC)
     185and reference system IGS08. Orbits are saved on disk in SP3 format and clocks
     186are saved in Clock RINEX format.
    195187
    19618817. File 'Combi.bnc'
    197 The purpose of this configuration is to pull several streams carrying
    198 Broadcast Corrections and a Broadcast Ephemeris stream from an Ntrip
    199 Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the
    200 combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip
    201 Broadcaster. The Broadcast Corrections stream is not referred to satellite
    202 Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format
    203 and clocks in Clock RINEX format.
     189Purpose: Pull several streams carrying Broadcast Corrections and a Broadcast
     190Ephemeris from an Ntrip Broadcaster to produce a combined Broadcast Correction
     191stream. BNC encodes the combination product in RTCM Version 3 SSR messages and
     192uploads that to an Ntrip Broadcaster. The Broadcast Correction stream is
     193referred to satellite Antenna Phase Center (APC) and not to satellite Center of
     194Mass (CoM). Its reference system is IGS08. Orbits are saved in SP3 format
     195(referred to CoM) and clocks in Clock RINEX format.
    204196
    20519718. File 'CombiPPP.bnc'
    206 This configuration equals the 'Combi.bnc' configuration. However, the
     198Purpose: This configuration equals the 'Combi.bnc' configuration. However, the
    207199combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
    208200solutions based on observations from a static reference station with known
    … …  
    211203
    21220419. File 'UploadEph.bnc'
    213 The purpose of this configuration is to pull a number of streams from
    214 reference stations to get hold of contained Broadcast Ephemeris messages. These
    215 are encoded then in a RTCM Version 3 stream which only provides Broadcast
    216 Ephemeris with an update rate of 5 seconds.
     205Purpose: Pull a number of streams from reference stations to get hold of
     206contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3
     207format and uploaded for the purpose of providing a Broadcast Ephemeris stream
     208with an update rate of 5 seconds.
    217209
    21821020. File 'CompareSp3.bnc'
    219 The purpose of this configuration is to compare two SP3 files to calculate
    220 RMS values for orbit and clock differences. GPS satellite G05 and GLONASS
    221 satellite R18 are excluded from this comparison. Comparison results are saved
    222 in a logfile.
     211Purpose: Compare two SP3 files to calculate RMS values for orbit and clock
     212differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this
     213comparison. Comparison results are saved in a logfile.
    223214
    22421521. File 'Empty.bnc'
    225 The purpose of this example is to provide an empty configuration file for
    226 BNC which only contains the default settings.
     216Purpose: Provide an empty example configuration file for BNC which only
     217contains the default settings.
    227218
    228219Georg Weber, BKG
    229 Frankfurt, December 2015
     220Frankfurt, January 2016
    230221igs-ip@bkg.bund.de
    231222
Note: See TracChangeset for help on using the changeset viewer.