@@ -17,29 +17,21 @@
-Feel free to send us comments, suggestions or bug reports. Your contribution would be appreciated. -
- -Contents
-1. Purpose
-2. Handling
-3. Settings
-4. Limitations
-5. Annex
-
-Authors
+Feel free to send us comments, suggestions or bug reports. Any contribution would be appreciated.
+
+Authors
The BKG Ntrip Client (BNC) and its Qt Graphical User Interface (GUI) has been developed for
Federal Agency for Cartography and Geodesy (BKG)
-c/o Dr. Georg Weber
-Department of Geodesy
+Department of Geodesy, Section Navigation
+c/o Dr. Axel Rülke
Frankfurt, Germany
-[euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]
-
-BNC was written by +[axel.ruelke@bkg.bund.de] +
+ ++The BNC software has been written by
@@ -52,14 +44,9 @@-While work on BNC started in June 2005, Prof. Mervart's sole responsibility for the program code and concept lasted till February 2015. Since March 2015 the expert in charge at BKG for further developments is -
- -
-Dipl.-Ing. Andrea Stürze
-Federal Agency for Cartography and Geodesy (BKG)
-Department of Geodesy
-Section Navigation
-Frankfurt, Germany
-[andrea.stuerze@bkg.bund.de]
+Prof. Mervart started working on BNC in June 2005. His sole responsibility for the program code ended February 2015. Since March 2015 the expert in charge at BKG for further BNC programming is Dipl.-Ing. Andrea Stürze [andrea.stuerze@bkg.bund.de].
+
+BNC provides context-sensitive online help (Shift+F1: 'What's This') related to specific objects. It furthermore comes with this software documentation which is available as an integral part of the software and as a PDF file. Responsible for online and offline documentation, example configurations (and till February 2014 the overall BNC concept) is Dr. Georg Weber [georg.weber@bkg.bund.de].
@@ -72,5 +59,5 @@-Note that some figures presented in this documentation show screenshots from earlier versions of BNC. If so then there is either no relevant change compared to the current appearance of the program or no change at all. +Note that some figures presented in this documentation may show screenshots from earlier versions of BNC. If so then there is either no relevant change compared to the current appearance of the program or no change at all.
@@ -105,4 +92,64 @@ +Contents
+1. Purpose
+2. Handling
+3. Settings
+4. Limitations
+5. Annex
+
+
List of Figures
+
| Fig. | Title | Chapter |
| 1 | Flowchart, BNC connected to a GNSS rover for Precise Point Positioning | 1.2 |
| 2 | Flowchart, BNC converting RTCM streams to RINEX batches | 1.2 |
| 3 | Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections | 1.2 |
| 4 | Flowchart, BNC combining Broadcast Correction streams | 1.2 |
| 5 | Sections on BNC's main window | 2 |
| 6 | Management of configuration options in BNC | 2.1 |
| 7 | BNC translating incoming streams to 15 min RINEX Version 3 files | 3.4 |
| 8 | Example for 'RINEX Editing Options' window | 3.6.7 |
| 9 | Example for RINEX file concatenation with BNC | 3.6.7 |
| 10 | Example for creating RINEX quality check analysis graphics output with BNC | 3.6.7 |
| 11 | Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC | 3.6.7 |
| 12 | Sky plot examples for multipath, part of RINEX quality check analysis with BNC | 3.6.7 |
| 13 | Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC | 3.6.7 |
| 14 | BNC configuration example for comparing two SP3 files with satellite orbit and clock data | 3.7.3 |
| 15 | BNC configuration example for pulling, saving and output of Broadcast Corrections | 3.8.3 |
| 16 | Synchronized BNC output via IP port to feed a GNSS real-time engine | 3.9 |
| 17 | Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams | 3.10 |
| 18 | BNC pulling a VRS stream to feed a serial connected RTK rover | 3.10 |
| 19 | RTCM message numbers, latencies and observation types | 3.12 |
| 20 | Real-time Precise Point Positioning with BNC, PPP Panel 1 | 3.13.1 |
| 21 | Precise Point Positioning with BNC, PPP Panel 2 | 3.13.2 |
| 22 | Precise Point Positioning with BNC, PPP Panel 3 | 3.13.3 |
| 23 | BNC in 'Quick-Start' mode (PPP, Panel 2) | 3.13.3.8 |
| 24 | Track of positions from BNC with Google Maps in the background | 3.13.4.3 |
| 25 | BNC combining Broadcast Correction streams | 3.14.1.1 |
| 26 | BNC uploading the combined Broadcast Corrections stream | 3.14.1.1 |
| 27 | 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream | 3.14.1.1 |
| 28 | Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94' | 3.15.3 |
| 29 | Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster | 3.15.9 |
| 30 | Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster | 3.16.3 |
| 31 | Bandwidth consumption of incoming streams | 3.18.2 |
| 32 | Latency of incoming streams | 3.18.3 |
| 33 | Time series plot of PPP session | 3.18.4 |
| 34 | Steam input communication links | 3.19 |
| 35 | Casters table | 3.19.1.1.2 |
| 36 | Broadcaster source-table | 3.19.1.1.4 |
| 37 | Stream distribution map derived from NTRIP Broadcaster source-table | 3.19.1.1.6 |
| 38 | BNC setup for pulling a stream via serial port | 3.19.1.4 |
List of Tables
+
| Tab. | Title | Chapter |
| 1 | Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems | 1.1 |
Table: Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems
- +Table 1: Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems
| Left: | BNC in graphics mode; active configuration options are introduced through GUI input fields and finally saved on disk. | |
| Middle: | BNC in 'no window' mode; active configuration options are read from disk. |
| mountPoints | Add stream coming from ... |
| ntripVersion | NTRIP Version |
Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data:
