BKG Ntrip Client

Index: /trunk/BNC/src/bncabout.html =================================================================== --- /trunk/BNC/src/bncabout.html (revision 8237) +++ /trunk/BNC/src/bncabout.html (revision 8238) @@ -27,3 +27,3 @@ E-Mail: igs-ip@bkg.bund.de.

-Copyright © 2005-2016 Bundesamt for Cartography and Geodesy (BKG), Frankfurt, Germany +Copyright © 2005-2018 Bundesamt for Cartography and Geodesy (BKG), Frankfurt, Germany Index: /trunk/BNC/src/bnchelp.html =================================================================== --- /trunk/BNC/src/bnchelp.html (revision 8237) +++ /trunk/BNC/src/bnchelp.html (revision 8238) @@ -1,3 +1,11 @@ - + + + + + + BKG Ntrip Client | Help + + +

@@ -5,11 +13,13 @@ Version 2.13 -

-Georg Weber⁽¹⁾, Leoš Mervart⁽²⁾, Andrea Stürze⁽¹⁾, Axel Rülke⁽¹⁾, Dirk Stöcker⁽³⁾ +

Georg Weber⁽¹⁾, Leoš Mervart⁽²⁾, Andrea Stürze⁽¹⁾, Axel Rülke⁽¹⁾, Dirk Stöcker⁽³⁾

^{(1) Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany}
^{(2) Czech Technical University (CTU), Department of Geomatics, Prague, Czech Republic}
^{(3) Alberding GmbH, Wildau, Germany} -

+

+
+ Copyright
© 2005-2016 Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany @@ -25,82 +35,83 @@

-Table of Contents

-1. General Information

- 1.1 Purpose
- 1.2 Supported GNSS
- 1.3 Data Flow
- 1.4 Handling
- 1.5 Installation
- 1.5.1 Compilation
- 1.6 Configuration
- 1.6.1 Examples
- 1.7 Limitations
- 1.8 Looking Back

-2. Settings Details

- 2.1 Top Menu Bar
- 2.1.1 File
- 2.1.2 Help
- 2.2 Network
- 2.2.1 Proxy
- 2.2.2 SSL
- 2.3 General
- 2.3.1 Logfile
- 2.3.2 Append Files
- 2.3.3 Reread Configuration
- 2.3.4 Auto Start
- 2.3.5 Raw Output File
- 2.4 RINEX Observations
- 2.4.1 Filenames
- 2.4.2 Directory
- 2.4.3 File Interval
- 2.4.4 Sampling
- 2.4.5 Skeleton Extension
- 2.4.6 Skeleton Mandatory
- 2.4.7 Script
- 2.4.8 Version 2
- 2.4.9 Version 3
- 2.4.10 Version 3 Filenames
- 2.5 RINEX Ephemeris
- 2.5.1 Directory
- 2.5.2 Interval
- 2.5.3 Port
- 2.5.4 Version
- 2.5.5 Version 3 Filenames
- 2.6 RINEX Editing & QC
- 2.6.1 Action
- 2.6.2 Input Files
- 2.6.3 Output Files
- 2.6.4 Logfiles
- 2.6.5 Plots for Signals
- 2.6.6 Directory for Plots
- 2.6.7 Set Edit Options
- 2.6.8 Command Line, No Window
- 2.7 SP3 Comparison
- 2.7.1 Input SP3 Files
- 2.7.2 Exclude Satellites
- 2.7.3 Logfile
- 2.8 Broadcast Corrections
- 2.8.1 Directory, ASCII
- 2.8.2 Interval
- 2.8.3 Port
- 2.8.4 Wait for Full Corr Epoch
- 2.9 Feed Engine
- 2.9.1 Port
- 2.9.2 Wait for Full Obs Epoch
- 2.9.3 Sampling
- 2.9.4 File
- 2.9.5 Port (unsynchronized)
- 2.10 Serial Output
- 2.10.1 Mountpoint
- 2.10.2 Port Name
- 2.10.3 Baud Rate
- 2.10.4 Flow Control
- 2.10.5 Parity
- 2.10.6 Data Bits
- 2.10.7 Stop Bits
- 2.10.8 NMEA
- 2.10.9 File
- 2.10.10 Height
- 2.10.11 Sampling
+

+Table of Contents

+1. General Information

+ 1.1 Purpose
+ 1.2 Supported GNSS
+ 1.3 Data Flow
+ 1.4 Handling
+ 1.5 Installation
+ 1.5.1 Compilation
+ 1.6 Configuration
+ 1.6.1 Examples
+ 1.7 Limitations
+ 1.8 Looking Back

+2. Settings Details

+ 2.1 Top Menu Bar
+ 2.1.1 File
+ 2.1.2 Help
+ 2.2 Network
+ 2.2.1 Proxy
+ 2.2.2 SSL
+ 2.3 General
+ 2.3.1 Logfile
+ 2.3.2 Append Files
+ 2.3.3 Reread Configuration
+ 2.3.4 Auto Start
+ 2.3.5 Raw Output File
+ 2.4 RINEX Observations
+ 2.4.1 Filenames
+ 2.4.2 Directory
+ 2.4.3 File Interval
+ 2.4.4 Sampling
+ 2.4.5 Skeleton Extension
+ 2.4.6 Skeleton Mandatory
+ 2.4.7 Script
+ 2.4.8 Version 2
+ 2.4.9 Version 3
+ 2.4.10 Version 3 Filenames
+ 2.5 RINEX Ephemeris
+ 2.5.1 Directory
+ 2.5.2 Interval
+ 2.5.3 Port
+ 2.5.4 Version
+ 2.5.5 Version 3 Filenames
+ 2.6 RINEX Editing & QC
+ 2.6.1 Action
+ 2.6.2 Input Files
+ 2.6.3 Output Files
+ 2.6.4 Logfiles
+ 2.6.5 Plots for Signals
+ 2.6.6 Directory for Plots
+ 2.6.7 Set Edit Options
+ 2.6.8 Command Line, No Window
+ 2.7 SP3 Comparison
+ 2.7.1 Input SP3 Files
+ 2.7.2 Exclude Satellites
+ 2.7.3 Logfile
+ 2.8 Broadcast Corrections
+ 2.8.1 Directory, ASCII
+ 2.8.2 Interval
+ 2.8.3 Port
+ 2.8.4 Wait for Full Corr Epoch
+ 2.9 Feed Engine
+ 2.9.1 Port
+ 2.9.2 Wait for Full Obs Epoch
+ 2.9.3 Sampling
+ 2.9.4 File
+ 2.9.5 Port (unsynchronized)
+ 2.10 Serial Output
+ 2.10.1 Mountpoint
+ 2.10.2 Port Name
+ 2.10.3 Baud Rate
+ 2.10.4 Flow Control
+ 2.10.5 Parity
+ 2.10.6 Data Bits
+ 2.10.7 Stop Bits
+ 2.10.8 NMEA
+ 2.10.9 File
+ 2.10.10 Height
+ 2.10.11 Sampling
2.11 Outages
2.11.1. Observation Rate
@@ -226,69 +237,75 @@ 3.4 Abbreviations

- - -

List of Figures

+
+ +

+List of Figures
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Fig. Title Chapter
1 Flowchart, BNC connected to a GNSS rover for Precise Point Positioning 1.3
2 Flowchart, BNC converting RTCM streams to RINEX batches 1.3
3 Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections 1.3
4 Flowchart, BNC combining Broadcast Correction streams 1.3
5 Sections on BNC's main window 1.4
6 Management of configuration options in BNC 1.6
7 BNC's 'Network' panel configured to ignore eventually occurring SSL error messages 2.2.2
8 BNC translating incoming streams to 15 min RINEX Version 3 files 2.4
9 BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files 2.5.5
10 Example for BNC's 'RINEX Editing Options' window 2.6.7
11 Example for RINEX file concatenation with BNC 2.6.7
12 Example for creating RINEX quality check analysis graphics output with BNC 2.6.7
13 Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC 2.6.7
14 Sky plot examples for multipath, part of RINEX quality check analysis with BNC 2.6.7
15 Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC 2.6.7
16 Example for comparing two SP3 files with satellite orbit and clock data using BNC 2.7.3
17 Example for pulling, saving and output of Broadcast Corrections using BNC 2.8.3
18 Synchronized BNC output via IP port to feed a GNSS real-time engine 2.9
19 Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is mandatory for VRS streams 2.10
20 BNC pulling a VRS stream to feed a serially connected RTK rover 2.10
21 RTCM message numbers, latencies and observation types logged by BNC 2.12
22 Real-time Precise Point Positioning with BNC, PPP Panel 1 2.13.1
23 Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization 2.13.2
24 Precise Point Positioning with BNC, PPP Panel 3 2.13.3
25 Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 4 2.13.3.8
26 Track of positions from BNC with Google Maps in background 2.13.4.3
27 Example for background map from Google Maps and OpenStreetMap (OSM) resources 2.13.4.3.1
28 BNC combining Broadcast Correction streams 2.14
29 INTERNAL' PPP with BNC using a combination of Broadcast Corrections 2.14
30 Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94' 2.15.3
31 BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster 2.15.11
32 BNC uploading a combined Broadcast Correction stream 2.15.11
33 BNC producing Broadcast Ephemeris stream from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster 2.16.3
34 Bandwidth consumption of RTCM streams received by BNC 2.18.2
35 Latency of RTCM streams received by BNC 2.18.3
36 Example for time series plot of displacements produced by BNC 2.18.4
37 Steam input communication links accepted by BNC 2.19
38 BNC's 'Select Broadcaster' table 2.19.1.1.2
39 Broadcaster source-table shown by BNC 2.19.1.1.4
40 Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table 2.19.1.1.6
41 BNC configuration for pulling a stream via serial port 2.19.1.4
Fig. Title Chapter
1 Flowchart, BNC connected to a GNSS rover for Precise Point Positioning 1.3
2 Flowchart, BNC converting RTCM streams to RINEX batches 1.3
3 Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections 1.3
4 Flowchart, BNC combining Broadcast Correction streams 1.3
5 Sections on BNC's main window 1.4
6 Management of configuration options in BNC 1.6
7 BNC's 'Network' panel configured to ignore eventually occurring SSL error messages 2.2.2
8 BNC translating incoming streams to 15 min RINEX Version 3 files 2.4
9 BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files 2.5.5
10 Example for BNC's 'RINEX Editing Options' window 2.6.7
11 Example for RINEX file concatenation with BNC 2.6.7
12 Example for creating RINEX quality check analysis graphics output with BNC 2.6.7
13 Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC 2.6.7
14 Sky plot examples for multipath, part of RINEX quality check analysis with BNC 2.6.7
15 Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC 2.6.7
16 Example for comparing two SP3 files with satellite orbit and clock data using BNC 2.7.3
17 Example for pulling, saving and output of Broadcast Corrections using BNC 2.8.3
18 Synchronized BNC output via IP port to feed a GNSS real-time engine 2.9
19 Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is mandatory for VRS streams 2.10
20 BNC pulling a VRS stream to feed a serially connected RTK rover 2.10
21 RTCM message numbers, latencies and observation types logged by BNC 2.12
22 Real-time Precise Point Positioning with BNC, PPP Panel 1 2.13.1
23 Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization 2.13.2
24 Precise Point Positioning with BNC, PPP Panel 3 2.13.3
25 Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 4 2.13.3.8
26 Track of positions from BNC with Google Maps in background 2.13.4.3
27 Example for background map from Google Maps and OpenStreetMap (OSM) resources 2.13.4.3.1
28 BNC combining Broadcast Correction streams 2.14
29 INTERNAL' PPP with BNC using a combination of Broadcast Corrections 2.14
30 Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94' 2.15.3
31 BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster 2.15.11
32 BNC uploading a combined Broadcast Correction stream 2.15.11
33 BNC producing Broadcast Ephemeris stream from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster 2.16.3
34 Bandwidth consumption of RTCM streams received by BNC 2.18.2
35 Latency of RTCM streams received by BNC 2.18.3
36 Example for time series plot of displacements produced by BNC 2.18.4
37 Steam input communication links accepted by BNC 2.19
38 BNC's 'Select Broadcaster' table 2.19.1.1.2
39 Broadcaster source-table shown by BNC 2.19.1.1.4
40 Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table 2.19.1.1.6
41 BNC configuration for pulling a stream via serial port 2.19.1.4

List of Tables

- - - + + +
Tab. Title Chapter
1 Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems 1.2
2 Contents and format of synchronized output of observations feeding a GNSS engine 2.9
Tab. Title Chapter
1 Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems 1.2
2 Contents and format of synchronized output of observations feeding a GNSS engine 2.9

1. General Information

-The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing or analyzing real-time GNSS data streams applying the 'Networked Transport of RTCM via Internet Protocol' (Ntrip) standard. It has been developed within the framework of the IAG sub-commission for Europe (EUREF) and the International GNSS Service (IGS). Although meant to be a real-time tool, it comes with some post processing functionality. It can be used for data coming from Ntrip Broadcasters like -

http://www.euref-ip.net/home

http://www.igs-ip.net/home

http://products.igs-ip.net/home

http://mgex.igs-ip.net/home

1. General Information

+The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing or +analyzing real-time GNSS data streams applying the 'Networked Transport of RTCM via Internet Protocol' (Ntrip) standard. + It has been developed within the framework of the IAG sub-commission for Europe (EUREF) and the International GNSS + Service (IGS). Although meant to be a real-time tool, it comes with some post processing functionality. It can be used + for data coming from Ntrip Broadcasters like +

-BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive http://software.rtcm-ntrip.org/svn/trunk/BNC. Precompiled binaries of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded from http://igs.bkg.bund.de/ntrip/download. +BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive + http://software.rtcm-ntrip.org/svn/trunk/BNC. + Precompiled binaries of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded from + http://igs.bkg.bund.de/ntrip/download.

@@ -307,8 +327,8 @@

    Federal Agency for Cartography and Geodesy (BKG)
-   c/o Dr. Axel Rülke
+   c/o Andrea Stuerze
    Department of Geodesy, Section Satellite Navigation
    Frankfurt, Germany
-   [axel.ruelke@bkg.bund.de]
+   [andrea.stuerze@bkg.bund.de]

-Prof. Mervart started working on BNC in 2005. His sole responsibility for writing the program code ended February 2015. In March 2015, Dipl.-Ing. Andrea Stürze took over the responsibility for maintaining and further developing BNC's source code. +Prof. Mervart started working on BNC in 2005. His sole responsibility for writing the program code ended February 2015. +In March 2015, Dipl.-Ing. Andrea Stürze took over the responsibility for maintaining and +further developing BNC's source code.

Documentation

-BNC provides context-sensitive help (What's This) related to specific objects. It furthermore comes with the here presented documentation, available as part of the software and as a PDF file. Responsible for offline documentation as well as online documentation at http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/src/bnchelp.html and the example configurations is Dr. Georg Weber. -

-Note that some figures presented in this documentation may show screenshots from earlier versions of BNC. If so, there is either no relevant change compared to the current appearance of the program or no change at all. +BNC provides context-sensitive help (What's This) related to specific objects. It furthermore comes with the +here presented documentation, available as part of the software and as a PDF file. Responsible for offline +documentation as well as online documentation at +http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/src/bnchelp.html and the example +configurations is Dr. Georg Weber. +

+Note that some figures presented in this documentation may show screenshots from earlier versions of BNC. +If so, there is either no relevant change compared to the current appearance of the program or no change at all.

Acknowledgements

-Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany published a RTCM Version 2 decoder unter GNU GPL which has been integrated in BNC. -
-Thomas Yan, Australian NSW Land and Property Information, proofread earlier versions of BNC's Help Contents. Up to Version 2.11 he also provides builds of BNC for Mac OS X systems. -
-James Perlt, BKG, helped fixing bugs and redesigned BNC's main window in version 1.5. -
-Andre Hauschild, German Space Operations Center, DLR, revised the RTCM Version 2 decoder. -
-Zdenek Lukes, Czech Technical University Prague, Department of Geodesy, extended the RTCM Version 2 decoder to handle message types 3, 20, 21, and 22 and added the loss of lock indicator. -
-Jan Dousa, Geodetic Observatory Pecny, Czech Republic, helped with fixing bugs in version 2.5. -
-Denis Laurichesse, Centre National d'Etudes Spatiales (CNES), suggested synchronizing observations and clock corrections to reduce high frequency noise in PPP solutions. -
-Lennard Huisman, Kadaster Netherlands, and Rolf Dach, Astronomical Institute University of Bern, assisted in handling satellite clocks in transformations from ITRF to regional reference frames. -

1.1 Purpose

- -

-Promoting Open RTCM Standards for streaming GNSS data over the Internet has been a major aspect in developing BNC as Open Source real-time software. Basically, the tool enables the test, validation and further evolution of new RTCM messages for precise satellite navigation. With high-level source code at hand, it also allows university education to catch up with comprehensive state-of-the-art positioning and potentially contributes fresh ideas which are free from any licensing. +

Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany published a RTCM Version 2 decoder + unter GNU GPL which has been integrated in BNC.

Thomas Yan, Australian NSW Land and Property Information, proofread earlier versions of BNC's Help Contents. + Up to Version 2.11 he also provides builds of BNC for Mac OS X systems.

Scott Glazier, OmniSTAR Australia, has been helpful in finding BNC bugs in version 1.5.

James Perlt, BKG, helped fixing bugs and redesigned BNC's main window in version 1.5.

Andre Hauschild, German Space Operations Center, DLR, revised the RTCM Version 2 decoder.

Zdenek Lukes, Czech Technical University Prague, Department of Geodesy, extended the RTCM Version 2 decoder to handle + message types 3, 20, 21, and 22 and added the loss of lock indicator.

Jan Dousa, Geodetic Observatory Pecny, Czech Republic, helped with fixing bugs in version 2.5.

Denis Laurichesse, Centre National d'Etudes Spatiales (CNES), suggested synchronizing observations and clock + corrections to reduce high frequency noise in PPP solutions.

Lennard Huisman, Kadaster Netherlands, and Rolf Dach, Astronomical Institute University of Bern, assisted in handling + satellite clocks in transformations from ITRF to regional reference frames.

+ +

1.1 Purpose

+ +

+Promoting Open RTCM Standards for streaming GNSS data over the Internet has been a major aspect in developing BNC as +Open Source real-time software. Basically, the tool enables the test, validation and further evolution of new RTCM +messages for precise satellite navigation. With high-level source code at hand, it also allows university education +to catch up with comprehensive state-of-the-art positioning and potentially contributes fresh ideas which are free +from any licensing.

BNC was designed to serve the following purposes:

Retrieve real-time GNSS data streams available through Ntrip transport protocol;
Retrieve real-time GNSS data streams via TCP directly from an IP address without using the Ntrip transport protocol;
Retrieve real-time GNSS data streams from a local UDP or serial port without using the Ntrip transport protocol;
Plot stream distribution map from Ntrip Broadcaster source-tables;
Generate RINEX Observation and Navigation files to support near real-time GNSS post processing applications;
Edit or concatenate RINEX files or carry out RINEX Quality Checks (QC);
Convert RINEX Version 2 to RINEX Version 3 and vice versa;
Compare SP3 files containing satellite orbit and clock data;
Generate orbit and clock corrections to Broadcast Ephemeris through an IP port to

support real-time Precise Point Positioning on GNSS rovers;
support the (outside) combination of such streams as coming simultaneously from various correction providers;

Generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port to support real-time GNSS network engines;
Feed a stream into a GNSS receiver via serial communication link;
Monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of outages or corrupted streams;
Scan RTCM streams for incoming antenna information, observation types, message types and repetition rates and latencies and GLONASS slot numbers and frequency channels;
Carry out real-time Precise Point Positioning to determine GNSS rover positions;
Enable multi-station Precise Point Positioning for simultaneous processing of observations from a whole network of receivers;
Plot positions derived via PPP from RTCM streams or RINEX files on maps from Google Map or OpenStreetMap;
Simultaneously process several Broadcast Correction streams to produce, encode and upload combined Broadcast Corrections;
Estimate real-time tropospheric zenith path delays and save them in SINEX troposphere file format;
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

Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and out-of-plane components;
Upload Broadcast Corrections as an RTCM Version 3 stream to an Ntrip Broadcaster;
Refer the orbit and clock corrections to a specific reference system;
Log the Broadcast Corrections as Clock RINEX files for further processing using other tools than BNC;
Log the Broadcast Corrections as SP3 files for further processing using other tools than BNC;

Upload a Broadcast Ephemeris stream in RTCM Version 3 format;
Retrieve real-time GNSS data streams available through Ntrip transport protocol
Retrieve real-time GNSS data streams via TCP directly from an IP address without using the Ntrip transport protocol
Retrieve real-time GNSS data streams from a local UDP or serial port without using the Ntrip transport protocol
Plot stream distribution map from Ntrip Broadcaster source-tables
Generate RINEX Observation and Navigation files to support near real-time GNSS post processing applications
Edit or concatenate RINEX files or carry out RINEX Quality Checks (QC)
Convert RINEX Version 2 to RINEX Version 3 and vice versa
Compare SP3 files containing satellite orbit and clock data
Generate orbit and clock corrections to Broadcast Ephemeris through an IP port to

support real-time Precise Point Positioning on GNSS rovers
support the (outside) combination of such streams as coming simultaneously from various correction providers

Generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port to support real-time GNSS network engines
Feed a stream into a GNSS receiver via serial communication link
Monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of outages or corrupted streams
Scan RTCM streams for incoming antenna information, observation types, message types and repetition rates and latencies and GLONASS slot numbers and frequency channels
Carry out real-time Precise Point Positioning to determine GNSS rover positions
Enable multi-station Precise Point Positioning for simultaneous processing of observations from a whole network of receivers
Plot positions derived via PPP from RTCM streams or RINEX files on maps from Google Map or OpenStreetMap
Simultaneously process several Broadcast Correction streams to produce, encode and upload combined Broadcast Corrections
Estimate real-time tropospheric zenith path delays and save them in SINEX troposphere file format
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

Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and out-of-plane components
Upload Broadcast Corrections as an RTCM Version 3 stream to an Ntrip Broadcaster
Refer the orbit and clock corrections to a specific reference system
Log the Broadcast Corrections as Clock RINEX files for further processing using other tools than BNC
Log the Broadcast Corrections as SP3 files for further processing using other tools than BNC

Upload a Broadcast Ephemeris stream in RTCM Version 3 format;

@@ -429,10 +447,10 @@

RTCM Version 2 message types;
RTCM Version 3 'conventional' message types;
RTCM Version 3 message types for Broadcast Ephemeris;
RTCM Version 3 'State Space Representation' (SSR) messages;
RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM);
RTNET, a plain ASCII format defined within BNC to receive orbits and clocks from a serving GNSS engine. +
RTCM Version 2 message types
RTCM Version 3 'conventional' message types
RTCM Version 3 message types for Broadcast Ephemeris
RTCM Version 3 'State Space Representation' (SSR) messages
RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM)
RTNET, a plain ASCII format defined within BNC to receive orbits and clocks from a serving GNSS engine

@@ -443,32 +461,35 @@

RINEX Version 2.11 & 3.03, Receiver Independent Exchange format for observations, navigation and meteorological data;
SINEX Version 2.10, Solution Independent Exchange format for station position and velocity solutions;
SINEX TRO Draft Version 2.00, Troposphere Solution Independent Exchange format for zenith path delay products;
SP3 Version c format for orbit solutions;
Clock RINEX Version 3.02 format for station and satellite clock solutions;
ANTEX Version 1.4, Antenna Exchange format for Antenna Phase Center variations;
NMEA Version 0813, National Marine Electronics Association format for satellite navigation data;

- -

-Note that BNC allows to by-pass decoding and conversion algorithms for incoming streams, leaves whatever is received untouched to save it in files or output it through local TCP/IP port. -

- -

1.2 Supported GNSS

-BNC is permanently completed to finally support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are supported so far by particular applications when using the latest BNC version. Application areas named here are: -

Decoding of RTCM or RTNET streams
RINEX and SP3 file input and output
Encoding of SSR and ephemeris messages
Upload of SSR and ephemeris messages
PPP (Precise Point Positioning)
Combining/merging SSR or ephemeris messages from various real-time sources
RINEX Version 2.11 & 3.03, Receiver Independent Exchange format for observations, navigation and meteorological data
SINEX Version 2.10, Solution Independent Exchange format for station position and velocity solutions
SINEX TRO Draft Version 2.00, Troposphere Solution Independent Exchange format for zenith path delay products
SP3 Version c format for orbit solutions
Clock RINEX Version 3.02 format for station and satellite clock solutions
ANTEX Version 1.4, Antenna Exchange format for Antenna Phase Center variations
NMEA Version 0813, National Marine Electronics Association format for satellite navigation data

+ +

+Note that BNC allows to by-pass decoding and conversion algorithms for incoming streams, leaves whatever is received +untouched to save it in files or output it through local TCP/IP port. +

+ +

1.2 Supported GNSS

+BNC is permanently completed to finally support all existing GNSS systems throughout all features of the program. +The table below shows in detail which GNSS systems are supported so far by particular applications when using the +latest BNC version. Application areas named here are: +

Decoding of RTCM or RTNET streams
RINEX and SP3 file input and output
Encoding of SSR and ephemeris messages
Upload of SSR and ephemeris messages
PPP (Precise Point Positioning)
Combining/merging SSR or ephemeris messages from various real-time sources

The table indicates if a message implementation in BNC could so far only be based on a 'RTCM Proposal'.

Table 1: Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems

@@ -551,54 +572,67 @@
-

1.3 Data Flow

- -

-BNC can be used in different contexts with varying data flows. Typical real-time communication follows the Ntrip protocol over TCP/IP (probably via SSL), RTSP/RTP or UDP, plain TCP/IP protocol, or serial communication links. Stream content could be observations, ephemeris, satellite orbit/clock products or NMEA sentences. -

-The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an Ntrip Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to disseminate the combination product while saving results in SP3 and Clock RINEX files. +

1.3 Data Flow

+ +

+BNC can be used in different contexts with varying data flows. Typical real-time communication follows the Ntrip protocol +over TCP/IP (probably via SSL), RTSP/RTP or UDP, plain TCP/IP protocol, or serial communication links. +Stream content could be observations, ephemeris, satellite orbit/clock products or NMEA sentences. +

+The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via +serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion +of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which +estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload +them to an Ntrip Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to +disseminate the combination product while saving results in SP3 and Clock RINEX files.

Figure 1: Flowchart, BNC connected to a GNSS rover for Precise Point Positioning

Figure 2: Flowchart, BNC converting RTCM streams to RINEX batches

Figure 3: Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections

Figure 4: Flowchart, BNC combining Broadcast Correction streams

- -

1.4 Handling

Figure 4: Flowchart, BNC combining Broadcast Correction streams

+ +

1.4 Handling

Although BNC is mainly a real-time tool to be operated online, it can be run offline

To simulate real-time observation situations for debugging purposes;
For post processing purposes.

-Furthermore, apart from its regular window mode, BNC can be run as a batch/background job in a 'no window' mode, using processing options from a previously saved configuration or from command line. -

To simulate real-time observation situations for debugging purposes;

For post processing purposes.

+ +Furthermore, apart from its regular window mode, BNC can be run as a batch/background job in a 'no window' mode, +using processing options from a previously saved configuration or from command line. +

Unless it runs offline, BNC

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;
Requires the clock of the host computer to be properly synchronized;
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.

- -

-The main window of BNC shows a 'Top menu bar' section, a 'Settings' sections with panels to set processing options, a 'Streams' section, a section for 'Log' tabs, and a 'Bottom menu bar' section, see figure below. +

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;

Requires the clock of the host computer to be properly synchronized;

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.

+ +

+The main window of BNC shows a 'Top menu bar' section, a 'Settings' sections with panels to set processing options, +a 'Streams' section, a section for 'Log' tabs, and a 'Bottom menu bar' section, see figure below.

Figure 5: Sections on BNC's main window

@@ -611,42 +645,73 @@

-The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration panels to set a combination of input, processing and output options before you start the program ('Start'). Most configuration panels are dedicated to a certain function of BNC. If the first option field on such a configuration panel is empty, the affected functionality is deactivated. -

- -

-Records of BNC's activities are shown in the 'Log' tab which is part of the 'Log' canvas. The bandwidth consumption per stream, the latency of incoming observations, and a PPP time series for coordinate displacements are also part of that canvas and shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs. -

- -

-Configuration options are usually first set using BNC's Graphical User Interface (GUI), then saved in a configuration file. For routine operations in batch mode all of BNC's configuration options can be extracted from the configuration file and applied using the program's Command Line Interface (CLI). -

- -

1.5 Installation

-Precompiled builds of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded for installation from http://igs.bkg.bund.de/ntrip/download. Please ensure that you always use the latest released version of the program. -

-MS Windows Build: A dynamically compiled shared library build for Mircrosoft Windows systems is provided as Microsoft Installer (MSI) file. MSI files are used for installation, storage, and removal of programs. The BNC files are contained in a MSI package, which is used with the program's client-side installer service, an .EXE file, to open and install the program. We used the MinGW Version 4.4.0 compiler to create BNC for Windows. After installation your 'bnc.exe' file shows up e.g. under 'All Programs'. -

- -

-Linux Build: Static library and shared library builds for BNC are provided for a selection of Linux distributions. Download the ZIP archive for a version which fits to your Linux system, unzip the archive and run the included BNC binary. A static build would be sufficient in case you do not want BNC to plot PPP results with Google Map (GM) or OpenStreetMap (OSM) maps in the background. GM/OSM usage requires BNC builds from shared libraries. -

- -

-Mac OS X Build: -A shared library 'Disk iMaGe' (DMG) file is provided for BNC on OS X systems; it also comes in a ZIP archive. The DMG file format is used in the Mac for distributing software. Mac install packages appear as a virtual disk drive. After download, when the DMG file icon is double clicked, the virtual drive is 'mounted' on the desktop. Install BNC by dragging the 'bnc.app' icon to your '/Applications' folder. To start BNC, double click on '/Applications/bnc.app'. You could also start BNC via Command Line Interface (CLI) using command '/Applications/bnc.app/Contents/MacOS/bnc'. -

- -

1.5.1 Compilation

- -

-BNC has been written as Open Source and published under GNU General Public License (GPL). The latest source code can be checked out from Subversion repository http://software.rtcm-ntrip.org/svn/trunk/BNC. A ZIP archive available from http://igs.bkg.bund.de/ntrip/download provides the source code for BNC Version 2.12.0, developed using Qt Version 4.8.5. -

The following describes how you can produce your own builds of BNC on MS Windows, Linux, and Mac systems. It is likely that BNC can also be compiled on other systems where a GNU compiler and Qt Version 4.8.5 or any later version is installed. +The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC +shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration +panels to set a combination of input, processing and output options before you start the program ('Start'). +Most configuration panels are dedicated to a certain function of BNC. If the first option field on such a configuration + panel is empty, the affected functionality is deactivated. +

+ +

+Records of BNC's activities are shown in the 'Log' tab which is part of the 'Log' canvas. The bandwidth consumption +per stream, the latency of incoming observations, and a PPP time series for coordinate displacements are also part +of that canvas and shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs. +

+ +

+Configuration options are usually first set using BNC's Graphical User Interface (GUI), then saved in a configuration + file. For routine operations in batch mode all of BNC's configuration options can be extracted from the configuration + file and applied using the program's Command Line Interface (CLI). +

+ +

1.5 Installation

+Precompiled builds of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded for +installation from http://igs.bkg.bund.de/ntrip/download. +Please ensure that you always use the latest released + version of the program. +

+MS Windows Build: A dynamically compiled shared library build for Mircrosoft Windows systems is provided as +Microsoft Installer (MSI) file. MSI files are used for installation, storage, and removal of programs. +The BNC files are contained in a MSI package, which is used with the program's client-side installer service, +an .EXE file, to open and install the program. We used the MinGW Version 4.4.0 compiler to create BNC for Windows. +After installation your 'bnc.exe' file shows up e.g. under 'All Programs'. +

+ +

+Linux Build: Static library and shared library builds for BNC are provided for a selection of Linux distributions. +Download the ZIP archive for a version which fits to your Linux system, unzip the archive and run the included BNC binary. +A static build would be sufficient in case you do not want BNC to plot PPP results with Google Map (GM) or +OpenStreetMap (OSM) maps in the background. GM/OSM usage requires BNC builds from shared libraries. +

+ +

+Mac OS X Build: +A shared library 'Disk iMaGe' (DMG) file is provided for BNC on OS X systems; it also comes in a ZIP archive. The DMG +file format is used in the Mac for distributing software. Mac install packages appear as a virtual disk drive. After +download, when the DMG file icon is double clicked, the virtual drive is 'mounted' on the desktop. Install BNC by +dragging the 'bnc.app' icon to your '/Applications' folder. To start BNC, double click on '/Applications/bnc.app'. +You could also start BNC via Command Line Interface (CLI) using command '/Applications/bnc.app/Contents/MacOS/bnc'. +

+ +

1.5.1 Compilation

+ +

+BNC has been written as Open Source and published under GNU General Public License (GPL). The latest source code can +be checked out from Subversion repository http://software.rtcm-ntrip.org/svn/trunk/BNC. A ZIP archive available from +http://igs.bkg.bund.de/ntrip/download +provides the source code. +

The following describes how you can produce your own builds of BNC on MS Windows, Linux, and Mac systems. +It is likely that BNC can also be compiled on other systems where a GNU compiler and Qt Version 4.8 or any later + version is installed.

Static versus Shared Libraries
-You can produce static or shared library builds of BNC. Static builds are sufficient in case you do not want BNC to produce track maps on top of Google Map (GM) or OpenStreetMap (OSM). GM/OSM usage would require the QtWebKit library which can only be part of BNC builds from shared Qt libraries. Hence, having a shared library Qt installation available is a precondition for producing a shared library build of BNC. +You can produce static or shared library builds of BNC. Static builds are sufficient in case you do not want +BNC to produce track maps on top of Google Map (GM) or OpenStreetMap (OSM). GM/OSM usage would require the +QtWebKit library which can only be part of BNC builds from shared Qt libraries. Hence, having a shared library + Qt installation available is a precondition for producing a shared library build of BNC.

@@ -655,16 +720,22 @@

Supposing that 'Secure Socket Layer (SSL)' is not available on you system, you should install OpenSSL libraries in C:\OpenSSL-Win32. They are available e.g. from http://igs.bkg.bund.de/root_ftp/NTRIP/software/Win32OpenSSL-1_0_1e.exe. See http://slproweb.com/products/Win32OpenSSL.html for other SSL resources. Ignore possibly occurring comments about missing components during installation.
Download MinGW compiler Version 4.4.0 e.g. from http://igs.bkg.bund.de/root_ftp/NTRIP/software/MinGW-gcc440_1.zip
Unzip the ZIP archive and move its contents to a directory C:\MinGW. Now you can do either (4) or (5, 6, 8, 9, 10). Following (4) is suggested.
Download file 'qt-win-opensource-4.8.5-mingw.exe' (317 MB) e.g. from https://download.qt.io/archive/qt/4.8/4.8.5/. Execute this file to install a pre-compiled shared Qt library.
Download file 'qt-everywhere-opensource-src-4.8.5.zip' (269 MB) e.g. from https://download.qt.io/archive/qt/4.8/4.8.5/
Unzip the ZIP archive and move the contents of the contained directory into a directory C:\Qt\4.8.5.

Supposing that 'Secure Socket Layer (SSL)' is not available on you system, you should install OpenSSL libraries +in C:\OpenSSL-Win32. They are available e.g. from http://igs.bkg.bund.de/root_ftp/NTRIP/software/Win32OpenSSL-1_0_1e.exe. +See http://slproweb.com/products/Win32OpenSSL.html +for other SSL resources. Ignore possibly occurring comments about missing components during installation.
Download MinGW compiler Version 4.4.0 e.g. from http://igs.bkg.bund.de/root_ftp/NTRIP/software/MinGW-gcc440_1.zip
Unzip the ZIP archive and move its contents to a directory C:\MinGW. Now you can do either (4) or (5, 6, 8, 9, 10). Following (4) is suggested.
Download file 'qt-win-opensource-4.8.5-mingw.exe' (317 MB) e.g. from https://download.qt.io/archive/qt/4.8/4.8.5/. Execute this file to install a pre-compiled shared Qt library.
Download file 'qt-everywhere-opensource-src-4.8.5.zip' (269 MB) e.g. from + https://download.qt.io/archive/qt/4.8/4.8.5/
Unzip the ZIP archive and move the contents of the contained directory into a directory C:\Qt\4.8.5.
Create somewhere a file QtEnv.bat with the following content: @@ -690,5 +761,6 @@ Should you want to reconfiguring Qt following steps (8)-(10) you first need to clean the previous configuration using command 'mingw32-make confclean'. Run command 'mingw32-make clean' to delete previously compiled source code.
Download latest BNC from SVN repository http://software.rtcm-ntrip.org/svn/trunk/BNC.
Download latest BNC from SVN repository http://software.rtcm-ntrip.org/svn/trunk/BNC.
Open command line window and execute file QtEnv.bat, see (7)

-Steps (11)-(15) can be repeated whenever a BNC update becomes available. Running bnc.exe on a windows system requires (1) when using the NTRIP Version 2s option for stream transfer over TLS/SSL. +Steps (11)-(15) can be repeated whenever a BNC update becomes available. Running bnc.exe on a windows system +requires (1) when using the NTRIP Version 2s option for stream transfer over TLS/SSL.

-Download file 'qt-everywhere-opensource-src-4.8.5.tar.gz' (230 MB) available from https://download.qt.io/archive/qt/4.8/4.8.5/. Unzip file, extract tar archive and change to directory 'qt-everywhere-opensource-src-4.8.5'. Run commands +Download file 'qt-everywhere-opensource-src-4.8.5.tar.gz' (230 MB) available from https://download.qt.io/archive/qt/4.8/4.8.5/. Unzip file, extract tar archive and change to +directory 'qt-everywhere-opensource-src-4.8.5'. Run commands

   ./configure -fast -webkit -nomake examples -nomake tutorial
@@ -729,6 +804,7 @@
 
 
-Qt will be installed into directory /usr/local/Trolltech/Qt-4.8.5. To reconfigure, run 'gmake confclean' and 'configure'. Note that the '-prefix' option allows you to specify a directory for saving the Qt libraries. This ensures that you do not run into conflicts with other
-Qt installations on your host. Note further that the following two lines
+Qt will be installed into directory /usr/local/Trolltech/Qt-4.8.5. To reconfigure, run 'gmake confclean' and 'configure'.
+Note that the '-prefix' option allows you to specify a directory for saving the Qt libraries. This ensures that you do not run
+into conflicts with other Qt installations on your host. Note further that the following two lines   export QTDIR="/usr/local/Trolltech/Qt-4.8.5"
   export PATH="$QTDIR/bin:$PATH"
@@ -737,5 +813,6 @@
 
 
-To compile the BNC program, you first download the source code from SVN repository http://software.rtcm-ntrip.org/svn/trunk/BNC. Go to directory BNC and run the following commands: 
+To compile the BNC program, you first download the source code from SVN repository http://software.rtcm-ntrip.org/svn/trunk/BNC. Go to directory BNC and run the following commands:    qmake bnc.pro
   make
@@ -747,10 +824,13 @@
 
 Xcode and Qt Installation

-Xcode and Qt are required to compile BNC on OS X. Both tools are freely available. Xcode can be downloaded from the App Store or the Apple Developer Connection website. Once installed, run Xcode, go to 'Preferences->Downloads' and install the Command Line Tools component. Qt can be downloaded from the Qt Project website. We suggest installing version 4.8.4 or higher. The Qt libraries for Mac can be downloaded from http://www.qt.io/download. Once downloaded, mount the disk image, run the Qt.mpkg package and follow instructions from the installation wizard.
+Xcode and Qt are required to compile BNC on OS X. Both tools are freely available. Xcode can be downloaded from the
+App Store or the Apple Developer Connection website. Once installed, run Xcode, go to 'Preferences->Downloads' and install the Command Line Tools component. Qt can be downloaded from the Qt Project website. We suggest installing version 4.8.4 or higher. The Qt libraries for Mac can be downloaded from http://www.qt.io/download. Once downloaded, mount the disk image, run the Qt.mpkg package and follow instructions from the installation wizard.
 
 
 
 Compiling BNC

-The version of qmake supplied in the Qt binary package is configured to use the macx-xcode specification. This can be overridden with the '-spec macx-g++' option which makes it possible to use qmake to create a Makefile to be used by 'make'.
+The version of qmake supplied in the Qt binary package is configured to use the macx-xcode specification.
+This can be overridden with the '-spec macx-g++' option which makes it possible to use qmake to create a Makefile to
+ be used by 'make'.
 
 
@@ -760,24 +840,33 @@
    make
 
-Refer to the following webpage for further information: http://doc.qt.io/qt-4.8/qmake-platform-notes.html.
+Refer to the following webpage for further information: http://doc.qt.io/qt-4.8/qmake-platform-notes.html.
 
 
 
 Bundle Deployment

-When distributing BNC it is necessary to bundle in all related Qt resources in the package. The Mac Deployment Tool has been designed to automate the process of creating a deployable application bundle that contains the Qt libraries as private frameworks. To use it, issue the following commands where bnc.app is located.
+When distributing BNC it is necessary to bundle in all related Qt resources in the package. The Mac Deployment Tool
+has been designed to automate the process of creating a deployable application bundle that contains the Qt libraries
+as private frameworks. To use it, issue the following commands where bnc.app is located.
 
    macdeployqt bnc.app -dmg
 
-Refer to the following webpage for further information: http://doc.qt.io/qt-4.8/deployment-mac.html.
-
-
-Once a DMG file for BNC is created, you can double click it and install BNC by dragging the 'bnc.app' icon to your 'Applications' folder. To start BNC, double click on '/Aplications/bnc.app'.
-
-
-
1.6 Configuration

-
-As a default, configuration files for running BNC on Unix/Linux/Mac OS X systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration filename is 'BNC.bnc'.
-
-The default filename 'BNC.bnc' can be changed and the file content can easily be edited. On graphical user interfaces it is possible to Drag & Drop a configuration file icon to start BNC (not on Mac OS X systems). It is also possible to start and configure BNC via command line. Some configuration options can be changed on-the-fly. See annexed 'Command Line Help' for a complete set of configuration options.
+Refer to the following webpage for further information: http://doc.qt.io/qt-4.8/deployment-mac.html.
+
+
+Once a DMG file for BNC is created, you can double click it and install BNC by dragging the 'bnc.app' icon to your
+'Applications' folder. To start BNC, double click on '/Aplications/bnc.app'.
+
+
+
1.6 Configuration

+
+As a default, configuration files for running BNC on Unix/Linux/Mac OS X systems are saved in directory
+'${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'.
+The default configuration filename is 'BNC.bnc'.
+
+The default filename 'BNC.bnc' can be changed and the file content can easily be edited. On graphical user interfaces
+ it is possible to Drag & Drop a configuration file icon to start BNC (not on Mac OS X systems).
+ It is also possible to start and configure BNC via command line. Some configuration options can be changed on-the-fly.
+ See annexed 'Command Line Help' for a complete set of configuration options.
 
 
@@ -786,12 +875,12 @@
 
 
-
-GUI, input fields level
-Active configuration level
-Configuration file, disk level
+
+  GUI, input fields level
+  Active configuration level
+  Configuration file, disk level
 
 
 
-Figure 6: Management of configuration options in BNC:

+
Figure 6: Management of configuration options in BNC:

@@ -803,157 +892,141 @@ Configuration options are usually specified using GUI input fields (1) after launching BNC. When hitting the 'Start' button, configuration options are transferred one level down to become BNC's active configuration (2), allowing the program to begin its operation. Pushing the 'Stop' button ends data processing so that the user can finally terminate BNC through 'File'->'Quit'->'Save Options' which saves processing options in a configuration file to disk (3). It is important to understand that:

Active configuration options (2) are independent from GUI input fields and configuration file content.
Hence changing configuration options at GUI level (1) while BNC is already processing data does not influence a running job.
Editing configuration options at disk level (3) while BNC is already processing data does also not influence a running job. However, there are two exceptions which force BNC to update certain active options on-the-fly:

Pushing the 'Reread & Save Configuration' button lets BNC immediately reread its configuration from GUI input fields to make them active configuration options. Then BNC saves them on disk.
Specifying the 'Reread configuration' option lets BNC reread its configuration from disk at pre-defined intervals.

A specific BNC configuration can be started in 'no window' mode from scratch without a configuration file if options for the active configuration level (2) are provided via command line.

- -

1.6.1 Examples

- -

-BNC comes with a number of configuration examples which can be used on all operating systems. Copy the complete directory 'Example_Configs' which comes with the software to your disc. It includes sub-directories 'Input' and 'Output'. There are several ways to start BNC using one of the example configurations: -

-On graphical systems (except for Mac systems), you may use the computer mouse to 'drag' a configuration file icon and 'drop' it on top of BNC's program icon. +
Active configuration options (2) are independent from GUI input fields and configuration file content.
Hence changing configuration options at GUI level (1) while BNC is already processing data does not influence a running job.
Editing configuration options at disk level (3) while BNC is already processing data does also not influence a running job. However, there are two exceptions which force BNC to update certain active options on-the-fly:

Pushing the 'Reread & Save Configuration' button lets BNC immediately reread its configuration from GUI input fields to make them active configuration options. Then BNC saves them on disk.
Specifying the 'Reread configuration' option lets BNC reread its configuration from disk at pre-defined intervals.

A specific BNC configuration can be started in 'no window' mode from scratch without a configuration file if options for the active configuration level (2) are provided via command line.

+ +

1.6.1 Examples

+ +

+BNC comes with a number of configuration examples which can be used on all operating systems. +Copy the complete directory 'Example_Configs' which comes with the software to your disc. It includes sub-directories +'Input' and 'Output'. There are several ways to start BNC using one of the example configurations: +

On graphical systems (except for Mac systems), you may use the computer mouse to 'drag' a configuration file icon and 'drop' it on top of BNC's program icon.
You could also start BNC using a command line for naming a specific configuration file (suggested e.g. for Mac systems):
+ /Applications/bnc.app/Contents/MacOS/bnc --conf <configFileName>
On non-graphical systems or when running BNC in batch mode in the background you may start the program using a command line with a configuration file option in 'no window' mode (example for Windows systems):
+ bnc.exe --conf <configFileName> --nw

+Although it's not a must, we suggest that you always create BNC configuration files with filename extension '.bnc'. +

+ +

+We furthermore suggest for convenience reasons that you configure your system to automatically start BNC when you double-click a file with the filename extension '.bnc'. The following describes what to do on MS Windows systems to associate the BNC program to such configuration files: +

+ +

Right-click a file that has the extension '.bnc' and then click 'Open'. If the 'Open' command is not available, click 'Open With' or double-click the file.
Windows displays a dialog box that says that the system cannot open this file. The dialog box offers several options for selecting a program.
Click 'Select the program from a list', and then click 'OK'.
The 'Open With' dialog box is displayed. Click 'Browse', locate and then click the BNC program, and then click 'Open'.
Click to select the 'Always use the selected program to open this kind of file' check box.
Click 'OK'.

+ +

+Some of the presented example configurations contain a user ID 'Example' with a password 'Configs' for accessing a few + GNSS streams from public Ntrip Broadcasters. This free generic account is arranged for convenience reasons only. + Please be so kind as to replace the generic account details as well as the place holder's 'User' and 'Pass' by the + personal user ID and password you receive following an online registration through http://register.rtcm-ntrip.org. +

+ +

+Note that the account for an Ntrip Broadcaster is usually limited to pulling a specified maximum number of streams at the same time. As running some of the example configurations requires pulling several streams, it is suggested to make sure that you do not exceed your account's limits. +

+ +

+Make also sure that sub-directories 'Input' and 'Output' which are part of the example configurations exist on your system or adjust the affected example configuration options according to your needs. +

+ +

+Some BNC options require Antenna Phase Center variations as made available from IGS through so-called ANTEX files at ftp://igs.org/pub/station/general. +An example ANTEX file 'igs14.atx' is part of the BNC package for convenience. +

+ +

+The example configurations assume that no proxy protects your BNC host. Should a proxy be operated in front of BNC then +you need to introduce its name or IP and port number in the 'Network' panel. +

+ +

+(A) Working with Configuration Files

+You should be able to run all configuration file examples without changing contained options. However, configuration +'Upload.bnc' is an exception because it requires an input stream from a connected network engine. +

+ +

Configuration File 'RinexObs.bnc'
+Purpose: 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.
-You could also start BNC using a command line for naming a specific configuration file (suggested e.g. for Mac systems):
-/Applications/bnc.app/Contents/MacOS/bnc --conf <configFileName> -
-On non-graphical systems or when running BNC in batch mode in the background you may start the program using a command line with a configuration file option in 'no window' mode (example for Windows systems):
-bnc.exe --conf <configFileName> --nw -

-Although it's not a must, we suggest that you always create BNC configuration files with filename extension '.bnc'. -

-We furthermore suggest for convenience reasons that you configure your system to automatically start BNC when you double-click a file with the filename extension '.bnc'. The following describes what to do on MS Windows systems to associate the BNC program to such configuration files: -

Right-click a file that has the extension '.bnc' and then click 'Open'. If the 'Open' command is not available, click 'Open With' or double-click the file.
Windows displays a dialog box that says that the system cannot open this file. The dialog box offers several options for selecting a program.
Click 'Select the program from a list', and then click 'OK'.
The 'Open With' dialog box is displayed. Click 'Browse', locate and then click the BNC program, and then click 'Open'.
Click to select the 'Always use the selected program to open this kind of file' check box.
Click 'OK'.

-Some of the presented example configurations contain a user ID 'Example' with a password 'Configs' for accessing a few GNSS streams from public Ntrip Broadcasters. This free generic account is arranged for convenience reasons only. Please be so kind as to replace the generic account details as well as the place holder's 'User' and 'Pass' by the personal user ID and password you receive following an online registration through http://register.rtcm-ntrip.org. -

-Note that the account for an Ntrip Broadcaster is usually limited to pulling a specified maximum number of streams at the same time. As running some of the example configurations requires pulling several streams, it is suggested to make sure that you do not exceed your account's limits. -

-Make also sure that sub-directories 'Input' and 'Output' which are part of the example configurations exist on your system or adjust the affected example configuration options according to your needs. -

-Some BNC options require Antenna Phase Center variations as made available from IGS through so-called ANTEX files at ftp://igs.org/pub/station/general. An example ANTEX file 'igs14.atx' is part of the BNC package for convenience. -

-The example configurations assume that no proxy protects your BNC host. Should a proxy be operated in front of BNC then you need to introduce its name or IP and port number in the 'Network' panel. -

-(A) Working with Configuration Files

-You should be able to run all configuration file examples without changing contained options. However, configuration 'Upload.bnc' is an exception because it requires an input stream from a connected network engine. -

Configuration File 'RinexObs.bnc'
-Purpose: 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. -

Configuration File 'RinexEph.bnc'
Purpose: Convert a RTCM stream -with navigation messages to RINEX Navigation files. The configuration -pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the -real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation -files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time -Broadcast Ephemeris resources. -

http://igs.bkg.bund.de/ntrip/ephemeris

Configuration File 'BrdcCorr.bnc'
-Purpose: Save Broadcast Corrections from RTCM -SSR messages in hourly plain ASCII files. See -http://igs.bkg.bund.de/ntrip/orbits for various real-time IGS or EUREF -orbit/clock correction products. -

http://igs.bkg.bund.de/ntrip/orbits

Configuration File 'RinexConcat.bnc'
-Purpose: Concatenate several RINEX Version 3 files to -produce one compiled 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 check. -

Configuration File 'RinexQC.bnc'
-Purpose: Check the quality of a RINEX Version 3 -file by means of a multipath analysis. Results are saved on 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 check. -

Configuration File 'RTK.bnc'
-Purpose: Feed a serially connected receiver with -observations from a nearby reference station for conventional RTK. The stream is -scanned for RTCM messages. Message type numbers and latencies of incoming -observations are reported in BNC's logfile. -

Configuration File 'FeedEngine.bnc'
-Purpose: Feed a real-time GNSS engine with -observations from remote reference stations. The configuration pulls a single -stream from an Ntrip Broadcaster. You could also pull -several streams from different casters. Incoming observations are decoded, -synchronized, output through a local IP port and also saved into a file. Failure -and recovery thresholds are specified to inform about outages. -

Configuration File 'PPP.bnc'
-Purpose: 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. -

Configuration File 'PPPNet.bnc'
-Purpose: Precise -Point Positioning for several rovers or receivers from an entire network of -reference stations in one BNC job. The possible maximum number of PPP solutions -per job depends on the processing power of the hosting computer. This example -configuration reads two RTCM Version 3 observation streams, a Broadcast -Ephemeris stream and a stream with Broadcast Corrections. PPP Results for the -two stations are saved in PPP logfiles. -

Configuration File 'PPPQuickStart.bnc'
-Purpose: 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. -They are also output through IP port for real-time visualization with tools +Purpose: 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. They are also output through IP port for real-time visualization with tools like RTKPLOT. Positions are saved in the logfile. -

Configuration File 'PPPPostProc.bnc'
@@ -964,5 +1037,5 @@ logfile and contains coordinates derived over time following the implemented PPP filter algorithm. -

Configuration File 'PPPGoogleMaps.bnc'
@@ -973,14 +1046,12 @@ 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. -

Configuration File 'SPPQuickStartGal.bnc'
Purpose: Single Point Positioning in Quick-Start mode from observations of a static receiver with quite precisely known position. -The configuration uses GPS, GLONASS and Galileo observations and a Broadcast -Ephemeris stream. -

Configuration File 'SaveSp3.bnc'
@@ -990,5 +1061,5 @@ producing SP3 requires an ANTEX file because SP3 file content should be referred to CoM. -

Configuration File 'Sp3ETRF2000PPP.bnc'
@@ -1000,5 +1071,5 @@ precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000 reference coordinate. -

Configuration File 'Upload.bnc'
@@ -1011,5 +1082,5 @@ Antenna Phase Center (APC) and reference system IGS14. Orbits are saved on disk in SP3 format and clocks are saved in Clock RINEX format. -

Configuration File 'Combi.bnc'
@@ -1021,5 +1092,5 @@ Center of Mass (CoM). Its reference system is IGS14. Orbits are saved in SP3 format (referred to CoM) and clocks in Clock RINEX format. -

Configuration File 'CombiPPP.bnc'
@@ -1029,5 +1100,5 @@ coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements. -

Configuration File 'UploadEph.bnc'
@@ -1036,5 +1107,5 @@ encoded to RTCM Version 3 format and uploaded for the purpose of providing a Broadcast Ephemeris stream with an update rate of 5 seconds. -

Configuration File 'CompareSp3.bnc'
@@ -1043,5 +1114,5 @@ satellite R18 are excluded from this comparison. Comparison results are saved in a logfile. -

Configuration File 'Empty.bnc'
@@ -1052,5 +1123,8 @@

(B) Working with Command Line configuration options

Shell Script 'RinexConcat.sh'
@@ -1066,5 +1140,5 @@ several RINEX Version 3 files to produce one compiled file and edit the marker name in the file header. The sampling interval is set to 30 seconds. -

Shell Script 'RinexEph.sh'
@@ -1073,8 +1147,7 @@ pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation -files. BNC runs online until it's terminated after 10 seconds. See -http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast -Ephemeris resources. -

http://igs.bkg.bund.de/ntrip/ephemeris

Shell Script 'ScanLate.sh'
@@ -1083,5 +1156,5 @@ reported every 10 seconds. BNC runs online until it's terminated after 20 seconds. -

Shell Script 'RinexObs.sh'
@@ -1089,5 +1162,5 @@ streams to RINEX Observation files. The configuration pulls streams from two 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 files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources. BNC runs online until it's terminated after 30 seconds. @@ -1103,11 +1176,13 @@

1.7 Limitations

+ +

1.7 Limitations

-In Qt-based desktop environments (like KDE) on Unix/Linux platforms it may happen that you experience a crash of BNC at startup even when running the program in the background using the '-nw' option. This is a known bug most likely resulting from an incompatibility of Qt libraries in the environment and in BNC. Entering the command 'unset SESSION_MANAGER' before running BNC may help as a work-around. +In Qt-based desktop environments (like KDE) on Unix/Linux platforms it may happen that you experience a crash of BNC at startup +even when running the program in the background using the '-nw' option. This is a known bug most likely resulting +from an incompatibility of Qt libraries in the environment and in BNC. Entering the command 'unset SESSION_MANAGER' +before running BNC may help as a work-around.

@@ -1122,5 +1197,10 @@

-EUREF as well as IGS adhere to an open data policy. Streams are made available through Ntrip Broadcasters at www.euref-ip.net, www.igs-ip.net, products.igs-ip.net, and mgex.igs-ip.net free of charge to anyone for any purpose. There is no indication up until now how many users will need to be supported simultaneously. The given situation may develop in such a way that it might become difficult to serve all registered users at the same times. In cases where limited resources on the Ntrip Broadcaster side (software restrictions, bandwidth limitation etc.) dictates, first priority in stream provision will be given to stream providers followed by re-broadcasting activities and real-time analysis centers while access to others might be temporarily denied. +EUREF as well as IGS adhere to an open data policy. Streams are made available through Ntrip Broadcasters at +http://www.euref-ip.net/home, + http://www.igs-ip.net/home, + http://products.igs-ip.net/home and + http://mgex.igs-ip.net/home + free of charge to anyone for any purpose. There is no indication up until now how many users will need to be supported simultaneously. The given situation may develop in such a way that it might become difficult to serve all registered users at the same times. In cases where limited resources on the Ntrip Broadcaster side (software restrictions, bandwidth limitation etc.) dictates, first priority in stream provision will be given to stream providers followed by re-broadcasting activities and real-time analysis centers while access to others might be temporarily denied.
@@ -1132,5 +1212,5 @@

1.8 Looking Back

Looking Back

A basic function of BNC is streaming GNSS data over the open Internet using the Ntrip transport protocol. Employing IP streaming for satellite positioning goes back to the beginning of our century. Wolfgang Rupprecht has been the first person who developed TCP/IP server software under the acronym of DGPS-IP (Rupprecht 2000) and published it under GNU General Public License (GPL). While connecting marine beacon receivers to PCs with permanent access to the Internet he transmitted DGPS corrections in an RTCM format to support Differential GPS positioning over North America. With approximately 200 bits/sec the bandwidth requirement for disseminating beacon data was comparatively small. Each stream was transmitted over a unique combination of IP address and port. Websites informed about existing streams and corresponding receiver positions. @@ -1143,5 +1223,15 @@

-With the advent of Ntrip as an open streaming standard, BKG's interest turned towards taking advantage from free real-time access to GNSS observations. International Associations such as the IAG Reference Frame Sub Commissions for Africa (AFREF), Asia & Pacific (APREF), Europe (EUREF), North America (NAREF) Latin America & Caribbean (SIRGAS), and the International GNSS Service (IGS) maintain continental or even global GNSS networks with the majority of modern receivers supporting Ntrip stream upload. Through operating BKG's NtripCaster software, these networks became extremely valuable sources of real-time GNSS information. In 2005, this was the starting point for developing the 'BKG Ntrip Client' (BNC) as a multi-stream Open Source NtripClient that allows pulling hundreds of streams simultaneously from any number of NtripCaster installations world-wide. Decoding incoming RTCM streams and output observations epoch by epoch via IP port to feed a real-time GNSS network engine became BNC's first and foremost ability (Weber and Mervart 2009). Converting decoded streams to short high-rate RINEX files to assist near real-time applications became a welcome by-product right from the start of this development. +With the advent of Ntrip as an open streaming standard, BKG's interest turned towards taking advantage from free +real-time access to GNSS observations. International Associations such as the IAG Reference Frame Sub Commissions +for Africa (AFREF), Asia & Pacific (APREF), Europe (EUREF), North America (NAREF) Latin America & Caribbean (SIRGAS), +and the International GNSS Service (IGS) maintain continental or even global GNSS networks with the majority of modern +receivers supporting Ntrip stream upload. Through operating BKG's NtripCaster software, these networks became extremely +valuable sources of real-time GNSS information. In 2005, this was the starting point for developing the +'BKG Ntrip Client' (BNC) as a multi-stream Open Source NtripClient that allows pulling hundreds of streams +simultaneously from any number of NtripCaster installations world-wide. Decoding incoming RTCM streams and output +observations epoch by epoch via IP port to feed a real-time GNSS network engine became BNC's first and foremost +ability (Weber and Mervart 2009). Converting decoded streams to short high-rate RINEX files to assist near real-time +applications became a welcome by-product right from the start of this development.

@@ -1156,8 +1246,8 @@

-In February 2014 the overall responsibility at BKG for the concept and realization of BNC was handed over from Georg Weber to Axel Rülke. He is in charge now for guiding the application and further evolution of the software in view of appearing new satellite navigation systems and services. -

- -

2. Settings Details

+In February 2014 the overall responsibility at BKG for the concept and realization of BNC was handed over from Georg Weber to Axel RÃ¼lke. He is in charge now for guiding the application and further evolution of the software in view of appearing new satellite navigation systems and services. +

+ +

2. Settings Details

The general documentation approach is to create a separate chapter for each processing option in a sequence which follows the layout of BNC's Graphical User Interface (GUI). The advantage is that searching for help by means of the document's Table of Contents (TOC) is quite convenient. A rather comprehensive number of TOC entries is the accepted downside of this approach. @@ -1167,49 +1257,40 @@

2.1 Top Menu Bar

The top menu bar allows selecting a font for the BNC windows, save configured options, or quit the program execution. It also provides access to the program's documentation.

2.1.1 File

The 'File' button lets you

Select an appropriate font.
-Use smaller font size if the BNC main window exceeds the size of your screen. -
Reread and save selected options in configuration file.
-When using 'Reread & Save Configuration' while BNC is already processing data, some configuration options become immediately effective on-the-fly without interrupting uninvolved threads while all of them are saved on disk. See section 'Reread Configuration' for a list of on-the-fly changeable configuration options. -
Quit the BNC program. -

- -

2.1.2 Help

Select an appropriate font.
+ Use smaller font size if the BNC main window exceeds the size of your screen.

Reread and save selected options in configuration file.
+ When using 'Reread & Save Configuration' while BNC is already processing data, some configuration options + become immediately effective on-the-fly without interrupting uninvolved threads while all of them are saved on + disk. See section 'Reread Configuration' for a list of on-the-fly changeable configuration options.

Quit the BNC program.

+ +

2.1.2 Help

The 'Help' button provides access to

-Help contents.
-You may keep the 'Help Contents' window open while configuring BNC. -
-A 'Flow Chart' showing BNC linked to a real-time GNSS network engine such as RTNET. -
-General information about BNC.
-Close the 'About BNC' window to continue working with BNC. -

- -

2.2 Network

Help contents.
You may keep the 'Help Contents' window open while configuring BNC.

A 'Flow Chart' showing BNC linked to a real-time GNSS network engine such as RTNET.

General information about BNC.
Close the 'About BNC' window to continue working with BNC.

+ +

2.2 Network

You may need to specify a proxy when running BNC in a protected network. You may also like to use the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure Ntrip communication over the Internet.

2.2.1 Proxy - Usage in a protected LAN

If you are running BNC within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you do not know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.

@@ -1218,5 +1299,5 @@

2.2.2 SSL - Transport Layer Security

Communication with an Ntrip Broadcaster over Secure Sockets Layer (SSL) as well as the download of RINEX skeleton files when available from HTTPS websites requires the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out http://software.rtcm-ntrip.org/wiki/Certificates for a list of known Ntrip Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved Ntrip Broadcaster.

SSL communication may involve queries coming from the Ntrip Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab especially when self-signed SSL certificates are used. Example: @@ -1239,12 +1320,12 @@

Figure 7: BNC's 'Network' panel configured to ignore eventually occurring SSL error messages

- -

2.3 General

Figure 7: BNC's 'Network' panel configured to ignore eventually occurring SSL error messages

+ +

2.3 General

The following defines general settings for BNC's logfile, file handling, reconfiguration on-the-fly, and auto-start.

2.3.1 Logfile - optional

Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' for the current date. This leads to series of daily logfiles when running BNC continuously. Message logs cover the communication status between BNC and the Ntrip Broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a file. @@ -1274,10 +1355,10 @@ -

2.3.2 Append Files - optional

When BNC is started, new files are created by default and existing files with the same name will be overwritten. However, users might want to append existing files following a restart of BNC, a system crash or a BNC crash. Tick 'Append files' to continue with existing files and keep what has been recorded so far. Note that option 'Append files' affects all types of files created by BNC.

2.3.3 Reread Configuration - optional

When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that, you force the program to reread parts of its configuration in pre-defined intervals from disk. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in-between edited options become effective without interrupting uninvolved threads. @@ -1289,14 +1370,14 @@

'mountPoints' to change the selection of streams to be processed, see section 'Streams';
'outWait' to change the 'Wait for full obs epoch' option, see section 'Feed Engine';
'outSampl' to change the 'Sampling' option, see section 'Feed Engine';
'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format.

- -

2.3.4 Auto Start - optional

'mountPoints' to change the selection of streams to be processed, see section 'Streams'

'outWait' to change the 'Wait for full obs epoch' option, see section 'Feed Engine'

'outSampl' to change the 'Sampling' option, see section 'Feed Engine'

'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format

+ +

2.3.4 Auto Start - optional

You may like to auto-start BNC at startup time in window mode with pre-assigned configuration options. This may be required e.g. immediately after booting your system. Tick 'Auto start' to supersede the usage of the 'Start' button. Make sure that you maintain a link to BNC for that in your Autostart directory (Windows systems) or call BNC in a script below directory /etc/init.d (Unix/Linux/Mac OS X systems). @@ -1306,5 +1387,5 @@

2.3.5 Raw Output File - optional

BNC can save all data coming in through various streams in one daily file. The information is recorded in the specified 'Raw output file' in the received order and format. This feature allows a BNC user to run the PPP option offline with observations, Broadcast Corrections, and Broadcast Ephemeris being read from a previously saved file. It supports the offline repetition of a real-time situation for debugging purposes (Record & Replay functionality) and is not meant for post processing. @@ -1323,5 +1404,5 @@

2.4 RINEX Observations

Observations will be converted to RINEX if they come in either RTCM Version 2 or RTCM Version 3 format. Depending on the RINEX version and incoming RTCM message types, files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS, and/or BDS (BeiDou). In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000' or left blank. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system. @@ -1349,7 +1430,7 @@

Figure 8: BNC translating incoming observation streams to 15 min RINEX Version 3 Observation files

- -

2.4.1 RINEX Filenames

Figure 8: BNC translating incoming observation streams to 15 min RINEX Version 3 Observation files

+ +

2.4.1 RINEX Filenames

The default for RINEX filenames in BNC follows the convention of RINEX Version 2. However, the software provides options to alternatively follow the filename convention of RINEX Version 3. RINEX Version 2 filenames are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4-Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named

@@ -1388,13 +1469,13 @@

Left:

BNC in graphics mode; active configuration options are introduced through GUI input fields and finally saved on disk

- - - - - - - - - + + + + + + + + +

Filename Parameter	# Char.	Meaning
Name	9	Site, station and country code
S	1	Data source
Start Time	11	YYYYDDDHHMM
Period	3	File period
Obs. Freq.	3	Observation frequency
Content	2	Content type
Format	3	File format
Compression	2-3	Compression method (optional)
Filename Parameter	# Char.	Meaning
Name	9	Site, station and country code
S	1	Data source
Start Time	11	YYYYDDDHHMM
Period	3	File period
Obs. Freq.	3	Observation frequency
Content	2	Content type
Format	3	File format
Compression	2-3	Compression method (optional)

@@ -1409,22 +1490,29 @@

2.4.2 Directory - optional

Here you can specify the path to where the RINEX Observation files will be stored. If the specified directory does not exist, BNC will not create RINEX Observation files. Default value for 'Directory' is an empty option field, meaning that no RINEX Observation files will be written.

2.4.3 File Interval - mandatory if 'Directory' is set

Select the length of the RINEX Observation file to be generated. The default value is 15 minutes.

2.4.4 Sampling - mandatory if 'Directory' is set

Select the RINEX Observation sampling interval in seconds. A value of zero '0' tells BNC to store all received epochs into RINEX. This is the default value.

2.4.5 Skeleton Extension - optional

-Whenever BNC starts to generate RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. An HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See http://www.epncb.oma.be:80/stations/log/skl/brus.skl for an example of a public RINEX header skeleton file for EPN station Brussels. Note that the download of RINEX skeleton files from HTTPS websites requires the exchange of client and/or server certificates. Clarify 'SSL' options offered through panel 'Network' for details. +

2.4.5 Skeleton Extension - optional

+Whenever BNC starts to generate RINEX Observation files (and then once every day at midnight), it first tries to +retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived +from sitelogs. An HTTP or HTTPS link to a directory containing these skeleton files may be available through data +field number 7 of the affected NET record in the source-table. +See http://www.epncb.oma.be:80/stations/log/skl/brus.skl +for an example of a public RINEX header skeleton file for EPN station Brussels. Note that the download of RINEX +skeleton files from HTTPS websites requires the exchange of client and/or server certificates. +Clarify 'SSL' options offered through panel 'Network' for details.

@@ -1445,30 +1533,27 @@ Note the following regulations regarding personal RINEX header skeleton files:

If such a file exists in the 'RINEX directory', the corresponding public RINEX header skeleton file is ignored. The RINEX header is generated solely from the content of the personal skeleton.
Personal skeletons should contain a complete first header record of type -
- RINEX VERSION / TYPE
They should then contain an empty header record of type -
- PGM / RUN BY / DATE
-BNC will complete this line and include it in the RINEX file header.
They should further contain complete header records of type -
- MARKER NAME -
- OBSERVER / AGENCY -
- REC # / TYPE / VERS -
- ANT # / TYPE -
- APPROX POSITION XYZ -
- ANTENNA: DELTA H/E/N -
- WAVELENGTH FACT L1/2 (RINEX Version 2) -
- SYS / # / OBS TYPES (for RINEX Version 3 files, will be ignored in Version 2 files)
They may contain any other optional complete header record as defined in the RINEX documentation.
They should also contain an empty header record of type -
- # / TYPES OF OBSERV (only RINEX Version 2, will be ignored when in Version 3 files) -
BNC will include these lines in the final RINEX file header together with an additional -
- COMMENT -
line describing the source of the stream.
They should finally contain an empty last header record of type -
- END OF HEADER
They must not contain a header record of type -
- TIME OF FIRST OBS
If such a file exists in the 'RINEX directory', the corresponding public RINEX header skeleton file is ignored. The RINEX header is generated solely from the content of the personal skeleton.
Personal skeletons should contain a complete first header record of type
+ - RINEX VERSION / TYPE
They should then contain an empty header record of type +
- PGM / RUN BY / DATE
BNC will complete this line and include it in the RINEX file header.
They should further contain complete header records of type +
- MARKER NAME +
- OBSERVER / AGENCY +
- REC # / TYPE / VERS +
- ANT # / TYPE +
- APPROX POSITION XYZ +
- ANTENNA: DELTA H/E/N +
- WAVELENGTH FACT L1/2 (RINEX Version 2) +
- SYS / # / OBS TYPES (for RINEX Version 3 files, will be ignored in Version 2 files)
They may contain any other optional complete header record as defined in the RINEX documentation.
They should also contain an empty header record of type +
- # / TYPES OF OBSERV (only RINEX Version 2, will be ignored when in Version 3 files) +
BNC will include these lines in the final RINEX file header together with an additional +
- COMMENT +
line describing the source of the stream.
They should finally contain an empty last header record of type +
- END OF HEADER
They must not contain a header record of type
- TIME OF FIRST OBS

@@ -1503,5 +1588,5 @@

2.4.6 Skeleton Mandatory - optional

Tick check box 'Skeleton mandatory' in case you want that RINEX files are only produced when skeleton files are available for BNC. If no skeleton file is available for a particular source, then no RINEX observation file will be produced from the affected stream. @@ -1510,5 +1595,5 @@

2.4.7 Script - optional

Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that, specify the full path to such script/batch file. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac OS X systems). @@ -1521,8 +1606,8 @@

2.4.8 Version 2 - optional

GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program is explicitly required to produce data files in RINEX Version 2 format: -

When saving the content of incoming observation streams in RINEX Version 2 files as described in this section.

When editing or concatenating RINEX 3 files to save them in Version 2 format, see section on 'RINEX Editing & QC'.

@@ -1557,5 +1642,5 @@

2.4.9 Version 3 - optional

The default format for RINEX Observation files is RINEX Version 2.11. Select RINEX 'Version 3' if you would like to save RTCM Version 3 observation streams in RINEX Version 3.03 format. @@ -1566,5 +1651,5 @@

2.4.10 Version 3 Filenames - optional

Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. @@ -1573,5 +1658,5 @@

2.5 RINEX Ephemeris

Broadcast Ephemeris can be saved in RINEX Navigation files when received e.g. via RTCM Version 3 message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (BDS/BeiDou, tentative message number). The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'. @@ -1598,15 +1683,15 @@

2.5.1 Directory - optional

Specify a path for saving Broadcast Ephemeris data in RINEX Navigation files. If the specified directory does not exist, BNC will not create RINEX Navigation files. Default value for Ephemeris 'Directory' is an empty option field, meaning that no RINEX Navigation files will be created.

2.5.2 Interval - mandatory if 'Directory' is set

Select the length of RINEX Navigation files. The default value is '1 day'.

2.5.3 Port - optional

BNC can output Broadcast Ephemeris in RINEX Version 3 format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no ASCII ephemeris output via IP port is generated. @@ -1616,5 +1701,5 @@

2.5.4 Version - optional

Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris data in RINEX Version 3.03 format. @@ -1624,5 +1709,5 @@

2.5.5 Version 3 Filenames - optional

Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. @@ -1632,24 +1717,24 @@

Figure 9: BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files

- -

2.6 RINEX Editing & QC

Figure 9: BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files

+ +

2.6 RINEX Editing & QC

Besides stream conversion from RTCM to RINEX, BNC allows editing RINEX files or concatenate their content. RINEX Observation and Navigation files can be handled. BNC can also carry out a RINEX file Quality Check. In summary and besides Stream Translation, this functionality in BNC covers

File Editing and concatenation
File Quality Check

Multipath analysis sky plots
Signal-to-noise ratio sky plots
Satellite availability plots
Satellite elevation plots
PDOP plots

File Editing and concatenation
File Quality Check

Multipath analysis sky plots
Signal-to-noise ratio sky plots
Satellite availability plots
Satellite elevation plots
PDOP plots

and hence follows UNAVCO's famous TEQC program (see Estey and Meertens 1999). The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License with full GUI support and graphics output.

2.6.1 Action - optional

Select an action. Options are 'Edit/Concatenate' and 'Analyze'.

@@ -1659,5 +1744,5 @@

2.6.2 Input Files - mandatory

Specify full path to input RINEX Observation file(s), and
@@ -1671,10 +1756,10 @@

2.6.3 Output Files - optional if 'Action' is set to 'Edit/Concatenate'

If 'Edit/Concatenate' is selected, specifying the full path to output RINEX Observation file(s) and specifying the full path to output RINEX Navigation file(s) is optional. Default are empty option fields, meaning that no RINEX files will be saved on disk.

2.6.4 Logfile - optional

Specify the name of a logfile to save information on RINEX file Editing/Concatenation or Analysis. Default is an empty option field, meaning that no logfile will be saved. @@ -1896,5 +1981,5 @@

2.6.5 Plots for Signals - mandatory if 'Action' is set to 'Analyze'

Multipath and signal-to-noise sky plots as well as plots for satellite availability, elevation and PDOP are produced per GNSS system and frequency with the multipath analysis based on CnC observation types (n = band / frequency). The 'Plots for signals' option lets you exactly specify the observation signals to be used for that and also enables the plot production. You can specify the navigation system (C = BDS, E = Galileo, G = GPS, J = QZSS, R = GLONASS, S = SBAS), the frequency, and the tracking mode or channel as defined in RINEX Version 3. Specifications for frequency and tracking mode or channel must be separated by ampersand character '&'. Specifications for each navigation systems must be separated by blank character ' '. The following string is an example for option field 'Plots of signals': @@ -1914,10 +1999,10 @@

2.6.6 Directory for Plots - optional if 'Action' is set to 'Analyze'

If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. Filenames will be composed from the RINEX input filename(s) plus suffix 'PNG' to indicate the plot file format in use. Default is an empty option field, meaning that plots will not be saved on disk.

2.6.7 Set Edit Options - mandatory if 'Action' is set to 'Edit/Concatenate'

Once the 'Edit/Concatenate' action is selected, you have to 'Set Edit Options'. BNC lets you specify the RINEX version, a signal priority list when mapping RINEX Version 3 to Version 2, the sampling interval, begin and end of file, operator, observation types, comment lines, and marker, antenna, receiver details. Note that some of the specifications for editing and concatenation are only meaningful for RINEX Observation files but not for RINEX Navigation files.

@@ -1929,19 +2014,19 @@

The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting RINEX Version 3 to Version 2 Observation files, BNC is forced to somehow map signals with attributes to signals without attributes although this cannot be done in one-to-one correspondence. Hence we introduce a 'Version 2 Signal Priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2, see details in section 'RINEX Observations/Version 2'. Signal priorities can be specified as equal for all systems, as system specific or as system and frequency specific. For example:

'CWPX_?' (General signal priorities valid for all GNSS)
'C:IQX I:ABCX' (System specific signal priorities for BDS and IRNSS)
'G:12&PWCSLXYN G:5&IQX R:12&PC R:3&IQX' (System and frequency specific signal priorities)

-The default 'Signal priority' list is defined as follows: -

'G:12&PWCSLXYN_ G:5&IQX_ R:12&PC_ R:3&IQX_ E:16&BCX_ E:578&IQX_ J:1&SLXCZ_ J:26&SLX_ J:5&IQX_ C:IQX_ I:ABCX_ S:1&C_ S:5&IQX_'

When converting RINEX Version 2 to Version 3 Observation files, the tracking mode or channel information in the (last character out of the 3-character) observation code is left blank if unknown. This is a compromise, knowing that it is not in accordance with the RINEX Version 3 documentation.
The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting RINEX Version 3 to Version 2 Observation files, BNC is forced to somehow map signals with attributes to signals without attributes although this cannot be done in one-to-one correspondence. Hence we introduce a 'Version 2 Signal Priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2, see details in section 'RINEX Observations/Version 2'. Signal priorities can be specified as equal for all systems, as system specific or as system and frequency specific. For example:

'CWPX_?' (General signal priorities valid for all GNSS)
'C:IQX I:ABCX' (System specific signal priorities for BDS and IRNSS)
'G:12&PWCSLXYN G:5&IQX R:12&PC R:3&IQX' (System and frequency specific signal priorities)

+ The default 'Signal priority' list is defined as follows: +

'G:12&PWCSLXYN_ G:5&IQX_ R:12&PC_ R:3&IQX_ E:16&BCX_ E:578&IQX_ J:1&SLXCZ_ J:26&SLX_ J:5&IQX_ C:IQX_ I:ABCX_ S:1&C_ S:5&IQX_'

When converting RINEX Version 2 to Version 3 Observation files, the tracking mode or channel information in the (last character out of the 3-character) observation code is left blank if unknown. This is a compromise, knowing that it is not in accordance with the RINEX Version 3 documentation.

@@ -1964,22 +2049,22 @@

Figure 10: Example for BNC's 'RINEX Editing Options' window

Figure 11: Example for RINEX file concatenation with BNC

Figure 12: Example for creating RINEX quality check analysis graphics output with BNC

Figure 13: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC

Figure 14: Sky plot examples for multipath, part of RINEX quality check analysis with BNC

Figure 15: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC

- -

2.6.8 Command Line, No Window - optional

Figure 15: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC

+ +

2.6.8 Command Line, No Window - optional

BNC applies options from the configuration file but allows updating every one of them on the command line while the content of the configuration file remains unchanged, see section on 'Command Line Options'. Note the following syntax for Command Line Interface (CLI) options: @@ -2064,5 +2149,5 @@ -

2.7 SP3 Comparison

2.6.7 SP3 Comparison

BNC allows to compare the contents of two files with GNSS orbit and clock data in SP3 format. SP3 ASCII files basically contain a list of records over a certain period of time. Each record carries a time tag, the XYZ position of the satellite's Center of Mass at that time and the corresponding satellite clock value. Both SP3 files may contain some records for different epochs. If so, then BNC only compares records for identical epochs. BNC accepts that a specific GNSS system or a specific satellite is only available from one of the SP3 files. Note that BNC does not interpolate orbits when comparing SP3 files. @@ -2072,18 +2157,18 @@

2.7.1 Input SP3 Files - optional

Specify the full paths of two SP3 files, separate them by comma.

2.7.2 Exclude Satellites - optional

You may want to exclude one or more satellites in your SP3 files from the comparison. Or you may like to exclude all satellites of a specific GNSS system from the comparison. The following are example strings to be entered for excluding satellites from the comparison.

G05,G31 (excluding GPS satellites with PRN 5 and 31)
G (excluding all GPS satellites)
R (excluding all GLONASS satellites)
R12,R24 (excluding GLONASS satellites with slot number 12 and 24)
G04,G31,R (excluding GPS satellites with PRN 4 and 31 as well as all GLONASS satellites)
G05,G31 (excluding GPS satellites with PRN 5 and 31)
G (excluding all GPS satellites)
R (excluding all GLONASS satellites)
R12,R24 (excluding GLONASS satellites with slot number 12 and 24)
G04,G31,R (excluding GPS satellites with PRN 4 and 31 as well as all GLONASS satellites)

@@ -2092,5 +2177,5 @@

2.7.3 Logfile - mandatory if 'Input SP3 Files' is set

Specify a logfile name to save results of the SP3 file comparison. @@ -2175,7 +2260,7 @@

Figure 16: Example for comparing two SP3 files with satellite orbit and clock data using BNC

- -

2.8 Broadcast Corrections

Figure 16: Example for comparing two SP3 files with satellite orbit and clock data using BNC

+ +

2.8 Broadcast Corrections

Differential GNSS and RTK operation using RTCM streams is currently based on corrections and/or raw measurements from single or multiple reference stations. This approach to differential positioning uses 'observation space' information. The representation with the RTCM standard can be called 'Observation Space Representation' (OSR). @@ -2188,19 +2273,19 @@

SSR, Step I:

Orbit corrections to Broadcast Ephemeris
Clock corrections to Broadcast Ephemeris
High-rate clock corrections to Broadcast Ephemeris
Combined orbit and clock corrections to Broadcast Ephemeris
User Range Accuracy (URA)
High Rate User Range Accuracy (HR URA)
Code biases

SSR, Step II:

Phase biases
Vertical Total Electron Content (VTEC)

SSR, Step I:

Orbit corrections to Broadcast Ephemeris
Clock corrections to Broadcast Ephemeris
High-rate clock corrections to Broadcast Ephemeris
Combined orbit and clock corrections to Broadcast Ephemeris
User Range Accuracy (URA)
High Rate User Range Accuracy (HR URA)
Code biases

SSR, Step II:

Phase biases
Vertical Total Electron Content (VTEC)

@@ -2253,33 +2338,33 @@

Special character '>' is the first character in each 'Epoch Record' (as we have it in RINEX Version 3)
SSR message or topic descriptor, valid descriptors are:
ORBIT, CLOCK, CODE_BIAS, PHASE_BIAS, or VTEC
Year, GPS time
Month, GPS time
Day, GPS time
Hour, GPS time
Minute, GPS time
Second, GPS time
SSR message update interval indicator

0 = 1 sec
1 = 2 sec
2 = 5 sec
3 = 10 sec
4 = 15 sec
5 = 30 sec
6 = 60 sec
7 = 120 sec
8 = 240 sec
9 = 300 sec
10 = 600 sec
11 = 900 sec
12 = 1800 sec
13 = 3600 sec
14 = 7200 sec
15 = 10800 sec

Number of following records in this block
Mountpoint, source/stream indicator
Special character '>' is the first character in each 'Epoch Record' (as we have it in RINEX Version 3)
SSR message or topic descriptor, valid descriptors are:
ORBIT, CLOCK, CODE_BIAS, PHASE_BIAS, or VTEC
Year, GPS time
Month, GPS time
Day, GPS time
Hour, GPS time
Minute, GPS time
Second, GPS time
SSR message update interval indicator

0 = 1 sec
1 = 2 sec
2 = 5 sec
3 = 10 sec
4 = 15 sec
5 = 30 sec
6 = 60 sec
7 = 120 sec
8 = 240 sec
9 = 300 sec
10 = 600 sec
11 = 900 sec
12 = 1800 sec
13 = 3600 sec
14 = 7200 sec
15 = 10800 sec

Number of following records in this block
Mountpoint, source/stream indicator

Each of the following 'satellite records' in such a block carries information for one specific satellite. Undefined parameters in the 'satellite records' could be set to zero "0.000". @@ -2363,13 +2448,13 @@ Records in this block provide the following satellite specific information:

GNSS Indicator and Satellite Vehicle Pseudo Random Number
Number of Code Biases, succeeded by code specific information:

Indicator to specify the signal and tracking mode
Code Bias [m]
Indicator to specify the signal and tracking mode
Code Bias [m]
etc.

GNSS Indicator and Satellite Vehicle Pseudo Random Number
Number of Code Biases, succeeded by code specific information:

Indicator to specify the signal and tracking mode
Code Bias [m]
Indicator to specify the signal and tracking mode
Code Bias [m]
etc.

@@ -2404,15 +2489,15 @@ Following records provide satellite specific information:

GNSS Indicator and Satellite Vehicle Pseudo Random Number
Yaw angle [°], restricted to [0°... 360°]
Yaw rate [°/s]
Number of phase biases in this record, succeeded by phase specific information:

Signal and tracking mode indicator
Phase bias [m]
Signal integer indicator
Signal wide-lane integer indicator
Signal discontinuity counter

GNSS Indicator and Satellite Vehicle Pseudo Random Number
Yaw angle [°], restricted to [0°... 360°]
Yaw rate [°/s]
Number of phase biases in this record, succeeded by phase specific information:

Signal and tracking mode indicator
Phase bias [m]
Signal integer indicator
Signal wide-lane integer indicator
Signal discontinuity counter

@@ -2442,26 +2527,26 @@ The second record in this block provides four parameters:

Layer number
Maximum degree of spherical harmonics
Maximum order of spherical harmonics
Height of ionospheric layer [m]
Layer number
Maximum degree of spherical harmonics
Maximum order of spherical harmonics
Height of ionospheric layer [m]

Subsequent records in this block provide the following information:

Spherical harmonic coefficients C and S, sorted by degree and order (0 to maximum)

- -

2.8.1 Directory, ASCII - optional

Spherical harmonic coefficients C and S, sorted by degree and order (0 to maximum)

+ +

2.8.1 Directory, ASCII - optional

Specify a directory for saving Broadcast Corrections in files. If the specified directory does not exist, BNC will not create Broadcast Correction files. Default value for Broadcast Correction 'Directory' is an empty option field, meaning that no Broadcast Correction files will be created.

2.8.2 Interval - mandatory if 'Directory, ASCII' is set

Select the length of the Broadcast Correction files. The default value is '1 day'.

2.8.3 Port - optional

BNC can output epoch by epoch synchronized Broadcast Corrections in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no Broadcast Correction output via IP port is generated. @@ -2539,7 +2624,7 @@

Figure 17: Example for pulling, saving and output of Broadcast Corrections using BNC

- -

2.9 Feed Engine

Figure 17: Example for pulling, saving and output of Broadcast Corrections using BNC

+ +

2.9 Feed Engine

@@ -2559,5 +2644,5 @@

Table 2: Contents and format of synchronized output of observations feeding a GNSS engine

@@ -3181,11 +3265,11 @@

- - - + + +

CUT000AUS_U_20152920000_01D_01S.nmea	NMEA filename, suffix 'nmea'
CUT000AUS_U_20152920000_01D_01S.ppp	PPP logfile name, suffix 'ppp'
CUT000AUS_U_20152920945_15M_01S.tra	SINEX Troposphere filename, suffix 'tra'
CUT000AUS_U_20152920000_01D_01S.nmea	NMEA filename, suffix 'nmea'
CUT000AUS_U_20152920000_01D_01S.ppp	PPP logfile name, suffix 'ppp'
CUT000AUS_U_20152920945_15M_01S.tra	SINEX Troposphere filename, suffix 'tra'

2.13.1.9 Logfile Directory - optional

Essential PPP results are shown in the 'Log' tab on the bottom of BNC's main window. Depending on the processing options, the following values are presented about once per second (example): @@ -3304,21 +3388,22 @@ Depending on selected processing options you find 'GPS Time' stamps (yyyy-mm-dd_hh:mm:ss.sss) followed by

SATNUM: Number of satellites per GNSS,
RES: Code and phase residuals for contributing GNSS systems in [m]
Given per satellite with cIF/lIF for ionosphere-free linear combination of code/phase observations,
CLK: Receiver clock errors in [m],
TRP: A priori and correction values of tropospheric zenith delay in [m], -
OFFGLO: Time offset between GPS time and GLONASS time in [m], -
OFFGAL: Time offset between GPS time and Galileo time in [m], -
OFFBDS: Time offset between GPS time and BDS time in [m], -
AMB: L3 biases, also known as 'floated ambiguities'
Given per satellite with 'nEpo' = number of epochs since last ambiguity reset, -
MOUNTPOINT: Here 'CUT07' with XYZ position in [m] and dN/dE/dU in [m] for North, East, and Up displacements compared to a priori marker coordinates.
SATNUM: Number of satellites per GNSS,
RES: Code and phase residuals for contributing GNSS systems in [m]
Given per satellite with cIF/lIF for ionosphere-free linear combination of code/phase observations,
CLK: Receiver clock errors in [m],
TRP: A priori and correction values of tropospheric zenith delay in [m], +
OFFGLO: Time offset between GPS time and GLONASS time in [m], +
OFFGAL: Time offset between GPS time and Galileo time in [m], +
OFFBDS: Time offset between GPS time and BDS time in [m], +
AMB: L3 biases, also known as 'floated ambiguities'
Given per satellite with 'nEpo' = number of epochs since last ambiguity reset, +
MOUNTPOINT: Here 'CUT07' with XYZ position in [m] and dN/dE/dU in [m] for North, East, and Up displacements compared to a priori marker coordinates.

Estimated parameters are presented together with their formal errors as derived from the implemented filter. The PPP algorithm includes outlier and cycle slip detection.

Default value for 'Logfile directory' is an empty option field, meaning that you do not want to save daily PPP logfiles on disk. If a specified directory does not exist, BNC will not create PPP logfiles.

2.13.1.10 NMEA Directory - optional

You can specify a 'NMEA directory' to save daily NMEA files with Point Positioning results recorded as NMEA sentences. Such sentences are usually generated about once per second with pairs of @@ -3326,6 +3411,6 @@

GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus
GPRMC sentences which mainly carry date and time information.
GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus
GPRMC sentences which mainly carry date and time information.

@@ -3361,5 +3446,5 @@

2.13.1.11 SNX TRO Directory - optional

BNC estimates the tropospheric delay according to equation @@ -3371,5 +3456,5 @@

-You can specify a 'SNX TRO Directory' for saving SINEX Troposphere files on disk, see https://igscb.jpl.nasa.gov/igscb/data/format/sinex_tropo.txt for a documentation of the file format. Note that receiver type information for these files must be provided through the coordinates file described in section 'Coordinates file'. The following is an example for a troposphere file content: +You can specify a 'SNX TRO Directory' for saving SINEX Troposphere files on disk, see https://igscb.jpl.nasa.gov/igscb/data/format/sinex_tropo.txt for a documentation of the file format. Note that receiver type information for these files must be provided through the coordinates file described in section 'Coordinates file'. The following is an example for a troposphere file content:

2.13.1.11.1 Interval - mandatory if 'SINEX TRO Directory' is set

Select the length of SINEX Troposphere files.

Default 'Interval' for saving SINEX Troposphere files on disk is '1 day'.

2.13.1.11.2 Sampling - mandatory if 'SINEX TRO Directory' is set

Select a 'Sampling' rate in seconds for saving troposphere parameters. @@ -3451,22 +3537,24 @@

2.13.1.11.3 Analysis Center - Mandatory if 'SINEX TRO Directory' is set

Specify a 3-character abbreviation describing you as the generating Analysis Center (AC) in your SINEX troposphere files. String 'BKG' is an example.

2.13.1.11.4 Solution ID - Mandatory if 'SINEX TRO Directory' is set

Specify a 4-character solution ID to allow a distingtion between different solutions per AC. String '0001' is an example.

2.13.2 PPP (2): Processed Stations

This panel allows to enter parameters specific to each PPP process or thread. Individual sigmas for a priori coordinates and a noise for coordinate variations over time can be introduced. Furthermore, a sigma for model-based troposphere estimates and the corresponding noise for troposphere variations can be specified. Finally, local IP server ports can be defined for output of NMEA streams carrying PPP results.

BNC offers to create a table with one line per PPP process or thread to specify station-specific parameters. Hit the 'Add Station' button to create the table or add a new line to it. To remove a line from the table, highlight it by clicking it and hit the 'Delete Station' button. You can also remove multiple lines simultaneously by highlighting them using +Shift or +Ctrl.

BNC will simultaneously produce PPP solutions for all stations listed in the 'Station' column of this table. @@ -3474,42 +3562,42 @@

Figure 23: Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization

- -

2.13.2.1 Station - mandatory

Figure 23: Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization

+ +

2.13.2.1 Station - mandatory

Hit the 'Add Station' button, double click on the 'Station' field, then specify an observation's mountpoint from the 'Streams' section or introduce the 4-character Station ID of your RINEX observation file and hit Enter. BNC will only produce PPP solutions for stations listed in this table.

2.13.2.2 Sigma North/East/Up - mandatory

Enter sigmas in meters for the initial coordinate components. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (e.g. 0.01) when starting for example from a station with a well-known position in so-called Quick-Start mode.

2.13.2.3 Noise North/East/Up - mandatory

Enter a white 'Noise' in meters for estimated coordinate components. A value of 100.0 (default) may be appropriate when considering possible sudden movements of a rover.

2.13.2.4 Tropo Sigma - mandatory

Enter a sigma in meters for the a priori model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice.

2.13.2.5 Tropo Noise - mandatory

Enter a white 'Noise' in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour.

2.13.2.6 NMEA Port - optional

Specify the IP port number of a local port where Point Positioning results become available as NMEA sentences. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA sentences via IP port. Note that NMEA file output and NMEA IP port output are the same.

-Note also that Tomoji Takasu has written a program named RTKPLOT for visualizing NMEA sentences from IP ports or files. It is available from http://www.rtklib.com and compatible with the NMEA file and port output of BNC's 'PPP' client option. -

-Furthermore, NASA's 'World Wind' software (see http://worldwindcentral.com/wiki/NASA_World_Wind_Download) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from http://worldwindcentral.com/wiki/GPS_Tracker for that. The 'Word Wind' map resolution is not meant for showing centimeter level details. -

- -

2.13.3 PPP (3): Processing Options

+Note also that Tomoji Takasu has written a program named RTKPLOT for visualizing NMEA sentences from IP ports or files. It is available from

http://www.rtklib.com

+Furthermore, NASA's 'World Wind' software (see http://worldwindcentral.com/wiki/NASA_World_Wind_Download) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from http://worldwindcentral.com/wiki/GPS_Tracker for that. The 'Word Wind' map resolution is not meant for showing centimeter level details. +

2.13.3 PPP (3): Processing Options

BNC allows using various Point Positioning processing options depending on the capability of the involved receiver and the application in mind. You can introduce specific sigmas for code and phase observations as well as for a priori coordinates and troposphere estimates. You could also carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold.

Figure 24: Precise Point Positioning with BNC, PPP Panel 3

2.13.3.1 Linear Combinations - mandatory

Figure 24: Precise Point Positioning with BNC, PPP Panel 3

+ +

2.13.3.1 Linear Combinations - mandatory

@@ -3528,8 +3616,7 @@

Selecting 'P3' means that you request BNC to use code data and the so-called P3 ionosphere-free linear combinations of code observations.
'L3' means that you request BNC to use phase data and the so-called L3 ionosphere-free linear combinations of phase observations.
'P3&L3' means that you request BNC to use both, code and phase data and the so-called P3 and L3 ionosphere-free linear combinations of code and phase observations. -
Selecting 'P3' means that you request BNC to use code data and the so-called P3 ionosphere-free linear combinations of code observations.
'L3' means that you request BNC to use phase data and the so-called L3 ionosphere-free linear combinations of phase observations.
'P3&L3' means that you request BNC to use both, code and phase data and the so-called P3 and L3 ionosphere-free linear combinations of code and phase observations.

@@ -3539,6 +3626,6 @@

2.13.3.2 Code Observations - mandatory

Enter a 'Sigma C1' for C1 code observations in meters. The bigger the sigma you enter, the less the contribution of C1 code observations to a PPP solution based on a combination of code and phase data. '2.0' meters is likely to be an appropriate choice.

@@ -3548,5 +3635,5 @@ -

2.13.3.3 Phase Observations - mandatory

Enter a 'Sigma L1' for L1 phase observations in meters. The bigger the sigma you enter, the less the contribution of L1 phase observations to a PPP solutions based on a combination of code and phase data. '0.01' meters is likely to be an appropriate choice. @@ -3559,10 +3646,10 @@ As the convergence characteristic of a PPP solution can be influenced by the ratio of sigmas for code and phase, you may like to introduce sigmas which differ from the default values.

Introducing a smaller sigma (higher accuracy) for code observations or a bigger sigma for phase observations leads to better results shortly after program start. However, it may take more time until you finally get the best possible solution.
Introducing a bigger sigma (lower accuracy) for code observations or a smaller sigma for phase observations may lead to less accurate results shortly after program start and thus a prolonged period of convergence but could provide better positions in the long run.

- -

2.13.3.4 Elevation Dependent Weighting - mandatory

Introducing a smaller sigma (higher accuracy) for code observations or a bigger sigma for phase observations leads to better results shortly after program start. However, it may take more time until you finally get the best possible solution.

Introducing a bigger sigma (lower accuracy) for code observations or a smaller sigma for phase observations may lead to less accurate results shortly after program start and thus a prolonged period of convergence but could provide better positions in the long run.

+ +

2.13.3.4 Elevation Dependent Weighting - mandatory

BNC allows elevation dependent weighting when processing GNSS observations. A weight function @@ -3582,10 +3669,10 @@

2.13.3.5 Minimum Number of Observations - mandatory

Select the minimum number of observations you want to use per epoch. The minimum for parameter 'Min # of Obs' is 4. This is also the default.

2.13.3.6 Minimum Elevation - mandatory

Select a minimum for satellite elevation angles. Selecting '10 deg' for option 'Min Elevation' may be an appropriate choice. @@ -3595,5 +3682,5 @@

2.13.3.7 Wait for Clock Corrections - optional

Specifying 'no' for option 'Wait for clock corr.' means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. A non-zero value means that epochs of data are buffered and the processing of each epoch is postponed until satellite clock corrections not older than 'Wait for clock corr.' seconds are available. Specifying a value of half the update rate of the clock corrections (e.g. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of half of the update rate. @@ -3606,10 +3693,10 @@

2.13.3.8 Seeding - optional if a priori coordinates specified in 'Coordinates file'

Enter the length of a startup period in seconds for which you want to fix the PPP solution to a known position, see option 'Coordinates file'. Constraining a priori coordinates is done in BNC through setting their white 'Noise' temporarily to zero.

-This so-called Quick-Start option allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the known position throughout the defined period. A value of '60' seconds is likely to be an appropriate choice for 'Seeding'. Default is an empty option field, meaning that you do not want BNC to start in Quick-Start mode. +This so-called Quick-Start option allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the known position throughout the defined period. A value of '60' seconds is likely to be an appropriate choice for 'Seeding'. Default is an empty option field, meaning that you do not want BNC to start in Quick-Start mode.

You may need to create your own reference coordinate beforehand through running BNC for an hour in normal mode before applying the 'Seeding' option. Do not forget to introduce realistic North/East/Up sigmas under panel 'PPP (2)' corresponding to the coordinate's precision. @@ -3617,5 +3704,9 @@

-'Seeding' has also a function for bridging gaps in PPP solutions from failures caused e.g. by longer lasting outages. Should the time span between two consecutive solutions exceed the limit of 60 seconds (maximum solution gap, hard-wired), the algorithm fixes the latest derived coordinate for a period of 'Seeding' seconds. This option avoids time-consuming reconvergences and makes especially sense for stationary operated receivers where convergence can be enforced because a good approximation for the receiver position is known. +'Seeding' has also a function for bridging gaps in PPP solutions from failures caused e.g. by longer lasting +outages. Should the time span between two consecutive solutions exceed the limit of 60 seconds (maximum solution gap, + hard-wired), the algorithm fixes the latest derived coordinate for a period of 'Seeding' seconds. This option avoids + time-consuming reconvergences and makes especially sense for stationary operated receivers where convergence can be + enforced because a good approximation for the receiver position is known.

@@ -3625,14 +3716,17 @@

Figure 25: Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 4

- -

2.13.4 PPP (4): Plots

-This panel presents options for visualizing PPP results as a time series plot or as a track map with PPP tracks on top of OSM or Google maps. -

- -

2.13.4.1 PPP Plot - optional

-PPP time series of North (red), East (green) and Up (blue) displacements will be plotted under the 'PPP Plot' tab when a 'Mountpoint' is specified. Values will be referred to an XYZ reference coordinate (if specified, see 'Coordinates file'). The sliding PPP time series window will cover the period of the latest 5 minutes. +

Figure 25: Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 4

+ +

2.13.4 PPP (4): Plots

+This panel presents options for visualizing PPP results as a time series plot or as a track map with PPP tracks on top +of OSM or Google maps. +

+ +

2.13.4.1 PPP Plot - optional

+PPP time series of North (red), East (green) and Up (blue) displacements will be plotted under the 'PPP Plot' tab when + a 'Mountpoint' is specified. Values will be referred to an XYZ reference coordinate (if specified, see + 'Coordinates file'). The sliding PPP time series window will cover the period of the latest 5 minutes.

@@ -3640,7 +3734,9 @@

2.13.4.2 Audio Response - optional

-For natural hazard prediction and monitoring landslides, it may be appropriate to generate audio alerts. For that you can specify an 'Audio response' threshold in meters. A beep is produced by BNC whenever a horizontal PPP coordinate component differs by more than the threshold value from the specified marker coordinate. +

2.13.4.2 Audio Response - optional

+For natural hazard prediction and monitoring landslides, it may be appropriate to generate audio alerts. For that +you can specify an 'Audio response' threshold in meters. A beep is produced by BNC whenever a horizontal PPP coordinate + component differs by more than the threshold value from the specified marker coordinate.

@@ -3648,10 +3744,12 @@

2.13.4.3 Track Map - optional

-You may like to track your rover position using Google Maps or OpenStreetMap as a background map. Track maps can be produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files. -

-Even when in 'RINEX Files' post processing mode, you should not forget to go online with your host and specify a proxy under the 'Network' panel if that is operated in front of BNC. +

2.13.4.3 Track Map - optional

+You may like to track your rover position using Google Maps or OpenStreetMap as a background map. Track maps can be +produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files. +

+Even when in 'RINEX Files' post processing mode, you should not forget to go online with your host and specify a +proxy under the 'Network' panel if that is operated in front of BNC.

@@ -3660,7 +3758,7 @@

Figure 26: Track of positions from BNC with Google Maps in background

- -

2.13.4.3.1 Google/OSM - mandatory before pushing 'Open Map'

Figure 26: Track of positions from BNC with Google Maps in background

+ +

2.13.4.3.1 Google/OSM - mandatory before pushing 'Open Map'

Select either 'Google' or 'OSM' as the background map for your rover positions. @@ -3668,36 +3766,55 @@

Figure 27: Example for background map from Google Maps and OpenStreetMap (OSM)

- -

2.13.4.4 Dot-properties - mandatory before pushing 'Open Map'

Figure 27: Example for background map from Google Maps and OpenStreetMap (OSM)

+ +

2.13.4.4 Dot-properties - mandatory before pushing 'Open Map'

PPP tracks are presented on maps through plotting one colored dot per observation epoch.

2.13.4.4.1 Size - mandatory before pushing 'Open Map'

-Specify the size of dots showing the rover position. A dot size of '3' may be appropriate. The maximum possible dot size is '10'. An empty option field or a size of '0' would mean that you do not want BNC to show the rover's track on the map. -

- -

2.13.4.4.2 Color - mandatory before pushing 'Open Map'

2.13.4.4.1 Size - mandatory before pushing 'Open Map'

+Specify the size of dots showing the rover position. A dot size of '3' may be appropriate. The maximum possible dot +size is '10'. An empty option field or a size of '0' would mean that you do not want BNC to show the rover's track +on the map. +

+ +

2.13.4.4.2 Color - mandatory before pushing 'Open Map'

Select the color of dots showing the rover track.

2.13.4.5 Post Processing Speed - mandatory before pushing 'Open Map'

-With BNC in PPP 'RINEX File' post processing mode, you can specify the speed of computations as appropriate for visualization. Note that you can adjust 'Post-processing speed' on-the-fly while BNC is already processing your observations. -

- -

2.14 Combine Corrections

-BNC allows processing several orbit and clock correction streams in real-time to produce, encode, upload and save a combination of Broadcast Corrections from various providers. All corrections must refer to satellite Antenna Phase Centers (APC). It is so far only the satellite clock corrections which are combined by BNC while orbit corrections in the combination product as well as product update rates are just taken over from one of the incoming Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference imposes the potential to introduce some analysis inconsistencies. We may therefore eventually consider improvements on this approach. The clock combination can be based either on a plain 'Single-Epoch' or on a Kalman 'Filter' approach. -

-In the Kalman Filter approach, satellite clocks estimated by individual Analyses Centers (ACs) are used as pseudo observations within the adjustment process. Each observation is modeled as a linear function (actually a simple sum) of three estimated parameters: AC specific offset, satellite specific offset common to all ACs, and the actual satellite clock correction, which represents the result of the combination. These three parameter types differ in their statistical properties. The satellite clock offsets are assumed to be static parameters while AC specific and satellite specific offsets are stochastic parameters affected by white noise. -

-The solution is regularized by a set of minimal constraints. In case of a change of the 'SSR Provider ID', 'SSR Solution ID', or 'IOD SSR' (see section 'Upload Corrections'), the satellite clock offsets belonging to the corresponding analysis center are reset in the adjustment. -

2.13.4.5 Post Processing Speed - mandatory before pushing 'Open Map'

+With BNC in PPP 'RINEX File' post processing mode, you can specify the speed of computations as appropriate for +visualization. Note that you can adjust 'Post-processing speed' on-the-fly while BNC is already processing your observations. +

+ +

2.14 Combine Corrections

+BNC allows processing several orbit and clock correction streams in real-time to produce, encode, upload and save a +combination of Broadcast Corrections from various providers. All corrections must refer to satellite +Antenna Phase Centers (APC). It is so far only the satellite clock corrections which are combined by BNC while orbit +corrections in the combination product as well as product update rates are just taken over from one of the incoming +Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference imposes the potential +to introduce some analysis inconsistencies. We may therefore eventually consider improvements on this approach. +The clock combination can be based either on a plain 'Single-Epoch' or on a Kalman 'Filter' approach. +

+ +

+In the Kalman Filter approach, satellite clocks estimated by individual Analyses Centers (ACs) are used as pseudo +observations within the adjustment process. Each observation is modeled as a linear function (actually a simple sum) +of three estimated parameters: AC specific offset, satellite specific offset common to all ACs, and the actual satellite + clock correction, which represents the result of the combination. These three parameter types differ in their statistical + properties. The satellite clock offsets are assumed to be static parameters while AC specific and satellite specific + offsets are stochastic parameters affected by white noise. +

+ +

+The solution is regularized by a set of minimal constraints. In case of a change of the 'SSR Provider ID', +'SSR Solution ID', or 'IOD SSR' (see section 'Upload Corrections'), the satellite clock offsets belonging to the +corresponding analysis center are reset in the adjustment. +

Removing the AC-dependent biases as well as possible is a major issue with clock combinations. Since they vary in time, it can be tricky to do this. Otherwise, there will be artificial jumps in the combined clock stream if one or more AC contributions drop out for certain epochs. Here the Kalman Filter approach is expected to do better than the Single-Epoch approach. @@ -3706,16 +3823,20 @@ In view of IGS real-time products, the 'Combine Corrections' functionality has been integrated in BNC (Weber and Mervart 2010) because

The software with its Graphic User Interface and range of supported Operating Systems represents a perfect platform to process many Broadcast Correction streams in parallel;
Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;
Generating a combination product from several AC products allows detecting and rejecting outliers;
A Combination Center (CC) can operate BNC to globally disseminate a combination product via Ntrip broadcast;
An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;
It enables a BNC PPP user to follow his own preference in combining streams from individual ACs for Precise Point Positioning;
It allows an instantaneous quality control of the combination process not only in the time domain but also in the space domain; this can be done by direct application of the combined stream in a PPP solution even without prior upload to an Ntrip Broadcaster;
It provides the means to output SP3 and Clock RINEX files containing precise orbit and clock information for further processing using other tools than BNC.

-Note that the combination process requires real-time access to Broadcast Ephemeris. Therefore, in addition to the orbit and clock correction streams BNC must pull a stream carrying Broadcast Ephemeris in the form of RTCM Version 3 messages. Stream 'RTCM3EPH' on caster products.igs-ip.net is an example for that. Note further that BNC will ignore incorrect or outdated Broadcast Ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile. +

The software with its Graphic User Interface and range of supported Operating Systems represents a perfect platform to process many Broadcast Correction streams in parallel;

Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;

Generating a combination product from several AC products allows detecting and rejecting outliers;

A Combination Center (CC) can operate BNC to globally disseminate a combination product via Ntrip broadcast;

An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;

It enables a BNC PPP user to follow his own preference in combining streams from individual ACs for Precise Point Positioning;

It allows an instantaneous quality control of the combination process not only in the time domain but also in the space domain; this can be done by direct application of the combined stream in a PPP solution even without prior upload to an Ntrip Broadcaster;

It provides the means to output SP3 and Clock RINEX files containing precise orbit and clock information for further processing using other tools than BNC.

+ +

+Note that the combination process requires real-time access to Broadcast Ephemeris. Therefore, in addition to the orbit + and clock correction streams BNC must pull a stream carrying Broadcast Ephemeris in the form of RTCM Version 3 messages. + Stream 'RTCM3EPH' on caster http://products.igs-ip.net is an example for that. Note further that BNC will ignore incorrect + or outdated Broadcast Ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile.

-The following recursive algorithm is used to detect orbit outliers in the Kalman Filter combination when Broadcast Corrections are provided by several ACs: -
-Step 1: We do not produce a combination for a certain satellite if only one AC provides corrections for it. -
-Step 2: A mean satellite position is calculated as the average of positions from all ACs. -
-Step 3: For each AC and satellite, the 3D distance between individual and mean satellite position is calculated. -
-Step 4: We find the greatest difference between AC specific and mean satellite positions. -
-Step 5: If that is less than a threshold, the conclusion is that we do not have an outlier and can proceed to the next epoch. -
+The following recursive algorithm is used to detect orbit outliers in the Kalman Filter combination when Broadcast Corrections are provided by several ACs:
+Step 1: We do not produce a combination for a certain satellite if only one AC provides corrections for it.
+Step 2: A mean satellite position is calculated as the average of positions from all ACs.
+Step 3: For each AC and satellite, the 3D distance between individual and mean satellite position is calculated.
+Step 4: We find the greatest difference between AC specific and mean satellite positions.
+Step 5: If that is less than a threshold, the conclusion is that we do not have an outlier and can proceed to the next epoch.
Step 6: If that is greater than a threshold, then corrections of the affiliated AC are ignored for the affected epoch and the outlier detection restarts with step 1.

The following screenshot shows an example setup of BNC when combining Broadcast Correction streams CLK11, CLK21, CLK91, and CLK80. @@ -3750,16 +3866,18 @@

Figure 28: BNC combining Broadcast Correction streams

Note that BNC can produce an internal PPP solution from combined Broadcast Corrections. For that you have to specify the keyword 'INTERNAL' as 'Corrections stream' in the PPP (1) panel. The following example combines correction streams IGS01 and IGS02 and simultaneously carries out a PPP solution with observations from stream FFMJ1 to allow monitoring the quality of the combination product in the space domain.

Figure 29: 'INTERNAL' PPP with BNC using a combination of Broadcast Corrections

2.14.1 Combine Corrections Table - optional

Figure 29: 'INTERNAL' PPP with BNC using a combination of Broadcast Corrections

+ +

2.14.1 Combine Corrections Table - optional

Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Correction mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the Antenna Phase Center (APC) related correction stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination.

The sequence of entries in the 'Combine Corrections' table is not of importance. Note that the orbit information in the final combination stream is just copied from one of the incoming streams. The stream used for providing the orbits may vary over time: if the orbit-providing stream has an outage then BNC switches to the next remaining stream for getting hold of the orbit information.

@@ -3767,19 +3885,20 @@ It is possible to specify only one Broadcast Ephemeris correction stream in the 'Combine Corrections' table. Instead of combining corrections from several sources, BNC will then merge the single corrections stream with Broadcast Ephemeris to allow saving results in SP3 and/or Clock RINEX format when specified accordingly under the 'Upload Corrections' panel. Note that in such a BNC application you must not pull more than one Broadcast Ephemeris correction stream even if a second stream would provide the same corrections from a backup caster.

Default is an empty 'Combine Corrections' table, meaning that you do not want BNC to combine orbit and clock correction streams.

2.14.1.1 Add Row, Delete - optional

Hit 'Add Row' button to add another row to the 'Combine Corrections' table or hit the 'Delete' button to delete the highlighted row(s).

2.14.1.2 Method - mandatory if 'Combine Corrections' table is populated

Select a clock combination method. Available options are Kalman 'Filter' and 'Single-Epoch. It is suggested to use the Kalman Filter approach in case the combined stream of Broadcast Corrections is intended for Precise Point Positioning.

2.14.1.3 Maximal Residuum - mandatory if 'Combine Corrections' table is populated

BNC combines all incoming clocks according to specified weights. Individual clock estimates that differ by more than 'Maximal Residuum' meters from the average of all clocks will be ignored.

@@ -3787,38 +3906,38 @@

Default is a 'Maximal Residuum' of 999.0 meters.

2.14.1.4 Sampling - mandatory if 'Combine Corrections' table is populated

Specify a combination sampling interval. Orbit and clock corrections will be produced following that interval. A value of 10 sec may be an appropriate choice.

2.14.1.5 Use GLONASS - optional

You may tick the 'Use GLONASS' option in case you want to produce a GPS plus GLONASS combination and both systems are supported by the Broadcast Correction streams participating in the combination.

2.15 Upload Corrections

-BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and out-of-plane components if they are

-either generated by BNC as a combination of several individual Broadcast Correction streams coming from an number of real-time Analysis Centers (ACs), see section 'Combine Corrections',

-or generated by BNC while the program receives an ASCII stream of precise satellite orbits and clocks via IP port from a connected real-time GNSS engine. Such a stream would be expected in a plain ASCII format and the associated 'decoder' string would have to be 'RTNET', see format description below.

2.15 Upload Corrections

+BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and out-of-plane components if they are +

either generated by BNC as a combination of several individual Broadcast Correction streams coming from an number of real-time Analysis Centers (ACs), see section 'Combine Corrections',
or generated by BNC while the program receives an ASCII stream of precise satellite orbits and clocks via IP port from a connected real-time GNSS engine. Such a stream would be expected in a plain ASCII format and the associated 'decoder' string would have to be 'RTNET', see format description below.

The procedure taken by BNC to generate the orbit and clock corrections to Broadcast Ephemeris and upload them to an Ntrip Broadcaster is as follow:

Continuously receive up-to-date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites. Read new Broadcast Ephemeris immediately whenever they become available. This information may come via a stream of RTCM messages generated from another BNC instance.
Continuously receive up-to-date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites. Read new Broadcast Ephemeris immediately whenever they become available. This information may come via a stream of RTCM messages generated from another BNC instance.

Then, epoch by epoch:

Continuously receive the best available orbit and clock estimates for all satellites in XYZ Earth-Centered-Earth-Fixed IGS14 reference system. Receive them every epoch in plain ASCII format as provided by a real-time GNSS engine such as RTNET or generate them following a combination approach.
Calculate XYZ coordinates from Broadcast Ephemeris orbits.
Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS14 orbits.
Transform these differences into radial, along-track and out-of-plane corrections to Broadcast Ephemeris orbits.
Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris clocks and IGS14 clocks.
Encode Broadcast Ephemeris orbit and clock corrections in RTCM Version 3 format.
Upload Broadcast Correction stream to Ntrip Broadcaster.
Continuously receive the best available orbit and clock estimates for all satellites in XYZ Earth-Centered-Earth-Fixed IGS14 reference system. Receive them every epoch in plain ASCII format as provided by a real-time GNSS engine such as RTNET or generate them following a combination approach.
Calculate XYZ coordinates from Broadcast Ephemeris orbits.
Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS14 orbits.
Transform these differences into radial, along-track and out-of-plane corrections to Broadcast Ephemeris orbits.
Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris clocks and IGS14 clocks.
Encode Broadcast Ephemeris orbit and clock corrections in RTCM Version 3 format.
Upload Broadcast Correction stream to Ntrip Broadcaster.

The orbit and clock corrections to Broadcast Ephemeris are usually referred to the latest set of broadcast messages, which are generally also received in real-time by a GNSS rover. However, the use of the latest broadcast message is delayed for a period of 60 seconds, measured from the time of complete reception of ephemeris and clock parameters, in order to accommodate rover applications to obtain the same set of broadcast orbital and clock parameters. This procedure is recommended in the RTCM SSR standard.

+ +

Because the stream delivery process may put a significant load on the communication link between BNC and the real-time GNSS engine, it is recommended to run both programs on the same host. However, doing so is not compulsory.

@@ -3826,4 +3945,5 @@ The usual handling of BNC when uploading a stream with Broadcast Corrections is that you first specify Broadcast Ephemeris and Broadcast Correction streams. You then specify an Ntrip Broadcaster for stream upload before you start the program.

'RTNET' Stream Format
@@ -3833,9 +3953,11 @@ Below you find an example for the 'RTNET' ASCII format coming from a real-time GNSS engine. Each epoch begins with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records can provide

Satellite specific parameters

+ +

Satellite specific parameters

A set of parameters can be defined for each satellite as follows: @@ -3846,17 +3968,17 @@ The following satellite specific keys and values are currently specified for that in BNC:

- - - - - - - - - + + + + + + + + +
Key Values
APC Satellite Antenna Phase Center coordinates in meters
Clk Satellite clock correction in meters, relativistic correction applied like in broadcast clocks
Vel Satellite velocity in meters per second
CoM Satellite Center of Mass coordinates in meters
CodeBias Satellite Code Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3 and preceded by total number of biases
YawAngle Satellite Yaw Angle in radian, restricted to be in [0, 2π] which shall be used for the computation of phase wind-up correction
YawRate Satellite Yaw Rate in radian per second which is the rate of Yaw Angle
PhaseBias Satellite Phase Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3, preceded by total number of biases and followed by Signal Integer Indicator, Signals Wilde-Lane Integer Indicator as well as Signal Discontinuity Counter
Key Values
APC Satellite Antenna Phase Center coordinates in meters
Clk Satellite clock correction in meters, relativistic correction applied like in broadcast clocks
Vel Satellite velocity in meters per second
CoM Satellite Center of Mass coordinates in meters
CodeBias Satellite Code Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3 and preceded by total number of biases
YawAngle Satellite Yaw Angle in radian, restricted to be in [0, 2π] which shall be used for the computation of phase wind-up correction
YawRate Satellite Yaw Rate in radian per second which is the rate of Yaw Angle
PhaseBias Satellite Phase Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3, preceded by total number of biases and followed by Signal Integer Indicator, Signals Wilde-Lane Integer Indicator as well as Signal Discontinuity Counter

Non-satellite specific parameters +
Non-satellite specific parameters

@@ -3868,21 +3990,25 @@ +

The following non-satellite specific keys and values are currently specified in BNC:

- - - + + +
Key Values
IND Stands for phase bias information and is followed by Dispersive Bias Consistency Indicator and MW Consistency Indicator
VTEC Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric Layers
Key Values
IND Stands for phase bias information and is followed by Dispersive Bias Consistency Indicator and MW Consistency Indicator
VTEC Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric Layers

If key VTEC is specified, a data set for each layer contains within its first line the Layers Number, followed by Maximum Degree, Maximum Order and Layer Height. After that, Cosine and Sinus Spherical Harmonic Coefficients will follow, one block each.

Because each keyword is associated to a certain number of values, an 'old' BNC could be operated with an incoming 'new' RTNET stream containing so far unknown keys - they would just be skipped in BNC.

Example for 'RTNET' stream content and format:

@@ -3905,7 +4031,9 @@

Note that the end of an epoch in the incoming stream is indicated by an ASCII string 'EOE' (for End Of Epoch).

When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may be important to understand that they are not corrected for the conventional periodic relativistic effect. Chapter 10 of the IERS Conventions 2003 mentions that the conventional periodic relativistic correction to the satellite clock (to be added to the broadcast clock) is computed as @@ -3916,15 +4044,17 @@

2.15.1 Add, Delete Row - optional

Hit 'Add Row' button to add a row to the stream 'Upload Table' or hit the 'Delete' button to delete the highlighted row(s).

Having an empty 'Upload Table' is default and means that you do not want BNC to upload orbit and clock correction streams to any Ntrip Broadcaster.

2.15.2 Host, Port, Mountpoint, Password - optional

Specify the domain name or IP number of an Ntrip Broadcaster for uploading the stream. Furthermore, specify the caster's listening IP port, an upload mountpoint and an upload password. Note that Ntrip Broadcasters are often configured to provide access through more than one port, usually ports 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).

BNC uploads a stream to the Ntrip Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a 4-character ID (capital letters) plus an integer number.

@@ -3934,16 +4064,16 @@

2.15.3 System - mandatory if 'Host' is set

BNC allows configuring several Broadcast Correction streams for upload so that they refer to different reference systems and different Ntrip Broadcasters. You may use this functionality for parallel support of a backup Ntrip Broadcaster or for simultaneous support of various regional reference systems. Available options for transforming orbit and clock corrections to specific target reference systems are

IGS14 which stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame 2014 (ITRF2014), and
ETRF2000 which stands for the European Terrestrial Reference Frame 2000 adopted by EUREF, and
NAD83 which stands for the North American Datum 1983 as adopted for the U.S.A., and
GDA2020 which stands for the Geodetic Datum Australia 2020 as adopted for Australia, and
SIRGAS2000 which stands for the Geodetic Datum adopted for Brazil, and
DREF91 which stands for the Geodetic Datum adopted for Germany, and
'Custom' which allows a transformation of Broadcast Corrections from the IGS14 system to any other system through specifying up to 14 Helmert Transformation Parameters.
IGS14 which stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame 2014 (ITRF2014), and
ETRF2000 which stands for the European Terrestrial Reference Frame 2000 adopted by EUREF, and
NAD83 which stands for the North American Datum 1983 as adopted for the U.S.A., and
GDA2020 which stands for the Geodetic Datum Australia 2020 as adopted for Australia, and
SIRGAS2000 which stands for the Geodetic Datum adopted for Brazil, and
DREF91 which stands for the Geodetic Datum adopted for Germany, and
'Custom' which allows a transformation of Broadcast Corrections from the IGS14 system to any other system through specifying up to 14 Helmert Transformation Parameters.

@@ -3958,4 +4088,5 @@ where s is the transformation scale, c is the speed of light, and ρ are the topocentric distance between an (approximate) center of the transformation's validity area and the satellite.

From a theoretical point of view, this kind of approximation leads to inconsistencies between orbits and clocks and is therefore not allowed (Huisman et al. 2012). However, it has been proved that resulting errors in Precise Point Positioning are on millimeter level for horizontal components and below one centimeter for height components. @@ -3963,9 +4094,9 @@

-IGS14: As the orbits and clocks coming from real-time GNSS engine are expected to be in the IGS14 system, no transformation is carried out if this option is selected. -

- -

-ETRF2000: The formulas for the transformation 'ITRF2008->ETRF2000' are taken from 'Claude Boucher and Zuheir Altamimi 2008: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see http://etrs89.ensg.ign.fr/memo-V8.pdf. The following 14 Helmert Transformation Parameters were introduced: +IGS14: As the orbits and clocks coming from real-time GNSS engine are expected to be in the IGS14 system, no transformation is carried out if this option is selected. +

+ +

+ETRF2000: The formulas for the transformation 'ITRF2008->ETRF2000' are taken from 'Claude Boucher and Zuheir Altamimi 2008: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see http://etrs89.ensg.ign.fr/memo-V8.pdf. The following 14 Helmert Transformation Parameters were introduced:

@@ -3991,5 +4122,5 @@

-NAD83: Formulas for the transformation 'ITRF2008->NAD83' are taken from 'Chris Pearson, Richard Snay 2013: Introducing HTDP 3.1 to transform coordinates across time and spatial reference frames', GPS Solutions, January 2013, Volume 17, Issue 1, pp 1-15. +NAD83: Formulas for the transformation 'ITRF2008->NAD83' are taken from 'Chris Pearson, Richard Snay 2013: Introducing HTDP 3.1 to transform coordinates across time and spatial reference frames', GPS Solutions, January 2013, Volume 17, Issue 1, pp 1-15.

@@ -4015,5 +4146,5 @@

-GDA2020: The formulas for the transformation 'ITRF2014->GDA2020' were provided via personal communication from Ryan Ruddick: 'Geocentric Datum of Australia 2020, Interim Release Note Version 1.01, Intergovernmental Committee on Surveying and Mapping (ICSM), Permanent Committee on Geodesy (PCG), 03 March 2017'. +GDA2020: The formulas for the transformation 'ITRF2014->GDA2020' were provided via personal communication from Ryan Ruddick: 'Geocentric Datum of Australia 2020, Interim Release Note Version 1.01, Intergovernmental Committee on Surveying and Mapping (ICSM), Permanent Committee on Geodesy (PCG), 03 March 2017'.

@@ -4038,5 +4169,5 @@

-SIRGAS2000: The formulas for the transformation 'IGb14->SIRGAS2000' were provided via personal communication from CGED-Coordenacao de Geodesia, IBGE/DGC - Diretoria de Geociencias, Brazil.. +SIRGAS2000: The formulas for the transformation 'IGb14->SIRGAS2000' were provided via personal communication from CGED-Coordenacao de Geodesia, IBGE/DGC - Diretoria de Geociencias, Brazil..

@@ -4061,5 +4192,5 @@

-DREF91: 'Referenzkoordinaten fuer SAPOS, Empfehlungen der Projektgruppe SAPOS-Koordinatenmonitoring 2008', Personal communication with Peter Franke, BKG, Germany. The following 14 Helmert Transformation Parameters were introduced: +DREF91: 'Referenzkoordinaten fuer SAPOS, Empfehlungen der Projektgruppe SAPOS-Koordinatenmonitoring 2008', Personal communication with Peter Franke, BKG, Germany. The following 14 Helmert Transformation Parameters were introduced:

@@ -4085,16 +4216,16 @@

-Custom: Feel free to specify your own 14 Helmert Transformation parameters for transformations from IGS14/ITRF2014 into your own target system. +Custom: Feel free to specify your own 14 Helmert Transformation parameters for transformations from IGS14/ITRF2014 into your own target system.

Figure 30: Setting BNC's Custom Transformation Parameters window, example for 'ITRF2014->GDA94'

- -

2.15.4 Center of Mass - optional

Figure 30: Setting BNC's Custom Transformation Parameters window, example for 'ITRF2014->GDA94'

+ +

2.15.4 Center of Mass - optional

BNC allows to either refer Broadcast Corrections to the satellite's Center of Mass (CoM) or to the satellite's Antenna Phase Center (APC). By default, corrections refer to APC. Tick 'Center of Mass' to refer uploaded corrections to CoM.

2.15.5 SP3 File - optional

Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system: @@ -4107,10 +4238,13 @@ Default is an empty option field, meaning that you do not want BNC to save the uploaded stream content in daily SP3 files.

As a SP3 file content should be referred to the satellites' Center of Mass (CoM) while Broadcast Corrections are referred to the satellites' APC, an offset has to be applied which is available from an IGS ANTEX file (see option 'ANTEX File' below). Hence, you should specify the 'ANTEX File' path there if you want to save the stream content in SP3 format. If you do not specify an 'ANTEX File' path, the SP3 file content will be referred to the satellites APCs.

The filenames for the daily SP3 files follow the convention for SP3 filenames. The first three characters of each filename are set to 'BNC'. Note that clocks in the SP3 orbit files are not corrected for the conventional periodic relativistic effect.

In case the 'Combine Corrections' table contains only one Broadcast Correction stream, BNC will merge that stream with Broadcast Ephemeris to save results in files specified here through SP3 and/or Clock RINEX file path. In such a case you have to define only the SP3 and Clock RINEX file path and no further option in the 'Upload Corrections' table. @@ -4121,5 +4255,5 @@

2.15.6 RNX File - optional

The clock corrections generated by BNC for upload can be logged in Clock RINEX format. The file naming follows the RINEX convention. @@ -4132,27 +4266,28 @@ Note that '${GPSWD}' produces the GPS Week and Day number in the filename.

Note further that clocks in the Clock RINEX files are not corrected for the conventional periodic relativistic effect.

2.15.7 PID, SID, IOD - optional

When applying Broadcast Ephemeris corrections in a PPP algorithm or in a combination of several correction streams, it is important for the client software to receive information on the continuity of discontinuity of the stream contents. Here you can specify three ID's to describe the contents of your Broadcast Ephemeris correction stream when it is uploaded.

A 'SSR Provider ID' is issued by RTCM SC-104 on request to identify a SSR service (see e.g. http://software.rtcm-ntrip.org/wiki/SSRProvider). This ID is globally unique. Values vary in the range of 0-65535. Values in the range of 0-255 are reserved for experimental services.
A provider may generate several Broadcast Ephemeris correction streams with different contents. The 'SSR Solution ID' indicates different SSR services of one SSR provider. Values vary in the range of 0-15.
A change of the 'IOD SSR' is used to indicate a change in the SSR generating configuration which may be relevant for the rover. Values vary in the range of 0-15.

- -

2.15.8 Interval - mandatory if 'Upload Table' entries specified

A 'SSR Provider ID' is issued by RTCM SC-104 on request to identify a SSR service (see e.g. http://software.rtcm-ntrip.org/wiki/SSRProvider). This ID is globally unique. Values vary in the range of 0-65535. Values in the range of 0-255 are reserved for experimental services.

A provider may generate several Broadcast Ephemeris correction streams with different contents. The 'SSR Solution ID' indicates different SSR services of one SSR provider. Values vary in the range of 0-15.

A change of the 'IOD SSR' is used to indicate a change in the SSR generating configuration which may be relevant for the rover. Values vary in the range of 0-15.

+ +

2.15.8 Interval - mandatory if 'Upload Table' entries specified

Select the length of Clock RINEX files and SP3 Orbit files. The default value is 1 day.

2.15.9 Sampling

BNC requires an orbit corrections sampling interval for the stream to be uploaded and sampling intervals for SP3 and Clock RINEX files. The outgoing stream's clock correction sampling interval follows that of incoming corrections and is therefore nothing to be specified here.

2.15.9.1 Orbits (Orb) - mandatory if 'Upload Table' entries specified

Select the stream's orbit correction sampling interval in seconds. A value of 60 sec may be appropriate.

A value of zero '0' tells BNC to upload all orbit correction samples coming in from the real-time GNSS engine along with the clock correction samples to produce combined orbit and clock corrections to Broadcast Ephemeris (1060 for GPS, 1066 for GLONASS). @@ -4161,38 +4296,38 @@ Configuration examples:

-Let us suppose a real-time network engine supporting BNC every 5 sec with GPS Broadcast Corrections for orbits, clocks and code biases in 'RTNET' stream format. -

With 'Sampling Orb' set to '0' BNC will produce

Every 5 sec a 1059 message for GPS code biases,
Every 5 sec a 1060 message for combined orbit and clock corrections to GPS Broadcast Ephemeris.

5 sec

With 'Sampling Orb' set to '0' BNC will produce

Every 5 sec a 1059 message for GPS code biases,
Every 5 sec a 1060 message for combined orbit and clock corrections to GPS Broadcast Ephemeris.

With 'Sampling Orb' set to '5' BNC will produce

Every 5 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,
Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,
Every 5 sec a 1059 message for GPS code biases.

With 'Sampling Orb' set to '10' BNC will produce

Every 10 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,
Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,
Every 5 sec a 1059 message for GPS code biases.

With 'Sampling Orb' set to '5' BNC will produce

Every 5 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,
Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,
Every 5 sec a 1059 message for GPS code biases.

With 'Sampling Orb' set to '10' BNC will produce

Every 10 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,
Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,
Every 5 sec a 1059 message for GPS code biases.

-
-Note that only when specifying a value of zero '0' (default) for 'Sampling Orb', BNC produces combined orbit and clock correction messages. -

2.15.9.2 SP3 - mandatory if 'SP3 File' is specified

+Note that only when specifying a value of zero '0' (default) for 'Sampling Orb', BNC produces combined orbit and clock correction messages. +

2.15.9.2 SP3 - mandatory if 'SP3 File' is specified

Select the SP3 orbit file sampling interval in minutes. A value of 15 min may be appropriate. A value of zero '0' tells BNC to store all available samples into SP3 orbit files.

2.15.9.3 RINEX (RNX) - mandatory if 'RNX File' is specified

Select the Clock RINEX file sampling interval in seconds. A value of 10 sec may be appropriate. A value of zero '0' tells BNC to store all available samples into Clock RINEX files.

2.15.10 Custom Trafo - optional if 'Upload Table' entries specified

Hit 'Custom Trafo' to specify your own 14 parameter Helmert Transformation instead of selecting a predefined transformation through 'System' button.

2.15.11 ANTEX File - mandatory if 'SP3 File' is specified

IGS provides a file containing absolute phase center variations for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required here for referring the SP3 file content to the satellite's Center of Mass (CoM). If you do not specify an ANTEX file, the SP3 file will contain orbit information which is referred to Antenna Phase Center (APC) instead of CoM. @@ -4202,15 +4337,15 @@

Figure 31: BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster

The following screenshot shows the encoding and uploading of several Broadcast Ephemeris correction streams combined from streams CLK11, CLK21, CLK80, and CLK91. Combined streams are uploaded to different Ntrip Broadcasters and referred to different reference systems. One of the uploaded streams is locally saved in SP3 and Clock RINEX format. Different SSR Provider IDs, SSR Solution IDs and Issue of Data IDs are specified. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'.

Figure 32: BNC uploading a combined Broadcast Correction stream

2.16 Upload Ephemeris

-BNC can generate streams carrying only Broadcast Ephemeris in RTCM Version 3 format and upload them to an Ntrip Broadcaster. This can be done for individual satellite systems or for all satellite systems, specifying the parameter ‘System’ for each stream. +

2.16 Upload Ephemeris

+BNC can generate streams carrying only Broadcast Ephemeris in RTCM Version 3 format and upload them to an Ntrip Broadcaster. This can be done for individual satellite systems or for all satellite systems, specifying the parameter âSystemâ for each stream.

@@ -4228,9 +4363,10 @@ A note 'OUTDATED EPHEMERIS' will be given in the logfile and the data will be disregarded when necessary.

Furthermore, received Broadcast Ephemeris parameters pass through a plausibility check in BNC which allows to ignore incorrect ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' in the logfile.

2.16.1 Host & Port - optional

Specify the 'Host' IP number or URL of an Ntrip Broadcaster to upload the stream. An empty option field means that you do not want to upload Broadcast Ephemeris. @@ -4240,5 +4376,5 @@

2.16.2 Mountpoint & Password - mandatory if 'Host' is set

BNC uploads a stream to the Ntrip Broadcaster by referring it to a dedicated mountpoint that has been set by its operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a 4-character ID (capital letters) plus an integer number.

@@ -4246,12 +4382,12 @@

2.16.3 Sampling - mandatory if 'Host' is set

Select the Broadcast Ephemeris repetition interval in seconds. Default is '5', meaning that a complete set of Broadcast Ephemeris is uploaded every 5 seconds.

Figure 33: BNC 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

- -

2.17 Streams Canvas

Figure 33: BNC 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

+ +

2.17 Streams Canvas

Each stream on an Ntrip Broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An Ntrip Client like BNC accesses the desired stream by referring to its mountpoint. Information about streams and their mountpoints is available through the source-table maintained by the Ntrip Broadcaster. @@ -4261,56 +4397,53 @@ Streams selected for retrieval are listed under the 'Streams' canvas on BNC's main window. The list provides the following information either extracted from source-table(s) produced by the Ntrip Broadcasters or introduced by BNC's user:

- - - - - - - - + + + + + + +
'resource loader' Ntrip Broadcaster URL and port, or
TCP/IP host and port, or
UDP port, or
Serial input port specification.
'mountpoint' Mountpoint introduced by Ntrip Broadcaster, or
Mountpoint introduced by BNC's user.
'decoder' Name of decoder used to handle the incoming stream content according to its format; editable.
'lat' Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.
'long' Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.
'nmea' Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'.
'ntrip' Selected Ntrip transport protocol version (1, 2, 2s, R, or U), or
'N' for TCP/IP streams without Ntrip, or
'UN' for UDP streams without Ntrip, or
'S' for serial input streams without Ntrip.
'bytes' Number of bytes received. +
'resource loader' Ntrip Broadcaster URL and port, or
TCP/IP host and port, or
UDP port, or
Serial input port specification.
'mountpoint' Mountpoint introduced by Ntrip Broadcaster, or
Mountpoint introduced by BNC's user.
'decoder' Name of decoder used to handle the incoming stream content according to its format; editable.
'lat' Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.
'long' Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.
'nmea' Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'.
'ntrip' Selected Ntrip transport protocol version (1, 2, 2s, R, or U), or
'N' for TCP/IP streams without Ntrip, or
'UN' for UDP streams without Ntrip, or
'S' for serial input streams without Ntrip.
'bytes' Number of bytes received.

2.17.1 Edit Streams

-BNC automatically allocates one of its internal decoders to a stream based on the stream's 'format' and 'format-details' as given in the source-table. However, there might be cases where you need to override the automatic selection due to an incorrect source-table for example. BNC allows users to manually select the required decoder by editing the decoder string. Double click on the 'decoder' field, enter your preferred decoder and then hit Enter. Accepted decoder strings are 'RTCM_2.x', 'RTCM_3.x' and 'RTNET'. -
-In case you need to log the raw data as it is, BNC allows users to by-pass its decoders and directly save the input in daily logfiles. To do this, specify the decoder string as 'ZERO'. The generated filenames are created from the characters of the streams mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save raw data in a file named WTZZ0_070329. -
-BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the Ntrip Broadcaster. In return, a user-specific data stream is generated, typically by Network RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the Ntrip Broadcaster via NMEA GGA sentences. -
If NMEA GGA sentences are not coming from a serially connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in many cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position should preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used. -
Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner when not using the Ntrip Version 2 transport protocol. -

- -

2.17.2 Delete Stream

2.17.1 Edit Streams

BNC automatically allocates one of its internal decoders to a stream based on the stream's 'format' and 'format-details' as given in the source-table. However, there might be cases where you need to override the automatic selection due to an incorrect source-table for example. BNC allows users to manually select the required decoder by editing the decoder string. Double click on the 'decoder' field, enter your preferred decoder and then hit Enter. Accepted decoder strings are 'RTCM_2.x', 'RTCM_3.x' and 'RTNET'.
In case you need to log the raw data as it is, BNC allows users to by-pass its decoders and directly save the input in daily logfiles. To do this, specify the decoder string as 'ZERO'. The generated filenames are created from the characters of the streams mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save raw data in a file named WTZZ0_070329.
BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the Ntrip Broadcaster. In return, a user-specific data stream is generated, typically by Network RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the Ntrip Broadcaster via NMEA GGA sentences.
+ If NMEA GGA sentences are not coming from a serially connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in many cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position should preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used.
+ Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner when not using the Ntrip Version 2 transport protocol.

2.18.1 Log

+ +

2.18.1 Log

2.19.1.1.2 Casters Table - optional

It may be that you are not sure about your Ntrip Broadcaster's host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at www.rtcm-ntrip.org/home. A window opens which allows selecting a broadcaster for stream retrieval, see figure below.

Figure 38: BNC's 'Select Broadcaster' table

- -

2.19.1.1.3 User and Password - mandatory for protected streams

Figure 38: BNC's 'Select Broadcaster' table

+ +

2.19.1.1.3 User and Password - mandatory for protected streams

Streams on Ntrip Broadcasters may be protected. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per Ntrip Broadcaster through a registration procedure. Register through http://register.rtcm-ntrip.org for access to protected streams from EUREF and IGS.

2.19.1.1.4 Get Table

Use the 'Get Table' button to download the source-table from the Ntrip Broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2, RTCM Version 3, or RTNET format. For access to observations, Broadcast Ephemeris and Broadcast Corrections in RTCM format, streams must contain a selection of appropriate message types as listed in the Annex, cf. data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files, RTCM Version 3 streams containing message types 1019 (GPS) and 1020 (GLONASS) and 1043 (SBAS) and 1044 (QZSS) and 1045, 1046 (Galileo) and 63 (BDS/BeiDou, tentative message number) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table.

The content of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA message carrying approximate position coordinates (Virtual Reference Station, VRS).

Hit 'OK' to return to the main window. If you wish, you can click on 'Add Stream' and repeat the process of retrieving streams from different casters.

Figure 39: Broadcaster source-table shown by BNC

- -

2.19.1.1.5 Ntrip Version - mandatory

Figure 39: Broadcaster source-table shown by BNC

+ +

2.19.1.1.5 Ntrip Version - mandatory

Some limitations and deficiencies of the Ntrip Version 1 stream transport protocol are solved in Ntrip Version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are: @@ -4394,11 +4530,11 @@

- - - - - - - + + + + + + +
Option Meaning
1 Ntrip Version 1, TCP/IP
2 Ntrip Version 2 in TCP/IP mode
2s Ntrip Version 2 in TCP/IP mode via SSL
R Ntrip Version 2 in RTSP/RTP mode
U Ntrip Version 2 in UDP mode
Option Meaning
1 Ntrip Version 1, TCP/IP
2 Ntrip Version 2 in TCP/IP mode
2s Ntrip Version 2 in TCP/IP mode via SSL
R Ntrip Version 2 in RTSP/RTP mode
U Ntrip Version 2 in UDP mode

@@ -4416,5 +4552,5 @@

2.19.1.1.6 Map - optional

Button 'Map' opens a window to show a distribution map of the caster's streams. You may like to zoom in or out using the mouse. Left button: draw a rectangle to zoom, right button: zoom out, middle button: zoom back. @@ -4422,16 +4558,16 @@

Figure 40: Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table

- -

2.19.1.2 Add Stream - Coming from TCP/IP Port

Figure 40: Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table

+ +

2.19.1.2 Add Stream - Coming from TCP/IP Port

Button 'Add Stream' > 'Coming from TCP/IP Port' allows to retrieve streams via TCP directly from an IP address without using the Ntrip transport protocol. For that you:

Enter the IP address of the stream providing host.
Enter the IP port number of the stream providing host.
Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ
Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', and 'ZERO'.
Enter the approximate latitude of the stream providing rover in degrees. Example: 45.32.
Enter the approximate longitude of the stream providing rover in degrees. Example: -15.20.
Enter the IP address of the stream providing host.
Enter the IP port number of the stream providing host.
Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ
Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', and 'ZERO'.
Enter the approximate latitude of the stream providing rover in degrees. Example: 45.32.
Enter the approximate longitude of the stream providing rover in degrees. Example: -15.20.

@@ -4439,17 +4575,18 @@ Streams directly received from a TCP/IP port show up with an 'N' for 'No Ntrip' in the 'Streams' canvas on BNC's main window. Latitude and longitude are to be entered just for informal reasons.

Note that this option works only if no proxy server is involved in the communication link.

2.19.1.3 Add Stream - Coming from UDP Port

Button 'Add Stream' > 'Coming from UDP Port' allows to pick up streams arriving directly at one of the local host's UDP ports without using the Ntrip transport protocol. For that you:

Enter the local port number where the UDP stream arrives.
Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ
Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', and 'ZERO'.
Enter the approximate latitude of the stream providing rover in degrees. Example: 45.32.
Enter the approximate longitude of the stream providing rover in degrees. Example: -15.20.
Enter the local port number where the UDP stream arrives.
Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ
Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', and 'ZERO'.
Enter the approximate latitude of the stream providing rover in degrees. Example: 45.32.
Enter the approximate longitude of the stream providing rover in degrees. Example: -15.20.

@@ -4458,13 +4595,13 @@

2.19.1.4 Add Stream - Coming from Serial Port

Button 'Add Stream' > 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the Ntrip transport protocol. For that you:

Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ
Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', and 'ZERO'.
Enter the approximate latitude of the stream providing receiver in degrees. Example: 45.32.
Enter the approximate longitude of the stream providing receiver in degrees. Example: -15.20.
Enter the serial 'Port name' selected on your host for communication with the receiver. Valid port names are +
Specify a mountpoint. Recommended is a 4-character station ID. Example: FFMJ
Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', and 'ZERO'.
Enter the approximate latitude of the stream providing receiver in degrees. Example: 45.32.
Enter the approximate longitude of the stream providing receiver in degrees. Example: -15.20.
Enter the serial 'Port name' selected on your host for communication with the receiver. Valid port names are
```
 Windows:       COM1, COM2
@@ -4477,11 +4614,12 @@
 
```
Select a 'Baud rate' for the serial input. Note that using a high baud rate is recommended.
Select the number of 'Data bits' for the serial input. Note that often '8' data bits are used.
Select the 'Parity' for the serial input. Note that parity is often set to 'NONE'.
Select the number of 'Stop bits' for the serial input. Note that often '1' stop bit is used.
Select a 'Flow control' for the serial link. Select 'OFF' if you do not know better.

Select a 'Baud rate' for the serial input. Note that using a high baud rate is recommended.

Select the number of 'Data bits' for the serial input. Note that often '8' data bits are used.

Select the 'Parity' for the serial input. Note that parity is often set to 'NONE'.

Select the number of 'Stop bits' for the serial input. Note that often '1' stop bit is used.

Select a 'Flow control' for the serial link. Select 'OFF' if you do not know better.

When selecting one of the serial communication options listed above, make sure that you pick those configured to the serially connected GNSS receiver. @@ -4496,50 +4634,54 @@

Figure 41: BNC configuration for pulling a stream via serial port

- -

2.19.2 Delete Stream

Figure 41: BNC configuration for pulling a stream via serial port

+ +

2.19.2 Delete Stream

Button 'Delete Stream' allows you to delete streams previously selected for retrieval as listed under the 'Streams' canvas on BNC's main window.

2.19.3 Map

Button 'Map' opens a window to show a distribution map of the streams selected for retrieval as listed under the 'Streams' canvas. You may like to zoom in or out using the mouse. Left button: draw a rectangle to zoom, right button: zoom out, middle button: zoom back.

2.19.4 Start

Hit 'Start' to start retrieving, decoding or converting GNSS data streams in real-time. Note that 'Start' generally forces BNC to begin with fresh RINEX files which might overwrite existing files when necessary unless option 'Append files' is ticked.

2.19.5 Stop

Hit the 'Stop' button in order to stop BNC.

2.19.6 Help? = Shift+F1

BNC comes with a What's This help system providing information about its functionality and usage. Short descriptions are available for any widget and program option. Focus to the relevant object and press Shift+F1 to request help information. A help text appears immediately; it disappears as soon as the user does something else. The dialogs on some operating systems may provide a '?' button that users can click; click the relevant widget to pop up the help text.

2.20 Command Line Options

Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging or post processing purposes. It is also possible to introduce a specific configuration filename instead of using the default filename 'BNC.bnc'. The self-explaining content of the configuration file can easily be edited.

In addition to reading processing options from the involved configuration file, BNC can optionally read any configuration option from command line. Running BNC with command line option 'help'

Example:

bnc --help (MS Windows: bnc.exe --help | more)

provides a list of all available command line options.

2.20.1 Version - optional

Command line option '--version' lets BNC print its version number.

Example:

@@ -4547,8 +4689,9 @@

2.20.2 Display - optional

On systems which support graphics, command line option '--display' forces BNC to present the BNC window on the specified display.

Example:

@@ -4556,12 +4699,14 @@

2.20.3 No Window Mode - optional

Apart from its regular windows mode, BNC can be started on all systems as a batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems.

Example:

bnc.exe --nw

It is obvious that BNC requires graphics support when started in interactive @@ -4590,8 +4735,9 @@ -

2.20.4 File Mode - optional

Although BNC is primarily a real-time online tool, for debugging purposes it can be run offline to read data from a file previously saved through option 'Raw output file' (Record & Replay functionality). Enter the following command line option for that

--file <inputFileName> @@ -4601,44 +4747,53 @@ ./bnc --file /home/user/raw.output_110301

Note that when running BNC offline, it will use options for file saving, interval, sampling, PPP etc. from its configuration file.

Note further that option '--file' forces BNC to apply the '-nw' option for running in 'no window' mode.

2.20.5 Configuration File - optional

The default configuration filename is 'BNC.bnc'. You may change this name at startup time using command line option '--conf <confFileName>'. This allows running several BNC jobs in parallel on the same host using different sets of configuration options. confFileName stands either for the full path to a configuration file or just for a filename. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNC is started.

Example:

./bnc --conf MyConfig.bnc

This leads to a BNC job using configuration file 'MyConfig.bnc'. The configuration file will be saved in the current working directory.

2.20.6 Configuration Options - optional

BNC applies options from the configuration file but allows updating every one of them on the command line while the content of the configuration file remains unchanged. Note the following syntax for Command Line Interface (CLI) options:

--key <keyName> <keyValue>

Parameter <keyName> stands for the key name of an option contained in the configuration file and <keyValue> stands for the value you want to assign to it. The following is a syntax example for a complete command line:

bnc --nw --conf <confFileName> --key <keyName1> <keyValue1> --key <keyName2> <keyValue2> ...

Configuration options which are part of the configuration files PPP section must be prefixed by 'PPP/'. As an example, option 'minObs' from the PPP section of the BNC configuration file would be specified as 'PPP/minObs' on a command line.

Values for configuration options can be introduced via command line exactly as they show up in the configuration file. However, any value containing one or more blank characters must be enclosed by quotation marks when specified on command line.

3. Annex

- -

3.1 RTCM Standards

3. Annex

+ +

3.1 RTCM Standards

@@ -4648,5 +4803,5 @@

3.1.1 Ntrip Version 1

@@ -4665,9 +4820,9 @@ Ntrip is an open none-proprietary protocol. Major characteristics of Ntrip's dissemination technique are:

Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and server platform resources available;
Application not limited to one particular plain or coded stream content; ability to distribute any kind of GNSS data;
Potential to support mass usage; disseminating hundreds of streams simultaneously for thousands of users possible when applying modified Internet Radio broadcasting software;
Considering security needs; stream providers and users do not necessarily get into contact, streams often not blocked by firewalls or proxy servers protecting Local Area Networks;
Enables streaming over mobile IP networks because of using TCP/IP.
Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and server platform resources available;
Application not limited to one particular plain or coded stream content; ability to distribute any kind of GNSS data;
Potential to support mass usage; disseminating hundreds of streams simultaneously for thousands of users possible when applying modified Internet Radio broadcasting software;
Considering security needs; stream providers and users do not necessarily get into contact, streams often not blocked by firewalls or proxy servers protecting Local Area Networks;
Enables streaming over mobile IP networks because of using TCP/IP.

@@ -4687,5 +4842,5 @@

3.1.2 Ntrip Version 2

@@ -4694,10 +4849,10 @@

Cleared and fixed design problems and HTTP protocol violations;
Replaced nonstandard directives;
Chunked transfer encoding;
Improvements in header records;
Source-table filtering;
RTSP communication.
Cleared and fixed design problems and HTTP protocol violations;
Replaced nonstandard directives;
Chunked transfer encoding;
Improvements in header records;
Source-table filtering;
RTSP communication.

@@ -4705,5 +4860,5 @@

3.1.3 RTCM Version 2

Transmitting GNSS carrier phase data can be done through RTCM Version 2 messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of interest here are: @@ -4711,66 +4866,46 @@

-Type 1 message is the range correction message and is the primary message in code-phase differential positioning (DGPS). It is computed in the base receiver by computing the error in the range measurement for each tracked SV. -
-Type 2 message is automatically generated when a new set of satellite ephemeris is downloaded to the base receiver. It is the computed difference between the old ephemeris and the new ephemeris. Type 2 messages are used when the base station is transmitting Type 1 messages. -
-Type 3 and 22 messages are the base station position and the antenna offset. Type 3 and 22 are used in RTK processing to perform antenna reduction. -
-Type 6 message is a null frame filler message that is provided for data links that require continuous transmission of data, even if there are no corrections to send. As many Type 6 messages are sent as required to fill in the gap between two correction messages (type 1). Message 6 is not sent in burst mode. -
-Type 9 message serves the same purpose as Type 1, but does not require a complete satellite set. As a result, Type 9 messages require a more stable clock than a station transmitting Type 1 's, because the satellite corrections have different time references. -
-Type 16 message is simply a text message entered by the user that is transmitted from the base station to the rover. It is used with code-phase differential. -
-Type 18 and 20 messages are RTK uncorrected carrier phase data and carrier phase corrections. -
-Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo-range corrections used in RTK. -
-Type 23 message provides the information on the antenna type used on the reference station. -
-Type 24 message carries the coordinates of the installed antenna's ARP in the GNSS coordinate system coordinates. -

- -

3.1.4 RTCM Version 3

Type 1 message is the range correction message and is the primary message in code-phase differential positioning (DGPS). It is computed in the base receiver by computing the error in the range measurement for each tracked SV.

Type 2 message is automatically generated when a new set of satellite ephemeris is downloaded to the base receiver. It is the computed difference between the old ephemeris and the new ephemeris. Type 2 messages are used when the base station is transmitting Type 1 messages.

Type 3 and 22 messages are the base station position and the antenna offset. Type 3 and 22 are used in RTK processing to perform antenna reduction.

Type 6 message is a null frame filler message that is provided for data links that require continuous transmission of data, even if there are no corrections to send. As many Type 6 messages are sent as required to fill in the gap between two correction messages (type 1). Message 6 is not sent in burst mode.

Type 9 message serves the same purpose as Type 1, but does not require a complete satellite set. As a result, Type 9 messages require a more stable clock than a station transmitting Type 1 's, because the satellite corrections have different time references.

Type 16 message is simply a text message entered by the user that is transmitted from the base station to the rover. It is used with code-phase differential.

Type 18 and 20 messages are RTK uncorrected carrier phase data and carrier phase corrections.

Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo-range corrections used in RTK.

Type 23 message provides the information on the antenna type used on the reference station.

Type 24 message carries the coordinates of the installed antenna's ARP in the GNSS coordinate system coordinates.

+ + +

3.1.4 RTCM Version 3

RTCM Version 3 has been developed as a more efficient alternative to RTCM Version 2. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3 standard is intended to correct these weaknesses.

RTCM Version 3 defines a number of message types. Messages that may be of interest here are:

Type 1001, GPS L1 code and phase.
Type 1002, GPS L1 code and phase and ambiguities and carrier-to-noise ratio.
Type 1003, GPS L1 and L2 code and phase.
Type 1004, GPS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.
Type 1005, Station coordinates XYZ for antenna reference point.
Type 1006, Station coordinates XYZ for antenna reference point and antenna height.
Type 1007, Antenna descriptor and ID.
Type 1008, Antenna serial number.
Type 1009, GLONASS L1 code and phase.
Type 1010, GLONASS L1 code and phase and ambiguities and carrier-to-noise ratio.
Type 1011, GLONASS L1 and L2 code and phase.
Type 1012, GLONASS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.
Type 1013, Modified Julian Date, leap second, configured message types and interval.
Type 1014 and 1017, Network RTK (MAK) messages.
Type 1019, GPS ephemeris.
Type 1020, GLONASS ephemeris.
Type 1043, SBAS ephemeris.
Type 1044, QZSS ephemeris.
Type 1045, Galileo F/NAV ephemeris.
Type 1046, Galileo I/NAV ephemeris.
Type 63, BeiDou ephemeris, tentative.
Type 4088 and 4095, Proprietary messages. -
Type 1001, GPS L1 code and phase.
Type 1002, GPS L1 code and phase and ambiguities and carrier-to-noise ratio.
Type 1003, GPS L1 and L2 code and phase.
Type 1004, GPS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.
Type 1005, Station coordinates XYZ for antenna reference point.
Type 1006, Station coordinates XYZ for antenna reference point and antenna height.
Type 1007, Antenna descriptor and ID.
Type 1008, Antenna serial number.
Type 1009, GLONASS L1 code and phase.
Type 1010, GLONASS L1 code and phase and ambiguities and carrier-to-noise ratio.
Type 1011, GLONASS L1 and L2 code and phase.
Type 1012, GLONASS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.
Type 1013, Modified Julian Date, leap second, configured message types and interval.
Type 1014 and 1017, Network RTK (MAK) messages.
Type 1019, GPS ephemeris.
Type 1020, GLONASS ephemeris.
Type 1043, SBAS ephemeris.
Type 1044, QZSS ephemeris.
Type 1045, Galileo F/NAV ephemeris.
Type 1046, Galileo I/NAV ephemeris.
Type 63, BeiDou ephemeris, tentative.
Type 4088 and 4095, Proprietary messages.

@@ -4779,53 +4914,53 @@ The following are so-called 'State Space Representation' (SSR) messages:

Type 1057, GPS orbit corrections to Broadcast Ephemeris
Type 1058, GPS clock corrections to Broadcast Ephemeris
Type 1059, GPS code biases
Type 1060, Combined orbit and clock corrections to GPS Broadcast Ephemeris
Type 1061, GPS User Range Accuracy (URA)
Type 1062, High-rate GPS clock corrections to Broadcast Ephemeris
Type 1063, GLONASS orbit corrections to Broadcast Ephemeris
Type 1064, GLONASS clock corrections to Broadcast Ephemeris
Type 1065, GLONASS code biases
Type 1066, Combined orbit and clock corrections to GLONASS Broadcast Ephemeris
Type 1067, GLONASS User Range Accuracy (URA)
Type 1068, High-rate GLONASS clock corrections to Broadcast Ephemeris
Type 1240, Galileo orbit corrections to Broadcast Ephemeris
Type 1241, Galileo clock corrections to Broadcast Ephemeris
Type 1242, Galileo code biases
Type 1243, Combined orbit and clock corrections to Galileo Broadcast Ephemeris
Type 1244, Galileo User Range Accuracy (URA)
Type 1245, High-rate Galileo clock corrections to Broadcast Ephemeris
Type 1246, QZSS orbit corrections to Broadcast Ephemeris
Type 1247, QZSS clock corrections to Broadcast Ephemeris
Type 1248, QZSS code biases
Type 1249, Combined orbit and clock corrections to QZSS Broadcast Ephemeris
Type 1250, QZSS User Range Accuracy (URA)
Type 1251, High-rate QZSS clock corrections to Broadcast Ephemeris
Type 1252, SBAS orbit corrections to Broadcast Ephemeris
Type 1253, SBAS clock corrections to Broadcast Ephemeris
Type 1254, SBAS code biases
Type 1255, Combined orbit and clock corrections to SBAS Broadcast Ephemeris
Type 1256, SBAS User Range Accuracy (URA)
Type 1257, High-rate SBAS clock corrections to Broadcast Ephemeris
Type 1258, BDS orbit corrections to Broadcast Ephemeris
Type 1259, BDS clock corrections to Broadcast Ephemeris
Type 1260, BDS code biases
Type 1261, Combined orbit and clock corrections to BDS Broadcast Ephemeris
Type 1262, BDS User Range Accuracy (URA)
Type 1263, High-rate BDS clock corrections to Broadcast Ephemeris
Type 1264 SSR Ionosphere VTEC Spherical Harmonics
Type 1265 SSR GPS Satellite Phase Bias
Type 1266 SSR Satellite GLONASS Phase Bias
Type 1267 SSR Satellite Galileo Phase Bias
Type 1268 SSR Satellite QZSS Phase Bias
Type 1269 SSR Satellite SBAS Phase Bias
Type 1270 SSR Satellite BDS Phase Bias
Type 1057, GPS orbit corrections to Broadcast Ephemeris
Type 1058, GPS clock corrections to Broadcast Ephemeris
Type 1059, GPS code biases
Type 1060, Combined orbit and clock corrections to GPS Broadcast Ephemeris
Type 1061, GPS User Range Accuracy (URA)
Type 1062, High-rate GPS clock corrections to Broadcast Ephemeris
Type 1063, GLONASS orbit corrections to Broadcast Ephemeris
Type 1064, GLONASS clock corrections to Broadcast Ephemeris
Type 1065, GLONASS code biases
Type 1066, Combined orbit and clock corrections to GLONASS Broadcast Ephemeris
Type 1067, GLONASS User Range Accuracy (URA)
Type 1068, High-rate GLONASS clock corrections to Broadcast Ephemeris
Type 1240, Galileo orbit corrections to Broadcast Ephemeris
Type 1241, Galileo clock corrections to Broadcast Ephemeris
Type 1242, Galileo code biases
Type 1243, Combined orbit and clock corrections to Galileo Broadcast Ephemeris
Type 1244, Galileo User Range Accuracy (URA)
Type 1245, High-rate Galileo clock corrections to Broadcast Ephemeris
Type 1246, QZSS orbit corrections to Broadcast Ephemeris
Type 1247, QZSS clock corrections to Broadcast Ephemeris
Type 1248, QZSS code biases
Type 1249, Combined orbit and clock corrections to QZSS Broadcast Ephemeris
Type 1250, QZSS User Range Accuracy (URA)
Type 1251, High-rate QZSS clock corrections to Broadcast Ephemeris
Type 1252, SBAS orbit corrections to Broadcast Ephemeris
Type 1253, SBAS clock corrections to Broadcast Ephemeris
Type 1254, SBAS code biases
Type 1255, Combined orbit and clock corrections to SBAS Broadcast Ephemeris
Type 1256, SBAS User Range Accuracy (URA)
Type 1257, High-rate SBAS clock corrections to Broadcast Ephemeris
Type 1258, BDS orbit corrections to Broadcast Ephemeris
Type 1259, BDS clock corrections to Broadcast Ephemeris
Type 1260, BDS code biases
Type 1261, Combined orbit and clock corrections to BDS Broadcast Ephemeris
Type 1262, BDS User Range Accuracy (URA)
Type 1263, High-rate BDS clock corrections to Broadcast Ephemeris
Type 1264 SSR Ionosphere VTEC Spherical Harmonics
Type 1265 SSR GPS Satellite Phase Bias
Type 1266 SSR Satellite GLONASS Phase Bias
Type 1267 SSR Satellite Galileo Phase Bias
Type 1268 SSR Satellite QZSS Phase Bias
Type 1269 SSR Satellite SBAS Phase Bias
Type 1270 SSR Satellite BDS Phase Bias

@@ -4834,40 +4969,39 @@ The following are so-called 'Multiple Signal Messages' (MSM):

Type 1071, Compact GPS pseudo-ranges
Type 1072, Compact GPS carrier phases
Type 1073, Compact GPS pseudo-ranges and carrier phases
Type 1074, Full GPS pseudo-ranges and carrier phases plus signal strength
Type 1075, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength
Type 1076, Full GPS pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1077, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1081, Compact GLONASS pseudo-ranges
Type 1082, Compact GLONASS carrier phases
Type 1083, Compact GLONASS pseudo-ranges and carrier phases
Type 1084, Full GLONASS pseudo-ranges and carrier phases plus signal strength
Type 1085, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength
Type 1086, Full GLONASS pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1087, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1091, Compact Galileo pseudo-ranges
Type 1092, Compact Galileo carrier phases
Type 1093, Compact Galileo pseudo-ranges and carrier phases
Type 1094, Full Galileo pseudo-ranges and carrier phases plus signal strength
Type 1095, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength
Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1121, Compact BeiDou pseudo-ranges
Type 1122, Compact BeiDou carrier phases
Type 1123, Compact BeiDou pseudo-ranges and carrier phases
Type 1124, Full BeiDou pseudo-ranges and carrier phases plus signal strength
Type 1125, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength
Type 1126, Full BeiDou pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1127, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1111, Compact QZSS pseudo-ranges
Type 1112, Compact QZSS carrier phases
Type 1113, Compact QZSS pseudo-ranges and carrier phases
Type 1114, Full QZSS pseudo-ranges and carrier phases plus signal strength
Type 1115, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength
Type 1116, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1117, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1071, Compact GPS pseudo-ranges
Type 1072, Compact GPS carrier phases
Type 1073, Compact GPS pseudo-ranges and carrier phases
Type 1074, Full GPS pseudo-ranges and carrier phases plus signal strength
Type 1075, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength
Type 1076, Full GPS pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1077, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1081, Compact GLONASS pseudo-ranges
Type 1082, Compact GLONASS carrier phases
Type 1083, Compact GLONASS pseudo-ranges and carrier phases
Type 1084, Full GLONASS pseudo-ranges and carrier phases plus signal strength
Type 1085, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength
Type 1086, Full GLONASS pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1087, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1091, Compact Galileo pseudo-ranges
Type 1092, Compact Galileo carrier phases
Type 1093, Compact Galileo pseudo-ranges and carrier phases
Type 1094, Full Galileo pseudo-ranges and carrier phases plus signal strength
Type 1095, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength
Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1121, Compact BeiDou pseudo-ranges
Type 1122, Compact BeiDou carrier phases
Type 1123, Compact BeiDou pseudo-ranges and carrier phases
Type 1124, Full BeiDou pseudo-ranges and carrier phases plus signal strength
Type 1125, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength
Type 1126, Full BeiDou pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1127, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
Type 1111, Compact QZSS pseudo-ranges
Type 1112, Compact QZSS carrier phases
Type 1113, Compact QZSS pseudo-ranges and carrier phases
Type 1114, Full QZSS pseudo-ranges and carrier phases plus signal strength
Type 1115, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength
Type 1116, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1117, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

@@ -4876,19 +5010,20 @@ The following are proposed 'Multiple Signal Messages' (MSM) under discussion for standardization:

Type 1101, Compact SBAS pseudo-ranges
Type 1102, Compact SBAS carrier phases
Type 1103, Compact SBAS pseudo-ranges and carrier phases
Type 1104, Full SBAS pseudo-ranges and carrier phases plus signal strength
Type 1105, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength
Type 1106, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)
Type 1107, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

- -

3.2 Command Line Help

Type 1101, Compact SBAS pseudo-ranges

Type 1102, Compact SBAS carrier phases

Type 1103, Compact SBAS pseudo-ranges and carrier phases

Type 1104, Full SBAS pseudo-ranges and carrier phases plus signal strength

Type 1105, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength

Type 1106, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)

Type 1107, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

+ +

3.2 Command Line Help

Command line option '--help' provides a complete list of all configuration parameters which can be specified via BNC's Command Line Interface (CLI). Note that command line options overrule configuration options specified in the configuration file. The following is the output produced when running BNC with command line option '--help':

 Usage:
@@ -5129,151 +5264,144 @@
                             CUT07,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7778"

3.3 Further Reading

- +

3.3 Further Reading

+ +Links:
- - - - - - - - - - - - - - - - + + + + + + + +

Links
Ntrip	http://igs.bkg.bund.de/ntrip/index
EUREF-IP Ntrip Broadcaster	http://www.euref-ip.net/home
IGS-IP Ntrip Broadcaster	http://www.igs-ip.net/home
IGS products Ntrip Broadcaster	http://products.igs-ip.net/home
IGS M-GEX Ntrip Broadcaster	http://mgex.igs-ip.net/home
IGS Central Bureau Ntrip Broadcaster	http://rt.igs.org
IGS Real-time Service	http://rts.igs.org
Distribution of IGS-IP streams	http://www.igs.oma.be/real_time/
Completeness and latency of IGS-IP data	http://www.igs.oma.be/highrate/
Ntrip Broadcaster overview	http://www.rtcm-ntrip.org/home
Ntrip Open Source software code	http://software.rtcm-ntrip.org
EUREF-IP Project	http://www.epncb.oma.be/euref_IP
Real-time IGS Pilot Project	http://www.rtigs.net/pilot
Radio Technical Commission for Maritime Services	http://www.rtcm.org +
Ntrip	http://igs.bkg.bund.de/ntrip/index
IGS Real-time Service	http://rts.igs.org
Distribution of IGS-IP streams	http://www.igs.oma.be/real_time/
Completeness and latency of IGS-IP data	http://www.igs.oma.be/highrate/
Ntrip Broadcaster overview	http://www.rtcm-ntrip.org/home
Ntrip Open Source software code	http://software.rtcm-ntrip.org
EUREF-IP Project	http://www.epncb.oma.be/euref_IP
Real-time IGS Pilot Project	http://www.rtigs.net/pilot
Radio Technical Commission for Maritime Services	http://www.rtcm.org

-
+ +Publications:
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +

Caissy, M., L. Agrotis, G. Weber, M. Hernandez-Pajares and U. Hugentobler (2012)	The International GNSS Real-Time Service. GPS World, June 1, 2012.
Estey, L. H. and C. M. Meertens (1999)	TEQC: The Multi-Purpose Toolkit for GPS/GLONASS Data. GPS Solutions, Vol. 3, No. 1, pp. 42-49, 1999.
Huisman, L., P. Teunissen and C. Hu (2012)	GNSS Precise Point Positioning in Regional Reference Frames Using Real-time Broadcast Corrections. Journal of Applied Geodesy, Vol. 6, pp15-23, 2012.
Mervart, L., Z. Lukes, C. Rocken and T. Iwabuchi (2008)	Precise Point Positioning With Ambiguity Resolution in Real-Time. ION GNSS 2008.
RTCM SC-104 (2011)	Amendment 1 to RTCM Standard 10410.1 Networked Transport of RTCM via Internet Protocol (Ntrip) - Version 2.0. RTCM Papter 139-2011-SC104-STD, 2011.
Rupprecht, W. (2000)	DGPS-IP. http://www.wsrcc.com/wolfgang/gps/dgps-ip.html, 2000.
Weber, G., D. Dettmering and H. Gebhard (2005a)	Networked Transport of RTCM via Internet Protocol (NTRIP). In: Sanso F. (Ed.): A Window on the Future, Proceedings of the IAG General Assembly, Sapporo, Japan, 2003, Springer Verlag, Symposia Series, Vol. 128, p. 60-64, 2005.
Weber, G., D. Dettmering, H. Gebhard and R. Kalafus (2005b)	Networked Transport of RTCM via Internet Protocol (Ntrip), IP-Streaming for Real-Time GNSS Applications. ION GNSS 2005.
Weber, G., and M. Honkala (2004)	The future is talking Ntrip. Newsletter, Trimble GmbH Raunheim, Germany, 2004.
Weber, G. and L. Mervart (2009)	The BKG Ntrip Client (BNC), Report on EUREF Symposium 2007 in London. Mitteilungen des Bundesamtes fuer Kartographie und Geodaesie, Band 42, Frankfurt, 2009.
Weber, G. and L. Mervart (2010)	Real-time Combination of GNSS Orbit and Clock Correction Streams Using a Kalman Filter Approach. ION GNSS 2010.
Weber, G, L. Mervart, Z. Lukes, C. Rocken and J. Dousa (2007)	Real-time Clock and Orbit Corrections for Improved Point Positioning via Ntrip. ION GNSS 2007.
Weber, G., L. Mervart, A. Stürze, A. Rülke and D. Stöcker (2016)	BKG Ntrip Client, Version 2.12. Mitteilungen des Bundesamtes für Kartographie und Geodäsie, Vol. 49, Frankfurt am Main, 2016.

+ +

3.4 Abbreviations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Publications
Caissy, M., L. Agrotis, G. Weber, M. Hernandez-Pajares and U. Hugentobler (2012)	The International GNSS Real-Time Service. GPS World, June 1, 2012.
Estey, L. H. and C. M. Meertens (1999)	TEQC: The Multi-Purpose Toolkit for GPS/GLONASS Data. GPS Solutions, Vol. 3, No. 1, pp. 42-49, 1999.
Huisman, L., P. Teunissen and C. Hu (2012)	GNSS Precise Point Positioning in Regional Reference Frames Using Real-time Broadcast Corrections. Journal of Applied Geodesy, Vol. 6, pp15-23, 2012.
Mervart, L., Z. Lukes, C. Rocken and T. Iwabuchi (2008)	Precise Point Positioning With Ambiguity Resolution in Real-Time. ION GNSS 2008.
RTCM SC-104 (2011)	Amendment 1 to RTCM Standard 10410.1 Networked Transport of RTCM via Internet Protocol (Ntrip) - Version 2.0. RTCM Papter 139-2011-SC104-STD, 2011.
Rupprecht, W. (2000)	DGPS-IP. http://www.wsrcc.com/wolfgang/gps/dgps-ip.html, 2000.
Weber, G., D. Dettmering and H. Gebhard (2005a)	Networked Transport of RTCM via Internet Protocol (NTRIP). In: Sanso F. (Ed.): A Window on the Future, Proceedings of the IAG General Assembly, Sapporo, Japan, 2003, Springer Verlag, Symposia Series, Vol. 128, p. 60-64, 2005.
Weber, G., D. Dettmering, H. Gebhard and R. Kalafus (2005b)	Networked Transport of RTCM via Internet Protocol (Ntrip), IP-Streaming for Real-Time GNSS Applications. ION GNSS 2005.
Weber, G., and M. Honkala (2004)	The future is talking Ntrip. Newsletter, Trimble GmbH Raunheim, Germany, 2004.
Weber, G. and L. Mervart (2009)	The BKG Ntrip Client (BNC), Report on EUREF Symposium 2007 in London. Mitteilungen des Bundesamtes fuer Kartographie und Geodaesie, Band 42, Frankfurt, 2009.
Weber, G. and L. Mervart (2010)	Real-time Combination of GNSS Orbit and Clock Correction Streams Using a Kalman Filter Approach. ION GNSS 2010.
Weber, G, L. Mervart, Z. Lukes, C. Rocken and J. Dousa (2007)	Real-time Clock and Orbit Corrections for Improved Point Positioning via Ntrip. ION GNSS 2007.
Weber, G., L. Mervart, A. Stürze, A. Rülke and D. Stöcker (2016)	BKG Ntrip Client, Version 2.12. Mitteilungen des Bundesamtes für Kartographie und Geodäsie, Vol. 49, Frankfurt am Main, 2016.
AC	Analysis Center
AFREF	IAG Reference Frame Sub-Commission for Africa
ANTEX	Antenna Exchange Format
APC	Antenna Phase Center
APREF	IAG Reference Frame Sub-Commission for Asia and Pacific
ARP	Antenna Reference Point
BKG	Bundesamt für Kartographie und Geodäsie
BNC	BNK Ntrip Client
BSW	Bernese GNSS Software
CC	Combination Center
CLI	Command Line Interface
CoM	Center Of Mass
DGNSS	Differential GNSS
DGPS-IP	Differential GPS via Internet Protocol
DMG	Disk Image, File
DREF91	Geodetic Datum for Germany 1991
ECEF	Earth-Centred-Earth-Fixed
EDGE	Enhanced Data Rates for GSM Evolution
ETRF2000	European Terrestrial Reference Frame 2000
EUREF	IAG Reference Frame Sub-Commission for Europe
EoE	End of Epoch
FKP	Flächen-Korrektur-Parameter
FTP	File Transfer Protocol
GDA2020	Geodetic Datum Australia 2020
GM	Google Maps
GNSS	Global Navigation Satellite System
GNU	GNU's Not Unix
GPL	General Public License
GPRS	General Packet Radio Service
GPSWD	GPS Week and Day
GSM	Global System for Mobile Communications
GUI	Graphical User Interface
HP MSM	High Precision Multiple Signal Messages
HR URA	High Rate User Range Accuracy
HTTP	Hypertext Transfer Protocol
HTTPS	Hypertext Transfer Protocol Secure
IAG	International Association of Geodesy
ICECAST	Streaming Media Server
IGS14	IGS Reference Frame 2014
IGS	International GNSS Service
IOD	Issue of Data
IP	Internet Protocol
ITRF2014	International Terrestrial Reference Frame 2014
L3	Ionosphere-Free Linear Combination Of Phase Observations
LAN	Local Area Network
LC	Linea Combination
M-GEX	Multi GNSS-Experiment
MAC	Master Auxiliary Concept
MJD	Modified Julian Date
MSI	Microsoft Installer, File
MSM	Multiple Signal Messages
MW	Melbourne Wübbena Linear Combination
NAD83	North American Datum 1983
NAREF	IAG Reference Frame Sub-Commission for North America
NMEA	National Marine Electronics Association Format
Ntrip	Networked Transport of RTCM via Internet Protocol
OSM	OpenStreetMap
OSR	Observation Space Representation
P3	Ionosphere-Free Linear Combination Of Code Observations
PDOP	Positional Dilution Of Precision
PNG	Portable Network Graphics
PPP	Precise Point Positioning
Qt	Cross-Platform Application Framework
REQC	RINEX Editing and Quality Checking
RINEX	Receiver Independent Exchange Format
RTCM SC-104	Radio Technical Commission for Maritime Services, Special Committee 104
RTK	Real Time Kinematic
RTKPLOT	View and Plot Positioning Solutions Software, Part of RTKLIB
RTNET	Real-Time Network Format
RTP	Real-Time Transport Protocol
RTSP	Real-Time Streaming Protocol
SBAS	Space Based Augmentation System
SINEX TRO	Troposphere Solution Independent Exchange Format
SINEX	Solution Independent Exchange Format
SIRGAS2000	Geodetic Datum for Latin America and Caribbean 2000
SIRGAS	IAG Reference Frame Sub-Commission for Latin America and Caribbean
SP3	Standard Product # 3
SPP	Single Point Positioning
SSL	Secure Sockets Layer
SSR	State Space Representation
SVN	Subversion, Revision Control System
TCP	Transmission Control Protocol
TEQC	Translation, Editing and Quality Checking
TLS	Transport Layer Security
UDP	User Datagram Protocol
UMTS	Universal Mobile Telecommunications System
URA	User Range Accuracy
VRS	Virtual Reference Station
VTEC	Vertical Total Electron Content

3.4 Abbreviations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

AC	Analysis Center
AFREF	IAG Reference Frame Sub-Commission for Africa
ANTEX	Antenna Exchange Format
APC	Antenna Phase Center
APREF	IAG Reference Frame Sub-Commission for Asia and Pacific
ARP	Antenna Reference Point
BKG	Bundesamt für Kartographie und Geodäsie
BNC	BNK Ntrip Client
BSW	Bernese GNSS Software
CC	Combination Center
CLI	Command Line Interface
CoM	Center Of Mass
DGNSS	Differential GNSS
DGPS-IP	Differential GPS via Internet Protocol
DMG	Disk Image, File
DREF91	Geodetic Datum for Germany 1991
ECEF	Earth-Centred-Earth-Fixed
EDGE	Enhanced Data Rates for GSM Evolution
ETRF2000	European Terrestrial Reference Frame 2000
EUREF	IAG Reference Frame Sub-Commission for Europe
EoE	End of Epoch
FKP	Flächen-Korrektur-Parameter
FTP	File Transfer Protocol
GDA2020	Geodetic Datum Australia 2020
GM	Google Maps
GNSS	Global Navigation Satellite System
GNU	GNU's Not Unix
GPL	General Public License
GPRS	General Packet Radio Service
GPSWD	GPS Week and Day
GSM	Global System for Mobile Communications
GUI	Graphical User Interface
HP MSM	High Precision Multiple Signal Messages
HR URA	High Rate User Range Accuracy
HTTP	Hypertext Transfer Protocol
HTTPS	Hypertext Transfer Protocol Secure
IAG	International Association of Geodesy
ICECAST	Streaming Media Server
IGS14	IGS Reference Frame 2014
IGS	International GNSS Service
IOD	Issue of Data
IP	Internet Protocol
ITRF2014	International Terrestrial Reference Frame 2014
L3	Ionosphere-Free Linear Combination Of Phase Observations
LAN	Local Area Network
LC	Linea Combination
M-GEX	Multi GNSS-Experiment
MAC	Master Auxiliary Concept
MJD	Modified Julian Date
MSI	Microsoft Installer, File
MSM	Multiple Signal Messages
MW	Melbourne Wübbena Linear Combination
NAD83	North American Datum 1983
NAREF	IAG Reference Frame Sub-Commission for North America
NMEA	National Marine Electronics Association Format
Ntrip	Networked Transport of RTCM via Internet Protocol
OSM	OpenStreetMap
OSR	Observation Space Representation
P3	Ionosphere-Free Linear Combination Of Code Observations
PDOP	Positional Dilution Of Precision
PNG	Portable Network Graphics
PPP	Precise Point Positioning
Qt	Cross-Platform Application Framework
REQC	RINEX Editing and Quality Checking
RINEX	Receiver Independent Exchange Format
RTCM SC-104	Radio Technical Commission for Maritime Services, Special Committee 104
RTK	Real Time Kinematic
RTKPLOT	View and Plot Positioning Solutions Software, Part of RTKLIB
RTNET	Real-Time Network Format
RTP	Real-Time Transport Protocol
RTSP	Real-Time Streaming Protocol
SBAS	Space Based Augmentation System
SINEX TRO	Troposphere Solution Independent Exchange Format
SINEX	Solution Independent Exchange Format
SIRGAS2000	Geodetic Datum for Latin America and Caribbean 2000
SIRGAS	IAG Reference Frame Sub-Commission for Latin America and Caribbean
SP3	Standard Product # 3
SPP	Single Point Positioning
SSL	Secure Sockets Layer
SSR	State Space Representation
SVN	Subversion, Revision Control System
TCP	Transmission Control Protocol
TEQC	Translation, Editing and Quality Checking
TLS	Transport Layer Security
UDP	User Datagram Protocol
UMTS	Universal Mobile Telecommunications System
URA	User Range Accuracy
VRS	Virtual Reference Station
VTEC	Vertical Total Electron Content

+ + Index: /trunk/BNC/src/bnchlpdlg.cpp =================================================================== --- /trunk/BNC/src/bnchlpdlg.cpp (revision 8237) +++ /trunk/BNC/src/bnchlpdlg.cpp (revision 8238) @@ -35,5 +35,5 @@ * Created: 24-Sep-2006 * - * Changes: + * Changes: * * -----------------------------------------------------------------------*/ @@ -86,5 +86,5 @@ setLayout(dlgLayout); - resize(60*ww, 60*ww); + resize(110*ww, 100*ww); show(); }

Fig.	Title	Chapter
1	Flowchart, BNC connected to a GNSS rover for Precise Point Positioning	1.3
2	Flowchart, BNC converting RTCM streams to RINEX batches	1.3
3	Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections	1.3
4	Flowchart, BNC combining Broadcast Correction streams	1.3
5	Sections on BNC's main window	1.4
6	Management of configuration options in BNC	1.6
7	BNC's 'Network' panel configured to ignore eventually occurring SSL error messages	2.2.2
8	BNC translating incoming streams to 15 min RINEX Version 3 files	2.4
9	BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files	2.5.5
10	Example for BNC's 'RINEX Editing Options' window	2.6.7
11	Example for RINEX file concatenation with BNC	2.6.7
12	Example for creating RINEX quality check analysis graphics output with BNC	2.6.7
13	Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC	2.6.7
14	Sky plot examples for multipath, part of RINEX quality check analysis with BNC	2.6.7
15	Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC	2.6.7
16	Example for comparing two SP3 files with satellite orbit and clock data using BNC	2.7.3
17	Example for pulling, saving and output of Broadcast Corrections using BNC	2.8.3
18	Synchronized BNC output via IP port to feed a GNSS real-time engine	2.9
19	Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is mandatory for VRS streams	2.10
20	BNC pulling a VRS stream to feed a serially connected RTK rover	2.10
21	RTCM message numbers, latencies and observation types logged by BNC	2.12
22	Real-time Precise Point Positioning with BNC, PPP Panel 1	2.13.1
23	Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization	2.13.2
24	Precise Point Positioning with BNC, PPP Panel 3	2.13.3
25	Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 4	2.13.3.8
26	Track of positions from BNC with Google Maps in background	2.13.4.3
27	Example for background map from Google Maps and OpenStreetMap (OSM) resources	2.13.4.3.1
28	BNC combining Broadcast Correction streams	2.14
29	INTERNAL' PPP with BNC using a combination of Broadcast Corrections	2.14
30	Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'	2.15.3
31	BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster	2.15.11
32	BNC uploading a combined Broadcast Correction stream	2.15.11
33	BNC producing Broadcast Ephemeris stream from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster	2.16.3
34	Bandwidth consumption of RTCM streams received by BNC	2.18.2
35	Latency of RTCM streams received by BNC	2.18.3
36	Example for time series plot of displacements produced by BNC	2.18.4
37	Steam input communication links accepted by BNC	2.19
38	BNC's 'Select Broadcaster' table	2.19.1.1.2
39	Broadcaster source-table shown by BNC	2.19.1.1.4
40	Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table	2.19.1.1.6
41	BNC configuration for pulling a stream via serial port	2.19.1.4
Fig.	Title	Chapter
1	Flowchart, BNC connected to a GNSS rover for Precise Point Positioning	1.3
2	Flowchart, BNC converting RTCM streams to RINEX batches	1.3
3	Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections	1.3
4	Flowchart, BNC combining Broadcast Correction streams	1.3
5	Sections on BNC's main window	1.4
6	Management of configuration options in BNC	1.6
7	BNC's 'Network' panel configured to ignore eventually occurring SSL error messages	2.2.2
8	BNC translating incoming streams to 15 min RINEX Version 3 files	2.4
9	BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files	2.5.5
10	Example for BNC's 'RINEX Editing Options' window	2.6.7
11	Example for RINEX file concatenation with BNC	2.6.7
12	Example for creating RINEX quality check analysis graphics output with BNC	2.6.7
13	Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC	2.6.7
14	Sky plot examples for multipath, part of RINEX quality check analysis with BNC	2.6.7
15	Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC	2.6.7
16	Example for comparing two SP3 files with satellite orbit and clock data using BNC	2.7.3
17	Example for pulling, saving and output of Broadcast Corrections using BNC	2.8.3
18	Synchronized BNC output via IP port to feed a GNSS real-time engine	2.9
19	Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is mandatory for VRS streams	2.10
20	BNC pulling a VRS stream to feed a serially connected RTK rover	2.10
21	RTCM message numbers, latencies and observation types logged by BNC	2.12
22	Real-time Precise Point Positioning with BNC, PPP Panel 1	2.13.1
23	Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization	2.13.2
24	Precise Point Positioning with BNC, PPP Panel 3	2.13.3
25	Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 4	2.13.3.8
26	Track of positions from BNC with Google Maps in background	2.13.4.3
27	Example for background map from Google Maps and OpenStreetMap (OSM) resources	2.13.4.3.1
28	BNC combining Broadcast Correction streams	2.14
29	INTERNAL' PPP with BNC using a combination of Broadcast Corrections	2.14
30	Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'	2.15.3
31	BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster	2.15.11
32	BNC uploading a combined Broadcast Correction stream	2.15.11
33	BNC producing Broadcast Ephemeris stream from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster	2.16.3
34	Bandwidth consumption of RTCM streams received by BNC	2.18.2
35	Latency of RTCM streams received by BNC	2.18.3
36	Example for time series plot of displacements produced by BNC	2.18.4
37	Steam input communication links accepted by BNC	2.19
38	BNC's 'Select Broadcaster' table	2.19.1.1.2
39	Broadcaster source-table shown by BNC	2.19.1.1.4
40	Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table	2.19.1.1.6
41	BNC configuration for pulling a stream via serial port	2.19.1.4

Tab.	Title	Chapter
1	Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems	1.2
2	Contents and format of synchronized output of observations feeding a GNSS engine	2.9
Tab.	Title	Chapter
1	Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems	1.2
2	Contents and format of synchronized output of observations feeding a GNSS engine	2.9


Pseudo-Range Data
Pseudo-Range Data
Observation Code	C1C	1X,A3
Pseudo-Range Observation	25394034.112	1X,F14.3

Carrier Phase Data
Carrier Phase Data
Observation Code	L1C	1X,A3
Carrier Phase Observation	133446552.870	1X,F14.3

Doppler Data
Doppler Data
Observation Code	D1C	1X,A3
Doppler Observation	-87.977	1X,F14.3

Signal Strength
Signal Strength
Observation Code	S2W	1X,A3
Observed Signal Strength	34.750	1X,F8.3

CUT018671.nmea	NMEA filename, suffix 'nmea'
CUT018671.ppp	PPP logfile name, suffix 'ppp'
CUT018671J30.tro	SINEX Troposphere filename, suffix 'tro'
CUT018671.nmea	NMEA filename, suffix 'nmea'
CUT018671.ppp	PPP logfile name, suffix 'ppp'
CUT018671J30.tro	SINEX Troposphere filename, suffix 'tro'

Key	Values
APC	Satellite Antenna Phase Center coordinates in meters
Clk	Satellite clock correction in meters, relativistic correction applied like in broadcast clocks
Vel	Satellite velocity in meters per second
CoM	Satellite Center of Mass coordinates in meters
CodeBias	Satellite Code Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3 and preceded by total number of biases
YawAngle	Satellite Yaw Angle in radian, restricted to be in [0, 2π] which shall be used for the computation of phase wind-up correction
YawRate	Satellite Yaw Rate in radian per second which is the rate of Yaw Angle
PhaseBias	Satellite Phase Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3, preceded by total number of biases and followed by Signal Integer Indicator, Signals Wilde-Lane Integer Indicator as well as Signal Discontinuity Counter
Key	Values
APC	Satellite Antenna Phase Center coordinates in meters
Clk	Satellite clock correction in meters, relativistic correction applied like in broadcast clocks
Vel	Satellite velocity in meters per second
CoM	Satellite Center of Mass coordinates in meters
CodeBias	Satellite Code Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3 and preceded by total number of biases
YawAngle	Satellite Yaw Angle in radian, restricted to be in [0, 2π] which shall be used for the computation of phase wind-up correction
YawRate	Satellite Yaw Rate in radian per second which is the rate of Yaw Angle
PhaseBias	Satellite Phase Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3, preceded by total number of biases and followed by Signal Integer Indicator, Signals Wilde-Lane Integer Indicator as well as Signal Discontinuity Counter

Key	Values
IND	Stands for phase bias information and is followed by Dispersive Bias Consistency Indicator and MW Consistency Indicator
VTEC	Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric Layers
Key	Values
IND	Stands for phase bias information and is followed by Dispersive Bias Consistency Indicator and MW Consistency Indicator
VTEC	Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric Layers

'resource loader'	Ntrip Broadcaster URL and port, or TCP/IP host and port, or UDP port, or Serial input port specification.
'mountpoint'	Mountpoint introduced by Ntrip Broadcaster, or Mountpoint introduced by BNC's user.
'decoder'	Name of decoder used to handle the incoming stream content according to its format; editable.
'lat'	Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.
'long'	Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.
'nmea'	Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'.
'ntrip'	Selected Ntrip transport protocol version (1, 2, 2s, R, or U), or 'N' for TCP/IP streams without Ntrip, or 'UN' for UDP streams without Ntrip, or 'S' for serial input streams without Ntrip.
'bytes'	Number of bytes received. +
'resource loader'	Ntrip Broadcaster URL and port, or TCP/IP host and port, or UDP port, or Serial input port specification.
'mountpoint'	Mountpoint introduced by Ntrip Broadcaster, or Mountpoint introduced by BNC's user.
'decoder'	Name of decoder used to handle the incoming stream content according to its format; editable.
'lat'	Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.
'long'	Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.
'nmea'	Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'.
'ntrip'	Selected Ntrip transport protocol version (1, 2, 2s, R, or U), or 'N' for TCP/IP streams without Ntrip, or 'UN' for UDP streams without Ntrip, or 'S' for serial input streams without Ntrip.
'bytes'	Number of bytes received.

Option	Meaning
1	Ntrip Version 1, TCP/IP
2	Ntrip Version 2 in TCP/IP mode
2s	Ntrip Version 2 in TCP/IP mode via SSL
R	Ntrip Version 2 in RTSP/RTP mode
U	Ntrip Version 2 in UDP mode
Option	Meaning
1	Ntrip Version 1, TCP/IP
2	Ntrip Version 2 in TCP/IP mode
2s	Ntrip Version 2 in TCP/IP mode via SSL
R	Ntrip Version 2 in RTSP/RTP mode
U	Ntrip Version 2 in UDP mode

1. General Information

1. General Information

1.1 Purpose

1.1 Purpose

1.2 Supported GNSS

1.3 Data Flow

1.3 Data Flow

1.4 Handling

1.5 Installation

1.5.1 Compilation

1.6 Configuration

1.6 Configuration

1.6.1 Examples

1.6.1 Examples

1.7 Limitations

1.7 Limitations

1.8 Looking Back

Looking Back

2. Settings Details

2.1 Top Menu Bar

2.1.1 File

2.1.2 Help

2.2 Network

2.2.1 Proxy - Usage in a protected LAN

2.2.2 SSL - Transport Layer Security

2.3 General

2.3.1 Logfile - optional

2.3.2 Append Files - optional

2.3.3 Reread Configuration - optional

2.3.4 Auto Start - optional

2.3.5 Raw Output File - optional

2.4 RINEX Observations

2.4.1 RINEX Filenames

2.4.2 Directory - optional

2.4.3 File Interval - mandatory if 'Directory' is set

2.4.4 Sampling - mandatory if 'Directory' is set

2.4.5 Skeleton Extension - optional

2.4.6 Skeleton Mandatory - optional

2.4.6 Skeleton Mandatory - optional

2.4.7 Script - optional

2.4.8 Version 2 - optional

2.4.9 Version 3 - optional

2.4.10 Version 3 Filenames - optional

2.5 RINEX Ephemeris

2.5.1 Directory - optional

2.5.2 Interval - mandatory if 'Directory' is set

2.5.3 Port - optional

2.5.4 Version - optional

2.5.5 Version 3 Filenames - optional

2.6 RINEX Editing & QC

2.6.1 Action - optional

2.6.2 Input Files - mandatory

2.6.3 Output Files - optional if 'Action' is set to 'Edit/Concatenate'

2.6.4 Logfile - optional

2.6.5 Plots for Signals - mandatory if 'Action' is set to 'Analyze'

2.6.6 Directory for Plots - optional if 'Action' is set to 'Analyze'

2.6.7 Set Edit Options - mandatory if 'Action' is set to 'Edit/Concatenate'

2.6.8 Command Line, No Window - optional

2.6.7 SP3 Comparison

2.7.1 Input SP3 Files - optional

2.7.2 Exclude Satellites - optional

2.7.3 Logfile - mandatory if 'Input SP3 Files' is set

2.8 Broadcast Corrections

2.8.1 Directory, ASCII - optional

2.8.2 Interval - mandatory if 'Directory, ASCII' is set

2.8.3 Port - optional

2.9 Feed Engine

2.9.1 Port - optional

2.9.1 Port - optional

2.9.2 Wait for Full Obs Epoch - mandatory if 'Port' is set

2.9.3 Sampling - mandatory if 'File' or 'Port' is set

2.9.4 File - optional

2.9.5 Port (unsynchronized) - optional

2.10 Serial Output

2.10.1 Mountpoint - optional

2.10.2 Port Name - mandatory if 'Mountpoint' is set

2.10.3 Baud Rate - mandatory if 'Mountpoint' is set

2.10.4 Flow Control - mandatory if 'Mountpoint' is set

2.10.5 Parity - mandatory if 'Mountpoint' is set

2.10.6 Data Bits - mandatory if 'Mountpoint' is set