Changeset 7127 in ntrip for trunk/BNC/src


Ignore:
Timestamp:
Jul 20, 2015, 10:06:33 AM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r7068 r7127  
    40884088
    40894089<li>File 'RinexObs.bnc'<br>
    4090 The purpose of this configuration is showing how to 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 Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources.
     4090The purpose of this configuration is showing how to convert RTCM streams to
     4091RINEX Observation files. The configuration pulls streams from Ntrip
     4092Broadcasters using Ntrip version 1 to generate 15min 1Hz RINEX Version 3
     4093Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation
     4094stream resources.
    40914095</li><br>
    40924096
    40934097<li>File 'RinexEph.bnc'<br>
    4094 The purpose of this configuration is showing how to convert a RTCM stream carrying navigation messages to a RINEX Navigation files. The configuration pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast Ephemeris resources.
     4098The purpose of this configuration is showing how to convert a RTCM stream
     4099carrying navigation messages to a RINEX Navigation files. The configuration
     4100pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the
     4101real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation
     4102files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time
     4103Broadcast Ephemeris resources.
    40954104</li><br>
    40964105
    40974106<li>File 'BrdcCorr.bnc'<br>
    4098 The purpose of this configuration is to 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 orbit/clock products.
     4107The purpose of this configuration is to save Broadcast Corrections from RTCM
     4108SSR messages in a plain ASCII format as hourly files. See
     4109http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF
     4110orbit/clock products.
    40994111</li><br>
    41004112
    41014113<li>File 'RinexConcat.bnc'<br>
    4102 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 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' mode for RINEX file editing, concatenation and quality checks.
     4114The purpose of this configuration is to concatenate RINEX Version 3 files to
     4115produce a concatenated file and edit the marker name in the file header. The
     4116sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the
     4117documentation for examples on how to call BNC from command line in 'no window'
     4118mode for RINEX file editing, concatenation and quality checks.
    41034119</li><br>
    41044120
    41054121<li>File 'RinexQC.bnc'<br>
    4106 The purpose of this configuration is to check the quality of a RINEX Version 3 file through a multipath analysis. The results is saved in 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 file editing, concatenation and quality checks.
     4122The purpose of this configuration is to check the quality of a RINEX Version 3
     4123file through a multipath analysis. The results is saved in disk in terms of a
     4124plot in PNG format. See section 'RINEX Editing & QC' in the documentation for
     4125examples on how to call BNC from command line in 'no window' mode for RINEX
     4126file editing, concatenation and quality checks.
    41074127</li><br>
    41084128
    41094129<li>File 'RTK.bnc'<br>
    4110 The purpose of this configuration is to 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 observation are reported in BNC's logfile.
     4130The purpose of this configuration is to feed a serial connected receiver with
     4131observations from a reference station for conventional RTK. The stream is
     4132scanned for RTCM messages. Message type numbers and latencies of incoming
     4133observation are reported in BNC's logfile.
    41114134</li><br>
    41124135
    41134136<li>File 'FeedEngine.bnc'<br>
    4114 The purpose of this configuration is to feed a real-time GNSS engine with observations from a remote reference stations. The configuration pulls a single stream from an NTRIP Broadcasters. It would of course be possible to pull several streams from different casters. Incoming observations are decoded, synchronized and output through a local IP port and saved into a file. Failure and recovery thresholds are specified to inform about outages.
     4137The purpose of this configuration is to feed a real-time GNSS engine with
     4138observations from a remote reference stations. The configuration pulls a single
     4139stream from an NTRIP Broadcasters. It would of course be possible to pull
     4140several streams from different casters. Incoming observations are decoded,
     4141synchronized and output through a local IP port and saved into a file. Failure
     4142and recovery thresholds are specified to inform about outages.
    41154143</li><br>
    41164144
    41174145<li>File 'PPP.bnc'<br>
    4118 The purpose of this configuration is 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 Corrections. Positions are saved in the logfile.
     4146The purpose of this configuration is Precise Point Positioning from
     4147observations of a rover receiver. The configuration reads RTCM Version 3
     4148observations, a Broadcast Ephemeris stream and a stream with Broadcast
     4149Corrections. Positions are saved in the logfile.
    41194150</li><br>
    41204151
     4152<li>File 'PPPNet.bnc'<br>
     4153The purpose of this configuration is to demonstrate siumultaneous Precise
     4154Point Positioning for several rovers or several receivers from a network of
     4155reference stations in one BNC job. The possible maximum number of PPP solutions
     4156per job depends on the processing power of the hosting computer. This example
     4157configuration reads two RTCM Version 3 observation streams, a Broadcast
     4158Ephemeris stream and a stream with Broadcast Corrections. PPP Results for the
     4159two stations are saved in PPP logfiles.
     4160</li><br>
     4161
    41214162<li>File 'PPPQuickStart.bnc'<br>
    4122 The purpose of this configuration is 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 Broadcast Ephemeris stream. Positions are saved in NMEA format on disc. Positions are also output through IP port for real-time visualization with tools like RTKPLOT. Positions are also saved in the logfile.
     4163The purpose of this configuration is Precise Point Positioning in Quick-Start
     4164mode from observations of a static receiver with precisely known position. The
     4165configuration reads RTCM Version 3 observations, Broadcast Corrections and a
     4166Broadcast Ephemeris stream. Positions are saved in NMEA format on disc.
     4167Positions are also output through IP port for real-time visualization with
     4168tools like RTKPLOT. Positions are also saved in the logfile.
    41234169</li><br>
    41244170
    41254171<li>File 'PPPPostProc.bnc'<br>
    4126 The purpose of this configuration is Precise Point Positioning in Post Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing options are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm.
     4172The purpose of this configuration is Precise Point Positioning in Post
     4173Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation
     4174files and a Broadcast Corrections file. PPP processing options are set to
     4175support the Quick-Start mode. The output is saved in a specific Post Processing
     4176logfile and contains the coordinates derived over time following the
     4177implemented PPP filter algorithm.
    41274178</li><br>
    41284179
    41294180<li>File 'PPPGoogleMaps.bnc'<br>
    4130 The purpose of this configuration is to track BNC's point positioning solution using Google Maps or Open StreetMap 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 this is not a real-time application it requires the BNC host to be connected to the Internet. Specify a computation speed, then hit button 'Open Map' to open the track map, then hit 'Start' to visualize receiver positions on top of GM/OSM maps.
     4181The purpose of this configuration is to track BNC's point positioning
     4182solution using Google Maps or Open StreetMap as background. BNC reads a
     4183RINEX Observation file and a RINEX Navigation file to carry out a
     4184'Standard Point Positioning' solution in post-processing mode. Although
     4185this is not a real-time application it requires the BNC host to be connected
     4186to the Internet. Specify a computation speed, then hit button 'Open Map'
     4187to open the track map, then hit 'Start' to visualize receiver positions
     4188on top of GM/OSM maps.
    41314189</li><br>
    41324190
    41334191<li>File 'SPPQuickStartGal.bnc'<br>
    4134 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 Ephemeris stream.
     4192The purpose of this configuration is Single Point Positioning in Quick-Start
     4193mode from observations of a static receiver with precisely known position. The
     4194configuration uses GPS, GLONASS and Galileo observations and a Broadcast
     4195Ephemeris stream.
    41354196</li><br>
    41364197
    4137 <li>File 'Sp3.bnc'<br>
    4138 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX file because SP3 file contents should be referred to CoM.
     4198<li>File 'SaveSp3.bnc'<br>
     4199The purpose of this configuration is to produce SP3 files from a Broadcast
     4200Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections
     4201stream is formally introduced in BNC's 'Combine Corrections' table. Note that
     4202producing SP3 requires an ANTEX file because SP3 file contents should be
     4203referred to CoM.
    41394204</li><br>
    41404205
    41414206<li>File 'Sp3ETRF2000PPP.bnc'<br>
    4142 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an 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.
     4207The purpose of this configuration is to produce SP3 files from a Broadcast
     4208Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The
     4209Broadcast Corrections stream is formally introduced in BNC's 'Combine
     4210Corrections' table. This leads to an SP3 file containing orbits referred also
     4211to ETRF2000. Pulling in addition observations from a reference station at
     4212precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution
     4213with ETRF2000 reference coordinates.
    41434214</li><br>
    41444215
    41454216<li>File 'Upload.bnc'<br>
    4146 The purpose of this configuration is to 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 Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to upload them to an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format.
     4217The purpose of this configuration is to upload orbits and clocks from a
     4218real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads
     4219precise orbits and clocks in RTNET format. It also reads a stream carrying
     4220Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast
     4221Corrections and encodes them in RTCM Version 3 SSR messages to upload them to
     4222an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite
     4223Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format
     4224and clocks in Clock RINEX format.
    41474225</li><br>
    41484226
    41494227<li>File 'UploadPPP.bnc'<br>
    4150 This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the Broadcast Corrections through observing coordinate displacements.
     4228This configuration equals the 'Upload.bnc' configuration. However, the
     4229Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution based
     4230on observations from a static reference station with known precise coordinates.
     4231This allows a continuous quality check of the Broadcast Corrections through
     4232observing coordinate displacements.
    41514233</li><br>
    41524234
    41534235<li>File 'Combi.bnc'<br>
    4154 The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format.
     4236The purpose of this configuration is to pull several streams carrying Broadcast
     4237Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to
     4238produce a combined Broadcast Corrections stream. BNC encodes the combination
     4239product in RTCM Version 3 SSR messages and uploads that to an Ntrip
     4240Broadcaster. The Broadcast Corrections stream is not referred to satellite
     4241Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format
     4242and clocks in Clock RINEX format.
    41554243</li><br>
    41564244
    41574245<li>File 'CombiPPP.bnc'<br>
    4158 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 coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements.
     4246This configuration equals the 'Combi.bnc' configuration. However, the combined
     4247Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions
     4248based on observations from a static reference station with known precise
     4249coordinates. This allows a continuous quality check of the combination product
     4250through observing coordinate displacements.
    41594251</li><br>
    41604252
    41614253<li>File 'UploadEph.bnc'<br>
    4162 The purpose of this configuration is to 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 which only provides Broadcast Ephemeris with an update rate of 5 seconds.
     4254The purpose of this configuration is to pull a number of streams from reference
     4255stations to get hold of contained Broadcast Ephemeris messages. These are
     4256encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris
     4257with an update rate of 5 seconds.
    41634258</li><br>
    41644259
     4260<li>File 'CompareSp3.bnc'<br>
     4261The purpose of this configuration is to compare two SP3 files to calculate
     4262RMS values for orbit and clock differences. GPS satellite G05 and GLONASS
     4263satellite R18 are excluded from this comparison. Comparison results are saved
     4264in a logfile.
     4265</li><br>
     4266
    41654267<li>File 'Empty.bnc'<br>
    4166 The purpose of this example is to provide an empty configuration file for BNC which only contains the default settings.
     4268The purpose of this example is to provide an empty configuration file for BNC
     4269which only contains the default settings.
    41674270</li>
    41684271
Note: See TracChangeset for help on using the changeset viewer.