Changeset 7683 in ntrip for trunk


Ignore:
Timestamp:
Jan 12, 2016, 3:38:14 PM (4 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

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

    r7682 r7683  
    707707
    708708<li>File 'RinexObs.bnc'<br>
    709 The purpose of this configuration is showing how to convert RTCM streams to
     709Purpose: Convert RTCM streams to
    710710RINEX Observation files. The configuration pulls streams from Ntrip
    711711Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3
     
    715715
    716716<li>File 'RinexEph.bnc'<br>
    717 The purpose of this configuration is showing how to convert a RTCM stream
    718 carrying navigation messages to a RINEX Navigation file. The configuration
     717Purpose: Convert a RTCM stream
     718carrying navigation messages to RINEX Navigation files. The configuration
    719719pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the
    720 real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation
     720real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation
    721721files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time
    722722Broadcast Ephemeris resources.
     
    724724
    725725<li>File 'BrdcCorr.bnc'<br>
    726 The purpose of this configuration is to save Broadcast Corrections from RTCM
     726Purpose: Save Broadcast Corrections from RTCM
    727727SSR messages in a plain ASCII format as hourly files. See
    728728http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF
     
    731731
    732732<li>File 'RinexConcat.bnc'<br>
    733 The purpose of this configuration is to concatenate RINEX Version 3 files to
    734 produce a concatenated file and edit the marker name in the file header. The
     733Purpose: Concatenate several RINEX Version 3 files to
     734produce one concatenated file and edit the marker name in the file header. The
    735735sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the
    736736documentation for examples on how to call BNC from command line in 'no window'
     
    739739
    740740<li>File 'RinexQC.bnc'<br>
    741 The purpose of this configuration is to check the quality of a RINEX Version 3
    742 file through a multipath analysis. Results are saved on disk in terms of a
     741Purpose: Check the quality of a RINEX Version 3
     742file by means of a multipath analysis. Results are saved on disk in terms of a
    743743plot in PNG format. See section 'RINEX Editing & QC' in the documentation for
    744744examples on how to call BNC from command line in 'no window' mode for RINEX
     
    747747
    748748<li>File 'RTK.bnc'<br>
    749 The purpose of this configuration is to feed a serial connected receiver with
     749Purpose: Feed a serial connected receiver with
    750750observations from a reference station for conventional RTK. The stream is
    751751scanned for RTCM messages. Message type numbers and latencies of incoming
     
    754754
    755755<li>File 'FeedEngine.bnc'<br>
    756 The purpose of this configuration is to feed a real-time GNSS engine with
     756Purpose: Feed a real-time GNSS engine with
    757757observations from remote reference stations. The configuration pulls a single
    758758stream from an Ntrip Broadcaster. It would of course be possible to pull
     
    763763
    764764<li>File 'PPP.bnc'<br>
    765 The purpose of this configuration is Precise Point Positioning from
     765Purpose: Precise Point Positioning from
    766766observations of a rover receiver. The configuration reads RTCM Version 3
    767767observations, a Broadcast Ephemeris stream and a stream with Broadcast
     
    770770
    771771<li>File 'PPPNet.bnc'<br>
    772 The purpose of this configuration is to demonstrate simultaneous Precise
    773 Point Positioning for several rovers or several receivers from a network of
     772Purpose: Precise
     773Point Positioning for several rovers or receivers from a network of
    774774reference stations in one BNC job. The possible maximum number of PPP solutions
    775775per job depends on the processing power of the hosting computer. This example
     
    780780
    781781<li>File 'PPPQuickStart.bnc'<br>
    782 The purpose of this configuration is Precise Point Positioning in Quick-Start
     782Purpose: Precise Point Positioning in Quick-Start
    783783mode from observations of a static receiver with precisely known position. The
    784784configuration reads RTCM Version 3 observations, Broadcast Corrections and a
     
    789789
    790790<li>File 'PPPPostProc.bnc'<br>
    791 The purpose of this configuration is Precise Point Positioning in post
     791Purpose: Precise Point Positioning in post
    792792processing mode. BNC reads RINEX Version 3 Observation and 3 Navigation files
    793793and a Broadcast Correction file. PPP processing options are set to support
     
    798798
    799799<li>File 'PPPGoogleMaps.bnc'<br>
    800 The purpose of this configuration is to track BNC's point positioning
     800Purpose: Track BNC's point positioning
    801801solution using Google Maps or OpenStreetMap as background. BNC reads a
    802802RINEX Observation file and a RINEX Navigation file to carry out a
     
    809809
    810810<li>File 'SPPQuickStartGal.bnc'<br>
    811 The purpose of this configuration is Single Point Positioning in Quick-Start
    812 mode from observations of a static receiver with precisely known position. The
    813 configuration uses GPS, GLONASS and Galileo observations and a Broadcast
     811Purpose: Single Point Positioning in Quick-Start mode from observations of a static
     812receiver with precisely known position.
     813The configuration uses GPS, GLONASS and Galileo observations and a Broadcast
    814814Ephemeris stream.
    815815</li><br>
    816816
    817817<li>File 'SaveSp3.bnc'<br>
    818 The purpose of this configuration is to produce SP3 files from a Broadcast
     818Purpose: Produces SP3 files from a Broadcast
    819819Ephemeris stream and a Broadcast Correction stream. The Broadcast Correction
    820820stream is formally introduced in BNC's 'Combine Corrections' table. Note that
     
    824824
    825825<li>File 'Sp3ETRF2000PPP.bnc'<br>
    826 The purpose of this configuration is to produce SP3 files from a Broadcast
     826Purpose: Produce SP3 files from a Broadcast
    827827Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The
    828828Broadcast Correction stream is formally introduced in BNC's 'Combine
    829 Corrections' table. This leads to a SP3 file containing orbits referred also
     829Corrections' table. The configuration leads to a SP3 file containing orbits referred also
    830830to ETRF2000. Pulling in addition observations from a reference station at
    831831precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution
    832 with ETRF2000 reference coordinates.
     832with a known ETRF2000 reference coordinate.
    833833</li><br>
    834834
    835835<li>File 'Upload.bnc'<br>
    836 The purpose of this configuration is to upload orbits and clocks from a
     836Purpose: Upload orbits and clocks from a
    837837real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads
    838838precise orbits and clocks in RTNET format. It also reads a stream carrying
     
    845845
    846846<li>File 'Combi.bnc'<br>
    847 The purpose of this configuration is to pull several streams carrying Broadcast
     847Purpose: Pull several streams carrying Broadcast
    848848Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to
    849849produce a combined Broadcast Correction stream. BNC encodes the combination
     
    855855
    856856<li>File 'CombiPPP.bnc'<br>
    857 This configuration equals the 'Combi.bnc' configuration. However, the combined
     857Purpose: This configuration equals the 'Combi.bnc' configuration. However, the combined
    858858Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions
    859859based on observations from a static reference station with known precise
     
    863863
    864864<li>File 'UploadEph.bnc'<br>
    865 The purpose of this configuration is to pull a number of streams from reference
     865Purpose: Pull a number of streams from reference
    866866stations to get hold of contained Broadcast Ephemeris messages. These are
    867867encoded then in a RTCM Version 3 stream with the sole purpose of providing
     
    870870
    871871<li>File 'CompareSp3.bnc'<br>
    872 The purpose of this configuration is to compare two SP3 files to calculate
     872Purpose: Compare two SP3 files to calculate
    873873RMS values from orbit and clock differences. GPS satellite G05 and GLONASS
    874874satellite R18 are excluded from this comparison. Comparison results are saved
     
    877877
    878878<li>File 'Empty.bnc'<br>
    879 The purpose of this example is to provide an empty configuration file for BNC
    880 which only contains default settings.
     879Purpose: Provide an empty example configuration file for
     880BNC which only contains the default settings.
    881881</li>
    882882
Note: See TracChangeset for help on using the changeset viewer.