Changeset 1191 in ntrip
- Timestamp:
- Nov 13, 2008, 9:30:57 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r1187 r1191 38 38 <li>generate ephemeris and synchronized observations epoch by epoch through an IP port to support real-time GNSS engines, and/or</li> 39 39 <li>generate clock and orbit corrections to broadcast ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers, and/or</li> 40 <li>generate synchronized clock and orbit corrections to broadcast ephemeris epoch by epoch through an IP port to support the combination of such streams coming from various providers, and/or</li> 40 41 <li>monitor the performance of a network of real-time GNSS reference stations to generate advisory notes, and/or</li> 41 42 <li>check RTCM streams for incoming message types and their repetition rates.</li> … … 51 52 <li>RTIGS containing GPS record types 200 (observations) and 300 (ephemeris).</li> 52 53 </ul> 53 BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. Although BNC is a real-time tool, it can be run offline for post processing of data made availabe from a file. 54 </p> 55 <p><a name="resources"><h3>2. Resources</h3></p> 54 BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. 55 </p> 56 <p><a name="resources"><h3>2. Modes and Resources</h3></p> 57 <p> 58 Although BNC is a real-time tool to be operated in online mode, it can be run offline for post processing of data made availabe from a file. Furthermore, besides its regular window mode, BNC can be started as a batch/background job in a 'no window' mode using processing options from previously saved configuration parameters. 59 </p> 56 60 <p> 57 61 Unless in offline mode, BNC 58 <ul> 59 <li>requires access to the Internet with a minimum of about 2 to 6 kbits/sec per stream depending on the stream format and the number of visible satellites. You need to make sure that the connection can sustain the required bandwidth.<li> 62 </p> 63 <ul> 64 <li>requires access to the Internet with a minimum of about 2 to 6 kbits/sec per stream depending on the stream format and the number of visible satellites. You need to make sure that the connection can sustain the required bandwidth.</li> 60 65 <li>requires the clock of the host computer to be properly synchronized.</li> 61 66 <li>has the capacity to retrieve hundreds of GNSS data streams simultaneously. Please be aware that such usage may incur a heavy load on the NTRIP broadcaster side depending on the number of streams requested. We recommend limiting the number of streams where possible to avoid unnecessary workload.</li>
Note:
See TracChangeset
for help on using the changeset viewer.