Changeset 7604 in ntrip for trunk/BNC/src/bnchelp.html

Timestamp:

Dec 6, 2015, 11:04:28 AM (8 years ago)

Author:

weber

Message:

Documentation completed

File:

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

trunk/BNC/src/bnchelp.html

@@ -355 +355 @@
 </p>
 
-<p> BNC has the following capabilities:
+<p> BNC was designed to serve the following purposes:
 <ul>
 <li>Retrieve real-time GNSS data streams available through Ntrip transport protocol;</li>
@@ -378 +378 @@
 <li>Plot positions derived via PPP from RTCM streams or RINEX files on maps from Google Map or OpenStreetMap;</li>
 <li>Simultaneously process several Broadcast Correction streams to produce, encode and upload combined Broadcast Corrections;</li>
+
+<li>Estimate real-time tropospheric zenith path delays and save them in SINEX troposphere file format;</li>
+
 <li>Read GNSS orbits and clocks in a plain ASCII format from an IP port. They can be produced by a real-time GNSS engine such as RTNET and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. BNC will then</li>
 <ul>
@@ -403 +406 @@
 </ul>
 </p>
+
 <p>
 Note that BNC allows to by-pass decoding and conversion algorithms for incoming streams, leave whatever is received untouched to save it in files or output it through local TCP/IP port.
+</p>
+
+<p>
+BNC supports the following GNSS file formats:
+</p>
+<p>
+<ul>
+<li>RINEX Version 2.11 & 3.02, Receiver Independent Exchange format for observations, navigation and meteorological data;</li>
+<li>SINEX Version 2.10, Solution Independent Exchange format for station position and velocity solutions;</li>
+<li>SINEX TRO, Troposphere Solution Independent Exchange format for zenith path delay products;</li>
+<li>SP3 Version c format for orbit solutions;</li>
+<li>Clock RINEX Version 3.02 format for station and satellite clock solutions;</li>
+<li>ANTEX Version 1.4, Antenna Exchange format for antenna calibration data;</li>
+<li>NMEA Version 0813, National Marine Electronics Association format for satellinte navigation data;</li>
+</ul>
 </p>
 
@@ -883 +902 @@
 
 <p>
-To cope with an increasing number of transmitting GNSS reference stations, the Federal Agency for Cartography and Geodesy (BKG) together with the Informatik Centrum Dortmund (ICD) in Germany developed a streaming protocol for satellite navigation data called 'Networked Transport of RTCM via Internet Protocol' (Ntrip). The protocol was built on top of the HTTP standard and included the provision of meta data describing the stream contents. Any stream could now be globally transmitted over just one IP port: HTTP port 80. Stream availability and content details became part of the transport protocol. The concept was first published in 2003 (Weber et al. 2003) and based on three software components, namely an NtripServer pushing data from a reference station to an NtripCaster and an NtripClient pulling data from a caster to support a rover receiver. (Note that from a socket-programmers perspective NtripServer and NtripClient both act as clients; only the NtripCaster operates as socket-server.) Ntrip could essentially benefit from Internet Radio developments. It was the ICECAST mulitmedia server which provided the bases for BKG's 'Professional Ntrip Broadcaster' with software published first in 2003 and of course again as Open Source under GPL.
+To cope with an increasing number of transmitting GNSS reference stations, the Federal Agency for Cartography and Geodesy (BKG) together with the Informatik Centrum Dortmund (ICD) in Germany developed a streaming protocol for satellite navigation data called 'Networked Transport of RTCM via Internet Protocol' (Ntrip). The protocol was built on top of the HTTP standard and included the provision of meta data describing the stream contents. Any stream could now be globally transmitted over just one IP port: HTTP port 80. Stream availability and content details became part of the transport protocol. The concept was first published in 2003 (Weber et al. 2003) and based on three software components, namely an NtripServer pushing data from a reference station to an NtripCaster and an NtripClient pulling data from the splitter caster to support a rover receiver. (Note that from a socket-programmers perspective NtripServer and NtripClient both act as clients; only the NtripCaster operates as socket-server.) Ntrip could essentially benefit from Internet Radio developments. It was the ICECAST mulitmedia server which provided the bases for BKG's 'Professional Ntrip Broadcaster' with software published first in 2003 and of course again as Open Source under GPL.
 </p>