Index: trunk/BNC/CHANGELOG.md
===================================================================
--- trunk/BNC/CHANGELOG.md	(revision 11018)
+++ trunk/BNC/CHANGELOG.md	(revision 11019)
@@ -1,3 +1,6 @@
 # Changelog
+## 2.13.8 (2026-10-??)
+- ADDED: epoch/velocity fields to PPP coordinates file to allow BNC to propagate the reference coordinates related to a dedicated reference epoch to the current processing epoch internally
+
 ## 2.13.7 (2026-07-31)
 - ADDED: PPP-AR Algorithm description is now part of BNCs help contents
Index: trunk/BNC/src/PPP/pppClient.cpp
===================================================================
--- trunk/BNC/src/PPP/pppClient.cpp	(revision 11018)
+++ trunk/BNC/src/PPP/pppClient.cpp	(revision 11019)
@@ -450,5 +450,11 @@
 
   if (_opt->xyzAprRoverSet()) {
-    station->setXyzApr(_opt->_xyzAprRover);
+    if (_opt->_refEpochRover != 0.0) {
+      double dt = decimalYear(time) - _opt->_refEpochRover;
+      station->setXyzApr(_opt->_xyzAprRover + dt * _opt->_velRover);
+    }
+    else {
+      station->setXyzApr(_opt->_xyzAprRover);
+    }
   }
   else {
Index: trunk/BNC/src/bnchelp.html
===================================================================
--- trunk/BNC/src/bnchelp.html	(revision 11018)
+++ trunk/BNC/src/bnchelp.html	(revision 11019)
@@ -4,9 +4,9 @@
 
 <head>
-  <meta charset="utf-8"/>
-  <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+  <meta charset="utf-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
   <title>BKG Ntrip Client | Help</title>
   <style>
-    html *{
+    html * {
       font-size: 1em !important;
       color: #000 !important;
@@ -21,33 +21,34 @@
 
 <body>
-<div>
-  <img src="IMG/BKG_Logo_oS.jpg" alt="bkg_logo" style="float:left;width:100px;margin-left:20px;margin-top:20px;"/>
-  <img src="ntrip-logo.png" alt="ntrip_logo" style="float:right;width:80px;margin-right:20px;margin-top:20px;"/>
-</div>
-<br><br><br><br><br><br>
-
-<div class="center">
-  <h1>BKG Ntrip Client (BNC)</h1>
+  <div>
+    <img src="IMG/BKG_Logo_oS.jpg" alt="bkg_logo" style="float:left;width:100px;margin-left:20px;margin-top:20px;" />
+    <img src="ntrip-logo.png" alt="ntrip_logo" style="float:right;width:80px;margin-right:20px;margin-top:20px;" />
+  </div>
+  <br><br><br><br><br><br>
+
+  <div class="center">
+    <h1>BKG Ntrip Client (BNC)</h1>
+    <br>
+    <h3>A toolkit for retrieving, decoding, converting and processing<br> real-time GNSS data streams</h3>
+    <br>
+    <h3>Version 2.13</h3>
+  </div>
   <br>
-  <h3>A toolkit for retrieving, decoding, converting and processing<br> real-time GNSS data streams</h3>
+
+  <h4>Authors</h4>
+  <p>
+    Georg Weber<sup>(1)</sup>, Leo&scaron; Mervart<sup>(2)</sup>, Andrea St&uuml;rze<sup>(1)</sup>, Dirk
+    St&ouml;cker<sup>(3)</sup><br><br>
+
+    <sup>(1) Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany</sup><br>
+    <sup>(2) Czech Technical University (CTU), Department of Geomatics, Prague, Czech Republic</sup><br>
+    <sup>(3) Alberding GmbH, Wildau, Germany</sup>
+  </p>
   <br>
-  <h3>Version 2.13</h3>
-</div>
-<br>
-
-<h4>Authors</h4>
-<p>
-Georg Weber<sup>(1)</sup>, Leo&scaron; Mervart<sup>(2)</sup>, Andrea St&uuml;rze<sup>(1)</sup>, Dirk St&ouml;cker<sup>(3)</sup><br><br>
-
-<sup>(1) Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany</sup><br>
-<sup>(2) Czech Technical University (CTU), Department of Geomatics, Prague, Czech Republic</sup><br>
-<sup>(3) Alberding GmbH, Wildau, Germany</sup>
-</p>
-<br>
-
-<h4>Contact</h4>
-<p>
-Feel free to send comments, suggestions or bug reports to:
-<pre>
+
+  <h4>Contact</h4>
+  <p>
+    Feel free to send comments, suggestions or bug reports to:
+  <pre>
  Federal Agency for Cartography and Geodesy (BKG)
  Department of Geodesy, Section Satellite Navigation
@@ -56,1325 +57,2509 @@
  email: igs-ip@bkg.bund.de
 </pre>
-</p>
-<br>
-
-<h4>Legal Notice</h4>
-<p>
-BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive
- <a href="https://software.rtcm-ntrip.org/svn/trunk/BNC" target="_blank">https://software.rtcm-ntrip.org/svn/trunk/BNC</a>.
- Precompiled binaries of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded from
- <a href="https://igs.bkg.bund.de/ntrip/bnc" target="_blank">https://igs.bkg.bund.de/ntrip/bnc</a>.
- <br>
- Copyright &copy;<sup>&nbsp;</sup> 2005-2023 Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany
-</p>
-<br>
-
-<h4>Citation</h4>
-<p>
-To help justify funding the development of BNC,<sup>&nbsp;</sup>we kindly ask users to include a citation when applying the software results in a publication. We suggest:
-<br>
-<pre>
+  </p>
+  <br>
+
+  <h4>Legal Notice</h4>
+  <p>
+    BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software
+    archive
+    <a href="https://software.rtcm-ntrip.org/svn/trunk/BNC"
+      target="_blank">https://software.rtcm-ntrip.org/svn/trunk/BNC</a>.
+    Precompiled binaries of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded from
+    <a href="https://igs.bkg.bund.de/ntrip/bnc" target="_blank">https://igs.bkg.bund.de/ntrip/bnc</a>.
+    <br>
+    Copyright &copy;<sup>&nbsp;</sup> 2005-2023 Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany
+  </p>
+  <br>
+
+  <h4>Citation</h4>
+  <p>
+    To help justify funding the development of BNC,<sup>&nbsp;</sup>we kindly ask users to include a citation when
+    applying the software results in a publication. We suggest:
+    <br>
+  <pre>
   Weber, G., L. Mervart, A. St&uuml;rze, A. R&uuml;lke and D. St&ouml;cker (2016):
     BKG Ntrip Client, Version 2.12. Mitteilungen des Bundesamtes
     f&uuml;r Kartographie und Geod&auml;sie, Vol. 49, Frankfurt am Main, 2016.
 </pre>
-</p>
-<br>
-
-<h4>Table of Contents</h4>
-<p>
-<b>1.</b> <a href="#genInstruction"><b>General Information</b></a><br><br>
-&nbsp; &nbsp; &nbsp; 1.1 <a href="#introPurpose">Purpose</a><br>
-&nbsp; &nbsp; &nbsp; 1.2 <a href="#introSystem">Supported GNSS</a><br>
-&nbsp; &nbsp; &nbsp; 1.3 <a href="#introFlow">Data Flow</a><br>
-&nbsp; &nbsp; &nbsp; 1.4 <a href="#introHandling">Handling</a><br>
-&nbsp; &nbsp; &nbsp; 1.5 <a href="#introInst">Installation</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1.5.1 <a href="#introCompile">Compilation</a><br>
-&nbsp; &nbsp; &nbsp; 1.6 <a href="#introConf">Configuration</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1.6.1 <a href="#introExamples">Examples</a><br>
-&nbsp; &nbsp; &nbsp; 1.7 <a href="#introLimit">Limitations</a><br>
-&nbsp; &nbsp; &nbsp; 1.8 <a href="#introLBack">Looking Back</a><br><br>
-<b>2.</b> <a href="#optsettings"><b>Settings Details</b></a><br><br>
-&nbsp; &nbsp; &nbsp; 2.1 <a href="#topmenu"><b>Top Menu Bar</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.1.1 <a href="#file">File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.1.2 <a href="#help">Help</a><br>
-&nbsp; &nbsp; &nbsp; 2.2 <a href="#network"><b>Network</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.2.1 <a href="#proxy">Proxy</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.2.2 <a href="#ssl">SSL</a><br>
-&nbsp; &nbsp; &nbsp; 2.3 <a href="#general"><b>General</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.1 <a href="#genlog">Logfile</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.2 <a href="#genapp">Append Files</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.3 <a href="#genconf">Reread Configuration</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.4 <a href="#genstart">Auto Start</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.5 <a href="#rawout">Raw Output File</a><br>
-&nbsp; &nbsp; &nbsp; 2.4 <a href="#rinex"><b>RINEX Observations</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.1 <a href="#rnxname">Filenames</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.2 <a href="#rnxdir">Directory</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.3 <a href="#rnxinterval">File Interval</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.4 <a href="#rnxsample">Sampling</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.5 <a href="#rnxskl">Skeleton Extension</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.6 <a href="#sklMandat">Skeleton Mandatory</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.7 <a href="#sklDir">Skeleton Directory</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.8 <a href="#rnxscript">Script</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.9 <a href="#rnxvers3_4">Version 3 and 4</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.10 <a href="#rnxvers2">Version 2</a><br>
-&nbsp; &nbsp; &nbsp; 2.5 <a href="#ephemeris"><b>RINEX Ephemeris</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.1 <a href="#ephdir">Directory</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.2 <a href="#ephint">Interval</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.3 <a href="#ephport">Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.4 <a href="#ephvers">Version</a><br>
-&nbsp; &nbsp; &nbsp; 2.6 <a href="#reqc"><b>RINEX Editing & QC</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.1 <a href="#reqcact">Action</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.2 <a href="#reqcinp">Input Files</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.3 <a href="#reqcout">Output Files</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.4 <a href="#reqcminele">Minimum Elevation</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.5 <a href="#reqclog">Logfiles</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.6 <a href="#reqcplots">Plots for Signals</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.7 <a href="#reqcdir">Directory for Plots</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.8 <a href="#reqcedit">Set Edit Options</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.9 <a href="#reqccommand">Command Line, No Window</a><br>
-&nbsp; &nbsp; &nbsp; 2.7 <a href="#sp3comp"><b>SP3 Comparison</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.7.1 <a href="#sp3input">Input SP3 Files</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.7.2 <a href="#sp3exclude">Exclude Satellites</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.7.3 <a href="#sp3log">Logfile</a><br>
-&nbsp; &nbsp; &nbsp; 2.8 <a href="#correct"><b>Broadcast Corrections</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.1 <a href="#corrdir">Directory, ASCII</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.2 <a href="#corrint">Interval</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.3 <a href="#corrport">Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.4 <a href="#corrwait">Wait for Full Corr Epoch</a><br>
-&nbsp; &nbsp; &nbsp; 2.9 <a href="#syncout"><b>Feed Engine</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.1 <a href="#syncport">Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.2 <a href="#syncwait">Wait for Full Obs Epoch</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.3 <a href="#syncsample">Sampling</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.4 <a href="#syncfile">File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.5 <a href="#syncuport">Port (unsynchronized)</a><br>
-&nbsp; &nbsp; &nbsp; 2.10 <a href="#serial"><b>Serial Output</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.1 <a href="#sermount">Mountpoint</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.2 <a href="#serport">Port Name</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.3 <a href="#serbaud">Baud Rate</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.4 <a href="#serflow">Flow Control</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.5 <a href="#serparity">Parity</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.6 <a href="#serdata">Data Bits</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.7 <a href="#serstop">Stop Bits</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.8 <a href="#serauto">NMEA</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.9 <a href="#serfile">File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.10 <a href="#serheight">Height</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.11 <a href="#sersampl">Sampling</a><br>
-&nbsp; &nbsp; &nbsp; 2.11 <a href=#advnote><b>Outages</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.1. <a href=#obsrate>Observation Rate</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.2. <a href=#advfail>Failure Threshold</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.3. <a href=#advreco>Recovery Threshold</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.4. <a href=#advscript>Script</a><br>
-&nbsp; &nbsp; &nbsp; 2.12 <a href=#misc><b>Miscellaneous</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.1. <a href=#miscmount>Mountpoint</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.2. <a href=#miscperf>Log Latency</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.3. <a href=#miscscan>Scan RTCM</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.4. <a href=#miscport>Port</a><br>
-&nbsp; &nbsp; &nbsp; 2.13 <a href=#pppclient><b>PPP Client</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1 <a href=#pppInp><b>PPP (1): Input and Output</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.1  <a href=#pppdatasource>Data Source</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.2  <a href=#pppcorrstream>Corrections Stream</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.3  <a href=#pppcorrfile>Corrections File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.4  <a href=#pppbiasstream>Biases Stream</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.5  <a href=#pppbiasfile>Biases File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.6  <a href=#pppionostream>Ionosphere Stream</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.7  <a href=#pppionofile>Ionosphere File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.8  <a href=#ppprnxobs>RINEX Observation File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.9  <a href=#ppprnxnav>RINEX Navigation File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.10 <a href=#pppantexfile>ANTEX File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.11 <a href=#pppmarkcoor>Coordinates File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.12 <a href=#pppblqfile>BLQ File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.13 <a href=#ppplogfile>Logfile Directory and Log mode</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.14 <a href=#pppnmeafile>NMEA Directory</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15 <a href=#pppsnxtrofile>SNX TRO Directory</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.1 <a href=#pppsnxtrointr>Interval</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.2 <a href=#pppsnxtrosampl>Sampling</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.3 <a href=#pppsnxAc>Analysis Center</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.4 <a href=#pppsnxSol>Solution ID</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2 <a href=#pppOptions><b>PPP (2): Processing Options</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.1 <a href=#pppobs>GNSS Observations</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.2 <a href=#pppcodeobs>Code Observations</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.3 <a href=#pppphaseobs>Phase Observations</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.4 <a href=#pppeleweight>Elevation Dependent Weighting</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.5 <a href=#pppminobs>Minimum Number of Observations</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.6 <a href=#pppmineleva>Minimum Elevation</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.7 <a href=#pppwaitclockcorr>Wait for Clock Corrections</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.8 <a href=#pppseeding>Seeding</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.9 <a href=#pppconstraints>Constraints</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.9.0 <a href=#ppppseudogimobs>GIM Pseudo Observations - How it works</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.9.1 <a href=#ppppseudogimobssigma>GIM Pseudo Observations Sigma</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10 <a href=#pppar>PPP-AR</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.0 <a href=#ppparmethod>Algorithm Description</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.1 <a href=#ppparsys>Constellations</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.2 <a href=#ppparmin>Min # Epo and Sat</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.3 <a href=#ppparmax>Max Frac and Sig</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.4 <a href=#ppparyaw>Yaw Usage</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.5 <a href=#ppparfix>Per-epoch fix percentage</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3 <a href=#pppStation><b>PPP (3): Processed Stations</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.1 <a href=#pppsite>Station</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.2 <a href=#pppnehsigma>Sigma North/East/Up</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.3 <a href=#pppnehnoise>Noise North/East/Up</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.4 <a href=#ppptropsigma>Tropo Sigma</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.5 <a href=#ppptropnoise>Tropo Noise</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.6 <a href=#pppnmeaport>NMEA Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.6 <a href=#pppsignalpriorities>Signal Priorities</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4 <a href=#pppPlots><b>PPP (4): Plots</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.1 <a href=#ppptimeseries>PPP Plot</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.2 <a href=#pppaudioresp>Audio Response</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.3 <a href=#ppptrackmap>Track Map</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.4 <a href=#pppdotprop>Dot-properties</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.4.1 <a href=#pppdotsize>Size</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.4.2 <a href=#pppdotcolor>Color</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.5 <a href=#pppspeed>Post Processing Speed</a><br>
-&nbsp; &nbsp; &nbsp; 2.14 <a href=#combi><b>Combine Corrections</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1 <a href=#combimounttab>Combine Corrections Table</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.1 <a href=#combiadd>Add Row, Delete</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.2 <a href=#combimethod>Method</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.3 <a href=#combimaxres>Maximal Clock Residuum</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.4 <a href=#combimaxdisp>Maximal Orbit Displacement</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.5 <a href=#combismpl>Sampling</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.6 <a href=#combisatsys>Satellite Systems</a><br>
-&nbsp; &nbsp; &nbsp; 2.15 <a href=#upclk><b>Upload Corrections</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.1 <a href=#upadd>Add, Delete Row</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.2 <a href=#uphost>Host, Port, Mountpoint, Ntrip Version, User and Password </a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.3 <a href=#upsystem>System</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.4 <a href=#upformat>Format</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.5 <a href=#upcom>Center of Mass</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.6 <a href=#upsp3>SP3 File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.7 <a href=#uprinex>RNX File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.8 <a href=#upsinex>BSX File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.9 <a href=#pidsidiod>PID, SID, IOD</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.10 <a href=#upinter>Interval</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11 <a href=#upclksmpl>Sampling</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.1 <a href=#upclkorb>Orbits</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.2 <a href=#upclksp3>SP3</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.3 <a href=#upclkrnx>RINEX</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.4 <a href=#upbiassnx>SINEX</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.12 <a href=#upcustom>Custom Trafo</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.13 <a href=#upantex>ANTEX File</a><br>
-&nbsp; &nbsp; &nbsp; 2.16 <a href=#upeph><b>Upload Ephemeris</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.1 <a href=#brdcserver>Host &amp; Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.2 <a href=#brdcmount>Mountpoint, Ntrip Version, User, Password</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.3 <a href=#brdcsys>Satellite System </a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.4 <a href=#brdcsmpl>Sampling</a><br>
-&nbsp; &nbsp; &nbsp; 2.17 <a href=#upraw><b>Upload Raw Data - NtripServer Functionality</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.17.1 <a href=#rawsourcemount>Source Mountpoint</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.17.2 <a href=#rawserver>Host &amp; Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.17.3 <a href=#rawmount>Upload Mountpoint, Ntrip Version, User, Password</a><br>
-&nbsp; &nbsp; &nbsp; 2.18 <a href=#streams><b>Streams Canvas</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.18.1 <a href=#streamedit>Edit Streams</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.18.2 <a href=#streamdelete>Delete Stream</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.18.3 <a href=#streamconf>Reconfigure Stream Selection On-the-fly</a><br>
-&nbsp; &nbsp; &nbsp; 2.19 <a href=#logs><b>Logging Canvas</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.1 <a href=#logfile>Log</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.2 <a href=#throughput>Throughput</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.3 <a href=#latency>Latency</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.4 <a href=#ppptab>PPP Plot</a><br>
-&nbsp; &nbsp; &nbsp; 2.20 <a href=#bottom><b>Bottom Menu Bar</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1 <a href=#streamadd>Add Stream</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1 <a href=#streamcaster>Add Stream - Coming from Caster</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.1 <a href=#streamhost>Caster Host and Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.2 <a href=#streamtable>Casters Table</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.3 <a href=#streamuser>User and Password</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.4 <a href=#gettable>Get Table</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.5 <a href=#ntripv>Ntrip Version</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.6 <a href=#castermap>Map</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.2 <a href=#streamip>Add Stream - Coming from TCP/IP Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.3 <a href=#streamudp>Add Stream - Coming from UDP Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.4 <a href=#streamser>Add Stream - Coming from Serial Port</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.2 <a href=#streamsdelete>Delete Stream</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.3 <a href=#streamsmap>Map</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.4 <a href=#start>Start</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.5 <a href=#stop>Stop</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.6 <a href=#contexthelp>Help? = Shift+F1</a><br>
-&nbsp; &nbsp; &nbsp; 2.21 <a href=#cmd><b>Command Line Options</b></a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.1 <a href=#cmdVersion>Version</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.2 <a href=#cmdDisplay>Display</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.3 <a href=#nw>No Window Mode</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.4 <a href=#post>File Mode</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.5 <a href=#conffile>Configuration File</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.6 <a href=#confopt>Configuration Options</a><br><br>
-<b>3.</b> <a href=#annex><b>Annex</b></a><br><br>
-&nbsp; &nbsp; &nbsp; 3.1 <a href=#rtcm>RTCM Standards</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.1 <a href=#ntrip1>Ntrip Version 1</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.2 <a href=#ntrip2>Ntrip Version 2</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.3 <a href=#rtcm2>RTCM Version 2</a><br>
-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.4 <a href=#rtcm3>RTCM Version 3</a><br>
-&nbsp; &nbsp; &nbsp; 3.2 <a href=#confList>Command Line Help</a><br>
-&nbsp; &nbsp; &nbsp; 3.3 <a href=#links>Further Reading</a><br>
-&nbsp; &nbsp; &nbsp; 3.4 <a href=#abbrev>Abbreviations</a>
-</p>
-<br>
-
-<p>
-<b>List of Figures</b><br>
-<table>
-  <tr><td><b>Fig.&nbsp;&nbsp;</b></td><td><b>Title</b></td><td><b>Chapter</b></td></tr>
-  <tr><td>1</td><td>Flowchart, BNC connected to a GNSS rover for Precise Point Positioning</td><td>1.3</td></tr>
-  <tr><td>2</td><td>Flowchart, BNC converting RTCM streams to RINEX batches</td><td>1.3</td></tr>
-  <tr><td>3</td><td>Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections</td><td>1.3</td></tr>
-  <tr><td>4</td><td>Flowchart, BNC combining Broadcast Correction streams</td><td>1.3</td></tr>
-  <tr><td>5</td><td>Sections on BNC's main window</td><td>1.4</td></tr>
-  <tr><td>6</td><td>Management of configuration options in BNC</td><td>1.6</td></tr>
-  <tr><td>7</td><td>BNC's 'Network' panel configured to ignore eventually occurring SSL error messages</td><td>2.2.2</td></tr>
-  <tr><td>8</td><td>BNC translating incoming RTCM Version 3 Observation streams to 15 min RINEX Version 4 Observation files</td><td>2.4</td></tr>
-  <tr><td>9</td><td>Example for creating RINEX quality check analysis graphics output with BNC</td><td>2.6.6</td></tr>
-  <tr><td>10</td><td>Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC</td><td>2.6.6</td></tr>
-  <tr><td>11</td><td>Sky plot examples for multipath, part of RINEX quality check analysis with BNC</td><td>2.6.6</td></tr>
-  <tr><td>12</td><td>Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC</td><td>2.6.6</td></tr>
-  <tr><td>13</td><td>Example for BNC's 'RINEX Editing Options' window</td><td>2.6.8</td></tr>
-  <tr><td>14</td><td>Example for RINEX file concatenation with BNC</td><td>2.6.8</td></tr>
-  <tr><td>15</td><td>Example for comparing two SP3 files with satellite orbit and clock data using BNC</td><td>2.7</td></tr>
-  <tr><td>16</td><td>Graphical results from an example comparison of two SP3 files with satellite orbit and clock data using BNC</td><td>2.7.3</td></tr>
-  <tr><td>17</td><td>Example for pulling, saving and output of Broadcast Corrections using BNC</td><td>2.8.3</td></tr>
-  <tr><td>18</td><td>Synchronized BNC output via IP port to feed a GNSS real-time engine</td><td>2.9</td></tr>
-  <tr><td>19</td><td>Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is mandatory for VRS streams</td><td>2.10</td></tr>
-  <tr><td>20</td><td>BNC pulling a RTCM Version 3 stream to feed a serial connected receiver with observations from a nearby reference station for conventional RTK</td><td>2.10</td></tr>
-  <tr><td>21</td><td>RTCM message numbers, latencies and observation types logged by BNC</td><td>2.12</td></tr>
-  <tr><td>22</td><td>Real-time Precise Point Positioning with BNC, PPP Panel 1</td><td>2.13.1</td></tr>
-  <tr><td>23</td><td>Precise Point Positioning with BNC, PPP Panel 2</td><td>2.13.2</td></tr>
-  <tr><td>25</td><td>Precise Point Positioning with BNC, PPP Panel 3</td><td>2.13.3</td></tr>
-  <tr><td>26</td><td>Precise Point Positioning with BNC with track of positions using OpenStreetMap, PPP Panel 4</td><td>2.13.4.3</td></tr>
-  <tr><td>27</td><td>BNC combining Broadcast Correction streams</td><td>2.14</td></tr>
-  <tr><td>28</td><td>'INTERNAL' PPP with BNC using a combination of Broadcast Corrections</td><td>2.14</td></tr>
-  <tr><td>29</td><td>BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster</td><td>2.15</td></tr>
-  <tr><td>30</td><td>Setting BNC's Custom Transformation Parameters window</td><td>2.15.3</td></tr>
-  <tr><td>31</td><td>BNC uploading a combined Broadcast Correction stream</td><td>2.15.12</td></tr>
-  <tr><td>32</td><td>BNC producing Broadcast Ephemeris streams from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster</td><td>2.16.3</td></tr>
-  <tr><td>33</td><td>Bandwidth consumption of RTCM streams received by BNC</td><td>2.18.2</td></tr>
-  <tr><td>34</td><td>Latency of RTCM streams received by BNC</td><td>2.18.3</td></tr>
-  <tr><td>35</td><td>Example for time series plot of displacements produced by BNC</td><td>2.18.4</td></tr>
-  <tr><td>36</td><td>Steam input communication links accepted by BNC</td><td>2.19</td></tr>
-  <tr><td>37</td><td>BNC's 'Select Broadcaster' table</td><td>2.19.1.1.2</td></tr>
-  <tr><td>38</td><td>Broadcaster source-table shown by BNC</td><td>2.19.1.1.4</td></tr>
-  <tr><td>39</td><td>Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table</td><td>2.19.1.1.6</td></tr>
-  <tr><td>40</td><td>BNC configuration for pulling a stream via serial port</td><td>2.19.1.4</td></tr>
-</table>
-</p>
-<br>
-
-<p><b>List of Tables</b><br><br>
-<table>
-  <tr><td><b>Tab.&nbsp;&nbsp;</b></td><td><b>Title</b></td><td><b>Chapter</b></td></tr>
-  <tr><td>1</td><td>Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</td><td>1.2</td></tr>
-  <tr><td>2</td><td>Contents and format of synchronized output of observations feeding a GNSS engine</td><td>2.9</td></tr>
-</table>
-</p>
-
-<h3 id="genInstruction">1. General Information</h3>
-<p>
-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
-<ul>
-  <li><a href="http://euref-ip.net/home" target="_blank">http://euref-ip.net/home</a></li>
-  <li><a href="http://igs-ip.net/home" target="_blank">http://igs-ip.net/home</a></li>
-  <li><a href="http://products.igs-ip.net/home" target="_blank">http://products.igs-ip.net/home</a></li>
-</ul>
-or similar caster installation.
-</p>
-
-<p>
-<b>Documentation</b><br><br>
-BNC provides context-sensitive help (<i>What's This</i>) related to specific objects.
-Furthermore, it comes with severl example configurations. The here presented documentation
-is available as part of the software, as a PDF file and can be find as well as an online documentation:
-<a href="http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/src/bnchelp.html"
-target="_blank">http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/src/bnchelp.html</a>.
-</p>
-
-<p>
-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.
-</p>
-
-<p>
-<b>Acknowledgements</b><br>
-<ul>
-  <li>Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany published a RTCM Version 2 decoder
+  </p>
+  <br>
+
+  <h4>Table of Contents</h4>
+  <p>
+    <b>1.</b> <a href="#genInstruction"><b>General Information</b></a><br><br>
+    &nbsp; &nbsp; &nbsp; 1.1 <a href="#introPurpose">Purpose</a><br>
+    &nbsp; &nbsp; &nbsp; 1.2 <a href="#introSystem">Supported GNSS</a><br>
+    &nbsp; &nbsp; &nbsp; 1.3 <a href="#introFlow">Data Flow</a><br>
+    &nbsp; &nbsp; &nbsp; 1.4 <a href="#introHandling">Handling</a><br>
+    &nbsp; &nbsp; &nbsp; 1.5 <a href="#introInst">Installation</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1.5.1 <a href="#introCompile">Compilation</a><br>
+    &nbsp; &nbsp; &nbsp; 1.6 <a href="#introConf">Configuration</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1.6.1 <a href="#introExamples">Examples</a><br>
+    &nbsp; &nbsp; &nbsp; 1.7 <a href="#introLimit">Limitations</a><br>
+    &nbsp; &nbsp; &nbsp; 1.8 <a href="#introLBack">Looking Back</a><br><br>
+    <b>2.</b> <a href="#optsettings"><b>Settings Details</b></a><br><br>
+    &nbsp; &nbsp; &nbsp; 2.1 <a href="#topmenu"><b>Top Menu Bar</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.1.1 <a href="#file">File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.1.2 <a href="#help">Help</a><br>
+    &nbsp; &nbsp; &nbsp; 2.2 <a href="#network"><b>Network</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.2.1 <a href="#proxy">Proxy</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.2.2 <a href="#ssl">SSL</a><br>
+    &nbsp; &nbsp; &nbsp; 2.3 <a href="#general"><b>General</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.1 <a href="#genlog">Logfile</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.2 <a href="#genapp">Append Files</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.3 <a href="#genconf">Reread Configuration</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.4 <a href="#genstart">Auto Start</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.3.5 <a href="#rawout">Raw Output File</a><br>
+    &nbsp; &nbsp; &nbsp; 2.4 <a href="#rinex"><b>RINEX Observations</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.1 <a href="#rnxname">Filenames</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.2 <a href="#rnxdir">Directory</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.3 <a href="#rnxinterval">File Interval</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.4 <a href="#rnxsample">Sampling</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.5 <a href="#rnxskl">Skeleton Extension</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.6 <a href="#sklMandat">Skeleton Mandatory</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.7 <a href="#sklDir">Skeleton Directory</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.8 <a href="#rnxscript">Script</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.9 <a href="#rnxvers3_4">Version 3 and 4</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4.10 <a href="#rnxvers2">Version 2</a><br>
+    &nbsp; &nbsp; &nbsp; 2.5 <a href="#ephemeris"><b>RINEX Ephemeris</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.1 <a href="#ephdir">Directory</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.2 <a href="#ephint">Interval</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.3 <a href="#ephport">Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.5.4 <a href="#ephvers">Version</a><br>
+    &nbsp; &nbsp; &nbsp; 2.6 <a href="#reqc"><b>RINEX Editing & QC</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.1 <a href="#reqcact">Action</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.2 <a href="#reqcinp">Input Files</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.3 <a href="#reqcout">Output Files</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.4 <a href="#reqcminele">Minimum Elevation</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.5 <a href="#reqclog">Logfiles</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.6 <a href="#reqcplots">Plots for Signals</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.7 <a href="#reqcdir">Directory for Plots</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.8 <a href="#reqcedit">Set Edit Options</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.6.9 <a href="#reqccommand">Command Line, No Window</a><br>
+    &nbsp; &nbsp; &nbsp; 2.7 <a href="#sp3comp"><b>SP3 Comparison</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.7.1 <a href="#sp3input">Input SP3 Files</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.7.2 <a href="#sp3exclude">Exclude Satellites</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.7.3 <a href="#sp3log">Logfile</a><br>
+    &nbsp; &nbsp; &nbsp; 2.8 <a href="#correct"><b>Broadcast Corrections</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.1 <a href="#corrdir">Directory, ASCII</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.2 <a href="#corrint">Interval</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.3 <a href="#corrport">Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.8.4 <a href="#corrwait">Wait for Full Corr Epoch</a><br>
+    &nbsp; &nbsp; &nbsp; 2.9 <a href="#syncout"><b>Feed Engine</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.1 <a href="#syncport">Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.2 <a href="#syncwait">Wait for Full Obs Epoch</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.3 <a href="#syncsample">Sampling</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.4 <a href="#syncfile">File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.9.5 <a href="#syncuport">Port (unsynchronized)</a><br>
+    &nbsp; &nbsp; &nbsp; 2.10 <a href="#serial"><b>Serial Output</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.1 <a href="#sermount">Mountpoint</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.2 <a href="#serport">Port Name</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.3 <a href="#serbaud">Baud Rate</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.4 <a href="#serflow">Flow Control</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.5 <a href="#serparity">Parity</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.6 <a href="#serdata">Data Bits</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.7 <a href="#serstop">Stop Bits</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.8 <a href="#serauto">NMEA</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.9 <a href="#serfile">File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.10 <a href="#serheight">Height</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.10.11 <a href="#sersampl">Sampling</a><br>
+    &nbsp; &nbsp; &nbsp; 2.11 <a href=#advnote><b>Outages</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.1. <a href=#obsrate>Observation Rate</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.2. <a href=#advfail>Failure Threshold</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.3. <a href=#advreco>Recovery Threshold</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.11.4. <a href=#advscript>Script</a><br>
+    &nbsp; &nbsp; &nbsp; 2.12 <a href=#misc><b>Miscellaneous</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.1. <a href=#miscmount>Mountpoint</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.2. <a href=#miscperf>Log Latency</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.3. <a href=#miscscan>Scan RTCM</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.12.4. <a href=#miscport>Port</a><br>
+    &nbsp; &nbsp; &nbsp; 2.13 <a href=#pppclient><b>PPP Client</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1 <a href=#pppInp><b>PPP (1): Input and Output</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.1 <a href=#pppdatasource>Data Source</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.2 <a href=#pppcorrstream>Corrections
+      Stream</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.3 <a href=#pppcorrfile>Corrections
+      File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.4 <a href=#pppbiasstream>Biases Stream</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.5 <a href=#pppbiasfile>Biases File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.6 <a href=#pppionostream>Ionosphere
+      Stream</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.7 <a href=#pppionofile>Ionosphere File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.8 <a href=#ppprnxobs>RINEX Observation
+      File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.9 <a href=#ppprnxnav>RINEX Navigation
+      File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.10 <a href=#pppantexfile>ANTEX File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.11 <a href=#pppmarkcoor>Coordinates
+      File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.12 <a href=#pppblqfile>BLQ File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.13 <a href=#ppplogfile>Logfile Directory and
+      Log mode</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.14 <a href=#pppnmeafile>NMEA Directory</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15 <a href=#pppsnxtrofile>SNX TRO
+      Directory</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.1 <a
+      href=#pppsnxtrointr>Interval</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.2 <a
+      href=#pppsnxtrosampl>Sampling</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.3 <a href=#pppsnxAc>Analysis
+      Center</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.1.15.4 <a href=#pppsnxSol>Solution
+      ID</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2 <a href=#pppOptions><b>PPP (2): Processing Options</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.1 <a href=#pppobs>GNSS Observations</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.2 <a href=#pppcodeobs>Code
+      Observations</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.3 <a href=#pppphaseobs>Phase
+      Observations</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.4 <a href=#pppeleweight>Elevation Dependent
+      Weighting</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.5 <a href=#pppminobs>Minimum Number of
+      Observations</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.6 <a href=#pppmineleva>Minimum
+      Elevation</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.7 <a href=#pppwaitclockcorr>Wait for Clock
+      Corrections</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.8 <a href=#pppseeding>Seeding</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.9 <a href=#pppconstraints>Constraints</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.9.0 <a href=#ppppseudogimobs>GIM Pseudo
+      Observations - How it works</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.9.1 <a href=#ppppseudogimobssigma>GIM Pseudo
+      Observations Sigma</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10 <a href=#pppar>PPP-AR</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.0 <a href=#ppparmethod>Algorithm
+      Description</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.1 <a href=#ppparsys>Constellations</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.2 <a href=#ppparmin>Min # Epo and
+      Sat</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.3 <a href=#ppparmax>Max Frac and
+      Sig</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.4 <a href=#ppparyaw>Yaw Usage</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.2.10.5 <a href=#ppparfix>Per-epoch fix
+      percentage</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3 <a href=#pppStation><b>PPP (3): Processed Stations</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.1 <a href=#pppsite>Station</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.2 <a href=#pppnehsigma>Sigma
+      North/East/Up</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.3 <a href=#pppnehnoise>Noise
+      North/East/Up</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.4 <a href=#ppptropsigma>Tropo Sigma</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.5 <a href=#ppptropnoise>Tropo Noise</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.6 <a href=#pppnmeaport>NMEA Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.3.6 <a href=#pppsignalpriorities>Signal
+      Priorities</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4 <a href=#pppPlots><b>PPP (4): Plots</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.1 <a href=#ppptimeseries>PPP Plot</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.2 <a href=#pppaudioresp>Audio Response</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.3 <a href=#ppptrackmap>Track Map</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.4 <a href=#pppdotprop>Dot-properties</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.4.1 <a
+      href=#pppdotsize>Size</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.4.2 <a
+      href=#pppdotcolor>Color</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.13.4.5 <a href=#pppspeed>Post Processing
+      Speed</a><br>
+    &nbsp; &nbsp; &nbsp; 2.14 <a href=#combi><b>Combine Corrections</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1 <a href=#combimounttab>Combine Corrections Table</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.1 <a href=#combiadd>Add Row, Delete</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.2 <a href=#combimethod>Method</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.3 <a href=#combimaxres>Maximal Clock
+      Residuum</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.4 <a href=#combimaxdisp>Maximal Orbit
+      Displacement</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.5 <a href=#combismpl>Sampling</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.14.1.6 <a href=#combisatsys>Satellite
+      Systems</a><br>
+    &nbsp; &nbsp; &nbsp; 2.15 <a href=#upclk><b>Upload Corrections</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.1 <a href=#upadd>Add, Delete Row</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.2 <a href=#uphost>Host, Port, Mountpoint, Ntrip Version, User and
+      Password </a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.3 <a href=#upsystem>System</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.4 <a href=#upformat>Format</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.5 <a href=#upcom>Center of Mass</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.6 <a href=#upsp3>SP3 File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.7 <a href=#uprinex>RNX File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.8 <a href=#upsinex>BSX File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.9 <a href=#pidsidiod>PID, SID, IOD</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.10 <a href=#upinter>Interval</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11 <a href=#upclksmpl>Sampling</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.1 <a href=#upclkorb>Orbits</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.2 <a href=#upclksp3>SP3</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.3 <a href=#upclkrnx>RINEX</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.11.4 <a href=#upbiassnx>SINEX</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.12 <a href=#upcustom>Custom Trafo</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.15.13 <a href=#upantex>ANTEX File</a><br>
+    &nbsp; &nbsp; &nbsp; 2.16 <a href=#upeph><b>Upload Ephemeris</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.1 <a href=#brdcserver>Host &amp; Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.2 <a href=#brdcmount>Mountpoint, Ntrip Version, User,
+      Password</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.3 <a href=#brdcsys>Satellite System </a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.16.4 <a href=#brdcsmpl>Sampling</a><br>
+    &nbsp; &nbsp; &nbsp; 2.17 <a href=#upraw><b>Upload Raw Data - NtripServer Functionality</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.17.1 <a href=#rawsourcemount>Source Mountpoint</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.17.2 <a href=#rawserver>Host &amp; Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.17.3 <a href=#rawmount>Upload Mountpoint, Ntrip Version, User,
+      Password</a><br>
+    &nbsp; &nbsp; &nbsp; 2.18 <a href=#streams><b>Streams Canvas</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.18.1 <a href=#streamedit>Edit Streams</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.18.2 <a href=#streamdelete>Delete Stream</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.18.3 <a href=#streamconf>Reconfigure Stream Selection On-the-fly</a><br>
+    &nbsp; &nbsp; &nbsp; 2.19 <a href=#logs><b>Logging Canvas</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.1 <a href=#logfile>Log</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.2 <a href=#throughput>Throughput</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.3 <a href=#latency>Latency</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.19.4 <a href=#ppptab>PPP Plot</a><br>
+    &nbsp; &nbsp; &nbsp; 2.20 <a href=#bottom><b>Bottom Menu Bar</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1 <a href=#streamadd>Add Stream</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1 <a href=#streamcaster>Add Stream - Coming
+      from Caster</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.1 <a
+      href=#streamhost>Caster Host and Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.2 <a
+      href=#streamtable>Casters Table</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.3 <a
+      href=#streamuser>User and Password</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.4 <a href=#gettable>Get
+      Table</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.5 <a href=#ntripv>Ntrip
+      Version</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.1.6 <a
+      href=#castermap>Map</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.2 <a href=#streamip>Add Stream - Coming from
+      TCP/IP Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.3 <a href=#streamudp>Add Stream - Coming from
+      UDP Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.1.4 <a href=#streamser>Add Stream - Coming from
+      Serial Port</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.2 <a href=#streamsdelete>Delete Stream</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.3 <a href=#streamsmap>Map</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.4 <a href=#start>Start</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.5 <a href=#stop>Stop</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.6 <a href=#contexthelp>Help? = Shift+F1</a><br>
+    &nbsp; &nbsp; &nbsp; 2.21 <a href=#cmd><b>Command Line Options</b></a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.1 <a href=#cmdVersion>Version</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.2 <a href=#cmdDisplay>Display</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.3 <a href=#nw>No Window Mode</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.4 <a href=#post>File Mode</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.5 <a href=#conffile>Configuration File</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.21.6 <a href=#confopt>Configuration Options</a><br><br>
+    <b>3.</b> <a href=#annex><b>Annex</b></a><br><br>
+    &nbsp; &nbsp; &nbsp; 3.1 <a href=#rtcm>RTCM Standards</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.1 <a href=#ntrip1>Ntrip Version 1</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.2 <a href=#ntrip2>Ntrip Version 2</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.3 <a href=#rtcm2>RTCM Version 2</a><br>
+    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.4 <a href=#rtcm3>RTCM Version 3</a><br>
+    &nbsp; &nbsp; &nbsp; 3.2 <a href=#confList>Command Line Help</a><br>
+    &nbsp; &nbsp; &nbsp; 3.3 <a href=#links>Further Reading</a><br>
+    &nbsp; &nbsp; &nbsp; 3.4 <a href=#abbrev>Abbreviations</a>
+  </p>
+  <br>
+
+  <p>
+    <b>List of Figures</b><br>
+  <table>
+    <tr>
+      <td><b>Fig.&nbsp;&nbsp;</b></td>
+      <td><b>Title</b></td>
+      <td><b>Chapter</b></td>
+    </tr>
+    <tr>
+      <td>1</td>
+      <td>Flowchart, BNC connected to a GNSS rover for Precise Point Positioning</td>
+      <td>1.3</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>Flowchart, BNC converting RTCM streams to RINEX batches</td>
+      <td>1.3</td>
+    </tr>
+    <tr>
+      <td>3</td>
+      <td>Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections</td>
+      <td>1.3</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>Flowchart, BNC combining Broadcast Correction streams</td>
+      <td>1.3</td>
+    </tr>
+    <tr>
+      <td>5</td>
+      <td>Sections on BNC's main window</td>
+      <td>1.4</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>Management of configuration options in BNC</td>
+      <td>1.6</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>BNC's 'Network' panel configured to ignore eventually occurring SSL error messages</td>
+      <td>2.2.2</td>
+    </tr>
+    <tr>
+      <td>8</td>
+      <td>BNC translating incoming RTCM Version 3 Observation streams to 15 min RINEX Version 4 Observation files</td>
+      <td>2.4</td>
+    </tr>
+    <tr>
+      <td>9</td>
+      <td>Example for creating RINEX quality check analysis graphics output with BNC</td>
+      <td>2.6.6</td>
+    </tr>
+    <tr>
+      <td>10</td>
+      <td>Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis
+        with BNC</td>
+      <td>2.6.6</td>
+    </tr>
+    <tr>
+      <td>11</td>
+      <td>Sky plot examples for multipath, part of RINEX quality check analysis with BNC</td>
+      <td>2.6.6</td>
+    </tr>
+    <tr>
+      <td>12</td>
+      <td>Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC</td>
+      <td>2.6.6</td>
+    </tr>
+    <tr>
+      <td>13</td>
+      <td>Example for BNC's 'RINEX Editing Options' window</td>
+      <td>2.6.8</td>
+    </tr>
+    <tr>
+      <td>14</td>
+      <td>Example for RINEX file concatenation with BNC</td>
+      <td>2.6.8</td>
+    </tr>
+    <tr>
+      <td>15</td>
+      <td>Example for comparing two SP3 files with satellite orbit and clock data using BNC</td>
+      <td>2.7</td>
+    </tr>
+    <tr>
+      <td>16</td>
+      <td>Graphical results from an example comparison of two SP3 files with satellite orbit and clock data using BNC
+      </td>
+      <td>2.7.3</td>
+    </tr>
+    <tr>
+      <td>17</td>
+      <td>Example for pulling, saving and output of Broadcast Corrections using BNC</td>
+      <td>2.8.3</td>
+    </tr>
+    <tr>
+      <td>18</td>
+      <td>Synchronized BNC output via IP port to feed a GNSS real-time engine</td>
+      <td>2.9</td>
+    </tr>
+    <tr>
+      <td>19</td>
+      <td>Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is mandatory for
+        VRS streams</td>
+      <td>2.10</td>
+    </tr>
+    <tr>
+      <td>20</td>
+      <td>BNC pulling a RTCM Version 3 stream to feed a serial connected receiver with observations from a nearby
+        reference station for conventional RTK</td>
+      <td>2.10</td>
+    </tr>
+    <tr>
+      <td>21</td>
+      <td>RTCM message numbers, latencies and observation types logged by BNC</td>
+      <td>2.12</td>
+    </tr>
+    <tr>
+      <td>22</td>
+      <td>Real-time Precise Point Positioning with BNC, PPP Panel 1</td>
+      <td>2.13.1</td>
+    </tr>
+    <tr>
+      <td>23</td>
+      <td>Precise Point Positioning with BNC, PPP Panel 2</td>
+      <td>2.13.2</td>
+    </tr>
+    <tr>
+      <td>25</td>
+      <td>Precise Point Positioning with BNC, PPP Panel 3</td>
+      <td>2.13.3</td>
+    </tr>
+    <tr>
+      <td>26</td>
+      <td>Precise Point Positioning with BNC with track of positions using OpenStreetMap, PPP Panel 4</td>
+      <td>2.13.4.3</td>
+    </tr>
+    <tr>
+      <td>27</td>
+      <td>BNC combining Broadcast Correction streams</td>
+      <td>2.14</td>
+    </tr>
+    <tr>
+      <td>28</td>
+      <td>'INTERNAL' PPP with BNC using a combination of Broadcast Corrections</td>
+      <td>2.14</td>
+    </tr>
+    <tr>
+      <td>29</td>
+      <td>BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip
+        Broadcaster</td>
+      <td>2.15</td>
+    </tr>
+    <tr>
+      <td>30</td>
+      <td>Setting BNC's Custom Transformation Parameters window</td>
+      <td>2.15.3</td>
+    </tr>
+    <tr>
+      <td>31</td>
+      <td>BNC uploading a combined Broadcast Correction stream</td>
+      <td>2.15.12</td>
+    </tr>
+    <tr>
+      <td>32</td>
+      <td>BNC producing Broadcast Ephemeris streams from globally distributed RTCM streams; upload in RTCM format to an
+        Ntrip Broadcaster</td>
+      <td>2.16.3</td>
+    </tr>
+    <tr>
+      <td>33</td>
+      <td>Bandwidth consumption of RTCM streams received by BNC</td>
+      <td>2.18.2</td>
+    </tr>
+    <tr>
+      <td>34</td>
+      <td>Latency of RTCM streams received by BNC</td>
+      <td>2.18.3</td>
+    </tr>
+    <tr>
+      <td>35</td>
+      <td>Example for time series plot of displacements produced by BNC</td>
+      <td>2.18.4</td>
+    </tr>
+    <tr>
+      <td>36</td>
+      <td>Steam input communication links accepted by BNC</td>
+      <td>2.19</td>
+    </tr>
+    <tr>
+      <td>37</td>
+      <td>BNC's 'Select Broadcaster' table</td>
+      <td>2.19.1.1.2</td>
+    </tr>
+    <tr>
+      <td>38</td>
+      <td>Broadcaster source-table shown by BNC</td>
+      <td>2.19.1.1.4</td>
+    </tr>
+    <tr>
+      <td>39</td>
+      <td>Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table</td>
+      <td>2.19.1.1.6</td>
+    </tr>
+    <tr>
+      <td>40</td>
+      <td>BNC configuration for pulling a stream via serial port</td>
+      <td>2.19.1.4</td>
+    </tr>
+  </table>
+  </p>
+  <br>
+
+  <p><b>List of Tables</b><br><br>
+  <table>
+    <tr>
+      <td><b>Tab.&nbsp;&nbsp;</b></td>
+      <td><b>Title</b></td>
+      <td><b>Chapter</b></td>
+    </tr>
+    <tr>
+      <td>1</td>
+      <td>Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</td>
+      <td>1.2</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>Contents and format of synchronized output of observations feeding a GNSS engine</td>
+      <td>2.9</td>
+    </tr>
+  </table>
+  </p>
+
+  <h3 id="genInstruction">1. General Information</h3>
+  <p>
+    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
+  <ul>
+    <li><a href="http://euref-ip.net/home" target="_blank">http://euref-ip.net/home</a></li>
+    <li><a href="http://igs-ip.net/home" target="_blank">http://igs-ip.net/home</a></li>
+    <li><a href="http://products.igs-ip.net/home" target="_blank">http://products.igs-ip.net/home</a></li>
+  </ul>
+  or similar caster installation.
+  </p>
+
+  <p>
+    <b>Documentation</b><br><br>
+    BNC provides context-sensitive help (<i>What's This</i>) related to specific objects.
+    Furthermore, it comes with severl example configurations. The here presented documentation
+    is available as part of the software, as a PDF file and can be find as well as an online documentation:
+    <a href="http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/src/bnchelp.html"
+      target="_blank">http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/src/bnchelp.html</a>.
+  </p>
+
+  <p>
+    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.
+  </p>
+
+  <p>
+    <b>Acknowledgements</b><br>
+  <ul>
+    <li>Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany published a RTCM Version 2
+      decoder
       unter GNU GPL which has been integrated in BNC.</li>
-  <li>Andre Hauschild, German Space Operations Center, DLR, revised the RTCM Version 2 decoder and has provided a lot of hints
+    <li>Andre Hauschild, German Space Operations Center, DLR, revised the RTCM Version 2 decoder and has provided a lot
+      of hints
       regarding bugs and new features.</li>
-  <li>Zdenek Lukes, Czech Technical University Prague, Department of Geodesy, extended the RTCM Version 2 decoder to handle
+    <li>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.</li>
-  <li>Lennard Huisman, Kadaster Netherlands, and Rolf Dach, Astronomical Institute University of Bern, assisted in handling
+    <li>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.</li>
-  <li>Denis Laurichesse, Centre National d'Etudes Spatiales (CNES), suggested synchronizing observations and clock
+    <li>Denis Laurichesse, Centre National d'Etudes Spatiales (CNES), suggested synchronizing observations and clock
       corrections to reduce high frequency noise in PPP solutions.</li>
-  <li>Alexis Blot, Centre National d'Etudes Spatiales (CNES), has provided a lot of hints regarding bugs and new features.
-      Furthermore he has helped in the interoperability tests of RTCM-SSR and IGS-SSR format as well as the therefore used RTNET Interface.</li>
-  <li>Loukis Agrotis, Symban Ltd, has provided a lot of hints regarding bugs and new features.</li>
-  <li>Erwin Wiesensarter, Federal Agency for Cartography and Geodesy (BKG), provides actual builds of BNC for several Linux operating
+    <li>Alexis Blot, Centre National d'Etudes Spatiales (CNES), has provided a lot of hints regarding bugs and new
+      features.
+      Furthermore he has helped in the interoperability tests of RTCM-SSR and IGS-SSR format as well as the therefore
+      used RTNET Interface.</li>
+    <li>Loukis Agrotis, Symban Ltd, has provided a lot of hints regarding bugs and new features.</li>
+    <li>Erwin Wiesensarter, Federal Agency for Cartography and Geodesy (BKG), provides actual builds of BNC for several
+      Linux operating
       systems as well as for Mac OS X systems. Furthermore, he has provided some helpful scripts available under
-      <a href="https://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/scripts"target="_blank">http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/scripts</a>.</li>
-  <li>Peter Neumaier, Federal Agency for Cartography and Geodesy (BKG), provide the Windows MSI File and helps a lot
+      <a href="https://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/scripts"
+        target="_blank">http://software.rtcm-ntrip.org/export/HEAD/ntrip/trunk/BNC/scripts</a>.
+    </li>
+    <li>Peter Neumaier, Federal Agency for Cartography and Geodesy (BKG), provide the Windows MSI File and helps a lot
       regarding testing and user support.</li>
-</ul>
-</p>
-
-<h4 id="introPurpose">1.1 Purpose</h4>
-
-<p>
-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.
-</p>
-
-<p> BNC was designed to serve the following purposes:
-<ul>
-  <li>Retrieve real-time GNSS data streams available through the Ntrip transport protocol</li>
-  <li>Retrieve real-time GNSS data streams via TCP directly from an IP address without using the Ntrip transport protocol</li>
-  <li>Retrieve real-time GNSS data streams from a local UDP or serial port without using the Ntrip transport protocol</li>
-  <li>Plot stream distribution map from Ntrip Broadcaster source-tables</li>
-  <li>Generate RINEX Observation and Navigation files to support near real-time GNSS post processing applications</li>
-  <li>Edit or concatenate RINEX files or carry out RINEX Quality Checks (QC)</li>
-  <li>Handle RINEX Versions 2, 3 and 4 Observation and Navigation files</li>
-  <li>Compare SP3 files containing satellite orbit and clock data</li>
-  <li>Generate State Space Represenation (SSR) messages through an IP port to</li>
+  </ul>
+  </p>
+
+  <h4 id="introPurpose">1.1 Purpose</h4>
+
+  <p>
+    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.
+  </p>
+
+  <p> BNC was designed to serve the following purposes:
+  <ul>
+    <li>Retrieve real-time GNSS data streams available through the Ntrip transport protocol</li>
+    <li>Retrieve real-time GNSS data streams via TCP directly from an IP address without using the Ntrip transport
+      protocol</li>
+    <li>Retrieve real-time GNSS data streams from a local UDP or serial port without using the Ntrip transport protocol
+    </li>
+    <li>Plot stream distribution map from Ntrip Broadcaster source-tables</li>
+    <li>Generate RINEX Observation and Navigation files to support near real-time GNSS post processing applications</li>
+    <li>Edit or concatenate RINEX files or carry out RINEX Quality Checks (QC)</li>
+    <li>Handle RINEX Versions 2, 3 and 4 Observation and Navigation files</li>
+    <li>Compare SP3 files containing satellite orbit and clock data</li>
+    <li>Generate State Space Represenation (SSR) messages through an IP port to</li>
     <ul>
-       <li>support real-time Precise Point Positioning on GNSS rovers</li>
-       <li>support the (outside) combination of such streams as coming simultaneously from various correction providers</li>
+      <li>support real-time Precise Point Positioning on GNSS rovers</li>
+      <li>support the (outside) combination of such streams as coming simultaneously from various correction providers
+      </li>
     </ul>
-  <li>Generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port
+    <li>Generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port
       to support real-time GNSS network engines</li>
-  <li>Feed a stream into a GNSS receiver via serial communication link</li>
-  <li>Monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of outages or corrupted streams</li>
-  <li>Scan RTCM streams for incoming antenna information, observation types, message types and repetition rates and latencies
+    <li>Feed a stream into a GNSS receiver via serial communication link</li>
+    <li>Monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of
+      outages or corrupted streams</li>
+    <li>Scan RTCM streams for incoming antenna information, observation types, message types and repetition rates and
+      latencies
       and GLONASS slot numbers and frequency channels</li>
-  <li>Carry out real-time Precise Point Positioning to determine GNSS rover positions</li>
-  <li>Enable multi-station Precise Point Positioning for simultaneous processing of observations from a whole network of receivers</li>
-  <li>Plot positions derived via PPP from RTCM streams or RINEX files on maps from OpenStreetMap</li>
-  <li>Simultaneously process several SSR streams to produce, encode and upload combined SSR streams</li>
-  <li>Estimate real-time tropospheric zenith path delays and save them in SINEX troposphere file format</li>
-  <li>Read GNSS orbits and clocks in a plain ASCII format from an IP port. They can be produced by a real-time GNSS engine
+    <li>Carry out real-time Precise Point Positioning to determine GNSS rover positions</li>
+    <li>Enable multi-station Precise Point Positioning for simultaneous processing of observations from a whole network
+      of receivers</li>
+    <li>Plot positions derived via PPP from RTCM streams or RINEX files on maps from OpenStreetMap</li>
+    <li>Simultaneously process several SSR streams to produce, encode and upload combined SSR streams</li>
+    <li>Estimate real-time tropospheric zenith path delays and save them in SINEX troposphere file format</li>
+    <li>Read GNSS orbits and clocks in a plain ASCII format from an IP port. They can be produced by a real-time GNSS
+      engine
       and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. BNC will then</li>
     <ul>
-      <li>Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and out-of-plane components</li>
+      <li>Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial,
+        along-track and out-of-plane components</li>
       <li>Upload Broadcast Corrections as an RTCM-SSR or IGS-SSR stream to an Ntrip Broadcaster</li>
       <li>Refer the orbit and clock corrections to a specific reference system</li>
-      <li>Log the Broadcast Clock Corrections as Clock RINEX files for further processing using other tools than BNC</li>
-      <li>Log the Broadcast Orbit and Clock Corrections as SP3 files for further processing using other tools than BNC</li>
+      <li>Log the Broadcast Clock Corrections as Clock RINEX files for further processing using other tools than BNC
+      </li>
+      <li>Log the Broadcast Orbit and Clock Corrections as SP3 files for further processing using other tools than BNC
+      </li>
       <li>Log the Code and Phase Biases as SINEX Bias files for further processing using other tools than BNC</li>
     </ul>
-  <li>Upload a Broadcast Ephemeris stream in RTCM Version 3 format;</li>
-</ul>
-</p>
-
-<p>
-BNC supports the following GNSS stream formats and message types:
-</p>
-<p>
-<ul>
-  <li>RTCM Version 2 message types</li>
-  <li>RTCM Version 3 legacy message types</li>
-  <li>RTCM Version 3 Multiple Signal Messages (MSM) and High Precision Multiple Signal Messages (HP MSM)</li>
-  <li>RTCM Version 3 message types for Broadcast Ephemeris</li>
-  <li>RTCM Version 3 State Space Representation (SSR) messages</li>
-  <li>IGS State Space Representation (SSR) Version 1 messages</li>
-  <li>RTNET, a plain ASCII format defined within BNC to receive SSR informations from a serving GNSS engine</li>
-</ul>
-</p>
-
-<p>
-BNC supports the following GNSS file formats:
-</p>
-<p>
-<ul>
-  <li>RINEX Version 2.11, 3.x and 4.x, Receiver Independent Exchange format for observation and navigation data</li>
-  <li>The Extended Standard Product 3 Orbit Format SP3-d</li>
-  <li>Clock RINEX Version 3.04 format for (station and) satellite clock solutions</li>
-  <li>SINEX BIAS — Solution (Software/technique) INdependent EXchange Format for GNSS Biases Version 1.00</li>
-  <li>SINEX TRO — Solution (Software/technique) INdependent EXchange Format for TROpospherican meteorological parameters Version 2.0
-  <li>ANTEX Version 1.4, Antenna Exchange format for Antenna Phase Center variations</li>
-  <li>NMEA Version 0813, National Marine Electronics Association format for satellite navigation data</li>
-  <li>A plain ASCII format defined within BNC to save all SSR informations within a file</li>
-</ul>
-</p>
-
-<p>
-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 a local TCP/IP port.
-</p>
-
-<p><h4 id="introSystem">1.2 Supported GNSS</h4></p>
-<p>
-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:
-<ul>
-  <li>Decoding of RTCM, RTCM-SSR, IGS-SSR and RTNET streams</li>
-  <li>RINEX and SINEX Bias file input and output</li>
-  <li>SINEX TRO and SP3 file output</li>
-  <li>Encoding of SSR and ephemeris messages</li>
-  <li>Upload of SSR and ephemeris messages</li>
-  <li>PPP (Precise Point Positioning)</li>
-  <li>Combining/merging SSR or ephemeris messages from various real-time sources</li>
-</ul>
-The table indicates if a message implementation in BNC could so far only be based on a 'RTCM Proposal'.
-</p>
-<p>Table 1: Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</p>
-<p></p>
-<table border="1" rules="rows" frame="box" bgcolor="#FFF5EE" style="font-size:13">
-
-<tr align="center"><td><b>Message<br>Type #</b></td> <td><b>Description</b></td> <td><b>GNSS<br>System</b></td> <td><b>RTCM<br>Proposal&nbsp;</b></td> <td><b>Decoding&nbsp;</b></td> <td><b>&nbsp;RINEX/&nbsp;<br>&nbsp;SP3</b></td> <td><b>Encoding&nbsp;</b></td> <td><b>Upload&nbsp;</b></td> <td><b>&nbsp;PPP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b></td> <td><b>Combin.&nbsp;</b></td> </tr>
-
-<tr align="center"> <td><b><br>General</b></td> <td></td>             <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1005,1006</td> <td>Station</td>               <td> </td>             <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1007,1008</td> <td>Antenna</td>               <td> </td>             <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1033</td>      <td>Receiver, Antenna</td>     <td> </td>             <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1013</td>      <td>System Parameters</td>     <td> </td>             <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1300</td>      <td>Service CRS      </td>     <td> </td>             <td> </td> <td>x</td> <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1301</td>      <td>Helmert Trafo Parameters  </td>     <td> </td>    <td> </td> <td>x</td> <td> </td> <td>(x)</td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1302</td>      <td>RTCM CRS         </td>     <td> </td>             <td> </td> <td>x</td> <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> </tr>
-
-<tr align="center"> <td><b><br>Navigation</b></td> <td></td>          <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1019</td> <td>Ephemeris</td>                  <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1020</td> <td>Ephemeris</td>                  <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1045</td> <td>Ephemeris</td>                  <td>Galileo F/Nav</td> <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1046</td> <td>Ephemeris</td>                  <td>Galileo I/Nav</td> <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1043</td> <td>Ephemeris</td>                  <td>SBAS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1044</td> <td>Ephemeris</td>                  <td>QZSS</td>          <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1042</td> <td>Ephemeris</td>                  <td>BDS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1041</td> <td>Ephemeris</td>                  <td>NavIC</td>         <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-
-<tr align="center"> <td><b><br>Observation</b></td> <td></td>         <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1001-4</td>  <td>Conventional Messages</td>   <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1009-12</td> <td>Conventional Messages</td>   <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
-
-<tr align="center"> <td><b><br>Observation</b></td> <td></td>         <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1071-77</td> <td>Multiple Signal Message</td> <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1081-87</td> <td>Multiple Signal Message</td> <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1091-97</td> <td>Multiple Signal Message</td> <td>Galileo</td>       <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1101-07</td> <td>Multiple Signal Message</td> <td>SBAS</td>          <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1111-17</td> <td>Multiple Signal Message</td> <td>QZSS</td>          <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1121-27</td> <td>Multiple Signal Message</td> <td>BDS</td>           <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1131-37</td> <td>Multiple Signal Message</td> <td>NavIC</td>         <td> </td> <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-
-<tr align="center"> <td><b><br>RTCM SSR I</b></td> <td></td>          <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1057</td> <td>Orbit Corrections</td>          <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1063</td> <td>Orbit Corrections</td>          <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1240</td> <td>Orbit Corrections</td>          <td>Galileo</td>       <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1246</td> <td>Orbit Corrections</td>          <td>SBAS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1252</td> <td>Orbit Corrections</td>          <td>QZSS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1258</td> <td>Orbit Corrections</td>          <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-
-<tr align="center"> <td>1058</td> <td>Clock Corrections</td>          <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1064</td> <td>Clock Corrections</td>          <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1241</td> <td>Clock Corrections</td>          <td>Galileo</td>       <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1247</td> <td>Clock Corrections</td>          <td>SBAS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1253</td> <td>Clock Corrections</td>          <td>QZSS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1259</td> <td>Clock Corrections</td>          <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-
-<tr align="center"> <td>1059</td> <td>Code Biases</td>                <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1065</td> <td>Code Biases</td>                <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1242</td> <td>Code Biases</td>                <td>Galileo</td>       <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1248</td> <td>Code Biases</td>                <td>SBAS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1254</td> <td>Code Biases</td>                <td>QZSS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1260</td> <td>Code Biases</td>                <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-
-<tr align="center"> <td>1061, 1062</td> <td>User Range Accuracy, HR&nbsp;</td> <td>GPS</td>        <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1067, 1068</td> <td>User Range Accuracy, HR&nbsp;</td> <td>GLONASS</td>    <td> </td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1244, 1245</td> <td>User Range Accuracy, HR&nbsp;</td> <td>Galileo</td>    <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1250, 1251</td> <td>User Range Accuracy, HR&nbsp;</td> <td>SBAS</td>       <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1256, 1257</td> <td>User Range Accuracy, HR&nbsp;</td> <td>QZSS</td>       <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1262, 1263</td> <td>User Range Accuracy, HR&nbsp;</td> <td>BDS</td>        <td>x</td> <td>x</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-
-<tr align="center"> <td>1060</td> <td>Comb. Orbits & Clocks</td>      <td>GPS</td>           <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1066</td> <td>Comb. Orbits & Clocks</td>      <td>GLONASS</td>       <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1243</td> <td>Comb. Orbits & Clocks</td>      <td>Galileo</td>       <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-<tr align="center"> <td>1249</td> <td>Comb. Orbits & Clocks</td>      <td>SBAS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1255</td> <td>Comb. Orbits & Clocks</td>      <td>QZSS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td>x</td> </tr>
-<tr align="center"> <td>1261</td> <td>Comb. Orbits & Clocks</td>      <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-
-<tr align="center"> <td><b><br>RTCM SSR II</b></td> <td></td>         <td></td>             <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td>  </td> </tr>
-<tr align="center"> <td>1264</td> <td>VTEC</td>                       <td>GNSS </td>         <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1265</td> <td>Phase Biases</td>               <td>GPS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1266</td> <td>Phase Biases</td>               <td>GLONASS</td>       <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1267</td> <td>Phase Biases</td>               <td>Galileo</td>       <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td>1268</td> <td>Phase Biases</td>               <td>SBAS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1269</td> <td>Phase Biases</td>               <td>QZSS</td>          <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>1270</td> <td>Phase Biases</td>               <td>BDS</td>           <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td> </td> </tr>
-<tr align="center"> <td><b><br>IGS SSR</b></td> <td></td>             <td></td>              <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr>
-<tr align="center"> <td>4076</td> <td>IGS SSR</td>                    <td>GNSS </td>         <td> </td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> <td>x</td> </tr>
-
-</table>
-<br>
-<p><h4 id="introFlow">1.3 Data Flow</h4></p>
-<p>
-BNC can be used in different contexts with varying data flows. Typical real-time communication follows the Ntrip protocol
-over TCP/IP (also via SSL), RTSP/RTP or UDP, plain TCP/IP protocol, or serial communication links.
-Stream content could be observations, ephemeris, SSR products or NMEA sentences.
-</p>
-<p>
-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.
-</p>
-<p><img src="IMG/Figure01.png" width="1000"></p>
-<p>Figure 1: Flowchart, BNC connected to a GNSS rover for Precise Point Positioning</p>
-<p>
-The second figure shows the conversion of RTCM streams to RINEX files.
-</p>
-<p>
-</p>
-<p><img src="IMG/Figure02.png"width=1000/></p>
-<p>Figure 2: Flowchart, BNC converting RTCM streams to RINEX batches</p>
-<p>
-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 SSR corrections to RTCM-SSR or IGS-SSR and upload
-them to an Ntrip Broadcaster.
-</p>
-<p>
-</p>
-<p><img src="IMG/Figure03.png"width=1000/></p>
-<p>Figure 3: Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections</p>
-<p>
-The fourth figure shows BNC combining several Broadcast SSR Correction streams to
-disseminate the combination product while saving results in SP3, Clock RINEX and SINEX Bias files.
-</p>
-<p>
-</p>
-<p><img src="IMG/Figure04.png"width=1000/></p>
-<p>Figure 4: Flowchart, BNC combining Broadcast Correction streams</p>
-
-<p><h4 id="introHandling">1.4 Handling</h4></p>
-<p>
-Although BNC is mainly a real-time tool to be operated online, it can be run offline
-<ul>
-  <li>To simulate real-time observation situations for debugging purposes;</li>
-  <li>For post processing purposes.</li>
-</ul>
-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.
-</p>
-<p>
-Unless it runs offline, BNC
-</p>
-<ul>
-  <li>Requires access to the Internet with a minimum of about 2 to 6 kbits/sec per stream depending on the stream
-      format and the number of visible satellites. You need to make sure that the connection can sustain the required bandwidth;</li>
-  <li>Requires the clock of the host computer to be properly synchronized;</li>
-  <li>Has the capacity to retrieve hundreds of GNSS data streams simultaneously. Please be aware that such usage may
+    <li>Upload a Broadcast Ephemeris stream in RTCM Version 3 format;</li>
+  </ul>
+  </p>
+
+  <p>
+    BNC supports the following GNSS stream formats and message types:
+  </p>
+  <p>
+  <ul>
+    <li>RTCM Version 2 message types</li>
+    <li>RTCM Version 3 legacy message types</li>
+    <li>RTCM Version 3 Multiple Signal Messages (MSM) and High Precision Multiple Signal Messages (HP MSM)</li>
+    <li>RTCM Version 3 message types for Broadcast Ephemeris</li>
+    <li>RTCM Version 3 State Space Representation (SSR) messages</li>
+    <li>IGS State Space Representation (SSR) Version 1 messages</li>
+    <li>RTNET, a plain ASCII format defined within BNC to receive SSR informations from a serving GNSS engine</li>
+  </ul>
+  </p>
+
+  <p>
+    BNC supports the following GNSS file formats:
+  </p>
+  <p>
+  <ul>
+    <li>RINEX Version 2.11, 3.x and 4.x, Receiver Independent Exchange format for observation and navigation data</li>
+    <li>The Extended Standard Product 3 Orbit Format SP3-d</li>
+    <li>Clock RINEX Version 3.04 format for (station and) satellite clock solutions</li>
+    <li>SINEX BIAS — Solution (Software/technique) INdependent EXchange Format for GNSS Biases Version 1.00</li>
+    <li>SINEX TRO — Solution (Software/technique) INdependent EXchange Format for TROpospherican meteorological
+      parameters Version 2.0
+    <li>ANTEX Version 1.4, Antenna Exchange format for Antenna Phase Center variations</li>
+    <li>NMEA Version 0813, National Marine Electronics Association format for satellite navigation data</li>
+    <li>A plain ASCII format defined within BNC to save all SSR informations within a file</li>
+  </ul>
+  </p>
+
+  <p>
+    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 a local TCP/IP port.
+  </p>
+
+  <p>
+  <h4 id="introSystem">1.2 Supported GNSS</h4>
+  </p>
+  <p>
+    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:
+  <ul>
+    <li>Decoding of RTCM, RTCM-SSR, IGS-SSR and RTNET streams</li>
+    <li>RINEX and SINEX Bias file input and output</li>
+    <li>SINEX TRO and SP3 file output</li>
+    <li>Encoding of SSR and ephemeris messages</li>
+    <li>Upload of SSR and ephemeris messages</li>
+    <li>PPP (Precise Point Positioning)</li>
+    <li>Combining/merging SSR or ephemeris messages from various real-time sources</li>
+  </ul>
+  The table indicates if a message implementation in BNC could so far only be based on a 'RTCM Proposal'.
+  </p>
+  <p>Table 1: Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</p>
+  <p></p>
+  <table border="1" rules="rows" frame="box" bgcolor="#FFF5EE" style="font-size:13">
+
+    <tr align="center">
+      <td><b>Message<br>Type #</b></td>
+      <td><b>Description</b></td>
+      <td><b>GNSS<br>System</b></td>
+      <td><b>RTCM<br>Proposal&nbsp;</b></td>
+      <td><b>Decoding&nbsp;</b></td>
+      <td><b>&nbsp;RINEX/&nbsp;<br>&nbsp;SP3</b></td>
+      <td><b>Encoding&nbsp;</b></td>
+      <td><b>Upload&nbsp;</b></td>
+      <td><b>&nbsp;PPP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b></td>
+      <td><b>Combin.&nbsp;</b></td>
+    </tr>
+
+    <tr align="center">
+      <td><b><br>General</b></td>
+      <td></td>
+      <td></td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1005,1006</td>
+      <td>Station</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1007,1008</td>
+      <td>Antenna</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1033</td>
+      <td>Receiver, Antenna</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1013</td>
+      <td>System Parameters</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1300</td>
+      <td>Service CRS </td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1301</td>
+      <td>Helmert Trafo Parameters </td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td>(x)</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1302</td>
+      <td>RTCM CRS </td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+
+    <tr align="center">
+      <td><b><br>Navigation</b></td>
+      <td></td>
+      <td></td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1019</td>
+      <td>Ephemeris</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1020</td>
+      <td>Ephemeris</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1045</td>
+      <td>Ephemeris</td>
+      <td>Galileo F/Nav</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1046</td>
+      <td>Ephemeris</td>
+      <td>Galileo I/Nav</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1043</td>
+      <td>Ephemeris</td>
+      <td>SBAS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1044</td>
+      <td>Ephemeris</td>
+      <td>QZSS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1042</td>
+      <td>Ephemeris</td>
+      <td>BDS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1041</td>
+      <td>Ephemeris</td>
+      <td>NavIC</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+
+    <tr align="center">
+      <td><b><br>Observation</b></td>
+      <td></td>
+      <td></td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1001-4</td>
+      <td>Conventional Messages</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1009-12</td>
+      <td>Conventional Messages</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+
+    <tr align="center">
+      <td><b><br>Observation</b></td>
+      <td></td>
+      <td></td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1071-77</td>
+      <td>Multiple Signal Message</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1081-87</td>
+      <td>Multiple Signal Message</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1091-97</td>
+      <td>Multiple Signal Message</td>
+      <td>Galileo</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1101-07</td>
+      <td>Multiple Signal Message</td>
+      <td>SBAS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1111-17</td>
+      <td>Multiple Signal Message</td>
+      <td>QZSS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1121-27</td>
+      <td>Multiple Signal Message</td>
+      <td>BDS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1131-37</td>
+      <td>Multiple Signal Message</td>
+      <td>NavIC</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+
+    <tr align="center">
+      <td><b><br>RTCM SSR I</b></td>
+      <td></td>
+      <td></td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1057</td>
+      <td>Orbit Corrections</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1063</td>
+      <td>Orbit Corrections</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1240</td>
+      <td>Orbit Corrections</td>
+      <td>Galileo</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1246</td>
+      <td>Orbit Corrections</td>
+      <td>SBAS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1252</td>
+      <td>Orbit Corrections</td>
+      <td>QZSS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1258</td>
+      <td>Orbit Corrections</td>
+      <td>BDS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+
+    <tr align="center">
+      <td>1058</td>
+      <td>Clock Corrections</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1064</td>
+      <td>Clock Corrections</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1241</td>
+      <td>Clock Corrections</td>
+      <td>Galileo</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1247</td>
+      <td>Clock Corrections</td>
+      <td>SBAS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1253</td>
+      <td>Clock Corrections</td>
+      <td>QZSS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1259</td>
+      <td>Clock Corrections</td>
+      <td>BDS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+
+    <tr align="center">
+      <td>1059</td>
+      <td>Code Biases</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1065</td>
+      <td>Code Biases</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1242</td>
+      <td>Code Biases</td>
+      <td>Galileo</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1248</td>
+      <td>Code Biases</td>
+      <td>SBAS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1254</td>
+      <td>Code Biases</td>
+      <td>QZSS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1260</td>
+      <td>Code Biases</td>
+      <td>BDS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+
+    <tr align="center">
+      <td>1061, 1062</td>
+      <td>User Range Accuracy, HR&nbsp;</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1067, 1068</td>
+      <td>User Range Accuracy, HR&nbsp;</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1244, 1245</td>
+      <td>User Range Accuracy, HR&nbsp;</td>
+      <td>Galileo</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1250, 1251</td>
+      <td>User Range Accuracy, HR&nbsp;</td>
+      <td>SBAS</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1256, 1257</td>
+      <td>User Range Accuracy, HR&nbsp;</td>
+      <td>QZSS</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1262, 1263</td>
+      <td>User Range Accuracy, HR&nbsp;</td>
+      <td>BDS</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+
+    <tr align="center">
+      <td>1060</td>
+      <td>Comb. Orbits & Clocks</td>
+      <td>GPS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1066</td>
+      <td>Comb. Orbits & Clocks</td>
+      <td>GLONASS</td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1243</td>
+      <td>Comb. Orbits & Clocks</td>
+      <td>Galileo</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1249</td>
+      <td>Comb. Orbits & Clocks</td>
+      <td>SBAS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1255</td>
+      <td>Comb. Orbits & Clocks</td>
+      <td>QZSS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td>x</td>
+    </tr>
+    <tr align="center">
+      <td>1261</td>
+      <td>Comb. Orbits & Clocks</td>
+      <td>BDS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+
+    <tr align="center">
+      <td><b><br>RTCM SSR II</b></td>
+      <td></td>
+      <td></td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1264</td>
+      <td>VTEC</td>
+      <td>GNSS </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1265</td>
+      <td>Phase Biases</td>
+      <td>GPS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1266</td>
+      <td>Phase Biases</td>
+      <td>GLONASS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1267</td>
+      <td>Phase Biases</td>
+      <td>Galileo</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1268</td>
+      <td>Phase Biases</td>
+      <td>SBAS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1269</td>
+      <td>Phase Biases</td>
+      <td>QZSS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>1270</td>
+      <td>Phase Biases</td>
+      <td>BDS</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td><b><br>IGS SSR</b></td>
+      <td></td>
+      <td></td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr align="center">
+      <td>4076</td>
+      <td>IGS SSR</td>
+      <td>GNSS </td>
+      <td> </td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+      <td>x</td>
+    </tr>
+
+  </table>
+  <br>
+  <p>
+  <h4 id="introFlow">1.3 Data Flow</h4>
+  </p>
+  <p>
+    BNC can be used in different contexts with varying data flows. Typical real-time communication follows the Ntrip
+    protocol
+    over TCP/IP (also via SSL), RTSP/RTP or UDP, plain TCP/IP protocol, or serial communication links.
+    Stream content could be observations, ephemeris, SSR products or NMEA sentences.
+  </p>
+  <p>
+    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.
+  </p>
+  <p><img src="IMG/Figure01.png" width="1000"></p>
+  <p>Figure 1: Flowchart, BNC connected to a GNSS rover for Precise Point Positioning</p>
+  <p>
+    The second figure shows the conversion of RTCM streams to RINEX files.
+  </p>
+  <p>
+  </p>
+  <p><img src="IMG/Figure02.png" width=1000 /></p>
+  <p>Figure 2: Flowchart, BNC converting RTCM streams to RINEX batches</p>
+  <p>
+    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 SSR corrections to RTCM-SSR or IGS-SSR
+    and upload
+    them to an Ntrip Broadcaster.
+  </p>
+  <p>
+  </p>
+  <p><img src="IMG/Figure03.png" width=1000 /></p>
+  <p>Figure 3: Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections</p>
+  <p>
+    The fourth figure shows BNC combining several Broadcast SSR Correction streams to
+    disseminate the combination product while saving results in SP3, Clock RINEX and SINEX Bias files.
+  </p>
+  <p>
+  </p>
+  <p><img src="IMG/Figure04.png" width=1000 /></p>
+  <p>Figure 4: Flowchart, BNC combining Broadcast Correction streams</p>
+
+  <p>
+  <h4 id="introHandling">1.4 Handling</h4>
+  </p>
+  <p>
+    Although BNC is mainly a real-time tool to be operated online, it can be run offline
+  <ul>
+    <li>To simulate real-time observation situations for debugging purposes;</li>
+    <li>For post processing purposes.</li>
+  </ul>
+  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.
+  </p>
+  <p>
+    Unless it runs offline, BNC
+  </p>
+  <ul>
+    <li>Requires access to the Internet with a minimum of about 2 to 6 kbits/sec per stream depending on the stream
+      format and the number of visible satellites. You need to make sure that the connection can sustain the required
+      bandwidth;</li>
+    <li>Requires the clock of the host computer to be properly synchronized;</li>
+    <li>Has the capacity to retrieve hundreds of GNSS data streams simultaneously. Please be aware that such usage may
       incur a heavy load on the Ntrip Broadcaster side depending on the number of streams requested. We recommend
       limiting the number of streams where possible to avoid unnecessary workload.</li>
-</ul>
-</p>
-<p>
-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.
-</p>
-<p><img src="IMG/Figure05.png"width=1000/></p>
-<p>Figure 5: Sections on BNC's main window</p>
-
-<p>
-Running BNC in interactive mode requires graphics support. This is also
-required in batch mode when producing plots. Windows and Mac OS X systems always
-support graphics. However, when using BNC in batch mode on Linux systems for
-producing plots, you need to make sure that at least a virtual X-Server like
-'Xvfb' is installed and the '-display' command line option is used. Alternatively,
-the command line option '--plattform' can be tried to use with the argument 'offscreen'
-and the '-display' command line option.
-</p>
-<p>
-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.
-</p>
-<p>
-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.
-</p>
-<p>
-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).
-</p>
-<h4 id="introInst">1.5 Installation</h4>
-<p>
-Precompiled builds of BNC are available for Windows, Linux, and Mac OS X systems. They can be downloaded for
-installation from <a href="https://igs.bkg.bund.de/ntrip/bnc" target="_blank">https://igs.bkg.bund.de/ntrip/bnc</a>.
-Please ensure that you always use the latest version of the program.
-</p>
-<p>
-<b>Windows:</b> 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 MSVC 2019 compiler to create BNC for Windows.
-After installation your 'bnc.exe' file shows up e.g. under 'All Programs'.
-</p>
-<p>
-<b>Linux:</b> 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.
-</p>
-<p>
-<b>Mac OS X Build:</b>
-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 <i>'/Applications'</i> folder. To start BNC, double click on <i>'/Applications/bnc.app'</i>.
-You could also start BNC via Command Line Interface (CLI) using command <i>'/Applications/bnc.app/Contents/MacOS/bnc'</i>.
-</p>
-<h4 id="introCompile">1.5.1 Compilation</h4>
-<p>
-BNC has been written as Open Source and published under GNU General Public License (GPL). The latest source code can
-be checked out from the Subversion repository at <a href="http://software.rtcm-ntrip.org/svn/trunk/BNC"
-target="_blank">http://software.rtcm-ntrip.org/svn/trunk/BNC</a>. A ZIP archive available from
-<a href="https://igs.bkg.bund.de/ntrip/bnc" target="_blank">https://igs.bkg.bund.de/ntrip/bnc</a>
-provides the source code.
-</p>
-<p>The following describes how you can produce your own builds of BNC on Windows, Linux, and Mac systems.
-It is likely that BNC can also be compiled on other systems where a GNU compiler and Qt Version 5 or any later
- version is installed.
-</p>
-<p><b>Static versus Shared Libraries</b><br>
-You can produce static or shared library builds of BNC. <b>Static</b> builds are sufficient in case you do not want
-BNC to produce track maps on top of OpenStreetMap (OSM). The usage would require the
-QtWebEngineWidges library which can only be part of BNC builds from <b>shared</b> Qt libraries. Hence, having a shared library
- Qt installation available is a precondition for producing a shared library build of BNC.
-</p>
-
-<p><b>MS Windows Systems, Shared Library</b><br>
-This section contains some hints how to build a shared Qt 15.5.8 library on MS Windows systems to then create your own shared build of BNC.
-But it is highly recommended to use the dynamically compiled shared library build for Mircrosoft Windows systems which is provided as
-Microsoft Installer (MSI) file.
-</p>
-<ul>
-<li>Support for Secure Sockets Layer (SSL) communication is provided by the OpenSSL Toolkit, which must be obtained separately.
-Download the latest version of the toolkit that is supported by Qt and install OpenSSL libraries in C:\OpenSSL-Win64.
-The OpenSSL libraries are looked up first in the drectory of the executable, then in the Windows System directory,
-and finally in all directories listed in the PATH environment variable.
-You can configure how Qt uses OpenSSL by setting either the -openssl / -openssl-runtime or -openssl-linked configure flags.
-To link Qt Network against OpenSSL libraries, set the -openssl-linked configure argument and use the OPENSSL_PREFIX variable
-to let Qt correctly locate and build against your OpenSSL installation.
-For example: configure -openssl-linked OPENSSL_PREFIX="C:\OpenSSL-Win64".</li>
-<li>The following tools are required at build time:
-<ul>
-    <li>Python 2.7.5 or later. Python 3 is not supported.</li>
-    <li>Windows binaries of Bison, Flex, GPerf from the GnuWin32 project (<a href="http://gnuwin32.sourceforge.net/" target="_blank">http://gnuwin32.sourceforge.net/</a>), required to build QtWebEngine</li>
-    <li>Node.js version 12 or later</li>
-    <li>Visual Studio 2019 or clang-cl (msvc mode) version 8 or later, required to build QtWebEngine</li>
-    <li>Jom is recommended because it is a clone of nmake to support the execution of multiple independent commands in parallel.
-        It basically adds the -j command line switch similar to GNU make</li>
-    <li>Active Template Library (ATL), usually included in the Visual Studio installation</li>
-    <li>Windows 10 SDK version 10.0.19041 or later</li>
-</ul>
-and its location should be listed in the PATH environment variable.
-</li>
-<li>To use OpenGL, pass the command line option '-opengl dynamic' to the configure script.</li>
-<li>Download the file 'qt-everywhere-opensource-src-5.15.8.zip' e.g. from
-<a href="https://download.qt.io/official_releases/qt/5.15/5.15.8/single/"
-target="_blank">https://download.qt.io/official_releases/qt/5.15/5.15.8/single/</a>
-and unzip the ZIP archive and move the contents of the contained directory into a directory e.g. C:\Qt\qt-everywhere-src-5.15.8. </li>
-<li>Open a x64 Native Tools Command Promt for VS 2019 </li>
-<li>Go to directory C:\Qt\qt-everywhere-src-5.15.8 and configure Qt using command
-<pre>
+  </ul>
+  </p>
+  <p>
+    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.
+  </p>
+  <p><img src="IMG/Figure05.png" width=1000 /></p>
+  <p>Figure 5: Sections on BNC's main window</p>
+
+  <p>
+    Running BNC in interactive mode requires graphics support. This is also
+    required in batch mode when producing plots. Windows and Mac OS X systems always
+    support graphics. However, when using BNC in batch mode on Linux systems for
+    producing plots, you need to make sure that at least a virtual X-Server like
+    'Xvfb' is installed and the '-display' command line option is used. Alternatively,
+    the command line option '--plattform' can be tried to use with the argument 'offscreen'
+    and the '-display' command line option.
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    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).
+  </p>
+  <h4 id="introInst">1.5 Installation</h4>
+  <p>
+    Precompiled builds of BNC are available for Windows, Linux, and Mac OS X systems. They can be downloaded for
+    installation from <a href="https://igs.bkg.bund.de/ntrip/bnc" target="_blank">https://igs.bkg.bund.de/ntrip/bnc</a>.
+    Please ensure that you always use the latest version of the program.
+  </p>
+  <p>
+    <b>Windows:</b> 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 MSVC 2019 compiler to create BNC for Windows.
+    After installation your 'bnc.exe' file shows up e.g. under 'All Programs'.
+  </p>
+  <p>
+    <b>Linux:</b> 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.
+  </p>
+  <p>
+    <b>Mac OS X Build:</b>
+    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 <i>'/Applications'</i> folder. To start BNC, double click on
+    <i>'/Applications/bnc.app'</i>.
+    You could also start BNC via Command Line Interface (CLI) using command
+    <i>'/Applications/bnc.app/Contents/MacOS/bnc'</i>.
+  </p>
+  <h4 id="introCompile">1.5.1 Compilation</h4>
+  <p>
+    BNC has been written as Open Source and published under GNU General Public License (GPL). The latest source code can
+    be checked out from the Subversion repository at <a href="http://software.rtcm-ntrip.org/svn/trunk/BNC"
+      target="_blank">http://software.rtcm-ntrip.org/svn/trunk/BNC</a>. A ZIP archive available from
+    <a href="https://igs.bkg.bund.de/ntrip/bnc" target="_blank">https://igs.bkg.bund.de/ntrip/bnc</a>
+    provides the source code.
+  </p>
+  <p>The following describes how you can produce your own builds of BNC on Windows, Linux, and Mac systems.
+    It is likely that BNC can also be compiled on other systems where a GNU compiler and Qt Version 5 or any later
+    version is installed.
+  </p>
+  <p><b>Static versus Shared Libraries</b><br>
+    You can produce static or shared library builds of BNC. <b>Static</b> builds are sufficient in case you do not want
+    BNC to produce track maps on top of OpenStreetMap (OSM). The usage would require the
+    QtWebEngineWidges library which can only be part of BNC builds from <b>shared</b> Qt libraries. Hence, having a
+    shared library
+    Qt installation available is a precondition for producing a shared library build of BNC.
+  </p>
+
+  <p><b>MS Windows Systems, Shared Library</b><br>
+    This section contains some hints how to build a shared Qt 15.5.8 library on MS Windows systems to then create your
+    own shared build of BNC.
+    But it is highly recommended to use the dynamically compiled shared library build for Mircrosoft Windows systems
+    which is provided as
+    Microsoft Installer (MSI) file.
+  </p>
+  <ul>
+    <li>Support for Secure Sockets Layer (SSL) communication is provided by the OpenSSL Toolkit, which must be obtained
+      separately.
+      Download the latest version of the toolkit that is supported by Qt and install OpenSSL libraries in
+      C:\OpenSSL-Win64.
+      The OpenSSL libraries are looked up first in the drectory of the executable, then in the Windows System directory,
+      and finally in all directories listed in the PATH environment variable.
+      You can configure how Qt uses OpenSSL by setting either the -openssl / -openssl-runtime or -openssl-linked
+      configure flags.
+      To link Qt Network against OpenSSL libraries, set the -openssl-linked configure argument and use the
+      OPENSSL_PREFIX variable
+      to let Qt correctly locate and build against your OpenSSL installation.
+      For example: configure -openssl-linked OPENSSL_PREFIX="C:\OpenSSL-Win64".</li>
+    <li>The following tools are required at build time:
+      <ul>
+        <li>Python 2.7.5 or later. Python 3 is not supported.</li>
+        <li>Windows binaries of Bison, Flex, GPerf from the GnuWin32 project (<a href="http://gnuwin32.sourceforge.net/"
+            target="_blank">http://gnuwin32.sourceforge.net/</a>), required to build QtWebEngine</li>
+        <li>Node.js version 12 or later</li>
+        <li>Visual Studio 2019 or clang-cl (msvc mode) version 8 or later, required to build QtWebEngine</li>
+        <li>Jom is recommended because it is a clone of nmake to support the execution of multiple independent commands
+          in parallel.
+          It basically adds the -j command line switch similar to GNU make</li>
+        <li>Active Template Library (ATL), usually included in the Visual Studio installation</li>
+        <li>Windows 10 SDK version 10.0.19041 or later</li>
+      </ul>
+      and its location should be listed in the PATH environment variable.
+    </li>
+    <li>To use OpenGL, pass the command line option '-opengl dynamic' to the configure script.</li>
+    <li>Download the file 'qt-everywhere-opensource-src-5.15.8.zip' e.g. from
+      <a href="https://download.qt.io/official_releases/qt/5.15/5.15.8/single/"
+        target="_blank">https://download.qt.io/official_releases/qt/5.15/5.15.8/single/</a>
+      and unzip the ZIP archive and move the contents of the contained directory into a directory e.g.
+      C:\Qt\qt-everywhere-src-5.15.8.
+    </li>
+    <li>Open a x64 Native Tools Command Promt for VS 2019 </li>
+    <li>Go to directory C:\Qt\qt-everywhere-src-5.15.8 and configure Qt using command
+      <pre>
 .\configure -prefix C:\Qt\5.15.8\ -opensource -release -platform win32-msvc -icu -I C:\icu-windows\include -L C:\icu-windows\lib64 -qt-pcre -qt-zlib -qt-freetype -qt-harfbuzz -qt-libpng -qt-libjpeg -qt-sqlite -qt-tiff -qt-webp -mp -confirm-license -openssl-linked OPENSSL_PREFIX="C:\OpenSSL-Win64" -opengl dynamic -webengine-proprietary-codecs -recheck-all -nomake tests -nomake examples -no-sql-mysql -skip qtdoc -skip qtquickcontrols -skip qtscript -skip qtxmlpatterns -skip qtandroidextras -skip qtgamepad -skip qtmultimedia -skip qtpurchasing -skip qtwayland -skip qtspeech -skip qtlottie -skip qtscxml -skip qt3d -skip qtcharts -skip qtdatavis3d -skip qtgraphicaleffects -skip qtquickcontrols -skip qtquickcontrols2 -skip qtremoteobjects
 </pre>
-</li>
-<li>Compile Qt using command <pre>  jom or nmake </pre></li>
-<li>Install Qt using command <pre>  jom install or nmake install</pre></li>
-
-<li>Create somewhere a file QtEnv.bat with the following content:
-<pre>
+    </li>
+    <li>Compile Qt using command
+      <pre>  jom or nmake </pre>
+    </li>
+    <li>Install Qt using command
+      <pre>  jom install or nmake install</pre>
+    </li>
+
+    <li>Create somewhere a file QtEnv.bat with the following content:
+      <pre>
    set QTDIR=C:\Qt\5.15.8
    set PATH=%PATH%C:\Qt\5.15.8\bin;
    set QMAKESPEC=C:\Qt\5.15.8\mkspecs\win32-msvc
 </pre>
-and exceute file QtEnv.bat</li>
-
-<li>Download latest BNC from SVN repository <a href="http://software.rtcm-ntrip.org/svn/trunk/BNC"
-target="_blank">http://software.rtcm-ntrip.org/svn/trunk/BNC</a>.</li>
-
-<li>Go to directory BNC and enter command
-<pre>
+      and exceute file QtEnv.bat
+    </li>
+
+    <li>Download latest BNC from SVN repository <a href="http://software.rtcm-ntrip.org/svn/trunk/BNC"
+        target="_blank">http://software.rtcm-ntrip.org/svn/trunk/BNC</a>.</li>
+
+    <li>Go to directory BNC and enter command
+      <pre>
    qmake bnc.pro
-</pre></li>
-
-<li>Enter command
-<pre>
+</pre>
+    </li>
+
+    <li>Enter command
+      <pre>
    nmake
-</pre></li>
-<li>Find binary file bnc.exe in directory named src.</li>
-</ul>
-<p>
-<b>Linux Systems</b><br>
-Qt development tools have to be installed as well as some other libraries e.g. for openssl. They can be easily installed from
-your system repositories. BNC 2.13 needs Qt5. See the <a href="https://software.rtcm-ntrip.org/browser/ntrip/trunk/BNC/docker" target="_blank">docker files</a> for the most used Linux systems.
-To compile the BNC program, you first download the source code from the SVN repository <a href="http://software.rtcm-ntrip.org/svn/trunk/BNC"
-target="_blank">http://software.rtcm-ntrip.org/svn/trunk/BNC</a>. Go to directory BNC and run the following commands:<br>
-</p>
-<pre>
+</pre>
+    </li>
+    <li>Find binary file bnc.exe in directory named src.</li>
+  </ul>
+  <p>
+    <b>Linux Systems</b><br>
+    Qt development tools have to be installed as well as some other libraries e.g. for openssl. They can be easily
+    installed from
+    your system repositories. BNC 2.13 needs Qt5. See the <a
+      href="https://software.rtcm-ntrip.org/browser/ntrip/trunk/BNC/docker" target="_blank">docker files</a> for the
+    most used Linux systems.
+    To compile the BNC program, you first download the source code from the SVN repository <a
+      href="http://software.rtcm-ntrip.org/svn/trunk/BNC"
+      target="_blank">http://software.rtcm-ntrip.org/svn/trunk/BNC</a>. Go to directory BNC and run the following
+    commands:<br>
+  </p>
+  <pre>
     qmake bnc.pro
     make
 </pre>
-You will find a build of BNC in directory BNC.
-<p>
-<b>Mac OS X Systems</b><br>
-</p>
-Please use the precompiled build of BNC
-</p>
-
-<p><h4 id="introConf">1.6 Configuration</h4></p>
-<p>
-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'.</p>
-<p>
-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 &amp; 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.
-</p>
-<p>
-BNC maintains configuration options at three different levels:
-</p>
-<ul>
-  <li>GUI, input fields level</li>
-  <li>Active configuration level</li>
-  <li>Configuration file, disk level</li>
-</ul>
-<p><img src="IMG/Figure06.png"width=1000/></p>
-<p>Figure 6: Management of configuration options in BNC:<br>
-<table>
-<tr><td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td><td>Left:</td><td>BNC in graphics mode; active configuration options are introduced through GUI input fields and finally saved on disk</td></tr>
-<tr><td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td><td>Middle:</td><td>BNC in 'no window' mode; active configuration options are read from disk</td></tr>
-<tr><td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td><td>Right:</td><td>BNC in 'no window' mode without configuration file; default configuration options can be overwritten via command line options</td></tr>
-</table>
-
-<p>
-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:
-</p>
-<ul>
-  <li>Active configuration options (2) are independent from GUI input fields and configuration file content.</li>
-  <li>Hence changing configuration options at GUI level (1) while BNC is already processing data does not influence a running job.</li>
-  <li>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:</li>
+  You will find a build of BNC in directory BNC.
+  <p>
+    <b>Mac OS X Systems</b><br>
+  </p>
+  Please use the precompiled build of BNC
+  </p>
+
+  <p>
+  <h4 id="introConf">1.6 Configuration</h4>
+  </p>
+  <p>
+    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'.</p>
+  <p>
+    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 &amp; 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.
+  </p>
+  <p>
+    BNC maintains configuration options at three different levels:
+  </p>
+  <ul>
+    <li>GUI, input fields level</li>
+    <li>Active configuration level</li>
+    <li>Configuration file, disk level</li>
+  </ul>
+  <p><img src="IMG/Figure06.png" width=1000 /></p>
+  <p>Figure 6: Management of configuration options in BNC:<br>
+  <table>
+    <tr>
+      <td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
+      <td>Left:</td>
+      <td>BNC in graphics mode; active configuration options are introduced through GUI input fields and finally saved
+        on disk</td>
+    </tr>
+    <tr>
+      <td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
+      <td>Middle:</td>
+      <td>BNC in 'no window' mode; active configuration options are read from disk</td>
+    </tr>
+    <tr>
+      <td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
+      <td>Right:</td>
+      <td>BNC in 'no window' mode without configuration file; default configuration options can be overwritten via
+        command line options</td>
+    </tr>
+  </table>
+
+  <p>
+    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:
+  </p>
+  <ul>
+    <li>Active configuration options (2) are independent from GUI input fields and configuration file content.</li>
+    <li>Hence changing configuration options at GUI level (1) while BNC is already processing data does not influence a
+      running job.</li>
+    <li>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:</li>
     <ul>
-      <li>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.</li>
-      <li>Specifying the 'Reread configuration' option lets BNC reread its configuration from disk at pre-defined intervals.</li>
+      <li>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.</li>
+      <li>Specifying the 'Reread configuration' option lets BNC reread its configuration from disk at pre-defined
+        intervals.</li>
     </ul>
-  <li>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.</li>
-</ul>
-
-
-<p><h4 id="introExamples">1.6.1 Examples</h4></p>
-<p>
-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:
-</p>
-<ul>
-  <li>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.</li>
-  <li>You could also start BNC using a command line for naming a specific configuration file (suggested e.g. for Mac systems):<br>
+    <li>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.</li>
+  </ul>
+
+
+  <p>
+  <h4 id="introExamples">1.6.1 Examples</h4>
+  </p>
+  <p>
+    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:
+  </p>
+  <ul>
+    <li>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.</li>
+    <li>You could also start BNC using a command line for naming a specific configuration file (suggested e.g. for Mac
+      systems):<br>
       /Applications/bnc.app/Contents/MacOS/bnc --conf &lt;configFileName&gt;</li>
-  <li>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 '<u>n</u>o <u>w</u>indow' mode (example for Windows systems):<br>
+    <li>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 '<u>n</u>o <u>w</u>indow' mode (example for Windows systems):<br>
       bnc.exe --conf &lt;configFileName&gt; --nw</li>
-</ul>
-<p>
-Although it's not a must, we suggest that you always create BNC configuration files with filename extension '.bnc'.
-</p>
-
-<p>
-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:
-</p>
-
-<ol type="1">
-  <li>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.</li>
-  <li>Windows displays a dialog box that says that the system cannot open this file. The dialog box offers several options for selecting a program.</li>
-  <li>Click 'Select the program from a list', and then click 'OK'.</li>
-  <li>The 'Open With' dialog box is displayed. Click 'Browse', locate and then click the BNC program, and then click 'Open'.</li>
-  <li>Click to select the 'Always use the selected program to open this kind of file' check box.</li>
-  <li>Click 'OK'.</li>
-</ol>
-
-<p>
-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 <a href="http://register.rtcm-ntrip.org" target="_blank">http://register.rtcm-ntrip.org</a>.
-</p>
-
-<p>
-  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.
-</p>
-
-<p>
-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.
-</p>
-
-<p>
-Some BNC options require Antenna Phase Center variations as made available from IGS through so-called ANTEX files
-at <a href="https://files.igs.org/pub/station/general/igs20.atx" target="_blank">https://files.igs.org/pub/station/general/igs20.atx</a>.
-An example ANTEX file 'igs20.atx' is part of the BNC package for convenience.
-</p>
-
-<p>
-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.
-</p>
-
-<p>
-<b>(A) Working with Configuration Files</b><br><br>
-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.
-</p>
-
-<ol type="1">
-<li> Configuration File 'RinexObs.bnc'<br>
-Purpose: Convert RTCM streams to RINEX Observation files.
-The configuration pulls RTCM Version 3 streams from Ntrip Broadcasters using
-Ntrip Version 2 to generate 15min 1Hz RINEX Version 4 Observation files.
-See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-obs" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-obs</a>
-for observation stream resources.
-</li>
-
-<li>Configuration File 'RinexEph.bnc'<br>
-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
-4 Navigation files. See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-eph" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-eph</a>
-for further real-time Broadcast Ephemeris resources.
-</li>
-
-<li>Configuration File 'BrdcCorr.bnc'<br>
-Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain
-ASCII files. See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-corr" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-corr</a>
-for various real-time IGS or EUREF orbit/clock correction products.
-</li>
-
-<li>Configuration File 'RinexConcat.bnc'<br>
-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.
-</li>
-
-<li>Configuration File 'RinexQC.bnc'<br>
-Purpose: Check the quality of a RINEX Version 4 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.
-</li>
-
-<li>Configuration File 'RTK.bnc'<br>
-Purpose: Feed a serial 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.
-</li>
-
-<li>Configuration File 'FeedEngine.bnc'<br>
-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.
-</li>
-
-<li>Configuration File 'PPP.bnc'<br>
-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.
-More detailed PPP results are saved in the PPP logfile.
-</li>
-
-<li>Configuration File 'PPPNet.bnc'<br>
-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.
-Detailed PPP Results for the two stations are saved in PPP logfiles.
-</li>
-
-<li>Configuration File 'PPPQuickStart.bnc'<br>
-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.
-</li>
-
-<li>Configuration File 'PPPPostProc.bnc'<br>
-Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX
-Version 3 Observation and Navigation files and a Broadcast Correction file.
-Optionally, an Ionosphere file containing VTEC informations can be used. If such
-a file is not specified, VTEC informations from the Broadcast Corrections file
-are used. PPP processing options are set to support the Quick-Start mode.
-The output is saved in a specific post processing logfile and contains
-coordinates derived over time following the implemented PPP filter algorithm.
-</li>
-
-<li>Configuration File 'PPPOsm.bnc'<br>
-Purpose: Track BNC's point positioning solutions using OpenStreetMap as background.
-BNC reads a RINEX Observation file and a RINEX Navigation file to carry out
-a 'Standard Point Positioning' solution in post processing mode.
-Although 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 OSM maps.
-</li>
-
-<li>Configuration File 'PPPGalHAS.bnc'<br>
-Purpose: Precise Point Positioning in Quick-Start mode with SSR corrections
-from the Galileo HAS Internet Data Distribution (IDD) interface with observations
-of a static receiver with quite precisely known position.
-Because the Galileo HAS provides Code Biases and corrections for satellite orbits
-and clocks for GPS and Galileo, the configuration uses GPS and Galileo
-navigation data only.
-Access to the Galileo HAS Internet Data Distribution is available by registration:
-<a href="https://www.gsc-europa.eu/galileo/services/galileo-high-accuracy-service-has/internet-data-distribution-registration-form"
-target="_blank">https://www.gsc-europa.eu/galileo/services/galileo-high-accuracy-service-has/internet-data-distribution-registration-form</a>
-
-Purpose: Single Point Positioning in Quick-Start mode from observations of a
-static receiver with quite precisely known position. The configuration uses
-Galileo observations only and a Broadcast Ephemeris stream.
-</li>
-
-<li>Configuration File 'SaveSp3.bnc'<br>
-Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast
-Correction stream. The Broadcast Correction stream is formally introduced in
-BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX
-file because SP3 file content should be referred to CoM..
-</li>
-
-<li>Configuration File 'Sp3ETRF2000PPP.bnc'<br>
-Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream
-carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is
-formally introduced in BNC's 'Combine Corrections' table. The configuration
-leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in
-addition observations from a reference station at precisely known ETRF2000
-position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000
-reference coordinate.
-</li>
-
-<li>Configuration File 'Upload.bnc'<br>
-Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip
-Broadcaster. For that the configuration reads precise orbits and clocks in
-RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts
-the orbits and clocks into Broadcast Corrections and encodes them to
-IGS-SSR messages to finally upload them to an Ntrip Broadcaster. The
-Broadcast Correction stream is referred to satellite Antenna Phase Center (APC)
-and reference system IGS20. Orbits are saved on disk in SP3 format and clocks
-are saved in Clock RINEX format.
-</li>
-
-<li>Configuration File 'Combi.bnc'<br>
-Purpose: Pull 2 streams carrying Broadcast Corrections, and Satellite Code Biases
-together with Broadcast Ephemeris from an Ntrip Broadcaster
-to produce a combined Broadcast Correction stream.
-BNC encodes the combination product in IGS-SSR messages and uploads them to
-an Ntrip Broadcaster. The Broadcast Correction stream is referred to
-satellite Antenna Phase Center (APC) and not to satellite Center of
-Mass (CoM). Its reference system is IGS20. Orbits are saved in SP3 format
-(referred to CoM) and clocks in Clock RINEX format.
-</li>
-
-<li>Configuration File 'CombiPPP.bnc'<br>
-Purpose: This configuration equals the 'Combi.bnc' configuration. However, the
-combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
-solutions based on observations from a static reference station with known
-precise coordinates. This allows a continuous quality check of the combination
-product through observing coordinate displacements.
-</li>
-
-<li>Configuration File 'UploadEph.bnc'<br>
-Purpose: Pull a number of streams from reference stations to get the
-contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3
-format and uploaded for the purpose of providing a Broadcast Ephemeris stream
-with an update rate of 5 seconds.
-</li>
-
-<li>Configuration File 'UploadRaw.bnc'<br>
-Purpose: Forward the stream contents of the incoming stream BCEP00BKG0
-from products.igs-ip.net to another caster.
-</li>
-
-<li>Configuration File 'CompareSp3.bnc'<br>
-Purpose: Compare two SP3 files to calculate RMS values for orbit and clock
-differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this
-comparison. Comparison results are saved in a logfile.
-</li>
-
-<li>Configuration File 'Empty.bnc'<br>
-Purpose: Provide an empty example configuration file for BNC which only
-contains the default settings.
-</li>
-
-<li value="29"> Configuration File '29_PPPAR_CNES.bnc'<br>
-Purpose: Precise Point Positioning with ambiguity resolution using an raw input file.
-Call: bnc --conf  29_PPPAR_CNES.bnc --file WTZR_CNES_20251117.raw
-The configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
-and a stream with SSR Corrections enabling PPP-AR. Positions are saved in the logfile.
-More detailed PPP results are saved in the PPP logfile.
-
-<li value="30"> Configuration File '30_PPPAR_WHU.bnc'<br>
-Purpose: Precise Point Positioning with ambiguity resolution using an raw input file.
-Call: bnc --conf 30_PPPAR_WHU.bnc --file  WTZR_WHU_20251129.raw
-The configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
-and a stream with SSR Corrections enabling PPP-AR. Positions are saved in the logfile.
-More detailed PPP results are saved in the PPP logfile.
-</li>
-
-</ol>
-<b>(B) Working with Command Line configuration options</b><br><br>
-The following configuration examples make use of BNC's 'Command Line Interface' (CLI). Configuration options are
-exclusively specified via command line. No configuration file is used. Examples are provided as shell scripts
-for a Linux system. They call BNC in 'no window' batch mode (command line option -nw). The scripts expect
-'Example_Configs' to be the current working directory.
-</li>
-
-<ol start="23">
-<li>Shell Script 'RinexQC.sh'<br>
-Purpose: Equals configuration file example 'RinexQC.bnc', checks the quality of
-a RINEX Version 4 file by means of a multipath analysis. The platform offscreen
-is used while producing plot files in PNG format. BNC is offline.
-All results are saved on disk.
-</li>
-
-<li>Shell Script 'RinexConcat.sh'<br>
-Purpose: Equals configuration file example 'RinexConcat.bnc', concatenates
-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. BNC is
-offline.
-</li>
-
-<li>Shell Script 'RinexEph.sh'<br>
-Purpose: Equals configuration file example 'RinexEph.bnc', converts 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 4 Navigation
-files. BNC runs online until it's terminated after 10 seconds.
-See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-eph" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-eph</a>
-for further real-time Broadcast Ephemeris resources.
-</li>
-
-<li>Shell Script 'ScanLate.sh'<br>
-Purpose: Scan an observation stream for contained RTCM message types, print
-observation latencies. The output is saved in a logfile. Latencies are
-reported every 10 seconds. BNC runs online until it's terminated after 20
-seconds.
-</li>
-
-<li>Shell Script 'RinexObs.sh'<br>
-Purpose: Equals configuration file example 'RinexObs.bnc', converts RTCM
-streams to RINEX Observation files. The configuration pulls streams from two
-Ntrip Broadcasters using Ntrip Version 2 to generate 15min 1Hz RINEX Version 4
-Observation files.
-See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-obs" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-obs</a>
-for observation stream resources. BNC runs online until it's terminated after 30
-seconds.
-</li>
-</ol>
-
-<b>(C) Command Line configuration options overwriting Configuration File options</b><br><br>
-For specific applications you may like to use your own set of standard configuration options from a configuration file and update some of its content via command line. When using a configuration file together with command line configuration options in one BNC call, the command line configuration options will always overrule options contained in the configuration file.
-
-<ol start="28">
-<li>Shell Script 'CompareSp3.sh'<br>
-Purpose: Equals configuration file example 'CompareSp3.bnc', compares two SP3
-files to calculate RMS values for orbit and clock differences. However, instead
-of excluding GPS satellite G05 and GLONASS satellite R18 from the comparison as
-specified in 'CompareSp3.bnc', GPS satellite G06 and all GLONASS satellites are
-excluded via command line option. BNC runs offline. Comparison results are saved
-in a logfile.
-</li>
-</ol>
-</p>
-
-<p><h4 id="introLimit">1.7 Limitations</h4></p>
-<ul>
-<li>
-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.
-</li>
-
-<li>
-Using RTCM Version 3 to produce RINEX files, BNC will properly handle most message types. However, when handling message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458 (speed of light).
-</li>
-<li>
-Using RTCM Version 2, BNC will only handle message types 18 and 19 or 20 and 21 together with position and the antenna offset information carried in types 3 and 22. Note that processing carrier phase corrections and pseudo-range corrections contained in message types 20 and 21 needs access to Broadcast Ephemeris. Hence, whenever dealing with message types 20 and 21, make sure that Broadcast Ephemeris become available for BNC through also retrieving at least one RTCM Version 3 stream carrying message types 1019 (GPS ephemeris) and 1020 (GLONASS ephemeris).
-</li>
-<li>
-BNC's 'Get Table' function only shows the STR records of a source-table. You can use an Internet browser to download the full source-table content of any Ntrip Broadcaster by simply entering its URL in the form of <u>http://host:port</u>. Data field number 8 in the NET records may provide information about where to register for an Ntrip Broadcaster account.
-</li>
-<li>
-EUREF as well as IGS adhere to an open data policy. Streams are made available through Ntrip Broadcasters at
- <a href="http://euref-ip.net/home" target="_blank">http://euref-ip.net/home</a>,
- <a href="http://igs-ip.net/home" target="_blank">http://igs-ip.net/home</a> and
- <a href="http://products.igs-ip.net/home" target="_blank">http://products.igs-ip.net/home</a>
- 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.
-</li>
-<li>
-Once BNC has been started, many of its configuration options cannot be changed as long as it is stopped. See chapter 'Reread Configuration' for on-the-fly configuration exceptions.
-</li>
-<li>
-Drag and drop of configuration files is currently not supported on Mac OS X. On such system you have to start BNC via command line.
-</li>
-</ul>
-
-<p><h4 id="introLBack">Looking Back</h4></p>
-<p>
-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.
-</p>
-<p>
-To cope with an increasing number of transmitting GNSS reference stations, the Federal Agency for Cartography and Geodesy (BKG)
-together with the Informatik Centrum Dortmund (ICD) in Germany developed a streaming protocol for satellite navigation data called
-'Networked Transport of RTCM via Internet Protocol' (Ntrip). The protocol was built on top of the HTTP standard and included the
-provision of meta data describing the stream content. Any stream could now be globally transmitted over just one IP port: HTTP port 80.
-Stream availability and content details became part of the transport protocol. The concept was first published in 2003
-(Weber and Honkala 2004, Weber et al. 2005a) and was based on three software components, namely an NtripServer pushing data from
-a reference station to an NtripCaster and an NtripClient pulling data from the stream splitting caster to support a rover receiver.
-(Note that from a socket-programmers perspective NtripServer and NtripClient both act as clients; only the NtripCaster operates as socket-server.)
-Ntrip could essentially benefit from Internet Radio developments. It was the ICECAST multimedia server, which provided the bases
-for BKG's 'Professional Ntrip Broadcaster' with software published first in 2003 and of course again as Open Source under GPL.
-</p>
-<p>
-For BKG as a governmental agency, making Ntrip an Open Industry Standard has been an objective from the very beginning.
-The 'Radio Technical Commission for Maritime Services' (RTCM) accepted 'Ntrip Version 1' in 2004 as 'RTCM Recommended Standard' (Weber et al. 2005b).
-Nowadays there is almost no geodetic GNSS receiver which does not come with integrated NtripClient and NtripServer functionality as part of the firmware.
-Hundreds of NtripCaster implementations are operated world-wide for highly accurate satellite navigation through RTK networks.
-Thousands of reference stations upload observations via NtripServer to central computing facilities for any kind of NtripClient application.
-In 2011 'Ntrip Version 2' was released (RTCM SC-104 2011) which cleared and fixed some design problems and HTTP protocol violations.
-It also supports TCP/IP via SSL and adds optional communication over RTSP/RTP and UDP.
-</p>
-<p>
-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.
-</p>
-<p>
-Adding real-time Precise Point Positioning (PPP) support to BNC began in 2010 as an important completion in view of developing an
-Open RTCM Standard for that. According to the State Space Representation (SSR) model, new Version 3 messages are proposed to provide e.g.
-satellite orbit and clock corrections and ionospheric corrections as well as biases for code and phase data.
-The ultimate goal for SSR standardization is to reach centimeter level accuracy within seconds as an alternative to Network RTK methods
-such as VRS, FKP, and MAC. Because of interoperability aspects, an Open Standard in this area is of particular interest for clients.
-Regarding stand-alone PPP in BNC, it is worth mentioning that the program is not and can never be in competition with a receiver
-manufacturer's proprietary solution. Only software or services that are part of a receiver firmware could have the potential of
-becoming a thread for commercial interests. However, implementing or not implementing an Open PPP approach in a firmware is and
-will always remain a manufacturer's decision.
-</p>
-<p>
-Implementing some post processing capability is essential for debugging real-time software in case of problems.
-So certain real-time options in BNC were complemented to work offline through reading data from files.
-Moreover, beginning in 2012, the software was extended to support Galileo, BeiDou, and QZSS besides GPS and GLONASS.
-With that, the Open Source tool BNC could be used for RINEX Version 3 file editing, concatenation and quality checks,
- a post processing functionality demanded by the IGS Multi-GNSS Experiment and not really covered at that time by
- UNAVCO's famous TEQC program with its limitation on GPS.
-</p>
-
-<p>
-The well-established, mature codebase is mostly written in C++ language.
-Its publication under GNU GPL is thought to be well-suited for test, validation and demonstration of new
-approaches in precise real-time satellite navigation when IP streaming is involved. Commissioned by a
-German governmental agency, the overall intention has been to push the development of RTCM Recommended Standards
-to the benefit of IAG institutions and services such as IGS and the interested public in general.
-</p>
-
-<p><h3 id="optsettings">2. Settings Details</h3></p>
-<p>
-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.
-</p>
-<p>
-The following chapters describe how to set BNC program options. They explain the 'Top Menu Bar', the 'Settings Canvas' with the
-processing options, the content of the 'Streams Canvas' and 'Logging Canvas', and the 'Bottom Menu Bar'.
-</p>
-
-<p><h4 id="topmenu">2.1 Top Menu Bar</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="file">2.1.1 File</h4></p>
-
-<p>
-The 'File' button lets you
-</p>
-<ul>
-  <li>Select an appropriate font.<br>
+  </ul>
+  <p>
+    Although it's not a must, we suggest that you always create BNC configuration files with filename extension '.bnc'.
+  </p>
+
+  <p>
+    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:
+  </p>
+
+  <ol type="1">
+    <li>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.</li>
+    <li>Windows displays a dialog box that says that the system cannot open this file. The dialog box offers several
+      options for selecting a program.</li>
+    <li>Click 'Select the program from a list', and then click 'OK'.</li>
+    <li>The 'Open With' dialog box is displayed. Click 'Browse', locate and then click the BNC program, and then click
+      'Open'.</li>
+    <li>Click to select the 'Always use the selected program to open this kind of file' check box.</li>
+    <li>Click 'OK'.</li>
+  </ol>
+
+  <p>
+    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 <a
+      href="http://register.rtcm-ntrip.org" target="_blank">http://register.rtcm-ntrip.org</a>.
+  </p>
+
+  <p>
+    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.
+  </p>
+
+  <p>
+    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.
+  </p>
+
+  <p>
+    Some BNC options require Antenna Phase Center variations as made available from IGS through so-called ANTEX files
+    at <a href="https://files.igs.org/pub/station/general/igs20.atx"
+      target="_blank">https://files.igs.org/pub/station/general/igs20.atx</a>.
+    An example ANTEX file 'igs20.atx' is part of the BNC package for convenience.
+  </p>
+
+  <p>
+    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.
+  </p>
+
+  <p>
+    <b>(A) Working with Configuration Files</b><br><br>
+    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.
+  </p>
+
+  <ol type="1">
+    <li> Configuration File 'RinexObs.bnc'<br>
+      Purpose: Convert RTCM streams to RINEX Observation files.
+      The configuration pulls RTCM Version 3 streams from Ntrip Broadcasters using
+      Ntrip Version 2 to generate 15min 1Hz RINEX Version 4 Observation files.
+      See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-obs" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-obs</a>
+      for observation stream resources.
+    </li>
+
+    <li>Configuration File 'RinexEph.bnc'<br>
+      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
+      4 Navigation files. See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-eph"
+        target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-eph</a>
+      for further real-time Broadcast Ephemeris resources.
+    </li>
+
+    <li>Configuration File 'BrdcCorr.bnc'<br>
+      Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain
+      ASCII files. See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-corr"
+        target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-corr</a>
+      for various real-time IGS or EUREF orbit/clock correction products.
+    </li>
+
+    <li>Configuration File 'RinexConcat.bnc'<br>
+      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.
+    </li>
+
+    <li>Configuration File 'RinexQC.bnc'<br>
+      Purpose: Check the quality of a RINEX Version 4 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.
+    </li>
+
+    <li>Configuration File 'RTK.bnc'<br>
+      Purpose: Feed a serial 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.
+    </li>
+
+    <li>Configuration File 'FeedEngine.bnc'<br>
+      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.
+    </li>
+
+    <li>Configuration File 'PPP.bnc'<br>
+      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.
+      More detailed PPP results are saved in the PPP logfile.
+    </li>
+
+    <li>Configuration File 'PPPNet.bnc'<br>
+      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.
+      Detailed PPP Results for the two stations are saved in PPP logfiles.
+    </li>
+
+    <li>Configuration File 'PPPQuickStart.bnc'<br>
+      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.
+    </li>
+
+    <li>Configuration File 'PPPPostProc.bnc'<br>
+      Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX
+      Version 3 Observation and Navigation files and a Broadcast Correction file.
+      Optionally, an Ionosphere file containing VTEC informations can be used. If such
+      a file is not specified, VTEC informations from the Broadcast Corrections file
+      are used. PPP processing options are set to support the Quick-Start mode.
+      The output is saved in a specific post processing logfile and contains
+      coordinates derived over time following the implemented PPP filter algorithm.
+    </li>
+
+    <li>Configuration File 'PPPOsm.bnc'<br>
+      Purpose: Track BNC's point positioning solutions using OpenStreetMap as background.
+      BNC reads a RINEX Observation file and a RINEX Navigation file to carry out
+      a 'Standard Point Positioning' solution in post processing mode.
+      Although 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 OSM maps.
+    </li>
+
+    <li>Configuration File 'PPPGalHAS.bnc'<br>
+      Purpose: Precise Point Positioning in Quick-Start mode with SSR corrections
+      from the Galileo HAS Internet Data Distribution (IDD) interface with observations
+      of a static receiver with quite precisely known position.
+      Because the Galileo HAS provides Code Biases and corrections for satellite orbits
+      and clocks for GPS and Galileo, the configuration uses GPS and Galileo
+      navigation data only.
+      Access to the Galileo HAS Internet Data Distribution is available by registration:
+      <a href="https://www.gsc-europa.eu/galileo/services/galileo-high-accuracy-service-has/internet-data-distribution-registration-form"
+        target="_blank">https://www.gsc-europa.eu/galileo/services/galileo-high-accuracy-service-has/internet-data-distribution-registration-form</a>
+
+      Purpose: Single Point Positioning in Quick-Start mode from observations of a
+      static receiver with quite precisely known position. The configuration uses
+      Galileo observations only and a Broadcast Ephemeris stream.
+    </li>
+
+    <li>Configuration File 'SaveSp3.bnc'<br>
+      Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast
+      Correction stream. The Broadcast Correction stream is formally introduced in
+      BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX
+      file because SP3 file content should be referred to CoM..
+    </li>
+
+    <li>Configuration File 'Sp3ETRF2000PPP.bnc'<br>
+      Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream
+      carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is
+      formally introduced in BNC's 'Combine Corrections' table. The configuration
+      leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in
+      addition observations from a reference station at precisely known ETRF2000
+      position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000
+      reference coordinate.
+    </li>
+
+    <li>Configuration File 'Upload.bnc'<br>
+      Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip
+      Broadcaster. For that the configuration reads precise orbits and clocks in
+      RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts
+      the orbits and clocks into Broadcast Corrections and encodes them to
+      IGS-SSR messages to finally upload them to an Ntrip Broadcaster. The
+      Broadcast Correction stream is referred to satellite Antenna Phase Center (APC)
+      and reference system IGS20. Orbits are saved on disk in SP3 format and clocks
+      are saved in Clock RINEX format.
+    </li>
+
+    <li>Configuration File 'Combi.bnc'<br>
+      Purpose: Pull 2 streams carrying Broadcast Corrections, and Satellite Code Biases
+      together with Broadcast Ephemeris from an Ntrip Broadcaster
+      to produce a combined Broadcast Correction stream.
+      BNC encodes the combination product in IGS-SSR messages and uploads them to
+      an Ntrip Broadcaster. The Broadcast Correction stream is referred to
+      satellite Antenna Phase Center (APC) and not to satellite Center of
+      Mass (CoM). Its reference system is IGS20. Orbits are saved in SP3 format
+      (referred to CoM) and clocks in Clock RINEX format.
+    </li>
+
+    <li>Configuration File 'CombiPPP.bnc'<br>
+      Purpose: This configuration equals the 'Combi.bnc' configuration. However, the
+      combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
+      solutions based on observations from a static reference station with known
+      precise coordinates. This allows a continuous quality check of the combination
+      product through observing coordinate displacements.
+    </li>
+
+    <li>Configuration File 'UploadEph.bnc'<br>
+      Purpose: Pull a number of streams from reference stations to get the
+      contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3
+      format and uploaded for the purpose of providing a Broadcast Ephemeris stream
+      with an update rate of 5 seconds.
+    </li>
+
+    <li>Configuration File 'UploadRaw.bnc'<br>
+      Purpose: Forward the stream contents of the incoming stream BCEP00BKG0
+      from products.igs-ip.net to another caster.
+    </li>
+
+    <li>Configuration File 'CompareSp3.bnc'<br>
+      Purpose: Compare two SP3 files to calculate RMS values for orbit and clock
+      differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this
+      comparison. Comparison results are saved in a logfile.
+    </li>
+
+    <li>Configuration File 'Empty.bnc'<br>
+      Purpose: Provide an empty example configuration file for BNC which only
+      contains the default settings.
+    </li>
+
+    <li value="29"> Configuration File '29_PPPAR_CNES.bnc'<br>
+      Purpose: Precise Point Positioning with ambiguity resolution using an raw input file.
+      Call: bnc --conf 29_PPPAR_CNES.bnc --file WTZR_CNES_20251117.raw
+      The configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
+      and a stream with SSR Corrections enabling PPP-AR. Positions are saved in the logfile.
+      More detailed PPP results are saved in the PPP logfile.
+
+    <li value="30"> Configuration File '30_PPPAR_WHU.bnc'<br>
+      Purpose: Precise Point Positioning with ambiguity resolution using an raw input file.
+      Call: bnc --conf 30_PPPAR_WHU.bnc --file WTZR_WHU_20251129.raw
+      The configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
+      and a stream with SSR Corrections enabling PPP-AR. Positions are saved in the logfile.
+      More detailed PPP results are saved in the PPP logfile.
+    </li>
+
+  </ol>
+  <b>(B) Working with Command Line configuration options</b><br><br>
+  The following configuration examples make use of BNC's 'Command Line Interface' (CLI). Configuration options are
+  exclusively specified via command line. No configuration file is used. Examples are provided as shell scripts
+  for a Linux system. They call BNC in 'no window' batch mode (command line option -nw). The scripts expect
+  'Example_Configs' to be the current working directory.
+  </li>
+
+  <ol start="23">
+    <li>Shell Script 'RinexQC.sh'<br>
+      Purpose: Equals configuration file example 'RinexQC.bnc', checks the quality of
+      a RINEX Version 4 file by means of a multipath analysis. The platform offscreen
+      is used while producing plot files in PNG format. BNC is offline.
+      All results are saved on disk.
+    </li>
+
+    <li>Shell Script 'RinexConcat.sh'<br>
+      Purpose: Equals configuration file example 'RinexConcat.bnc', concatenates
+      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. BNC is
+      offline.
+    </li>
+
+    <li>Shell Script 'RinexEph.sh'<br>
+      Purpose: Equals configuration file example 'RinexEph.bnc', converts 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 4 Navigation
+      files. BNC runs online until it's terminated after 10 seconds.
+      See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-eph" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-eph</a>
+      for further real-time Broadcast Ephemeris resources.
+    </li>
+
+    <li>Shell Script 'ScanLate.sh'<br>
+      Purpose: Scan an observation stream for contained RTCM message types, print
+      observation latencies. The output is saved in a logfile. Latencies are
+      reported every 10 seconds. BNC runs online until it's terminated after 20
+      seconds.
+    </li>
+
+    <li>Shell Script 'RinexObs.sh'<br>
+      Purpose: Equals configuration file example 'RinexObs.bnc', converts RTCM
+      streams to RINEX Observation files. The configuration pulls streams from two
+      Ntrip Broadcasters using Ntrip Version 2 to generate 15min 1Hz RINEX Version 4
+      Observation files.
+      See <a href="https://igs.bkg.bund.de/ntrip/#rtcm-obs" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-obs</a>
+      for observation stream resources. BNC runs online until it's terminated after 30
+      seconds.
+    </li>
+  </ol>
+
+  <b>(C) Command Line configuration options overwriting Configuration File options</b><br><br>
+  For specific applications you may like to use your own set of standard configuration options from a configuration file
+  and update some of its content via command line. When using a configuration file together with command line
+  configuration options in one BNC call, the command line configuration options will always overrule options contained
+  in the configuration file.
+
+  <ol start="28">
+    <li>Shell Script 'CompareSp3.sh'<br>
+      Purpose: Equals configuration file example 'CompareSp3.bnc', compares two SP3
+      files to calculate RMS values for orbit and clock differences. However, instead
+      of excluding GPS satellite G05 and GLONASS satellite R18 from the comparison as
+      specified in 'CompareSp3.bnc', GPS satellite G06 and all GLONASS satellites are
+      excluded via command line option. BNC runs offline. Comparison results are saved
+      in a logfile.
+    </li>
+  </ol>
+  </p>
+
+  <p>
+  <h4 id="introLimit">1.7 Limitations</h4>
+  </p>
+  <ul>
+    <li>
+      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.
+    </li>
+
+    <li>
+      Using RTCM Version 3 to produce RINEX files, BNC will properly handle most message types. However, when handling
+      message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX.
+      All values will be stored modulo 299792.458 (speed of light).
+    </li>
+    <li>
+      Using RTCM Version 2, BNC will only handle message types 18 and 19 or 20 and 21 together with position and the
+      antenna offset information carried in types 3 and 22. Note that processing carrier phase corrections and
+      pseudo-range corrections contained in message types 20 and 21 needs access to Broadcast Ephemeris. Hence, whenever
+      dealing with message types 20 and 21, make sure that Broadcast Ephemeris become available for BNC through also
+      retrieving at least one RTCM Version 3 stream carrying message types 1019 (GPS ephemeris) and 1020 (GLONASS
+      ephemeris).
+    </li>
+    <li>
+      BNC's 'Get Table' function only shows the STR records of a source-table. You can use an Internet browser to
+      download the full source-table content of any Ntrip Broadcaster by simply entering its URL in the form of
+      <u>http://host:port</u>. Data field number 8 in the NET records may provide information about where to register
+      for an Ntrip Broadcaster account.
+    </li>
+    <li>
+      EUREF as well as IGS adhere to an open data policy. Streams are made available through Ntrip Broadcasters at
+      <a href="http://euref-ip.net/home" target="_blank">http://euref-ip.net/home</a>,
+      <a href="http://igs-ip.net/home" target="_blank">http://igs-ip.net/home</a> and
+      <a href="http://products.igs-ip.net/home" target="_blank">http://products.igs-ip.net/home</a>
+      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.
+    </li>
+    <li>
+      Once BNC has been started, many of its configuration options cannot be changed as long as it is stopped. See
+      chapter 'Reread Configuration' for on-the-fly configuration exceptions.
+    </li>
+    <li>
+      Drag and drop of configuration files is currently not supported on Mac OS X. On such system you have to start BNC
+      via command line.
+    </li>
+  </ul>
+
+  <p>
+  <h4 id="introLBack">Looking Back</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    To cope with an increasing number of transmitting GNSS reference stations, the Federal Agency for Cartography and
+    Geodesy (BKG)
+    together with the Informatik Centrum Dortmund (ICD) in Germany developed a streaming protocol for satellite
+    navigation data called
+    'Networked Transport of RTCM via Internet Protocol' (Ntrip). The protocol was built on top of the HTTP standard and
+    included the
+    provision of meta data describing the stream content. Any stream could now be globally transmitted over just one IP
+    port: HTTP port 80.
+    Stream availability and content details became part of the transport protocol. The concept was first published in
+    2003
+    (Weber and Honkala 2004, Weber et al. 2005a) and was based on three software components, namely an NtripServer
+    pushing data from
+    a reference station to an NtripCaster and an NtripClient pulling data from the stream splitting caster to support a
+    rover receiver.
+    (Note that from a socket-programmers perspective NtripServer and NtripClient both act as clients; only the
+    NtripCaster operates as socket-server.)
+    Ntrip could essentially benefit from Internet Radio developments. It was the ICECAST multimedia server, which
+    provided the bases
+    for BKG's 'Professional Ntrip Broadcaster' with software published first in 2003 and of course again as Open Source
+    under GPL.
+  </p>
+  <p>
+    For BKG as a governmental agency, making Ntrip an Open Industry Standard has been an objective from the very
+    beginning.
+    The 'Radio Technical Commission for Maritime Services' (RTCM) accepted 'Ntrip Version 1' in 2004 as 'RTCM
+    Recommended Standard' (Weber et al. 2005b).
+    Nowadays there is almost no geodetic GNSS receiver which does not come with integrated NtripClient and NtripServer
+    functionality as part of the firmware.
+    Hundreds of NtripCaster implementations are operated world-wide for highly accurate satellite navigation through RTK
+    networks.
+    Thousands of reference stations upload observations via NtripServer to central computing facilities for any kind of
+    NtripClient application.
+    In 2011 'Ntrip Version 2' was released (RTCM SC-104 2011) which cleared and fixed some design problems and HTTP
+    protocol violations.
+    It also supports TCP/IP via SSL and adds optional communication over RTSP/RTP and UDP.
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Adding real-time Precise Point Positioning (PPP) support to BNC began in 2010 as an important completion in view of
+    developing an
+    Open RTCM Standard for that. According to the State Space Representation (SSR) model, new Version 3 messages are
+    proposed to provide e.g.
+    satellite orbit and clock corrections and ionospheric corrections as well as biases for code and phase data.
+    The ultimate goal for SSR standardization is to reach centimeter level accuracy within seconds as an alternative to
+    Network RTK methods
+    such as VRS, FKP, and MAC. Because of interoperability aspects, an Open Standard in this area is of particular
+    interest for clients.
+    Regarding stand-alone PPP in BNC, it is worth mentioning that the program is not and can never be in competition
+    with a receiver
+    manufacturer's proprietary solution. Only software or services that are part of a receiver firmware could have the
+    potential of
+    becoming a thread for commercial interests. However, implementing or not implementing an Open PPP approach in a
+    firmware is and
+    will always remain a manufacturer's decision.
+  </p>
+  <p>
+    Implementing some post processing capability is essential for debugging real-time software in case of problems.
+    So certain real-time options in BNC were complemented to work offline through reading data from files.
+    Moreover, beginning in 2012, the software was extended to support Galileo, BeiDou, and QZSS besides GPS and GLONASS.
+    With that, the Open Source tool BNC could be used for RINEX Version 3 file editing, concatenation and quality
+    checks,
+    a post processing functionality demanded by the IGS Multi-GNSS Experiment and not really covered at that time by
+    UNAVCO's famous TEQC program with its limitation on GPS.
+  </p>
+
+  <p>
+    The well-established, mature codebase is mostly written in C++ language.
+    Its publication under GNU GPL is thought to be well-suited for test, validation and demonstration of new
+    approaches in precise real-time satellite navigation when IP streaming is involved. Commissioned by a
+    German governmental agency, the overall intention has been to push the development of RTCM Recommended Standards
+    to the benefit of IAG institutions and services such as IGS and the interested public in general.
+  </p>
+
+  <p>
+  <h3 id="optsettings">2. Settings Details</h3>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    The following chapters describe how to set BNC program options. They explain the 'Top Menu Bar', the 'Settings
+    Canvas' with the
+    processing options, the content of the 'Streams Canvas' and 'Logging Canvas', and the 'Bottom Menu Bar'.
+  </p>
+
+  <p>
+  <h4 id="topmenu">2.1 Top Menu Bar</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="file">2.1.1 File</h4>
+  </p>
+
+  <p>
+    The 'File' button lets you
+  </p>
+  <ul>
+    <li>Select an appropriate font.<br>
       Use smaller font size if the BNC main window exceeds the size of your screen.</li>
-  <li>Reread and save selected options in configuration file.<br>
+    <li>Reread and save selected options in configuration file.<br>
       When using 'Reread &amp; 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.</li>
-  <li>Quit the BNC program.</li>
-</ul>
-
-
-<p><h4 id="help">2.1.2 Help</h4></p>
-
-<p>
-The 'Help' button provides access to
-</p>
-<ul>
-  <li>Help contents.<br>You may keep the 'Help Contents' window open while configuring BNC.</li>
-  <li>A 'Flow Chart' showing BNC linked to a real-time GNSS network engine such as RTNET.</li>
-  <li>General information about BNC.<br>Close the 'About BNC' window to continue working with BNC.</li>
-</ul>
-
-<p><h4 id="network">2.2 Network</h4></p>
-<p>
-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.
-</p>
-<p><h4 id="proxy">2.2.1 Proxy - Usage in a protected LAN</h4></p>
-<p>
-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.
-Without any entry, BNC will try to use the system proxies.</p>
-<p>
-Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification
-of the local security policy or for the installation of a TCP relay to the Ntrip Broadcaster you need to access.
-If this is not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet.</p>
-
-<p><h4 id="ssl">2.2.2 SSL - Transport Layer Security</h4></p>
-<p>
-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.  </p><p>
-Specify the path to a directory where you save CA certificates on your system.
-BNC creates from *.crt and *.pem files a CA certificate database, which is used by the socket during the handshake phase to validate the peer's certificate. </p>
-<p>
-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:
-<pre><p style="font-family:Monospace">
+    <li>Quit the BNC program.</li>
+  </ul>
+
+
+  <p>
+  <h4 id="help">2.1.2 Help</h4>
+  </p>
+
+  <p>
+    The 'Help' button provides access to
+  </p>
+  <ul>
+    <li>Help contents.<br>You may keep the 'Help Contents' window open while configuring BNC.</li>
+    <li>A 'Flow Chart' showing BNC linked to a real-time GNSS network engine such as RTNET.</li>
+    <li>General information about BNC.<br>Close the 'About BNC' window to continue working with BNC.</li>
+  </ul>
+
+  <p>
+  <h4 id="network">2.2 Network</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+  <h4 id="proxy">2.2.1 Proxy - Usage in a protected LAN</h4>
+  </p>
+  <p>
+    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.
+    Without any entry, BNC will try to use the system proxies.</p>
+  <p>
+    Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an
+    appropriate modification
+    of the local security policy or for the installation of a TCP relay to the Ntrip Broadcaster you need to access.
+    If this is not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to
+    the Internet.</p>
+
+  <p>
+  <h4 id="ssl">2.2.2 SSL - Transport Layer Security</h4>
+  </p>
+  <p>
+    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. </p>
+  <p>
+    Specify the path to a directory where you save CA certificates on your system.
+    BNC creates from *.crt and *.pem files a CA certificate database, which is used by the socket during the handshake
+    phase to validate the peer's certificate. </p>
+  <p>
+    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:
+  <pre><p style="font-family:Monospace">
    SSL Error
    Server Certificate Issued by:
@@ -1387,47 +2572,58 @@
    No certificates could be verified
 </pre>
-</p>
-<p>
-Queries should not be received by a client when a server uses official SSL certificates. </p>
-<p>
-You may also just try communication via SSL to check out whether this is supported by the involved Ntrip Broadcaster.
-Note that SSL communication is usually done over port 443.</p>
-<p>
-Two-sided communication with an Ntrip Broadcaster over SSL requires in addition the exchange of client certificates.
-Specify the full path to the client certificates on your system. The file naming convention for client certificates in BNC is as follows:
-<pre>
+  </p>
+  <p>
+    Queries should not be received by a client when a server uses official SSL certificates. </p>
+  <p>
+    You may also just try communication via SSL to check out whether this is supported by the involved Ntrip
+    Broadcaster.
+    Note that SSL communication is usually done over port 443.</p>
+  <p>
+    Two-sided communication with an Ntrip Broadcaster over SSL requires in addition the exchange of client certificates.
+    Specify the full path to the client certificates on your system. The file naming convention for client certificates
+    in BNC is as follows:
+  <pre>
    &lt;hostname&gt;.&lt;port&gt;.crt for the certificate and
    &lt;hostname&gt;.&lt;port&gt;.key for the private key, where &lt;hostname&gt; is without https://.
 </pre>
-</p>
-<p>
-If available, the client or personal authentication certificate is presented to the peer during the SSL handshake process.
-Password protected key files are not supported.
-Don't try communication via two sided SSL if you are not sure whether this is supported by the involved Ntrip Broadcaster. </p>
-<p>
-Tick 'Ignore SSL authorization errors' if you generally trust the server and do not want to be bothered with this. </p>
-<p><img src="IMG/Figure07.png"width=800/></p>
-<p>Figure 7: BNC's 'Network' panel configured to ignore eventually occurring SSL error messages</p>
-
-<p><h4 id="general">2.3 General</h4></p>
-<p>
-The following defines general settings for BNC's logfile, file handling, reconfiguration on-the-fly, and auto-start.
-</p>
-
-<p><h4 id="genlog">2.3.1 Logfile - optional</h4></p>
-<p>
-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.
-The time stamps within the 'Log' tab are given in UTC. The time stamps within the logfile are given in GPS Time.
-The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a file.
-</p>
-<p>
-The following is an example for the content of a logfile written by BNC when operated in Precise Point Positioning (PPP) mode:
-</p>
-<pre><p style="font-family:Monospace">
+  </p>
+  <p>
+    If available, the client or personal authentication certificate is presented to the peer during the SSL handshake
+    process.
+    Password protected key files are not supported.
+    Don't try communication via two sided SSL if you are not sure whether this is supported by the involved Ntrip
+    Broadcaster. </p>
+  <p>
+    Tick 'Ignore SSL authorization errors' if you generally trust the server and do not want to be bothered with this.
+  </p>
+  <p><img src="IMG/Figure07.png" width=800 /></p>
+  <p>Figure 7: BNC's 'Network' panel configured to ignore eventually occurring SSL error messages</p>
+
+  <p>
+  <h4 id="general">2.3 General</h4>
+  </p>
+  <p>
+    The following defines general settings for BNC's logfile, file handling, reconfiguration on-the-fly, and auto-start.
+  </p>
+
+  <p>
+  <h4 id="genlog">2.3.1 Logfile - optional</h4>
+  </p>
+  <p>
+    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.
+    The time stamps within the 'Log' tab are given in UTC. The time stamps within the logfile are given in GPS Time.
+    The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a
+    file.
+  </p>
+  <p>
+    The following is an example for the content of a logfile written by BNC when operated in Precise Point Positioning
+    (PPP) mode:
+  </p>
+  <pre><p style="font-family:Monospace">
 22-10-04 19:53:57 ========== Start BNC v2.13 (LINUX) ==========
 22-10-04 19:53:57 Panel 'PPP' active
@@ -1450,189 +2646,285 @@
 ...
 </pre>
-</p>
-
-<p><h4 id="genapp">2.3.2 Append Files - optional</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="genconf">2.3.3 Reread Configuration - optional</h4></p>
-<p>
-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.
-</p>
-
-<p>
-Note that following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data:
-</p>
-<p>
-<ul>
-  <li>'mountPoints' to change the selection of streams to be processed, see section 'Streams'</li>
-  <li>'outWait' to change the 'Wait for full obs epoch' option, see section 'Feed Engine'</li>
-  <li>'outSampl' to change the 'Sampling' option, see section 'Feed Engine'</li>
-  <li>'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format</li>
-</ul>
-</p>
-<p>
-</p>
-
-<p><h4 id="genstart">2.3.4 Auto Start - optional</h4></p>
-<p>
-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).
-</p>
-<p>
-See BNC's command line option '-nw' for an auto-start of BNC in 'no window' mode.
-</p>
-
-<p><h4 id="rawout">2.3.5 Raw Output File - optional</h4></p>
-<p>
-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 &amp; Replay functionality) and is not meant for post processing.
-</p>
-<p>
-Data will be saved in blocks in the received format separated by ASCII time stamps like (example):
-<pre>
+  </p>
+
+  <p>
+  <h4 id="genapp">2.3.2 Append Files - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="genconf">2.3.3 Reread Configuration - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+    Note that following configuration options saved on disk can be changed/edited on-the-fly while BNC is already
+    processing data:
+  </p>
+  <p>
+  <ul>
+    <li>'mountPoints' to change the selection of streams to be processed, see section 'Streams'</li>
+    <li>'outWait' to change the 'Wait for full obs epoch' option, see section 'Feed Engine'</li>
+    <li>'outSampl' to change the 'Sampling' option, see section 'Feed Engine'</li>
+    <li>'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format</li>
+  </ul>
+  </p>
+  <p>
+  </p>
+
+  <p>
+  <h4 id="genstart">2.3.4 Auto Start - optional</h4>
+  </p>
+  <p>
+    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).
+  </p>
+  <p>
+    See BNC's command line option '-nw' for an auto-start of BNC in 'no window' mode.
+  </p>
+
+  <p>
+  <h4 id="rawout">2.3.5 Raw Output File - optional</h4>
+  </p>
+  <p>
+    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 &amp; Replay
+    functionality) and is not meant for post processing.
+  </p>
+  <p>
+    Data will be saved in blocks in the received format separated by ASCII time stamps like (example):
+  <pre>
    2022-10-04T20:07:31 WTZR00DEU0 RTCM_3.3 202
 </pre>
-</p>
-<p>
-This example block header tells you that 202 bytes were saved in the data block following this time stamp. The information in this block is encoded in RTCM Version 3 format, comes from mountpoint WTZR00DEU0 and was received at 20:07:31 GPS Time on 2022-10-04. BNC adds its own time stamps in order to allow the reconstruction of a recorded real-time situation.
-</p>
-<p>
-The default value for 'Raw output file' is an empty option field, meaning that BNC will not save all raw data into one single daily file.
-</p>
-
-<p><h4 id="rinex">2.4 RINEX Observations</h4></p>
-<p>
-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, BDS, SBAS, QZSS, and/or NavIC. 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.
-</p>
-<p>
-It is important to understand that converting RTCM streams to RINEX files requires a priori information on observation types
-for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined
-in the Version 2 standard and later reports "0.000" for observations which are not received.
-However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number
-of observation types, which might in principle show up. The solution implemented in BNC is to start with
-RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension' and 'Skeleton Mandatory') and switch to
-a default selection of observation types when such file is not available or does not contain the required information.
-<p>
-Please note that RTCM Version 3 messages 1084 (MSM4) for GLONASS observations do not contain the GLONASS channel numbers.
-These observation messages can only be converted to RINEX when you add messages which include the channel numbers,
-such as the GLONASS ephemeris messages 1020. The GLONASS channel number is available as extended information within MSM5/7 messages.
-</p>
-<p>
-The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from Ntrip Broadcaster
-<a href="http://igs-ip.net:2101" target="_blank">http://igs-ip.net:2101</a>.
-Specifying a decoder string 'ZERO2FILE' would mean to not convert the affected stream but save its content as received.
-On Wed Oct  5 2022 that would result for the Mountpoint 'FFMJ00DEU0' into a file named 'FFMJ00DEU0_221005'.
-</p>
-
-<p><img src="IMG/Figure08.png"width=1000/></p>
-<p>Figure 8: BNC translating incoming RTCM Version 3 Observation streams to 15 min RINEX Version 4 Observation files</p>
-
-<p><h4 id="rnxname">2.4.1 RINEX Filenames</h4></p>
-<p>
-The RINEX filenames generated by BNC depend on the chosen RINEX format.
-The following convention holds in case of RINEX Version 3 and RINEX Version 4 filenames:
-</p>
-
-<table>
-  <tr><td><b>Filename Parameter&nbsp; &nbsp;</b></td><td><b>&nbsp;# Char.</b></td><td><b>&nbsp; Meaning</b></td></tr>
-  <tr><td>Name</td><td>&nbsp; 9</td><td>&nbsp; Site, station and country code</td></tr>
-  <tr><td>S</td><td>&nbsp; 1</td><td>&nbsp; Data source</td></tr>
-  <tr><td>Start Time</td><td>&nbsp; 11</td><td>&nbsp; YYYYDDDHHMM</td></tr>
-  <tr><td>Period</td><td>&nbsp; 3</td><td>&nbsp; File period</td></tr>
-  <tr><td>Obs. Freq.</td><td>&nbsp; 3</td><td>&nbsp; Observation frequency</td></tr>
-  <tr><td>Content</td><td>&nbsp; 2</td><td>&nbsp; Content type</td></tr>
-  <tr><td>Format</td><td>&nbsp; 3</td><td>&nbsp; File format</td></tr>
-  <tr><td>Compression</td><td>&nbsp; 2-3</td><td>&nbsp; Compression method (optional)</td></tr>
-</table>
-
-<p>
-Examples (Figure 8) for Mixed RINEX Version 4 GNSS observation filenames, files containing 15 minutes of data,
-one observation every second, 'MO' standing for 'Mixed Observations':
-</p>
-<pre>
+  </p>
+  <p>
+    This example block header tells you that 202 bytes were saved in the data block following this time stamp. The
+    information in this block is encoded in RTCM Version 3 format, comes from mountpoint WTZR00DEU0 and was received at
+    20:07:31 GPS Time on 2022-10-04. BNC adds its own time stamps in order to allow the reconstruction of a recorded
+    real-time situation.
+  </p>
+  <p>
+    The default value for 'Raw output file' is an empty option field, meaning that BNC will not save all raw data into
+    one single daily file.
+  </p>
+
+  <p>
+  <h4 id="rinex">2.4 RINEX Observations</h4>
+  </p>
+  <p>
+    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, BDS, SBAS, QZSS, and/or NavIC. 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.
+  </p>
+  <p>
+    It is important to understand that converting RTCM streams to RINEX files requires a priori information on
+    observation types
+    for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all
+    observation types defined
+    in the Version 2 standard and later reports "0.000" for observations which are not received.
+    However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because
+    of the huge number
+    of observation types, which might in principle show up. The solution implemented in BNC is to start with
+    RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension' and 'Skeleton
+    Mandatory') and switch to
+    a default selection of observation types when such file is not available or does not contain the required
+    information.
+  <p>
+    Please note that RTCM Version 3 messages 1084 (MSM4) for GLONASS observations do not contain the GLONASS channel
+    numbers.
+    These observation messages can only be converted to RINEX when you add messages which include the channel numbers,
+    such as the GLONASS ephemeris messages 1020. The GLONASS channel number is available as extended information within
+    MSM5/7 messages.
+  </p>
+  <p>
+    The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from Ntrip
+    Broadcaster
+    <a href="http://igs-ip.net:2101" target="_blank">http://igs-ip.net:2101</a>.
+    Specifying a decoder string 'ZERO2FILE' would mean to not convert the affected stream but save its content as
+    received.
+    On Wed Oct 5 2022 that would result for the Mountpoint 'FFMJ00DEU0' into a file named 'FFMJ00DEU0_221005'.
+  </p>
+
+  <p><img src="IMG/Figure08.png" width=1000 /></p>
+  <p>Figure 8: BNC translating incoming RTCM Version 3 Observation streams to 15 min RINEX Version 4 Observation files
+  </p>
+
+  <p>
+  <h4 id="rnxname">2.4.1 RINEX Filenames</h4>
+  </p>
+  <p>
+    The RINEX filenames generated by BNC depend on the chosen RINEX format.
+    The following convention holds in case of RINEX Version 3 and RINEX Version 4 filenames:
+  </p>
+
+  <table>
+    <tr>
+      <td><b>Filename Parameter&nbsp; &nbsp;</b></td>
+      <td><b>&nbsp;# Char.</b></td>
+      <td><b>&nbsp; Meaning</b></td>
+    </tr>
+    <tr>
+      <td>Name</td>
+      <td>&nbsp; 9</td>
+      <td>&nbsp; Site, station and country code</td>
+    </tr>
+    <tr>
+      <td>S</td>
+      <td>&nbsp; 1</td>
+      <td>&nbsp; Data source</td>
+    </tr>
+    <tr>
+      <td>Start Time</td>
+      <td>&nbsp; 11</td>
+      <td>&nbsp; YYYYDDDHHMM</td>
+    </tr>
+    <tr>
+      <td>Period</td>
+      <td>&nbsp; 3</td>
+      <td>&nbsp; File period</td>
+    </tr>
+    <tr>
+      <td>Obs. Freq.</td>
+      <td>&nbsp; 3</td>
+      <td>&nbsp; Observation frequency</td>
+    </tr>
+    <tr>
+      <td>Content</td>
+      <td>&nbsp; 2</td>
+      <td>&nbsp; Content type</td>
+    </tr>
+    <tr>
+      <td>Format</td>
+      <td>&nbsp; 3</td>
+      <td>&nbsp; File format</td>
+    </tr>
+    <tr>
+      <td>Compression</td>
+      <td>&nbsp; 2-3</td>
+      <td>&nbsp; Compression method (optional)</td>
+    </tr>
+  </table>
+
+  <p>
+    Examples (Figure 8) for Mixed RINEX Version 4 GNSS observation filenames, files containing 15 minutes of data,
+    one observation every second, 'MO' standing for 'Mixed Observations':
+  </p>
+  <pre>
    FFMJ00DEU_S_20222781400_15M_01S_MO.rnx
    CUT000AUS_S_20222781400_15M_01S_MO.rnx
 </pre>
 
-<p>
-Note that filename details are produced from the stream's mountpoint as well as corresponding BNC settings and meta data from the Ntrip Broadcaster source-table.
-</p>
-
-<p>
-RINEX Version 2 filenames are derived from the first 4 characters of the corresponding stream's mountpoint (4-Char Station ID).
-For example, data from mountpoints FFMJ00DEU0 and CUT000AUS0 will have 15-minutes RINEX Observation files named
-</p>
-<pre>
+  <p>
+    Note that filename details are produced from the stream's mountpoint as well as corresponding BNC settings and meta
+    data from the Ntrip Broadcaster source-table.
+  </p>
+
+  <p>
+    RINEX Version 2 filenames are derived from the first 4 characters of the corresponding stream's mountpoint (4-Char
+    Station ID).
+    For example, data from mountpoints FFMJ00DEU0 and CUT000AUS0 will have 15-minutes RINEX Observation files named
+  </p>
+  <pre>
    FFMJ278O00.22O
    CUT0278O00.22O
 </pre>
 
-<p>
-The RINEX version 2 filneme convention can be summrized as follows:
-<pre>
+  <p>
+    The RINEX version 2 filneme convention can be summrized as follows:
+  <pre>
    {4-Char-Station-ID}{ddd}{h}{mm}.{yy}O
 </pre>
-where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block,
-'mm' is the starting minute within the hour. and 'yy' is the year.
-</p>
-
-<p><h4 id="rnxdir">2.4.2 Directory - optional</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="rnxinterval">2.4.3 File Interval - mandatory if 'Directory' is set</h4></p>
-<p>
-Select the length of the RINEX Observation file to be generated. The default value is 1 day.
-</p>
-
-<p><h4 id="rnxsample">2.4.4 Sampling - mandatory if 'Directory' is set </h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="rnxskl">2.4.5 Skeleton Extension - optional</h4></p>
-<p>
-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 <a href="https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl" target="_blank">https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl</a>
-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.
-</p>
-<p>
-Sometimes public RINEX header skeleton files are not available, their content is not up to date, or you need to put additional/optional
-records in the RINEX header. For that, BNC allows using personal skeleton files that contain the header records you would like to include.
-You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog.
-A file in the RINEX Observations 'Directory' with a 'Skeleton extension' suffix is interpreted by BNC as a personal RINEX header skeleton file
-for the corresponding stream.
-</p>
-<p>
-When producing RINEX Observation files from mountpoints like 'BRUX00BEL0' or 'WTZR_RTCM3', the following skeleton filenames would be accepted
-</p>
-<pre>
+  where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block,
+  'mm' is the starting minute within the hour. and 'yy' is the year.
+  </p>
+
+  <p>
+  <h4 id="rnxdir">2.4.2 Directory - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="rnxinterval">2.4.3 File Interval - mandatory if 'Directory' is set</h4>
+  </p>
+  <p>
+    Select the length of the RINEX Observation file to be generated. The default value is 1 day.
+  </p>
+
+  <p>
+  <h4 id="rnxsample">2.4.4 Sampling - mandatory if 'Directory' is set </h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="rnxskl">2.4.5 Skeleton Extension - optional</h4>
+  </p>
+  <p>
+    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 <a href="https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl"
+      target="_blank">https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl</a>
+    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.
+  </p>
+  <p>
+    Sometimes public RINEX header skeleton files are not available, their content is not up to date, or you need to put
+    additional/optional
+    records in the RINEX header. For that, BNC allows using personal skeleton files that contain the header records you
+    would like to include.
+    You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog.
+    A file in the RINEX Observations 'Directory' with a 'Skeleton extension' suffix is interpreted by BNC as a personal
+    RINEX header skeleton file
+    for the corresponding stream.
+  </p>
+  <p>
+    When producing RINEX Observation files from mountpoints like 'BRUX00BEL0' or 'WTZR_RTCM3', the following skeleton
+    filenames would be accepted
+  </p>
+  <pre>
    BRUX00BEL.skl (9 char corresponding to RINEX version 3,4)
    WTZR_RTCM.skl (9 char corresponding to RINEX version 3,4)
 </pre>
-<p>
-if 'Skeleton extension' is set to 'skl'. As an alternative the basename is tried to use with lower cases as well.
-</p>
-<p>
-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.
-<ul>
-  <li>Personal skeletons should contain a complete first header record of type 'RINEX VERSION / TYPE'</li>
-  <li>They should then contain an empty header record of type 'PGM / RUN BY / DATE' which will be completed by BNC and included in the RINEX file header.</li>
-  <li>They should further contain complete header records of type
+  <p>
+    if 'Skeleton extension' is set to 'skl'. As an alternative the basename is tried to use with lower cases as well.
+  </p>
+  <p>
+    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.
+  <ul>
+    <li>Personal skeletons should contain a complete first header record of type 'RINEX VERSION / TYPE'</li>
+    <li>They should then contain an empty header record of type 'PGM / RUN BY / DATE' which will be completed by BNC and
+      included in the RINEX file header.</li>
+    <li>They should further contain complete header records of type
       <br> &nbsp; 'MARKER NAME'
       <br> &nbsp; 'OBSERVER / AGENCY'
@@ -1642,22 +2934,25 @@
       <br> &nbsp; 'ANTENNA: DELTA H/E/N'
       <br> &nbsp; 'WAVELENGTH FACT L1/2 for RINEX Version 2 files
-      <br> &nbsp; 'SYS / # / OBS TYPES' for RINEX Version 3 files, will be ignored in Version 2 files</li>
-  <li>They may contain any other optional complete header record as defined in the RINEX documentation.</li>
-  <li>They should also contain an empty header record of type '# / TYPES OF OBSERV'. It will be used in RINEX Version 2 files and ignored in Version 3 files.
-  <li>BNC will include these lines in the final RINEX file header together with an additional 'COMMENT'-line describing the source of the stream.</li>
-  <li>Personal skeletons  must not contain a header record of type 'TIME OF FIRST OBS'</li>
-  <li>They should finally contain an empty last header record of type 'END OF HEADER'</li>
-
-
-</ul>
-<p>
-If neither a public nor a personal RINEX header skeleton file is available for BNC, a default header will be used.
-</p>
-<p>
-The following is a skeleton example for a RINEX file:
-</p>
-
-
-<pre><p style="font-family:Monospace">
+      <br> &nbsp; 'SYS / # / OBS TYPES' for RINEX Version 3 files, will be ignored in Version 2 files
+    </li>
+    <li>They may contain any other optional complete header record as defined in the RINEX documentation.</li>
+    <li>They should also contain an empty header record of type '# / TYPES OF OBSERV'. It will be used in RINEX Version
+      2 files and ignored in Version 3 files.
+    <li>BNC will include these lines in the final RINEX file header together with an additional 'COMMENT'-line
+      describing the source of the stream.</li>
+    <li>Personal skeletons must not contain a header record of type 'TIME OF FIRST OBS'</li>
+    <li>They should finally contain an empty last header record of type 'END OF HEADER'</li>
+
+
+  </ul>
+  <p>
+    If neither a public nor a personal RINEX header skeleton file is available for BNC, a default header will be used.
+  </p>
+  <p>
+    The following is a skeleton example for a RINEX file:
+  </p>
+
+
+  <pre><p style="font-family:Monospace">
                     OBSERVATION DATA    M                   RINEX VERSION / TYPE
 PORTIONS OF THIS HEADER GENERATED BY BKG AT 05-Oct-22 04:51 COMMENT
@@ -1684,281 +2979,616 @@
 
 
-<p><h4 id="sklMandat">2.4.6 Skeleton Mandatory - optional</h4></p>
-<p>
-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.
-</p>
-<p>Note that a skeleton file contains RINEX header information such as receiver and antenna types. In case of stream conversion to RINEX Version 3, a skeleton file should also contain information on potentially available observation types. A missing skeleton file will force BNC to only save a default set of RINEX 3 observation types.
-</p>
-<p>
-A skeleton file carrying only RINEX Version 2 style observation types (2-character codes, e.g. 'C1', 'L1') cannot supply the tracking-mode
-attribute a RINEX Version 3/4 header needs, so BNC will not use such a skeleton when producing Version 3/4 files. It is treated the same
-way as a missing skeleton: with 'Skeleton mandatory' ticked, no RINEX file is produced for the affected stream; otherwise BNC falls back
-to a default set of RINEX 3/4 observation types. Conversely, a skeleton carrying RINEX Version 3/4 style observation types
-(3-character codes) is always usable when producing RINEX Version 2 files, because the Version 3/4 codes can be unambiguously mapped
-down to Version 2 codes (see section 'Version 2').
-</p>
-
-<p><h4 id="sklDir">2.4.7 Skeleton Directory - optional</h4></p>
-<p>
-Here you can specify the path, where local skeleton files are located. If no directory is specified, the path is assumed to where the RINEX Observation files will stored.
-</p>
-
-
-<p><h4 id="rnxscript">2.4.8 Script - optional</h4></p>
-<p>
-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).
-</p>
-<p>
-The triggering event for calling the script or batch file is the end of a RINEX Observation file 'Interval'. If that is overridden by a stream outage, the triggering event is the stream reconnection.
-</p>
-<p>
-As an alternative to initiating file uploads through BNC, you may like to call an upload script or batch file through your crontable or Task Scheduler (independent from BNC) once every one or two minutes after the end of each RINEX file 'Interval'.
-</p>
-
-<p><h4 id="rnxvers3_4">2.4.9 Version 3 and 4 - optional</h4></p>
-<p>
-Currently, the default format for RINEX Observation files is RINEX Version 3.
-RINEX version 4 can be chosen as well. The resulting observation files are backward compatible to RINEX version 3.
-</p>
-<p>
-Note, that it is possible to force an RTCM Version 2 stream to be saved in RINEX Version 3 file format.
-However, this is not recommended, because such stream cannot be precisely mapped to RINEX Version 3
-as the required information on tracking modes (observation attributes) is not part of RTCM Version 2.
-</p>
-<p>
-For the same reason, a RINEX header skeleton file that only carries RINEX Version 2 style observation types
-(2-character codes) cannot be used to build a RINEX Version 3/4 header. BNC ignores such a skeleton for that
-purpose and falls back to a default set of RINEX 3/4 observation types instead, see section 'Skeleton Mandatory'.
-</p>
-
-<p><h4 id="rnxvers2">2.4.10 Version 2 - optional</h4></p>
-<p>
-GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3 or 4.
-These attributes describe the tracking mode or channel when generating the observation signals.
-Capital letters specifying signal generation attributes are e.g. A, B, C, D, E, I, L, M, N, P, Q, S, W, X, Y, or Z, see RINEX Version 3 and 4 documentation.
-Nevertheless, there are two applications where the program can be setup to produce data files in RINEX Version 2.11 format:
-<ol type="1">
-<li>When saving the content of incoming observation streams in RINEX Version 2 files as described in this section.</li>
-<li>When editing or concatenating RINEX version 3/4 files to save them in Version 2 format, see section on 'RINEX Editing & QC'.</li>
-</ol>
-Select RINEX 'Version 2' if you would like to save RTCM Version 3 observation streams in RINEX Version 2 format.
-As the Version 2 format ignores signal generation attributes, BNC is forced to somehow map RINEX Version 3/4 to RINEX Version 2
-although this cannot be done in one-to-one correspondence.
-Hence we introduce a 'Signal priority' list of attributes (characters, forming a string) for mapping Version 3/4 to Version 2.
-</p>
-<p>
-Signal priorities can be specified as equal for all systems, as system specific or as system and frequency specific. For example:
-</p>
-<ul>
-<li>'CWPX_?' (General signal priorities valid for all GNSS)</li>
-<li>'I:ABCX' (System specific signal priorities for NavIC)</li>
-<li>'G:12&PWCSLX G:5&IQX R:12&PC R:3&IQX' (System and frequency specific signal priorities)</li>
-</ul>
-
-<p>
-The default 'Signal priority' list is defined as follows:
-<ul>
- <li>'G:12&PWCSLX G:5&IQX R:12&PC R:3&IQX R:46&ABX E:16&BCXZ E:578&IQX J:1&SLXCZ J:26&SLX J:5&IQX C:267&IQX C:18&DPX I:ABCX S:1&C S:5&IQX'</li>
-</ul>
-
-As an example the 'Signal priority' of 'CWPX_?' is explained in more detail:
-<ul>
-<li>Signals with attribute 'C' enjoy the highest priority. If such a RINEX Version 3/4 observation becomes available,
-    it is presented as RINEX Version 2 observation if that is the format you wish to see. Observations with other attributes are being ignored.</li>
-<li>If no signal with 'C' attribute is available but we have an observation with 'W' attribute, BNC presents that one as RINEX Version 2 observation
-    and ignores all observations with other attributes. The same applies mutatis mutandis to observations with P and X attributes.</li>
-<li>If no signal with 'C', 'W', 'P', or 'X' attribute is available but a signal with undefined generation attribute (underscore character, '_') exists,
-    BNC presents that one as RINEX Version 2 observation. Note that observation attributes should actually always be available in RINEX Version 3/4.
-    Hence the underscore character makes only sense in a few very special cases.</li>
-<li>If no signal with 'C', 'W', 'P', 'X', or '_' generation attribute exists then the question mark '?' tells BNC to present the first of any other
-    appearing signal as RINEX Version 2 observation.</li>
-</ul>
-</p>
-
-<p>
-You may like to specify your own 'Signal priority' string(s) for producing RINEX Version 2 files.
-</p>
-
-<p><h4 id="ephemeris">2.5 RINEX Ephemeris</h4></p>
-<p>
-Broadcast Ephemeris can be saved in RINEX Navigation files when received e.g. via RTCM Version 3 message types.</p>
-<p>
-In RINEX version 4 the following navigation message types are defined but not all of them are currently supported in RTCM version 3 messages:
-</p>
-<table>
-<tr><td>Navigation 		</td><td>Description							</td><td>Constellation  		</td><td>RTCM </td></tr>
-<tr><td>Message Type	</td><td>										</td><td>and Signal 			</td><td>Message Type</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>LNAV</td><td>			GPS Legacy navigation message			</td><td>GPS  L1 C/A           	</td><td>1019</td></tr>
-<tr><td>	</td><td>			QZSS Legacy navigation message 			</td><td>QZSS L1 C/A or L1 C/B 	</td><td>1044</td></tr>
-<tr><td>	</td><td>			NavIC Legacy navigation message 		</td><td>NavIC L5/S SPS        	</td><td>1041</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>FDMA</td><td>			GLONASS Legacy FDMA navigation message	</td><td>GLO L1 C/A			 	</td><td>1020</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>FNAV</td><td>			Galileo Free      	navigation message 	</td><td>GAL E5a        	    </td><td>1045</td></tr>
-<tr><td>INAV</td><td>			Galileo Integrity 	navigation message 	</td><td>GAL E1, E5b        	</td><td>1046</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>D1	</td><td>			BeiDou-2/3 MEO/IGSO navigation message 	</td><td>BDS B1I, B2I, B3I  	</td><td>1042</td></tr>
-<tr><td>D2	</td><td>			BeiDou-2/3 GEO      navigation message 	</td><td>BDS B1I, B2I, B3I 		</td><td>1042</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>SBAS</td><td>			SBAS      navigation message 			</td><td>SBAS L1            	</td><td>1043</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>CNAV</td><td>			GPS  CNAV navigation message  			</td><td>GPS  L2C, L5  		  	</td><td>	 </td></tr>
-<tr><td>	</td><td>			QZSS CNAV navigation message  			</td><td>QZSS L2C, L5   		</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>CNV1</td><td>			BeiDou-3 CNAV-1 navigation message      </td><td>BDS-3 B1C              </td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>CNV2</td><td>			GPS      CNAV-2 navigation message      </td><td>GPS L1C                </td><td>	 </td></tr>
-<tr><td>	</td><td>			QZSS     CNAV-2 navigation message      </td><td>QZSS L1C               </td><td>	 </td></tr>
-<tr><td>	</td><td>			BeiDou-3 CNAV-2 navigation message      </td><td>BDS-3 B2a              </td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>CNV3</td><td>			BeiDou-3 CNAV-3 navigation message    	</td><td>BDS-3 B2b	          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>L1NV</td><td>		    NavIC L1 navigation messages			</td><td>NavIC L1            	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>L1OC</td><td>		    GLONASS L1 CDMA navigation message		</td><td>GLO L1 OC	          	</td><td>	 </td></tr>
-<tr><td>L3OC</td><td>		    GLONASS L3 CDMA navigation message		</td><td>GLO L3 OC	          	</td><td>	 </td></tr>
-</table>
- <p>
-The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'.
-</p>
-<p>
-Regarding RINEX Version 3/4 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, BDS, and NavIC gathered in one Navigation file.
-</p>
-<p>
-The following is an example for a RINEX Version 3/4 Navigation filename. The file contains one hour's data. 'MN' stands for 'Multi Constellation Navigation' data.
-</p>
-<pre>
+  <p>
+  <h4 id="sklMandat">2.4.6 Skeleton Mandatory - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>Note that a skeleton file contains RINEX header information such as receiver and antenna types. In case of stream
+    conversion to RINEX Version 3, a skeleton file should also contain information on potentially available observation
+    types. A missing skeleton file will force BNC to only save a default set of RINEX 3 observation types.
+  </p>
+  <p>
+    A skeleton file carrying only RINEX Version 2 style observation types (2-character codes, e.g. 'C1', 'L1') cannot
+    supply the tracking-mode
+    attribute a RINEX Version 3/4 header needs, so BNC will not use such a skeleton when producing Version 3/4 files. It
+    is treated the same
+    way as a missing skeleton: with 'Skeleton mandatory' ticked, no RINEX file is produced for the affected stream;
+    otherwise BNC falls back
+    to a default set of RINEX 3/4 observation types. Conversely, a skeleton carrying RINEX Version 3/4 style observation
+    types
+    (3-character codes) is always usable when producing RINEX Version 2 files, because the Version 3/4 codes can be
+    unambiguously mapped
+    down to Version 2 codes (see section 'Version 2').
+  </p>
+
+  <p>
+  <h4 id="sklDir">2.4.7 Skeleton Directory - optional</h4>
+  </p>
+  <p>
+    Here you can specify the path, where local skeleton files are located. If no directory is specified, the path is
+    assumed to where the RINEX Observation files will stored.
+  </p>
+
+
+  <p>
+  <h4 id="rnxscript">2.4.8 Script - optional</h4>
+  </p>
+  <p>
+    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).
+  </p>
+  <p>
+    The triggering event for calling the script or batch file is the end of a RINEX Observation file 'Interval'. If that
+    is overridden by a stream outage, the triggering event is the stream reconnection.
+  </p>
+  <p>
+    As an alternative to initiating file uploads through BNC, you may like to call an upload script or batch file
+    through your crontable or Task Scheduler (independent from BNC) once every one or two minutes after the end of each
+    RINEX file 'Interval'.
+  </p>
+
+  <p>
+  <h4 id="rnxvers3_4">2.4.9 Version 3 and 4 - optional</h4>
+  </p>
+  <p>
+    Currently, the default format for RINEX Observation files is RINEX Version 3.
+    RINEX version 4 can be chosen as well. The resulting observation files are backward compatible to RINEX version 3.
+  </p>
+  <p>
+    Note, that it is possible to force an RTCM Version 2 stream to be saved in RINEX Version 3 file format.
+    However, this is not recommended, because such stream cannot be precisely mapped to RINEX Version 3
+    as the required information on tracking modes (observation attributes) is not part of RTCM Version 2.
+  </p>
+  <p>
+    For the same reason, a RINEX header skeleton file that only carries RINEX Version 2 style observation types
+    (2-character codes) cannot be used to build a RINEX Version 3/4 header. BNC ignores such a skeleton for that
+    purpose and falls back to a default set of RINEX 3/4 observation types instead, see section 'Skeleton Mandatory'.
+  </p>
+
+  <p>
+  <h4 id="rnxvers2">2.4.10 Version 2 - optional</h4>
+  </p>
+  <p>
+    GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3
+    or 4.
+    These attributes describe the tracking mode or channel when generating the observation signals.
+    Capital letters specifying signal generation attributes are e.g. A, B, C, D, E, I, L, M, N, P, Q, S, W, X, Y, or Z,
+    see RINEX Version 3 and 4 documentation.
+    Nevertheless, there are two applications where the program can be setup to produce data files in RINEX Version 2.11
+    format:
+  <ol type="1">
+    <li>When saving the content of incoming observation streams in RINEX Version 2 files as described in this section.
+    </li>
+    <li>When editing or concatenating RINEX version 3/4 files to save them in Version 2 format, see section on 'RINEX
+      Editing & QC'.</li>
+  </ol>
+  Select RINEX 'Version 2' if you would like to save RTCM Version 3 observation streams in RINEX Version 2 format.
+  As the Version 2 format ignores signal generation attributes, BNC is forced to somehow map RINEX Version 3/4 to RINEX
+  Version 2
+  although this cannot be done in one-to-one correspondence.
+  Hence we introduce a 'Signal priority' list of attributes (characters, forming a string) for mapping Version 3/4 to
+  Version 2.
+  </p>
+  <p>
+    Signal priorities can be specified as equal for all systems, as system specific or as system and frequency specific.
+    For example:
+  </p>
+  <ul>
+    <li>'CWPX_?' (General signal priorities valid for all GNSS)</li>
+    <li>'I:ABCX' (System specific signal priorities for NavIC)</li>
+    <li>'G:12&PWCSLX G:5&IQX R:12&PC R:3&IQX' (System and frequency specific signal priorities)</li>
+  </ul>
+
+  <p>
+    The default 'Signal priority' list is defined as follows:
+  <ul>
+    <li>'G:12&PWCSLX G:5&IQX R:12&PC R:3&IQX R:46&ABX E:16&BCXZ E:578&IQX J:1&SLXCZ J:26&SLX J:5&IQX C:267&IQX C:18&DPX
+      I:ABCX S:1&C S:5&IQX'</li>
+  </ul>
+
+  As an example the 'Signal priority' of 'CWPX_?' is explained in more detail:
+  <ul>
+    <li>Signals with attribute 'C' enjoy the highest priority. If such a RINEX Version 3/4 observation becomes
+      available,
+      it is presented as RINEX Version 2 observation if that is the format you wish to see. Observations with other
+      attributes are being ignored.</li>
+    <li>If no signal with 'C' attribute is available but we have an observation with 'W' attribute, BNC presents that
+      one as RINEX Version 2 observation
+      and ignores all observations with other attributes. The same applies mutatis mutandis to observations with P and X
+      attributes.</li>
+    <li>If no signal with 'C', 'W', 'P', or 'X' attribute is available but a signal with undefined generation attribute
+      (underscore character, '_') exists,
+      BNC presents that one as RINEX Version 2 observation. Note that observation attributes should actually always be
+      available in RINEX Version 3/4.
+      Hence the underscore character makes only sense in a few very special cases.</li>
+    <li>If no signal with 'C', 'W', 'P', 'X', or '_' generation attribute exists then the question mark '?' tells BNC to
+      present the first of any other
+      appearing signal as RINEX Version 2 observation.</li>
+  </ul>
+  </p>
+
+  <p>
+    You may like to specify your own 'Signal priority' string(s) for producing RINEX Version 2 files.
+  </p>
+
+  <p>
+  <h4 id="ephemeris">2.5 RINEX Ephemeris</h4>
+  </p>
+  <p>
+    Broadcast Ephemeris can be saved in RINEX Navigation files when received e.g. via RTCM Version 3 message types.</p>
+  <p>
+    In RINEX version 4 the following navigation message types are defined but not all of them are currently supported in
+    RTCM version 3 messages:
+  </p>
+  <table>
+    <tr>
+      <td>Navigation </td>
+      <td>Description </td>
+      <td>Constellation </td>
+      <td>RTCM </td>
+    </tr>
+    <tr>
+      <td>Message Type </td>
+      <td> </td>
+      <td>and Signal </td>
+      <td>Message Type</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>LNAV</td>
+      <td> GPS Legacy navigation message </td>
+      <td>GPS L1 C/A </td>
+      <td>1019</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> QZSS Legacy navigation message </td>
+      <td>QZSS L1 C/A or L1 C/B </td>
+      <td>1044</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> NavIC Legacy navigation message </td>
+      <td>NavIC L5/S SPS </td>
+      <td>1041</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>FDMA</td>
+      <td> GLONASS Legacy FDMA navigation message </td>
+      <td>GLO L1 C/A </td>
+      <td>1020</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>FNAV</td>
+      <td> Galileo Free navigation message </td>
+      <td>GAL E5a </td>
+      <td>1045</td>
+    </tr>
+    <tr>
+      <td>INAV</td>
+      <td> Galileo Integrity navigation message </td>
+      <td>GAL E1, E5b </td>
+      <td>1046</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>D1 </td>
+      <td> BeiDou-2/3 MEO/IGSO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td>D2 </td>
+      <td> BeiDou-2/3 GEO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>SBAS</td>
+      <td> SBAS navigation message </td>
+      <td>SBAS L1 </td>
+      <td>1043</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>CNAV</td>
+      <td> GPS CNAV navigation message </td>
+      <td>GPS L2C, L5 </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> QZSS CNAV navigation message </td>
+      <td>QZSS L2C, L5 </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>CNV1</td>
+      <td> BeiDou-3 CNAV-1 navigation message </td>
+      <td>BDS-3 B1C </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>CNV2</td>
+      <td> GPS CNAV-2 navigation message </td>
+      <td>GPS L1C </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> QZSS CNAV-2 navigation message </td>
+      <td>QZSS L1C </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> BeiDou-3 CNAV-2 navigation message </td>
+      <td>BDS-3 B2a </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>CNV3</td>
+      <td> BeiDou-3 CNAV-3 navigation message </td>
+      <td>BDS-3 B2b </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>L1NV</td>
+      <td> NavIC L1 navigation messages </td>
+      <td>NavIC L1 </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>L1OC</td>
+      <td> GLONASS L1 CDMA navigation message </td>
+      <td>GLO L1 OC </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>L3OC</td>
+      <td> GLONASS L3 CDMA navigation message </td>
+      <td>GLO L3 OC </td>
+      <td> </td>
+    </tr>
+  </table>
+  <p>
+    The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters
+    are 'BRDC'.
+  </p>
+  <p>
+    Regarding RINEX Version 3/4 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, BDS, and NavIC
+    gathered in one Navigation file.
+  </p>
+  <p>
+    The following is an example for a RINEX Version 3/4 Navigation filename. The file contains one hour's data. 'MN'
+    stands for 'Multi Constellation Navigation' data.
+  </p>
+  <pre>
    BRDC00WRD_S_20222791000_01H_MN.rnx
 </pre>
 
 
-<p>
-For RINEX Version 2 Navigation files the last character is 'N' or 'G' for GPS or GLONASS ephemeris in two separate files.
-</p>
-
-<p>
-Note further that BNC will ignore incorrect or outdated Broadcast Ephemeris data, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile.
-</p>
-
-<p><h4 id="ephdir">2.5.1 Directory - optional</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="ephint">2.5.2 Interval - mandatory if 'Directory' is set</h4></p>
-<p>
-Select the length of RINEX Navigation files. The default value is '1 day'.
-</p>
-
-<p><h4 id="ephport">2.5.3 Port - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-The source code for BNC comes with an example Perl script 'test_tcpip_client.pl' that allows you to read BNC's ephemeris ASCII output from the IP port.
-</p>
-
-<p><h4 id="ephvers">2.5.4 Version - optional</h4></p>
-<p>
-Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 3, saving the ephemeris data in RINEX Version 3.05.
-Select 'Version 2' if you want to save the ephemeris data in RINEX Version 2.11 format.
-Select 'Version 4' if you want to save the ephemeris data in RINEX Version 4.x format.
-</p>
-<p>
-Note that the here choosen Version concerns the Broadcast Ephemeris output through IP port as well.
-</p>
-
-<p><h4 id="reqc">2.6 RINEX Editing & QC</h4></p>
-<p>
-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 <b>T</b>ranslation, this functionality in BNC covers
-<ul>
-  <li>File <b>E</b>diting and concatenation</li>
-  <li>File <b>Q</b>uality <b>C</b>heck</li>
+  <p>
+    For RINEX Version 2 Navigation files the last character is 'N' or 'G' for GPS or GLONASS ephemeris in two separate
+    files.
+  </p>
+
+  <p>
+    Note further that BNC will ignore incorrect or outdated Broadcast Ephemeris data, leaving a note 'WRONG EPHEMERIS'
+    or 'OUTDATED EPHEMERIS' in the logfile.
+  </p>
+
+  <p>
+  <h4 id="ephdir">2.5.1 Directory - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="ephint">2.5.2 Interval - mandatory if 'Directory' is set</h4>
+  </p>
+  <p>
+    Select the length of RINEX Navigation files. The default value is '1 day'.
+  </p>
+
+  <p>
+  <h4 id="ephport">2.5.3 Port - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    The source code for BNC comes with an example Perl script 'test_tcpip_client.pl' that allows you to read BNC's
+    ephemeris ASCII output from the IP port.
+  </p>
+
+  <p>
+  <h4 id="ephvers">2.5.4 Version - optional</h4>
+  </p>
+  <p>
+    Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 3, saving the ephemeris
+    data in RINEX Version 3.05.
+    Select 'Version 2' if you want to save the ephemeris data in RINEX Version 2.11 format.
+    Select 'Version 4' if you want to save the ephemeris data in RINEX Version 4.x format.
+  </p>
+  <p>
+    Note that the here choosen Version concerns the Broadcast Ephemeris output through IP port as well.
+  </p>
+
+  <p>
+  <h4 id="reqc">2.6 RINEX Editing & QC</h4>
+  </p>
+  <p>
+    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 <b>T</b>ranslation, this
+    functionality in BNC covers
   <ul>
-    <li>Multipath analysis sky plots</li>
-    <li>Signal-to-noise ratio sky plots</li>
-    <li>Satellite availability plots</li>
-    <li>Satellite elevation plots</li>
-    <li>PDOP plots</li>
+    <li>File <b>E</b>diting and concatenation</li>
+    <li>File <b>Q</b>uality <b>C</b>heck</li>
+    <ul>
+      <li>Multipath analysis sky plots</li>
+      <li>Signal-to-noise ratio sky plots</li>
+      <li>Satellite availability plots</li>
+      <li>Satellite elevation plots</li>
+      <li>PDOP plots</li>
+    </ul>
   </ul>
-</ul>
-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.
-
-<p><h4 id="reqcact">2.6.1 Action - optional</h4></p>
-<p>Select an action. Options are 'Edit/Concatenate' and 'Analyze'.
-<ul>
-<li>Select 'Edit/Concatenate' if you want to edit RINEX file content according to options specified under 'Set Edit Options' or if you want
-    to concatenate several RINEX files.</li>
-<li>Select 'Analyze' if you are interested in a quality check of your RINEX file content.</li>
-</ul>
-
-<p><h4 id="reqcinp">2.6.2 Input Files - mandatory</h4></p>
-<p>
-Specify full path to input RINEX Observation file(s), and<br>
-specify full path to input RINEX Navigation file(s).
-</p>
-<p>
-In case of a Quality Check the following type of Broadcast navigation messages is used per individulal GNSS:
-</p>
-<table>
-<tr><td>Navigation 		</td><td>Description							</td><td>Constellation  		</td><td>RTCM </td></tr>
-<tr><td>Message Type	</td><td>										</td><td>and Signal 			</td><td>Message Type</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>LNAV</td><td>			GPS Legacy navigation message			</td><td>GPS  L1 C/A           	</td><td>1019</td></tr>
-<tr><td>	</td><td>			QZSS Legacy navigation message 			</td><td>QZSS L1 C/A or L1 C/B 	</td><td>1044</td></tr>
-<tr><td>	</td><td>			NavIC Legacy navigation message 		</td><td>NavIC L5/S SPS        	</td><td>1041</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>FDMA</td><td>			GLONASS Legacy FDMA navigation message	</td><td>GLO L1 C/A			 	</td><td>1020</td></tr>
-<tr><td>	</td><td>			from M-satellites						</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>INAV</td><td>			Galileo Integrity 	navigation message 	</td><td>GAL E1, E5b        	</td><td>1046</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>D1	</td><td>			BeiDou-2/3 MEO/IGSO navigation message 	</td><td>BDS B1I, B2I, B3I  	</td><td>1042</td></tr>
-<tr><td>D2	</td><td>			BeiDou-2/3 GEO      navigation message 	</td><td>BDS B1I, B2I, B3I 		</td><td>1042</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>SBAS</td><td>			SBAS      navigation message 			</td><td>SBAS L1            	</td><td>1043</td></tr>
-</table>
-<p>
-When specifying several input files, BNC will concatenate their contents. In case of RINEX Observation input files
-with different observation type header records, BNC will output only one set of adjusted observation type records in
-the RINEX header which fits to the whole file content.
-</p>
-
-<p><h4 id="reqcout">2.6.3 Output Files - optional if 'Action' is set to 'Edit/Concatenate'</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="reqcminele">2.6.4 Minimum Elevation - optional</h4></p>
-<p>
-Select a minimum for satellite elevation angles. Observations from a satellite not reaching or exceeding this minimum
-elevation will be excluded, no matter whether 'Action' is set to 'Edit/Concatenate' or 'Analyze'. Determining a satellite's
-elevation requires specifying a RINEX Navigation input file, see section 'Input Files'.
-</p>
-<p>
-Default is '0 deg', meaning that no elevation mask is applied and all observations are used regardless of the involved satellite's elevation angle.
-</p>
-
-<p><h4 id="reqclog">2.6.5 Logfile - optional</h4></p>
-<p>
-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.
-</p>
-
-<p>
-Note that logfiles from analyzing RINEX files may become quite large. Hence, BNC provides an option 'Summary only'
-to limit logfile content to some essential information in case 'Action' is set to 'Analyze'.
-The following is an example for a RINEX quality check analysis logfile:
-</p>
-<pre><p style="font-family:Monospace">
+  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.
+
+  <p>
+  <h4 id="reqcact">2.6.1 Action - optional</h4>
+  </p>
+  <p>Select an action. Options are 'Edit/Concatenate' and 'Analyze'.
+  <ul>
+    <li>Select 'Edit/Concatenate' if you want to edit RINEX file content according to options specified under 'Set Edit
+      Options' or if you want
+      to concatenate several RINEX files.</li>
+    <li>Select 'Analyze' if you are interested in a quality check of your RINEX file content.</li>
+  </ul>
+
+  <p>
+  <h4 id="reqcinp">2.6.2 Input Files - mandatory</h4>
+  </p>
+  <p>
+    Specify full path to input RINEX Observation file(s), and<br>
+    specify full path to input RINEX Navigation file(s).
+  </p>
+  <p>
+    In case of a Quality Check the following type of Broadcast navigation messages is used per individulal GNSS:
+  </p>
+  <table>
+    <tr>
+      <td>Navigation </td>
+      <td>Description </td>
+      <td>Constellation </td>
+      <td>RTCM </td>
+    </tr>
+    <tr>
+      <td>Message Type </td>
+      <td> </td>
+      <td>and Signal </td>
+      <td>Message Type</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>LNAV</td>
+      <td> GPS Legacy navigation message </td>
+      <td>GPS L1 C/A </td>
+      <td>1019</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> QZSS Legacy navigation message </td>
+      <td>QZSS L1 C/A or L1 C/B </td>
+      <td>1044</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> NavIC Legacy navigation message </td>
+      <td>NavIC L5/S SPS </td>
+      <td>1041</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>FDMA</td>
+      <td> GLONASS Legacy FDMA navigation message </td>
+      <td>GLO L1 C/A </td>
+      <td>1020</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> from M-satellites </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>INAV</td>
+      <td> Galileo Integrity navigation message </td>
+      <td>GAL E1, E5b </td>
+      <td>1046</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>D1 </td>
+      <td> BeiDou-2/3 MEO/IGSO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td>D2 </td>
+      <td> BeiDou-2/3 GEO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>SBAS</td>
+      <td> SBAS navigation message </td>
+      <td>SBAS L1 </td>
+      <td>1043</td>
+    </tr>
+  </table>
+  <p>
+    When specifying several input files, BNC will concatenate their contents. In case of RINEX Observation input files
+    with different observation type header records, BNC will output only one set of adjusted observation type records in
+    the RINEX header which fits to the whole file content.
+  </p>
+
+  <p>
+  <h4 id="reqcout">2.6.3 Output Files - optional if 'Action' is set to 'Edit/Concatenate'</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="reqcminele">2.6.4 Minimum Elevation - optional</h4>
+  </p>
+  <p>
+    Select a minimum for satellite elevation angles. Observations from a satellite not reaching or exceeding this
+    minimum
+    elevation will be excluded, no matter whether 'Action' is set to 'Edit/Concatenate' or 'Analyze'. Determining a
+    satellite's
+    elevation requires specifying a RINEX Navigation input file, see section 'Input Files'.
+  </p>
+  <p>
+    Default is '0 deg', meaning that no elevation mask is applied and all observations are used regardless of the
+    involved satellite's elevation angle.
+  </p>
+
+  <p>
+  <h4 id="reqclog">2.6.5 Logfile - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+    Note that logfiles from analyzing RINEX files may become quite large. Hence, BNC provides an option 'Summary only'
+    to limit logfile content to some essential information in case 'Action' is set to 'Analyze'.
+    The following is an example for a RINEX quality check analysis logfile:
+  </p>
+  <pre><p style="font-family:Monospace">
 QC Format Version  : 1.1
 
@@ -2206,205 +3836,239 @@
 </pre>
 
-<p>
-<b>The epoch-specific output </b>
-</p>
-
-<p>
-Each 'Epoch Record' contains 9 parameters. Example:
-</p>
-<pre>
+  <p>
+    <b>The epoch-specific output </b>
+  </p>
+
+  <p>
+    Each 'Epoch Record' contains 9 parameters. Example:
+  </p>
+  <pre>
 > 2022 06 21 00 00 30.0000000 49  0.5
 </pre>
-<p>
-Their meaning is as follows:
-</p>
-<ul>
-  <li>Special character '&#62;' is the first character in each 'Epoch Record' (as we have it in RINEX Version 3/4)</li>
-  <li>Year, GPS time</li>
-  <li>Month, GPS time</li>
-  <li>Day, GPS time</li>
-  <li>Hour, GPS time</li>
-  <li>Minute, GPS time</li>
-  <li>Second, GPS time</li>
-  <li>Number of satellites</li>
-  <li>PDOP value</li>
-</ul>
-<p>
-Each of the 'Satellite Records' in such an epoch block carries information for one specific satellite. Example:
-</p>
-<pre>
+  <p>
+    Their meaning is as follows:
+  </p>
+  <ul>
+    <li>Special character '&#62;' is the first character in each 'Epoch Record' (as we have it in RINEX Version 3/4)
+    </li>
+    <li>Year, GPS time</li>
+    <li>Month, GPS time</li>
+    <li>Day, GPS time</li>
+    <li>Hour, GPS time</li>
+    <li>Minute, GPS time</li>
+    <li>Second, GPS time</li>
+    <li>Number of satellites</li>
+    <li>PDOP value</li>
+  </ul>
+  <p>
+    Each of the 'Satellite Records' in such an epoch block carries information for one specific satellite. Example:
+  </p>
+  <pre>
 E05  37.64  160.08  10  L1C .. 46.5  C1C  . 0.13  L6C .. 49.7  C6C  . 0.00  L5Q .. 47.0  C5Q  . 0.12  L7Q .. 47.5  C7Q  . 0.10  L8Q .. 50.3  C8Q  . 0.00
 </pre>
-<p>
-A satellite-specific line starts with:
-</p>
-<ul>
-<li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
-<li>Elevation [&deg;]</li>
-<li>Azimuth [&deg;]</li>
-<li>Number of observations types</li>
-</ul>
-<p>
-An observation type block, for example
-</p>
-<pre>
+  <p>
+    A satellite-specific line starts with:
+  </p>
+  <ul>
+    <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
+    <li>Elevation [&deg;]</li>
+    <li>Azimuth [&deg;]</li>
+    <li>Number of observations types</li>
+  </ul>
+  <p>
+    An observation type block, for example
+  </p>
+  <pre>
 L1C .. 46.5
 </pre>
-<p>
-or
-</p>
-<pre>
+  <p>
+    or
+  </p>
+  <pre>
 C1C  . 0.13
 </pre>
-<p>
-contains the RINEX Version 3/4 observation code and
-</p>
-<ul>
-  <li>for a carrier phase observation: </li>
+  <p>
+    contains the RINEX Version 3/4 observation code and
+  </p>
   <ul>
-  <li>two characters,  where 's' means cycle slip, 'g' means gap and '.' means OK </li>
-  <li>  signal-to-noise ratio SNR [dBHz] </li>
+    <li>for a carrier phase observation: </li>
+    <ul>
+      <li>two characters, where 's' means cycle slip, 'g' means gap and '.' means OK </li>
+      <li> signal-to-noise ratio SNR [dBHz] </li>
+    </ul>
+    <li>for a code observation: </li>
+    <ul>
+      <li> two characters: the first one (for slips) is empty, 'g' means gap and '.' means OK </li>
+      <li> multipath standard deviation [m] </li>
+    </ul>
   </ul>
-  <li>for a code observation: </li>
+  <p>
+    With respect to the summary note, that in addition to cycle slips recorded in the RINEX 'file',
+    cycle slips identified by BNC are reported as 'found'.
+  </p>
+
+  <p>
+  <h4 id="reqcplots">2.6.6 Plots for Signals - mandatory if 'Action' is set to 'Analyze'</h4>
+  </p>
+  <p>
+    BNC can produce plots for multipath, signal-to-noise ratio, satellite availability, satellite elevation, and PDOP
+    values.
+    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
   <ul>
-  <li> two characters: the first one (for slips) is empty, 'g' means gap and '.' means OK </li>
-  <li> multipath standard deviation [m] </li>
+    <li> the navigation system (C = BDS, E = Galileo, G = GPS, I = NavIC, J = QZSS, R = GLONASS, S = SBAS),</li>
+    <li> the band/frequency, and </li>
+    <li> the attribute as defined in RINEX Version 3/4.</li>
   </ul>
-</ul>
-<p>
-With respect to the summary note, that in addition to cycle slips recorded in the RINEX 'file',
-cycle slips identified by BNC are reported as 'found'.
-</p>
-
-<p><h4 id="reqcplots">2.6.6 Plots for Signals - mandatory if 'Action' is set to 'Analyze'</h4></p>
-<p>
-BNC can produce plots for multipath, signal-to-noise ratio, satellite availability, satellite elevation, and PDOP values.
-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
-<ul>
-<li> the navigation system (C = BDS, E = Galileo, G = GPS, I = NavIC, J = QZSS, R = GLONASS, S = SBAS),</li>
-<li> the band/frequency, and </li>
-<li> the attribute as defined in RINEX Version 3/4.</li>
-</ul>
-Specifications for band/frequency and attribute must be separated by ampersand character '&'.
-<p>
-Specifications for each navigation system must be separated by blank character ' '.
-</p>
-<p>
-Default is 'G:1&2&5 R:1&2&3 E:1&7 C:2&6 J:1&2 I:5&9 S:1&5'. Specifying an empty option string would be overruled by this default.
-</p>
-Examples for the 'Plots for signals' option:
-<ul>
-<li>G:1&2&5 E:1&7 (Plots will be based on GPS observations on 1st, 2nd and 5th frequency as well as on Galileo observations on 1st and 7th frequency.)</li>
-<li>G:1C&5X (Plots will be based on GPS observations on the 1st frequency in 'C' tracking mode andand on the 5th frequency in 'X' tracking mode.)</li>
-<li>C:2I&6I (Plots will be based on BDS observations on the 2th and on the 6th frequency; both in 'I' tracking mode.)</li>
-</ul>
-<p>
-An example configuration with plot results can be seen below.
-</p>
-<p><img src="IMG/Figure09.png"width=1000/></p>
-<p>Figure 9: Example for creating RINEX quality check analysis graphics output with BNC</p>
-
-<p><img src="IMG/Figure10.png"width=1000/></p>
-<p>Figure 10: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC</p>
-
-<p><img src="IMG/Figure11.png"width=1000/></p>
-<p>Figure 11: Sky plot examples for multipath, part of RINEX quality check analysis with BNC</p>
-
-<p><img src="IMG/Figure12.png"width=1000/></p>
-<p>Figure 12: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC</p>
-
-<p><h4 id="reqcdir">2.6.7 Directory for Plots - optional if 'Action' is set to 'Analyze'</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="reqcedit">2.6.8 Set Edit Options - mandatory if 'Action' is set to 'Edit/Concatenate'</h4></p>
-<p>
-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/4 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.
-</p>
-
-<p>
-A note on converting RINEX Version 3 to RINEX Version 2 and vice versa:
-</p>
-
-<ul>
-  <li>The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting <b>RINEX Version 3/4 to Version 2</b>
-      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)
+  Specifications for band/frequency and attribute must be separated by ampersand character '&'.
+  <p>
+    Specifications for each navigation system must be separated by blank character ' '.
+  </p>
+  <p>
+    Default is 'G:1&2&5 R:1&2&3 E:1&7 C:2&6 J:1&2 I:5&9 S:1&5'. Specifying an empty option string would be overruled by
+    this default.
+  </p>
+  Examples for the 'Plots for signals' option:
+  <ul>
+    <li>G:1&2&5 E:1&7 (Plots will be based on GPS observations on 1st, 2nd and 5th frequency as well as on Galileo
+      observations on 1st and 7th frequency.)</li>
+    <li>G:1C&5X (Plots will be based on GPS observations on the 1st frequency in 'C' tracking mode andand on the 5th
+      frequency in 'X' tracking mode.)</li>
+    <li>C:2I&6I (Plots will be based on BDS observations on the 2th and on the 6th frequency; both in 'I' tracking
+      mode.)</li>
+  </ul>
+  <p>
+    An example configuration with plot results can be seen below.
+  </p>
+  <p><img src="IMG/Figure09.png" width=1000 /></p>
+  <p>Figure 9: Example for creating RINEX quality check analysis graphics output with BNC</p>
+
+  <p><img src="IMG/Figure10.png" width=1000 /></p>
+  <p>Figure 10: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check
+    analysis with BNC</p>
+
+  <p><img src="IMG/Figure11.png" width=1000 /></p>
+  <p>Figure 11: Sky plot examples for multipath, part of RINEX quality check analysis with BNC</p>
+
+  <p><img src="IMG/Figure12.png" width=1000 /></p>
+  <p>Figure 12: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC</p>
+
+  <p>
+  <h4 id="reqcdir">2.6.7 Directory for Plots - optional if 'Action' is set to 'Analyze'</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="reqcedit">2.6.8 Set Edit Options - mandatory if 'Action' is set to 'Edit/Concatenate'</h4>
+  </p>
+  <p>
+    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/4 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.
+  </p>
+
+  <p>
+    A note on converting RINEX Version 3 to RINEX Version 2 and vice versa:
+  </p>
+
+  <ul>
+    <li>The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting <b>RINEX Version 3/4
+        to Version 2</b>
+      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/4 to Version 2, see details in section 'RINEX Observations/Version 2'.</li>
-  <li>Converting <b>RINEX Version 2 to Version 3/4</b> Observation files  is not recommended because the attribute in the observation code
-      (last character out of the 3-character) is left blank if unknown. This is a compromise, which is not in accordance with the
+    <li>Converting <b>RINEX Version 2 to Version 3/4</b> Observation files is not recommended because the attribute in
+      the observation code
+      (last character out of the 3-character) is left blank if unknown. This is a compromise, which is not in accordance
+      with the
       RINEX Version 3/4 documentation.</li>
-</ul>
-
-<p>
-Optionally you may specify a 'RUN BY' string to be included in the emerging new RINEX file header. Default is an empty option field,
-meaning the operator's ID is automatically used as 'RUN BY' string.
-</p>
-<p>
-You can specify a list of observation codes in field 'Use Obs. Types' to limit the output file content to specific observation codes.
-GNSS system characters in that list are followed by a colon and a 2- or 3-Character observation code.
-A 2-Character observation code would mean that all available tracking modes of the affected observation type and frequency
-will be accepted as part of the RINEX output file. Observation codes are separated by a blank character.
-Default is an empty option field, meaning that any input observation code will become part of the RINEX output file.
-</p>
-
-<p>
-Specifying comment line text to be added to the emerging new RINEX file header is another option.
-Any introduction of a newline through '\n' in this enforces the beginning of a further comment line.
-Comment lines will be added to the header immediately after the 'PGM / RUN BY / DATE' record.
-Default is an empty option field, meaning that no additional comment line will be added to the RINEX header.
-</p>
-
-<p>
-If you specify a 'New' but no 'Old' marker/antenna/receiver name, the corresponding data field in the emerging new RINEX Observation file
-will be filled accordingly. If you in addition specify an 'Old' marker/antenna/receiver name, the corresponding data field
-in the emerging new RINEX Observation file will only be filled accordingly where 'Old' specifications match existing file content.
-</p>
-
-<p><img src="IMG/Figure13.png"width=500/></p>
-<p>Figure 13: Example for BNC's 'RINEX Editing Options' window</p>
-
-<p><img src="IMG/Figure14.png"width=1000/></p>
-<p>Figure 14: Example for RINEX file concatenation with BNC</p>
-
-<p><h4 id="reqccommand">2.6.9 Command Line, No Window - optional</h4></p>
-<p>
-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:
-</p>
-<pre>
+  </ul>
+
+  <p>
+    Optionally you may specify a 'RUN BY' string to be included in the emerging new RINEX file header. Default is an
+    empty option field,
+    meaning the operator's ID is automatically used as 'RUN BY' string.
+  </p>
+  <p>
+    You can specify a list of observation codes in field 'Use Obs. Types' to limit the output file content to specific
+    observation codes.
+    GNSS system characters in that list are followed by a colon and a 2- or 3-Character observation code.
+    A 2-Character observation code would mean that all available tracking modes of the affected observation type and
+    frequency
+    will be accepted as part of the RINEX output file. Observation codes are separated by a blank character.
+    Default is an empty option field, meaning that any input observation code will become part of the RINEX output file.
+  </p>
+
+  <p>
+    Specifying comment line text to be added to the emerging new RINEX file header is another option.
+    Any introduction of a newline through '\n' in this enforces the beginning of a further comment line.
+    Comment lines will be added to the header immediately after the 'PGM / RUN BY / DATE' record.
+    Default is an empty option field, meaning that no additional comment line will be added to the RINEX header.
+  </p>
+
+  <p>
+    If you specify a 'New' but no 'Old' marker/antenna/receiver name, the corresponding data field in the emerging new
+    RINEX Observation file
+    will be filled accordingly. If you in addition specify an 'Old' marker/antenna/receiver name, the corresponding data
+    field
+    in the emerging new RINEX Observation file will only be filled accordingly where 'Old' specifications match existing
+    file content.
+  </p>
+
+  <p><img src="IMG/Figure13.png" width=500 /></p>
+  <p>Figure 13: Example for BNC's 'RINEX Editing Options' window</p>
+
+  <p><img src="IMG/Figure14.png" width=1000 /></p>
+  <p>Figure 14: Example for RINEX file concatenation with BNC</p>
+
+  <p>
+  <h4 id="reqccommand">2.6.9 Command Line, No Window - optional</h4>
+  </p>
+  <p>
+    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:
+  </p>
+  <pre>
    --key &lt;keyName&gt; &lt;keyValue&gt;
 </pre>
-<p>
-Parameter &lt;keyName&gt; stands for the name of an option contained in the configuration file
-and &lt;keyValue&gt; stands for the value you want to assign to it.
-This functionality may be helpful in the 'RINEX Editing & QC' context when running BNC on a routine basis
-for maintaining a RINEX file archive.
-</p>
-<p>
-You may use asterisk '*' and/or question mark '?' wildcard characters as shown with the following globbing command line option
-to specify a selection of files in the working directory:
-</p>
-<p><pre>
+  <p>
+    Parameter &lt;keyName&gt; stands for the name of an option contained in the configuration file
+    and &lt;keyValue&gt; stands for the value you want to assign to it.
+    This functionality may be helpful in the 'RINEX Editing & QC' context when running BNC on a routine basis
+    for maintaining a RINEX file archive.
+  </p>
+  <p>
+    You may use asterisk '*' and/or question mark '?' wildcard characters as shown with the following globbing command
+    line option
+    to specify a selection of files in the working directory:
+  </p>
+  <p>
+  <pre>
    --key reqcObsFile "Input/BRUX00BEL_S_2021125*_15M_01S_MO.rnx"
-</pre><p>
-or:
-</p>
-<p><pre>
+</pre>
+  <p>
+    or:
+  </p>
+  <p>
+  <pre>
    --key reqcObsFile Input/BRUX00BEL_S_2021125\*_15M_01S_MO.rnx
-</pre><p>
-The following example for a Linux platform calls BNC in 'no window' mode with a local configuration file 'rnx.conf'
-for concatenating four 15min RINEX files from station BRUX00BEL residing in the 'Input' directory to produce an hourly RINEX Version 3 file
-with 30 seconds sampling interval:
-<pre><p style="font-family:Monospace">
+</pre>
+  <p>
+    The following example for a Linux platform calls BNC in 'no window' mode with a local configuration file 'rnx.conf'
+    for concatenating four 15min RINEX files from station BRUX00BEL residing in the 'Input' directory to produce an
+    hourly RINEX Version 3 file
+    with 30 seconds sampling interval:
+  <pre><p style="font-family:Monospace">
   /home/user/bnc --nw --conf rnx.conf \
        --key reqcAction Edit/Concatenate \
@@ -2416,10 +4080,11 @@
        --key reqcOutObsFile Output/BRUX00BEL_S_20211251100_01H_01S_MO.rnx
 </p></pre>
-<p>
-The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode
-and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no configuration options
-previously saved on disc are used:
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode
+    and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no
+    configuration options
+    previously saved on disc are used:
+  </p>
+  <pre><p style="font-family:Monospace">
   /home/user/bnc --nw --conf /dev/null -display :1 --platform offscreen \
        --key reqcAction Analyze \
@@ -2430,8 +4095,8 @@
        --key reqcPlotDir Output 2>/dev/null
 </p></pre>
-<p>
-<p>The following Linux command line produces the same RINEX QC plots in interactive autoStart mode:
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+  <p>The following Linux command line produces the same RINEX QC plots in interactive autoStart mode:
+  </p>
+  <pre><p style="font-family:Monospace">
   /home/user/bnc --conf /dev/null \
        --key reqcAction Analyze \
@@ -2442,96 +4107,248 @@
        --key startTab 4 --key autoStart 2
 </p></pre>
-<p>
-The following is a list of available key names for '<u>R</u>INEX <u>E</u>diting & <u>QC</u>' (short: REQC, pronounced 'rek') options
-and their meaning, cf. section 'Configuration Examples':
-</p>
-<table>
-<tr></tr>
-<tr><td><b>Keyname</b></td><td></td><td><b>Meaning</b></td></tr>
-<tr><td>reqcAction</td><td></td><td>RINEX Editing & QC action</td></tr>
-<tr><td>reqcObsFile</td><td></td><td>RINEX Observation input file(s)</td></tr>
-<tr><td>reqcNavFile</td><td></td><td>RINEX Navigation input files(s)</td></tr>
-<tr><td>reqcOutObsFile</td><td></td><td>RINEX Observation output file</td></tr>
-<tr><td>reqcOutNavFile</td><td></td><td>RINEX Navigation output file</td></tr>
-<tr><td>reqcMinEle</td><td></td><td>Minimum Elevation</td></tr>
-<tr><td>reqcOutLogFile</td><td></td><td>Logfile</td></tr>
-<tr><td>reqcLogSummaryOnly</td><td></td><td>Summary of Logfile</td></tr>
-<tr><td>reqcSkyPlotSignals</td><td></td><td>Plots for signals</td></tr>
-<tr><td>reqcPlotDir</td><td></td><td>RINEX QC plot directory</td></tr>
-<tr><td>reqcRnxVersion</td><td></td><td>RINEX version of emerging new file</td></tr>
-<tr><td>reqcSampling</td><td></td><td>Sampling interval of emerging new RINEX file</td></tr>
-<tr><td>reqcV2Priority</td><td></td><td>Version 2 Signal Priority</td></tr>
-<tr><td>reqcStartDateTime</td><td></td><td>Begin of emerging new RINEX file</td></tr>
-<tr><td>reqcEndDateTime</td><td></td><td>End of emerging new RINEX file</td></tr>
-<tr><td>reqcRunBy</td><td></td><td>Operator name</td></tr>
-<tr><td>reqcUseObsTypes</td><td></td><td>GNSS systems and observation types</td></tr>
-<tr><td>reqcComment</td><td></td><td>Additional comment lines</td></tr>
-<tr><td>reqcOldMarkerName</td><td></td><td>Old marker name</td></tr>
-<tr><td>reqcNewMarkerName</td><td></td><td>New marker name</td></tr>
-<tr><td>reqcOldAntennaName</td><td></td><td>Old antenna name</td></tr>
-<tr><td>reqcNewAntennaName</td><td></td><td>New antenna name</td></tr>
-<tr><td>reqcOldAntennaNumber</td><td></td><td>Old antenna number</td></tr>
-<tr><td>reqcNewAntennaNumber</td><td></td><td>New antenna number</td></tr>
-<tr><td>reqcOldAntennadN</td><td></td><td>Old component of north eccentricity</td></tr>
-<tr><td>reqcOldAntennadE</td><td></td><td>Old component of east eccentricity</td></tr>
-<tr><td>reqcOldAntennadU</td><td></td><td>Old component of up eccentricity</td></tr>
-<tr><td>reqcNewAntennadN</td><td></td><td>New component of north eccentricity</td></tr>
-<tr><td>reqcNewAntennadE</td><td></td><td>New component of east eccentricity</td></tr>
-<tr><td>reqcNewAntennadU</td><td></td><td>New component of up eccentricity</td></tr>
-<tr><td>reqcOldReceiverName</td><td></td><td>Old receiver name</td></tr>
-<tr><td>reqcNewReceiverName</td><td></td><td>New receiver name</td></tr>
-<tr><td>reqcOldReceiverNumber</td><td></td><td>Old receiver number</td></tr>
-<tr><td>reqcNewReceiverNumber</td><td></td><td>New receiver number</td></tr>
-</table>
-
-<p><h4 id="sp3comp">2.7 SP3 Comparison</h4></p>
-<p>
-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.
-</p>
-<p>
-To compare satellite clocks provided by the two files, BNC first converts coordinate differences dX,dY,dZ
-into along track, out-of-plane, and radial components. It then corrects the clock differences for the radial components
-of coordinate differences. RMS values of clock differences are finally calculated after introducing at first one offset
-'per epoch for all satellites' and secondly one offset 'per satellite for all epochs'.
-</p>
-<p><img src="IMG/Figure15.png"width=800/></p>
-<p>Figure 15: Example for comparing two SP3 files with satellite orbit and clock data using BNC</p>
-
-<p><h4 id="sp3input">2.7.1 Input SP3 Files - optional</h4></p>
-<p>
-Specify the full paths of two SP3 files, separate them by comma.
-</p>
-
-<p><h4 id="sp3exclude">2.7.2 Exclude Satellites - optional</h4></p>
-<p>
-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.
-<ul>
-  <li>G05,G31 (excluding GPS satellites with PRN 5 and 31)</li>
-  <li>G (excluding all GPS satellites)</li>
-  <li>R (excluding all GLONASS satellites)</li>
-  <li>R12,R24 (excluding GLONASS satellites with slot number 12 and 24)</li>
-  <li>G04,G31,R (excluding GPS satellites with PRN 4 and 31 as well as all GLONASS satellites)</li>
-</ul>
-</p>
-<p>
-Default is an empty option field, meaning that no satellite will be excluded from the comparison.
-</p>
-
-<p><h4 id="sp3log">2.7.3 Logfile - mandatory if 'Input SP3 Files' is set</h4></p>
-<p>
-Specify a logfile name to save results of the SP3 file comparison. BNC provides an option 'Summary only' to limit logfile content to 'Summary' information only.
-</p>
-<p>
-The following is an example for a SP3 Comparison logfile:
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    The following is a list of available key names for '<u>R</u>INEX <u>E</u>diting & <u>QC</u>' (short: REQC,
+    pronounced 'rek') options
+    and their meaning, cf. section 'Configuration Examples':
+  </p>
+  <table>
+    <tr></tr>
+    <tr>
+      <td><b>Keyname</b></td>
+      <td></td>
+      <td><b>Meaning</b></td>
+    </tr>
+    <tr>
+      <td>reqcAction</td>
+      <td></td>
+      <td>RINEX Editing & QC action</td>
+    </tr>
+    <tr>
+      <td>reqcObsFile</td>
+      <td></td>
+      <td>RINEX Observation input file(s)</td>
+    </tr>
+    <tr>
+      <td>reqcNavFile</td>
+      <td></td>
+      <td>RINEX Navigation input files(s)</td>
+    </tr>
+    <tr>
+      <td>reqcOutObsFile</td>
+      <td></td>
+      <td>RINEX Observation output file</td>
+    </tr>
+    <tr>
+      <td>reqcOutNavFile</td>
+      <td></td>
+      <td>RINEX Navigation output file</td>
+    </tr>
+    <tr>
+      <td>reqcMinEle</td>
+      <td></td>
+      <td>Minimum Elevation</td>
+    </tr>
+    <tr>
+      <td>reqcOutLogFile</td>
+      <td></td>
+      <td>Logfile</td>
+    </tr>
+    <tr>
+      <td>reqcLogSummaryOnly</td>
+      <td></td>
+      <td>Summary of Logfile</td>
+    </tr>
+    <tr>
+      <td>reqcSkyPlotSignals</td>
+      <td></td>
+      <td>Plots for signals</td>
+    </tr>
+    <tr>
+      <td>reqcPlotDir</td>
+      <td></td>
+      <td>RINEX QC plot directory</td>
+    </tr>
+    <tr>
+      <td>reqcRnxVersion</td>
+      <td></td>
+      <td>RINEX version of emerging new file</td>
+    </tr>
+    <tr>
+      <td>reqcSampling</td>
+      <td></td>
+      <td>Sampling interval of emerging new RINEX file</td>
+    </tr>
+    <tr>
+      <td>reqcV2Priority</td>
+      <td></td>
+      <td>Version 2 Signal Priority</td>
+    </tr>
+    <tr>
+      <td>reqcStartDateTime</td>
+      <td></td>
+      <td>Begin of emerging new RINEX file</td>
+    </tr>
+    <tr>
+      <td>reqcEndDateTime</td>
+      <td></td>
+      <td>End of emerging new RINEX file</td>
+    </tr>
+    <tr>
+      <td>reqcRunBy</td>
+      <td></td>
+      <td>Operator name</td>
+    </tr>
+    <tr>
+      <td>reqcUseObsTypes</td>
+      <td></td>
+      <td>GNSS systems and observation types</td>
+    </tr>
+    <tr>
+      <td>reqcComment</td>
+      <td></td>
+      <td>Additional comment lines</td>
+    </tr>
+    <tr>
+      <td>reqcOldMarkerName</td>
+      <td></td>
+      <td>Old marker name</td>
+    </tr>
+    <tr>
+      <td>reqcNewMarkerName</td>
+      <td></td>
+      <td>New marker name</td>
+    </tr>
+    <tr>
+      <td>reqcOldAntennaName</td>
+      <td></td>
+      <td>Old antenna name</td>
+    </tr>
+    <tr>
+      <td>reqcNewAntennaName</td>
+      <td></td>
+      <td>New antenna name</td>
+    </tr>
+    <tr>
+      <td>reqcOldAntennaNumber</td>
+      <td></td>
+      <td>Old antenna number</td>
+    </tr>
+    <tr>
+      <td>reqcNewAntennaNumber</td>
+      <td></td>
+      <td>New antenna number</td>
+    </tr>
+    <tr>
+      <td>reqcOldAntennadN</td>
+      <td></td>
+      <td>Old component of north eccentricity</td>
+    </tr>
+    <tr>
+      <td>reqcOldAntennadE</td>
+      <td></td>
+      <td>Old component of east eccentricity</td>
+    </tr>
+    <tr>
+      <td>reqcOldAntennadU</td>
+      <td></td>
+      <td>Old component of up eccentricity</td>
+    </tr>
+    <tr>
+      <td>reqcNewAntennadN</td>
+      <td></td>
+      <td>New component of north eccentricity</td>
+    </tr>
+    <tr>
+      <td>reqcNewAntennadE</td>
+      <td></td>
+      <td>New component of east eccentricity</td>
+    </tr>
+    <tr>
+      <td>reqcNewAntennadU</td>
+      <td></td>
+      <td>New component of up eccentricity</td>
+    </tr>
+    <tr>
+      <td>reqcOldReceiverName</td>
+      <td></td>
+      <td>Old receiver name</td>
+    </tr>
+    <tr>
+      <td>reqcNewReceiverName</td>
+      <td></td>
+      <td>New receiver name</td>
+    </tr>
+    <tr>
+      <td>reqcOldReceiverNumber</td>
+      <td></td>
+      <td>Old receiver number</td>
+    </tr>
+    <tr>
+      <td>reqcNewReceiverNumber</td>
+      <td></td>
+      <td>New receiver number</td>
+    </tr>
+  </table>
+
+  <p>
+  <h4 id="sp3comp">2.7 SP3 Comparison</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    To compare satellite clocks provided by the two files, BNC first converts coordinate differences dX,dY,dZ
+    into along track, out-of-plane, and radial components. It then corrects the clock differences for the radial
+    components
+    of coordinate differences. RMS values of clock differences are finally calculated after introducing at first one
+    offset
+    'per epoch for all satellites' and secondly one offset 'per satellite for all epochs'.
+  </p>
+  <p><img src="IMG/Figure15.png" width=800 /></p>
+  <p>Figure 15: Example for comparing two SP3 files with satellite orbit and clock data using BNC</p>
+
+  <p>
+  <h4 id="sp3input">2.7.1 Input SP3 Files - optional</h4>
+  </p>
+  <p>
+    Specify the full paths of two SP3 files, separate them by comma.
+  </p>
+
+  <p>
+  <h4 id="sp3exclude">2.7.2 Exclude Satellites - optional</h4>
+  </p>
+  <p>
+    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.
+  <ul>
+    <li>G05,G31 (excluding GPS satellites with PRN 5 and 31)</li>
+    <li>G (excluding all GPS satellites)</li>
+    <li>R (excluding all GLONASS satellites)</li>
+    <li>R12,R24 (excluding GLONASS satellites with slot number 12 and 24)</li>
+    <li>G04,G31,R (excluding GPS satellites with PRN 4 and 31 as well as all GLONASS satellites)</li>
+  </ul>
+  </p>
+  <p>
+    Default is an empty option field, meaning that no satellite will be excluded from the comparison.
+  </p>
+
+  <p>
+  <h4 id="sp3log">2.7.3 Logfile - mandatory if 'Input SP3 Files' is set</h4>
+  </p>
+  <p>
+    Specify a logfile name to save results of the SP3 file comparison. BNC provides an option 'Summary only' to limit
+    logfile content to 'Summary' information only.
+  </p>
+  <p>
+    The following is an example for a SP3 Comparison logfile:
+  </p>
+  <pre><p style="font-family:Monospace">
 ! SP3 File 1: Input/CNE1MGXRTS_20222410000_01D_05S_ORB.SP3
 ! SP3 File 2: Input/BKG1MGXRTS_20222410000_01D_05S_ORB.SP3
@@ -2603,160 +4420,235 @@
 </p>
 </pre>
-<p>
-The first part of this output following string 'following string' uses the following abbreviations:
-</p>
-
-<table>
-<tr><td>'Epoch' &nbsp;</td><td>Epoch Date and Time</td></tr>
-<tr><td>'PRN' &nbsp;</td><td>Satellite specification</td></tr>
-<tr><td>'radial' &nbsp;</td><td>Radial component of orbit coordinate difference [m]</td></tr>
-<tr><td>'along' &nbsp;</td><td>Along track component of orbit coordinate difference [m]</td></tr>
-<tr><td>'out' &nbsp;</td><td>Out-of-plane component of orbit coordinate difference [m]</td></tr>
-<tr><td>'clk' &nbsp;</td><td>Clock difference [m]</td></tr>
-<tr><td>'clkRed' &nbsp;</td><td>Clock difference reduced by radial component of orbit coordinate difference [m]</td></tr>
-<tr><td>'iPRN' &nbsp;</td><td>BNC internal sequence number</td></tr>
-</table>
-<p>
-The second part following string 'Summary' provides a summary of the comparison using the following
-abbreviations:<br>
-</p>
-<table>
-<tr><td>'PRN' &nbsp;</td><td>Satellite specification</td></tr>
-<tr><td>'radialRMS' &nbsp;</td><td>RMS of the radial component of orbit coordinate differences [mm]</td></tr>
-<tr><td>'alongRMS' &nbsp;</td><td>RMS of the along track component of orbit coordinate differences [mm]</td></tr>
-<tr><td>'outRMS' &nbsp;</td><td>RMS of the out-of-plane component of orbit coordinate differences [mm]</td></tr>
-<tr><td>'3DRMS' &nbsp;</td><td>3D RMS of the orbit coordinate differences [mm]</td></tr>
-<tr><td>'nOrb' &nbsp;</td><td>Number of epochs used in in orbit comparison</td></tr>
-<tr><td>'clkRMS' &nbsp;</td><td>RMS of clock differences [ns]</td></tr>
-<tr><td>'clkRedRMS' &nbsp;</td><td>RMS of the clock differences after reduction of radial orbit differences [ns]</td></tr>
-<tr><td>'clkRedSig' &nbsp;</td><td>Sigma of the clock differences after reduction of radial orbit differences [ns]</td></tr>
-<tr><td>'nClk' &nbsp;</td><td>Number of epochs use in clock comparisons</td></tr>
-<tr><td>'Offset' &nbsp;</td><td>Clock offset [ns]</td></tr>
-</table>
-<br>
-<p><img src="IMG/Figure16.png"width=1000/></p>
-<p>Figure 16: Graphical results from an example comparison of two SP3 files with satellite orbit and clock data using BNC</p>
-
-<p><h4 id="correct">2.8 Broadcast Corrections</h4></p>
-<p>
-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).
-</p>
-<p>
-An alternative to the observation space approach is the so-called 'state space' approach. The principle here is to provide
-information on individual error sources. It can be called 'State Space Representation' (SSR).
-For a rover position, state space information concerning precise satellite clocks, orbits, ionosphere, troposphere et cetera
-can be converted into observation space and used to correct the rover observables for more accurate positioning.
-Alternatively, the state information can be used directly in the rover's processing or adjustment model.
-</p>
-<p>
-RTCM is currently developing Version 3 messages to transport SSR corrections in real-time. They may refer to satellite Antenna Phase Center (APC)
-or Center of Mass (CoM). Because the development was stagnating in RTCM over years, IGS has developed similar SSR messages in parallel.
-Available and unter development are:
-<ul>
-  <li>SSR, Step I:</li>
+  <p>
+    The first part of this output following string 'following string' uses the following abbreviations:
+  </p>
+
+  <table>
+    <tr>
+      <td>'Epoch' &nbsp;</td>
+      <td>Epoch Date and Time</td>
+    </tr>
+    <tr>
+      <td>'PRN' &nbsp;</td>
+      <td>Satellite specification</td>
+    </tr>
+    <tr>
+      <td>'radial' &nbsp;</td>
+      <td>Radial component of orbit coordinate difference [m]</td>
+    </tr>
+    <tr>
+      <td>'along' &nbsp;</td>
+      <td>Along track component of orbit coordinate difference [m]</td>
+    </tr>
+    <tr>
+      <td>'out' &nbsp;</td>
+      <td>Out-of-plane component of orbit coordinate difference [m]</td>
+    </tr>
+    <tr>
+      <td>'clk' &nbsp;</td>
+      <td>Clock difference [m]</td>
+    </tr>
+    <tr>
+      <td>'clkRed' &nbsp;</td>
+      <td>Clock difference reduced by radial component of orbit coordinate difference [m]</td>
+    </tr>
+    <tr>
+      <td>'iPRN' &nbsp;</td>
+      <td>BNC internal sequence number</td>
+    </tr>
+  </table>
+  <p>
+    The second part following string 'Summary' provides a summary of the comparison using the following
+    abbreviations:<br>
+  </p>
+  <table>
+    <tr>
+      <td>'PRN' &nbsp;</td>
+      <td>Satellite specification</td>
+    </tr>
+    <tr>
+      <td>'radialRMS' &nbsp;</td>
+      <td>RMS of the radial component of orbit coordinate differences [mm]</td>
+    </tr>
+    <tr>
+      <td>'alongRMS' &nbsp;</td>
+      <td>RMS of the along track component of orbit coordinate differences [mm]</td>
+    </tr>
+    <tr>
+      <td>'outRMS' &nbsp;</td>
+      <td>RMS of the out-of-plane component of orbit coordinate differences [mm]</td>
+    </tr>
+    <tr>
+      <td>'3DRMS' &nbsp;</td>
+      <td>3D RMS of the orbit coordinate differences [mm]</td>
+    </tr>
+    <tr>
+      <td>'nOrb' &nbsp;</td>
+      <td>Number of epochs used in in orbit comparison</td>
+    </tr>
+    <tr>
+      <td>'clkRMS' &nbsp;</td>
+      <td>RMS of clock differences [ns]</td>
+    </tr>
+    <tr>
+      <td>'clkRedRMS' &nbsp;</td>
+      <td>RMS of the clock differences after reduction of radial orbit differences [ns]</td>
+    </tr>
+    <tr>
+      <td>'clkRedSig' &nbsp;</td>
+      <td>Sigma of the clock differences after reduction of radial orbit differences [ns]</td>
+    </tr>
+    <tr>
+      <td>'nClk' &nbsp;</td>
+      <td>Number of epochs use in clock comparisons</td>
+    </tr>
+    <tr>
+      <td>'Offset' &nbsp;</td>
+      <td>Clock offset [ns]</td>
+    </tr>
+  </table>
+  <br>
+  <p><img src="IMG/Figure16.png" width=1000 /></p>
+  <p>Figure 16: Graphical results from an example comparison of two SP3 files with satellite orbit and clock data using
+    BNC</p>
+
+  <p>
+  <h4 id="correct">2.8 Broadcast Corrections</h4>
+  </p>
+  <p>
+    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).
+  </p>
+  <p>
+    An alternative to the observation space approach is the so-called 'state space' approach. The principle here is to
+    provide
+    information on individual error sources. It can be called 'State Space Representation' (SSR).
+    For a rover position, state space information concerning precise satellite clocks, orbits, ionosphere, troposphere
+    et cetera
+    can be converted into observation space and used to correct the rover observables for more accurate positioning.
+    Alternatively, the state information can be used directly in the rover's processing or adjustment model.
+  </p>
+  <p>
+    RTCM is currently developing Version 3 messages to transport SSR corrections in real-time. They may refer to
+    satellite Antenna Phase Center (APC)
+    or Center of Mass (CoM). Because the development was stagnating in RTCM over years, IGS has developed similar SSR
+    messages in parallel.
+    Available and unter development are:
   <ul>
-    <li>Orbit corrections to Broadcast Ephemeris</li>
-    <li>Clock corrections to Broadcast Ephemeris</li>
-    <li>High-rate clock corrections to Broadcast Ephemeris</li>
-    <li>Combined orbit and clock corrections to Broadcast Ephemeris</li>
-    <li>User Range Accuracy (URA)</li>
-    <li>High Rate User Range Accuracy (HR URA)</li>
-    <li>Code biases</li>
+    <li>SSR, Step I:</li>
+    <ul>
+      <li>Orbit corrections to Broadcast Ephemeris</li>
+      <li>Clock corrections to Broadcast Ephemeris</li>
+      <li>High-rate clock corrections to Broadcast Ephemeris</li>
+      <li>Combined orbit and clock corrections to Broadcast Ephemeris</li>
+      <li>User Range Accuracy (URA)</li>
+      <li>High Rate User Range Accuracy (HR URA)</li>
+      <li>Code biases</li>
+    </ul>
+    <li>SSR, Step II:</li>
+    <ul>
+      <li>Phase biases</li>
+      <li>Vertical Total Electron Content (VTEC)</li>
+    </ul>
   </ul>
-  <li>SSR, Step II:</li>
-  <ul>
-    <li>Phase biases</li>
-    <li>Vertical Total Electron Content (VTEC)</li>
-  </ul>
-</ul>
-
-<p>
-SSR streams carrying these messages may be used e.g. to support real-time Precise Point Positioning (PPP) applications.
-</p>
-<p>
-Orbit corrections are provided in along-track, out-of-plane and radial components.
-These components are defined in the Earth-Centered, Earth-Fixed reference frame of the Broadcast Ephemeris.
-For an observer in this frame, the along-track component is aligned in both direction and sign with the velocity vector,
-the out-of-plane component is perpendicular to the plane defined by the satellite position and velocity vectors, and
-the radial direction is perpendicular to the along track and out-of-plane ones. The three components form a right-handed orthogonal system.
-</p>
-
-<p>
-After applying corrections, the satellite position and clock is referred to the 'ionospheric free' phase center of the antenna
-which is compatible with the broadcast orbit reference.
-</p>
-
-<p>
-The orbit and clock corrections do not include local effects like Ocean Loading, Solid Earth Tides or tropospheric delays.
-However, accurate single frequency applications can be corrected for global ionospheric effects using so-call VTEC messages
-for global ionospheric state parameters.
-</p>
-
-<p>
-While we have a plain ASCII standard for saving Broadcast Ephemeris in RINEX Navigation files, we do not have an equivalent standard
-for corrections to Broadcast Ephemeris. Hence, BNC saves Broadcast Correction files following its own format definition.
-</p>
-<p>
-The filename convention for Broadcast Correction files follows in general the convention for RINEX Version 3/4 files
-except for the two characters of the data type as well as for the characters of the filename suffix, which is set to 'ssr':
-The files below contains one day's data. 'MC' stands for 'Multi Constellation Clock' data and 'ION' stands for 'Ionosphere' data.
-</p>
-<pre>
+
+  <p>
+    SSR streams carrying these messages may be used e.g. to support real-time Precise Point Positioning (PPP)
+    applications.
+  </p>
+  <p>
+    Orbit corrections are provided in along-track, out-of-plane and radial components.
+    These components are defined in the Earth-Centered, Earth-Fixed reference frame of the Broadcast Ephemeris.
+    For an observer in this frame, the along-track component is aligned in both direction and sign with the velocity
+    vector,
+    the out-of-plane component is perpendicular to the plane defined by the satellite position and velocity vectors, and
+    the radial direction is perpendicular to the along track and out-of-plane ones. The three components form a
+    right-handed orthogonal system.
+  </p>
+
+  <p>
+    After applying corrections, the satellite position and clock is referred to the 'ionospheric free' phase center of
+    the antenna
+    which is compatible with the broadcast orbit reference.
+  </p>
+
+  <p>
+    The orbit and clock corrections do not include local effects like Ocean Loading, Solid Earth Tides or tropospheric
+    delays.
+    However, accurate single frequency applications can be corrected for global ionospheric effects using so-call VTEC
+    messages
+    for global ionospheric state parameters.
+  </p>
+
+  <p>
+    While we have a plain ASCII standard for saving Broadcast Ephemeris in RINEX Navigation files, we do not have an
+    equivalent standard
+    for corrections to Broadcast Ephemeris. Hence, BNC saves Broadcast Correction files following its own format
+    definition.
+  </p>
+  <p>
+    The filename convention for Broadcast Correction files follows in general the convention for RINEX Version 3/4 files
+    except for the two characters of the data type as well as for the characters of the filename suffix, which is set to
+    'ssr':
+    The files below contains one day's data. 'MC' stands for 'Multi Constellation Clock' data and 'ION' stands for
+    'Ionosphere' data.
+  </p>
+  <pre>
 SSRA00CNE1_S_20222750000_01D_MC.ssr
 IONO00IGS1_S_20222740000_01D_ION.ssr
 </pre>
-BNC's Broadcast Correction files contain blocks of records in plain ASCII format.
-Each block covers information about one specific topic and starts with an 'Epoch Record'.
-<p>
-<b>The 'Epoch Record' of a Broadcast Correction block</b>
-</p>
-
-<p>
-The leading 'Epoch Record' of each block in a Broadcast Correction file contains 11 parameters. Example:
-</p>
-<pre><p style="font-family:Monospace">
+  BNC's Broadcast Correction files contain blocks of records in plain ASCII format.
+  Each block covers information about one specific topic and starts with an 'Epoch Record'.
+  <p>
+    <b>The 'Epoch Record' of a Broadcast Correction block</b>
+  </p>
+
+  <p>
+    The leading 'Epoch Record' of each block in a Broadcast Correction file contains 11 parameters. Example:
+  </p>
+  <pre><p style="font-family:Monospace">
 > ORBIT 2022 10 01 23 59 45.0 2 110 SSRA00CNE1
 </p></pre>
-Their meaning is as follows:
-<ol type="1">
-  <li>Special character '&#62;' is the first character in each 'Epoch Record' (as we have it in RINEX Version 3)</li>
-  <li>SSR message or topic descriptor, valid descriptors are:<br>ORBIT, CLOCK, CODE_BIAS, PHASE_BIAS, or VTEC</li>
-  <li>Year, GPS time</li>
-  <li>Month, GPS time</li>
-  <li>Day, GPS time</li>
-  <li>Hour, GPS time</li>
-  <li>Minute, GPS time</li>
-  <li>Second, GPS time</li>
-  <li>SSR message update interval indicator</li>
-  <ul>
-    <li>0 = 1 sec</li>
-    <li>1 = 2 sec</li>
-    <li>2 = 5 sec</li>
-    <li>3 = 10 sec</li>
-    <li>4 = 15 sec</li>
-    <li>5 = 30 sec</li>
-    <li>6 = 60 sec</li>
-    <li>7 = 120 sec</li>
-    <li>8 = 240 sec</li>
-    <li>9 = 300 sec</li>
-    <li>10 = 600 sec</li>
-    <li>11 = 900 sec</li>
-    <li>12 = 1800 sec</li>
-    <li>13 = 3600 sec</li>
-    <li>14 = 7200 sec</li>
-    <li>15 = 10800 sec</li>
-  </ul>
-  <li>Number of following records in this block</li>
-  <li>Mountpoint, source/stream indicator</li>
-</ol>
-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 &quot;0.000&quot;.
-
-<p>
-<b>Example for block 'ORBIT' carrying orbit corrections</b>
-</p>
-<pre><p style="font-family:Monospace">
+  Their meaning is as follows:
+  <ol type="1">
+    <li>Special character '&#62;' is the first character in each 'Epoch Record' (as we have it in RINEX Version 3)</li>
+    <li>SSR message or topic descriptor, valid descriptors are:<br>ORBIT, CLOCK, CODE_BIAS, PHASE_BIAS, or VTEC</li>
+    <li>Year, GPS time</li>
+    <li>Month, GPS time</li>
+    <li>Day, GPS time</li>
+    <li>Hour, GPS time</li>
+    <li>Minute, GPS time</li>
+    <li>Second, GPS time</li>
+    <li>SSR message update interval indicator</li>
+    <ul>
+      <li>0 = 1 sec</li>
+      <li>1 = 2 sec</li>
+      <li>2 = 5 sec</li>
+      <li>3 = 10 sec</li>
+      <li>4 = 15 sec</li>
+      <li>5 = 30 sec</li>
+      <li>6 = 60 sec</li>
+      <li>7 = 120 sec</li>
+      <li>8 = 240 sec</li>
+      <li>9 = 300 sec</li>
+      <li>10 = 600 sec</li>
+      <li>11 = 900 sec</li>
+      <li>12 = 1800 sec</li>
+      <li>13 = 3600 sec</li>
+      <li>14 = 7200 sec</li>
+      <li>15 = 10800 sec</li>
+    </ul>
+    <li>Number of following records in this block</li>
+    <li>Mountpoint, source/stream indicator</li>
+  </ol>
+  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 &quot;0.000&quot;.
+
+  <p>
+    <b>Example for block 'ORBIT' carrying orbit corrections</b>
+  </p>
+  <pre><p style="font-family:Monospace">
 > ORBIT 2022 10 01 23 59 45.0 2 110 SSRA00CNE1
 G01          93    -0.1588    -0.8664    -0.0600        0.2210    -0.1200    -0.0400
@@ -2780,22 +4672,22 @@
 <p></pre>
 
-Records in this block provide the following satellite specific information:
-<ul>
-<li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
-<li>IOD referring to Broadcast Ephemeris set</li>
-<li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li>
-<li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
-<li>Out-of-plane Component of Orbit Correction to Broadcast Ephemeris [m]</li>
-<li>Velocity of Radial Component of Orbit Correction to Broadcast Ephemeris [mm/s]</li>
-<li>Velocity of Along-track Component of Orbit Correction to Broadcast Ephemeris [mm/s]</li>
-<li>Velocity of Out-of-plane Component of Orbit Correction to Broadcast Ephemeris [mm/s]</li>
-</ul>
-</p>
-
-<p>
-<b>Example for block 'CLOCK' carrying clock corrections</b>
-</p>
-
-<pre><p style="font-family:Monospace">
+  Records in this block provide the following satellite specific information:
+  <ul>
+    <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
+    <li>IOD referring to Broadcast Ephemeris set</li>
+    <li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li>
+    <li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
+    <li>Out-of-plane Component of Orbit Correction to Broadcast Ephemeris [m]</li>
+    <li>Velocity of Radial Component of Orbit Correction to Broadcast Ephemeris [mm/s]</li>
+    <li>Velocity of Along-track Component of Orbit Correction to Broadcast Ephemeris [mm/s]</li>
+    <li>Velocity of Out-of-plane Component of Orbit Correction to Broadcast Ephemeris [mm/s]</li>
+  </ul>
+  </p>
+
+  <p>
+    <b>Example for block 'CLOCK' carrying clock corrections</b>
+  </p>
+
+  <pre><p style="font-family:Monospace">
 > CLOCK 2022 10 01 23 59 45.0 2 110 SSRA00CNE1
 G01          93     0.1498     0.0000     0.0000
@@ -2818,18 +4710,18 @@
 </p>
 </pre>
-<p>
-Records in this block provide the following satellite specific information:
-<ul>
-<li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
-<li>IOD referring to Broadcast Ephemeris set</li>
-<li>C0 polynomial coefficient for Clock Correction to Broadcast Ephemeris [m]</li>
-<li>C1 polynomial coefficient for Clock Correction to Broadcast Ephemeris [mm/s]</li>
-<li>C2 polynomial coefficient for Clock Correction to Broadcast Ephemeris [mm/s**2]</li>
-</ul>
-</p>
-<p>
-<b>Example for block 'CODE_BIAS' carrying code biases</b>
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    Records in this block provide the following satellite specific information:
+  <ul>
+    <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
+    <li>IOD referring to Broadcast Ephemeris set</li>
+    <li>C0 polynomial coefficient for Clock Correction to Broadcast Ephemeris [m]</li>
+    <li>C1 polynomial coefficient for Clock Correction to Broadcast Ephemeris [mm/s]</li>
+    <li>C2 polynomial coefficient for Clock Correction to Broadcast Ephemeris [mm/s**2]</li>
+  </ul>
+  </p>
+  <p>
+    <b>Example for block 'CODE_BIAS' carrying code biases</b>
+  </p>
+  <pre><p style="font-family:Monospace">
 > CODE_BIAS 2022 10 01 23 59 45.0 2 110 SSRA00CNE1
 G01    7   1C    -2.6900   1P    -2.8300   1W    -3.1000   2L    -3.8000   2S    -3.8000   2W    -5.1000   5Q    -0.6300
@@ -2851,23 +4743,23 @@
 C02    3   2I     4.4700   6I     6.7600   7I     1.9700
 </p></pre>
-<p>
-Records in this block provide the following satellite specific information:
-<ul>
-  <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
-  <li>Number of Code Biases, succeeded by code specific information:</li>
+  <p>
+    Records in this block provide the following satellite specific information:
   <ul>
-    <li>Indicator to specify the signal and tracking mode</li>
-    <li>Code Bias [m]</li>
-    <li>Indicator to specify the signal and tracking mode</li>
-    <li>Code Bias [m]</li>
-    <li>etc.</li>
+    <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
+    <li>Number of Code Biases, succeeded by code specific information:</li>
+    <ul>
+      <li>Indicator to specify the signal and tracking mode</li>
+      <li>Code Bias [m]</li>
+      <li>Indicator to specify the signal and tracking mode</li>
+      <li>Code Bias [m]</li>
+      <li>etc.</li>
+    </ul>
   </ul>
-</ul>
-</p>
-
-<p>
-<b>Example for block 'PHASE_BIAS' carrying phase biases</b>
-</p>
-<pre><p style="font-family:Monospace">
+  </p>
+
+  <p>
+    <b>Example for block 'PHASE_BIAS' carrying phase biases</b>
+  </p>
+  <pre><p style="font-family:Monospace">
 > PHASE_BIAS 2022 10 01 23 59 45.0 2 110 SSRA00CNE1
  0   1
@@ -2890,39 +4782,39 @@
 C02   0.00000000   0.00000000    3   2I     0.5378   0   2  15   7I     4.1515   0   2  15   6I     0.7121   0   2  15
 </p></pre>
-<p>
-The second record in this block provides the following consistency information:
-<ul>
-
-<li>Dispersive bias consistency indicatory<br>
-0 &minus; phase biases valid for non-dispersive signal only<br>
-1 &minus; phase biases maintain consistency between non-dispersive and all original dispersive phase signals
-</li>
-
-<li>MW consistency indicator<br>
-0 &minus; code and phase biases are independently derived<br>
-1 &minus; consistency between code and phase biases is maintained for the MW combinations
-</li>
-
-</ul>
-Following records provide satellite specific information:
-<ul>
-  <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
-  <li>Yaw angle [&deg;], restricted to [0&deg... 360&deg]</li>
-  <li>Yaw rate [&deg;/s]</li>
-  <li>Number of phase biases in this record, succeeded by phase specific information:</li>
+  <p>
+    The second record in this block provides the following consistency information:
   <ul>
-    <li>Signal and tracking mode indicator</li>
-    <li>Phase bias [m]</li>
-    <li>Signal integer indicator</li>
-    <li>Signal wide-lane integer indicator</li>
-    <li>Signal discontinuity counter</li>
+
+    <li>Dispersive bias consistency indicatory<br>
+      0 &minus; phase biases valid for non-dispersive signal only<br>
+      1 &minus; phase biases maintain consistency between non-dispersive and all original dispersive phase signals
+    </li>
+
+    <li>MW consistency indicator<br>
+      0 &minus; code and phase biases are independently derived<br>
+      1 &minus; consistency between code and phase biases is maintained for the MW combinations
+    </li>
+
   </ul>
-</ul>
-</p>
-
-<p>
-<b>Example for block 'VTEC' carrying ionospheric corrections</b>
-</p>
-<pre><p style="font-family:Monospace"
+  Following records provide satellite specific information:
+  <ul>
+    <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
+    <li>Yaw angle [&deg;], restricted to [0&deg... 360&deg]</li>
+    <li>Yaw rate [&deg;/s]</li>
+    <li>Number of phase biases in this record, succeeded by phase specific information:</li>
+    <ul>
+      <li>Signal and tracking mode indicator</li>
+      <li>Phase bias [m]</li>
+      <li>Signal integer indicator</li>
+      <li>Signal wide-lane integer indicator</li>
+      <li>Signal discontinuity counter</li>
+    </ul>
+  </ul>
+  </p>
+
+  <p>
+    <b>Example for block 'VTEC' carrying ionospheric corrections</b>
+  </p>
+  <pre><p style="font-family:Monospace"
 > VTEC 2022 10 02 00 00 00.0 6 1 SSRA00CNE1
  1 12 12   450000.0
@@ -2954,136 +4846,279 @@
     0.0000     0.0750    -0.1400     0.0850    -0.0200    -0.0150     0.0750     0.0000     0.0050     0.0200     0.0250     0.0100     0.0450
 </p></pre>
-<p>
-The second record in this block provides four parameters:
-<ul>
-  <li>Layer number</li>
-  <li>Maximum degree of spherical harmonics</li>
-  <li>Maximum order of spherical harmonics</li>
-  <li>Height of ionospheric layer [m]</li>
-</ul>
-Subsequent records in this block provide the following information:
-<ul>
-  <li>Spherical harmonic coefficients C and S, sorted by degree and order (0 to maximum)</li>
-</ul>
-</p>
-
-<p><h4 id="corrdir">2.8.1 Directory, ASCII - optional</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="corrint">2.8.2 Interval - mandatory if 'Directory, ASCII' is set</h4></p>
-<p>
-Select the length of the Broadcast Correction files. The default value is '1 day'.
-</p>
-
-<p><h4 id="corrport">2.8.3 Port - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-The output format is the same to the format used for saving Broadcast Corrections in a file.
-</p>
-<p>
-The source code for BNC comes with an example Perl script 'test_tcpip_client.pl' that allows to read
-BNC's Broadcast Corrections from the IP port for verification.
-</p>
-
-<p><img src="IMG/Figure17.png"width=1000/></p>
-<p>Figure 17: Example for pulling, saving and output of Broadcast Corrections using BNC</p>
-
-<p><h4 id="syncout">2.9 Feed Engine</h4></p>
-
-<p>
-BNC can produce synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed
-a real-time GNSS network engine.  Observations can be streamed out through an IP port and/or saved in a local file.
-The output is always in the same plain ASCII format and sorted per incoming stream.
-</p>
-
-<p>
-Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the GPS Week.
-Following lines begin with the mountpoint string of the stream which provides the observations followed by a satellite number.
-Specifications for satellite number, code, phase, doppler and signal strength data follow definitions presented in the
-RINEX Version 3 documentation. In case of phase observations, a 'Slip Counter' is added. The end of an epoch is indicated by an empty line.
-</p>
-
-<p>
-A valid 'Slip Counter' is only presented for observations from RTCM Version 2 streams (Cummulative Loss of Lock Indicator).
-In RTCM Version 3 streams a 'Lock Time Indicator' is available instead. This parameter indicates a measure of the amount
-of time that has elapsed during which the receiver has maintained continuous lock on that satellite signal.
-If a cycle slip occurs during the previous measurement cycle, the 'Lock Time Indicator' will be reset to zero.
-But, this 'Lock Time Indicator' ist defined with different resolution for different RTCM version 3 observation types (MSMi, legacy messages).
-</p>
-
-<p>
-From the RTCM version 3 'Lock Time Indicator' a valid 'Lock Time' can be computed with the respective calculation rule.
-This parameter provides a measure of the amount of time that has elapsed during which the receiver has maintained continuous
-lock on that satellite signal in seconds. If a cycle slip occurs during the previous measurement cycle, the 'Lock Time' will decrease.
-This information will be used, to provide a 'Slip Counter' for RTCM Version 3 observations as well.  With it, we have an output
-format that is independent from the RTCM version of the observations. The 'Lock Time' output can be activated optional.
-</p>
-
-<p>
-The following table describes the format of BNC's synchronized output of GNSS observations which consists of 'Epoch Records'
-and 'Observation Records'. Each Epoch Record is followed by one or more Observation Records. The Observation Record is repeated
-for each satellite having been observed in the current epoch. The length of an Observation Record is given by the number of
-observation types for this satellite.
-</p>
-
-<p>Table 2: Contents and format of synchronized output of observations feeding a GNSS engine</p>
-<p>
-<table>
-<tr><td></td><td><b>Example</b></td><td><b>Format</b></td></tr>
-
-<tr><td><b>Epoch Record</b></td><td></td><td></td></tr>
-<tr><td>Record Identifier</td><td>></td><td>A1</td></tr>
-<tr><td>GPS Week Number</td><td>1850</td><td>1X,I4</td></tr>
-<tr><td>GPS Seconds of Week</td><td>120556.0000000 &nbsp; &nbsp;</td><td>1X,F14.7</td></tr>
-
-<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-<tr><td><b>Observation Record</b></td><td></td><td></td></tr>
-<tr><td>Mountpoint</td><td>WTZR00DEU0</td><td>A</td></tr>
-<tr><td>Satellite Number</td><td>G01</td><td>1X,A3</td></tr>
-
-<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-
-<tr><td><b>Pseudo-Range Data</b></td><td></td><td></td></tr>
-<tr><td>Observation Code</td><td><b>C</b>1C</td><td>1X,A3</td></tr>
-<tr><td>Pseudo-Range Observation</td><td>25394034.112</td><td>1X,F14.3</td></tr>
-
-<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-
-<tr><td><b>Carrier Phase Data</b></td><td></td><td></td></tr>
-<tr><td>Observation Code</td><td><b>L</b>1C</td><td>1X,A3</td></tr>
-<tr><td>Carrier Phase Observation</td><td>133446552.870</td><td>1X,F14.3</td></tr>
-<tr><td>Slip Counter</td><td>11</td><td>1X,I4</td></tr>
-
-<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-
-<tr><td><b>Doppler Data</b></td><td></td><td></td></tr>
-<tr><td>Observation Code</td><td><b>D</b>1C</td><td>1X,A3</td></tr>
-<tr><td>Doppler Observation</td><td>-87.977</td><td>1X,F14.3</td></tr>
-
-<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-
-<tr><td><b>Signal Strength</b></td><td></td><td></td></tr>
-<tr><td>Observation Code</td><td><b>S</b>2W</td><td>1X,A3</td></tr>
-<tr><td>Observed Signal Strength &nbsp; &nbsp;</td><td>34.750</td><td>1X,F8.3</td></tr>
-
-<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-
-<tr><td><b>Lock Time (optional)</b></td><td></td><td></td></tr>
-<tr><td>Observation Code</td><td><b>T</b>2W</td><td>1X,A3</td></tr>
-<tr><td>Computed Lock Time &nbsp; &nbsp;</td><td>937.000</td><td>1X,F8.3</td></tr>
-</table>
-</p>
-
-The following is an example epoch for synchronized file and IP port output, which presents observations
-from GPS, GLONASS, Galileo, BDS (BeiDou), and QZSS satellites as collected through the stream CUT000AUS0:
-<pre><p style="font-family:Monospace">
+  <p>
+    The second record in this block provides four parameters:
+  <ul>
+    <li>Layer number</li>
+    <li>Maximum degree of spherical harmonics</li>
+    <li>Maximum order of spherical harmonics</li>
+    <li>Height of ionospheric layer [m]</li>
+  </ul>
+  Subsequent records in this block provide the following information:
+  <ul>
+    <li>Spherical harmonic coefficients C and S, sorted by degree and order (0 to maximum)</li>
+  </ul>
+  </p>
+
+  <p>
+  <h4 id="corrdir">2.8.1 Directory, ASCII - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="corrint">2.8.2 Interval - mandatory if 'Directory, ASCII' is set</h4>
+  </p>
+  <p>
+    Select the length of the Broadcast Correction files. The default value is '1 day'.
+  </p>
+
+  <p>
+  <h4 id="corrport">2.8.3 Port - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    The output format is the same to the format used for saving Broadcast Corrections in a file.
+  </p>
+  <p>
+    The source code for BNC comes with an example Perl script 'test_tcpip_client.pl' that allows to read
+    BNC's Broadcast Corrections from the IP port for verification.
+  </p>
+
+  <p><img src="IMG/Figure17.png" width=1000 /></p>
+  <p>Figure 17: Example for pulling, saving and output of Broadcast Corrections using BNC</p>
+
+  <p>
+  <h4 id="syncout">2.9 Feed Engine</h4>
+  </p>
+
+  <p>
+    BNC can produce synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed
+    a real-time GNSS network engine. Observations can be streamed out through an IP port and/or saved in a local file.
+    The output is always in the same plain ASCII format and sorted per incoming stream.
+  </p>
+
+  <p>
+    Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the
+    GPS Week.
+    Following lines begin with the mountpoint string of the stream which provides the observations followed by a
+    satellite number.
+    Specifications for satellite number, code, phase, doppler and signal strength data follow definitions presented in
+    the
+    RINEX Version 3 documentation. In case of phase observations, a 'Slip Counter' is added. The end of an epoch is
+    indicated by an empty line.
+  </p>
+
+  <p>
+    A valid 'Slip Counter' is only presented for observations from RTCM Version 2 streams (Cummulative Loss of Lock
+    Indicator).
+    In RTCM Version 3 streams a 'Lock Time Indicator' is available instead. This parameter indicates a measure of the
+    amount
+    of time that has elapsed during which the receiver has maintained continuous lock on that satellite signal.
+    If a cycle slip occurs during the previous measurement cycle, the 'Lock Time Indicator' will be reset to zero.
+    But, this 'Lock Time Indicator' ist defined with different resolution for different RTCM version 3 observation types
+    (MSMi, legacy messages).
+  </p>
+
+  <p>
+    From the RTCM version 3 'Lock Time Indicator' a valid 'Lock Time' can be computed with the respective calculation
+    rule.
+    This parameter provides a measure of the amount of time that has elapsed during which the receiver has maintained
+    continuous
+    lock on that satellite signal in seconds. If a cycle slip occurs during the previous measurement cycle, the 'Lock
+    Time' will decrease.
+    This information will be used, to provide a 'Slip Counter' for RTCM Version 3 observations as well. With it, we have
+    an output
+    format that is independent from the RTCM version of the observations. The 'Lock Time' output can be activated
+    optional.
+  </p>
+
+  <p>
+    The following table describes the format of BNC's synchronized output of GNSS observations which consists of 'Epoch
+    Records'
+    and 'Observation Records'. Each Epoch Record is followed by one or more Observation Records. The Observation Record
+    is repeated
+    for each satellite having been observed in the current epoch. The length of an Observation Record is given by the
+    number of
+    observation types for this satellite.
+  </p>
+
+  <p>Table 2: Contents and format of synchronized output of observations feeding a GNSS engine</p>
+  <p>
+  <table>
+    <tr>
+      <td></td>
+      <td><b>Example</b></td>
+      <td><b>Format</b></td>
+    </tr>
+
+    <tr>
+      <td><b>Epoch Record</b></td>
+      <td></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Record Identifier</td>
+      <td>></td>
+      <td>A1</td>
+    </tr>
+    <tr>
+      <td>GPS Week Number</td>
+      <td>1850</td>
+      <td>1X,I4</td>
+    </tr>
+    <tr>
+      <td>GPS Seconds of Week</td>
+      <td>120556.0000000 &nbsp; &nbsp;</td>
+      <td>1X,F14.7</td>
+    </tr>
+
+    <tr>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+    </tr>
+    <tr>
+      <td><b>Observation Record</b></td>
+      <td></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Mountpoint</td>
+      <td>WTZR00DEU0</td>
+      <td>A</td>
+    </tr>
+    <tr>
+      <td>Satellite Number</td>
+      <td>G01</td>
+      <td>1X,A3</td>
+    </tr>
+
+    <tr>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+    </tr>
+
+    <tr>
+      <td><b>Pseudo-Range Data</b></td>
+      <td></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Observation Code</td>
+      <td><b>C</b>1C</td>
+      <td>1X,A3</td>
+    </tr>
+    <tr>
+      <td>Pseudo-Range Observation</td>
+      <td>25394034.112</td>
+      <td>1X,F14.3</td>
+    </tr>
+
+    <tr>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+    </tr>
+
+    <tr>
+      <td><b>Carrier Phase Data</b></td>
+      <td></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Observation Code</td>
+      <td><b>L</b>1C</td>
+      <td>1X,A3</td>
+    </tr>
+    <tr>
+      <td>Carrier Phase Observation</td>
+      <td>133446552.870</td>
+      <td>1X,F14.3</td>
+    </tr>
+    <tr>
+      <td>Slip Counter</td>
+      <td>11</td>
+      <td>1X,I4</td>
+    </tr>
+
+    <tr>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+    </tr>
+
+    <tr>
+      <td><b>Doppler Data</b></td>
+      <td></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Observation Code</td>
+      <td><b>D</b>1C</td>
+      <td>1X,A3</td>
+    </tr>
+    <tr>
+      <td>Doppler Observation</td>
+      <td>-87.977</td>
+      <td>1X,F14.3</td>
+    </tr>
+
+    <tr>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+    </tr>
+
+    <tr>
+      <td><b>Signal Strength</b></td>
+      <td></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Observation Code</td>
+      <td><b>S</b>2W</td>
+      <td>1X,A3</td>
+    </tr>
+    <tr>
+      <td>Observed Signal Strength &nbsp; &nbsp;</td>
+      <td>34.750</td>
+      <td>1X,F8.3</td>
+    </tr>
+
+    <tr>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+      <td>&nbsp;</td>
+    </tr>
+
+    <tr>
+      <td><b>Lock Time (optional)</b></td>
+      <td></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Observation Code</td>
+      <td><b>T</b>2W</td>
+      <td>1X,A3</td>
+    </tr>
+    <tr>
+      <td>Computed Lock Time &nbsp; &nbsp;</td>
+      <td>937.000</td>
+      <td>1X,F8.3</td>
+    </tr>
+  </table>
+  </p>
+
+  The following is an example epoch for synchronized file and IP port output, which presents observations
+  from GPS, GLONASS, Galileo, BDS (BeiDou), and QZSS satellites as collected through the stream CUT000AUS0:
+  <pre><p style="font-family:Monospace">
 > 2235 161041.0000000
 CUT000AUS0 G05 C1C   22397546.124 L1C  117700392.329    0 D1C      -1640.054 S1C   43.812 C2W   22397552.729 L2W   91714594.476    0 S2W   40.500 C2X   22397553.316 L2X   91714226.480    0 S2X   42.312
@@ -3134,70 +5169,93 @@
 ..
 </p></pre>
-<p>
-The source code for BNC comes with a Perl script named 'test_tcpip_client.pl' that allows to read BNC's (synchronized or unsynchronized)
-ASCII observation output from the IP port and print it on standard output for verification.
-</p>
-
-<p>
-Note that any socket connection of an application to BNC's synchronized or unsynchronized observation ports is recorded in the 'Log' tab
-on the bottom of the main window together with a connection counter, resulting in log records like 'New client connection on sync/usync port: # 1'.
-</p>
-
-<p>
-The following figure shows the screenshot of a BNC configuration where a number of streams is pulled from different Ntrip Broadcasters
-to feed a GNSS engine via IP port output.
-</p>
-<p><img src="IMG/Figure18.png"width=1000/></p>
-<p>Figure 18: Synchronized BNC output via IP port to feed a GNSS real-time engine</p>
-
-<p><h4 id="syncport">2.9.1 Port - optional</h4></p>
-<p>
-BNC can produce synchronized observations in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'.
-Synchronized means that BNC collects all observation data for a specific epoch, which become available within
-a certain number of seconds (see 'Wait for Full Obs Epoch' option). It then - epoch by epoch - outputs whatever has been received.
-The output comes block-wise per stream following the format specified in Table 2. Enter an IP port number here to activate this function.
-The default is an empty option field, meaning that no synchronized output is generated.</p>
-</p>
-
-<p><h4 id="syncwait">2.9.2 Wait for Full Obs Epoch - mandatory if 'Port' is set</h4></p>
-<p>
-When feeding a real-time GNSS network engine waiting for synchronized observations epoch by epoch, BNC drops whatever is
-received later than 'Wait for full obs epoch' seconds. A value of 3 to 5 seconds could be an appropriate choice for that,
-depending on the latency of the incoming streams and the delay acceptable for your real-time GNSS product.
-Default value for 'Wait for full obs epoch' is 5 seconds.
-Note that 'Wait for full obs epoch' does not affect the RINEX Observation file content. Observations received later
-than 'Wait for full obs epoch' seconds will still be included in the RINEX Observation files.
-</p>
-
-<p><h4 id="syncsample">2.9.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p>
-<p>
-Select a synchronized observation output sampling interval in seconds.
-</p>
-
-<p><h4 id="syncfile">2.9.4 File - optional</h4></p>
-<p>
-Specify the full path to a 'File' where synchronized observations are saved in plain ASCII format.
-The default value is an empty option field, meaning that no ASCII output file is created.
-Beware that the size of this file can rapidly increase depending on the number of incoming streams.
-To prevent it from becoming too large, the name of the file can be changed on-the-fly.
-This option is primarily meant for test and evaluation.
-</p>
-
-<p><h4 id="syncuport">2.9.5 Port (unsynchronized) - optional</h4></p>
-<p>
-BNC can produce unsynchronized observations from all configured streams in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'.
-Unsynchronized means that BNC immediately forwards any received observation to the port.
-Nevertheless, the output is produced block-wise per stream. Specify an IP port number here to activate this function.
-The default is an empty option field, meaning that no unsynchronized output is generated.
-</p>
-<p>
-The following is an example for unsynchronized IP port output which presents observations from GPS, GLONASS, Galileo, BDS (BeiDou)
-as collected through stream WTZR00DEU0. The format for synchronized and unsynchronized output of observations is very much the same.
-However, unsynchronized output does not have 'Epoch Records' and 'Observation Records'.
-Instead each record contains the 'GPS Week Number' and 'GPS Second of Week' time tag between the mountpoint string and the satellite number,
-see Table 2 for format details.
-</p>
-
-<pre><p style="font-family:Monospace">
+  <p>
+    The source code for BNC comes with a Perl script named 'test_tcpip_client.pl' that allows to read BNC's
+    (synchronized or unsynchronized)
+    ASCII observation output from the IP port and print it on standard output for verification.
+  </p>
+
+  <p>
+    Note that any socket connection of an application to BNC's synchronized or unsynchronized observation ports is
+    recorded in the 'Log' tab
+    on the bottom of the main window together with a connection counter, resulting in log records like 'New client
+    connection on sync/usync port: # 1'.
+  </p>
+
+  <p>
+    The following figure shows the screenshot of a BNC configuration where a number of streams is pulled from different
+    Ntrip Broadcasters
+    to feed a GNSS engine via IP port output.
+  </p>
+  <p><img src="IMG/Figure18.png" width=1000 /></p>
+  <p>Figure 18: Synchronized BNC output via IP port to feed a GNSS real-time engine</p>
+
+  <p>
+  <h4 id="syncport">2.9.1 Port - optional</h4>
+  </p>
+  <p>
+    BNC can produce synchronized observations in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'.
+    Synchronized means that BNC collects all observation data for a specific epoch, which become available within
+    a certain number of seconds (see 'Wait for Full Obs Epoch' option). It then - epoch by epoch - outputs whatever has
+    been received.
+    The output comes block-wise per stream following the format specified in Table 2. Enter an IP port number here to
+    activate this function.
+    The default is an empty option field, meaning that no synchronized output is generated.</p>
+  </p>
+
+  <p>
+  <h4 id="syncwait">2.9.2 Wait for Full Obs Epoch - mandatory if 'Port' is set</h4>
+  </p>
+  <p>
+    When feeding a real-time GNSS network engine waiting for synchronized observations epoch by epoch, BNC drops
+    whatever is
+    received later than 'Wait for full obs epoch' seconds. A value of 3 to 5 seconds could be an appropriate choice for
+    that,
+    depending on the latency of the incoming streams and the delay acceptable for your real-time GNSS product.
+    Default value for 'Wait for full obs epoch' is 5 seconds.
+    Note that 'Wait for full obs epoch' does not affect the RINEX Observation file content. Observations received later
+    than 'Wait for full obs epoch' seconds will still be included in the RINEX Observation files.
+  </p>
+
+  <p>
+  <h4 id="syncsample">2.9.3 Sampling - mandatory if 'File' or 'Port' is set</h4>
+  </p>
+  <p>
+    Select a synchronized observation output sampling interval in seconds.
+  </p>
+
+  <p>
+  <h4 id="syncfile">2.9.4 File - optional</h4>
+  </p>
+  <p>
+    Specify the full path to a 'File' where synchronized observations are saved in plain ASCII format.
+    The default value is an empty option field, meaning that no ASCII output file is created.
+    Beware that the size of this file can rapidly increase depending on the number of incoming streams.
+    To prevent it from becoming too large, the name of the file can be changed on-the-fly.
+    This option is primarily meant for test and evaluation.
+  </p>
+
+  <p>
+  <h4 id="syncuport">2.9.5 Port (unsynchronized) - optional</h4>
+  </p>
+  <p>
+    BNC can produce unsynchronized observations from all configured streams in ASCII format on your local host (IP
+    127.0.0.1) through an IP 'Port'.
+    Unsynchronized means that BNC immediately forwards any received observation to the port.
+    Nevertheless, the output is produced block-wise per stream. Specify an IP port number here to activate this
+    function.
+    The default is an empty option field, meaning that no unsynchronized output is generated.
+  </p>
+  <p>
+    The following is an example for unsynchronized IP port output which presents observations from GPS, GLONASS,
+    Galileo, BDS (BeiDou)
+    as collected through stream WTZR00DEU0. The format for synchronized and unsynchronized output of observations is
+    very much the same.
+    However, unsynchronized output does not have 'Epoch Records' and 'Observation Records'.
+    Instead each record contains the 'GPS Week Number' and 'GPS Second of Week' time tag between the mountpoint string
+    and the satellite number,
+    see Table 2 for format details.
+  </p>
+
+  <pre><p style="font-family:Monospace">
 WTZR00DEU0 2235 163641.0000000 C45 C2I   21792728.974 L2I  113480606.233    0 D2I       -840.222 S2I   49.000 C6I   21792718.056 L6I   92212301.720    0 D6I       -682.735 S6I   53.000 C5P   21792722.630 L5P   85519518.841    0 D5P       -633.150 S5P   55.000 C1P   21792728.867 L1P  114521718.308    0 D1P       -847.940 S1P   49.000
 WTZR00DEU0 2235 163641.0000000 C57 C2I   35241541.940 L2I  183511967.699    0 D2I       3312.134 S2I   38.000
@@ -3227,205 +5285,294 @@
 </p></pre>
 
-<p><h4 id="serial">2.10 Serial Output</h4></p>
-<p>
-You may use BNC to feed a serially connected device like a GNSS receiver. For that, an incoming stream can be forwarded to a serial port.
-Depending on the stream content, the receiver may use it for Differential GNSS, Precise Point Positioning or any other purpose
-supported by its firmware.
-</p>
-<p>
-Note that receiving a VRS stream requires the receiver sending NMEA sentences (option 'NMEA' set to 'Manual' or 'Auto') to the Ntrip Broadcaster.
-The following figure shows the data flow when pulling a VRS stream or a physical (non-VRS) stream.
-</p>
-
-<p><img src="IMG/Figure19.png"width=1000/></p>
-<p>Figure 19: Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is mandatory for VRS streams</p>
-
-<p>
-The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an Ntrip Broadcaster
-to feed a serially connected RTK rover.
-</p>
-
-<p><img src="IMG/Figure20.png"width=1000/></p>
-<p>Figure 20: BNC pulling a RTCM Version 3 stream to feed a serial connected receiver with observations from a nearby reference station for conventional RTK</p>
-
-<p><h4 id="sermount">2.10.1 Mountpoint - optional</h4></p>
-<p>
-Enter a 'Mountpoint' to forward its corresponding stream to a serially connected GNSS receiver.
-</p>
-<p>
-When selecting one of the serial communication options listed below, make sure that you pick those configured to the
-serially connected receiver.
-</p>
-
-<p><h4 id="serport">2.10.2 Port Name - mandatory if 'Mountpoint' is set</h4></p>
-<p>
-Enter the serial 'Port name' selected on your host for communication with the serially connected receiver.
-Valid port names are
-</p>
-<table>
-  <tr><td>Windows:      </td><td>&nbsp; COM1, COM2              </td></tr>
-  <tr><td>Linux:        </td><td>&nbsp; /dev/ttyS0, /dev/ttyS1  </td></tr>
-  <tr><td>FreeBSD:      </td><td>&nbsp; /dev/ttyd0, /dev/ttyd1  </td></tr>
-  <tr><td>Digital Unix: </td><td>&nbsp; /dev/tty01, /dev/tty02  </td></tr>
-  <tr><td>HP-UX:        </td><td>&nbsp; /dev/tty1p0, /dev/tty2p0</td></tr>
-  <tr><td>SGI/IRIX:     </td><td>&nbsp; /dev/ttyf1, /dev/ttyf2  </td></tr>
-  <tr><td>SunOS/Solaris:</td><td>&nbsp; /dev/ttya, /dev/ttyb    </td></tr>
-</table>
-<p>
-Note that you must plug a serial cable in the port defined here before you start BNC.
-</p>
-
-<p><h4 id="serbaud">2.10.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p>
-<p>
-Select a 'Baud rate' for the serial output link. Note that using a high baud rate is recommended.
-</p>
-
-<p><h4 id="serflow">2.10.4 Flow Control - mandatory if 'Mountpoint' is set</h4></p>
-<p>
-Select a 'Flow control' for the serial output link. Note that your selection must equal the flow control configured to the serially connected device.
-Select 'OFF' if you do not know better.
-</p>
-
-<p><h4 id="serparity">2.10.5 Parity - mandatory if 'Mountpoint' is set</h4></p>
-<p>
-Select the 'Parity' for the serial output link. Note that parity is often set to 'NONE'.
-</p>
-
-<p><h4 id="serdata">2.10.6 Data Bits - mandatory if 'Mountpoint' is set</h4></p>
-<p>
-Select the number of 'Data bits' for the serial output link. Note that often '8' data bits are used.
-</p>
-
-<p><h4 id="serstop">2.10.7 Stop Bits - mandatory if 'Mountpoint' is set</h4></p>
-<p>
-Select the number of 'Stop bits' for the serial output link. Note that often '1' stop bit is used.
-</p>
-
-<p><h4 id="serauto">2.10.8 NMEA - mandatory if 'Mountpoint' is set</h4></p>
-<p>The 'NMEA' option supports the so-called 'Virtual Reference Station' (VRS) concept which requires the receiver to send
-approximate position information to the Ntrip Broadcaster. Select 'no' if you do not want BNC to forward or upload any NMEA sentence
-to the Ntrip broadcaster in support of VRS.
-</p>
-<p>
-Select 'Auto' to automatically forward NMEA sentences of type GGA from your serially connected receiver to the Ntrip broadcaster
-and/or save them in a file.
-</p>
-<p>Select 'Manual GPGGA' or 'Manual GNGGA' if you want BNC to produce and upload GPGGA or GNGGA NMEA sentences to the Ntrip broadcaster
-because your serially connected receiver does not generate them. A Talker ID 'GP' proceeding the GGA string stands for GPS solutions
-while a Talker ID 'GN' stands for multi-constellation solutions.
-</p>
-<p>
-Note that selecting 'Auto' or 'Manual' works only for VRS streams which show up under the 'Streams' canvas on BNC's main window
-with 'nmea' stream attribute set to 'yes'. This attribute is either extracted from the Ntrip broadcaster's source-table or
-introduced by the user through editing the BNC configuration file.
-</p>
-
-<p><h4 id="serfile">2.10.9 File - optional if 'NMEA' is set to 'Auto'</h4></p>
-<p>
-Specify the full path to a file where NMEA sentences coming from your serially connected receiver are saved.
-Default is an empty option field, meaning that no NMEA sentences will be saved on disk.
-</p>
-<p><h4 id="serheight">2.10.10 Height - mandatory if 'NMEA' is set to 'Manual'</h4></p>
-<p>
-Specify an approximate 'Height' above mean sea level in meters for the reference station introduced through 'Mountpoint'.
-Together with the latitude and longitude from the Ntrip broadcaster source-table, the height information is used
-to build GGA sentences to be sent to the Ntrip broadcaster.
-</p>
-<p>
-For adjusting latitude and longitude values of a VRS stream given in the 'Streams' canvas,
-you can double click the latitude/longitude data fields, specify appropriate values and then hit Enter.
-</p>
-<p>
-This option is only relevant when option 'NMEA' is set to 'Manual GPGGA' or 'Manual GNGGA' respectively.
-</p>
-
-<p><h4 id="sersampl">2.10.11 Sampling - mandatory if 'NMEA' is set to 'Manual'</h4></p>
-<p>
-Select a sampling interval in seconds for manual generation and upload of NMEA GGA sentences.
-</p>
-<p>
-A sampling rate of '0' means that a GGA sentence will be sent only once to initialize the requested VRS stream.
-Note that some VRS systems need GGA sentences at regular intervals.
-</p>
-
-<p><h4 id="advnote">2.11 Outages</h4></p>
-<p>
-At any time an incoming stream might become unavailable or corrupted. In such cases, it is important that the BNC operator
-and/or the stream providers become aware of the situation so that measures can be taken to restore the stream.
-Furthermore, continuous attempts to decode a corrupted stream can generate unnecessary workload for BNC.
-Outages and corruptions are handled by BNC as follows:
-</p>
-<p>
-<u>Stream outages:</u> BNC considers a connection to be broken when there are no incoming data detected for more than 20 seconds.
-When this occurs, BNC will try to reconnect at a decreasing rate. It will first try to reconnect with 1 second delay and
-again in 2 seconds if the previous attempt failed. If the attempt is still unsuccessful, it will try to reconnect
-within 4 seconds after the previous attempt and so on. The waiting time doubles each time with a maximum of 256 seconds.
-</p>
-<p>
-<u>Stream corruption:</u> Not all chunks of bits transferred to BNC's internal decoder may return valid observations.
-Sometimes several chunks might be needed before the next observation can be properly decoded.
-BNC buffers all outputs (both valid and invalid) from the decoder for a short time span
-(size derived from the expected 'Observation rate') to then determine whether a stream is valid or corrupted.
-</p>
-<p>
-Outage and corruption events are reported in the 'Log' tab. They can also be passed on as parameters to a shell script
-or batch file to generate an advisory note to BNC's operator or affected stream providers.
-This functionality lets users utilize BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
-</p>
-
-<p><h4 id="obsrate">2.11.1 Observation Rate - optional</h4></p>
-<p>
-BNC can collect all returns (success or failure) coming from a decoder within a certain short time span to then decide whether
-a stream has an outage or its content is corrupted. This procedure needs a rough a priori estimate of the expected
-observation rate of the incoming streams.
-</p>
-<p>An empty option field (default) means that you do not want explicit information from BNC about stream outages and
-incoming streams that cannot be decoded.
-</p>
-
-<p><h4 id="advfail">2.11.2 Failure Threshold - mandatory if 'Observation rate' is set</h4></p>
-<p>
-Event 'Begin_Failure' will be reported if no data is received continuously for longer than the 'Failure threshold' time.
-Similarly, event 'Begin_Corrupted' will be reported when corrupted data is detected by the decoder continuously for
-longer than this 'Failure threshold' time. The default value is set to 15 minutes and is recommended as to not inundate
-users with too many event reports.
-</p>
-<p>
-Note that specifying a value of zero '0' for the 'Failure threshold' will force BNC to report any stream failure immediately.
-Note also that for using this function you need to specify the 'Observation rate'.
-</p>
-
-<p><h4 id="advreco">2.11.3 Recovery Threshold - mandatory if 'Observation rate' is set</h4></p>
-<p>
-Once a 'Begin_Failure' or 'Begin_Corrupted' event has been reported, BNC will check when the stream again becomes available or uncorrupted.
-Event 'End_Failure' or 'End_Corrupted' will be reported as soon as valid observations are detected continuously throughout
-the 'Recovery threshold' time span. The default value is set to 5 minutes and is recommended as to not inundate users with too many event reports.
-</p>
-<p>
-Note that specifying a value of zero '0' for the 'Recovery threshold' will force BNC to report any stream recovery immediately.
-Note also that for using this function you need to specify the 'Observation rate'.
-</p>
-
-<p><h4 id="advscript">2.11.4 Script - optional if 'Observation rate' is set</h4></p>
-<p>
-As mentioned before, BNC can trigger a shell script or a batch file to be executed when one of the described events is reported.
-This script can be used to email an advisory note to network operator or stream providers. To enable this feature,
-specify the full path to the script or batch file in the 'Script' field. The affected stream's mountpoint and type of event
-reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script as
-command line parameters (%1 and %2 on Windows systems or $1 and $2 on Unix/Linux/Mac OS X systems) together with date and time information.
-</p>
-<p>
-Leave the 'Script' field empty if you do not wish to use this option. An invalid path will also disable this option.
-</p>
-<p>
-Examples for command line parameter strings passed on to the advisory 'Script' are:
-<pre><p style="font-family:Monospace">
+  <p>
+  <h4 id="serial">2.10 Serial Output</h4>
+  </p>
+  <p>
+    You may use BNC to feed a serially connected device like a GNSS receiver. For that, an incoming stream can be
+    forwarded to a serial port.
+    Depending on the stream content, the receiver may use it for Differential GNSS, Precise Point Positioning or any
+    other purpose
+    supported by its firmware.
+  </p>
+  <p>
+    Note that receiving a VRS stream requires the receiver sending NMEA sentences (option 'NMEA' set to 'Manual' or
+    'Auto') to the Ntrip Broadcaster.
+    The following figure shows the data flow when pulling a VRS stream or a physical (non-VRS) stream.
+  </p>
+
+  <p><img src="IMG/Figure19.png" width=1000 /></p>
+  <p>Figure 19: Flowcharts, BNC forwarding a stream to a serially connected receiver; sending NMEA sentences is
+    mandatory for VRS streams</p>
+
+  <p>
+    The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an Ntrip
+    Broadcaster
+    to feed a serially connected RTK rover.
+  </p>
+
+  <p><img src="IMG/Figure20.png" width=1000 /></p>
+  <p>Figure 20: BNC pulling a RTCM Version 3 stream to feed a serial connected receiver with observations from a nearby
+    reference station for conventional RTK</p>
+
+  <p>
+  <h4 id="sermount">2.10.1 Mountpoint - optional</h4>
+  </p>
+  <p>
+    Enter a 'Mountpoint' to forward its corresponding stream to a serially connected GNSS receiver.
+  </p>
+  <p>
+    When selecting one of the serial communication options listed below, make sure that you pick those configured to the
+    serially connected receiver.
+  </p>
+
+  <p>
+  <h4 id="serport">2.10.2 Port Name - mandatory if 'Mountpoint' is set</h4>
+  </p>
+  <p>
+    Enter the serial 'Port name' selected on your host for communication with the serially connected receiver.
+    Valid port names are
+  </p>
+  <table>
+    <tr>
+      <td>Windows: </td>
+      <td>&nbsp; COM1, COM2 </td>
+    </tr>
+    <tr>
+      <td>Linux: </td>
+      <td>&nbsp; /dev/ttyS0, /dev/ttyS1 </td>
+    </tr>
+    <tr>
+      <td>FreeBSD: </td>
+      <td>&nbsp; /dev/ttyd0, /dev/ttyd1 </td>
+    </tr>
+    <tr>
+      <td>Digital Unix: </td>
+      <td>&nbsp; /dev/tty01, /dev/tty02 </td>
+    </tr>
+    <tr>
+      <td>HP-UX: </td>
+      <td>&nbsp; /dev/tty1p0, /dev/tty2p0</td>
+    </tr>
+    <tr>
+      <td>SGI/IRIX: </td>
+      <td>&nbsp; /dev/ttyf1, /dev/ttyf2 </td>
+    </tr>
+    <tr>
+      <td>SunOS/Solaris:</td>
+      <td>&nbsp; /dev/ttya, /dev/ttyb </td>
+    </tr>
+  </table>
+  <p>
+    Note that you must plug a serial cable in the port defined here before you start BNC.
+  </p>
+
+  <p>
+  <h4 id="serbaud">2.10.3 Baud Rate - mandatory if 'Mountpoint' is set</h4>
+  </p>
+  <p>
+    Select a 'Baud rate' for the serial output link. Note that using a high baud rate is recommended.
+  </p>
+
+  <p>
+  <h4 id="serflow">2.10.4 Flow Control - mandatory if 'Mountpoint' is set</h4>
+  </p>
+  <p>
+    Select a 'Flow control' for the serial output link. Note that your selection must equal the flow control configured
+    to the serially connected device.
+    Select 'OFF' if you do not know better.
+  </p>
+
+  <p>
+  <h4 id="serparity">2.10.5 Parity - mandatory if 'Mountpoint' is set</h4>
+  </p>
+  <p>
+    Select the 'Parity' for the serial output link. Note that parity is often set to 'NONE'.
+  </p>
+
+  <p>
+  <h4 id="serdata">2.10.6 Data Bits - mandatory if 'Mountpoint' is set</h4>
+  </p>
+  <p>
+    Select the number of 'Data bits' for the serial output link. Note that often '8' data bits are used.
+  </p>
+
+  <p>
+  <h4 id="serstop">2.10.7 Stop Bits - mandatory if 'Mountpoint' is set</h4>
+  </p>
+  <p>
+    Select the number of 'Stop bits' for the serial output link. Note that often '1' stop bit is used.
+  </p>
+
+  <p>
+  <h4 id="serauto">2.10.8 NMEA - mandatory if 'Mountpoint' is set</h4>
+  </p>
+  <p>The 'NMEA' option supports the so-called 'Virtual Reference Station' (VRS) concept which requires the receiver to
+    send
+    approximate position information to the Ntrip Broadcaster. Select 'no' if you do not want BNC to forward or upload
+    any NMEA sentence
+    to the Ntrip broadcaster in support of VRS.
+  </p>
+  <p>
+    Select 'Auto' to automatically forward NMEA sentences of type GGA from your serially connected receiver to the Ntrip
+    broadcaster
+    and/or save them in a file.
+  </p>
+  <p>Select 'Manual GPGGA' or 'Manual GNGGA' if you want BNC to produce and upload GPGGA or GNGGA NMEA sentences to the
+    Ntrip broadcaster
+    because your serially connected receiver does not generate them. A Talker ID 'GP' proceeding the GGA string stands
+    for GPS solutions
+    while a Talker ID 'GN' stands for multi-constellation solutions.
+  </p>
+  <p>
+    Note that selecting 'Auto' or 'Manual' works only for VRS streams which show up under the 'Streams' canvas on BNC's
+    main window
+    with 'nmea' stream attribute set to 'yes'. This attribute is either extracted from the Ntrip broadcaster's
+    source-table or
+    introduced by the user through editing the BNC configuration file.
+  </p>
+
+  <p>
+  <h4 id="serfile">2.10.9 File - optional if 'NMEA' is set to 'Auto'</h4>
+  </p>
+  <p>
+    Specify the full path to a file where NMEA sentences coming from your serially connected receiver are saved.
+    Default is an empty option field, meaning that no NMEA sentences will be saved on disk.
+  </p>
+  <p>
+  <h4 id="serheight">2.10.10 Height - mandatory if 'NMEA' is set to 'Manual'</h4>
+  </p>
+  <p>
+    Specify an approximate 'Height' above mean sea level in meters for the reference station introduced through
+    'Mountpoint'.
+    Together with the latitude and longitude from the Ntrip broadcaster source-table, the height information is used
+    to build GGA sentences to be sent to the Ntrip broadcaster.
+  </p>
+  <p>
+    For adjusting latitude and longitude values of a VRS stream given in the 'Streams' canvas,
+    you can double click the latitude/longitude data fields, specify appropriate values and then hit Enter.
+  </p>
+  <p>
+    This option is only relevant when option 'NMEA' is set to 'Manual GPGGA' or 'Manual GNGGA' respectively.
+  </p>
+
+  <p>
+  <h4 id="sersampl">2.10.11 Sampling - mandatory if 'NMEA' is set to 'Manual'</h4>
+  </p>
+  <p>
+    Select a sampling interval in seconds for manual generation and upload of NMEA GGA sentences.
+  </p>
+  <p>
+    A sampling rate of '0' means that a GGA sentence will be sent only once to initialize the requested VRS stream.
+    Note that some VRS systems need GGA sentences at regular intervals.
+  </p>
+
+  <p>
+  <h4 id="advnote">2.11 Outages</h4>
+  </p>
+  <p>
+    At any time an incoming stream might become unavailable or corrupted. In such cases, it is important that the BNC
+    operator
+    and/or the stream providers become aware of the situation so that measures can be taken to restore the stream.
+    Furthermore, continuous attempts to decode a corrupted stream can generate unnecessary workload for BNC.
+    Outages and corruptions are handled by BNC as follows:
+  </p>
+  <p>
+    <u>Stream outages:</u> BNC considers a connection to be broken when there are no incoming data detected for more
+    than 20 seconds.
+    When this occurs, BNC will try to reconnect at a decreasing rate. It will first try to reconnect with 1 second delay
+    and
+    again in 2 seconds if the previous attempt failed. If the attempt is still unsuccessful, it will try to reconnect
+    within 4 seconds after the previous attempt and so on. The waiting time doubles each time with a maximum of 256
+    seconds.
+  </p>
+  <p>
+    <u>Stream corruption:</u> Not all chunks of bits transferred to BNC's internal decoder may return valid
+    observations.
+    Sometimes several chunks might be needed before the next observation can be properly decoded.
+    BNC buffers all outputs (both valid and invalid) from the decoder for a short time span
+    (size derived from the expected 'Observation rate') to then determine whether a stream is valid or corrupted.
+  </p>
+  <p>
+    Outage and corruption events are reported in the 'Log' tab. They can also be passed on as parameters to a shell
+    script
+    or batch file to generate an advisory note to BNC's operator or affected stream providers.
+    This functionality lets users utilize BNC as a real-time performance monitor and alarm system for a network of GNSS
+    reference stations.
+  </p>
+
+  <p>
+  <h4 id="obsrate">2.11.1 Observation Rate - optional</h4>
+  </p>
+  <p>
+    BNC can collect all returns (success or failure) coming from a decoder within a certain short time span to then
+    decide whether
+    a stream has an outage or its content is corrupted. This procedure needs a rough a priori estimate of the expected
+    observation rate of the incoming streams.
+  </p>
+  <p>An empty option field (default) means that you do not want explicit information from BNC about stream outages and
+    incoming streams that cannot be decoded.
+  </p>
+
+  <p>
+  <h4 id="advfail">2.11.2 Failure Threshold - mandatory if 'Observation rate' is set</h4>
+  </p>
+  <p>
+    Event 'Begin_Failure' will be reported if no data is received continuously for longer than the 'Failure threshold'
+    time.
+    Similarly, event 'Begin_Corrupted' will be reported when corrupted data is detected by the decoder continuously for
+    longer than this 'Failure threshold' time. The default value is set to 15 minutes and is recommended as to not
+    inundate
+    users with too many event reports.
+  </p>
+  <p>
+    Note that specifying a value of zero '0' for the 'Failure threshold' will force BNC to report any stream failure
+    immediately.
+    Note also that for using this function you need to specify the 'Observation rate'.
+  </p>
+
+  <p>
+  <h4 id="advreco">2.11.3 Recovery Threshold - mandatory if 'Observation rate' is set</h4>
+  </p>
+  <p>
+    Once a 'Begin_Failure' or 'Begin_Corrupted' event has been reported, BNC will check when the stream again becomes
+    available or uncorrupted.
+    Event 'End_Failure' or 'End_Corrupted' will be reported as soon as valid observations are detected continuously
+    throughout
+    the 'Recovery threshold' time span. The default value is set to 5 minutes and is recommended as to not inundate
+    users with too many event reports.
+  </p>
+  <p>
+    Note that specifying a value of zero '0' for the 'Recovery threshold' will force BNC to report any stream recovery
+    immediately.
+    Note also that for using this function you need to specify the 'Observation rate'.
+  </p>
+
+  <p>
+  <h4 id="advscript">2.11.4 Script - optional if 'Observation rate' is set</h4>
+  </p>
+  <p>
+    As mentioned before, BNC can trigger a shell script or a batch file to be executed when one of the described events
+    is reported.
+    This script can be used to email an advisory note to network operator or stream providers. To enable this feature,
+    specify the full path to the script or batch file in the 'Script' field. The affected stream's mountpoint and type
+    of event
+    reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script
+    as
+    command line parameters (%1 and %2 on Windows systems or $1 and $2 on Unix/Linux/Mac OS X systems) together with
+    date and time information.
+  </p>
+  <p>
+    Leave the 'Script' field empty if you do not wish to use this option. An invalid path will also disable this option.
+  </p>
+  <p>
+    Examples for command line parameter strings passed on to the advisory 'Script' are:
+  <pre><p style="font-family:Monospace">
    FFMJ00DEU0 Begin_Outage 22-02-21 09:25:59
    FFMJ00DEU0 End_Outage 22-02-21 11:36:02 Begin was 22-02-21 09:25:59
 </p></pre>
-<p>
-Sample script for Unix/Linux/Mac OS X systems:
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    Sample script for Unix/Linux/Mac OS X systems:
+  </p>
+  <pre><p style="font-family:Monospace">
    #!/bin/bash
    sleep $((60*RANDOM/32767))
@@ -3438,42 +5585,51 @@
    mail -s &quot;NABU: $1&quot; email@address &lt; mail.txt
 </p></pre>
-<p>
-Note the sleep command in this script, which causes the system to wait for a random period of up to 60 seconds before sending the email.
-This should avoid overloading your mail server in case of a simultaneous failure of many streams.
-</p>
-
-<p><h4 id="misc">2.12 Miscellaneous</h4></p>
-<p>
-This section describes several miscellaneous options which can be applied to a single stream (mountpoint) or to all configured streams.
-</p>
-
-<p>
-The following figure shows RTCM message numbers and observation types contained in stream 'CUT000AUS0' and the message latencies
-recorded every 2 seconds.
-</p>
-<p><img src="IMG/Figure21.png"width=1000/></p>
-<p>Figure 21: RTCM message numbers, latencies and observation types logged by BNC</p>
-
-
-<p><h4 id="miscmount">2.12.1 Mountpoint - optional </h4></p>
-<p>
-Specify a mountpoint to apply one or several of the 'Miscellaneous' options to the corresponding stream.
-Enter 'ALL' if you want to apply these options to all configured streams. An empty option field (default) means
-that you do not want BNC to apply any of these options.
-</p>
-
-<p><h4 id="miscperf">2.12.2 Log Latency - optional </h4></p>
-<p>
- BNC can average latencies per stream over a certain period of GPS time, the 'Log latency' interval.
- Mean latencies are calculated from the individual latencies of one (first incoming) observation or
- Broadcast Correction per second. The mean latencies are then saved in BNC's logfile.
- Note that computing correct latencies requires the clock of the host computer to be properly synchronized.
- Note further that visualized latencies from the 'Latency' tab on the bottom of the main window represent
- individual latencies and not the mean latencies for the logfile.
-</p>
-<p>
-<b>Latency:</b> Latency is defined in BNC by the following equation:
-</p>
-<pre>
+  <p>
+    Note the sleep command in this script, which causes the system to wait for a random period of up to 60 seconds
+    before sending the email.
+    This should avoid overloading your mail server in case of a simultaneous failure of many streams.
+  </p>
+
+  <p>
+  <h4 id="misc">2.12 Miscellaneous</h4>
+  </p>
+  <p>
+    This section describes several miscellaneous options which can be applied to a single stream (mountpoint) or to all
+    configured streams.
+  </p>
+
+  <p>
+    The following figure shows RTCM message numbers and observation types contained in stream 'CUT000AUS0' and the
+    message latencies
+    recorded every 2 seconds.
+  </p>
+  <p><img src="IMG/Figure21.png" width=1000 /></p>
+  <p>Figure 21: RTCM message numbers, latencies and observation types logged by BNC</p>
+
+
+  <p>
+  <h4 id="miscmount">2.12.1 Mountpoint - optional </h4>
+  </p>
+  <p>
+    Specify a mountpoint to apply one or several of the 'Miscellaneous' options to the corresponding stream.
+    Enter 'ALL' if you want to apply these options to all configured streams. An empty option field (default) means
+    that you do not want BNC to apply any of these options.
+  </p>
+
+  <p>
+  <h4 id="miscperf">2.12.2 Log Latency - optional </h4>
+  </p>
+  <p>
+    BNC can average latencies per stream over a certain period of GPS time, the 'Log latency' interval.
+    Mean latencies are calculated from the individual latencies of one (first incoming) observation or
+    Broadcast Correction per second. The mean latencies are then saved in BNC's logfile.
+    Note that computing correct latencies requires the clock of the host computer to be properly synchronized.
+    Note further that visualized latencies from the 'Latency' tab on the bottom of the main window represent
+    individual latencies and not the mean latencies for the logfile.
+  </p>
+  <p>
+    <b>Latency:</b> Latency is defined in BNC by the following equation:
+  </p>
+  <pre>
     UTC time provided by BNC's host (QDateTime::currentDateTime().toUTC())
   - GPS time of currently processed epoch
@@ -3482,308 +5638,500 @@
   = Latency
 </pre>
-<p>
-<b>Statistics:</b> BNC counts the number of GPS seconds covered by at least one observation.
-It also estimates an observation rate (independent from the a priori specified 'Observation rate')
-from all observations received throughout the first full 'Log latency' interval. Based on this rate,
-BNC estimates the number of data gaps when appearing in subsequent intervals.
-</p>
-<p>
-Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the 'Log' tab
-at the end of each 'Log latency' interval. A typical output from a 1 hour 'Log latency' interval would be:
-</p>
-<pre>
+  <p>
+    <b>Statistics:</b> BNC counts the number of GPS seconds covered by at least one observation.
+    It also estimates an observation rate (independent from the a priori specified 'Observation rate')
+    from all observations received throughout the first full 'Log latency' interval. Based on this rate,
+    BNC estimates the number of data gaps when appearing in subsequent intervals.
+  </p>
+  <p>
+    Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the
+    'Log' tab
+    at the end of each 'Log latency' interval. A typical output from a 1 hour 'Log latency' interval would be:
+  </p>
+  <pre>
 22-11-09 11:59:42 CUT000AUS0 Observations: Mean latency 0.48 sec, min 0.25, max 0.97, rms 0.50, 3600 epochs, 0 gaps
 </pre>
-<p>
-Select a 'Log latency' interval to activate this function or select the empty option field if you do not want BNC
-to log latencies and statistical information.
-</p>
-
-
-<p><h4 id="miscscan">2.12.3 Scan RTCM - optional</h4></p>
-<p>
-When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about
-RTCM message types and observation types. As reliable information concerning stream content should be available e.g.
-for Ntrip Broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for
-incoming message types and printout some of the contained meta-data. Contained observation types are also printed because
-such information is required a priori for the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files.
-</p>
-<p>
-Tick 'Scan RTCM' to scan RTCM Version 2 or 3 streams and log all contained
-</p>
-<ul>
-  <li>Numbers and size of incoming message types</li>
-  <li>Antenna Reference Point (ARP) coordinates</li>
-  <li>Antenna Phase Center (APC) coordinates</li>
-  <li>Antenna height above marker</li>
-  <li>Antenna descriptor.</li>
-</ul>
-In case of RTCM Version 3 streams the output includes
-<ul>
-  <li>RINEX Version 3 Observation types</li>
-</ul>
-</p>
-
-<p>
-Note that in RTCM Version 2 message types 18 and 19 carry only the observables of one frequency.
-Hence it needs two type 18 and 19 messages per epoch to transport observations from dual frequency receivers.
-</p>
-
-<p>
-Please note further that RTCM Version 3 message types 1084 for GLONASS do not contain GLONASS channel numbers.
-The same is true for most of the GLONASS MSM messages, expect for MSM5 and MSM7, where the GLONASS channel number is available
-as extended information. Such observations can only be decoded when you include 1020 GLONASS ephemeris messages to your stream,
-which contain the channels. You could also add another stream carrying 1087 GLONASS observation messages or
-1020 GLONASS ephemeris messages to get the GLONASS channel numbers.
-</p>
-
-<p>
-Logged time stamps refer to message reception time and allow understanding repetition rates.
-Enter 'ALL' if you want to log this information from all configured streams.
-Beware that the size of the logfile can rapidly increase depending on the number of incoming RTCM streams.
-</p>
-<p>This option is primarily meant for test and evaluation. Use it to figure out what exactly is produced
-by a specific GNSS receiver's configuration. An empty option field (default) means that you do not want BNC
-to print message type numbers and antenna information carried in RTCM streams.
-</p>
-
-<p><h4 id="miscport">2.12.4 Port - optional</h4></p>
-<p>
-BNC can output streams related to the above specified 'Mountpoint' through a TCP/IP port of your local host.
-Enter a port number to activate this function. The stream content remains untouched. BNC does not decode or reformat the data for this output.
-If the decoder string is not an accepted one ('RTCM_2.x', 'RTCM_3.x' and 'RTNET'), please change the decoder string to <ul>
-<li> 'ZERO' (forward the raw data) or </li>
-<li> 'ZERO2File' (forward and store the raw data)</li> </ul> in addition.
-</p>
-
-<p>
- An empty option field (default) means that you do not want BNC to apply the TCP/IP port output option.
-</p>
-
-<p><h4 id="pppclient">2.13 PPP Client</h4></p>
-<p>
-BNC can derive coordinates for rover positions following different Precise Point Positioning (PPP) methods:
-<ul>
-  <li>Uncombined PPP for GPS, GLONASS, Galileo and BDS</li>
-  <li>Ionosphere-free PPP for GPS, GLONASS, Galileo and BDS</li>
-  <li>PPP with ambiguity resolution for GPS, Galileo and BDS </li>
-</ul>
-Therefore it uses code data (P), phase data (L) from one or more GNSS.
-Besides pulling streams of observations from a dual frequency GNSS receiver, this
-<ul>
-  <li>Requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of
+  <p>
+    Select a 'Log latency' interval to activate this function or select the empty option field if you do not want BNC
+    to log latencies and statistical information.
+  </p>
+
+
+  <p>
+  <h4 id="miscscan">2.12.3 Scan RTCM - optional</h4>
+  </p>
+  <p>
+    When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details
+    about
+    RTCM message types and observation types. As reliable information concerning stream content should be available e.g.
+    for Ntrip Broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for
+    incoming message types and printout some of the contained meta-data. Contained observation types are also printed
+    because
+    such information is required a priori for the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files.
+  </p>
+  <p>
+    Tick 'Scan RTCM' to scan RTCM Version 2 or 3 streams and log all contained
+  </p>
+  <ul>
+    <li>Numbers and size of incoming message types</li>
+    <li>Antenna Reference Point (ARP) coordinates</li>
+    <li>Antenna Phase Center (APC) coordinates</li>
+    <li>Antenna height above marker</li>
+    <li>Antenna descriptor.</li>
+  </ul>
+  In case of RTCM Version 3 streams the output includes
+  <ul>
+    <li>RINEX Version 3 Observation types</li>
+  </ul>
+  </p>
+
+  <p>
+    Note that in RTCM Version 2 message types 18 and 19 carry only the observables of one frequency.
+    Hence it needs two type 18 and 19 messages per epoch to transport observations from dual frequency receivers.
+  </p>
+
+  <p>
+    Please note further that RTCM Version 3 message types 1084 for GLONASS do not contain GLONASS channel numbers.
+    The same is true for most of the GLONASS MSM messages, expect for MSM5 and MSM7, where the GLONASS channel number is
+    available
+    as extended information. Such observations can only be decoded when you include 1020 GLONASS ephemeris messages to
+    your stream,
+    which contain the channels. You could also add another stream carrying 1087 GLONASS observation messages or
+    1020 GLONASS ephemeris messages to get the GLONASS channel numbers.
+  </p>
+
+  <p>
+    Logged time stamps refer to message reception time and allow understanding repetition rates.
+    Enter 'ALL' if you want to log this information from all configured streams.
+    Beware that the size of the logfile can rapidly increase depending on the number of incoming RTCM streams.
+  </p>
+  <p>This option is primarily meant for test and evaluation. Use it to figure out what exactly is produced
+    by a specific GNSS receiver's configuration. An empty option field (default) means that you do not want BNC
+    to print message type numbers and antenna information carried in RTCM streams.
+  </p>
+
+  <p>
+  <h4 id="miscport">2.12.4 Port - optional</h4>
+  </p>
+  <p>
+    BNC can output streams related to the above specified 'Mountpoint' through a TCP/IP port of your local host.
+    Enter a port number to activate this function. The stream content remains untouched. BNC does not decode or reformat
+    the data for this output.
+    If the decoder string is not an accepted one ('RTCM_2.x', 'RTCM_3.x' and 'RTNET'), please change the decoder string
+    to
+  <ul>
+    <li> 'ZERO' (forward the raw data) or </li>
+    <li> 'ZERO2File' (forward and store the raw data)</li>
+  </ul> in addition.
+  </p>
+
+  <p>
+    An empty option field (default) means that you do not want BNC to apply the TCP/IP port output option.
+  </p>
+
+  <p>
+  <h4 id="pppclient">2.13 PPP Client</h4>
+  </p>
+  <p>
+    BNC can derive coordinates for rover positions following different Precise Point Positioning (PPP) methods:
+  <ul>
+    <li>Uncombined PPP for GPS, GLONASS, Galileo and BDS</li>
+    <li>Ionosphere-free PPP for GPS, GLONASS, Galileo and BDS</li>
+    <li>PPP with ambiguity resolution for GPS, Galileo and BDS </li>
+  </ul>
+  Therefore it uses code data (P), phase data (L) from one or more GNSS.
+  Besides pulling streams of observations from a dual frequency GNSS receiver, this
+  <ul>
+    <li>Requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in
+      the form of
       RTCM-SSR or IGS-SSR messages. Note that for BNC these Broadcast Corrections need to be referred to the satellite's
       Antenna Phase Center (APC). Streams providing such messages are listed on
       <a href="https://igs.bkg.bund.de/ntrip/#rtcm-corr" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-corr</a>
-      Stream 'SSRA00BKG0' (RTCM-SSR) or 'SSRA00BKG1' (IGS-SSR) on Ntrip Broadcaster 'products.igs-ip.net:2101' is an example.</li>
-  <li>May require pulling a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020, 1043, 1044, 1045, 1046, etc..
-      This becomes a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only
+      Stream 'SSRA00BKG0' (RTCM-SSR) or 'SSRA00BKG1' (IGS-SSR) on Ntrip Broadcaster 'products.igs-ip.net:2101' is an
+      example.
+    </li>
+    <li>May require pulling a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020,
+      1043, 1044, 1045, 1046, etc..
+      This becomes a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides
+      them only
       at very low repetition rate. Streams providing such messages are listed on
       <a href="https://igs.bkg.bund.de/ntrip/#rtcm-eph" target="_blank">https://igs.bkg.bund.de/ntrip/#rtcm-eph</a>
-      Stream 'BCEP00BKG0' on caster 'products.igs-ip.net:2101' is an example.</li>
-</ul>
-Note that Broadcast Ephemeris parameters pass a plausibility check in BNC which allows to ignore incorrect or outdated ephemeris data
-when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile. Unhealthy ephemeris data sets are remaining
-and leaving a note 'UNHEALTHY' in the logfile.
-</p>
-When using the PPP option, BNC does correct for:
-<ul>
-  <li>Solid Earth Tides and Phase Windup</li>
-  <li>Satellite Antenna Phase Center offsets and variations</li>
-  <li>Receiver  Antenna Phase Center offsets and variations:
+      Stream 'BCEP00BKG0' on caster 'products.igs-ip.net:2101' is an example.
+    </li>
+  </ul>
+  Note that Broadcast Ephemeris parameters pass a plausibility check in BNC which allows to ignore incorrect or outdated
+  ephemeris data
+  when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile. Unhealthy ephemeris data sets
+  are remaining
+  and leaving a note 'UNHEALTHY' in the logfile.
+  </p>
+  When using the PPP option, BNC does correct for:
+  <ul>
+    <li>Solid Earth Tides and Phase Windup</li>
+    <li>Satellite Antenna Phase Center offsets and variations</li>
+    <li>Receiver Antenna Phase Center offsets and variations:
       Depending on whether or not these corrections are applied, the estimated position is either that of the receiver's
       Antenna Phase Center or that of the receiver's Antenna Reference Point</li>
-  <li>Ocean and atmospheric loading:
-      Atmospheric loading is pretty small but Ocean loading may reach up to about 10 centimeters for coastal stations</li>
-</ul>
-<p>
-Rotational deformation due to polar motion (Polar Tides) is not corrected because this is a small effect usually less than 2 centimeters.
-</p>
-<p>
-The provider of an orbit/clock correction stream may switch with his service at any time from a duty to a backup server installation.
-This shall be noted in the SSR stream through a change of the Issue Of Data (IOD SSR) parameter.
-The PPP option in BNC will immediately reset all ambiguities in such a situation.
-</p>
-<p>
-PPP options are specified in BNC through the following four panels.
-<ul>
-  <li>PPP (1): Input and output, specifying real-time or post processing mode and associated data sources</li>
-  <li>PPP (2): Processing options, specifying general PPP processing options</li>
-  <li>PPP (3): Processed stations, specifying sigmas and noise of a priori coordinates and troposphere paremeters,
-               NMEA stream output and signal priorities</li>
-  <li>PPP (4): Plots, specifying visualization through time series and track maps</li>
-</ul>
-</p>
-
-<p><h4 id="pppInp">2.13.1 PPP (1): Input and Output</h4></p>
-<p>
-This panel provides options for specifying the input and output streams and files required by BNC for real-time or post processing PPP.
-</p>
-<p><img src="IMG/Figure22.png"width=1000/></p>
-<p>Figure 22: Real-time Precise Point Positioning with BNC, PPP Panel 1</p>
-
-<p><h4 id="pppdatasource">2.13.1.1 Data Source - optional</h4></p>
-<p>
-Choose between input from 'Real-time Streams' or 'RINEX Files' for PPP with BNC in real-time or post processing mode.
-</p>
-<p><b>Real-time Streams</b>: When choosing 'Real-time Streams' BNC will do PPP solutions in real-time.
-This requires pulling GNSS observation streams, Broadcast Ephemeris messages and a stream containing corrections to Broadcast Ephemerides.
-Streams with observation and navigation data have to be in RTCM Version 3 format. Correction streams have to be in RTCM-SSR or IGS-SSR format.
-If you do not pull Broadcast Corrections, BNC will switch with its solution to 'Single Point Positioning' (SPP) mode.
-</p>
-<p><b>RINEX Files</b>: This input mode allows to specify RINEX Observation, RINEX Navigation and Broadcast Correction files.
-BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats.
-Files carrying Broadcast Corrections must have the format produced by BNC through the 'Broadcast Corrections' panel.
-Specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Correction file leads BNC to a
-'Single Point Positioning' (SPP) solution.
-<p>
-The following type of Broadcast navigation messages is used per individulal GNSS:</p>
-      <table>
-		<tr><td>Navigation 		</td><td>Description							</td><td>Constellation  		</td><td>RTCM </td></tr>
-		<tr><td>Message Type	</td><td>										</td><td>and Signal 			</td><td>Message Type</td></tr>
-		<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-		<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-		<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-		<tr><td>LNAV</td><td>			GPS Legacy navigation message			</td><td>GPS  L1 C/A           	</td><td>1019</td></tr>
-		<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-		<tr><td>FDMA</td><td>			GLONASS Legacy FDMA navigation message	</td><td>GLO L1 C/A			 	</td><td>1020</td></tr>
-		<tr><td>	</td><td>	        from M-satellites     					</td><td>			          	</td><td>	 </td></tr>
-		<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-		<tr><td>INAV</td><td>			Galileo Integrity 	navigation message 	</td><td>GAL E1, E5b        	</td><td>1046</td></tr>
-		<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-		<tr><td>D1	</td><td>			BeiDou-2/3 MEO/IGSO navigation message 	</td><td>BDS B1I, B2I, B3I  	</td><td>1042</td></tr>
-		<tr><td>D2	</td><td>			BeiDou-2/3 GEO      navigation message 	</td><td>BDS B1I, B2I, B3I 		</td><td>1042</td></tr>
-		</table>
-<p>
-Note that for debugging purposes, BNC's real-time PPP functionality can also be used offline.
-Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations,
-orbit and clock correctors, and Broadcast Ephemeris. Example:</p>
-<pre>
+    <li>Ocean and atmospheric loading:
+      Atmospheric loading is pretty small but Ocean loading may reach up to about 10 centimeters for coastal stations
+    </li>
+  </ul>
+  <p>
+    Rotational deformation due to polar motion (Polar Tides) is not corrected because this is a small effect usually
+    less than 2 centimeters.
+  </p>
+  <p>
+    The provider of an orbit/clock correction stream may switch with his service at any time from a duty to a backup
+    server installation.
+    This shall be noted in the SSR stream through a change of the Issue Of Data (IOD SSR) parameter.
+    The PPP option in BNC will immediately reset all ambiguities in such a situation.
+  </p>
+  <p>
+    PPP options are specified in BNC through the following four panels.
+  <ul>
+    <li>PPP (1): Input and output, specifying real-time or post processing mode and associated data sources</li>
+    <li>PPP (2): Processing options, specifying general PPP processing options</li>
+    <li>PPP (3): Processed stations, specifying sigmas and noise of a priori coordinates and troposphere paremeters,
+      NMEA stream output and signal priorities</li>
+    <li>PPP (4): Plots, specifying visualization through time series and track maps</li>
+  </ul>
+  </p>
+
+  <p>
+  <h4 id="pppInp">2.13.1 PPP (1): Input and Output</h4>
+  </p>
+  <p>
+    This panel provides options for specifying the input and output streams and files required by BNC for real-time or
+    post processing PPP.
+  </p>
+  <p><img src="IMG/Figure22.png" width=1000 /></p>
+  <p>Figure 22: Real-time Precise Point Positioning with BNC, PPP Panel 1</p>
+
+  <p>
+  <h4 id="pppdatasource">2.13.1.1 Data Source - optional</h4>
+  </p>
+  <p>
+    Choose between input from 'Real-time Streams' or 'RINEX Files' for PPP with BNC in real-time or post processing
+    mode.
+  </p>
+  <p><b>Real-time Streams</b>: When choosing 'Real-time Streams' BNC will do PPP solutions in real-time.
+    This requires pulling GNSS observation streams, Broadcast Ephemeris messages and a stream containing corrections to
+    Broadcast Ephemerides.
+    Streams with observation and navigation data have to be in RTCM Version 3 format. Correction streams have to be in
+    RTCM-SSR or IGS-SSR format.
+    If you do not pull Broadcast Corrections, BNC will switch with its solution to 'Single Point Positioning' (SPP)
+    mode.
+  </p>
+  <p><b>RINEX Files</b>: This input mode allows to specify RINEX Observation, RINEX Navigation and Broadcast Correction
+    files.
+    BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats.
+    Files carrying Broadcast Corrections must have the format produced by BNC through the 'Broadcast Corrections' panel.
+    Specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Correction file leads BNC to a
+    'Single Point Positioning' (SPP) solution.
+  <p>
+    The following type of Broadcast navigation messages is used per individulal GNSS:</p>
+  <table>
+    <tr>
+      <td>Navigation </td>
+      <td>Description </td>
+      <td>Constellation </td>
+      <td>RTCM </td>
+    </tr>
+    <tr>
+      <td>Message Type </td>
+      <td> </td>
+      <td>and Signal </td>
+      <td>Message Type</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>LNAV</td>
+      <td> GPS Legacy navigation message </td>
+      <td>GPS L1 C/A </td>
+      <td>1019</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>FDMA</td>
+      <td> GLONASS Legacy FDMA navigation message </td>
+      <td>GLO L1 C/A </td>
+      <td>1020</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> from M-satellites </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>INAV</td>
+      <td> Galileo Integrity navigation message </td>
+      <td>GAL E1, E5b </td>
+      <td>1046</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>D1 </td>
+      <td> BeiDou-2/3 MEO/IGSO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td>D2 </td>
+      <td> BeiDou-2/3 GEO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+  </table>
+  <p>
+    Note that for debugging purposes, BNC's real-time PPP functionality can also be used offline.
+    Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations,
+    orbit and clock correctors, and Broadcast Ephemeris. Example:</p>
+  <pre>
 	Windows: bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\RAW
 </pre>
-Such a file (here: 'RAW') must be saved beforehand using BNC's 'Raw output file' option.
-</p>
-<p><h4 id="pppcorrstream">2.13.1.2 Corrections Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4></p>
-<p>
-Specify a Broadcast 'Corrections stream' from the list of selected 'Streams' you are pulling if you want BNC to correct your
-satellite ephemeris and observations accordingly. Note that the stream's orbit and clock corrections must refer to the
-satellite Antenna Phase Center (APC). Streams providing such corrections are made available e.g. through the
-International GNSS Service (IGS) and can for example be be pulled from <a href="https://products.igs-ip.net" target="_blank">https://products.igs-ip.net</a>
-The stream format must be RTCM-SSR or IGS-SSR containing so-called SSR messages. Streams 'SSRA03IGS1' and 'SSRA00BKG1' are examples
-using the IGS-SSR format.
-If you do not specify a 'Corrections stream', BNC will fall back from a PPP solution to a Single Point Positioning (SPP) solution.
-</p>
-<p><h4 id="pppcorrfile">2.13.1.3 Corrections File - optional if 'Data source' is set to 'RINEX Files'</h4></p>
-<p>
-Specify a Broadcast 'Corrections file' as saved beforehand using BNC. The file content is basically the ASCII representation of a
-RTCM-SSR or a IGS-SSR Broadcast Correction stream. If you do not specify a 'Correction file', BNC will fall back from a PPP solution
-to a Single Point Positioning (SPP) solution.
-</p>
-<p><h4 id="pppbiasstream">2.13.1.4 Biases Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4></p>
-<p>
-Specify a 'Biases stream' which provides satellite biases in SSR format from the list of selected 'Streams' you are pulling
-if you want BNC to correct your observations accordingly. Streams providing such satellite biases are made available e.g. through the
-International GNSS Service (IGS) and can for example be be pulled from <a href="https://products.igs-ip.net" target="_blank">https://products.igs-ip.net</a>
-The stream format must be RTCM-SSR or IGS-SSR containing so-called SSR messages. Streams 'OSBC00WHU1' is an example using the IGS-SSR format.
-If you do not specify a 'Biases stream' via this option, BNC will use satellite biases from the Corrections stream 'mountpoint',
-if available.
-</p>
-<p><h4 id="pppbiasfile">2.13.1.5 Biases File - optional if 'Data source' is set to 'RINEX Files'</h4></p>
-<p>
-Specify a 'Biases file' as saved beforehand using BNC. The file content is basically the ASCII representation of a
-RTCM-SSR or a IGS-SSR Biases stream.
-</p>
-<p><h4 id="pppionostream">2.13.1.6 Ionosphere Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4></p>
-<p>
-Specify a 'Ionosphere stream' which provides VTEC informations in SSR format from the list of selected 'Streams' you are pulling
-if you want BNC to correct your observations accordingly. Streams providing such VTEC informations are made available e.g. through the
-International GNSS Service (IGS) and can for example be be pulled from <a href="https://products.igs-ip.net" target="_blank">https://products.igs-ip.net</a>
-The stream format must be RTCM-SSR or IGS-SSR containing so-called SSR messages. Streams 'IONO00IGS1' and 'IONO00UPC1' are examples
-using the IGS-SSR format.
-If you do not specify a 'Ionosphere stream' via this option, BNC will use VTEC informations from the Corrections stream 'mountpoint',
-if available.
-</p>
-<p><h4 id="pppionofile">2.13.1.7 Ionosphere File - optional if 'Data source' is set to 'RINEX Files'</h4></p>
-<p>
-Specify a 'Ionosphere file' as saved beforehand using BNC. The file content is basically the ASCII representation of a
-RTCM-SSR or a IGS-SSR Ionosphere stream.
-</p>
-<p><h4 id="ppprnxobs">2.13.1.8 RINEX Observation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p>
-<p>
-Specify a RINEX Observation file. The file format can be RINEX Version 2, RINEX Version 3 or RINEX Version 4.
-</p>
-<p><h4 id="ppprnxnav">2.13.1.9 RINEX Navigation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p>
-<p>
-Specify a RINEX Navigation file.The file format can be RINEX Version 2, RINEX Version 3 or RINEX Version 4.
-</p>
-<p><h4 id="pppantexfile">2.13.1.10 ANTEX File - optional</h4></p>
-<p>
-IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX format Version 1.4
-(at <a href="https://kb.igs.org/hc/en-us/articles/216104678-ANTEX-format-description" target="_blank">https://kb.igs.org/hc/en-us/articles/216104678-ANTEX-format-description/</a>).
-Such so-called ANTEX files are available from IGS through
-at <a href="https://files.igs.org/pub/station/general/" target="_blank">https://files.igs.org/pub/station/general/</a>.
-An example ANTEX file 'igs20.atx' is part of the BNC package for convenience.
-</p>
-<p>
-Entering the full path to such an ANTEX file is required for correcting observations in PPP for Antenna Phase Center offsets
-and variations. Note that for applying such corrections you need to specify the receiver's antenna name and radome in BNC's 'Coordinates file'.
-</p>
-<p>
-Default value for 'ANTEX file' is an empty option field, meaning that you do not want to correct observations for
-Antenna Phase Center offsets and variations.
-</p>
-<p><h4 id="pppmarkcoor">2.13.1.11 Coordinates File - optional </h4></p>
-<p>
-Enter the full path to an ASCII file which specifies all observation streams or files from stationary or mobile receivers
-you possibly may want to process.
-</p>
-<p>
-Specifying a 'Coordinates file' is optional. If it exists, it should contain one record per stream or file
-with the following parameters separated by blank characters:
-</p>
-<ul>
-  <li>Input data source, to be specified either through
+  Such a file (here: 'RAW') must be saved beforehand using BNC's 'Raw output file' option.
+  </p>
+  <p>
+  <h4 id="pppcorrstream">2.13.1.2 Corrections Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4>
+  </p>
+  <p>
+    Specify a Broadcast 'Corrections stream' from the list of selected 'Streams' you are pulling if you want BNC to
+    correct your
+    satellite ephemeris and observations accordingly. Note that the stream's orbit and clock corrections must refer to
+    the
+    satellite Antenna Phase Center (APC). Streams providing such corrections are made available e.g. through the
+    International GNSS Service (IGS) and can for example be be pulled from <a href="https://products.igs-ip.net"
+      target="_blank">https://products.igs-ip.net</a>
+    The stream format must be RTCM-SSR or IGS-SSR containing so-called SSR messages. Streams 'SSRA03IGS1' and
+    'SSRA00BKG1' are examples
+    using the IGS-SSR format.
+    If you do not specify a 'Corrections stream', BNC will fall back from a PPP solution to a Single Point Positioning
+    (SPP) solution.
+  </p>
+  <p>
+  <h4 id="pppcorrfile">2.13.1.3 Corrections File - optional if 'Data source' is set to 'RINEX Files'</h4>
+  </p>
+  <p>
+    Specify a Broadcast 'Corrections file' as saved beforehand using BNC. The file content is basically the ASCII
+    representation of a
+    RTCM-SSR or a IGS-SSR Broadcast Correction stream. If you do not specify a 'Correction file', BNC will fall back
+    from a PPP solution
+    to a Single Point Positioning (SPP) solution.
+  </p>
+  <p>
+  <h4 id="pppbiasstream">2.13.1.4 Biases Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4>
+  </p>
+  <p>
+    Specify a 'Biases stream' which provides satellite biases in SSR format from the list of selected 'Streams' you are
+    pulling
+    if you want BNC to correct your observations accordingly. Streams providing such satellite biases are made available
+    e.g. through the
+    International GNSS Service (IGS) and can for example be be pulled from <a href="https://products.igs-ip.net"
+      target="_blank">https://products.igs-ip.net</a>
+    The stream format must be RTCM-SSR or IGS-SSR containing so-called SSR messages. Streams 'OSBC00WHU1' is an example
+    using the IGS-SSR format.
+    If you do not specify a 'Biases stream' via this option, BNC will use satellite biases from the Corrections stream
+    'mountpoint',
+    if available.
+  </p>
+  <p>
+  <h4 id="pppbiasfile">2.13.1.5 Biases File - optional if 'Data source' is set to 'RINEX Files'</h4>
+  </p>
+  <p>
+    Specify a 'Biases file' as saved beforehand using BNC. The file content is basically the ASCII representation of a
+    RTCM-SSR or a IGS-SSR Biases stream.
+  </p>
+  <p>
+  <h4 id="pppionostream">2.13.1.6 Ionosphere Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4>
+  </p>
+  <p>
+    Specify a 'Ionosphere stream' which provides VTEC informations in SSR format from the list of selected 'Streams' you
+    are pulling
+    if you want BNC to correct your observations accordingly. Streams providing such VTEC informations are made
+    available e.g. through the
+    International GNSS Service (IGS) and can for example be be pulled from <a href="https://products.igs-ip.net"
+      target="_blank">https://products.igs-ip.net</a>
+    The stream format must be RTCM-SSR or IGS-SSR containing so-called SSR messages. Streams 'IONO00IGS1' and
+    'IONO00UPC1' are examples
+    using the IGS-SSR format.
+    If you do not specify a 'Ionosphere stream' via this option, BNC will use VTEC informations from the Corrections
+    stream 'mountpoint',
+    if available.
+  </p>
+  <p>
+  <h4 id="pppionofile">2.13.1.7 Ionosphere File - optional if 'Data source' is set to 'RINEX Files'</h4>
+  </p>
+  <p>
+    Specify a 'Ionosphere file' as saved beforehand using BNC. The file content is basically the ASCII representation of
+    a
+    RTCM-SSR or a IGS-SSR Ionosphere stream.
+  </p>
+  <p>
+  <h4 id="ppprnxobs">2.13.1.8 RINEX Observation File - mandatory if 'Data source' is set to 'RINEX Files'</h4>
+  </p>
+  <p>
+    Specify a RINEX Observation file. The file format can be RINEX Version 2, RINEX Version 3 or RINEX Version 4.
+  </p>
+  <p>
+  <h4 id="ppprnxnav">2.13.1.9 RINEX Navigation File - mandatory if 'Data source' is set to 'RINEX Files'</h4>
+  </p>
+  <p>
+    Specify a RINEX Navigation file.The file format can be RINEX Version 2, RINEX Version 3 or RINEX Version 4.
+  </p>
+  <p>
+  <h4 id="pppantexfile">2.13.1.10 ANTEX File - optional</h4>
+  </p>
+  <p>
+    IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX
+    format Version 1.4
+    (at <a href="https://kb.igs.org/hc/en-us/articles/216104678-ANTEX-format-description"
+      target="_blank">https://kb.igs.org/hc/en-us/articles/216104678-ANTEX-format-description/</a>).
+    Such so-called ANTEX files are available from IGS through
+    at <a href="https://files.igs.org/pub/station/general/"
+      target="_blank">https://files.igs.org/pub/station/general/</a>.
+    An example ANTEX file 'igs20.atx' is part of the BNC package for convenience.
+  </p>
+  <p>
+    Entering the full path to such an ANTEX file is required for correcting observations in PPP for Antenna Phase Center
+    offsets
+    and variations. Note that for applying such corrections you need to specify the receiver's antenna name and radome
+    in BNC's 'Coordinates file'.
+  </p>
+  <p>
+    Default value for 'ANTEX file' is an empty option field, meaning that you do not want to correct observations for
+    Antenna Phase Center offsets and variations.
+  </p>
+  <p>
+  <h4 id="pppmarkcoor">2.13.1.11 Coordinates File - optional </h4>
+  </p>
+  <p>
+    Enter the full path to an ASCII file which specifies all observation streams or files from stationary or mobile
+    receivers
+    you possibly may want to process.
+  </p>
+  <p>
+    Specifying a 'Coordinates file' is optional. If it exists, it should contain one record per stream or file
+    with the following parameters separated by blank characters:
+  </p>
   <ul>
-    <li>the 'Mountpoint' of an RTCM stream (when in real-time PPP mode), or</li>
-    <li>the first four (RINEX Version 2) or nine (RINEX Version 3 and 4) characters of the RINEX observations file (when in post processing PPP mode).</li>
-  </ul>
-      Having at least this first parameter in each record is mandatory.</li><br>
-  <li>For static observations from a stationary receiver an approximate a priori XYZ coordinate [m] of the station's marker should be specified. <br>
-      If such an approximate a priori XYZ coordinate is unknown or when observations come from a mobile receiver, '0.0 0.0 0.0' shall be used instead.</li>
+    <li>Input data source, to be specified either through
+      <ul>
+        <li>the 'Mountpoint' of an RTCM stream (when in real-time PPP mode), or</li>
+        <li>the first four (RINEX Version 2) or nine (RINEX Version 3 and 4) characters of the RINEX observations file
+          (when in post processing PPP mode).</li>
+      </ul>
+      Having at least this first parameter in each record is mandatory.
+    </li><br>
+    <li>For static observations from a stationary receiver an approximate a priori XYZ coordinate [m] of the station's
+      marker should be specified. <br>
+      If such an approximate a priori XYZ coordinate is unknown or when observations come from a mobile receiver, '0.0
+      0.0 0.0' shall be used instead.</li>
+    <br>
+    <li>Optionally, right after the a priori XYZ coordinate, its reference epoch and ITRF velocity may be specified
+      through the keyword tokens
+      <span style="font-family:Monospace">EPOCH:&lt;decimalYear&gt;</span> and
+      <span style="font-family:Monospace">VEL:&lt;vx&gt;,&lt;vy&gt;,&lt;vz&gt;</span>
+      (in any order, separated by blank characters). <span style="font-family:Monospace">&lt;decimalYear&gt;</span> is
+      the epoch the a priori
+      coordinate refers to (e.g. '2026.5'), and <span
+        style="font-family:Monospace">&lt;vx&gt;,&lt;vy&gt;,&lt;vz&gt;</span> is the station's
+      ITRF velocity in X, Y, Z [m/year], comma-separated without blanks (e.g. 'VEL:-0.0142,0.0187,0.0091'). When
+      'EPOCH:' is specified, BNC
+      propagates the a priori coordinate from its reference epoch to the actual observation epoch using the given
+      velocity before using it,
+      which accounts for the station's tectonic motion between the coordinate's reference epoch and the time of
+      processing.
+      <ul>
+        <li> Every SINEX (including IGS cumulative solutions) states epochs in
+          YY:DOY:SOD format (2-digit year : day-of-year : seconds-of-day) — in the
+          %=SNX header line and/or the SOLUTION/EPOCHS block, e.g.: 26:048:00000<br>
+          Convert directly: decimalYear = YYYY + (DOY - 1 + SOD/86400) / 365.25.
+          (For 26:048:00000 → 2026 + 47/365.25 = 2026.1287)
+        </li>
+      </ul>
       <br>
-  <li>The North, East and Up component [m] of antenna eccentricity, which is the difference between the Antenna Reference Point (ARP)
+      Leave out 'EPOCH:' and 'VEL:' if the a priori coordinate is already valid for the epoch of processing, or if the
+      station's ITRF velocity is unknown;
+      in that case the a priori coordinate is used unchanged, as before.
+    </li>
+    <br>
+    <li>The North, East and Up component [m] of antenna eccentricity, which is the difference between the Antenna
+      Reference Point (ARP)
       and a nearby marker position, can be specified.<br>
-      Please note, when specifying the antenna eccentricity, BNC will produce coordinates referring to the marker position and not referring to the ARP.<br>
-      If the eccentricity is unknown or the ARP itself is understood as the marker, '0.0 0.0 0.0' shall be specified instead.</li>
-      <br>
-  <li>Receiver's antenna name as defined in your ANTEX file (see below).
-      The specified name must consist of 20 characters. Add trailing blanks if the antenna name has less than 20 characters. <br>Examples:<br>
-  	<pre><p style="font-family:Monospace">
+      Please note, when specifying the antenna eccentricity, BNC will produce coordinates referring to the marker
+      position and not referring to the ARP.<br>
+      If the eccentricity is unknown or the ARP itself is understood as the marker, '0.0 0.0 0.0' shall be specified
+      instead.</li>
+    <br>
+    <li>Receiver's antenna name as defined in your ANTEX file (see below).
+      The specified name must consist of 20 characters. Add trailing blanks if the antenna name has less than 20
+      characters. <br>Examples:<br>
+      <pre><p style="font-family:Monospace">
 		&nbsp;'JPSREGANT_SD_E      ' (no radome)
 		&nbsp;'LEIAT504        NONE' (no radome)
 		&nbsp;'LEIAR25.R3      LEIT' (radome is LEIT)
 	</p></pre>
-	  Observations will be corrected for the receiver Antenna Phase Center (APC) offsets and variations.<br>
-      Leave antenna name blank if you do not want to correct observations for APC offsets and variations or if you do not know the antenna name.</li>
-      <br>
-  <li>Receiver type following the naming convention for IGS equipment as defined in
-      <a href="https://files.igs.org/pub/station/general/rcvr_ant.tab" target="_blank">https://files.igs.org/pub/station/general/rcvr_ant.tab</a>.<br>
-   <li>Specifying the receiver type is only required when saving SINEX Troposphere files. In those files it becomes part of the 'SITE/RECEIVER' specifications,
-       see section 'SNX TRO Directory'.</li>
-</ul>
-<p>
-Records in the 'Coordinates' file with exclamation mark '!' in the first column or blank records will be understood as comment lines and ignored.
-</p>
-<p>
-The following is the content of an example 'Coordinates file'. Here each record describes the mountpoint of a stream
-available from the global IGS real-time reference station network.
-A priori coordinates are followed by North/East/Up eccentricity components of the ARP,
-followed by the antenna name and radome in use, and followed by the receiver name.
-</p>
-<pre><p style="font-family:Monospace">
+      Observations will be corrected for the receiver Antenna Phase Center (APC) offsets and variations.<br>
+      Leave antenna name blank if you do not want to correct observations for APC offsets and variations or if you do
+      not know the antenna name.
+    </li>
+    <br>
+    <li>Receiver type following the naming convention for IGS equipment as defined in
+      <a href="https://files.igs.org/pub/station/general/rcvr_ant.tab"
+        target="_blank">https://files.igs.org/pub/station/general/rcvr_ant.tab</a>.<br>
+    <li>Specifying the receiver type is only required when saving SINEX Troposphere files. In those files it becomes
+      part of the 'SITE/RECEIVER' specifications,
+      see section 'SNX TRO Directory'.</li>
+  </ul>
+  <p>
+    Records in the 'Coordinates' file with exclamation mark '!' in the first column or blank records will be understood
+    as comment lines and ignored.
+  </p>
+  <p>
+    The following is the content of an example 'Coordinates file'. Here each record describes the mountpoint of a stream
+    available from the global IGS real-time reference station network.
+    A priori coordinates are followed by North/East/Up eccentricity components of the ARP,
+    followed by the antenna name and radome in use, and followed by the receiver name.
+  </p>
+  <pre><p style="font-family:Monospace">
 # Apriori coordinates with eccentricities, antenna and receiver, Reference System IGS20 (IGS0OPSSNX_20260480000_01D_01D_CRD.SNX)
 # ---------------------------------------------------------------------------------------------------------------------------------
-# REAL-TIME 
+# REAL-TIME
 FFMJ01DEU0  4.05345556487862e+06  6.17730016327370e+05  4.86939592304988e+06    0.0000   0.0000   0.0450 LEIAR25.R3      LEIT LEICA GR50
+WTZR00DEU1  4.07558020555194e+06  9.31854158691225e+05  4.80156833793210e+06 EPOCH:2026.5 VEL:-0.0142,0.0187,0.0091    0.0000   0.0000   0.0710 LEIAR25.R3      LEIT LEICA GR50
 REYK00ISL0  2.58738387057569e+06 -1.04303361185251e+06  5.71656422200577e+06    0.0000   0.0000   0.0635 LEIAR25.R4      LEIT LEICA GR50
 WTZR00DEU0  4.07558020555194e+06  9.31854158691225e+05  4.80156833793210e+06    0.0000   0.0000   0.0710 LEIAR25.R3      LEIT LEICA GR50
@@ -3797,34 +6145,46 @@
 VM01            0.0            0.0            0.0          0.0000     0.0000     0.0000
 </p></pre>
-In this file
-<ul>
-  <li> Record 'FFMJ01DEU0' describes a stream from a stationary receiver with known a priori marker coordinates, antenna eccentricities,
-       antenna and radome type, and receiver type.</li>
-  <li> Record 'FFMJ01DEU' indicates that a RINEX version 3 or 4 observations file for post processing PPP is available for station 'FFMJ01DEU'
-       with known a priori marker coordinates, antenna eccentricities, antenna and radome type, and receiver type.</li>
-  <li> The 4-character station ID 'VM01' indicates that a RINEX version 2 observations file, resultant from a mobile rover receiver,
-       is available for post processing PPP. Hence a priori coordinates are unknown although antenna eccentricities, antenna and radome type,
-       and receiver type are known.</li>
-</ul>
-<p>
-Note again that the only mandatory parameters in this file are the 'Station' parameters in the first column,
-each standing for an observation stream's mountpoint or the 9/4-character station ID of a RINEX filename.
-</p>
-
-<p><h4 id="pppblqfile">2.13.1.12 BLQ File - optional </h4></p>
-<p>
-Specify a 'BLQ file' containing the ocean loading coefficients for all stations you want to process.
-These coefficients can be obtained from the ocean loading service under request trough the web site
-<a href="http://holt.oso.chalmers.se/loading/" target="_blank">http://holt.oso.chalmers.se/loading/</a>
- .
-BNC computes time series of tidal displacements for the respective stations using that input file.
-</p>
-
-
-<p><h4 id="ppplogfile">2.13.1.13 Logfile Directory and Log mode - optional</h4></p>
-<p>
-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):
-<pre><p style="font-family:Monospace">
+  In this file
+  <ul>
+    <li> Record 'FFMJ01DEU0' describes a stream from a stationary receiver with known a priori marker coordinates,
+      antenna eccentricities,
+      antenna and radome type, and receiver type.</li>
+    <li> Record 'WTZR00DEU1' additionally specifies the reference epoch ('2026.5') and ITRF velocity of its a priori
+      marker coordinate.
+      BNC will propagate that coordinate to the epoch of each processed observation before using it.</li>
+    <li> Record 'FFMJ01DEU' indicates that a RINEX version 3 or 4 observations file for post processing PPP is available
+      for station 'FFMJ01DEU'
+      with known a priori marker coordinates, antenna eccentricities, antenna and radome type, and receiver type.</li>
+    <li> The 4-character station ID 'VM01' indicates that a RINEX version 2 observations file, resultant from a mobile
+      rover receiver,
+      is available for post processing PPP. Hence a priori coordinates are unknown although antenna eccentricities,
+      antenna and radome type,
+      and receiver type are known.</li>
+  </ul>
+  <p>
+    Note again that the only mandatory parameters in this file are the 'Station' parameters in the first column,
+    each standing for an observation stream's mountpoint or the 9/4-character station ID of a RINEX filename.
+  </p>
+
+  <p>
+  <h4 id="pppblqfile">2.13.1.12 BLQ File - optional </h4>
+  </p>
+  <p>
+    Specify a 'BLQ file' containing the ocean loading coefficients for all stations you want to process.
+    These coefficients can be obtained from the ocean loading service under request trough the web site
+    <a href="http://holt.oso.chalmers.se/loading/" target="_blank">http://holt.oso.chalmers.se/loading/</a>
+    .
+    BNC computes time series of tidal displacements for the respective stations using that input file.
+  </p>
+
+
+  <p>
+  <h4 id="ppplogfile">2.13.1.13 Logfile Directory and Log mode - optional</h4>
+  </p>
+  <p>
+    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):
+  <pre><p style="font-family:Monospace">
 ...
 26-07-28 15:06:51 2026-07-28_15:06:45.000 FFMJ01DEU0 X = 4053455.5855 Y = 617730.0277 Z = 4869395.9163 NEU:  -0.0213  +0.0081  +0.0090 TRP:  +2.3453  +0.0951 fix +96 %
@@ -3840,18 +6200,25 @@
 ...
 </p></pre>
-<p>
-Each row reports the PPP result of one epoch. It begins with a UTC time stamp (yy-mm-dd hh:mm:ss) which tells us when the result was produced.
-A second time stamp (yyyy-mm-dd_hh:mm:ss) describes the PPP's epoch in 'GPS Time'. It is followed by the Mountpoint/Stream/Station Name, the derived XYZ position in [m],
-its North, East and Up displacement, compared to an introduced a priori coordinate, the estimated tropospheric delay [m] (model plus correction) 
-and a remark regarding the status of the ambiguities (flt/fix with its percentile).
-</p>
-<p>
-If you require more information, you can specify a 'Logfile directory' to save daily logfiles per station (filename suffix 'ppp')
-with additional processing details on disk. The details of the PPP client processing output can be controled by the 'log mode' option.
-The 'normal' mode produces a log file, related to the estimated parameters and observation residuals as printed below.
-If the user selects 'debug' additional information (particularly about used SSR corrections) is printed.
-The option value 'all' triggers a very detailed log including the information about the constituents of the observation model.
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    Each row reports the PPP result of one epoch. It begins with a UTC time stamp (yy-mm-dd hh:mm:ss) which tells us
+    when the result was produced.
+    A second time stamp (yyyy-mm-dd_hh:mm:ss) describes the PPP's epoch in 'GPS Time'. It is followed by the
+    Mountpoint/Stream/Station Name, the derived XYZ position in [m],
+    its North, East and Up displacement, compared to an introduced a priori coordinate, the estimated tropospheric delay
+    [m] (model plus correction)
+    and a remark regarding the status of the ambiguities (flt/fix with its percentile).
+  </p>
+  <p>
+    If you require more information, you can specify a 'Logfile directory' to save daily logfiles per station (filename
+    suffix 'ppp')
+    with additional processing details on disk. The details of the PPP client processing output can be controled by the
+    'log mode' option.
+    The 'normal' mode produces a log file, related to the estimated parameters and observation residuals as printed
+    below.
+    If the user selects 'debug' additional information (particularly about used SSR corrections) is printed.
+    The option value 'all' triggers a very detailed log including the information about the constituents of the
+    observation model.
+  </p>
+  <pre><p style="font-family:Monospace">
 ..
 PPP of Epoch 2026-07-28_15:12:14.000 using SSRA01CAS1
@@ -4187,47 +6554,82 @@
 ..
 </p></pre>
-<p>
- Depending on the selected processing options you find 'GPS Time' stamps (yyyy-mm-dd_hh:mm:ss.sss) followed by
- <table>
-  <tr><td>&nbsp; SATNUM G    </td><td>&nbsp; &nbsp; Number of satellites per contributing GNSS, here GPS</td></tr>
-  <tr><td>&nbsp; RES cG1/lG1 </td><td>&nbsp; &nbsp; Code and phase residuals for contributing GNSS in [m] given per satellite</td></tr>
-  <tr><td>&nbsp; REC_CLK  G  </td><td>&nbsp; &nbsp; Receiver clock errors per contributing GNSS, here GPS in [m]</td></tr>
-  <tr><td>&nbsp; TRP         </td><td>&nbsp; &nbsp; A priori and correction values of tropospheric zenith delay in [m]</td></tr>
-  <tr><td>&nbsp; ION         </td><td>&nbsp; &nbsp; A priori and correction values of ionospheric delay in [m]</td></tr>
-  <tr><td>&nbsp; AMB lG1     </td><td>&nbsp; &nbsp; Floated/fixed ambiguities given per satellite and frequency band with 'nEpo' = number of epochs since last ambiguity reset</td></tr>
-  <tr><td>&nbsp; BIA cG1     </td><td>&nbsp; &nbsp; Satellite code/phase bias related to GNSS and frequency band in [m], here code bias for GPS and band 1</td></tr>
-  <tr><td>&nbsp; MOUNTPOINT  </td><td>&nbsp; &nbsp; Here 'FFMJ01DEU0' with XYZ position in [m], dN/dE/dU in [m] for North, East, and Up displacements compared to a priori marker coordinates)</td></tr>
-  <tr><td>&nbsp;             </td><td>&nbsp; &nbsp; as well as a remark regarding the status of the ambiguities (flt/fix with its percentile)</td></tr>
-</table>
-<p>
-Estimated parameters are presented together with their formal errors as derived from the implemented filter.
-The PPP algorithm includes outlier and cycle slip detection.
-</p>
-
-<p>
-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.
-</p>
-<p>
-BNC follows the RINEX Version 3 standard to create filenames for PPP logfiles (suffix 'ppp'), see section 'RINEX Filenames' for details:
-For example:
-<pre><p style="font-family:Monospace">
+  <p>
+    Depending on the selected processing options you find 'GPS Time' stamps (yyyy-mm-dd_hh:mm:ss.sss) followed by
+  <table>
+    <tr>
+      <td>&nbsp; SATNUM G </td>
+      <td>&nbsp; &nbsp; Number of satellites per contributing GNSS, here GPS</td>
+    </tr>
+    <tr>
+      <td>&nbsp; RES cG1/lG1 </td>
+      <td>&nbsp; &nbsp; Code and phase residuals for contributing GNSS in [m] given per satellite</td>
+    </tr>
+    <tr>
+      <td>&nbsp; REC_CLK G </td>
+      <td>&nbsp; &nbsp; Receiver clock errors per contributing GNSS, here GPS in [m]</td>
+    </tr>
+    <tr>
+      <td>&nbsp; TRP </td>
+      <td>&nbsp; &nbsp; A priori and correction values of tropospheric zenith delay in [m]</td>
+    </tr>
+    <tr>
+      <td>&nbsp; ION </td>
+      <td>&nbsp; &nbsp; A priori and correction values of ionospheric delay in [m]</td>
+    </tr>
+    <tr>
+      <td>&nbsp; AMB lG1 </td>
+      <td>&nbsp; &nbsp; Floated/fixed ambiguities given per satellite and frequency band with 'nEpo' = number of epochs
+        since last ambiguity reset</td>
+    </tr>
+    <tr>
+      <td>&nbsp; BIA cG1 </td>
+      <td>&nbsp; &nbsp; Satellite code/phase bias related to GNSS and frequency band in [m], here code bias for GPS and
+        band 1</td>
+    </tr>
+    <tr>
+      <td>&nbsp; MOUNTPOINT </td>
+      <td>&nbsp; &nbsp; Here 'FFMJ01DEU0' with XYZ position in [m], dN/dE/dU in [m] for North, East, and Up
+        displacements compared to a priori marker coordinates)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; </td>
+      <td>&nbsp; &nbsp; as well as a remark regarding the status of the ambiguities (flt/fix with its percentile)</td>
+    </tr>
+  </table>
+  <p>
+    Estimated parameters are presented together with their formal errors as derived from the implemented filter.
+    The PPP algorithm includes outlier and cycle slip detection.
+  </p>
+
+  <p>
+    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.
+  </p>
+  <p>
+    BNC follows the RINEX Version 3 standard to create filenames for PPP logfiles (suffix 'ppp'), see section 'RINEX
+    Filenames' for details:
+    For example:
+  <pre><p style="font-family:Monospace">
   FFMJ01DEU_20262090000_01D_01S.ppp
 </pre>
 
-<p><h4 id="pppnmeafile">2.13.1.14 NMEA Directory - optional</h4></p>
-<p>
-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
-</p>
-<p>
-<ul>
-  <li> GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus</li>
-  <li> GPRMC sentences which mainly carry date and time information.</li>
-</ul>
-</p>
-The following is an example for an NMEA output file from BNC.
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+  <h4 id="pppnmeafile">2.13.1.14 NMEA Directory - optional</h4>
+  </p>
+  <p>
+    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
+  </p>
+  <p>
+  <ul>
+    <li> GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus</li>
+    <li> GPRMC sentences which mainly carry date and time information.</li>
+  </ul>
+  </p>
+  The following is an example for an NMEA output file from BNC.
+  </p>
+  <pre><p style="font-family:Monospace">
 ..
 $GPRMC,151742.000,A,5005.4349,N,00839.8984,E,,,280726,,*0b
@@ -4244,34 +6646,40 @@
 </p></pre>
 
-<p>
-BNC follows the RINEX Version 3 standard to create filenames for NMEA logfiles (suffix 'nmea'), see section 'RINEX Filenames' for details.
-For example:
-<pre><p style="font-family:Monospace">
+  <p>
+    BNC follows the RINEX Version 3 standard to create filenames for NMEA logfiles (suffix 'nmea'), see section 'RINEX
+    Filenames' for details.
+    For example:
+  <pre><p style="font-family:Monospace">
   FFMJ01DEU_20262090000_01D_01S.nmea
 </pre>
-The default value for 'NMEA directory' is an empty option field, meaning that BNC will not save NMEA sentences into files.
-If a specified directory does not exist, BNC will not create NMEA files.
-<p>
-Note that Tomoji Takasu has written a program named RTKPLOT for visualizing NMEA sentences from IP ports or files.
-It is available from <a href="http://www.rtklib.com" target="_blank">http://www.rtklib.com</a> and compatible with
-the 'NMEA Directory' and port output of BNC's 'PPP' client option.
-</p>
-
-<p><h4 id="pppsnxtrofile">2.13.1.15 SNX TRO Directory - optional</h4></p>
-<p>
-BNC estimates the tropospheric delay according to equation
-<pre>
+  The default value for 'NMEA directory' is an empty option field, meaning that BNC will not save NMEA sentences into
+  files.
+  If a specified directory does not exist, BNC will not create NMEA files.
+  <p>
+    Note that Tomoji Takasu has written a program named RTKPLOT for visualizing NMEA sentences from IP ports or files.
+    It is available from <a href="http://www.rtklib.com" target="_blank">http://www.rtklib.com</a> and compatible with
+    the 'NMEA Directory' and port output of BNC's 'PPP' client option.
+  </p>
+
+  <p>
+  <h4 id="pppsnxtrofile">2.13.1.15 SNX TRO Directory - optional</h4>
+  </p>
+  <p>
+    BNC estimates the tropospheric delay according to equation
+  <pre>
    T(z) = T_apr(z) + dT / cos(z)
 </pre>
-where T_apr is the a priori tropospheric delay derived from Saastamoinen model.
-</p>
-
-<p>
-You can specify a 'SNX TRO Directory' for saving SINEX Troposphere files on disk, see
-<a href="https://files.igs.org/pub/data/format/sinex_tro_v2.00.pdf" target="_blank">https://files.igs.org/pub/data/format/sinex_tro_v2.00.pdf</a>
-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:
-</p>
-<pre><p style="font-family:Monospace">
+  where T_apr is the a priori tropospheric delay derived from Saastamoinen model.
+  </p>
+
+  <p>
+    You can specify a 'SNX TRO Directory' for saving SINEX Troposphere files on disk, see
+    <a href="https://files.igs.org/pub/data/format/sinex_tro_v2.00.pdf"
+      target="_blank">https://files.igs.org/pub/data/format/sinex_tro_v2.00.pdf</a>
+    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:
+  </p>
+  <pre><p style="font-family:Monospace">
 %=TRO 2.00 CAS 2026:209:00000 CAS 2026:209:00000 2026:209:03599 P FFMJ01DEU
 *-------------------------------------------------------------------------------
@@ -4349,1031 +6757,1575 @@
 %=ENDTROP
 </p></pre>
-For file naming, BNC follows the new format convention according to IGS products considering the site
-<a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf" target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
-<pre>
+  For file naming, BNC follows the new format convention according to IGS products considering the site
+  <a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf"
+    target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
+  <pre>
   AAAVPPPTTT_YYYYDOYHHMM_LEN_SMP_SITENAME_CNT.FMT
 </pre>
-With
-<p>
-<table>
-  <tr><td>&nbsp; AAA        </td><td>&nbsp; &nbsp; Analysis Center abbreviation</td></tr>
-  <tr><td>&nbsp; V          </td><td>&nbsp; &nbsp; Version / Solution identifier (0-9)</td></tr>
-  <tr><td>&nbsp; PPP        </td><td>&nbsp; &nbsp; Project/Campaign identification, here demonstration (DEM)</td></tr>
-  <tr><td>&nbsp; TTT        </td><td>&nbsp; &nbsp; Solution Type, here real-time streamed product(RTS)</td></tr>
-  <tr><td>&nbsp; YYYYDOYHHMM</td><td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td></tr>
-  <tr><td>&nbsp; LEN        </td><td>&nbsp; &nbsp; Intended product period of the file </td></tr>
-  <tr><td>&nbsp; SMP        </td><td>&nbsp; &nbsp; Data sampling rate</td></tr>
-  <tr><td>&nbsp; SITENAME   </td><td>&nbsp; &nbsp; 9-char site name</td></tr>
-  <tr><td>&nbsp; CNT        </td><td>&nbsp; &nbsp; Content type, here TRO</td></tr>
-  <tr><td>&nbsp; FMT        </td><td>&nbsp; &nbsp; File format, here TRO</td></tr>
-</table>
-</p>
-A result for example is:
-<pre><p style="font-family:Monospace">
+  With
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; AAA </td>
+      <td>&nbsp; &nbsp; Analysis Center abbreviation</td>
+    </tr>
+    <tr>
+      <td>&nbsp; V </td>
+      <td>&nbsp; &nbsp; Version / Solution identifier (0-9)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; PPP </td>
+      <td>&nbsp; &nbsp; Project/Campaign identification, here demonstration (DEM)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; TTT </td>
+      <td>&nbsp; &nbsp; Solution Type, here real-time streamed product(RTS)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; YYYYDOYHHMM</td>
+      <td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td>
+    </tr>
+    <tr>
+      <td>&nbsp; LEN </td>
+      <td>&nbsp; &nbsp; Intended product period of the file </td>
+    </tr>
+    <tr>
+      <td>&nbsp; SMP </td>
+      <td>&nbsp; &nbsp; Data sampling rate</td>
+    </tr>
+    <tr>
+      <td>&nbsp; SITENAME </td>
+      <td>&nbsp; &nbsp; 9-char site name</td>
+    </tr>
+    <tr>
+      <td>&nbsp; CNT </td>
+      <td>&nbsp; &nbsp; Content type, here TRO</td>
+    </tr>
+    <tr>
+      <td>&nbsp; FMT </td>
+      <td>&nbsp; &nbsp; File format, here TRO</td>
+    </tr>
+  </table>
+  </p>
+  A result for example is:
+  <pre><p style="font-family:Monospace">
   CAS0DEMRTS_20262091400_01H_01S_FFMJ01DEU_TRO.TRO
 </pre>
 
-<p>
-The default value for 'SNX TRO Directory' is an empty option field, meaning that BNC will not save SINEX Troposphere files.
-If a specified directory does not exist, BNC will not create SINEX Troposphere files.
-</p>
-
-<p><h4 id="pppsnxtrointr">2.13.1.15.1 Interval - mandatory if 'SINEX TRO Directory' is set</h4></p>
-<p>
-Select the length of SINEX Troposphere files.
-</p>
-<p>
-Default 'Interval' for saving SINEX Troposphere files on disk is '1 day'.
-</p>
-<p><h4 id="pppsnxtrosampl">2.13.1.15.2 Sampling - mandatory if 'SINEX TRO Directory' is set</h4></p>
-<p>
-Select a 'Sampling' rate in seconds for saving troposphere parameters.
-</p>
-<p>
-Default 'Sampling' rate is '0', meaning that all troposphere estimates will be saved on disk.
-</p>
-
-<p><h4 id="pppsnxAc">2.13.1.15.3 Analysis Center - Mandatory if 'SINEX TRO Directory' is set</h4></p>
-<p>
-Specify a 3-character abbreviation describing you as the generating Analysis Center (AC) in your SINEX troposphere files. String 'BKG' is an example.
-</p>
-
-<p><h4 id="pppsnxSol">2.13.1.15.4 Solution ID - Mandatory if 'SINEX TRO Directory' is set</h4></p>
-<p>
-Specify a 1-character solution ID to allow a distingtion between different solutions per AC. String '1' is an example.
-</p>
-
-<p><h4 id="pppOptions">2.13.2 PPP (2): Processing Options</h4></p>
-<p>
-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.
-</p>
-<p>
-The intention of this panel is to specify general processing options to be applied to all PPP threads in one BNC job.
-</p>
-
-<p><img src="IMG/Figure23.png"width=1000/></p>
-<p>Figure 23: Precise Point Positioning with BNC, PPP Panel 2</p>
-
-<p><h4 id="pppobs">2.13.2.1 GNSS Observations - mandatory</h4></p>
-<p>
-Specify which kind of observations you want to use and on which kind of linear combination the ambiguity resolutions shall be based.
-The specification has to be done per GNSS ('GPS', 'GLONASS', 'Galileo', 'BDS').
-The following options are available for all GNSS:
-</p>
-<ul>
-      <li>'Pi&Li' means that uncombined code and phase data of two frequencies shall be used.</li>
-      <li>'Pi'    means that uncombined code data of two frequencies shall be used.</li>
-      <li>'P1&L1' means that uncombined code and phase data of one frequency shall be used.</li>
-      <li>'P1'    means that uncombined code data of one frequency shall be used.</li>
-      <li>'P3&L3' means that the inonosphere-free linear combination of code and phase data shall be used.</li>
-      <li>'P3'    means that the inonosphere-free linear combination of code data shall be used.</li>
-      <li>'L3'    means that the inonosphere-free linear combination of phase data shall be used.</li>
-</ul>
-Band and attribute can be specified per station using the Signal Priorities in PPP(3).
-<p>
-For GPS, Galileo and BDS this option is editable. Hence, you can specify your own frequencies for code (P) and phase (L) observations, e.g.:
-<ul>
-<li>for GPS: P125&L125, which means that band 1,2 and 5 of code and phase observations are used. </li>
-<li>for Galileo or BDS 'P1576&L1576' means that band 1,5,7 and 6 of code and phase observations are used. </li>
-</ul>
-The tracking mode for each frequency can be specified per station using the Signal Priorities in PPP(3).
-<p>
-Note that most geodetic GPS receivers support the observation of both, code and phase data.
-Hence, specifying 'Pi&Li' would be a good choice for GPS when processing data from such a receiver.
-If multi-GNSS data processing is your intention, make sure your receiver supports GLONASS and/or Galileo and/or BDS observations besides GPS.
-Note also that the Broadcast Correction stream or file, which is required for PPP, also supports all the systems you have in mind.
-</p>
-<p>Specifying 'no' means that you do not at all want BNC to use observations from the affected GNSS system.
-</p>
-
-<p>
-The choice between an uncombined ('Pi&amp;Li', 'Pi', 'P1&amp;L1', 'P1') and an ionosphere-free ('P3&amp;L3', 'P3',
-'L3') linear combination does not just change which observations are read - it changes the set of parameters
-estimated by BNC's Kalman filter and how each observation enters the filter:
-</p>
-
-<p><b>Uncombined PPP</b><br>
-Each frequency's code and/or phase observation enters the filter on its own, without forming the
-ionosphere-free combination first. The state vector therefore carries, in addition to receiver position, one
-receiver clock per GNSS system and troposphere zenith delay (if estimated):
-<ul>
-  <li>one carrier-phase ambiguity per satellite and per phase frequency,</li>
-  <li>one slant ionospheric delay (ION) per satellite, and</li>
-  <li>one differential code/phase bias per frequency and GNSS system (common to all satellites of that
+  <p>
+    The default value for 'SNX TRO Directory' is an empty option field, meaning that BNC will not save SINEX Troposphere
+    files.
+    If a specified directory does not exist, BNC will not create SINEX Troposphere files.
+  </p>
+
+  <p>
+  <h4 id="pppsnxtrointr">2.13.1.15.1 Interval - mandatory if 'SINEX TRO Directory' is set</h4>
+  </p>
+  <p>
+    Select the length of SINEX Troposphere files.
+  </p>
+  <p>
+    Default 'Interval' for saving SINEX Troposphere files on disk is '1 day'.
+  </p>
+  <p>
+  <h4 id="pppsnxtrosampl">2.13.1.15.2 Sampling - mandatory if 'SINEX TRO Directory' is set</h4>
+  </p>
+  <p>
+    Select a 'Sampling' rate in seconds for saving troposphere parameters.
+  </p>
+  <p>
+    Default 'Sampling' rate is '0', meaning that all troposphere estimates will be saved on disk.
+  </p>
+
+  <p>
+  <h4 id="pppsnxAc">2.13.1.15.3 Analysis Center - Mandatory if 'SINEX TRO Directory' is set</h4>
+  </p>
+  <p>
+    Specify a 3-character abbreviation describing you as the generating Analysis Center (AC) in your SINEX troposphere
+    files. String 'BKG' is an example.
+  </p>
+
+  <p>
+  <h4 id="pppsnxSol">2.13.1.15.4 Solution ID - Mandatory if 'SINEX TRO Directory' is set</h4>
+  </p>
+  <p>
+    Specify a 1-character solution ID to allow a distingtion between different solutions per AC. String '1' is an
+    example.
+  </p>
+
+  <p>
+  <h4 id="pppOptions">2.13.2 PPP (2): Processing Options</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    The intention of this panel is to specify general processing options to be applied to all PPP threads in one BNC
+    job.
+  </p>
+
+  <p><img src="IMG/Figure23.png" width=1000 /></p>
+  <p>Figure 23: Precise Point Positioning with BNC, PPP Panel 2</p>
+
+  <p>
+  <h4 id="pppobs">2.13.2.1 GNSS Observations - mandatory</h4>
+  </p>
+  <p>
+    Specify which kind of observations you want to use and on which kind of linear combination the ambiguity resolutions
+    shall be based.
+    The specification has to be done per GNSS ('GPS', 'GLONASS', 'Galileo', 'BDS').
+    The following options are available for all GNSS:
+  </p>
+  <ul>
+    <li>'Pi&Li' means that uncombined code and phase data of two frequencies shall be used.</li>
+    <li>'Pi' means that uncombined code data of two frequencies shall be used.</li>
+    <li>'P1&L1' means that uncombined code and phase data of one frequency shall be used.</li>
+    <li>'P1' means that uncombined code data of one frequency shall be used.</li>
+    <li>'P3&L3' means that the inonosphere-free linear combination of code and phase data shall be used.</li>
+    <li>'P3' means that the inonosphere-free linear combination of code data shall be used.</li>
+    <li>'L3' means that the inonosphere-free linear combination of phase data shall be used.</li>
+  </ul>
+  Band and attribute can be specified per station using the Signal Priorities in PPP(3).
+  <p>
+    For GPS, Galileo and BDS this option is editable. Hence, you can specify your own frequencies for code (P) and phase
+    (L) observations, e.g.:
+  <ul>
+    <li>for GPS: P125&L125, which means that band 1,2 and 5 of code and phase observations are used. </li>
+    <li>for Galileo or BDS 'P1576&L1576' means that band 1,5,7 and 6 of code and phase observations are used. </li>
+  </ul>
+  The tracking mode for each frequency can be specified per station using the Signal Priorities in PPP(3).
+  <p>
+    Note that most geodetic GPS receivers support the observation of both, code and phase data.
+    Hence, specifying 'Pi&Li' would be a good choice for GPS when processing data from such a receiver.
+    If multi-GNSS data processing is your intention, make sure your receiver supports GLONASS and/or Galileo and/or BDS
+    observations besides GPS.
+    Note also that the Broadcast Correction stream or file, which is required for PPP, also supports all the systems you
+    have in mind.
+  </p>
+  <p>Specifying 'no' means that you do not at all want BNC to use observations from the affected GNSS system.
+  </p>
+
+  <p>
+    The choice between an uncombined ('Pi&amp;Li', 'Pi', 'P1&amp;L1', 'P1') and an ionosphere-free ('P3&amp;L3', 'P3',
+    'L3') linear combination does not just change which observations are read - it changes the set of parameters
+    estimated by BNC's Kalman filter and how each observation enters the filter:
+  </p>
+
+  <p><b>Uncombined PPP</b><br>
+    Each frequency's code and/or phase observation enters the filter on its own, without forming the
+    ionosphere-free combination first. The state vector therefore carries, in addition to receiver position, one
+    receiver clock per GNSS system and troposphere zenith delay (if estimated):
+  <ul>
+    <li>one carrier-phase ambiguity per satellite and per phase frequency,</li>
+    <li>one slant ionospheric delay (ION) per satellite, and</li>
+    <li>one differential code/phase bias per frequency and GNSS system (common to all satellites of that
       system), mainly needed to absorb hardware delays and to remove the rank deficiency between receiver
       clock, ambiguities and biases.</li>
-</ul>
-Receiver clock, biases and the per-satellite ionospheric delay are re-estimated fresh every epoch (no Kalman
-process noise carried over), while position, troposphere and ambiguities accumulate over time. This means each
-epoch's ionospheric delay per satellite is, by default, determined from that epoch's code-minus-phase
-combination alone - exactly the weakly observable quantity that the optional ionospheric pseudo-observations
-(see <a href=#pppconstraints>Section 2.13.2.9</a>) are meant to stabilize.
-</p>
-<p>
-Uncombined PPP is not limited to two frequencies. For GPS, Galileo and BDS the custom band selection (e.g.
-'P125&amp;L125', see above) adds a third, fourth, etc. frequency the same way: one more code and phase
-observation, one more carrier-phase ambiguity, and one more per-frequency bias parameter, all referring to the
-very same single per-satellite ionospheric delay (ION) parameter, scaled to each frequency through the usual
-1/f&sup2; ionospheric mapping. The optional ionospheric pseudo-observations of
-<a href=#pppconstraints>Section 2.13.2.9</a> are added for any uncombined band selection this way, predefined
-('Pi&amp;Li', 'Pi', 'P1&amp;L1', 'P1') or custom, as long as at least one code or phase observation is configured
-for the affected GNSS system.
-</p>
-
-<p><b>Ionosphere-free PPP</b><br>
-The dual-frequency ionosphere-free linear combination is formed from code and/or phase data before it enters
-the filter, which removes the first-order ionospheric delay from the observation equation. The state vector
-therefore needs no per-satellite ionospheric delay parameter at all; it carries only receiver position, one
-receiver clock per system, troposphere (if estimated), and one combined (non-integer) ambiguity-like parameter
-per satellite that absorbs the carrier-phase ambiguity together with the satellite/receiver hardware delays of
-the combination. Because this combined parameter is not an integer number of cycles, ambiguity resolution
-(<a href=#pppar>Section 2.13.2.10</a>) is not applicable in this mode, and the optional ionospheric
-pseudo-observations of <a href=#pppconstraints>Section 2.13.2.9</a> do not apply either, since there is no
-per-satellite ionospheric state left to constrain.
-</p>
-
-<p><h4 id="pppcodeobs">2.13.2.2 Code Observations - mandatory</h4></p>
-<p>
-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. '1.0' meters is likely to be an appropriate choice.
-</p>
-<p>
-Specify a maximum for residuals 'Max Res C1' for C1 code observations in a PPP solution. '2.0' meters may be an appropriate choice for that.
-If the maximum is exceeded, contributions from the corresponding observation will be ignored in the PPP solution.
-</p>
-
-<p><h4 id="pppphaseobs">2.13.2.3 Phase Observations - mandatory</h4></p>
-<p>
-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.
-</p>
-<p>
-Specify a maximum for residuals 'Max Res L1' for L1 phase observations in a PPP solution. '0.02' meters may be an appropriate choice for that.
-If the maximum is exceeded, contributions from the corresponding observation will be ignored in the PPP solution.
-</p>
-<p>
-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.
-<ul>
-  <li>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.</li>
-  <li>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
+  </ul>
+  Receiver clock, biases and the per-satellite ionospheric delay are re-estimated fresh every epoch (no Kalman
+  process noise carried over), while position, troposphere and ambiguities accumulate over time. This means each
+  epoch's ionospheric delay per satellite is, by default, determined from that epoch's code-minus-phase
+  combination alone - exactly the weakly observable quantity that the optional ionospheric pseudo-observations
+  (see <a href=#pppconstraints>Section 2.13.2.9</a>) are meant to stabilize.
+  </p>
+  <p>
+    Uncombined PPP is not limited to two frequencies. For GPS, Galileo and BDS the custom band selection (e.g.
+    'P125&amp;L125', see above) adds a third, fourth, etc. frequency the same way: one more code and phase
+    observation, one more carrier-phase ambiguity, and one more per-frequency bias parameter, all referring to the
+    very same single per-satellite ionospheric delay (ION) parameter, scaled to each frequency through the usual
+    1/f&sup2; ionospheric mapping. The optional ionospheric pseudo-observations of
+    <a href=#pppconstraints>Section 2.13.2.9</a> are added for any uncombined band selection this way, predefined
+    ('Pi&amp;Li', 'Pi', 'P1&amp;L1', 'P1') or custom, as long as at least one code or phase observation is configured
+    for the affected GNSS system.
+  </p>
+
+  <p><b>Ionosphere-free PPP</b><br>
+    The dual-frequency ionosphere-free linear combination is formed from code and/or phase data before it enters
+    the filter, which removes the first-order ionospheric delay from the observation equation. The state vector
+    therefore needs no per-satellite ionospheric delay parameter at all; it carries only receiver position, one
+    receiver clock per system, troposphere (if estimated), and one combined (non-integer) ambiguity-like parameter
+    per satellite that absorbs the carrier-phase ambiguity together with the satellite/receiver hardware delays of
+    the combination. Because this combined parameter is not an integer number of cycles, ambiguity resolution
+    (<a href=#pppar>Section 2.13.2.10</a>) is not applicable in this mode, and the optional ionospheric
+    pseudo-observations of <a href=#pppconstraints>Section 2.13.2.9</a> do not apply either, since there is no
+    per-satellite ionospheric state left to constrain.
+  </p>
+
+  <p>
+  <h4 id="pppcodeobs">2.13.2.2 Code Observations - mandatory</h4>
+  </p>
+  <p>
+    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. '1.0' meters is likely to be an appropriate choice.
+  </p>
+  <p>
+    Specify a maximum for residuals 'Max Res C1' for C1 code observations in a PPP solution. '2.0' meters may be an
+    appropriate choice for that.
+    If the maximum is exceeded, contributions from the corresponding observation will be ignored in the PPP solution.
+  </p>
+
+  <p>
+  <h4 id="pppphaseobs">2.13.2.3 Phase Observations - mandatory</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Specify a maximum for residuals 'Max Res L1' for L1 phase observations in a PPP solution. '0.02' meters may be an
+    appropriate choice for that.
+    If the maximum is exceeded, contributions from the corresponding observation will be ignored in the PPP solution.
+  </p>
+  <p>
+    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.
+  <ul>
+    <li>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.</li>
+    <li>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.</li>
-</ul>
-</p>
-
-<p><h4 id="pppeleweight">2.13.2.4 Elevation Dependent Weighting - mandatory</h4></p>
-<p>
-BNC allows elevation dependent weighting when processing GNSS observations. A weight function
-</p>
-<p>&nbsp; &nbsp; &nbsp; P = cos&sup2; * z</p>
-<p>
-with 'z' being the zenith distance to the involved satellite can be applied instead of the simple weight function 'P = 1'
-independent from satellite elevation angles.
-</p>
-<ul>
-<li>Tick 'Ele Wgt Code' if you want Elevation Dependent Weighting for code observations.</li>
-<li>Tick 'Ele Wgt Phase' if you want Elevation Dependent Weighting for phase observations.</li>
-</ul>
-<p>
-Default is using the plain weight function 'P = 1' for code and phase observations.
-</p>
-
-<p><h4 id="pppminobs">2.13.2.5 Minimum Number of Observations - mandatory</h4></p>
-<p>
-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.
-</p>
-<p><h4 id="pppmineleva">2.13.2.6 Minimum Elevation - mandatory</h4></p>
-<p>
-Select a minimum for satellite elevation angles. Selecting '7 deg' for option 'Min Elevation' may be an appropriate choice.
-</p>
-<p>
-Default is '0 deg', meaning that any observation will be used regardless of the involved satellite elevation angle.
-</p>
-
-<p><h4 id="pppwaitclockcorr">2.13.2.7 Wait for Clock Corrections - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-Using observations in sync with the corrections can avoid a possible high frequency noise of PPP solutions.
-Such noise could result from processing observations regardless of how late after a clock correction they were received.
-Note that applying the 'Wait for clock corr.' option significantly reduces the PPP computation effort for BNC.
-</p>
-<p>
-Default is an empty option field, meaning that you want BNC to process observations immediately after their arrival
-through applying the latest received clock correction.
-</p>
-
-<p><h4 id="pppseeding">2.13.2.8 Seeding - optional if a priori coordinates specified in 'Coordinates file'</h4></p>
-<p>
-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.
-</p>
-<p>
-This so-called <b>Quick-Start</b> 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.
-<p>
-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 (3)' corresponding to the
-coordinate's precision.
-</p>
-<p>
-'Seeding' has also a function for <b>bridging gaps</b> 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.
-</p>
-
-<p><h4 id="pppconstraints">2.13.2.9 Constraints - optional</h4></p>
-<p>
-Specify, whether ionospheric constraints in form of pseudo-observations shall be added to an uncombined PPP
-solution ('Pi&amp;Li', 'Pi', 'P1&amp;L1' or 'P1', see <a href=#pppobs>Section 2.13.2.1</a>). This is sometimes
-called 'PPP with pseudo-observations for STEC'.
-</p>
-<p><h4 id="ppppseudogimobs">2.13.2.9.0 GIM Pseudo Observations - How it works</h4></p>
-<p>
-When ionospheric constraints are activated, BNC derives a slant ionospheric delay (STEC) for every satellite from VTEC informations - taken
-from an Ionosphere stream/file (<a href=#pppionostream>Section 2.13.1.6</a>, <a href=#pppionofile>Section
-2.13.1.7</a>) or from the Corrections stream/file if no dedicated Ionosphere source is specified. For each GNSS
-system, one satellite is chosen as 'reference satellite' (initially the one with the highest elevation), and one
-satellite-differenced pseudo-observation per remaining satellite is added to the Kalman filter:
-</p>
-<p>
-&nbsp; &nbsp; STEC(reference satellite) &minus; STEC(satellite) = ION(reference satellite) &minus; ION(satellite)
-</p>
-<p>
-where ION(satellite) is the per-satellite ionospheric delay state already estimated by the uncombined PPP filter.
-This single difference constrains the relative ionospheric delay between satellites without removing the
-receiver's own freedom to estimate it from code and phase data. The reference satellite is kept as long as it
-stays in view; a new one is selected only once the previous reference satellite disappears from the
-observations, which avoids spurious jumps in the constraint from one epoch to the next.
-</p>
-<p>
-Pseudo-observations are treated as a soft constraint: they contribute to the solution with a weight derived from
-'Sigma GIM' (see below) but are never rejected as outliers, regardless of their residual size. They are also
-fully independent of ambiguity resolution (<a href=#pppar>Section 2.13.2.10</a>), which only ever resolves
-carrier-phase ambiguities.
-</p>
-<p>
-Please note that this option is only valid if no ionosphere-free linear combination is used and VTEC informations
-are actually available. Without VTEC data, no pseudo-observations are added and the PPP solution falls back to
-estimating per-satellite ionospheric delays from code and phase data alone. The pseudo-observations are only
-helpful once the ionosphere information is more accurate than the code data accuracy.
-</p>
-
-<p><h4 id="ppppseudogimobssigma">2.13.2.9.1 GIM Pseudo Observations Sigma - optional</h4></p>
-<p>
-Enter a 'Sigma GIM' for pseudo observations regarding the Ionosphere in meters.
-The bigger the sigma you enter, the less the contribution of GIM Pseudo observations to a PPP solutions
-based on a combination of code and phase data. '5.0' meters is likely to be an appropriate choice.
-</p>
-<p><h4 id="pppar">2.13.2.10 PPP-AR - optional</h4></p>
-<p>
-The BNC PPP ambiguity resolution combines two classical methods:
-<ul>
-  <li>the <b>LAMBDA</b> (Least-squares AMBiguity Decorrelation Adjustment) algorithm for the integer search, and </li>
-  <li>the <b>BIE</b> (Best Integer Equivariant) weighting for the final estimate.</li>
-</ul>
-References:
-</p>
-<p>
-Teunissen P.J.G. (1993) Least-squares estimation of the integer GPS ambiguities, Invited Lecture, Section IV Theory and Methodology, 
-IAG General Meeting, Beijing, China, August 1993. Also in: LGR Series, No. 6, Delft Geodetic Computing Centre.
-<a href="https://gnss.curtin.edu.au/wp-content/uploads/sites/21/2016/04/Teunissen1993Least.pdf" target="_blank">https://gnss.curtin.edu.au/wp-content/uploads/sites/21/2016/04/Teunissen1993Least.pdf</a>
-
-</p>
-<p>
-Teunissen P.J.G. (2005) GNSS Best Integer Equivariant Estimation. In book: A Window on the Future of Geodesy. pp. 422-427. Sanso, F., Berlin: Springer. Inpress.
-<a href="https://doi.org/10.1007/3-540-27432-4_72" target="_blank">https://doi.org/10.1007/3-540-27432-4_72</a>
-</p>
-
-<p><h4 id="ppparmethod">2.13.2.10.0 Algorithm Description</h4></p>
-<p>
-The following describes the individual steps as implemented for BNCs PPP-AR solution.
-</p>
-
-<p><b>Step 1 &ndash; Float ambiguity extraction</b><br>
-The Kalman filter state vector contains all estimated parameters (receiver position, receiver clock,
-troposphere, and carrier-phase ambiguities). The AR module extracts only the ambiguity entries
-into a reduced vector using a design matrix, together with the corresponding sub-block of the
-variance&ndash;covariance matrix.
-</p>
-
-<p><b>Step 2 &ndash; Resolvability filtering</b><br>
-Before entering the search, each ambiguity must pass the following quality gates:
-</p>
-<ul>
-  <li>A minimum number of epochs observed (see <a href="#ppparmin">Min # Epo</a>)</li>
-  <li>A minimum satellite elevation angle</li>
-  <li>At least 2 ambiguities available per GNSS group</li>
-  <li>A minimum number of satellites per constellation (see <a href="#ppparmin">Min # Sat</a>)</li>
-</ul>
-
-<p><b>Step 3 &ndash; Reference ambiguity selection</b><br>
-One ambiguity per constellation group is chosen as a reference (the one that minimises the sum of
-double-difference variances). It is tightly constrained to its nearest integer via a Kalman
-pseudo-observation update. This step effectively converts zero-difference to single-difference
-ambiguity space and ensures a stable basis for the search.
-</p>
-
-<p><b>Step 4 &ndash; LAMBDA decorrelation</b><br>
-The ambiguity covariance matrix is decomposed as <i>L&middot;D&middot;L</i><sup>T</sup>.
-An integer-preserving transformation matrix <i>Z</i> (with det(<i>Z</i>)&nbsp;=&nbsp;&plusmn;1) is
-applied to minimise the correlation between ambiguities. After this step the search is far more
-efficient because the transformed ambiguities are nearly uncorrelated.
-</p>
-
-<p><b>Step 5 &ndash; BIE candidate search</b><br>
-A sequential search-and-shrink algorithm (SSEARCH) finds the top 100 integer candidate vectors
-ranked by their squared Mahalanobis distance &chi;&sup2;. For each candidate <i>i</i> an
-exponential weight is computed:
-</p>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;<i>w</i>(<i>i</i>) = exp(&minus;0.5 &middot; (&chi;&sup2;<sub><i>i</i></sub> &minus; &chi;&sup2;<sub>best</sub>))</p>
-<p>
-The <b>BIE estimate</b> is then the weighted average over all candidates:
-</p>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;<i>a</i><sub>BIE</sub> = &sum; <i>w</i>(<i>i</i>) &middot; <i>a</i>(<i>i</i>) / &sum; <i>w</i>(<i>i</i>)</p>
-<p>
-This is the key difference from plain LAMBDA/ILS, which picks only the single best integer vector.
-BIE produces a real-valued weighted combination and is the minimum mean-square error estimator
-under a Gaussian distribution.
-</p>
-
-<p><b>Step 6 &ndash; BIE variance</b><br>
-Rather than adopting the optimistic variance of the single best candidate, BIE computes a
-conservative variance that reflects the probability mass spread across all candidates:
-</p>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;&sigma;&sup2;<sub>BIE</sub>(<i>j</i>) = &sum; <i>w</i>(<i>i</i>) &middot; (<i>a</i><sub>BIE</sub>(<i>j</i>) &minus; <i>a</i>(<i>j</i>,<i>i</i>))&sup2;</p>
-
-<p><b>Step 7 &ndash; Fixability decision and constraint imposition</b><br>
-An ambiguity is considered fixable if both of the following criteria are met:
-</p>
-<ul>
-  <li>|<i>a</i><sub>BIE</sub> &minus; round(<i>a</i><sub>BIE</sub>)| &le; Max Frac (see <a href="#ppparmax">Max Frac and Sig</a>)</li>
-  <li>&sigma;<sub>BIE</sub> &le; Max Sig (see <a href="#ppparmax">Max Frac and Sig</a>)</li>
-</ul>
-<p>
-For all fixable ambiguities, Kalman equality constraints with a tight weight are applied to force
-the filter state vector to adopt the integer values. Subsequent filter updates treat these fixed
-ambiguities as pseudo-observations until a cycle-slip triggers a reset.
-</p>
-
-<p><b>Comparison with other PPP ambiguity resolution methods</b></p>
-<table border="1" rules="all" frame="box" bgcolor="#FFF5EE" style="font-size:13">
-  <tr bgcolor="#E0E0E0">
-    <td><b>&nbsp;Method&nbsp;</b></td>
-    <td><b>&nbsp;Integer choice&nbsp;</b></td>
-    <td><b>&nbsp;Output&nbsp;</b></td>
-  </tr>
-  <tr>
-    <td>&nbsp;Rounding&nbsp;</td>
-    <td>&nbsp;Nearest integer per ambiguity, independently&nbsp;</td>
-    <td>&nbsp;Hard fix, simple but fragile&nbsp;</td>
-  </tr>
-  <tr>
-    <td>&nbsp;Bootstrapping&nbsp;</td>
-    <td>&nbsp;Sequential conditional rounding&nbsp;</td>
-    <td>&nbsp;Hard fix, faster than ILS&nbsp;</td>
-  </tr>
-  <tr>
-    <td>&nbsp;ILS / LAMBDA&nbsp;</td>
-    <td>&nbsp;Single globally optimal integer vector&nbsp;</td>
-    <td>&nbsp;Hard fix, optimal under Gaussian noise&nbsp;</td>
-  </tr>
-  <tr>
-    <td>&nbsp;<b>BIE (BNC)</b>&nbsp;</td>
-    <td>&nbsp;Weighted combination of top-N candidates&nbsp;</td>
-    <td>&nbsp;Soft/weighted fix, minimum MSE estimator&nbsp;</td>
-  </tr>
-</table>
-<br>
-
-<p><h4 id="ppparsys">2.13.2.10.1 Constellations - optional</h4></p>
-<p>
-Specify, for which constellations the ambiguities should be resolved to their integer values. This option is available for GPS, Galileo and BDS.
-</p>
-<p><h4 id="ppparmin">2.13.2.10.2 Min # Epo and Sat - optional</h4></p>
-<p>
-Using 'Min # Epo' you can specify the number of epochs for which the unknown ambiguity parameter has to be observed at least,
-to be included into the search.
-</p>
-<p>
-Using 'Min # Sat' you can define that the ambiguity search is performed if at least the specified number of satellites per constellation is being tracked.
-</p>
-<p><h4 id="ppparmax">2.13.2.10.3 Max Frac and Sig - optional</h4></p>
-<p>
-Using the options 'Max Frac' and 'Max Sig' you may decide whether to use this additional information and fix (constrain) only those
-ambiguities which meet these requirements. In more detail:
-</p>
-<p>
-If 'Max Frac' is greater than zero, the ambiguity is constrained only if the absolute value of the fractional part of its BIE value
-is lower or equal than the specified value.
-</p>
-<p>
-If 'Max Sig' is greater than zero, the ambiguity is constrained only if the BIE sigma (uncertainty of the BIE result)
-is lower or equal than the specified value.
-</p>
-<p><h4 id="ppparyaw">2.13.2.10.4 Yaw Usage - optional</h4></p>
-<p>
-If 'Use Yaw' is set, the information about the satellite attitude (yaw angle) is taken from the corresponding
-SSR correction (phase bias message). Otherwise a standard satellite attitude model is used.
-</p> 
-
-<p><h4 id="ppparfix">2.13.2.10.5 Per-epoch fix percentage</h4></p>
-<p>
-The number printed in the log (... fix XX %) is a fixRatio computed as follows: 
-<ol>
-  <li>A copy of the float filter state is taken — the real recursive filter state is never touched by AR.</li>
-  <li>Ambiguities are grouped per system/LC into zero-difference sets if minimum number of tracked epochs (see <a href="#ppparmin">Min # Epo</a>) and the minimum elevation (see <a href=#pppmineleva>Minimum Elevation</a>) is exceeded.</li>
-  <li>One reference ambiguity per group is hard-constrained to its rounded value with a tiny σ (sigCon = 1e-4 cycles, turning the rest into single-differences (SD).</li>
-  <li>A LAMBDA/BIE (Best Integer Equivariant) search produces xBie/covBie — a probability-weighted blend over candidate integer vectors, not a hard integer.</li>
-  <li>isFixable() flags an SD ambiguity as fixed if |frac(xBie)| ≤ arMaxFrac and sqrt(covBie) ≤ arMaxSig (see <a href=#ppparmax>Max Frac and Sig</a>).</li>
-  <li>fixRatio = numFixSdAll / numSdAmbs — fixed SD ambiguities divided by all SD ambiguities in groups that already passed step 2's pre-filter.</li>
-</ol>
-Some remarks: 
-<ul>
-  <li>It's a statistical sharpness test, not a validated fix. Unlike classical LAMBDA AR (ratio test against the second-best candidate), isFixable() only checks that the BIE estimate is close to an integer with small posterior variance. BIE will confidently "fix" a self-consistent but wrong combination if the underlying float ambiguities carry a systematic, unmodeled bias — there's no independent validation step.</li>
-  <li> The fix is a per-epoch snapshot, not a recursive hold. Since AR runs on a copy of the filter state and the result is never fed back into _xFlt/_QFlt, each epoch's "fix" is recomputed from scratch from whatever the float ambiguity looks like that epoch. A satellite can be reported "fixed" to slightly different integer realizations epoch-to-epoch, which shows up as scatter in the AR-constrained coordinate even though the printed percentage stays high.</li>
-  <li>Everything hinges on the phase-bias corrections. Ambiguity resolution only works because incoming SSR phase-bias corrections with fixIndicator set are applied per satellite/frequency before this stage; satellites lacking valid biases are dropped entirely when AR is on (useObsWithBiasesOnly). If that correction stream is stale, low-quality, or inconsistent with the orbit/clock product (different AC, different update interval), the float ambiguities will still sharpen and "fix" statistically — just around the wrong integer — degrading rather than improving the position.</li>
-  <li> Small denominator effect: 'numSdAmbs' only counts already pre-filtered, resolvable ambiguities in groups of ≥2; with a thin satellite/group count it's easy to get 100% from very few satellites, which isn't representative of overall solution strength.</li>
-</ul>
- If the per-epoch fix percentage values look too high in comparison with the resulting coordinate displacements, 
- try:
+  </ul>
+  </p>
+
+  <p>
+  <h4 id="pppeleweight">2.13.2.4 Elevation Dependent Weighting - mandatory</h4>
+  </p>
+  <p>
+    BNC allows elevation dependent weighting when processing GNSS observations. A weight function
+  </p>
+  <p>&nbsp; &nbsp; &nbsp; P = cos&sup2; * z</p>
+  <p>
+    with 'z' being the zenith distance to the involved satellite can be applied instead of the simple weight function 'P
+    = 1'
+    independent from satellite elevation angles.
+  </p>
   <ul>
-  <li>tightening 'Max Frac' / 'Max Sig' and </li>
-  <li>raising 'Min # Sat' / 'Min # Epo' </li>
+    <li>Tick 'Ele Wgt Code' if you want Elevation Dependent Weighting for code observations.</li>
+    <li>Tick 'Ele Wgt Phase' if you want Elevation Dependent Weighting for phase observations.</li>
   </ul>
-to see if the percentage drops to something  more consistent with the achieved coordinate repeatability — if it doesn't, the bias-correction quality/consistency 
- is the more likely root cause than the AR logic itself. 
-</p>
-<p><h4 id="pppStation">2.13.3 PPP (3): Processed Stations</h4></p>
-<p>
-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.
-</p>
-
-<p>
-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.</p>
-</p>
-
-<p>
-BNC will simultaneously produce PPP solutions for all stations listed in the 'Station' column of this table.
-</p>
-
-<p><img src="IMG/Figure25.png"width=1000/></p>
-<p>Figure 25: Precise Point Positioning with BNC, PPP Panel 3</p>
-
-<p><h4 id="pppsite">2.13.2.1 Station - mandatory</h4></p>
-<p>
-Hit the 'Add Station' button, double click on the 'Station' field, then specify an observation's mountpoint from the
-'Streams' section or introduce the 9-character Station ID of your RINEX observation file and hit Enter.
-BNC will only produce PPP solutions for stations listed in this table.
-</p>
-
-<p><h4 id="pppnehsigma">2.13.2.2 Sigma North/East/Up - mandatory</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="pppnehnoise">2.13.2.3 Noise North/East/Up - mandatory</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="ppptropsigma">2.13.2.4 Tropo Sigma - mandatory</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="ppptropnoise">2.13.2.5 Tropo Noise - mandatory</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="pppnmeaport">2.13.2.6 NMEA Port - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-Note also that Tomoji Takasu has written a program named RTKPLOT for visualizing NMEA sentences from IP ports or files.
-It is available from <a href="http://www.rtklib.com" target="_blank">http://www.rtklib.com</a> and compatible with the
-NMEA file and port output of BNC's 'PPP' client option.
-</p>
-<p>
-Furthermore, NASA's 'World Wind' software
-(see <a href="http://worldwindcentral.com/wiki/NASA_World_Wind_Download" target="_blank">http://worldwindcentral.com/wiki/NASA_World_Wind_Download</a>)
-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
-<a href="http://worldwindcentral.com/wiki/GPS_Tracker" target="_blank">http://worldwindcentral.com/wiki/GPS_Tracker</a> for that.
-The 'Word Wind' map resolution is not meant for showing centimeter level details.
-</p>
-
-<p><h4 id="pppsignalpriorities">2.13.2.7 Signal Priorities - optional</h4></p>
-<p>
-Specify a list of 'Signal Priorities' for the observations that shall be used for PPP.
-Signal priorities can be specified as system (G,R,E,C) and frequency specific.
-Two frequency bands per GNSS are allowed and will be considered.
-The following frequency bands are available for selection:
-<ul>
-<li>G: 1, 2, 5</li>
-<li>R: 1, 2</li>
-<li>E: 1, 5, 6, 7, 8</li>
-<li>C: 1, 2, 5, 6, 7, 8</li>
-</ul>
-<p>'Default' is the following list of 'Signal Priorities':
-<ul><li>'G:12&CWPSLX R:12&CP E:1&CBX E:5&QIX C:26&IQX'</li></ul>
-<p>
-But it is recommended to specify it in more detail per individual station, e.g.:</p>
-<ul> <li>'G:12&W R:12&P E:1&C E:5&Q C:26&I'</li></ul>
-
-<p><h4 id="pppPlots">2.13.4 PPP (4): Plots</h4></p>
-<p>
-This panel presents options for visualizing PPP results as a time series plot or as a track map with PPP tracks on top
-of OpenStreetMap (OSM) maps.
-</p>
-
-<p><h4 id="ppptimeseries">2.13.4.1 PPP Plot - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-Note that a PPP dicplacements time series makes only sense for a stationary operated receiver.
-</p>
-
-<p><h4 id="pppaudioresp">2.13.4.2 Audio Response - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-Default is an empty option field, meaning that you do not want BNC to produce acoustic warnings.
-</p>
-
-<p><h4 id="ppptrackmap">2.13.4.3 Track Map - optional</h4></p>
-<p>
-You may like to track your rover position using 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.
-</p>
-<p>
-The 'Open Map' button opens a window showing the map.
-</p>
-
-<p><img src="IMG/Figure26.png"width=1000/></p>
-<p>Figure 26: Precise Point Positioning with BNC with track of positions using OpenStreetMap, PPP Panel 4.</p>
-
-
-<p><h4 id="pppdotprop">2.13.4.4 Dot-properties - mandatory before pushing 'Open Map'</h4></p>
-<p>
-PPP tracks are presented on maps through plotting one colored dot per observation epoch.
-</p>
-
-<p><h4 id="pppdotsize">2.13.4.4.1 Size - mandatory before pushing 'Open Map'</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="pppdotcolor">2.13.4.4.2 Color - mandatory before pushing 'Open Map'</h4></p>
-<p>
-Select the color of dots showing the rover track.
-</p>
-
-<p><h4 id="pppspeed">2.13.4.5 Post Processing Speed - mandatory before pushing 'Open Map'</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="combi">2.14 Combine Corrections</h4></p>
-<p>
-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  (Weber and Mervart 2010). 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 are just taken over from one of the incoming
-Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference (which means the individual orbit of
-an incoming AC = Master orbit) imposes the potential to introduce analysis inconsistencies. Hence, some a priori corrections dC
-are applied before clock combination, to compensate for the inconsistency between MasterAC and other orbits.
-This should include corrections for inconsistent frames, attitude mode and phase center offset:
-</p>
-<pre>
+  <p>
+    Default is using the plain weight function 'P = 1' for code and phase observations.
+  </p>
+
+  <p>
+  <h4 id="pppminobs">2.13.2.5 Minimum Number of Observations - mandatory</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+  <h4 id="pppmineleva">2.13.2.6 Minimum Elevation - mandatory</h4>
+  </p>
+  <p>
+    Select a minimum for satellite elevation angles. Selecting '7 deg' for option 'Min Elevation' may be an appropriate
+    choice.
+  </p>
+  <p>
+    Default is '0 deg', meaning that any observation will be used regardless of the involved satellite elevation angle.
+  </p>
+
+  <p>
+  <h4 id="pppwaitclockcorr">2.13.2.7 Wait for Clock Corrections - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Using observations in sync with the corrections can avoid a possible high frequency noise of PPP solutions.
+    Such noise could result from processing observations regardless of how late after a clock correction they were
+    received.
+    Note that applying the 'Wait for clock corr.' option significantly reduces the PPP computation effort for BNC.
+  </p>
+  <p>
+    Default is an empty option field, meaning that you want BNC to process observations immediately after their arrival
+    through applying the latest received clock correction.
+  </p>
+
+  <p>
+  <h4 id="pppseeding">2.13.2.8 Seeding - optional if a priori coordinates specified in 'Coordinates file'</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    This so-called <b>Quick-Start</b> 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.
+  <p>
+    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 (3)' corresponding
+    to the
+    coordinate's precision.
+  </p>
+  <p>
+    'Seeding' has also a function for <b>bridging gaps</b> 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.
+  </p>
+
+  <p>
+  <h4 id="pppconstraints">2.13.2.9 Constraints - optional</h4>
+  </p>
+  <p>
+    Specify, whether ionospheric constraints in form of pseudo-observations shall be added to an uncombined PPP
+    solution ('Pi&amp;Li', 'Pi', 'P1&amp;L1' or 'P1', see <a href=#pppobs>Section 2.13.2.1</a>). This is sometimes
+    called 'PPP with pseudo-observations for STEC'.
+  </p>
+  <p>
+  <h4 id="ppppseudogimobs">2.13.2.9.0 GIM Pseudo Observations - How it works</h4>
+  </p>
+  <p>
+    When ionospheric constraints are activated, BNC derives a slant ionospheric delay (STEC) for every satellite from
+    VTEC informations - taken
+    from an Ionosphere stream/file (<a href=#pppionostream>Section 2.13.1.6</a>, <a href=#pppionofile>Section
+      2.13.1.7</a>) or from the Corrections stream/file if no dedicated Ionosphere source is specified. For each GNSS
+    system, one satellite is chosen as 'reference satellite' (initially the one with the highest elevation), and one
+    satellite-differenced pseudo-observation per remaining satellite is added to the Kalman filter:
+  </p>
+  <p>
+    &nbsp; &nbsp; STEC(reference satellite) &minus; STEC(satellite) = ION(reference satellite) &minus; ION(satellite)
+  </p>
+  <p>
+    where ION(satellite) is the per-satellite ionospheric delay state already estimated by the uncombined PPP filter.
+    This single difference constrains the relative ionospheric delay between satellites without removing the
+    receiver's own freedom to estimate it from code and phase data. The reference satellite is kept as long as it
+    stays in view; a new one is selected only once the previous reference satellite disappears from the
+    observations, which avoids spurious jumps in the constraint from one epoch to the next.
+  </p>
+  <p>
+    Pseudo-observations are treated as a soft constraint: they contribute to the solution with a weight derived from
+    'Sigma GIM' (see below) but are never rejected as outliers, regardless of their residual size. They are also
+    fully independent of ambiguity resolution (<a href=#pppar>Section 2.13.2.10</a>), which only ever resolves
+    carrier-phase ambiguities.
+  </p>
+  <p>
+    Please note that this option is only valid if no ionosphere-free linear combination is used and VTEC informations
+    are actually available. Without VTEC data, no pseudo-observations are added and the PPP solution falls back to
+    estimating per-satellite ionospheric delays from code and phase data alone. The pseudo-observations are only
+    helpful once the ionosphere information is more accurate than the code data accuracy.
+  </p>
+
+  <p>
+  <h4 id="ppppseudogimobssigma">2.13.2.9.1 GIM Pseudo Observations Sigma - optional</h4>
+  </p>
+  <p>
+    Enter a 'Sigma GIM' for pseudo observations regarding the Ionosphere in meters.
+    The bigger the sigma you enter, the less the contribution of GIM Pseudo observations to a PPP solutions
+    based on a combination of code and phase data. '5.0' meters is likely to be an appropriate choice.
+  </p>
+  <p>
+  <h4 id="pppar">2.13.2.10 PPP-AR - optional</h4>
+  </p>
+  <p>
+    The BNC PPP ambiguity resolution combines two classical methods:
+  <ul>
+    <li>the <b>LAMBDA</b> (Least-squares AMBiguity Decorrelation Adjustment) algorithm for the integer search, and </li>
+    <li>the <b>BIE</b> (Best Integer Equivariant) weighting for the final estimate.</li>
+  </ul>
+  References:
+  </p>
+  <p>
+    Teunissen P.J.G. (1993) Least-squares estimation of the integer GPS ambiguities, Invited Lecture, Section IV Theory
+    and Methodology,
+    IAG General Meeting, Beijing, China, August 1993. Also in: LGR Series, No. 6, Delft Geodetic Computing Centre.
+    <a href="https://gnss.curtin.edu.au/wp-content/uploads/sites/21/2016/04/Teunissen1993Least.pdf"
+      target="_blank">https://gnss.curtin.edu.au/wp-content/uploads/sites/21/2016/04/Teunissen1993Least.pdf</a>
+
+  </p>
+  <p>
+    Teunissen P.J.G. (2005) GNSS Best Integer Equivariant Estimation. In book: A Window on the Future of Geodesy. pp.
+    422-427. Sanso, F., Berlin: Springer. Inpress.
+    <a href="https://doi.org/10.1007/3-540-27432-4_72" target="_blank">https://doi.org/10.1007/3-540-27432-4_72</a>
+  </p>
+
+  <p>
+  <h4 id="ppparmethod">2.13.2.10.0 Algorithm Description</h4>
+  </p>
+  <p>
+    The following describes the individual steps as implemented for BNCs PPP-AR solution.
+  </p>
+
+  <p><b>Step 1 &ndash; Float ambiguity extraction</b><br>
+    The Kalman filter state vector contains all estimated parameters (receiver position, receiver clock,
+    troposphere, and carrier-phase ambiguities). The AR module extracts only the ambiguity entries
+    into a reduced vector using a design matrix, together with the corresponding sub-block of the
+    variance&ndash;covariance matrix.
+  </p>
+
+  <p><b>Step 2 &ndash; Resolvability filtering</b><br>
+    Before entering the search, each ambiguity must pass the following quality gates:
+  </p>
+  <ul>
+    <li>A minimum number of epochs observed (see <a href="#ppparmin">Min # Epo</a>)</li>
+    <li>A minimum satellite elevation angle</li>
+    <li>At least 2 ambiguities available per GNSS group</li>
+    <li>A minimum number of satellites per constellation (see <a href="#ppparmin">Min # Sat</a>)</li>
+  </ul>
+
+  <p><b>Step 3 &ndash; Reference ambiguity selection</b><br>
+    One ambiguity per constellation group is chosen as a reference (the one that minimises the sum of
+    double-difference variances). It is tightly constrained to its nearest integer via a Kalman
+    pseudo-observation update. This step effectively converts zero-difference to single-difference
+    ambiguity space and ensures a stable basis for the search.
+  </p>
+
+  <p><b>Step 4 &ndash; LAMBDA decorrelation</b><br>
+    The ambiguity covariance matrix is decomposed as <i>L&middot;D&middot;L</i><sup>T</sup>.
+    An integer-preserving transformation matrix <i>Z</i> (with det(<i>Z</i>)&nbsp;=&nbsp;&plusmn;1) is
+    applied to minimise the correlation between ambiguities. After this step the search is far more
+    efficient because the transformed ambiguities are nearly uncorrelated.
+  </p>
+
+  <p><b>Step 5 &ndash; BIE candidate search</b><br>
+    A sequential search-and-shrink algorithm (SSEARCH) finds the top 100 integer candidate vectors
+    ranked by their squared Mahalanobis distance &chi;&sup2;. For each candidate <i>i</i> an
+    exponential weight is computed:
+  </p>
+  <p>&nbsp;&nbsp;&nbsp;&nbsp;<i>w</i>(<i>i</i>) = exp(&minus;0.5 &middot; (&chi;&sup2;<sub><i>i</i></sub> &minus;
+    &chi;&sup2;<sub>best</sub>))</p>
+  <p>
+    The <b>BIE estimate</b> is then the weighted average over all candidates:
+  </p>
+  <p>&nbsp;&nbsp;&nbsp;&nbsp;<i>a</i><sub>BIE</sub> = &sum; <i>w</i>(<i>i</i>) &middot; <i>a</i>(<i>i</i>) / &sum;
+    <i>w</i>(<i>i</i>)
+  </p>
+  <p>
+    This is the key difference from plain LAMBDA/ILS, which picks only the single best integer vector.
+    BIE produces a real-valued weighted combination and is the minimum mean-square error estimator
+    under a Gaussian distribution.
+  </p>
+
+  <p><b>Step 6 &ndash; BIE variance</b><br>
+    Rather than adopting the optimistic variance of the single best candidate, BIE computes a
+    conservative variance that reflects the probability mass spread across all candidates:
+  </p>
+  <p>&nbsp;&nbsp;&nbsp;&nbsp;&sigma;&sup2;<sub>BIE</sub>(<i>j</i>) = &sum; <i>w</i>(<i>i</i>) &middot;
+    (<i>a</i><sub>BIE</sub>(<i>j</i>) &minus; <i>a</i>(<i>j</i>,<i>i</i>))&sup2;</p>
+
+  <p><b>Step 7 &ndash; Fixability decision and constraint imposition</b><br>
+    An ambiguity is considered fixable if both of the following criteria are met:
+  </p>
+  <ul>
+    <li>|<i>a</i><sub>BIE</sub> &minus; round(<i>a</i><sub>BIE</sub>)| &le; Max Frac (see <a href="#ppparmax">Max Frac
+        and Sig</a>)</li>
+    <li>&sigma;<sub>BIE</sub> &le; Max Sig (see <a href="#ppparmax">Max Frac and Sig</a>)</li>
+  </ul>
+  <p>
+    For all fixable ambiguities, Kalman equality constraints with a tight weight are applied to force
+    the filter state vector to adopt the integer values. Subsequent filter updates treat these fixed
+    ambiguities as pseudo-observations until a cycle-slip triggers a reset.
+  </p>
+
+  <p><b>Comparison with other PPP ambiguity resolution methods</b></p>
+  <table border="1" rules="all" frame="box" bgcolor="#FFF5EE" style="font-size:13">
+    <tr bgcolor="#E0E0E0">
+      <td><b>&nbsp;Method&nbsp;</b></td>
+      <td><b>&nbsp;Integer choice&nbsp;</b></td>
+      <td><b>&nbsp;Output&nbsp;</b></td>
+    </tr>
+    <tr>
+      <td>&nbsp;Rounding&nbsp;</td>
+      <td>&nbsp;Nearest integer per ambiguity, independently&nbsp;</td>
+      <td>&nbsp;Hard fix, simple but fragile&nbsp;</td>
+    </tr>
+    <tr>
+      <td>&nbsp;Bootstrapping&nbsp;</td>
+      <td>&nbsp;Sequential conditional rounding&nbsp;</td>
+      <td>&nbsp;Hard fix, faster than ILS&nbsp;</td>
+    </tr>
+    <tr>
+      <td>&nbsp;ILS / LAMBDA&nbsp;</td>
+      <td>&nbsp;Single globally optimal integer vector&nbsp;</td>
+      <td>&nbsp;Hard fix, optimal under Gaussian noise&nbsp;</td>
+    </tr>
+    <tr>
+      <td>&nbsp;<b>BIE (BNC)</b>&nbsp;</td>
+      <td>&nbsp;Weighted combination of top-N candidates&nbsp;</td>
+      <td>&nbsp;Soft/weighted fix, minimum MSE estimator&nbsp;</td>
+    </tr>
+  </table>
+  <br>
+
+  <p>
+  <h4 id="ppparsys">2.13.2.10.1 Constellations - optional</h4>
+  </p>
+  <p>
+    Specify, for which constellations the ambiguities should be resolved to their integer values. This option is
+    available for GPS, Galileo and BDS.
+  </p>
+  <p>
+  <h4 id="ppparmin">2.13.2.10.2 Min # Epo and Sat - optional</h4>
+  </p>
+  <p>
+    Using 'Min # Epo' you can specify the number of epochs for which the unknown ambiguity parameter has to be observed
+    at least,
+    to be included into the search.
+  </p>
+  <p>
+    Using 'Min # Sat' you can define that the ambiguity search is performed if at least the specified number of
+    satellites per constellation is being tracked.
+  </p>
+  <p>
+  <h4 id="ppparmax">2.13.2.10.3 Max Frac and Sig - optional</h4>
+  </p>
+  <p>
+    Using the options 'Max Frac' and 'Max Sig' you may decide whether to use this additional information and fix
+    (constrain) only those
+    ambiguities which meet these requirements. In more detail:
+  </p>
+  <p>
+    If 'Max Frac' is greater than zero, the ambiguity is constrained only if the absolute value of the fractional part
+    of its BIE value
+    is lower or equal than the specified value.
+  </p>
+  <p>
+    If 'Max Sig' is greater than zero, the ambiguity is constrained only if the BIE sigma (uncertainty of the BIE
+    result)
+    is lower or equal than the specified value.
+  </p>
+  <p>
+  <h4 id="ppparyaw">2.13.2.10.4 Yaw Usage - optional</h4>
+  </p>
+  <p>
+    If 'Use Yaw' is set, the information about the satellite attitude (yaw angle) is taken from the corresponding
+    SSR correction (phase bias message). Otherwise a standard satellite attitude model is used.
+  </p>
+
+  <p>
+  <h4 id="ppparfix">2.13.2.10.5 Per-epoch fix percentage</h4>
+  </p>
+  <p>
+    The number printed in the log (... fix XX %) is a fixRatio computed as follows:
+  <ol>
+    <li>A copy of the float filter state is taken — the real recursive filter state is never touched by AR.</li>
+    <li>Ambiguities are grouped per system/LC into zero-difference sets if minimum number of tracked epochs (see <a
+        href="#ppparmin">Min # Epo</a>) and the minimum elevation (see <a href=#pppmineleva>Minimum Elevation</a>) is
+      exceeded.</li>
+    <li>One reference ambiguity per group is hard-constrained to its rounded value with a tiny σ (sigCon = 1e-4 cycles,
+      turning the rest into single-differences (SD).</li>
+    <li>A LAMBDA/BIE (Best Integer Equivariant) search produces xBie/covBie — a probability-weighted blend over
+      candidate integer vectors, not a hard integer.</li>
+    <li>isFixable() flags an SD ambiguity as fixed if |frac(xBie)| ≤ arMaxFrac and sqrt(covBie) ≤ arMaxSig (see <a
+        href=#ppparmax>Max Frac and Sig</a>).</li>
+    <li>fixRatio = numFixSdAll / numSdAmbs — fixed SD ambiguities divided by all SD ambiguities in groups that already
+      passed step 2's pre-filter.</li>
+  </ol>
+  Some remarks:
+  <ul>
+    <li>It's a statistical sharpness test, not a validated fix. Unlike classical LAMBDA AR (ratio test against the
+      second-best candidate), isFixable() only checks that the BIE estimate is close to an integer with small posterior
+      variance. BIE will confidently "fix" a self-consistent but wrong combination if the underlying float ambiguities
+      carry a systematic, unmodeled bias — there's no independent validation step.</li>
+    <li> The fix is a per-epoch snapshot, not a recursive hold. Since AR runs on a copy of the filter state and the
+      result is never fed back into _xFlt/_QFlt, each epoch's "fix" is recomputed from scratch from whatever the float
+      ambiguity looks like that epoch. A satellite can be reported "fixed" to slightly different integer realizations
+      epoch-to-epoch, which shows up as scatter in the AR-constrained coordinate even though the printed percentage
+      stays high.</li>
+    <li>Everything hinges on the phase-bias corrections. Ambiguity resolution only works because incoming SSR phase-bias
+      corrections with fixIndicator set are applied per satellite/frequency before this stage; satellites lacking valid
+      biases are dropped entirely when AR is on (useObsWithBiasesOnly). If that correction stream is stale, low-quality,
+      or inconsistent with the orbit/clock product (different AC, different update interval), the float ambiguities will
+      still sharpen and "fix" statistically — just around the wrong integer — degrading rather than improving the
+      position.</li>
+    <li> Small denominator effect: 'numSdAmbs' only counts already pre-filtered, resolvable ambiguities in groups of ≥2;
+      with a thin satellite/group count it's easy to get 100% from very few satellites, which isn't representative of
+      overall solution strength.</li>
+  </ul>
+  If the per-epoch fix percentage values look too high in comparison with the resulting coordinate displacements,
+  try:
+  <ul>
+    <li>tightening 'Max Frac' / 'Max Sig' and </li>
+    <li>raising 'Min # Sat' / 'Min # Epo' </li>
+  </ul>
+  to see if the percentage drops to something more consistent with the achieved coordinate repeatability — if it
+  doesn't, the bias-correction quality/consistency
+  is the more likely root cause than the AR logic itself.
+  </p>
+  <p>
+  <h4 id="pppStation">2.13.3 PPP (3): Processed Stations</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+    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.</p>
+  </p>
+
+  <p>
+    BNC will simultaneously produce PPP solutions for all stations listed in the 'Station' column of this table.
+  </p>
+
+  <p><img src="IMG/Figure25.png" width=1000 /></p>
+  <p>Figure 25: Precise Point Positioning with BNC, PPP Panel 3</p>
+
+  <p>
+  <h4 id="pppsite">2.13.2.1 Station - mandatory</h4>
+  </p>
+  <p>
+    Hit the 'Add Station' button, double click on the 'Station' field, then specify an observation's mountpoint from the
+    'Streams' section or introduce the 9-character Station ID of your RINEX observation file and hit Enter.
+    BNC will only produce PPP solutions for stations listed in this table.
+  </p>
+
+  <p>
+  <h4 id="pppnehsigma">2.13.2.2 Sigma North/East/Up - mandatory</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="pppnehnoise">2.13.2.3 Noise North/East/Up - mandatory</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="ppptropsigma">2.13.2.4 Tropo Sigma - mandatory</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="ppptropnoise">2.13.2.5 Tropo Noise - mandatory</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="pppnmeaport">2.13.2.6 NMEA Port - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Note also that Tomoji Takasu has written a program named RTKPLOT for visualizing NMEA sentences from IP ports or
+    files.
+    It is available from <a href="http://www.rtklib.com" target="_blank">http://www.rtklib.com</a> and compatible with
+    the
+    NMEA file and port output of BNC's 'PPP' client option.
+  </p>
+  <p>
+    Furthermore, NASA's 'World Wind' software
+    (see <a href="http://worldwindcentral.com/wiki/NASA_World_Wind_Download"
+      target="_blank">http://worldwindcentral.com/wiki/NASA_World_Wind_Download</a>)
+    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
+    <a href="http://worldwindcentral.com/wiki/GPS_Tracker"
+      target="_blank">http://worldwindcentral.com/wiki/GPS_Tracker</a> for that.
+    The 'Word Wind' map resolution is not meant for showing centimeter level details.
+  </p>
+
+  <p>
+  <h4 id="pppsignalpriorities">2.13.2.7 Signal Priorities - optional</h4>
+  </p>
+  <p>
+    Specify a list of 'Signal Priorities' for the observations that shall be used for PPP.
+    Signal priorities can be specified as system (G,R,E,C) and frequency specific.
+    Two frequency bands per GNSS are allowed and will be considered.
+    The following frequency bands are available for selection:
+  <ul>
+    <li>G: 1, 2, 5</li>
+    <li>R: 1, 2</li>
+    <li>E: 1, 5, 6, 7, 8</li>
+    <li>C: 1, 2, 5, 6, 7, 8</li>
+  </ul>
+  <p>'Default' is the following list of 'Signal Priorities':
+  <ul>
+    <li>'G:12&CWPSLX R:12&CP E:1&CBX E:5&QIX C:26&IQX'</li>
+  </ul>
+  <p>
+    But it is recommended to specify it in more detail per individual station, e.g.:</p>
+  <ul>
+    <li>'G:12&W R:12&P E:1&C E:5&Q C:26&I'</li>
+  </ul>
+
+  <p>
+  <h4 id="pppPlots">2.13.4 PPP (4): Plots</h4>
+  </p>
+  <p>
+    This panel presents options for visualizing PPP results as a time series plot or as a track map with PPP tracks on
+    top
+    of OpenStreetMap (OSM) maps.
+  </p>
+
+  <p>
+  <h4 id="ppptimeseries">2.13.4.1 PPP Plot - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Note that a PPP dicplacements time series makes only sense for a stationary operated receiver.
+  </p>
+
+  <p>
+  <h4 id="pppaudioresp">2.13.4.2 Audio Response - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Default is an empty option field, meaning that you do not want BNC to produce acoustic warnings.
+  </p>
+
+  <p>
+  <h4 id="ppptrackmap">2.13.4.3 Track Map - optional</h4>
+  </p>
+  <p>
+    You may like to track your rover position using 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.
+  </p>
+  <p>
+    The 'Open Map' button opens a window showing the map.
+  </p>
+
+  <p><img src="IMG/Figure26.png" width=1000 /></p>
+  <p>Figure 26: Precise Point Positioning with BNC with track of positions using OpenStreetMap, PPP Panel 4.</p>
+
+
+  <p>
+  <h4 id="pppdotprop">2.13.4.4 Dot-properties - mandatory before pushing 'Open Map'</h4>
+  </p>
+  <p>
+    PPP tracks are presented on maps through plotting one colored dot per observation epoch.
+  </p>
+
+  <p>
+  <h4 id="pppdotsize">2.13.4.4.1 Size - mandatory before pushing 'Open Map'</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="pppdotcolor">2.13.4.4.2 Color - mandatory before pushing 'Open Map'</h4>
+  </p>
+  <p>
+    Select the color of dots showing the rover track.
+  </p>
+
+  <p>
+  <h4 id="pppspeed">2.13.4.5 Post Processing Speed - mandatory before pushing 'Open Map'</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="combi">2.14 Combine Corrections</h4>
+  </p>
+  <p>
+    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 (Weber and Mervart 2010). 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 are just taken over from one of the incoming
+    Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference (which means the
+    individual orbit of
+    an incoming AC = Master orbit) imposes the potential to introduce analysis inconsistencies. Hence, some a priori
+    corrections dC
+    are applied before clock combination, to compensate for the inconsistency between MasterAC and other orbits.
+    This should include corrections for inconsistent frames, attitude mode and phase center offset:
+  </p>
+  <pre>
  dC = dC_frame + dC_att + dC_pco [m]
 </pre>
- But because at present, no PCO information is available via SSR, we consider only
-<pre>
+  But because at present, no PCO information is available via SSR, we consider only
+  <pre>
  dC_frame = Orb_AC * (Orb_AC - Orb_MasterAC) / Range_sat
 </pre>
-<pre>
+  <pre>
  dC_att = (yawAngle_AC - yawAngle_MasterAC) / (2*PI) * wavelength(IF)
 </pre>
 
-<p>
-The 'Combine Corrections' functionality may be of interrest because:
-<ul>
-  <li>Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;</li>
-  <li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li>
-  <li>A Combination Center (CC) can operate BNC to globally disseminate a combination product via Ntrip broadcast;</li>
-  <li>An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;</li>
-  <li>It enables a BNC PPP user to follow his own preference in combining streams from individual ACs for Precise Point Positioning;</li>
-  <li>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;</li>
-  <li>It provides the means to output SP3 and Clock RINEX files containing precise orbit and clock information as well as SINEX Bias files for further processing using other tools than BNC.</li>
-</ul>
-</p>
-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:
-<pre>
+  <p>
+    The 'Combine Corrections' functionality may be of interrest because:
+  <ul>
+    <li>Outages of single AC product streams can be mitigated through merging several incoming streams into a combined
+      product;</li>
+    <li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li>
+    <li>A Combination Center (CC) can operate BNC to globally disseminate a combination product via Ntrip broadcast;
+    </li>
+    <li>An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce
+      outages;</li>
+    <li>It enables a BNC PPP user to follow his own preference in combining streams from individual ACs for Precise
+      Point Positioning;</li>
+    <li>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;</li>
+    <li>It provides the means to output SP3 and Clock RINEX files containing precise orbit and clock information as well
+      as SINEX Bias files for further processing using other tools than BNC.</li>
+  </ul>
+  </p>
+  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:
+  <pre>
  Clk_Corr = AC_Offset + Sat_Offset + Clk
  </pre>
- With
- <p>
-<table>
-  <tr><td>&nbsp; AC_Offset </td><td>&nbsp; &nbsp; AC specific offset</td></tr>
-  <tr><td>&nbsp; Sat_Offset</td><td>&nbsp; &nbsp; Satellite specific offset common to all ACs</td></tr>
-  <tr><td>&nbsp; Clk       </td><td>&nbsp; &nbsp; the actual satellite clock correction, which represents the result of the combination</td></tr>
-</table>
-</p>
-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.
-</p>
-<p>
-Removing the AC-dependent biases 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.
-</p>
-<p>
-The following recursive algorithm is used to detect orbit outliers in the Kalman Filter combination when Broadcast Corrections are provided by several ACs:<br>
- <p>
-<table>
-  <tr><td>&nbsp; Step 1 </td><td>&nbsp; &nbsp; We do not produce a combination for a certain satellite if only one AC provides corrections for it.</td></tr>
-  <tr><td>&nbsp; Step 2 </td><td>&nbsp; &nbsp; A mean satellite position is calculated as the average of positions from all ACs.</td></tr>
-  <tr><td>&nbsp; Step 3 </td><td>&nbsp; &nbsp; For each AC and satellite, the 3D distance between individual and mean satellite position is calculated.</td></tr>
-  <tr><td>&nbsp; Step 4 </td><td>&nbsp; &nbsp; We find the greatest difference between AC specific and mean satellite positions.</td></tr>
-  <tr><td>&nbsp; Step 5 </td><td>&nbsp; &nbsp; If that is less than a threshold, the conclusion is that we do not have an outlier and can proceed to the next epoch.</td></tr>
-  <tr><td>&nbsp; Step 6 </td><td>&nbsp; &nbsp; 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.</td></tr>
-</table>
-</p>
-<p>
-The following screenshot shows an example setup of BNC when combining several Broadcast Correction streams.
-</p>
-<p><img src="IMG/Figure27.png"width=1000/></p>
-<p>Figure 27: BNC combining Broadcast Correction streams</p>
-
-<p>
-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 'BCEP00BKG0' on caster <a href="http://products.igs-ip.net" target="_blank">http://products.igs-ip.net</a>
-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.
-</p>
-<p>
-The combination is done system-wise for the following reference signals as specified in the IGS Real-Time Committee:
- <p>
-<table>
-  <tr><td>&nbsp; GPS:    </td><td>&nbsp; &nbsp; C1W/C2W</td></tr>
-  <tr><td>&nbsp; GLONASS:</td><td>&nbsp; &nbsp; C1P/C2P</td></tr>
-  <tr><td>&nbsp; Galileo:</td><td>&nbsp; &nbsp; C1C/C5Q</td></tr>
-  <tr><td>&nbsp; BDS:    </td><td>&nbsp; &nbsp; C2I/C6I</td></tr>
-  <tr><td>&nbsp; QZSS:   </td><td>&nbsp; &nbsp; C1C/C2L</td></tr>
-  <tr><td>&nbsp; SBAS:   </td><td>&nbsp; &nbsp; C1C/C5Q</td></tr>
-  <tr><td>&nbsp; NavIC:  </td><td>&nbsp; &nbsp; nothing declared</td></tr>
-</table>
-</p>
-<p>
-When the individual satellite clocks and code biases are used together, the effective Observable-Specific Biases (OSBs) are recovered.
-With it, the interoperability between corrections of different RTACs, which may use different signals for clock estimation, is ensured.
-Hence, the individual RTAC satellite clocks are reduced epoch by epoch by the individual ionosphere-free linear combination
-of individual RTAC satellite code biases, delivered for the reference signals, before its combination.
-With it, the combined satellite clocks are consistent to IGS clocks, which means ionosphere-free clocks
-based on the defined reference signals - despite the fact, that the delivered code biases of an RTAC may contain contributions
-from other biases, also phase biases (Banville et al. 2020).
-</p>
-<p>
-Hence, the ionosphere-free linear combination of code biases for the IGS reference signals is determined
-from the supplied code biases and subtracted from the clocks before combination.
-The combined satellite clocks are consistent to IGS clocks, which means ionosphere-free clocks based on the defined reference signals
- - despite the fact, that the delivered code biases of an AC may contain contributions from other biases, also phase biases.
-</p>
-<p>
-This convention allows the ionosphere-free linear combination of the two OSBs of the reference signals to be set to zero.
-All other OSBs can then be expressed in terms of Differential Code Biases. For this,
-the PCO-corrected satellite DCB product (Wang et al. 2025) of the Chinese Academy of Sciences (CAS) is used and send out
-as SSR code bias together with the combined clocks. These SINEX Bias files are archived at CDDIS:
-<a href="https://cddis.nasa.gov/archive/gnss/products/bias/" target="_blank">https://cddis.nasa.gov/archive/gnss/products/bias/</a>
-</p>
-<p>
-References:
-</p>
-<p>
-Banville S., Geng J., Loyer S., Schaer S., Springer T., Strasser S. (2020) On the interoperability of IGS products for precise point positioning with ambiguity resolution. Journal of Geodesy. 94, 10 (2020).
-<a href="https://doi.org/10.1007/s00190-019-01335-w" target="_blank">https://doi.org/10.1007/s00190-019-01335-w</a>
-</p>
-<p>
-Wang N., Li Y., Li Z., Liu A., Liu B. (2025) Determination of multi-GNSS differential code biases with satellite antenna phase center corrections. GPS Solutions 30, 22 (2026).
-<a href="https://doi.org/10.1007/s10291-025-01983-w" target="_blank">https://doi.org/10.1007/s10291-025-01983-w</a>
-</p>
-<p>
-A combination is carried out following a specified sampling interval. BNC waits for incoming Broadcast Corrections for the period
-of one such interval. Corrections received later than that will be ignored. If incoming streams have different rates,
-only epochs that correspond to the sampling interval are used.
-</p>
-<p>
-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 SSRA00BKG1 and SSRA00CNE1 and simultaneously carries out a PPP solution
-with observations from stream FFMJ01DEU0 to allow monitoring the quality of the combination product in the space domain.
-</p>
-<p><img src="IMG/Figure28.png"width=1000/></p>
-<p>Figure 28: 'INTERNAL' PPP with BNC using a combination of Broadcast Corrections</p>
-
-<p><h4 id="combimounttab">2.14.1 Combine Corrections Table - optional</h4></p>
-<p>
-Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Correction mountpoint from the 'Streams' section
-and hit Enter.</p>
-<p>
-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.</p>
-<p>
-After that, double click on the 'Weight Factor' field to enter a weight to be applied to this stream in the combination.
-A Factor greater than 1 will enlarge the sigma of the clock pseudo-observations and with it down-weight its contribution.</p>
-<p>
-Finally, double click on the 'Exclude Satellites' field and specify satellites or satellite systems, to exclude them for an individual AC.
-An entry 'G04,G31,R' means to excludes GPS satellites PRN 4 and 31 as well as all GLONASS satellites from one individual AC.
-Default is an empty option field, meaning that no satellite is excluded from this individual AC.</p>
-<p>
-Use the 'Attitude' field to select how satellite attitude is modelled when converting Antenna Phase Center (APC) corrections to
-Center-of-Mass (CoM) positions required for SP3 output. Three options are available:
-<ul>
-<li><b>Computed</b> (default): BNC applies its own kinematic attitude model:
-GPS noon/midnight turn manoeuvres (Kouba 2009/2015, Bar-Sever 1996),
-GLONASS yaw-fixed mode (Dilssner et al. 2011), and
-Galileo / BDS orbit-normal mode switching (Kouba 2017, Dai et al. 2015, Steigenberger et al. 2018).</li>
-<li><b>Nominal</b>: a simplified, continuous Sun-pointing model is used without any manoeuvre modelling.</li>
-<li><b>SSR</b>: the yaw angle transmitted in the SSR phase bias message is used directly, if present for the satellite and epoch.
-If no yaw angle is available for a particular satellite in a given epoch, BNC falls back to 'Computed'.
-Select this option only if you trust the yaw values provided by the Analysis Center.</li>
-</ul>
-Note that the attitude model affects APC-referenced correction streams only.
-For CoM-referenced streams (SSRC) the Analysis Center has already applied its own attitude model before encoding.</p>
-<p>
-Note that the orbit information in the resulting 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.</p>
-<p>
-The combination process requires Broadcast Ephemeris.
-Besides orbit and clock correction streams BNC should therefore pull a stream carrying Broadcast Ephemeris in the form of RTCM Version 3 messages.
-The following type of Broadcast navigation messages is used per individulal GNSS:</p>
-<table>
-<tr><td>Navigation 		</td><td>Description							</td><td>Constellation  		</td><td>RTCM </td></tr>
-<tr><td>Message Type	</td><td>										</td><td>and Signal 			</td><td>Message Type</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>LNAV</td><td>			GPS Legacy navigation message			</td><td>GPS  L1 C/A           	</td><td>1019</td></tr>
-<tr><td>	</td><td>			QZSS Legacy navigation message 			</td><td>QZSS L1 C/A or L1 C/B 	</td><td>1044</td></tr>
-<tr><td>	</td><td>			NavIC Legacy navigation message 		</td><td>NavIC L5/S SPS        	</td><td>1041</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>FDMA</td><td>			GLONASS Legacy FDMA navigation message	</td><td>GLO L1 C/A			 	</td><td>1020</td></tr>
-<tr><td>	</td><td>			from M-satellites						</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>INAV</td><td>			Galileo Integrity 	navigation message 	</td><td>GAL E1, E5b        	</td><td>1046</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>D1	</td><td>			BeiDou-2/3 MEO/IGSO navigation message 	</td><td>BDS B1I, B2I, B3I  	</td><td>1042</td></tr>
-<tr><td>D2	</td><td>			BeiDou-2/3 GEO      navigation message 	</td><td>BDS B1I, B2I, B3I 		</td><td>1042</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>SBAS</td><td>			SBAS      navigation message 			</td><td>SBAS L1            	</td><td>1043</td></tr>
-</table>
-<p>
-It is possible to specify only one Broadcast Ephemeris Correction stream in the 'Combine Corrections' table.
-Instead of combining corrections BNC will then add the corrections to the Broadcast Ephemeris with the possibility
-to save final orbit and clock results in SP3 and/or Clock RINEX format.
-</p>
-<p>
-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.</p>
-<p>
-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.
-</p>
-
-<p>
-Default is an empty 'Combine Corrections' table, meaning that you do not want BNC to combine orbit and clock correction streams.
-</p>
-
-<p><h4 id="combiadd">2.14.1.1 Add Row, Delete - optional</h4></p>
-<p>
-Hit 'Add Row' button to add another row to the 'Combine Corrections' table or hit the 'Delete' button to delete the highlighted row(s).
-</p>
-
-<p><h4 id="combimethod">2.14.1.2 Method - mandatory if 'Combine Corrections' table is populated</h4></p>
-<p>
-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.</p>
-
-<p><h4 id="combimaxres">2.14.1.3 Maximal Clock Residuum - mandatory if 'Combine Corrections' table is populated</h4></p>
-<p>
-BNC combines all incoming clocks according to specified weights. Individual clock estimates that differ by more than
-'Maximal Clk Residuum' meters from the average of all clocks will be ignored.
-It is suggested to specify a value of about 0.2 m for the Kalman Filter combination approach and
-a value of about 3.0 meters for the Single-Epoch combination approach.</p>
-<p>
-Default is a 'Maximal Clk Residuum' of 999.0 meters.</p>
-
-<p><h4 id="combimaxdisp">2.14.1.4 Maximal Orbit Displacement - mandatory if 'Combine Corrections' table is populated</h4></p>
-<p>
-BNC builds mean values for all incoming orbit corrections per satellite.
-Individual orbit corrections that differ by more than 'Maximal Orb Displacement' meters from the average
-of all orbit corrections per satellite will be ignored. It is suggested to specify a value of about 0.5 m.</p>
-<p>
-Default is a 'Maximal Orb Displacement' of 2.0 meters.</p>
-
-<p><h4 id="combismpl">2.14.1.5 Sampling - mandatory if 'Combine Corrections' table is populated</h4></p>
-<p>
-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.</p>
-
-<p><h4 id="combisatsys">2.14.1.6 Satellite Systems - mandatory if 'Combine Corrections' table is populated</h4></p>
-<p>
-Specify for each satellite system whether the clock corrections shall be combined.</p>
-
-<p><h4 id="upclk">2.15 Upload Corrections</h4></p>
-<p>
-BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and out-of-plane
-components if they are
-<ol type="a">
-  <li>either generated by BNC as a combination of several individual Broadcast Correction streams coming from an number of
+  With
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; AC_Offset </td>
+      <td>&nbsp; &nbsp; AC specific offset</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Sat_Offset</td>
+      <td>&nbsp; &nbsp; Satellite specific offset common to all ACs</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Clk </td>
+      <td>&nbsp; &nbsp; the actual satellite clock correction, which represents the result of the combination</td>
+    </tr>
+  </table>
+  </p>
+  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.
+  </p>
+  <p>
+    Removing the AC-dependent biases 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.
+  </p>
+  <p>
+    The following recursive algorithm is used to detect orbit outliers in the Kalman Filter combination when Broadcast
+    Corrections are provided by several ACs:<br>
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; Step 1 </td>
+      <td>&nbsp; &nbsp; We do not produce a combination for a certain satellite if only one AC provides corrections for
+        it.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Step 2 </td>
+      <td>&nbsp; &nbsp; A mean satellite position is calculated as the average of positions from all ACs.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Step 3 </td>
+      <td>&nbsp; &nbsp; For each AC and satellite, the 3D distance between individual and mean satellite position is
+        calculated.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Step 4 </td>
+      <td>&nbsp; &nbsp; We find the greatest difference between AC specific and mean satellite positions.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Step 5 </td>
+      <td>&nbsp; &nbsp; If that is less than a threshold, the conclusion is that we do not have an outlier and can
+        proceed to the next epoch.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Step 6 </td>
+      <td>&nbsp; &nbsp; 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.</td>
+    </tr>
+  </table>
+  </p>
+  <p>
+    The following screenshot shows an example setup of BNC when combining several Broadcast Correction streams.
+  </p>
+  <p><img src="IMG/Figure27.png" width=1000 /></p>
+  <p>Figure 27: BNC combining Broadcast Correction streams</p>
+
+  <p>
+    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 'BCEP00BKG0' on caster <a href="http://products.igs-ip.net" target="_blank">http://products.igs-ip.net</a>
+    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.
+  </p>
+  <p>
+    The combination is done system-wise for the following reference signals as specified in the IGS Real-Time Committee:
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; GPS: </td>
+      <td>&nbsp; &nbsp; C1W/C2W</td>
+    </tr>
+    <tr>
+      <td>&nbsp; GLONASS:</td>
+      <td>&nbsp; &nbsp; C1P/C2P</td>
+    </tr>
+    <tr>
+      <td>&nbsp; Galileo:</td>
+      <td>&nbsp; &nbsp; C1C/C5Q</td>
+    </tr>
+    <tr>
+      <td>&nbsp; BDS: </td>
+      <td>&nbsp; &nbsp; C2I/C6I</td>
+    </tr>
+    <tr>
+      <td>&nbsp; QZSS: </td>
+      <td>&nbsp; &nbsp; C1C/C2L</td>
+    </tr>
+    <tr>
+      <td>&nbsp; SBAS: </td>
+      <td>&nbsp; &nbsp; C1C/C5Q</td>
+    </tr>
+    <tr>
+      <td>&nbsp; NavIC: </td>
+      <td>&nbsp; &nbsp; nothing declared</td>
+    </tr>
+  </table>
+  </p>
+  <p>
+    When the individual satellite clocks and code biases are used together, the effective Observable-Specific Biases
+    (OSBs) are recovered.
+    With it, the interoperability between corrections of different RTACs, which may use different signals for clock
+    estimation, is ensured.
+    Hence, the individual RTAC satellite clocks are reduced epoch by epoch by the individual ionosphere-free linear
+    combination
+    of individual RTAC satellite code biases, delivered for the reference signals, before its combination.
+    With it, the combined satellite clocks are consistent to IGS clocks, which means ionosphere-free clocks
+    based on the defined reference signals - despite the fact, that the delivered code biases of an RTAC may contain
+    contributions
+    from other biases, also phase biases (Banville et al. 2020).
+  </p>
+  <p>
+    Hence, the ionosphere-free linear combination of code biases for the IGS reference signals is determined
+    from the supplied code biases and subtracted from the clocks before combination.
+    The combined satellite clocks are consistent to IGS clocks, which means ionosphere-free clocks based on the defined
+    reference signals
+    - despite the fact, that the delivered code biases of an AC may contain contributions from other biases, also phase
+    biases.
+  </p>
+  <p>
+    This convention allows the ionosphere-free linear combination of the two OSBs of the reference signals to be set to
+    zero.
+    All other OSBs can then be expressed in terms of Differential Code Biases. For this,
+    the PCO-corrected satellite DCB product (Wang et al. 2025) of the Chinese Academy of Sciences (CAS) is used and send
+    out
+    as SSR code bias together with the combined clocks. These SINEX Bias files are archived at CDDIS:
+    <a href="https://cddis.nasa.gov/archive/gnss/products/bias/"
+      target="_blank">https://cddis.nasa.gov/archive/gnss/products/bias/</a>
+  </p>
+  <p>
+    References:
+  </p>
+  <p>
+    Banville S., Geng J., Loyer S., Schaer S., Springer T., Strasser S. (2020) On the interoperability of IGS products
+    for precise point positioning with ambiguity resolution. Journal of Geodesy. 94, 10 (2020).
+    <a href="https://doi.org/10.1007/s00190-019-01335-w" target="_blank">https://doi.org/10.1007/s00190-019-01335-w</a>
+  </p>
+  <p>
+    Wang N., Li Y., Li Z., Liu A., Liu B. (2025) Determination of multi-GNSS differential code biases with satellite
+    antenna phase center corrections. GPS Solutions 30, 22 (2026).
+    <a href="https://doi.org/10.1007/s10291-025-01983-w" target="_blank">https://doi.org/10.1007/s10291-025-01983-w</a>
+  </p>
+  <p>
+    A combination is carried out following a specified sampling interval. BNC waits for incoming Broadcast Corrections
+    for the period
+    of one such interval. Corrections received later than that will be ignored. If incoming streams have different
+    rates,
+    only epochs that correspond to the sampling interval are used.
+  </p>
+  <p>
+    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 SSRA00BKG1 and SSRA00CNE1 and simultaneously carries out a PPP
+    solution
+    with observations from stream FFMJ01DEU0 to allow monitoring the quality of the combination product in the space
+    domain.
+  </p>
+  <p><img src="IMG/Figure28.png" width=1000 /></p>
+  <p>Figure 28: 'INTERNAL' PPP with BNC using a combination of Broadcast Corrections</p>
+
+  <p>
+  <h4 id="combimounttab">2.14.1 Combine Corrections Table - optional</h4>
+  </p>
+  <p>
+    Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Correction mountpoint from the
+    'Streams' section
+    and hit Enter.</p>
+  <p>
+    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.</p>
+  <p>
+    After that, double click on the 'Weight Factor' field to enter a weight to be applied to this stream in the
+    combination.
+    A Factor greater than 1 will enlarge the sigma of the clock pseudo-observations and with it down-weight its
+    contribution.</p>
+  <p>
+    Finally, double click on the 'Exclude Satellites' field and specify satellites or satellite systems, to exclude them
+    for an individual AC.
+    An entry 'G04,G31,R' means to excludes GPS satellites PRN 4 and 31 as well as all GLONASS satellites from one
+    individual AC.
+    Default is an empty option field, meaning that no satellite is excluded from this individual AC.</p>
+  <p>
+    Use the 'Attitude' field to select how satellite attitude is modelled when converting Antenna Phase Center (APC)
+    corrections to
+    Center-of-Mass (CoM) positions required for SP3 output. Three options are available:
+  <ul>
+    <li><b>Computed</b> (default): BNC applies its own kinematic attitude model:
+      GPS noon/midnight turn manoeuvres (Kouba 2009/2015, Bar-Sever 1996),
+      GLONASS yaw-fixed mode (Dilssner et al. 2011), and
+      Galileo / BDS orbit-normal mode switching (Kouba 2017, Dai et al. 2015, Steigenberger et al. 2018).</li>
+    <li><b>Nominal</b>: a simplified, continuous Sun-pointing model is used without any manoeuvre modelling.</li>
+    <li><b>SSR</b>: the yaw angle transmitted in the SSR phase bias message is used directly, if present for the
+      satellite and epoch.
+      If no yaw angle is available for a particular satellite in a given epoch, BNC falls back to 'Computed'.
+      Select this option only if you trust the yaw values provided by the Analysis Center.</li>
+  </ul>
+  Note that the attitude model affects APC-referenced correction streams only.
+  For CoM-referenced streams (SSRC) the Analysis Center has already applied its own attitude model before encoding.</p>
+  <p>
+    Note that the orbit information in the resulting 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.</p>
+  <p>
+    The combination process requires Broadcast Ephemeris.
+    Besides orbit and clock correction streams BNC should therefore pull a stream carrying Broadcast Ephemeris in the
+    form of RTCM Version 3 messages.
+    The following type of Broadcast navigation messages is used per individulal GNSS:</p>
+  <table>
+    <tr>
+      <td>Navigation </td>
+      <td>Description </td>
+      <td>Constellation </td>
+      <td>RTCM </td>
+    </tr>
+    <tr>
+      <td>Message Type </td>
+      <td> </td>
+      <td>and Signal </td>
+      <td>Message Type</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>LNAV</td>
+      <td> GPS Legacy navigation message </td>
+      <td>GPS L1 C/A </td>
+      <td>1019</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> QZSS Legacy navigation message </td>
+      <td>QZSS L1 C/A or L1 C/B </td>
+      <td>1044</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> NavIC Legacy navigation message </td>
+      <td>NavIC L5/S SPS </td>
+      <td>1041</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>FDMA</td>
+      <td> GLONASS Legacy FDMA navigation message </td>
+      <td>GLO L1 C/A </td>
+      <td>1020</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> from M-satellites </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>INAV</td>
+      <td> Galileo Integrity navigation message </td>
+      <td>GAL E1, E5b </td>
+      <td>1046</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>D1 </td>
+      <td> BeiDou-2/3 MEO/IGSO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td>D2 </td>
+      <td> BeiDou-2/3 GEO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>SBAS</td>
+      <td> SBAS navigation message </td>
+      <td>SBAS L1 </td>
+      <td>1043</td>
+    </tr>
+  </table>
+  <p>
+    It is possible to specify only one Broadcast Ephemeris Correction stream in the 'Combine Corrections' table.
+    Instead of combining corrections BNC will then add the corrections to the Broadcast Ephemeris with the possibility
+    to save final orbit and clock results in SP3 and/or Clock RINEX format.
+  </p>
+  <p>
+    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.</p>
+  <p>
+    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.
+  </p>
+
+  <p>
+    Default is an empty 'Combine Corrections' table, meaning that you do not want BNC to combine orbit and clock
+    correction streams.
+  </p>
+
+  <p>
+  <h4 id="combiadd">2.14.1.1 Add Row, Delete - optional</h4>
+  </p>
+  <p>
+    Hit 'Add Row' button to add another row to the 'Combine Corrections' table or hit the 'Delete' button to delete the
+    highlighted row(s).
+  </p>
+
+  <p>
+  <h4 id="combimethod">2.14.1.2 Method - mandatory if 'Combine Corrections' table is populated</h4>
+  </p>
+  <p>
+    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.</p>
+
+  <p>
+  <h4 id="combimaxres">2.14.1.3 Maximal Clock Residuum - mandatory if 'Combine Corrections' table is populated</h4>
+  </p>
+  <p>
+    BNC combines all incoming clocks according to specified weights. Individual clock estimates that differ by more than
+    'Maximal Clk Residuum' meters from the average of all clocks will be ignored.
+    It is suggested to specify a value of about 0.2 m for the Kalman Filter combination approach and
+    a value of about 3.0 meters for the Single-Epoch combination approach.</p>
+  <p>
+    Default is a 'Maximal Clk Residuum' of 999.0 meters.</p>
+
+  <p>
+  <h4 id="combimaxdisp">2.14.1.4 Maximal Orbit Displacement - mandatory if 'Combine Corrections' table is populated</h4>
+  </p>
+  <p>
+    BNC builds mean values for all incoming orbit corrections per satellite.
+    Individual orbit corrections that differ by more than 'Maximal Orb Displacement' meters from the average
+    of all orbit corrections per satellite will be ignored. It is suggested to specify a value of about 0.5 m.</p>
+  <p>
+    Default is a 'Maximal Orb Displacement' of 2.0 meters.</p>
+
+  <p>
+  <h4 id="combismpl">2.14.1.5 Sampling - mandatory if 'Combine Corrections' table is populated</h4>
+  </p>
+  <p>
+    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.</p>
+
+  <p>
+  <h4 id="combisatsys">2.14.1.6 Satellite Systems - mandatory if 'Combine Corrections' table is populated</h4>
+  </p>
+  <p>
+    Specify for each satellite system whether the clock corrections shall be combined.</p>
+
+  <p>
+  <h4 id="upclk">2.15 Upload Corrections</h4>
+  </p>
+  <p>
+    BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and
+    out-of-plane
+    components if they are
+  <ol type="a">
+    <li>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',</li>
-  <li>or generated by BNC while the program receives an ASCII stream of precise satellite orbits and clocks via IP port
+    <li>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. </li>
-</ol>
-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:
-<ul>
-  <li>Continuously receive up-to-date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites.
+  </ol>
+  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:
+  <ul>
+    <li>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.
       The following type of Broadcast navigation messages is used per individulal GNSS:
       <p>
-<table>
-<tr><td>Navigation 		</td><td>Description							</td><td>Constellation  		</td><td>RTCM </td></tr>
-<tr><td>Message Type	</td><td>										</td><td>and Signal 			</td><td>Message Type</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>LNAV</td><td>			GPS Legacy navigation message			</td><td>GPS  L1 C/A           	</td><td>1019</td></tr>
-<tr><td>	</td><td>			QZSS Legacy navigation message 			</td><td>QZSS L1 C/A or L1 C/B 	</td><td>1044</td></tr>
-<tr><td>	</td><td>			NavIC Legacy navigation message 		</td><td>NavIC L5/S SPS        	</td><td>1041</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>FDMA</td><td>			GLONASS Legacy FDMA navigation message	</td><td>GLO L1 C/A			 	</td><td>1020</td></tr>
-<tr><td>	</td><td>			from M-satellites						</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>INAV</td><td>			Galileo Integrity 	navigation message 	</td><td>GAL E1, E5b        	</td><td>1046</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>D1	</td><td>			BeiDou-2/3 MEO/IGSO navigation message 	</td><td>BDS B1I, B2I, B3I  	</td><td>1042</td></tr>
-<tr><td>D2	</td><td>			BeiDou-2/3 GEO      navigation message 	</td><td>BDS B1I, B2I, B3I 		</td><td>1042</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>SBAS</td><td>			SBAS      navigation message 			</td><td>SBAS L1            	</td><td>1043</td></tr>
-</table>
-  </li>
-</ul>
-Then, epoch by epoch:
-<ul>
-  <li>Continuously receive the best available orbit and clock estimates for all satellites in
+      <table>
+        <tr>
+          <td>Navigation </td>
+          <td>Description </td>
+          <td>Constellation </td>
+          <td>RTCM </td>
+        </tr>
+        <tr>
+          <td>Message Type </td>
+          <td> </td>
+          <td>and Signal </td>
+          <td>Message Type</td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td>LNAV</td>
+          <td> GPS Legacy navigation message </td>
+          <td>GPS L1 C/A </td>
+          <td>1019</td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> QZSS Legacy navigation message </td>
+          <td>QZSS L1 C/A or L1 C/B </td>
+          <td>1044</td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> NavIC Legacy navigation message </td>
+          <td>NavIC L5/S SPS </td>
+          <td>1041</td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td>FDMA</td>
+          <td> GLONASS Legacy FDMA navigation message </td>
+          <td>GLO L1 C/A </td>
+          <td>1020</td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> from M-satellites </td>
+          <td> </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td>INAV</td>
+          <td> Galileo Integrity navigation message </td>
+          <td>GAL E1, E5b </td>
+          <td>1046</td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td>D1 </td>
+          <td> BeiDou-2/3 MEO/IGSO navigation message </td>
+          <td>BDS B1I, B2I, B3I </td>
+          <td>1042</td>
+        </tr>
+        <tr>
+          <td>D2 </td>
+          <td> BeiDou-2/3 GEO navigation message </td>
+          <td>BDS B1I, B2I, B3I </td>
+          <td>1042</td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td>SBAS</td>
+          <td> SBAS navigation message </td>
+          <td>SBAS L1 </td>
+          <td>1043</td>
+        </tr>
+      </table>
+    </li>
+  </ul>
+  Then, epoch by epoch:
+  <ul>
+    <li>Continuously receive the best available orbit and clock estimates for all satellites in
       XYZ Earth-Centered-Earth-Fixed IGS20 reference system.
-      Receive them every epoch in plain ASCII format as provided by a real-time GNSS engine such as RTNET or generate them
+      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. </li>
-  <li>Calculate XYZ coordinates from Broadcast Ephemeris orbits.</li>
-  <li>Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS20 orbits.</li>
-  <li>Transform these differences into radial, along-track and out-of-plane corrections to Broadcast Ephemeris orbits.</li>
-  <li>Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris clocks and IGS20 clocks.</li>
-  <li>Encode Broadcast Ephemeris orbit and clock corrections, biases and atmospheric parameters in 'State Space Reperesentation' messages'</li>
-  <li>Upload Broadcast Correction stream to Ntrip Broadcaster.</li>
-</ul>
-<p>
-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.
-</p>
-<p>
-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.
-</p>
-<p>
-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.
-</p>
-
-<p>
-<b>'RTNET' Stream Format:</b> When uploading an SSR stream generated according to (b) then BNC requires
-precise GNSS orbits and clocks in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific ASCII format
-named 'RTNET' because the data may come from a real-time engine such as RTNET.
-The sampling interval for data transmission should not exceed 15 sec.
-Note that otherwise tools involved in IP streaming such as Ntrip Broadcasters or Ntrip Clients may respond with a timeout.
-</p>
-<p>
-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
-</p>
-<p>
-<ul>
-  <li>Satellite specific parameters </li>
-</ul>
-</p>
-<p>
-A set of parameters can be defined for each satellite as follows:
-<pre>
+    <li>Calculate XYZ coordinates from Broadcast Ephemeris orbits.</li>
+    <li>Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS20 orbits.</li>
+    <li>Transform these differences into radial, along-track and out-of-plane corrections to Broadcast Ephemeris orbits.
+    </li>
+    <li>Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris clocks and IGS20
+      clocks.</li>
+    <li>Encode Broadcast Ephemeris orbit and clock corrections, biases and atmospheric parameters in 'State Space
+      Reperesentation' messages'</li>
+    <li>Upload Broadcast Correction stream to Ntrip Broadcaster.</li>
+  </ul>
+  <p>
+    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.
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+    <b>'RTNET' Stream Format:</b> When uploading an SSR stream generated according to (b) then BNC requires
+    precise GNSS orbits and clocks in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific ASCII
+    format
+    named 'RTNET' because the data may come from a real-time engine such as RTNET.
+    The sampling interval for data transmission should not exceed 15 sec.
+    Note that otherwise tools involved in IP streaming such as Ntrip Broadcasters or Ntrip Clients may respond with a
+    timeout.
+  </p>
+  <p>
+    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
+  </p>
+  <p>
+  <ul>
+    <li>Satellite specific parameters </li>
+  </ul>
+  </p>
+  <p>
+    A set of parameters can be defined for each satellite as follows:
+  <pre>
 &lt;SatelliteID&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt;
               &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; ... &nbsp;
 </pre>
-The following satellite specific keys and values are currently specified for that in BNC:<br><br>
-<table>
-  <tr><td>&nbsp;<i>Key&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</i></td><td>&nbsp;&nbsp;<i>Values</i></td></tr>
-  <tr><td>&nbsp;APC      </td><td>&nbsp; &nbsp;Satellite Antenna Phase Center coordinate components in meters</td></tr>
-  <tr><td>&nbsp;Clk      </td><td>&nbsp; &nbsp;Satellite clock correction components in meters, meters per seconds and meters per sec&#178 (relativistic correction applied like in broadcast clocks)</td></tr>
-  <tr><td>&nbsp;ClkSig   </td><td>&nbsp; &nbsp;Standard deviation for satellite clock correction components in meters, meters per seconds and meters per sec&#178 (required for Clock RINEX file only) /td></tr>
-  <tr><td>&nbsp;Vel      </td><td>&nbsp; &nbsp;Satellite velocity components in meters per second</td></tr>
-  <tr><td>&nbsp;CoM      </td><td>&nbsp; &nbsp;Satellite Center of Mass coordinate components in meters</td></tr>
-  <tr><td>&nbsp;Ura      </td><td>&nbsp; &nbsp;User range accuracy value in meters</td></tr>
-  <tr><td>&nbsp;CodeBias </td><td>&nbsp; &nbsp;Satellite Code Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3/4 and preceded by total number of biases</td></tr>
-  <tr><td>&nbsp;PhaseBias</td><td>&nbsp; &nbsp;Satellite Phase Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3/4, preceded by total number of biases <br>&nbsp; &nbsp;and followed by Signal Integer Indicator, Signals Wilde-Lane Integer Indicator as well as Signal Discontinuity Counter</td></tr>
-  <tr><td>&nbsp;YawAngle </td><td>&nbsp; &nbsp;Satellite Yaw Angle in radian, restricted to be in [0, 2&#960], which shall be used for the computation of phase wind-up correction</td></tr>
-  <tr><td>&nbsp;YawRate  </td><td>&nbsp; &nbsp;Satellite Yaw Rate in radian per second which is the rate of Yaw Angle</td></tr>
-</table>
-<p>
-<ul>
-  <li> Non-satellite specific parameters
-</ul>
-</p>
-<p>
-The following syntax will be used:
-</p>
-<pre>
+  The following satellite specific keys and values are currently specified for that in BNC:<br><br>
+  <table>
+    <tr>
+      <td>&nbsp;<i>Key&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</i></td>
+      <td>&nbsp;&nbsp;<i>Values</i></td>
+    </tr>
+    <tr>
+      <td>&nbsp;APC </td>
+      <td>&nbsp; &nbsp;Satellite Antenna Phase Center coordinate components in meters</td>
+    </tr>
+    <tr>
+      <td>&nbsp;Clk </td>
+      <td>&nbsp; &nbsp;Satellite clock correction components in meters, meters per seconds and meters per sec&#178
+        (relativistic correction applied like in broadcast clocks)</td>
+    </tr>
+    <tr>
+      <td>&nbsp;ClkSig </td>
+      <td>&nbsp; &nbsp;Standard deviation for satellite clock correction components in meters, meters per seconds and
+        meters per sec&#178 (required for Clock RINEX file only) /td>
+    </tr>
+    <tr>
+      <td>&nbsp;Vel </td>
+      <td>&nbsp; &nbsp;Satellite velocity components in meters per second</td>
+    </tr>
+    <tr>
+      <td>&nbsp;CoM </td>
+      <td>&nbsp; &nbsp;Satellite Center of Mass coordinate components in meters</td>
+    </tr>
+    <tr>
+      <td>&nbsp;Ura </td>
+      <td>&nbsp; &nbsp;User range accuracy value in meters</td>
+    </tr>
+    <tr>
+      <td>&nbsp;CodeBias </td>
+      <td>&nbsp; &nbsp;Satellite Code Biases in meters with two characters for frequency and tracking mode per bias as
+        defined in RINEX 3/4 and preceded by total number of biases</td>
+    </tr>
+    <tr>
+      <td>&nbsp;PhaseBias</td>
+      <td>&nbsp; &nbsp;Satellite Phase Biases in meters with two characters for frequency and tracking mode per bias as
+        defined in RINEX 3/4, preceded by total number of biases <br>&nbsp; &nbsp;and followed by Signal Integer
+        Indicator, Signals Wilde-Lane Integer Indicator as well as Signal Discontinuity Counter</td>
+    </tr>
+    <tr>
+      <td>&nbsp;YawAngle </td>
+      <td>&nbsp; &nbsp;Satellite Yaw Angle in radian, restricted to be in [0, 2&#960], which shall be used for the
+        computation of phase wind-up correction</td>
+    </tr>
+    <tr>
+      <td>&nbsp;YawRate </td>
+      <td>&nbsp; &nbsp;Satellite Yaw Rate in radian per second which is the rate of Yaw Angle</td>
+    </tr>
+  </table>
+  <p>
+  <ul>
+    <li> Non-satellite specific parameters
+  </ul>
+  </p>
+  <p>
+    The following syntax will be used:
+  </p>
+  <pre>
 &lt;key&gt; &lt;value1 value2 ...&gt;
 &nbsp;
 </pre>
-<p>
-</ul>
-The following non-satellite specific keys and values are currently specified in BNC:<br><br>
-<table>
-  <tr><td>&nbsp;<i>Key&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</i></td><td><i>&nbsp; &nbsp;Values</i></td></tr>
-  <tr><td>&nbsp;IND </td><td>&nbsp; &nbsp;Stands for phase bias information and is followed by Dispersive Bias Consistency Indicator and MW Consistency Indicator</td></tr>
-  <tr><td>&nbsp;VTEC</td><td>&nbsp; &nbsp;Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric Layers</td></tr>
-</table>
-<br>
-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.
-</p>
-<p>
-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.
-</p>
-
-<p>
-Example for 'RTNET' stream content and format:
-</p>
-<p>
-<pre><p style="font-family:Monospace">
+  <p>
+    </ul>
+    The following non-satellite specific keys and values are currently specified in BNC:<br><br>
+  <table>
+    <tr>
+      <td>&nbsp;<i>Key&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</i></td>
+      <td><i>&nbsp; &nbsp;Values</i></td>
+    </tr>
+    <tr>
+      <td>&nbsp;IND </td>
+      <td>&nbsp; &nbsp;Stands for phase bias information and is followed by Dispersive Bias Consistency Indicator and MW
+        Consistency Indicator</td>
+    </tr>
+    <tr>
+      <td>&nbsp;VTEC</td>
+      <td>&nbsp; &nbsp;Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric
+        Layers</td>
+    </tr>
+  </table>
+  <br>
+  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.
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+    Example for 'RTNET' stream content and format:
+  </p>
+  <p>
+  <pre><p style="font-family:Monospace">
 *  2022 11 25 22 04 05.000
 G01 Clk 2     73898.6410 -0.00164097340 ClkSig 2   0.0024  0.00021199856 CoM 3  -3022799.7396 -14423300.4562 -22402573.0244 Vel 3   2691.3388   -619.5739     69.3300 APC 3  -3022799.9547 -14423299.6874 -22402571.6928 YawAngle 1 -2.756 CodeBias 3 1C   -2.6653 1W   -3.0640 2W   -5.0462
@@ -5394,92 +8346,138 @@
 </p></pre>
 
-<p>
-Note that the end of an epoch in the incoming stream is indicated by an ASCII string 'EOE' (for End Of Epoch).
-</p>
-<p>
-The following screenshot shows the encoding and uploading of several streams using precise orbits and clocks coming from a real-time network engine
-in 'RTNET' ASCII format. The streams are uploaded to Ntrip Broadcaster 'products.igs-ip.net'. They are referred to APC or CoM and IGS20 or DREF91.
-Required Broadcast Ephemeris are received via stream 'BCEP00BKG0'.
-</p>
-<p><img src="IMG/Figure29.png"width=1000/></p>
-<p>Figure 29: BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster</p>
-
-<p><h4 id="upadd">2.15.1 Add, Delete Row - optional</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="uphost">2.15.2 Host, Port, Mountpoint, Ntrip Version, User and Password - optional</h4></p>
-<p>
-Specify the domain name or IP number of an Ntrip Broadcaster for uploading the stream. Furthermore, specify the caster's
-listening IP port and an upload mountpoint. Select the Ntrip Version that shall be used for data upload and, depending on this,
-an upload user (Ntrip Version 2 only) and an upload password.
-</p>
-<p>
-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).
-</p>
-<p>
-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 9-character ID (capital letters) plus an integer number.
-</p>
-<p>
-For stream upload the Ntrip Version can be chosen. An Ntrip version 1 upload is protected through an upload 'Password' only.
-For an Ntrip Version 2 upload an upload 'User' is required in addition. Enter user and password you received from the
-Ntrip Broadcaster operator along with the mountpoint(s).
-</p>
-<p>
-If 'Host', 'Port', 'Mountpoint', 'Ntrip' Version, 'User' and 'Password' are set, the stream will be encoded into 'State Space Representation' (SSR)
-messages and uploaded to the specified broadcaster following the specified Ntrip transport protocol options.
-</p>
-
-<p><h4 id="upsystem">2.15.3 System - mandatory if 'Host' is set</h4></p>
-<p>
-BNC allows configuring several Broadcast Correction streams for upload, so that they may 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
-</p>
-<table>
-  <tr><td>&nbsp;IGS20:     </td><td>&nbsp; &nbsp;Stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame 2020 (ITRF2020)</td></tr>
-  <tr><td>&nbsp;ETRF2000:  </td><td>&nbsp; &nbsp;Stands for the European Terrestrial Reference Frame 2000 adopted by EUREF</td></tr>
-  <tr><td>&nbsp;GDA2020:   </td><td>&nbsp; &nbsp;Stands for the Geodetic Datum Australia 2020 as adopted for Australia</td></tr>
-  <tr><td>&nbsp;SIRGAS2000:</td><td>&nbsp; &nbsp;Stands for the Geodetic Datum adopted for Brazil</td></tr>
-  <tr><td>&nbsp;DREF91:    </td><td>&nbsp; &nbsp;Stands for the Geodetic Datum adopted for Germany</td></tr>
-  <tr><td>&nbsp;Custom:    </td><td>&nbsp; &nbsp;Allows a transformation of Broadcast Corrections from the IGS20 system to any other system through specifying
-                              up to 14 Helmert Transformation Parameters </td></tr>
-</table>
-With each target reference system a respective Service CRS and RTCM CRS message is generated and uploaded.
-<p>
-Because a mathematically strict transformation to a regional reference system is not possible on the BNC server side when a scale factor is involved,
-the program follows an approximate solution. While <u>orbits</u> are transformed in full accordance with given equations,
-a transformed <u>clock</u> is derived through applying correction term
-</p>
-<pre>
+  <p>
+    Note that the end of an epoch in the incoming stream is indicated by an ASCII string 'EOE' (for End Of Epoch).
+  </p>
+  <p>
+    The following screenshot shows the encoding and uploading of several streams using precise orbits and clocks coming
+    from a real-time network engine
+    in 'RTNET' ASCII format. The streams are uploaded to Ntrip Broadcaster 'products.igs-ip.net'. They are referred to
+    APC or CoM and IGS20 or DREF91.
+    Required Broadcast Ephemeris are received via stream 'BCEP00BKG0'.
+  </p>
+  <p><img src="IMG/Figure29.png" width=1000 /></p>
+  <p>Figure 29: BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an
+    Ntrip Broadcaster</p>
+
+  <p>
+  <h4 id="upadd">2.15.1 Add, Delete Row - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="uphost">2.15.2 Host, Port, Mountpoint, Ntrip Version, User and Password - optional</h4>
+  </p>
+  <p>
+    Specify the domain name or IP number of an Ntrip Broadcaster for uploading the stream. Furthermore, specify the
+    caster's
+    listening IP port and an upload mountpoint. Select the Ntrip Version that shall be used for data upload and,
+    depending on this,
+    an upload user (Ntrip Version 2 only) and an upload password.
+  </p>
+  <p>
+    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).
+  </p>
+  <p>
+    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 9-character ID (capital letters) plus an integer number.
+  </p>
+  <p>
+    For stream upload the Ntrip Version can be chosen. An Ntrip version 1 upload is protected through an upload
+    'Password' only.
+    For an Ntrip Version 2 upload an upload 'User' is required in addition. Enter user and password you received from
+    the
+    Ntrip Broadcaster operator along with the mountpoint(s).
+  </p>
+  <p>
+    If 'Host', 'Port', 'Mountpoint', 'Ntrip' Version, 'User' and 'Password' are set, the stream will be encoded into
+    'State Space Representation' (SSR)
+    messages and uploaded to the specified broadcaster following the specified Ntrip transport protocol options.
+  </p>
+
+  <p>
+  <h4 id="upsystem">2.15.3 System - mandatory if 'Host' is set</h4>
+  </p>
+  <p>
+    BNC allows configuring several Broadcast Correction streams for upload, so that they may 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
+  </p>
+  <table>
+    <tr>
+      <td>&nbsp;IGS20: </td>
+      <td>&nbsp; &nbsp;Stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame 2020
+        (ITRF2020)</td>
+    </tr>
+    <tr>
+      <td>&nbsp;ETRF2000: </td>
+      <td>&nbsp; &nbsp;Stands for the European Terrestrial Reference Frame 2000 adopted by EUREF</td>
+    </tr>
+    <tr>
+      <td>&nbsp;GDA2020: </td>
+      <td>&nbsp; &nbsp;Stands for the Geodetic Datum Australia 2020 as adopted for Australia</td>
+    </tr>
+    <tr>
+      <td>&nbsp;SIRGAS2000:</td>
+      <td>&nbsp; &nbsp;Stands for the Geodetic Datum adopted for Brazil</td>
+    </tr>
+    <tr>
+      <td>&nbsp;DREF91: </td>
+      <td>&nbsp; &nbsp;Stands for the Geodetic Datum adopted for Germany</td>
+    </tr>
+    <tr>
+      <td>&nbsp;Custom: </td>
+      <td>&nbsp; &nbsp;Allows a transformation of Broadcast Corrections from the IGS20 system to any other system
+        through specifying
+        up to 14 Helmert Transformation Parameters </td>
+    </tr>
+  </table>
+  With each target reference system a respective Service CRS and RTCM CRS message is generated and uploaded.
+  <p>
+    Because a mathematically strict transformation to a regional reference system is not possible on the BNC server side
+    when a scale factor is involved,
+    the program follows an approximate solution. While <u>orbits</u> are transformed in full accordance with given
+    equations,
+    a transformed <u>clock</u> is derived through applying correction term
+  </p>
+  <pre>
    dC = (s - 1) / s * &rho; / c
 </pre>
-<p>
-where s is the transformation scale, c is the speed of light, and &rho;
-are the topocentric distance between an (approximate) center of the transformation's validity area and the satellite.
-</p>
-<p>
-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.
-</p>
-<p>
-<b>IGS20:</b> As the orbits and clocks coming from real-time GNSS engine are expected to be in the IGS20 system,
-no transformation is carried out if this option is selected.
-</p>
-<p>
-As long as no updated transformation parameters are available regarding IGS20,
-a transformation from 'ITRF2020-&gt;ITRF2014' is done in a fist step using the following
-14 Helmert Transformation Parameters, which are available at
-<a href="https://itrf.ign.fr/en/solutions/transformations" target="_blank">https://itrf.ign.fr/en/solutions/transformations</a>
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    where s is the transformation scale, c is the speed of light, and &rho;
+    are the topocentric distance between an (approximate) center of the transformation's validity area and the
+    satellite.
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    <b>IGS20:</b> As the orbits and clocks coming from real-time GNSS engine are expected to be in the IGS20 system,
+    no transformation is carried out if this option is selected.
+  </p>
+  <p>
+    As long as no updated transformation parameters are available regarding IGS20,
+    a transformation from 'ITRF2020-&gt;ITRF2014' is done in a fist step using the following
+    14 Helmert Transformation Parameters, which are available at
+    <a href="https://itrf.ign.fr/en/solutions/transformations"
+      target="_blank">https://itrf.ign.fr/en/solutions/transformations</a>
+  </p>
+  <pre><p style="font-family:Monospace">
    dx  = -0.0014;
    dy  = -0.0009;
@@ -5503,6 +8501,6 @@
    t0  =  2015.0;
 </p></pre>
-where
-<pre>
+  where
+  <pre>
 <table>
   <tr><td>&nbsp;dx  </td><td>&nbsp; &nbsp;Translation in X at epoch t0 [m]</td></tr>
@@ -5520,11 +8518,12 @@
 </table>
 </pre>
-<p>
-<b>ETRF2000:</b> The transformation Parameters from ITRF2014 to ETRF2000 are taken from the EUREF Technical Note 1
-'EUREF Technical Note 1: Relationship and Transformation between
-the International and the European Terrestrial Reference Systems', Zuheir Altamimi, June 28, 2018:
-<a href="http://etrs89.ensg.ign.fr/pub/EUREF-TN-1.pdf" target="_blank">http://etrs89.ensg.ign.fr/pub/EUREF-TN-1.pdf</a>:
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    <b>ETRF2000:</b> The transformation Parameters from ITRF2014 to ETRF2000 are taken from the EUREF Technical Note 1
+    'EUREF Technical Note 1: Relationship and Transformation between
+    the International and the European Terrestrial Reference Systems', Zuheir Altamimi, June 28, 2018:
+    <a href="http://etrs89.ensg.ign.fr/pub/EUREF-TN-1.pdf"
+      target="_blank">http://etrs89.ensg.ign.fr/pub/EUREF-TN-1.pdf</a>:
+  </p>
+  <pre><p style="font-family:Monospace">
     dx  =  0.0547;
     dy  =  0.0522;
@@ -5548,9 +8547,10 @@
     t0  =  2010.0;
 </p></pre>
-<p>
-<b>GDA2020:</b> The parameters for the transformation 'ITRF2014-&gt;GDA2020' were provided by Ryan Ruddick (Geoscience Australia):
-via personal communication:
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    <b>GDA2020:</b> The parameters for the transformation 'ITRF2014-&gt;GDA2020' were provided by Ryan Ruddick
+    (Geoscience Australia):
+    via personal communication:
+  </p>
+  <pre><p style="font-family:Monospace">
     dx  = 0.0;
     dy  = 0.0;
@@ -5574,8 +8574,9 @@
     t0  = 2020.0;
 </p></pre>
-<p>
-<b>SIRGAS2000:</b> The parameters for the transformation 'IGb14-&gt;SIRGAS2000' were provided from Sonia Costa, BRA via personal communication:</u>.
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    <b>SIRGAS2000:</b> The parameters for the transformation 'IGb14-&gt;SIRGAS2000' were provided from Sonia Costa, BRA
+    via personal communication:</u>.
+  </p>
+  <pre><p style="font-family:Monospace">
     dx  = -0.0027;
     dy  = -0.0025;
@@ -5599,9 +8600,10 @@
     t0  =  2000.0;
 </p></pre>
-<p>
-<b>DREF91:</b> The parameters for the transformation 'IGb14-&gt;DREF91' were provided from Peter Franke, BKG, Germany
-  via personal communication:
-</p>
-<pre><p style="font-family:Monospace">
+  <p>
+    <b>DREF91:</b> The parameters for the transformation 'IGb14-&gt;DREF91' were provided from Peter Franke, BKG,
+    Germany
+    via personal communication:
+  </p>
+  <pre><p style="font-family:Monospace">
     dx  =  0.0547;
     dy  =  0.0522;
@@ -5626,796 +8628,1259 @@
     t0  =  2010.0;
 </p></pre>
-<p>
-<b>Custom:</b> Feel free to specify your own 14 Helmert Transformation parameters for transformations from IGS20/ITRF2020 into your own target system.
-</p>
-<p><img src="IMG/Figure30.png"width=700/></p>
-<p>Figure 30: Setting BNC's Custom Transformation Parameters window</p>
-
-<p><h4 id="upformat">2.15.4 Format - mandatory if 'Host' is set</h4></p>
-<p>
-BNC may upload the Broadcast Correction streams using different Formats. Supported are:
-<p>
-<ul>
-  <li>IGS-SSR which was developed within the IGS Real-Time Working Group (<a href="https://files.igs.org/pub/data/format/igs_ssr_v1.pdf" target="_blank">https://files.igs.org/pub/data/format/igs_ssr_v1.pdf</a>), and</li>
-  <li>RTCM-SSR which stands for the standardized and proposed SSR Messages which are developed within the RTCM SC-104 Working Group 'State Space Representation' (<a href="https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards" target="_blank">https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards</a>).</li>
-</ul>
-</p>
-<p><h4 id="upcom">2.15.5 Center of Mass - optional</h4></p>
-<p>
-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.
-</p>
-<p><h4 id="upsp3">2.15.6  SP3 File - optional</h4></p>
-<p>
-Specify a path for saving the generated orbit corrections as SP3 orbit files
-(<a href="http://epncb.eu/ftp/data/format/sp3d.pdf" target="_blank">http://epncb.eu/ftp/data/format/sp3d.pdf</a>).
-The following is a path example for a Linux system:
-<pre>
+  <p>
+    <b>Custom:</b> Feel free to specify your own 14 Helmert Transformation parameters for transformations from
+    IGS20/ITRF2020 into your own target system.
+  </p>
+  <p><img src="IMG/Figure30.png" width=700 /></p>
+  <p>Figure 30: Setting BNC's Custom Transformation Parameters window</p>
+
+  <p>
+  <h4 id="upformat">2.15.4 Format - mandatory if 'Host' is set</h4>
+  </p>
+  <p>
+    BNC may upload the Broadcast Correction streams using different Formats. Supported are:
+  <p>
+  <ul>
+    <li>IGS-SSR which was developed within the IGS Real-Time Working Group (<a
+        href="https://files.igs.org/pub/data/format/igs_ssr_v1.pdf"
+        target="_blank">https://files.igs.org/pub/data/format/igs_ssr_v1.pdf</a>), and</li>
+    <li>RTCM-SSR which stands for the standardized and proposed SSR Messages which are developed within the RTCM SC-104
+      Working Group 'State Space Representation' (<a
+        href="https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards"
+        target="_blank">https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards</a>).
+    </li>
+  </ul>
+  </p>
+  <p>
+  <h4 id="upcom">2.15.5 Center of Mass - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+  <h4 id="upsp3">2.15.6 SP3 File - optional</h4>
+  </p>
+  <p>
+    Specify a path for saving the generated orbit corrections as SP3 orbit files
+    (<a href="http://epncb.eu/ftp/data/format/sp3d.pdf" target="_blank">http://epncb.eu/ftp/data/format/sp3d.pdf</a>).
+    The following is a path example for a Linux system:
+  <pre>
    /home/user/BKG0MGXRTS${V3PROD}.SP3
 </pre>
-If the specified directory does not exist, BNC will not create SP3 orbit files.
-</p>
-<p>
-For file naming, BNC follows the new format convention according to IGS products
-<a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf" target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
-</p>
-<pre>
+  If the specified directory does not exist, BNC will not create SP3 orbit files.
+  </p>
+  <p>
+    For file naming, BNC follows the new format convention according to IGS products
+    <a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf"
+      target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
+  </p>
+  <pre>
   AAAVPPPTTT_YYYYDDDHHMM_LEN_SMP_CNT.FMT
 </pre>
-With
-<p>
-<table>
-  <tr><td>&nbsp; AAA        </td><td>&nbsp; &nbsp; Analysis Center abbrevaition, here BKG</td></tr>
-  <tr><td>&nbsp; V          </td><td>&nbsp; &nbsp; Version / Solution identifier (0-9), here 0</td></tr>
-  <tr><td>&nbsp; PPP        </td><td>&nbsp; &nbsp; Project/Campaign identification, here Multi-GNSS product (MGX)</td></tr>
-  <tr><td>&nbsp; TTT        </td><td>&nbsp; &nbsp; Solution Type, here real-time streamed product (RTS)</td></tr>
-  <tr><td>&nbsp; YYYYDOYHHMM</td><td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td></tr>
-  <tr><td>&nbsp; LEN        </td><td>&nbsp; &nbsp; Intended product period of the file </td></tr>
-  <tr><td>&nbsp; SMP        </td><td>&nbsp; &nbsp; Data sampling rate</td></tr>
-  <tr><td>&nbsp; CNT        </td><td>&nbsp; &nbsp; Content type ORB</td></tr>
-  <tr><td>&nbsp; FMT        </td><td>&nbsp; &nbsp; File format, here SP3</td></tr>
-</table>
-</p>
-<p>
-Note that '${V3PROD}' produces the part 'YYYYDDDHHMM_LEN_SMP_CNT' of the filename according the 'Upload Corrections' setup.
-</p>
-A result for examle is:
-<pre>
+  With
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; AAA </td>
+      <td>&nbsp; &nbsp; Analysis Center abbrevaition, here BKG</td>
+    </tr>
+    <tr>
+      <td>&nbsp; V </td>
+      <td>&nbsp; &nbsp; Version / Solution identifier (0-9), here 0</td>
+    </tr>
+    <tr>
+      <td>&nbsp; PPP </td>
+      <td>&nbsp; &nbsp; Project/Campaign identification, here Multi-GNSS product (MGX)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; TTT </td>
+      <td>&nbsp; &nbsp; Solution Type, here real-time streamed product (RTS)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; YYYYDOYHHMM</td>
+      <td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td>
+    </tr>
+    <tr>
+      <td>&nbsp; LEN </td>
+      <td>&nbsp; &nbsp; Intended product period of the file </td>
+    </tr>
+    <tr>
+      <td>&nbsp; SMP </td>
+      <td>&nbsp; &nbsp; Data sampling rate</td>
+    </tr>
+    <tr>
+      <td>&nbsp; CNT </td>
+      <td>&nbsp; &nbsp; Content type ORB</td>
+    </tr>
+    <tr>
+      <td>&nbsp; FMT </td>
+      <td>&nbsp; &nbsp; File format, here SP3</td>
+    </tr>
+  </table>
+  </p>
+  <p>
+    Note that '${V3PROD}' produces the part 'YYYYDDDHHMM_LEN_SMP_CNT' of the filename according the 'Upload Corrections'
+    setup.
+  </p>
+  A result for examle is:
+  <pre>
   BKG0MGXRTS_20223330000_01D_01M_ORB.SP3
 </pre>
-<p>
-Default is an empty option field, meaning that you do not want BNC to save the uploaded stream content in daily SP3 files.
-</p>
-<p>
-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.
-</p>
-<p>
-For GLONASS satellites, that APC/CoM offset is rotated into the satellite-fixed frame using the satellite's
-yaw attitude. BNC assumes the nominal Sun-pointing yaw-steering law used for the other GNSS systems, except
-close to the orbit noon and midnight points when the Sun's elevation above the orbital plane (the 'beta'
-angle) is small. There, GLONASS-M satellites are known to stop tracking that law and instead hold the yaw
-angle fixed, following the model described in Dilssner, Springer, Flohrer, Dow (2011), 'The GLONASS-M
-satellite yaw-attitude model', Advances in Space Research 47(1), 160-171. Without that correction, the
-converted GLONASS CoM position can be off by several decimeters in the along-track and cross-track
-components in that situation. The maximum yaw rate used to decide when GLONASS-M can no longer follow the
-nominal law (0.25 deg/s) is taken from the literature and not calibrated against any specific satellite, so
-results should be checked against independently known attitude or orbit information where high accuracy on
-GLONASS is required.
-</p>
-<p>
- Note that clocks in the SP3 orbit files are not corrected for the conventional periodic relativistic effect.
-</p>
-<p>
-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.
-</p>
-<p>
-Note that BNC outputs a complete list of SP3 'Epoch Header Records', even if no 'Position and Clock Records' are available for certain epochs
-because of stream outages. Note further that the 'Number of Epochs' in the first SP3 header record may not be correct because that number
-is not available when the file is created. Depending on your processing software (e.g. Bernese GNSS Software, BSW) it could therefore be necessary
-to correct an incorrect 'Number of Epochs' in the file before you use it in post processing.
-</p>
-
-<p><h4 id="uprinex">2.15.7 RNX File - optional</h4></p>
-<p>
-The clock corrections generated by BNC for upload can be logged in Clock RINEX format
-<a href="https://files.igs.org/pub/data/format/rinex_clock304.txt" target="_blank">https://files.igs.org/pub/data/format/rinex_clock304.txt</a>:.
-</p>
-<p>
-Specify a path for saving the generated clock corrections as Clock RINEX files. The following is a path example for a Linux system:
-<pre>
+  <p>
+    Default is an empty option field, meaning that you do not want BNC to save the uploaded stream content in daily SP3
+    files.
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    For GLONASS satellites, that APC/CoM offset is rotated into the satellite-fixed frame using the satellite's
+    yaw attitude. BNC assumes the nominal Sun-pointing yaw-steering law used for the other GNSS systems, except
+    close to the orbit noon and midnight points when the Sun's elevation above the orbital plane (the 'beta'
+    angle) is small. There, GLONASS-M satellites are known to stop tracking that law and instead hold the yaw
+    angle fixed, following the model described in Dilssner, Springer, Flohrer, Dow (2011), 'The GLONASS-M
+    satellite yaw-attitude model', Advances in Space Research 47(1), 160-171. Without that correction, the
+    converted GLONASS CoM position can be off by several decimeters in the along-track and cross-track
+    components in that situation. The maximum yaw rate used to decide when GLONASS-M can no longer follow the
+    nominal law (0.25 deg/s) is taken from the literature and not calibrated against any specific satellite, so
+    results should be checked against independently known attitude or orbit information where high accuracy on
+    GLONASS is required.
+  </p>
+  <p>
+    Note that clocks in the SP3 orbit files are not corrected for the conventional periodic relativistic effect.
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Note that BNC outputs a complete list of SP3 'Epoch Header Records', even if no 'Position and Clock Records' are
+    available for certain epochs
+    because of stream outages. Note further that the 'Number of Epochs' in the first SP3 header record may not be
+    correct because that number
+    is not available when the file is created. Depending on your processing software (e.g. Bernese GNSS Software, BSW)
+    it could therefore be necessary
+    to correct an incorrect 'Number of Epochs' in the file before you use it in post processing.
+  </p>
+
+  <p>
+  <h4 id="uprinex">2.15.7 RNX File - optional</h4>
+  </p>
+  <p>
+    The clock corrections generated by BNC for upload can be logged in Clock RINEX format
+    <a href="https://files.igs.org/pub/data/format/rinex_clock304.txt"
+      target="_blank">https://files.igs.org/pub/data/format/rinex_clock304.txt</a>:.
+  </p>
+  <p>
+    Specify a path for saving the generated clock corrections as Clock RINEX files. The following is a path example for
+    a Linux system:
+  <pre>
    /home/user/BKG0MGXRTS${V3PROD}.CLK
 </pre>
-If the specified directory does not exist, BNC will not create Clock RINEX files.
-</p>
-<p>
-For file naming, BNC follows the new format convention according to IGS products
-<a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf" target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
-</p>
-<pre>
+  If the specified directory does not exist, BNC will not create Clock RINEX files.
+  </p>
+  <p>
+    For file naming, BNC follows the new format convention according to IGS products
+    <a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf"
+      target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
+  </p>
+  <pre>
   AAAVPPPTTT_YYYYDDDHHMM_LEN_SMP_CNT.FMT
 </pre>
-With
-<p>
-<table>
-  <tr><td>&nbsp; AAA        </td><td>&nbsp; &nbsp; Analysis Center abbrevaition, here BKG</td></tr>
-  <tr><td>&nbsp; V          </td><td>&nbsp; &nbsp; Version / Solution identifier (0-9), here 0</td></tr>
-  <tr><td>&nbsp; PPP        </td><td>&nbsp; &nbsp; Project/Campaign identification, here Multi-GNSS product (MGX)</td></tr>
-  <tr><td>&nbsp; TTT        </td><td>&nbsp; &nbsp; Solution Type, here real-time streamed product (RTS)</td></tr>
-  <tr><td>&nbsp; YYYYDOYHHMM</td><td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td></tr>
-  <tr><td>&nbsp; LEN        </td><td>&nbsp; &nbsp; Intended product period of the file </td></tr>
-  <tr><td>&nbsp; SMP        </td><td>&nbsp; &nbsp; Data sampling rate</td></tr>
-  <tr><td>&nbsp; CNT        </td><td>&nbsp; &nbsp; Content type CLK</td></tr>
-  <tr><td>&nbsp; FMT        </td><td>&nbsp; &nbsp; File format, here CLK</td></tr>
-</table>
-</p>
-<p>
-Note that '${V3PROD}' produces the part 'YYYYDDDHHMM_LEN_SMP_CNT' of the filename according the 'Upload Corrections' setup.
-</p>
-A result for examle is:
-<pre>
+  With
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; AAA </td>
+      <td>&nbsp; &nbsp; Analysis Center abbrevaition, here BKG</td>
+    </tr>
+    <tr>
+      <td>&nbsp; V </td>
+      <td>&nbsp; &nbsp; Version / Solution identifier (0-9), here 0</td>
+    </tr>
+    <tr>
+      <td>&nbsp; PPP </td>
+      <td>&nbsp; &nbsp; Project/Campaign identification, here Multi-GNSS product (MGX)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; TTT </td>
+      <td>&nbsp; &nbsp; Solution Type, here real-time streamed product (RTS)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; YYYYDOYHHMM</td>
+      <td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td>
+    </tr>
+    <tr>
+      <td>&nbsp; LEN </td>
+      <td>&nbsp; &nbsp; Intended product period of the file </td>
+    </tr>
+    <tr>
+      <td>&nbsp; SMP </td>
+      <td>&nbsp; &nbsp; Data sampling rate</td>
+    </tr>
+    <tr>
+      <td>&nbsp; CNT </td>
+      <td>&nbsp; &nbsp; Content type CLK</td>
+    </tr>
+    <tr>
+      <td>&nbsp; FMT </td>
+      <td>&nbsp; &nbsp; File format, here CLK</td>
+    </tr>
+  </table>
+  </p>
+  <p>
+    Note that '${V3PROD}' produces the part 'YYYYDDDHHMM_LEN_SMP_CNT' of the filename according the 'Upload Corrections'
+    setup.
+  </p>
+  A result for examle is:
+  <pre>
   BKG0MGXRTS_20223330000_01D_05S_CLK.CLK
 </pre>
-<p>
-Default is an empty option field, meaning that you do not want BNC to save the uploaded stream content in daily Clock RINEX files.
-</p>
-<p>
-Note further that clocks in the Clock RINEX files are not corrected for the conventional periodic relativistic effect.
-</p>
-<p><h4 id="upsinex">2.15.8 BSX File - optional</h4></p>
-<p>
-The satellite biases generated by BNC for upload can be logged in SINEX Bias format
-<a href="https://files.igs.org/pub/data/format/sinex_bias_100.pdf" target="_blank">https://files.igs.org/pub/data/format/sinex_bias_100.pdf</a>:.
-</p>
-<p>
-Specify a path for saving the generated clock corrections as Clock RINEX files. The following is a path example for a Linux system:
-<pre>
+  <p>
+    Default is an empty option field, meaning that you do not want BNC to save the uploaded stream content in daily
+    Clock RINEX files.
+  </p>
+  <p>
+    Note further that clocks in the Clock RINEX files are not corrected for the conventional periodic relativistic
+    effect.
+  </p>
+  <p>
+  <h4 id="upsinex">2.15.8 BSX File - optional</h4>
+  </p>
+  <p>
+    The satellite biases generated by BNC for upload can be logged in SINEX Bias format
+    <a href="https://files.igs.org/pub/data/format/sinex_bias_100.pdf"
+      target="_blank">https://files.igs.org/pub/data/format/sinex_bias_100.pdf</a>:.
+  </p>
+  <p>
+    Specify a path for saving the generated clock corrections as Clock RINEX files. The following is a path example for
+    a Linux system:
+  <pre>
    /home/user/BKG0MGXRTS${V3PROD}.BIA
 </pre>
-If the specified directory does not exist, BNC will not create SINEX Bias files.
-</p>
-<p>
-For file naming, BNC follows the new format convention according to IGS products
-<a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf" target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
-</p>
-<pre>
+  If the specified directory does not exist, BNC will not create SINEX Bias files.
+  </p>
+  <p>
+    For file naming, BNC follows the new format convention according to IGS products
+    <a href="https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf"
+      target="_blank">https://files.igs.org/pub/resource/guidelines/Guidelines_For_Long_Product_Filenames_in_the_IGS_v2.0.pdf</a>:
+  </p>
+  <pre>
   AAAVPPPTTT_YYYYDDDHHMM_LEN_SMP_CNT.FMT
 </pre>
-With
-<p>
-<table>
-  <tr><td>&nbsp; AAA        </td><td>&nbsp; &nbsp; Analysis Center abbrevaition, here BKG</td></tr>
-  <tr><td>&nbsp; V          </td><td>&nbsp; &nbsp; Version / Solution identifier (0-9), here 0</td></tr>
-  <tr><td>&nbsp; PPP        </td><td>&nbsp; &nbsp; Project/Campaign identification, here Multi-GNSS product (MGX)</td></tr>
-  <tr><td>&nbsp; TTT        </td><td>&nbsp; &nbsp; Solution Type, here real-time streamed product (RTS)</td></tr>
-  <tr><td>&nbsp; YYYYDOYHHMM</td><td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td></tr>
-  <tr><td>&nbsp; LEN        </td><td>&nbsp; &nbsp; Intended product period of the file </td></tr>
-  <tr><td>&nbsp; SMP        </td><td>&nbsp; &nbsp; Data sampling rate</td></tr>
-  <tr><td>&nbsp; CNT        </td><td>&nbsp; &nbsp; Content type, here Observable-specific signal biases, code and phase (OSB)</td></tr>
-  <tr><td>&nbsp; FMT        </td><td>&nbsp; &nbsp; File format, here BIA</td></tr>
-</table>
-</p>
-<p>
-Note that '${V3PROD}' produces the part 'YYYYDDDHHMM_LEN_SMP_CNT' of the filename according the 'Upload Corrections' setup.
-</p>
-A result for examle is:
-<pre>
+  With
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; AAA </td>
+      <td>&nbsp; &nbsp; Analysis Center abbrevaition, here BKG</td>
+    </tr>
+    <tr>
+      <td>&nbsp; V </td>
+      <td>&nbsp; &nbsp; Version / Solution identifier (0-9), here 0</td>
+    </tr>
+    <tr>
+      <td>&nbsp; PPP </td>
+      <td>&nbsp; &nbsp; Project/Campaign identification, here Multi-GNSS product (MGX)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; TTT </td>
+      <td>&nbsp; &nbsp; Solution Type, here real-time streamed product (RTS)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; YYYYDOYHHMM</td>
+      <td>&nbsp; &nbsp; String representing beginning time of nominal data interval</td>
+    </tr>
+    <tr>
+      <td>&nbsp; LEN </td>
+      <td>&nbsp; &nbsp; Intended product period of the file </td>
+    </tr>
+    <tr>
+      <td>&nbsp; SMP </td>
+      <td>&nbsp; &nbsp; Data sampling rate</td>
+    </tr>
+    <tr>
+      <td>&nbsp; CNT </td>
+      <td>&nbsp; &nbsp; Content type, here Observable-specific signal biases, code and phase (OSB)</td>
+    </tr>
+    <tr>
+      <td>&nbsp; FMT </td>
+      <td>&nbsp; &nbsp; File format, here BIA</td>
+    </tr>
+  </table>
+  </p>
+  <p>
+    Note that '${V3PROD}' produces the part 'YYYYDDDHHMM_LEN_SMP_CNT' of the filename according the 'Upload Corrections'
+    setup.
+  </p>
+  A result for examle is:
+  <pre>
   BKG0MGXRTS_20223330000_01D_05S_OSB.BIA
 </pre>
-<p>
-Default is an empty option field, meaning that you do not want BNC to save the uploaded stream content in daily Clock RINEX files.
-</p>
-
-<p><h4 id="pidsidiod">2.15.9 PID, SID, IOD - optional</h4></p>
-<p>
-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.
-<ul>
-  <li>A 'SSR Provider ID' is issued by RTCM SC-104 on request to identify a SSR service
-      (see e.g.<a href="https://software.rtcm-ntrip.org/wiki/SSRProvider" target="_blank">https://software.rtcm-ntrip.org/wiki/SSRProvider</a>)
-      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.</li>
-  <li>A provider may generate several Broadcast Ephemeris correction streams with different contents. The 'SSR Solution ID' indicates different
+  <p>
+    Default is an empty option field, meaning that you do not want BNC to save the uploaded stream content in daily
+    Clock RINEX files.
+  </p>
+
+  <p>
+  <h4 id="pidsidiod">2.15.9 PID, SID, IOD - optional</h4>
+  </p>
+  <p>
+    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.
+  <ul>
+    <li>A 'SSR Provider ID' is issued by RTCM SC-104 on request to identify a SSR service
+      (see e.g.<a href="https://software.rtcm-ntrip.org/wiki/SSRProvider"
+        target="_blank">https://software.rtcm-ntrip.org/wiki/SSRProvider</a>)
+      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.</li>
+    <li>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.</li>
-  <li>A change of the 'IOD SSR' is used to indicate a change in the SSR generating configuration which may be relevant for the rover.
+    <li>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.</li>
-</ul>
-</p>
-
-<p><h4 id="upinter">2.15.10 Interval - mandatory if 'Upload Table' entries specified</h4></p>
-<p>
-Select the length of SP3 Orbit files, Clock RINEX files and SINAX Bias files. The default value is 1 day.
-</p>
-
-<p><h4 id="upclksmpl">2.15.11 Sampling</h4></p>
-<p>
-BNC requires an orbit corrections sampling interval for the stream to be uploaded and sampling intervals for SP3, Clock RINEX, and SINEX Bias files.
-The outgoing stream's clock correction sampling interval follows that of incoming corrections and is therefore nothing to be specified here.</p>
-
-<p><h4 id="upclkorb">2.15.11.1 Orbits (Orb) - mandatory if 'Upload Table' entries specified</h4></p>
-<p>
-Select the stream's orbit correction sampling interval in seconds. A value of 60 sec may be appropriate.
-</p>
-<p>
-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; for example message type 1060 for GPS.
-</p>
-<p>
-Configuration examples:
-</p>
-Let us suppose a real-time network engine supporting BNC every <b>5 sec</b> with GPS Broadcast Corrections for orbits, clocks and code biases
-in 'RTNET' stream format.
-<ul>
-  <li>With 'Sampling Orb' set to '0'  BNC will produce</li>
+  </ul>
+  </p>
+
+  <p>
+  <h4 id="upinter">2.15.10 Interval - mandatory if 'Upload Table' entries specified</h4>
+  </p>
+  <p>
+    Select the length of SP3 Orbit files, Clock RINEX files and SINAX Bias files. The default value is 1 day.
+  </p>
+
+  <p>
+  <h4 id="upclksmpl">2.15.11 Sampling</h4>
+  </p>
+  <p>
+    BNC requires an orbit corrections sampling interval for the stream to be uploaded and sampling intervals for SP3,
+    Clock RINEX, and SINEX Bias files.
+    The outgoing stream's clock correction sampling interval follows that of incoming corrections and is therefore
+    nothing to be specified here.</p>
+
+  <p>
+  <h4 id="upclkorb">2.15.11.1 Orbits (Orb) - mandatory if 'Upload Table' entries specified</h4>
+  </p>
+  <p>
+    Select the stream's orbit correction sampling interval in seconds. A value of 60 sec may be appropriate.
+  </p>
+  <p>
+    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; for
+    example message type 1060 for GPS.
+  </p>
+  <p>
+    Configuration examples:
+  </p>
+  Let us suppose a real-time network engine supporting BNC every <b>5 sec</b> with GPS Broadcast Corrections for orbits,
+  clocks and code biases
+  in 'RTNET' stream format.
   <ul>
-    <li>Every 5 sec a 1059 message for GPS code biases,</li>
-    <li>Every 5 sec a 1060 message for combined orbit and clock corrections to GPS Broadcast Ephemeris.</li>
+    <li>With 'Sampling Orb' set to '0' BNC will produce</li>
+    <ul>
+      <li>Every 5 sec a 1059 message for GPS code biases,</li>
+      <li>Every 5 sec a 1060 message for combined orbit and clock corrections to GPS Broadcast Ephemeris.</li>
+    </ul>
+    <br>
+    <li>With 'Sampling Orb' set to '5' BNC will produce</li>
+    <ul>
+      <li>Every 5 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,</li>
+      <li>Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,</li>
+      <li>Every 5 sec a 1059 message for GPS code biases.</li>
+    </ul>
+    <br>
+    <li>With 'Sampling Orb' set to '10' BNC will produce</li>
+    <ul>
+      <li>Every 10 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,</li>
+      <li>Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,</li>
+      <li>Every 10 sec a 1059 message for GPS code biases.</li>
+    </ul>
   </ul>
-  <br>
-  <li>With 'Sampling Orb' set to '5' BNC will produce</li>
+  </p>
+  <p>
+    Note that only when specifying a value of zero '0' (default) for 'Sampling Orb', BNC produces <b>combined</b>
+    orbit and clock correction messages.
+  </p>
+
+  <p>
+  <h4 id="upclksp3">2.15.11.2 SP3 - mandatory if 'SP3 File' is specified</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="upclkrnx">2.15.11.3 RINEX (RNX) - mandatory if 'RNX File' is specified</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="upbiassnx">2.15.11.4 SINEX (BSX) - mandatory if 'BSX File' is specified</h4>
+  </p>
+  <p>
+    Select the SINEX Bias 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 SINEX Bias files.
+  </p>
+
+  <p>
+  <h4 id="upcustom">2.15.11 Custom Trafo - optional if 'Upload Table' entries specified</h4>
+  </p>
+  <p>
+    Hit 'Custom Trafo' to specify your own 14 parameter Helmert Transformation instead of selecting a predefined
+    transformation
+    through 'System' button.
+    .</p>
+
+  <p>
+  <h4 id="upantex">2.15.12 ANTEX File - mandatory if 'SP3 File' is specified</h4>
+  </p>
+  <p>
+    IGS provides a file containing absolute phase center offsets and 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.
+  </p>
+  <p>
+    The following screenshot shows the encoding and uploading of several Broadcast Ephemeris correction streams combined
+    from different AC streams.
+    Combined streams using different SSR formats are uploaded to different Ntrip Broadcasters and referred to different
+    reference systems.
+    Different SSR Provider IDs, SSR Solution IDs and Issue of Data IDs are specified. Required Broadcast Ephemeris are
+    received via stream 'BCEP00BKG0'.
+  </p>
+  <p><img src="IMG/Figure31.png" width=1000 /></p>
+  <p>Figure 31: BNC uploading a combined Broadcast Correction stream</p>
+  <p></p>
+
+  <p>
+  <h4 id="upeph">2.16 Upload Ephemeris</h4>
+  </p>
+  <p>
+    BNC can generate streams carrying only Broadcast Ephemeris in RTCM Version 3 format and upload them to an Ntrip
+    Broadcaster. The satellite system(s)
+    that shall be part of the uploaded stream can be specified using the 'System' parameter. This can be done:
   <ul>
-    <li>Every 5 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,</li>
-    <li>Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,</li>
-    <li>Every 5 sec a 1059 message for GPS code biases.</li>
+    <li>for an individual satellite system, specifying e.g. 'G' for GPS or 'E' for Galileo, etc. or </li>
+    <li>for a seclection of satellite systems, specifying e.g. 'GRE' for GPS and GLONASS and Galileo or</li>
+    <li>for all satellite systems, specifying 'ALL'. </li>
   </ul>
-  <br>
-  <li>With 'Sampling Orb' set to '10' BNC will produce</li>
-  <ul>
-    <li>Every 10 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,</li>
-    <li>Every  5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,</li>
-    <li>Every 10 sec a 1059 message for GPS code biases.</li>
-  </ul>
-</ul>
-</p>
-<p>
-Note that only when specifying a value of zero '0' (default) for 'Sampling Orb', BNC produces <b>combined</b>
-orbit and clock correction messages.
-</p>
-
-<p><h4 id="upclksp3">2.15.11.2 SP3 - mandatory if 'SP3 File' is specified</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="upclkrnx">2.15.11.3 RINEX (RNX) - mandatory if 'RNX File' is specified</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="upbiassnx">2.15.11.4 SINEX (BSX) - mandatory if 'BSX File' is specified</h4></p>
-<p>
-Select the SINEX Bias 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 SINEX Bias files.
-</p>
-
-<p><h4 id="upcustom">2.15.11 Custom Trafo - optional if 'Upload Table' entries specified</h4></p>
-<p>
-Hit 'Custom Trafo' to specify your own 14 parameter Helmert Transformation instead of selecting a predefined transformation
-through 'System' button.
-.</p>
-
-<p><h4 id="upantex">2.15.12 ANTEX File - mandatory if 'SP3 File' is specified</h4></p>
-<p>
-IGS provides a file containing absolute phase center offsets and 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.
-</p>
-<p>
-The following screenshot shows the encoding and uploading of several Broadcast Ephemeris correction streams combined from different AC streams.
-Combined streams using different SSR formats are uploaded to different Ntrip Broadcasters and referred to different reference systems.
-Different SSR Provider IDs, SSR Solution IDs and Issue of Data IDs are specified. Required Broadcast Ephemeris are received via stream 'BCEP00BKG0'.
-</p>
-<p><img src="IMG/Figure31.png"width=1000/></p>
-<p>Figure 31: BNC uploading a combined Broadcast Correction stream</p>
-<p></p>
-
-<p><h4 id="upeph">2.16 Upload Ephemeris</h4></p>
-<p>
-BNC can generate streams carrying only Broadcast Ephemeris in RTCM Version 3 format and upload them to an Ntrip Broadcaster. The satellite system(s)
-that shall be part of the uploaded stream can be specified using the 'System' parameter. This can be done:
-<ul>
-<li>for an individual satellite system, specifying e.g. 'G' for GPS or 'E' for Galileo, etc. or </li>
-<li>for a seclection of satellite systems, specifying e.g. 'GRE' for GPS and GLONASS and Galileo or</li>
-<li>for all satellite systems, specifying 'ALL'. </li>
-</ul>
-</p>
-<p>
-Note that Broadcast Ephemeris received in real-time have a system specific period of validity in BNC,
-which is defined in accordance with the update rates and validity intervals of the navigation messages.
-For this, the time difference dt of Time of Clock (TOC) with respect the current time is determined:
-</p>
-<pre>
+  </p>
+  <p>
+    Note that Broadcast Ephemeris received in real-time have a system specific period of validity in BNC,
+    which is defined in accordance with the update rates and validity intervals of the navigation messages.
+    For this, the time difference dt of Time of Clock (TOC) with respect the current time is determined:
+  </p>
+  <pre>
    dt = currentTime - TOC [sec]
 </pre>
-<p>
-Hence,
-<ul>
-<li>GPS ephemeris will be interpreted as outdated and ignored when dt > 14400.0 or dt < -7200.0.</li>
-<li>GLONASS ephemeris will be interpreted as outdated and ignored when dt >  3900.0 or dt < -2100.0.</li>
-<li>Galileo ephemeris will be interpreted as outdated and ignored when dt > 14400.0 or dt < 0.0.</li>
-<li>BDS ephemeris will be interpreted as outdated and ignored when dt > 3900.0 or dt < 0.0.</li>
-<li>SBAS ephemeris will be interpreted as outdated and ignored when dt > 600.0 or dt < -600.0.</li>
-<li>QZSS ephemeris will be interpreted as outdated and ignored when dt > 7200.0 or dt < -3600.0.</li>
-<li>NavIC ephemeris will be interpreted as outdated and ignored when fabs(dt > 86400.0).</li>
-</ul>
-A note 'OUTDATED EPHEMERIS' will be given in the logfile and the data will be disregarded when necessary.
-</p>
-<p>
-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.
-Unhealthy Broadcast Ephemeris will not be excluded. A note 'UNHEALTHY EPHEMERIS' will be added in the logfile.
-</p>
-<p><h4 id="brdcserver">2.16.1 Host &amp; Port - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-Enter the Ntrip Broadcaster's IP 'Port' number for stream upload. 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).
-</p>
-
-<p><h4 id="brdcmount">2.16.2 Mountpoint, Ntrip Version, User, Password - mandatory if 'Host' is set</h4></p>
-<p>
-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 9-character ID (capital letters)
-plus an integer number.
-</p>
-<p>
-For stream upload the Ntrip Version can be chosen. An Ntrip version 1 upload is protected through an upload 'Password' only.
-For an Ntrip Version 2 upload an upload 'User' is required in addition. Enter the user name and the password you received
-from the Ntrip Broadcaster operator along with the mountpoint.
-</p>
-<p><h4 id="brdcsys">2.16.3 Satellite System - mandatory if 'Host' is set</h4></p>
-Specify the satellite system(s) that shall be part of the uploaded stream (e.g. 'G' for GPS or 'GRE' for GPS+GLONASS+Galileo, or 'ALL').
-</p>
-<p><h4 id="brdcsmpl">2.16.4 Sampling - mandatory if 'Host' is set</h4></p>
-Select the Broadcast Ephemeris repetition interval in seconds. Default is '5', meaning that a complete set of Broadcast Ephemeris is uploaded
-every 5 seconds.
-</p>
-<p><img src="IMG/Figure32.png"width=1000/></p>
-<p>Figure 32: BNC producing Broadcast Ephemeris streams from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster</p>
-
-<p><h4 id="upraw">2.17 Upload Raw Data - NtripServer Functionality</h4></p>
-<p>
-BNC can upload Raw Data streams in any format like a NtripServer. To fill the 'Upload Raw Data' table, hit the 'Add Row' button.
-</p>
-<p><h4 id="rawsourcemount">2.17.1 Source Mountpoint</h4></p>
-<p>
-Within the 'Source Mountpoint' field please specify the Source of data from the 'Streams' section below, which shall be forwarded without decoding.
-If the decoder string is not an accepted one ('RTCM_2.x', 'RTCM_3.x' and 'RTNET'), please change the decoder string to
-<ul>
-<li> 'ZERO' (forward the raw data) or </li>
-<li> 'ZERO2FILE' (forward and store the raw data)</li>
-</ul> in addition.
-</p>
-<p><h4 id="rawserver">2.17.2 Host &amp; Port - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-Enter the Ntrip Broadcaster's IP 'Port' number for stream upload. 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).
-</p>
-
-<p><h4 id="rawmount">2.17.3 Mountpoint, Ntrip Version, User, Password - mandatory if 'Host' is set</h4></p>
-<p>
-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 9-character ID (capital letters)
-plus an integer number.
-</p>
-<p>
-For stream upload the Ntrip Version can be chosen. An Ntrip version 1 upload is protected through an upload 'Password' only.
-For an Ntrip Version 2 upload an upload 'User' is required in addition. Enter the user name and the password you received
-from the Ntrip Broadcaster operator along with the mountpoint.
-</p>
-
-<p><h4 id="streams">2.18 Streams Canvas</h4></p>
-<p>
-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.
-</p>
-<p>
-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:
-</p>
-<p>
-<table>
-  <tr><td>&nbsp; 'resource loader'&nbsp; &nbsp; </td><td>Ntrip Broadcaster URL and port, or TCP/IP host and port, or UDP port, or Serial input port specification.</td></tr>
-  <tr><td>&nbsp; 'mountpoint'     &nbsp; &nbsp; </td><td>Mountpoint introduced by Ntrip Broadcaster, or Mountpoint introduced by BNC's user.</td></tr>
-  <tr><td>&nbsp; 'decoder'        &nbsp; &nbsp; </td><td>Name of decoder used to handle the incoming stream content according to its format; editable.</td></tr>
-  <tr><td>&nbsp; 'lat'            &nbsp; &nbsp; </td><td>Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.</td></tr>
-  <tr><td>&nbsp; 'long'           &nbsp; &nbsp; </td><td>Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.</td></tr>
-  <tr><td>&nbsp; 'nmea'           &nbsp; &nbsp; </td><td>Indicates whether or not streaming needs to be initiated by BNC through sending
-                                                         NMEA-GGA message carrying position coordinates in 'lat' and 'long'.</td></tr>
-  <tr><td>&nbsp; 'ntrip'          &nbsp; &nbsp; </td><td>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.</td></tr>
-  <tr><td>&nbsp; 'bytes'          &nbsp; &nbsp; </td><td>Number of bytes received.
-</table>
-</p>
-<p><h4 id="streamedit">2.18.1 Edit Streams</h4></p>
-<ul>
-  <li>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'.</li>
-  <li>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 'ZERO2FILE'. 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 WTZZ00DEU0 to 'ZERO2FILE' and
+  <p>
+    Hence,
+  <ul>
+    <li>GPS ephemeris will be interpreted as outdated and ignored when dt > 14400.0 or dt < -7200.0.</li>
+    <li>GLONASS ephemeris will be interpreted as outdated and ignored when dt > 3900.0 or dt < -2100.0.</li>
+    <li>Galileo ephemeris will be interpreted as outdated and ignored when dt > 14400.0 or dt < 0.0.</li>
+    <li>BDS ephemeris will be interpreted as outdated and ignored when dt > 3900.0 or dt < 0.0.</li>
+    <li>SBAS ephemeris will be interpreted as outdated and ignored when dt > 600.0 or dt < -600.0.</li>
+    <li>QZSS ephemeris will be interpreted as outdated and ignored when dt > 7200.0 or dt < -3600.0.</li>
+    <li>NavIC ephemeris will be interpreted as outdated and ignored when fabs(dt > 86400.0).</li>
+  </ul>
+  A note 'OUTDATED EPHEMERIS' will be given in the logfile and the data will be disregarded when necessary.
+  </p>
+  <p>
+    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.
+    Unhealthy Broadcast Ephemeris will not be excluded. A note 'UNHEALTHY EPHEMERIS' will be added in the logfile.
+  </p>
+  <p>
+  <h4 id="brdcserver">2.16.1 Host &amp; Port - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Enter the Ntrip Broadcaster's IP 'Port' number for stream upload. 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).
+  </p>
+
+  <p>
+  <h4 id="brdcmount">2.16.2 Mountpoint, Ntrip Version, User, Password - mandatory if 'Host' is set</h4>
+  </p>
+  <p>
+    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
+    9-character ID (capital letters)
+    plus an integer number.
+  </p>
+  <p>
+    For stream upload the Ntrip Version can be chosen. An Ntrip version 1 upload is protected through an upload
+    'Password' only.
+    For an Ntrip Version 2 upload an upload 'User' is required in addition. Enter the user name and the password you
+    received
+    from the Ntrip Broadcaster operator along with the mountpoint.
+  </p>
+  <p>
+  <h4 id="brdcsys">2.16.3 Satellite System - mandatory if 'Host' is set</h4>
+  </p>
+  Specify the satellite system(s) that shall be part of the uploaded stream (e.g. 'G' for GPS or 'GRE' for
+  GPS+GLONASS+Galileo, or 'ALL').
+  </p>
+  <p>
+  <h4 id="brdcsmpl">2.16.4 Sampling - mandatory if 'Host' is set</h4>
+  </p>
+  Select the Broadcast Ephemeris repetition interval in seconds. Default is '5', meaning that a complete set of
+  Broadcast Ephemeris is uploaded
+  every 5 seconds.
+  </p>
+  <p><img src="IMG/Figure32.png" width=1000 /></p>
+  <p>Figure 32: BNC producing Broadcast Ephemeris streams from globally distributed RTCM streams; upload in RTCM format
+    to an Ntrip Broadcaster</p>
+
+  <p>
+  <h4 id="upraw">2.17 Upload Raw Data - NtripServer Functionality</h4>
+  </p>
+  <p>
+    BNC can upload Raw Data streams in any format like a NtripServer. To fill the 'Upload Raw Data' table, hit the 'Add
+    Row' button.
+  </p>
+  <p>
+  <h4 id="rawsourcemount">2.17.1 Source Mountpoint</h4>
+  </p>
+  <p>
+    Within the 'Source Mountpoint' field please specify the Source of data from the 'Streams' section below, which shall
+    be forwarded without decoding.
+    If the decoder string is not an accepted one ('RTCM_2.x', 'RTCM_3.x' and 'RTNET'), please change the decoder string
+    to
+  <ul>
+    <li> 'ZERO' (forward the raw data) or </li>
+    <li> 'ZERO2FILE' (forward and store the raw data)</li>
+  </ul> in addition.
+  </p>
+  <p>
+  <h4 id="rawserver">2.17.2 Host &amp; Port - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Enter the Ntrip Broadcaster's IP 'Port' number for stream upload. 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).
+  </p>
+
+  <p>
+  <h4 id="rawmount">2.17.3 Mountpoint, Ntrip Version, User, Password - mandatory if 'Host' is set</h4>
+  </p>
+  <p>
+    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
+    9-character ID (capital letters)
+    plus an integer number.
+  </p>
+  <p>
+    For stream upload the Ntrip Version can be chosen. An Ntrip version 1 upload is protected through an upload
+    'Password' only.
+    For an Ntrip Version 2 upload an upload 'User' is required in addition. Enter the user name and the password you
+    received
+    from the Ntrip Broadcaster operator along with the mountpoint.
+  </p>
+
+  <p>
+  <h4 id="streams">2.18 Streams Canvas</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    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:
+  </p>
+  <p>
+  <table>
+    <tr>
+      <td>&nbsp; 'resource loader'&nbsp; &nbsp; </td>
+      <td>Ntrip Broadcaster URL and port, or TCP/IP host and port, or UDP port, or Serial input port specification.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; 'mountpoint' &nbsp; &nbsp; </td>
+      <td>Mountpoint introduced by Ntrip Broadcaster, or Mountpoint introduced by BNC's user.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; 'decoder' &nbsp; &nbsp; </td>
+      <td>Name of decoder used to handle the incoming stream content according to its format; editable.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; 'lat' &nbsp; &nbsp; </td>
+      <td>Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; 'long' &nbsp; &nbsp; </td>
+      <td>Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; 'nmea' &nbsp; &nbsp; </td>
+      <td>Indicates whether or not streaming needs to be initiated by BNC through sending
+        NMEA-GGA message carrying position coordinates in 'lat' and 'long'.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; 'ntrip' &nbsp; &nbsp; </td>
+      <td>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.</td>
+    </tr>
+    <tr>
+      <td>&nbsp; 'bytes' &nbsp; &nbsp; </td>
+      <td>Number of bytes received.
+  </table>
+  </p>
+  <p>
+  <h4 id="streamedit">2.18.1 Edit Streams</h4>
+  </p>
+  <ul>
+    <li>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'.
+    </li>
+    <li>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 'ZERO2FILE'. 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 WTZZ00DEU0
+      to 'ZERO2FILE' and
       running BNC on December 01, 2022 would save raw data in a file named WTZZ00DEU0_221201.</li>
- <li> BNC allows as well to forward streams related to the specified 'Mountpoint' on top of the 'Miscellaneous Panel'
-      through a TCP/IP port of your local host. In this case, the stream content remains untouched; BNC does not decode or reformat the data for this output.
-      If the decoder string is not an accepted one, please change the decoder string to 'ZERO' (forward the raw data only) or 'ZERO2FILE' (forward and store the raw data) in addition.</li>
-  <li>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
+    <li> BNC allows as well to forward streams related to the specified 'Mountpoint' on top of the 'Miscellaneous Panel'
+      through a TCP/IP port of your local host. In this case, the stream content remains untouched; BNC does not decode
+      or reformat the data for this output.
+      If the decoder string is not an accepted one, please change the decoder string to 'ZERO' (forward the raw data
+      only) or 'ZERO2FILE' (forward and store the raw data) in addition.</li>
+    <li>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.</li>
-</ul>
-
-<p><h4 id="streamdelete">2.18.2 Delete Stream</h4></p>
-<p>
-To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Stream' button.
-You can also remove multiple streams simultaneously by highlighting them using +Shift or +Ctrl.
-</p>
-
-<p><h4 id="streamconf">2.18.3 Reconfigure Stream Selection On-the-fly</h4></p>
-<p>
-The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process.
-</p>
-<p>
-<b>Window mode:</b> Hit 'Reread &amp; Save Configuration' while BNC is in window mode and already processing data
-to let changes of your stream selection immediately become effective.
-<p>
-<b>No window mode:</b> When operating BNC online in 'no window' mode (command line option -nw),
-you force BNC to reread its 'mountPoints' configuration option from disk at pre-defined intervals.
-Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option
-every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file
-become effective without terminating uninvolved threads. See section 'Configuration Examples' for
-configuration file examples and section 'Reread Configuration' for a list of other on-the-fly changeable options.
-</p>
-
-<p><h4 id="logs">2.19 Logging Canvas</h4></p>
-<p>
-The 'Logging Canvas' above the bottom menu bar on the main window labeled 'Log', 'Throughput', 'Latency', and 'PPP Plot'
-provides control of BNC's activities. Tabs are available for continuously showing logfile content,
-for a plot controlling the bandwidth consumption, a plot showing stream latencies, and for time series plots of PPP results.
-</p>
-
-<p><h4 id="logfile">2.19.1 Log</h4></p>
-<p>
-Records of BNC's activities are shown in the 'Log' tab. They can be saved into a file when a valid path is specified in the 'Logfile (full path)' field.
-</p>
-
-<p><h4 id="throughput">2.19.2 Throughput</h4></p>
-<p>
-The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilobits per second (kbps).
-The following figure shows an example for the bandwidth consumption of incoming streams.
-</p>
-<p><img src="IMG/Figure33.png"width=1000/></p>
-<p>Figure 33: Bandwidth consumption of RTCM streams received by BNC</p>
-<p><h4 id="latency">2.19.3 Latency</h4></p>
-<p>
-The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds.
-Streams not carrying observations (e.g. those providing only Broadcast Ephemeris messages) or having an outage
-are not considered here and shown in red color. Note that the calculation of correct latencies requires the
-clock of the host computer to be properly synchronized. The next figure shows an example for the latency
-of incoming streams.
-</p>
-<p><img src="IMG/Figure34.png"width=1000/></p>
-<p>Figure 34: Latency of RTCM streams received by BNC</p>
-
-<p><h4 id="ppptab">2.19.4 PPP Plot</h4></p>
-<p>
-Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when
-a 'Mountpoint' option is defined under PPP (4). Values are referred to a priori reference coordinates. The time as given in format [hh:mm]
-refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more until
-the first PPP solutions becomes available. The following figure shows the screenshot of a PPP time series plot of North, East and Up
-coordinate displacements.
-</p>
-<p><img src="IMG/Figure35.png"width=1000/></p>
-<p>Figure 35: Example for time series plot of displacements produced by BNC</p>
-
-<p><h4 id="bottom">2.20 Bottom Menu Bar</h4></p>
-<p>
-The bottom menu bar allows to add or delete streams to or from BNC's configuration and to start or stop it.
-It also provides access to BNC's online help function. The 'Add Stream' button opens a window that allows users
-to select one of several input communication links, see figure below.
-</p>
-<p><img src="IMG/Figure36.png"width=400/></p>
-<p>Figure 36: Steam input communication links accepted by BNC</p>
-
-<p><h4 id="streamadd">2.20.1 Add Stream</h4></p>
-<p>
-Button 'Add Stream' allows you to pull streams either from an Ntrip Broadcaster or from a TCP/IP port, UPD port, or serial port.
-</p>
-
-<p><h4 id="streamcaster">2.20.1.1 Add Stream - Coming from Caster</h4></p>
-<p>
-Button 'Add Stream' &gt; 'Coming from Caster' opens a window that allows users to select data streams from an Ntrip Broadcaster according
-to their mountpoints and show a distribution map of offered streams.
-</p>
-
-<p><h4 id="streamhost">2.20.1.1.1 Caster Host and Port - mandatory</h4></p>
-<p>
-Enter the Ntrip Broadcaster host IP and port number. Note that EUREF and IGS operate Ntrip Broadcasters
-<a href="https://euref-ip.net/home" target="_blank">https://euref-ip.net/home</a>,
-<a href="https://igs-ip.net/home" target="_blank">https://igs-ip.net/home</a> and
-<a href="https://products.igs-ip.net/home" target="_blank">https://products.igs-ip.net/home</a>.
-</p>
-
-<p><h4 id="streamtable">2.20.1.1.2 Casters Table - optional</h4></p>
-<p>
-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
-<a href="https://rtcm-ntrip.org/home " target="_blank">https://rtcm-ntrip.org/home </a>.
-A window opens which allows selecting a broadcaster for stream retrieval, see figure below.
-</p>
-<p><img src="IMG/Figure37.png"width=1000/></p>
-<p>Figure 37: BNC's 'Select Broadcaster' table</p>
-
-<p><h4 id="streamuser">2.20.1.1.3 User and Password - mandatory for protected streams</h4></p>
-<p>
-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 <a href="https://register.rtcm-ntrip.org" target="_blank">https://register.rtcm-ntrip.org</a>
-for access to protected streams from EUREF and IGS.
-</p>
-
-<p><h4 id="gettable">2.20.1.1.4 Get Table</h4></p>
-<p>
-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 Ephemerides 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 navigation messages are required:
-<table>
-<tr><td>Navigation 		</td><td>Description							</td><td>Constellation  		</td><td>RTCM </td></tr>
-<tr><td>Message Type	</td><td>										</td><td>and Signal 			</td><td>Message Type</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>LNAV</td><td>			GPS Legacy navigation message			</td><td>GPS  L1 C/A           	</td><td>1019</td></tr>
-<tr><td>	</td><td>			QZSS Legacy navigation message 			</td><td>QZSS L1 C/A or L1 C/B 	</td><td>1044</td></tr>
-<tr><td>	</td><td>			NavIC Legacy navigation message 		</td><td>NavIC L5/S SPS        	</td><td>1041</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>FDMA</td><td>			GLONASS Legacy FDMA navigation message	</td><td>GLO L1 C/A			 	</td><td>1020</td></tr>
-<tr><td>	</td><td>			from M-satellites						</td><td>			          	</td><td>	 </td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>INAV</td><td>			Galileo Integrity 	navigation message 	</td><td>GAL E1, E5b        	</td><td>1046</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>D1	</td><td>			BeiDou-2/3 MEO/IGSO navigation message 	</td><td>BDS B1I, B2I, B3I  	</td><td>1042</td></tr>
-<tr><td>D2	</td><td>			BeiDou-2/3 GEO      navigation message 	</td><td>BDS B1I, B2I, B3I 		</td><td>1042</td></tr>
-<tr><td>	</td><td>													</td><td>			          	</td><td>	 </td></tr>
-<tr><td>SBAS</td><td>			SBAS      navigation message 			</td><td>SBAS L1            	</td><td>1043</td></tr>
-</table>
-Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table.
-</p>
-<p>
-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).
-</p>
-<p>
-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.
-</p>
-<p><img src="IMG/Figure38.png"width=1000/></p>
-<p>Figure 38: Broadcaster source-table shown by BNC</p>
-
-<p><h4 id="ntripv">2.20.1.1.5 Ntrip Version - mandatory</h4></p>
-<p>
-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:
-</p>
-<p>
-<table>
-  <tr><td><b>Option &nbsp;  &nbsp; </b></td><td><b>Meaning</b></td></tr>
-  <tr><td>&nbsp; &nbsp; 1  </td><td>Ntrip Version 1, TCP/IP</td></tr>
-  <tr><td>&nbsp; &nbsp; 2  </td><td>Ntrip Version 2 in TCP/IP mode</td></tr>
-  <tr><td>&nbsp; &nbsp; 2s </td><td>Ntrip Version 2 in TCP/IP mode via SSL</td></tr>
-  <tr><td>&nbsp; &nbsp; R  </td><td>Ntrip Version 2 in RTSP/RTP mode</td></tr>
-  <tr><td>&nbsp; &nbsp; U  </td><td>Ntrip Version 2 in UDP mode</td></tr>
-</table>
-</p>
-<p>
-Try using option '2' if your streams are otherwise blocked by a proxy server operated in front of BNC.
-</p>
-<p>
-When using Ntrip Version 2 via SSL (option '2s') you need to specify the appropriate 'Caster port' for that.
-It is usually port number 443. Clarify 'SSL' options offered in panel 'Network'.
-</p>
-<p>
-Option 'R' or 'U' may be selected if latency is more important than completeness for your application.
-Note that the latency reduction is likely to be in the order of 0.5 sec or less.
-Note further that options 'R' (RTSP/RTP mode) and 'U' (UDP mode) are not accepted by proxy servers and
-a mobile Internet Service Provider may not support it.
-</p>
-<p><h4 id="castermap">2.20.1.1.6 Map - optional</h4></p>
-<p>
-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.
-</p>
-<p><img src="IMG/Figure39.png"width=1000/></p>
-<p>Figure 39: Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table</p>
-
-<p><h4 id="streamip">2.20.1.2 Add Stream - Coming from TCP/IP Port</h4></p>
-<p>
-Button 'Add Stream' &gt; '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:
-<ul>
-  <li>Enter the IP address of the stream providing host.</li>
-  <li>Enter the IP port number of the stream providing host.</li>
-  <li>Specify a mountpoint. Recommended is a 9-character station ID. Example: FFMJ00DEU</li>
-  <li>Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', 'ZERO' and 'ZERO2FILE'.</li>
-  <li>Enter the approximate latitude of the stream providing rover in degrees. Example: 50.09.</li>
-  <li>Enter the approximate longitude of the stream providing rover in degrees. Example: 8.66.</li>
-</ul>
-</p>
-<p>
-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.
-<p>
-</p>
-Note that this option works only if no proxy server is involved in the communication link.
-</p>
-<p><h4 id="streamudp">2.20.1.3 Add Stream - Coming from UDP Port</h4></p>
-<p>
-Button 'Add Stream' &gt; '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:
-<ul>
-  <li>Enter the local port number where the UDP stream arrives.</li>
-  <li>Specify a mountpoint. Recommended is a 9-character station ID. Example: FFMJ00DEU</li>
-  <li>Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', 'ZERO' and 'ZERO2FILE'.</li>
-  <li>Enter the approximate latitude of the stream providing rover in degrees. Example: 50.09.</li>
-  <li>Enter the approximate longitude of the stream providing rover in degrees. Example: 8.66.</li>
-</ul>
-</p>
-<p>
-Streams directly received at a UDP port show up with a 'UN' for 'UDP, No Ntrip' in the 'Streams' canvas section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
-<p>
-
-<p><h4 id="streamser">2.20.1.4 Add Stream - Coming from Serial Port</h4></p>
-<p>
-Button 'Add Stream' &gt; 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the Ntrip transport protocol. For that you:
-<ul>
-  <li>Specify a mountpoint. Recommended is a 9-character station ID. Example: FFMJ00DEU</li>
-  <li>Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', 'ZERO' and 'ZERO2FILE'.</li>
-  <li>Enter the approximate latitude of the stream providing rover in degrees. Example: 50.09.</li>
-  <li>Enter the approximate longitude of the stream providing rover in degrees. Example: 8.66.</li>
-  <li>Enter the serial 'Port name' selected on your host for communication with the receiver. Valid port names are
+      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.</li>
+  </ul>
+
+  <p>
+  <h4 id="streamdelete">2.18.2 Delete Stream</h4>
+  </p>
+  <p>
+    To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete
+    Stream' button.
+    You can also remove multiple streams simultaneously by highlighting them using +Shift or +Ctrl.
+  </p>
+
+  <p>
+  <h4 id="streamconf">2.18.3 Reconfigure Stream Selection On-the-fly</h4>
+  </p>
+  <p>
+    The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process.
+  </p>
+  <p>
+    <b>Window mode:</b> Hit 'Reread &amp; Save Configuration' while BNC is in window mode and already processing data
+    to let changes of your stream selection immediately become effective.
+  <p>
+    <b>No window mode:</b> When operating BNC online in 'no window' mode (command line option -nw),
+    you force BNC to reread its 'mountPoints' configuration option from disk at pre-defined intervals.
+    Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option
+    every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file
+    become effective without terminating uninvolved threads. See section 'Configuration Examples' for
+    configuration file examples and section 'Reread Configuration' for a list of other on-the-fly changeable options.
+  </p>
+
+  <p>
+  <h4 id="logs">2.19 Logging Canvas</h4>
+  </p>
+  <p>
+    The 'Logging Canvas' above the bottom menu bar on the main window labeled 'Log', 'Throughput', 'Latency', and 'PPP
+    Plot'
+    provides control of BNC's activities. Tabs are available for continuously showing logfile content,
+    for a plot controlling the bandwidth consumption, a plot showing stream latencies, and for time series plots of PPP
+    results.
+  </p>
+
+  <p>
+  <h4 id="logfile">2.19.1 Log</h4>
+  </p>
+  <p>
+    Records of BNC's activities are shown in the 'Log' tab. They can be saved into a file when a valid path is specified
+    in the 'Logfile (full path)' field.
+  </p>
+
+  <p>
+  <h4 id="throughput">2.19.2 Throughput</h4>
+  </p>
+  <p>
+    The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilobits per
+    second (kbps).
+    The following figure shows an example for the bandwidth consumption of incoming streams.
+  </p>
+  <p><img src="IMG/Figure33.png" width=1000 /></p>
+  <p>Figure 33: Bandwidth consumption of RTCM streams received by BNC</p>
+  <p>
+  <h4 id="latency">2.19.3 Latency</h4>
+  </p>
+  <p>
+    The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds.
+    Streams not carrying observations (e.g. those providing only Broadcast Ephemeris messages) or having an outage
+    are not considered here and shown in red color. Note that the calculation of correct latencies requires the
+    clock of the host computer to be properly synchronized. The next figure shows an example for the latency
+    of incoming streams.
+  </p>
+  <p><img src="IMG/Figure34.png" width=1000 /></p>
+  <p>Figure 34: Latency of RTCM streams received by BNC</p>
+
+  <p>
+  <h4 id="ppptab">2.19.4 PPP Plot</h4>
+  </p>
+  <p>
+    Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in
+    the 'PPP Plot' tab when
+    a 'Mountpoint' option is defined under PPP (4). Values are referred to a priori reference coordinates. The time as
+    given in format [hh:mm]
+    refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30
+    seconds or more until
+    the first PPP solutions becomes available. The following figure shows the screenshot of a PPP time series plot of
+    North, East and Up
+    coordinate displacements.
+  </p>
+  <p><img src="IMG/Figure35.png" width=1000 /></p>
+  <p>Figure 35: Example for time series plot of displacements produced by BNC</p>
+
+  <p>
+  <h4 id="bottom">2.20 Bottom Menu Bar</h4>
+  </p>
+  <p>
+    The bottom menu bar allows to add or delete streams to or from BNC's configuration and to start or stop it.
+    It also provides access to BNC's online help function. The 'Add Stream' button opens a window that allows users
+    to select one of several input communication links, see figure below.
+  </p>
+  <p><img src="IMG/Figure36.png" width=400 /></p>
+  <p>Figure 36: Steam input communication links accepted by BNC</p>
+
+  <p>
+  <h4 id="streamadd">2.20.1 Add Stream</h4>
+  </p>
+  <p>
+    Button 'Add Stream' allows you to pull streams either from an Ntrip Broadcaster or from a TCP/IP port, UPD port, or
+    serial port.
+  </p>
+
+  <p>
+  <h4 id="streamcaster">2.20.1.1 Add Stream - Coming from Caster</h4>
+  </p>
+  <p>
+    Button 'Add Stream' &gt; 'Coming from Caster' opens a window that allows users to select data streams from an Ntrip
+    Broadcaster according
+    to their mountpoints and show a distribution map of offered streams.
+  </p>
+
+  <p>
+  <h4 id="streamhost">2.20.1.1.1 Caster Host and Port - mandatory</h4>
+  </p>
+  <p>
+    Enter the Ntrip Broadcaster host IP and port number. Note that EUREF and IGS operate Ntrip Broadcasters
+    <a href="https://euref-ip.net/home" target="_blank">https://euref-ip.net/home</a>,
+    <a href="https://igs-ip.net/home" target="_blank">https://igs-ip.net/home</a> and
+    <a href="https://products.igs-ip.net/home" target="_blank">https://products.igs-ip.net/home</a>.
+  </p>
+
+  <p>
+  <h4 id="streamtable">2.20.1.1.2 Casters Table - optional</h4>
+  </p>
+  <p>
+    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
+    <a href="https://rtcm-ntrip.org/home " target="_blank">https://rtcm-ntrip.org/home </a>.
+    A window opens which allows selecting a broadcaster for stream retrieval, see figure below.
+  </p>
+  <p><img src="IMG/Figure37.png" width=1000 /></p>
+  <p>Figure 37: BNC's 'Select Broadcaster' table</p>
+
+  <p>
+  <h4 id="streamuser">2.20.1.1.3 User and Password - mandatory for protected streams</h4>
+  </p>
+  <p>
+    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 <a href="https://register.rtcm-ntrip.org" target="_blank">https://register.rtcm-ntrip.org</a>
+    for access to protected streams from EUREF and IGS.
+  </p>
+
+  <p>
+  <h4 id="gettable">2.20.1.1.4 Get Table</h4>
+  </p>
+  <p>
+    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 Ephemerides 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 navigation messages are
+    required:
   <table>
-  <tr><td>&nbsp; &nbsp; Windows:       </td><td>COM1, COM2</td></tr>
-  <tr><td>&nbsp; &nbsp; Linux:         </td><td>/dev/ttyS0, /dev/ttyS1</td></tr>
-  <tr><td>&nbsp; &nbsp; FreeBSD:       </td><td>/dev/ttyd0, /dev/ttyd1</td></tr>
-  <tr><td>&nbsp; &nbsp; Digital Unix:  </td><td>/dev/tty01, /dev/tty02</td></tr>
-  <tr><td>&nbsp; &nbsp; HP-UX:         </td><td>/dev/tty1p0, /dev/tty2p0</td></tr>
-  <tr><td>&nbsp; &nbsp; SGI/IRIX;      </td><td>/dev/ttyf1, /dev/ttyf2</td></tr>
-  <tr><td>&nbsp; &nbsp; SunOS/Solaris: </td><td>/dev/ttya, /dev/ttyb</td></tr>
-</table>
-</li>
-  <li>Select a 'Baud rate' for the serial input. Note that using a high baud rate is recommended.</li>
-  <li>Select the number of 'Data bits' for the serial input. Note that often '8' data bits are used.</li>
-  <li>Select the 'Parity' for the serial input. Note that parity is often set to 'NONE'.</li>
-  <li>Select the number of 'Stop bits' for the serial input. Note that often '1' stop bit is used.</li>
-  <li>Select a 'Flow control' for the serial link. Select 'OFF' if you do not know better.</li>
-</ul>
-</p>
-<p>
-When selecting one of the serial communication options listed above, make sure that you pick those configured to the serially connected GNSS receiver.
-</p>
-<p>
-Streams received from a serially connected GNSS receiver show up with an 'S' (for <u>S</u>erial Port, no Ntrip) in the 'Streams' canvas
-section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
-<p>
-<p>
-The following figure shows a BNC example setup for pulling a stream via serial port on a Windows operating system.
-</p>
-<p><img src="IMG/Figure40.png"width=400/></p>
-<p>Figure 40: BNC configuration for pulling a stream via serial port</p>
-
-<p><h4 id="streamsdelete">2.20.2 Delete Stream</h4></p>
-<p>
-Button 'Delete Stream' allows you to delete streams previously selected for retrieval as listed under the 'Streams' canvas on BNC's main window.
-</p>
-
-<p><h4 id="streamsmap">2.20.3 Map</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="start">2.20.4 Start</h4></p>
-<p>
-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.
-</p>
-
-<p><h4 id="stop">2.20.5 Stop</h4></p>
-<p>
-Hit the 'Stop' button in order to stop BNC.
-</p>
-
-<p><h4 id="contexthelp">2.20.6 Help? = Shift+F1</h4></p>
-<p>
-BNC comes with a <i>What's This</i> 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.
-</p>
-<p><h4 id="cmd">2.21 Command Line Options</h4></p>
-<p>
-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.
-</p>
-<p>
-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'
-</p>
-<p>
-Example:<br><br>
-&nbsp; &nbsp; &nbsp; bnc --help (MS Windows: bnc.exe --help | more)
-</p>
-<p>
-provides a list of all available command line options.
-</p>
-<p><h4 id="cmdVersion">2.21.1 Version - optional</h4></p>
-<p>
-Command line option '--version' lets BNC print its version number.
-</p>
-<p>
-Example:<br><br>
-&nbsp; &nbsp; &nbsp; bnc --version (MS Windows: bnc.exe --version | more)
-</p>
-<p><h4 id="cmdDisplay">2.21.2 Display - optional</h4></p>
-<p>
-On systems which support graphics, command line option '--display' forces BNC to present the BNC window on the specified display.
-</p>
-<p>
-Example:<br><br>
-&nbsp; &nbsp; &nbsp; bnc.exe --display localhost:10.0
-</p>
-<p><h4 id="nw">2.21.3 No Window Mode - optional</h4></p>
-<p>
-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.
-</p>
-<p>
-Example:<br><br>
-&nbsp; &nbsp; &nbsp; bnc.exe --nw
-</p>
-<p>
-The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode
-and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no configuration options
-previously saved on disc are used:
-It is obvious that BNC requires graphics support when started in interactive
-mode. However, note that graphics support is also required when producing plots in
-batch mode (option -nw). Windows and Mac OS X systems always support graphics. For
-producing plots in batch mode on Linux systems you must make sure that at
-least a virtual X-Server such as 'Xvfb' is installed and the '-display' option
-is used. The following is an example shell script to execute BNC in batch mode
-for producing QC plots from RINEX files. It could be used via 'crontab':
-
-<pre><p style="font-family:Monospace">
+    <tr>
+      <td>Navigation </td>
+      <td>Description </td>
+      <td>Constellation </td>
+      <td>RTCM </td>
+    </tr>
+    <tr>
+      <td>Message Type </td>
+      <td> </td>
+      <td>and Signal </td>
+      <td>Message Type</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>LNAV</td>
+      <td> GPS Legacy navigation message </td>
+      <td>GPS L1 C/A </td>
+      <td>1019</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> QZSS Legacy navigation message </td>
+      <td>QZSS L1 C/A or L1 C/B </td>
+      <td>1044</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> NavIC Legacy navigation message </td>
+      <td>NavIC L5/S SPS </td>
+      <td>1041</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>FDMA</td>
+      <td> GLONASS Legacy FDMA navigation message </td>
+      <td>GLO L1 C/A </td>
+      <td>1020</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> from M-satellites </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>INAV</td>
+      <td> Galileo Integrity navigation message </td>
+      <td>GAL E1, E5b </td>
+      <td>1046</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>D1 </td>
+      <td> BeiDou-2/3 MEO/IGSO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td>D2 </td>
+      <td> BeiDou-2/3 GEO navigation message </td>
+      <td>BDS B1I, B2I, B3I </td>
+      <td>1042</td>
+    </tr>
+    <tr>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>SBAS</td>
+      <td> SBAS navigation message </td>
+      <td>SBAS L1 </td>
+      <td>1043</td>
+    </tr>
+  </table>
+  Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example
+  source-table.
+  </p>
+  <p>
+    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).
+  </p>
+  <p>
+    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.
+  </p>
+  <p><img src="IMG/Figure38.png" width=1000 /></p>
+  <p>Figure 38: Broadcaster source-table shown by BNC</p>
+
+  <p>
+  <h4 id="ntripv">2.20.1.1.5 Ntrip Version - mandatory</h4>
+  </p>
+  <p>
+    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:
+  </p>
+  <p>
+  <table>
+    <tr>
+      <td><b>Option &nbsp; &nbsp; </b></td>
+      <td><b>Meaning</b></td>
+    </tr>
+    <tr>
+      <td>&nbsp; &nbsp; 1 </td>
+      <td>Ntrip Version 1, TCP/IP</td>
+    </tr>
+    <tr>
+      <td>&nbsp; &nbsp; 2 </td>
+      <td>Ntrip Version 2 in TCP/IP mode</td>
+    </tr>
+    <tr>
+      <td>&nbsp; &nbsp; 2s </td>
+      <td>Ntrip Version 2 in TCP/IP mode via SSL</td>
+    </tr>
+    <tr>
+      <td>&nbsp; &nbsp; R </td>
+      <td>Ntrip Version 2 in RTSP/RTP mode</td>
+    </tr>
+    <tr>
+      <td>&nbsp; &nbsp; U </td>
+      <td>Ntrip Version 2 in UDP mode</td>
+    </tr>
+  </table>
+  </p>
+  <p>
+    Try using option '2' if your streams are otherwise blocked by a proxy server operated in front of BNC.
+  </p>
+  <p>
+    When using Ntrip Version 2 via SSL (option '2s') you need to specify the appropriate 'Caster port' for that.
+    It is usually port number 443. Clarify 'SSL' options offered in panel 'Network'.
+  </p>
+  <p>
+    Option 'R' or 'U' may be selected if latency is more important than completeness for your application.
+    Note that the latency reduction is likely to be in the order of 0.5 sec or less.
+    Note further that options 'R' (RTSP/RTP mode) and 'U' (UDP mode) are not accepted by proxy servers and
+    a mobile Internet Service Provider may not support it.
+  </p>
+  <p>
+  <h4 id="castermap">2.20.1.1.6 Map - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p><img src="IMG/Figure39.png" width=1000 /></p>
+  <p>Figure 39: Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table</p>
+
+  <p>
+  <h4 id="streamip">2.20.1.2 Add Stream - Coming from TCP/IP Port</h4>
+  </p>
+  <p>
+    Button 'Add Stream' &gt; '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:
+  <ul>
+    <li>Enter the IP address of the stream providing host.</li>
+    <li>Enter the IP port number of the stream providing host.</li>
+    <li>Specify a mountpoint. Recommended is a 9-character station ID. Example: FFMJ00DEU</li>
+    <li>Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', 'ZERO' and 'ZERO2FILE'.</li>
+    <li>Enter the approximate latitude of the stream providing rover in degrees. Example: 50.09.</li>
+    <li>Enter the approximate longitude of the stream providing rover in degrees. Example: 8.66.</li>
+  </ul>
+  </p>
+  <p>
+    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.
+  <p>
+  </p>
+  Note that this option works only if no proxy server is involved in the communication link.
+  </p>
+  <p>
+  <h4 id="streamudp">2.20.1.3 Add Stream - Coming from UDP Port</h4>
+  </p>
+  <p>
+    Button 'Add Stream' &gt; '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:
+  <ul>
+    <li>Enter the local port number where the UDP stream arrives.</li>
+    <li>Specify a mountpoint. Recommended is a 9-character station ID. Example: FFMJ00DEU</li>
+    <li>Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', 'ZERO' and 'ZERO2FILE'.</li>
+    <li>Enter the approximate latitude of the stream providing rover in degrees. Example: 50.09.</li>
+    <li>Enter the approximate longitude of the stream providing rover in degrees. Example: 8.66.</li>
+  </ul>
+  </p>
+  <p>
+    Streams directly received at a UDP port show up with a 'UN' for 'UDP, No Ntrip' in the 'Streams' canvas section on
+    BNC's main window. Latitude and longitude are to be entered just for informal reasons.
+  <p>
+
+  <p>
+  <h4 id="streamser">2.20.1.4 Add Stream - Coming from Serial Port</h4>
+  </p>
+  <p>
+    Button 'Add Stream' &gt; 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port
+    without using the Ntrip transport protocol. For that you:
+  <ul>
+    <li>Specify a mountpoint. Recommended is a 9-character station ID. Example: FFMJ00DEU</li>
+    <li>Specify the stream format. Available options are 'RTCM_2', 'RTCM_3', 'RTNET', 'ZERO' and 'ZERO2FILE'.</li>
+    <li>Enter the approximate latitude of the stream providing rover in degrees. Example: 50.09.</li>
+    <li>Enter the approximate longitude of the stream providing rover in degrees. Example: 8.66.</li>
+    <li>Enter the serial 'Port name' selected on your host for communication with the receiver. Valid port names are
+      <table>
+        <tr>
+          <td>&nbsp; &nbsp; Windows: </td>
+          <td>COM1, COM2</td>
+        </tr>
+        <tr>
+          <td>&nbsp; &nbsp; Linux: </td>
+          <td>/dev/ttyS0, /dev/ttyS1</td>
+        </tr>
+        <tr>
+          <td>&nbsp; &nbsp; FreeBSD: </td>
+          <td>/dev/ttyd0, /dev/ttyd1</td>
+        </tr>
+        <tr>
+          <td>&nbsp; &nbsp; Digital Unix: </td>
+          <td>/dev/tty01, /dev/tty02</td>
+        </tr>
+        <tr>
+          <td>&nbsp; &nbsp; HP-UX: </td>
+          <td>/dev/tty1p0, /dev/tty2p0</td>
+        </tr>
+        <tr>
+          <td>&nbsp; &nbsp; SGI/IRIX; </td>
+          <td>/dev/ttyf1, /dev/ttyf2</td>
+        </tr>
+        <tr>
+          <td>&nbsp; &nbsp; SunOS/Solaris: </td>
+          <td>/dev/ttya, /dev/ttyb</td>
+        </tr>
+      </table>
+    </li>
+    <li>Select a 'Baud rate' for the serial input. Note that using a high baud rate is recommended.</li>
+    <li>Select the number of 'Data bits' for the serial input. Note that often '8' data bits are used.</li>
+    <li>Select the 'Parity' for the serial input. Note that parity is often set to 'NONE'.</li>
+    <li>Select the number of 'Stop bits' for the serial input. Note that often '1' stop bit is used.</li>
+    <li>Select a 'Flow control' for the serial link. Select 'OFF' if you do not know better.</li>
+  </ul>
+  </p>
+  <p>
+    When selecting one of the serial communication options listed above, make sure that you pick those configured to the
+    serially connected GNSS receiver.
+  </p>
+  <p>
+    Streams received from a serially connected GNSS receiver show up with an 'S' (for <u>S</u>erial Port, no Ntrip) in
+    the 'Streams' canvas
+    section on BNC's main window. Latitude and longitude are to be entered just for informal reasons.
+  <p>
+  <p>
+    The following figure shows a BNC example setup for pulling a stream via serial port on a Windows operating system.
+  </p>
+  <p><img src="IMG/Figure40.png" width=400 /></p>
+  <p>Figure 40: BNC configuration for pulling a stream via serial port</p>
+
+  <p>
+  <h4 id="streamsdelete">2.20.2 Delete Stream</h4>
+  </p>
+  <p>
+    Button 'Delete Stream' allows you to delete streams previously selected for retrieval as listed under the 'Streams'
+    canvas on BNC's main window.
+  </p>
+
+  <p>
+  <h4 id="streamsmap">2.20.3 Map</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="start">2.20.4 Start</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+  <h4 id="stop">2.20.5 Stop</h4>
+  </p>
+  <p>
+    Hit the 'Stop' button in order to stop BNC.
+  </p>
+
+  <p>
+  <h4 id="contexthelp">2.20.6 Help? = Shift+F1</h4>
+  </p>
+  <p>
+    BNC comes with a <i>What's This</i> 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.
+  </p>
+  <p>
+  <h4 id="cmd">2.21 Command Line Options</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    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'
+  </p>
+  <p>
+    Example:<br><br>
+    &nbsp; &nbsp; &nbsp; bnc --help (MS Windows: bnc.exe --help | more)
+  </p>
+  <p>
+    provides a list of all available command line options.
+  </p>
+  <p>
+  <h4 id="cmdVersion">2.21.1 Version - optional</h4>
+  </p>
+  <p>
+    Command line option '--version' lets BNC print its version number.
+  </p>
+  <p>
+    Example:<br><br>
+    &nbsp; &nbsp; &nbsp; bnc --version (MS Windows: bnc.exe --version | more)
+  </p>
+  <p>
+  <h4 id="cmdDisplay">2.21.2 Display - optional</h4>
+  </p>
+  <p>
+    On systems which support graphics, command line option '--display' forces BNC to present the BNC window on the
+    specified display.
+  </p>
+  <p>
+    Example:<br><br>
+    &nbsp; &nbsp; &nbsp; bnc.exe --display localhost:10.0
+  </p>
+  <p>
+  <h4 id="nw">2.21.3 No Window Mode - optional</h4>
+  </p>
+  <p>
+    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.
+  </p>
+  <p>
+    Example:<br><br>
+    &nbsp; &nbsp; &nbsp; bnc.exe --nw
+  </p>
+  <p>
+    The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode
+    and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no
+    configuration options
+    previously saved on disc are used:
+    It is obvious that BNC requires graphics support when started in interactive
+    mode. However, note that graphics support is also required when producing plots in
+    batch mode (option -nw). Windows and Mac OS X systems always support graphics. For
+    producing plots in batch mode on Linux systems you must make sure that at
+    least a virtual X-Server such as 'Xvfb' is installed and the '-display' option
+    is used. The following is an example shell script to execute BNC in batch mode
+    for producing QC plots from RINEX files. It could be used via 'crontab':
+
+  <pre><p style="font-family:Monospace">
 #!/bin/bash
 
@@ -6430,312 +9895,381 @@
 </p></pre>
 
-<p><h4 id="post">2.21.4 File Mode - optional</h4></p>
-<p>
-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 &amp; Replay functionality). Enter the following command line option for that
-</p>
-<p>
-&nbsp; &nbsp; &nbsp; --file &lt;<u>inputFileName</u>&gt;
-</p>
-and specify the full path to an input file containing previously saved data. Example:<br><br>
-&nbsp; &nbsp; &nbsp; ./bnc --file /home/user/raw.output_221202
-</p>
-<p>
-Note that when running BNC offline, it will use options for file saving, interval, sampling, PPP etc. from its configuration file.
-</p>
-<p>Note further that option '--file' forces BNC to apply the '-nw' option for running in 'no window' mode.
-</p>
-<p><h4 id="conffile">2.21.5 Configuration File - optional</h4></p>
-The default configuration filename is 'BNC.bnc'. You may change this name at startup time using command line option '--conf &lt;<u>confFileName</u>&gt;'. This allows running several BNC jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> 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.
-</p>
-<p>
-Example:<br><br>
-&nbsp; &nbsp; &nbsp; ./bnc --conf MyConfig.bnc
-</p>
-<p>
-This leads to a BNC job using configuration file 'MyConfig.bnc'. The configuration file will be saved in the current working directory.
-</p>
-<p><h4 id="confopt">2.21.6 Configuration Options - optional</h4></p>
-<p>
-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:
-</p>
-<p>
-&nbsp; &nbsp; &nbsp; --key &lt;keyName&gt; &lt;keyValue&gt;
-</p>
-<p>
-Parameter &lt;keyName&gt; stands for the key name of an option contained in the configuration file and &lt;keyValue&gt;
-stands for the value you want to assign to it. The following is a syntax example for a complete command line:
-</p>
-<p>
-&nbsp; &nbsp; &nbsp; bnc --nw --conf &lt;confFileName&gt --key &lt;keyName1&gt; &lt;keyValue1&gt; --key &lt;keyName2&gt; &lt;keyValue2&gt; ...
-</p>
-<p>
-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
-</p>
-<p>
-&nbsp; &nbsp; &nbsp; 'PPP/minObs'
-</p>
-on a command line.
-<p>
-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.
-</p>
-<p><h3 id="annex">3. Annex</h3></p>
-
-<p><h4 id="rtcm">3.1 RTCM Standards</h4></p>
-<p>
-The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional and educational organization.
-Special Committees provide a forum in which governmental and non-governmental members work together to develop
-technical standards and consensus recommendations in regard to issues of particular concern.
-RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication systems.
-The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards.
-Topics concerning Differential Global Navigation Satellite Systems (DGNSS) are handled by the Special Committee SC 104.
-<p>
-Personal copies of RTCM Recommended Standards can be ordered through
-<a href="https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards" target="_blank">https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards</a>
-
-</p>
-<p><h4 id="ntrip1">3.1.1 Ntrip Version 1</h4></p>
-<p>
-'Networked Transport of RTCM via Internet Protocol' Version 1.0 (Ntrip) stands for an application-level protocol streaming
-Global Navigation Satellite System (GNSS) data over the Internet. Ntrip is a generic, stateless protocol based on the
-Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.
-</p>
-<p>
-Ntrip Version 1 is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or
-other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA,
-or receiver connections to a broadcasting host. Ntrip supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.
-</p>
-
-<p>
-Ntrip is implemented in three system software components: Ntrip Clients, Ntrip Servers and Ntrip Broadcasters.
-The Ntrip Broadcaster is the actual HTTP server program whereas Ntrip Client and Ntrip Server are acting as HTTP clients.
-</p>
-<p>
-Ntrip is an open none-proprietary protocol. Major characteristics of Ntrip's dissemination technique are:
-<ul>
-  <li>Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and server platform resources available;</li>
-  <li>Application not limited to one particular plain or coded stream content; ability to distribute any kind of GNSS data;</li>
-  <li>Potential to support mass usage; disseminating hundreds of streams simultaneously for thousands of users possible when applying modified Internet Radio broadcasting software;</li>
-  <li>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;</li>
-  <li>Enables streaming over mobile IP networks because of using TCP/IP.</li>
-</ul>
-</p>
-<p>
-The Ntrip Broadcaster maintains a source-table containing information on available Ntrip streams, networks of Ntrip streams and Ntrip Broadcasters.
-See at <a href="https://software.rtcm-ntrip.org/wiki/Sourcetable" target="_blank">https://software.rtcm-ntrip.org/wiki/Sourcetable</a> for details.
-</p>
-<p>
-Source-table records are dedicated to one of the following:
-<ul>
-  <li>Data Streams (record type STR, for details see at: <a href="https://software.rtcm-ntrip.org/wiki/STR" target="_blank">https://software.rtcm-ntrip.org/wiki/STR</a> </li>
-  <li>Casters (record type CAS, for details see at: <a href="https://software.rtcm-ntrip.org/wiki/CAS" target="_blank">https://software.rtcm-ntrip.org/wiki/CAS</a> </li>
-  <li>Networks of streams (record type NET, for details see at: <a href="https://software.rtcm-ntrip.org/wiki/NET" target="_blank">https://software.rtcm-ntrip.org/wiki/NET</a> </li>
-</ul>
-</p>
-The source-table is sent to an Ntrip Client on request.
-</p>
-<p><h4 id="ntrip2">3.1.2 Ntrip Version 2</h4></p>
-<p>
-The major changes of Ntrip Version 2 compared to Version 1.0 are:
-</p>
-<ul>
-  <li>Cleared and fixed design problems and HTTP protocol violations;</li>
-  <li>Replaced nonstandard directives;</li>
-  <li>Chunked transfer encoding;</li>
-  <li>Improvements in header records;</li>
-  <li>Source-table filtering;</li>
-  <li>RTSP communication.</li>
-</ul>
-<p>
-Ntrip Version 2 allows to communicate either in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas Version 1 is limited to TCP/IP only.
-</p>
-<p>
-It furthermore allows using the Transport Layer Security (TLS) for secure Ntrip communication over the Internet.
-</p>
-<p><h4 id="rtcm2">3.1.3 RTCM Version 2</h4></p>
-<p>
-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:
-</p>
-<ul>
-  <li>Type 1 message is the range correction message and is the primary message in code-phase differential positioning (DGPS).
+  <p>
+  <h4 id="post">2.21.4 File Mode - optional</h4>
+  </p>
+  <p>
+    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 &amp; Replay functionality). Enter the following command
+    line option for that
+  </p>
+  <p>
+    &nbsp; &nbsp; &nbsp; --file &lt;<u>inputFileName</u>&gt;
+  </p>
+  and specify the full path to an input file containing previously saved data. Example:<br><br>
+  &nbsp; &nbsp; &nbsp; ./bnc --file /home/user/raw.output_221202
+  </p>
+  <p>
+    Note that when running BNC offline, it will use options for file saving, interval, sampling, PPP etc. from its
+    configuration file.
+  </p>
+  <p>Note further that option '--file' forces BNC to apply the '-nw' option for running in 'no window' mode.
+  </p>
+  <p>
+  <h4 id="conffile">2.21.5 Configuration File - optional</h4>
+  </p>
+  The default configuration filename is 'BNC.bnc'. You may change this name at startup time using command line option
+  '--conf &lt;<u>confFileName</u>&gt;'. This allows running several BNC jobs in parallel on the same host using
+  different sets of configuration options. <u>confFileName</u> 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.
+  </p>
+  <p>
+    Example:<br><br>
+    &nbsp; &nbsp; &nbsp; ./bnc --conf MyConfig.bnc
+  </p>
+  <p>
+    This leads to a BNC job using configuration file 'MyConfig.bnc'. The configuration file will be saved in the current
+    working directory.
+  </p>
+  <p>
+  <h4 id="confopt">2.21.6 Configuration Options - optional</h4>
+  </p>
+  <p>
+    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:
+  </p>
+  <p>
+    &nbsp; &nbsp; &nbsp; --key &lt;keyName&gt; &lt;keyValue&gt;
+  </p>
+  <p>
+    Parameter &lt;keyName&gt; stands for the key name of an option contained in the configuration file and
+    &lt;keyValue&gt;
+    stands for the value you want to assign to it. The following is a syntax example for a complete command line:
+  </p>
+  <p>
+    &nbsp; &nbsp; &nbsp; bnc --nw --conf &lt;confFileName&gt --key &lt;keyName1&gt; &lt;keyValue1&gt; --key
+    &lt;keyName2&gt; &lt;keyValue2&gt; ...
+  </p>
+  <p>
+    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
+  </p>
+  <p>
+    &nbsp; &nbsp; &nbsp; 'PPP/minObs'
+  </p>
+  on a command line.
+  <p>
+    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.
+  </p>
+  <p>
+  <h3 id="annex">3. Annex</h3>
+  </p>
+
+  <p>
+  <h4 id="rtcm">3.1 RTCM Standards</h4>
+  </p>
+  <p>
+    The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional
+    and educational organization.
+    Special Committees provide a forum in which governmental and non-governmental members work together to develop
+    technical standards and consensus recommendations in regard to issues of particular concern.
+    RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication
+    systems.
+    The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards.
+    Topics concerning Differential Global Navigation Satellite Systems (DGNSS) are handled by the Special Committee SC
+    104.
+  <p>
+    Personal copies of RTCM Recommended Standards can be ordered through
+    <a href="https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards"
+      target="_blank">https://rtcm.myshopify.com/collections/differential-global-navigation-satellite-dgnss-standards</a>
+
+  </p>
+  <p>
+  <h4 id="ntrip1">3.1.1 Ntrip Version 1</h4>
+  </p>
+  <p>
+    'Networked Transport of RTCM via Internet Protocol' Version 1.0 (Ntrip) stands for an application-level protocol
+    streaming
+    Global Navigation Satellite System (GNSS) data over the Internet. Ntrip is a generic, stateless protocol based on
+    the
+    Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.
+  </p>
+  <p>
+    Ntrip Version 1 is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104
+    format) or
+    other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC,
+    Laptop, PDA,
+    or receiver connections to a broadcasting host. Ntrip supports wireless Internet access through Mobile IP Networks
+    like GSM, GPRS, EDGE, or UMTS.
+  </p>
+
+  <p>
+    Ntrip is implemented in three system software components: Ntrip Clients, Ntrip Servers and Ntrip Broadcasters.
+    The Ntrip Broadcaster is the actual HTTP server program whereas Ntrip Client and Ntrip Server are acting as HTTP
+    clients.
+  </p>
+  <p>
+    Ntrip is an open none-proprietary protocol. Major characteristics of Ntrip's dissemination technique are:
+  <ul>
+    <li>Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and
+      server platform resources available;</li>
+    <li>Application not limited to one particular plain or coded stream content; ability to distribute any kind of GNSS
+      data;</li>
+    <li>Potential to support mass usage; disseminating hundreds of streams simultaneously for thousands of users
+      possible when applying modified Internet Radio broadcasting software;</li>
+    <li>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;</li>
+    <li>Enables streaming over mobile IP networks because of using TCP/IP.</li>
+  </ul>
+  </p>
+  <p>
+    The Ntrip Broadcaster maintains a source-table containing information on available Ntrip streams, networks of Ntrip
+    streams and Ntrip Broadcasters.
+    See at <a href="https://software.rtcm-ntrip.org/wiki/Sourcetable"
+      target="_blank">https://software.rtcm-ntrip.org/wiki/Sourcetable</a> for details.
+  </p>
+  <p>
+    Source-table records are dedicated to one of the following:
+  <ul>
+    <li>Data Streams (record type STR, for details see at: <a href="https://software.rtcm-ntrip.org/wiki/STR"
+        target="_blank">https://software.rtcm-ntrip.org/wiki/STR</a> </li>
+    <li>Casters (record type CAS, for details see at: <a href="https://software.rtcm-ntrip.org/wiki/CAS"
+        target="_blank">https://software.rtcm-ntrip.org/wiki/CAS</a> </li>
+    <li>Networks of streams (record type NET, for details see at: <a href="https://software.rtcm-ntrip.org/wiki/NET"
+        target="_blank">https://software.rtcm-ntrip.org/wiki/NET</a> </li>
+  </ul>
+  </p>
+  The source-table is sent to an Ntrip Client on request.
+  </p>
+  <p>
+  <h4 id="ntrip2">3.1.2 Ntrip Version 2</h4>
+  </p>
+  <p>
+    The major changes of Ntrip Version 2 compared to Version 1.0 are:
+  </p>
+  <ul>
+    <li>Cleared and fixed design problems and HTTP protocol violations;</li>
+    <li>Replaced nonstandard directives;</li>
+    <li>Chunked transfer encoding;</li>
+    <li>Improvements in header records;</li>
+    <li>Source-table filtering;</li>
+    <li>RTSP communication.</li>
+  </ul>
+  <p>
+    Ntrip Version 2 allows to communicate either in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas Version 1 is
+    limited to TCP/IP only.
+  </p>
+  <p>
+    It furthermore allows using the Transport Layer Security (TLS) for secure Ntrip communication over the Internet.
+  </p>
+  <p>
+  <h4 id="rtcm2">3.1.3 RTCM Version 2</h4>
+  </p>
+  <p>
+    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:
+  </p>
+  <ul>
+    <li>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.</li>
-  <li>Type 2 message is automatically generated when a new set of satellite ephemeris is downloaded to the base receiver.
+    <li>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.</li>
-  <li>Type 3 and 22 messages are the base station position and the antenna offset.
+    <li>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.</li>
-  <li>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).
+    <li>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.</li>
-  <li>Type 9 message serves the same purpose as Type 1, but does not require a complete satellite set.
+    <li>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.</li>
-  <li>Type 16 message is simply a text message entered by the user that is transmitted from the base station to the rover.
+    <li>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.</li>
-  <li>Type 18 and 20 messages are RTK uncorrected carrier phase data and carrier phase corrections.</li>
-  <li>Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo-range corrections used in RTK.</li>
-  <li>Type 23 message provides the information on the antenna type used on the reference station.</li>
-  <li>Type 24 message carries the coordinates of the installed antenna's ARP in the GNSS coordinate system coordinates.</li>
-</ul>
-
-<p><h4 id="rtcm3">3.1.4 RTCM Version 3</h4></p>
-<p>
-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.
-</p>
-
-<p>
-RTCM Version 3 defines a number of message types. Messages that may be of interest here are:
-<ul>
-  <li>Type 1001, GPS L1 code and phase.</li>
-  <li>Type 1002, GPS L1 code and phase and ambiguities and carrier-to-noise ratio.</li>
-  <li>Type 1003, GPS L1 and L2 code and phase.</li>
-  <li>Type 1004, GPS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.</li>
-  <li>Type 1005, Station coordinates XYZ for antenna reference point.</li>
-  <li>Type 1006, Station coordinates XYZ for antenna reference point and antenna height.</li>
-  <li>Type 1007, Antenna descriptor and ID.</li>
-  <li>Type 1008, Antenna serial number.</li>
-  <li>Type 1009, GLONASS L1 code and phase.</li>
-  <li>Type 1010, GLONASS L1 code and phase and ambiguities and carrier-to-noise ratio.</li>
-  <li>Type 1011, GLONASS L1 and L2 code and phase.</li>
-  <li>Type 1012, GLONASS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.</li>
-  <li>Type 1013, Modified Julian Date, leap second, configured message types and interval.</li>
-  <li>Type 1019, GPS ephemeris.</li>
-  <li>Type 1020, GLONASS ephemeris.</li>
-  <li>Type 1041  NavIC ephemeris.</li>
-  <li>Type 1042, BDS/BeiDou ephemeris.</li>
-  <li>Type 1043, SBAS ephemeris.</li>
-  <li>Type 1044, QZSS ephemeris.</li>
-  <li>Type 1045, Galileo F/NAV ephemeris.</li>
-  <li>Type 1046, Galileo I/NAV ephemeris.</li>
-  <li>Type 1300, Service CRS. </li>
-  <li>Type 1301, Helmert transformation parameters. </li>
-  <li>Type 1302, RTCM CRS. </li>
-  <li>Type 4076, Proprietary messages of the International IGS Service.</li>
-</ul>
-</p>
-
-<p>
-The following are so-called 'State Space Representation' (SSR) messages defined or proposed within RTCM SC-104:
-<ul>
-  <li>Type 1057, GPS orbit corrections to Broadcast Ephemeris</li>
-  <li>Type 1058, GPS clock corrections to Broadcast Ephemeris</li>
-  <li>Type 1059, GPS code biases</li>
-  <li>Type 1060, Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
-  <li>Type 1061, GPS User Range Accuracy (URA)</li>
-  <li>Type 1062, High-rate GPS clock corrections to Broadcast Ephemeris<br><br></li>
-
-  <li>Type 1063, GLONASS orbit corrections to Broadcast Ephemeris</li>
-  <li>Type 1064, GLONASS clock corrections to Broadcast Ephemeris</li>
-  <li>Type 1065, GLONASS code biases</li>
-  <li>Type 1066, Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
-  <li>Type 1067, GLONASS User Range Accuracy (URA)</li>
-  <li>Type 1068, High-rate GLONASS clock corrections to Broadcast Ephemeris<br><br></li>
-
-  <li>Type 1240, Galileo orbit corrections to Broadcast Ephemeris</li>
-  <li>Type 1241, Galileo clock corrections to Broadcast Ephemeris</li>
-  <li>Type 1242, Galileo code biases</li>
-  <li>Type 1243, Combined orbit and clock corrections to Galileo Broadcast Ephemeris</li>
-  <li>Type 1244, Galileo User Range Accuracy (URA)</li>
-  <li>Type 1245, High-rate Galileo clock corrections to Broadcast Ephemeris<br><br></li>
-
-  <li>Type 1246, QZSS orbit corrections to Broadcast Ephemeris</li>
-  <li>Type 1247, QZSS clock corrections to Broadcast Ephemeris</li>
-  <li>Type 1248, QZSS code biases</li>
-  <li>Type 1249, Combined orbit and clock corrections to QZSS Broadcast Ephemeris</li>
-  <li>Type 1250, QZSS User Range Accuracy (URA)</li>
-  <li>Type 1251, High-rate QZSS clock corrections to Broadcast Ephemeris<br><br></li>
-
-  <li>Type 1252, SBAS orbit corrections to Broadcast Ephemeris</li>
-  <li>Type 1253, SBAS clock corrections to Broadcast Ephemeris</li>
-  <li>Type 1254, SBAS code biases</li>
-  <li>Type 1255, Combined orbit and clock corrections to SBAS Broadcast Ephemeris</li>
-  <li>Type 1256, SBAS User Range Accuracy (URA)</li>
-  <li>Type 1257, High-rate SBAS clock corrections to Broadcast Ephemeris<br><br></li>
-
-  <li>Type 1258, BDS orbit corrections to Broadcast Ephemeris</li>
-  <li>Type 1259, BDS clock corrections to Broadcast Ephemeris</li>
-  <li>Type 1260, BDS code biases</li>
-  <li>Type 1261, Combined orbit and clock corrections to BDS Broadcast Ephemeris</li>
-  <li>Type 1262, BDS User Range Accuracy (URA)</li>
-  <li>Type 1263, High-rate BDS clock corrections to Broadcast Ephemeris<br><br></li>
-
-  <li>Type 1264 SSR Ionosphere VTEC Spherical Harmonics</li>
-  <li>Type 1265 SSR GPS Satellite Phase Bias</li>
-  <li>Type 1266 SSR Satellite GLONASS Phase Bias</li>
-  <li>Type 1267 SSR Satellite Galileo Phase Bias</li>
-  <li>Type 1268 SSR Satellite QZSS Phase Bias</li>
-  <li>Type 1269 SSR Satellite SBAS Phase Bias</li>
-  <li>Type 1270 SSR Satellite BDS Phase Bias</li>
-</ul>
-</p>
-
-<p>
-The following are so-called 'Multiple Signal Messages' (MSM) defined within RTCM SC-104:
-<ul>
-  <li>Type 1071, Compact GPS pseudo-ranges</li>
-  <li>Type 1072, Compact GPS carrier phases</li>
-  <li>Type 1073, Compact GPS pseudo-ranges and carrier phases</li>
-  <li>Type 1074, Full GPS pseudo-ranges and carrier phases plus signal strength</li>
-  <li>Type 1075, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength</li>
-  <li>Type 1076, Full GPS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
-  <li>Type 1077, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
-
-  <li>Type 1081, Compact GLONASS pseudo-ranges</li>
-  <li>Type 1082, Compact GLONASS carrier phases</li>
-  <li>Type 1083, Compact GLONASS pseudo-ranges and carrier phases</li>
-  <li>Type 1084, Full GLONASS pseudo-ranges and carrier phases plus signal strength</li>
-  <li>Type 1085, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength</li>
-  <li>Type 1086, Full GLONASS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
-  <li>Type 1087, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
-
-  <li>Type 1091, Compact Galileo pseudo-ranges</li>
-  <li>Type 1092, Compact Galileo carrier phases</li>
-  <li>Type 1093, Compact Galileo pseudo-ranges and carrier phases</li>
-  <li>Type 1094, Full Galileo pseudo-ranges and carrier phases plus signal strength</li>
-  <li>Type 1095, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength</li>
-  <li>Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
-  <li>Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
-
-  <li>Type 1101, Compact SBAS pseudo-ranges</li>
-  <li>Type 1102, Compact SBAS carrier phases</li>
-  <li>Type 1103, Compact SBAS pseudo-ranges and carrier phases</li>
-  <li>Type 1104, Full SBAS pseudo-ranges and carrier phases plus signal strength</li>
-  <li>Type 1105, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength</li>
-  <li>Type 1106, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
-  <li>Type 1107, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
-
-  <li>Type 1121, Compact BeiDou pseudo-ranges</li>
-  <li>Type 1122, Compact BeiDou carrier phases</li>
-  <li>Type 1123, Compact BeiDou pseudo-ranges and carrier phases</li>
-  <li>Type 1124, Full BeiDou pseudo-ranges and carrier phases plus signal strength</li>
-  <li>Type 1125, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength</li>
-  <li>Type 1126, Full BeiDou pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
-  <li>Type 1127, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
-
-  <li>Type 1111, Compact QZSS pseudo-ranges</li>
-  <li>Type 1112, Compact QZSS carrier phases</li>
-  <li>Type 1113, Compact QZSS pseudo-ranges and carrier phases</li>
-  <li>Type 1114, Full QZSS pseudo-ranges and carrier phases plus signal strength</li>
-  <li>Type 1115, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength</li>
-  <li>Type 1116, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
-  <li>Type 1117, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
-</ul>
-</p>
-
-<p><h4 id="confList">3.2 Command Line Help</h3></p>
-<p>
-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':
-</p>
-
-<pre><p style="font-family:Monospace">
+    <li>Type 18 and 20 messages are RTK uncorrected carrier phase data and carrier phase corrections.</li>
+    <li>Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo-range corrections used in RTK.
+    </li>
+    <li>Type 23 message provides the information on the antenna type used on the reference station.</li>
+    <li>Type 24 message carries the coordinates of the installed antenna's ARP in the GNSS coordinate system
+      coordinates.</li>
+  </ul>
+
+  <p>
+  <h4 id="rtcm3">3.1.4 RTCM Version 3</h4>
+  </p>
+  <p>
+    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.
+  </p>
+
+  <p>
+    RTCM Version 3 defines a number of message types. Messages that may be of interest here are:
+  <ul>
+    <li>Type 1001, GPS L1 code and phase.</li>
+    <li>Type 1002, GPS L1 code and phase and ambiguities and carrier-to-noise ratio.</li>
+    <li>Type 1003, GPS L1 and L2 code and phase.</li>
+    <li>Type 1004, GPS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.</li>
+    <li>Type 1005, Station coordinates XYZ for antenna reference point.</li>
+    <li>Type 1006, Station coordinates XYZ for antenna reference point and antenna height.</li>
+    <li>Type 1007, Antenna descriptor and ID.</li>
+    <li>Type 1008, Antenna serial number.</li>
+    <li>Type 1009, GLONASS L1 code and phase.</li>
+    <li>Type 1010, GLONASS L1 code and phase and ambiguities and carrier-to-noise ratio.</li>
+    <li>Type 1011, GLONASS L1 and L2 code and phase.</li>
+    <li>Type 1012, GLONASS L1 and L2 code and phase and ambiguities and carrier-to-noise ratio.</li>
+    <li>Type 1013, Modified Julian Date, leap second, configured message types and interval.</li>
+    <li>Type 1019, GPS ephemeris.</li>
+    <li>Type 1020, GLONASS ephemeris.</li>
+    <li>Type 1041 NavIC ephemeris.</li>
+    <li>Type 1042, BDS/BeiDou ephemeris.</li>
+    <li>Type 1043, SBAS ephemeris.</li>
+    <li>Type 1044, QZSS ephemeris.</li>
+    <li>Type 1045, Galileo F/NAV ephemeris.</li>
+    <li>Type 1046, Galileo I/NAV ephemeris.</li>
+    <li>Type 1300, Service CRS. </li>
+    <li>Type 1301, Helmert transformation parameters. </li>
+    <li>Type 1302, RTCM CRS. </li>
+    <li>Type 4076, Proprietary messages of the International IGS Service.</li>
+  </ul>
+  </p>
+
+  <p>
+    The following are so-called 'State Space Representation' (SSR) messages defined or proposed within RTCM SC-104:
+  <ul>
+    <li>Type 1057, GPS orbit corrections to Broadcast Ephemeris</li>
+    <li>Type 1058, GPS clock corrections to Broadcast Ephemeris</li>
+    <li>Type 1059, GPS code biases</li>
+    <li>Type 1060, Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
+    <li>Type 1061, GPS User Range Accuracy (URA)</li>
+    <li>Type 1062, High-rate GPS clock corrections to Broadcast Ephemeris<br><br></li>
+
+    <li>Type 1063, GLONASS orbit corrections to Broadcast Ephemeris</li>
+    <li>Type 1064, GLONASS clock corrections to Broadcast Ephemeris</li>
+    <li>Type 1065, GLONASS code biases</li>
+    <li>Type 1066, Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
+    <li>Type 1067, GLONASS User Range Accuracy (URA)</li>
+    <li>Type 1068, High-rate GLONASS clock corrections to Broadcast Ephemeris<br><br></li>
+
+    <li>Type 1240, Galileo orbit corrections to Broadcast Ephemeris</li>
+    <li>Type 1241, Galileo clock corrections to Broadcast Ephemeris</li>
+    <li>Type 1242, Galileo code biases</li>
+    <li>Type 1243, Combined orbit and clock corrections to Galileo Broadcast Ephemeris</li>
+    <li>Type 1244, Galileo User Range Accuracy (URA)</li>
+    <li>Type 1245, High-rate Galileo clock corrections to Broadcast Ephemeris<br><br></li>
+
+    <li>Type 1246, QZSS orbit corrections to Broadcast Ephemeris</li>
+    <li>Type 1247, QZSS clock corrections to Broadcast Ephemeris</li>
+    <li>Type 1248, QZSS code biases</li>
+    <li>Type 1249, Combined orbit and clock corrections to QZSS Broadcast Ephemeris</li>
+    <li>Type 1250, QZSS User Range Accuracy (URA)</li>
+    <li>Type 1251, High-rate QZSS clock corrections to Broadcast Ephemeris<br><br></li>
+
+    <li>Type 1252, SBAS orbit corrections to Broadcast Ephemeris</li>
+    <li>Type 1253, SBAS clock corrections to Broadcast Ephemeris</li>
+    <li>Type 1254, SBAS code biases</li>
+    <li>Type 1255, Combined orbit and clock corrections to SBAS Broadcast Ephemeris</li>
+    <li>Type 1256, SBAS User Range Accuracy (URA)</li>
+    <li>Type 1257, High-rate SBAS clock corrections to Broadcast Ephemeris<br><br></li>
+
+    <li>Type 1258, BDS orbit corrections to Broadcast Ephemeris</li>
+    <li>Type 1259, BDS clock corrections to Broadcast Ephemeris</li>
+    <li>Type 1260, BDS code biases</li>
+    <li>Type 1261, Combined orbit and clock corrections to BDS Broadcast Ephemeris</li>
+    <li>Type 1262, BDS User Range Accuracy (URA)</li>
+    <li>Type 1263, High-rate BDS clock corrections to Broadcast Ephemeris<br><br></li>
+
+    <li>Type 1264 SSR Ionosphere VTEC Spherical Harmonics</li>
+    <li>Type 1265 SSR GPS Satellite Phase Bias</li>
+    <li>Type 1266 SSR Satellite GLONASS Phase Bias</li>
+    <li>Type 1267 SSR Satellite Galileo Phase Bias</li>
+    <li>Type 1268 SSR Satellite QZSS Phase Bias</li>
+    <li>Type 1269 SSR Satellite SBAS Phase Bias</li>
+    <li>Type 1270 SSR Satellite BDS Phase Bias</li>
+  </ul>
+  </p>
+
+  <p>
+    The following are so-called 'Multiple Signal Messages' (MSM) defined within RTCM SC-104:
+  <ul>
+    <li>Type 1071, Compact GPS pseudo-ranges</li>
+    <li>Type 1072, Compact GPS carrier phases</li>
+    <li>Type 1073, Compact GPS pseudo-ranges and carrier phases</li>
+    <li>Type 1074, Full GPS pseudo-ranges and carrier phases plus signal strength</li>
+    <li>Type 1075, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength</li>
+    <li>Type 1076, Full GPS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
+    <li>Type 1077, Full GPS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
+
+    <li>Type 1081, Compact GLONASS pseudo-ranges</li>
+    <li>Type 1082, Compact GLONASS carrier phases</li>
+    <li>Type 1083, Compact GLONASS pseudo-ranges and carrier phases</li>
+    <li>Type 1084, Full GLONASS pseudo-ranges and carrier phases plus signal strength</li>
+    <li>Type 1085, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength</li>
+    <li>Type 1086, Full GLONASS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
+    <li>Type 1087, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br>
+    </li>
+
+    <li>Type 1091, Compact Galileo pseudo-ranges</li>
+    <li>Type 1092, Compact Galileo carrier phases</li>
+    <li>Type 1093, Compact Galileo pseudo-ranges and carrier phases</li>
+    <li>Type 1094, Full Galileo pseudo-ranges and carrier phases plus signal strength</li>
+    <li>Type 1095, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength</li>
+    <li>Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
+    <li>Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br>
+    </li>
+
+    <li>Type 1101, Compact SBAS pseudo-ranges</li>
+    <li>Type 1102, Compact SBAS carrier phases</li>
+    <li>Type 1103, Compact SBAS pseudo-ranges and carrier phases</li>
+    <li>Type 1104, Full SBAS pseudo-ranges and carrier phases plus signal strength</li>
+    <li>Type 1105, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength</li>
+    <li>Type 1106, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
+    <li>Type 1107, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
+
+    <li>Type 1121, Compact BeiDou pseudo-ranges</li>
+    <li>Type 1122, Compact BeiDou carrier phases</li>
+    <li>Type 1123, Compact BeiDou pseudo-ranges and carrier phases</li>
+    <li>Type 1124, Full BeiDou pseudo-ranges and carrier phases plus signal strength</li>
+    <li>Type 1125, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength</li>
+    <li>Type 1126, Full BeiDou pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
+    <li>Type 1127, Full BeiDou pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
+
+    <li>Type 1111, Compact QZSS pseudo-ranges</li>
+    <li>Type 1112, Compact QZSS carrier phases</li>
+    <li>Type 1113, Compact QZSS pseudo-ranges and carrier phases</li>
+    <li>Type 1114, Full QZSS pseudo-ranges and carrier phases plus signal strength</li>
+    <li>Type 1115, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength</li>
+    <li>Type 1116, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
+    <li>Type 1117, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
+  </ul>
+  </p>
+
+  <p>
+  <h4 id="confList">3.2 Command Line Help</h3>
+    </p>
+    <p>
+      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':
+    </p>
+
+    <pre><p style="font-family:Monospace">
 Usage:
    bnc --help (MS Windows: bnc.exe --help | more)
@@ -7003,138 +10537,470 @@
 </p></pre>
 
-<p><h4 id="links">3.3 Further Reading</h3></p>
-
-<b>Links:</b><br>
-<table>
-  <tr><td>Ntrip &nbsp;</td><td><a href="https://igs.bkg.bund.de/ntrip/index" target="_blank">https://igs.bkg.bund.de/ntrip/index</a></td></tr>
-  <tr><td>IGS Real-Rime Service (RTS) &nbsp;</td><td><a href="https://igs.org/rts/" target="_blank">https://igs.org/rts/</a></td></tr>
-  <tr><td>Ntrip Broadcaster overview &nbsp;</td><td><a href="https://rtcm-ntrip.org/home" target="_blank">https://rtcm-ntrip.org/home</a></td></tr>
-  <tr><td>Ntrip Open Source software code &nbsp;</td><td><a href="https://software.rtcm-ntrip.org" target="_blank">https://software.rtcm-ntrip.org</a></td></tr>
-  <tr><td>Radio Technical Commission for Maritime Services &nbsp;</td><td><a href="https://www.rtcm.org/" target="_blank">https://www.rtcm.org/</a></td></tr>
-</table>
-<br>
-
-<b>Publications:</b><br>
-<table border="1">
-<tr><td>Caissy, M., L. Agrotis, G. Weber, M. Hernandez-Pajares and U. Hugentobler (2012)</td><td>The International GNSS Real-Time Service. GPS World, June 1, 2012.</td></tr>
-
-<tr><td>Estey, L. H. and C. M. Meertens (1999)</td><td>TEQC: The Multi-Purpose Toolkit for GPS/GLONASS Data. GPS Solutions, Vol. 3, No. 1, pp. 42-49, 1999.</td></tr>
-
-<tr><td>Huisman, L., P. Teunissen and C. Hu (2012)</td><td>GNSS Precise Point Positioning in Regional Reference Frames Using Real-time Broadcast Corrections. Journal of Applied Geodesy, Vol. 6, pp15-23, 2012.</td></tr>
-
-<tr><td>Mervart, L., Z. Lukes, C. Rocken and T. Iwabuchi (2008)</td><td>Precise Point Positioning With Ambiguity Resolution in Real-Time. ION GNSS 2008.</td></tr>
-
-<tr><td>RTCM SC-104 (2011)</td><td>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.</td></tr>
-
-<tr><td>Rupprecht, W. (2000)</td><td>DGPS-IP. <u>http://www.wsrcc.com/wolfgang/gps/dgps-ip.html</u>, 2000.</td></tr>
-
-<tr><td>St&uuml;rze, A., L. Mervart, W. Söhne, G. Weber, G. Wübbena (2012)</td><td>Real-Time PPP using open CORS Networks and RTCM Standards. 3rd International Conference on Machine Control & Guidance, March 27-29, 2012  </td></tr>
-
-<tr><td>Weber, G., D. Dettmering and H. Gebhard (2005a)</td><td>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.</td></tr>
-
-<tr><td>Weber, G., D. Dettmering, H. Gebhard and R. Kalafus (2005b)</td><td>Networked Transport of RTCM via Internet Protocol (Ntrip), IP-Streaming for Real-Time GNSS Applications. ION GNSS 2005.</td></tr>
-
-<tr><td>Weber, G., and M. Honkala (2004)</td><td>The future is talking Ntrip. Newsletter, Trimble GmbH Raunheim, Germany, 2004.</td></tr>
-
-<tr><td>Weber, G. and L. Mervart (2009)</td><td>The BKG Ntrip Client (BNC), Report on EUREF Symposium 2007 in London. Mitteilungen des Bundesamtes fuer Kartographie und Geodaesie, Band 42, Frankfurt, 2009.</td></tr>
-
-<tr><td>Weber, G. and L. Mervart (2010)</td><td>Real-time Combination of GNSS Orbit and Clock Correction Streams Using a Kalman Filter Approach. ION GNSS 2010.</td></tr>
-
-<tr><td>Weber, G, L. Mervart, Z. Lukes, C. Rocken and J. Dousa (2007)</td><td>Real-time Clock and Orbit Corrections for Improved Point Positioning via Ntrip. ION GNSS 2007.</td></tr>
-
-<tr><td>Weber, G., L. Mervart, A. St&uuml;rze, A. R&uuml;lke and D. St&ouml;cker (2016)</td><td>BKG Ntrip Client, Version 2.12. Mitteilungen des Bundesamtes f&uuml;r Kartographie und Geod&auml;sie, Vol. 49, Frankfurt am Main, 2016.</td><tr>
-</table>
-
-<p><h4 id="abbrev">3.4 Abbreviations</h3></p>
-<table>
-  <tr><td>AC</td><td>Analysis Center</td></tr>
-  <tr><td>AFREF</td><td>IAG Reference Frame Sub-Commission for Africa</td></tr>
-  <tr><td>ANTEX</td><td>Antenna Exchange Format</td></tr>
-  <tr><td>APC</td><td>Antenna Phase Center</td></tr>
-  <tr><td>APREF</td><td>IAG Reference Frame Sub-Commission for Asia and Pacific</td></tr>
-  <tr><td>ARP</td><td>Antenna Reference Point</td></tr>
-  <tr><td>BKG</td><td>Bundesamt f&uuml;r Kartographie und  Geod&auml;sie</td></tr>
-  <tr><td>BNC</td><td>BNK Ntrip Client</td></tr>
-  <tr><td>BSW</td><td>Bernese GNSS Software</td></tr>
-  <tr><td>CC</td><td>Combination Center</td></tr>
-  <tr><td>CLI</td><td>Command Line Interface</td></tr>
-  <tr><td>CoM</td><td>Center Of Mass</td></tr>
-  <tr><td>DGNSS</td><td>Differential GNSS</td></tr>
-  <tr><td>DGPS-IP</td><td>Differential GPS via Internet Protocol</td></tr>
-  <tr><td>DMG</td><td>Disk Image, File</td></tr>
-  <tr><td>DREF91</td><td>Geodetic Datum for Germany 1991</td></tr>
-  <tr><td>ECEF</td><td>Earth-Centred-Earth-Fixed</td></tr>
-  <tr><td>EDGE</td><td>Enhanced Data Rates for GSM Evolution</td></tr>
-  <tr><td>ETRF2000</td><td>European Terrestrial Reference Frame 2000</td></tr>
-  <tr><td>EUREF</td><td>IAG Reference Frame Sub-Commission for Europe</td></tr>
-  <tr><td>EoE</td><td>End of Epoch</td></tr>
-  <tr><td>FKP</td><td>Fl&auml;chen-Korrektur-Parameter</td></tr>
-  <tr><td>FTP</td><td>File Transfer Protocol</td></tr>
-  <tr><td>GDA2020</td><td>Geodetic Datum Australia 2020</td></tr>
-  <tr><td>GNSS</td><td>Global Navigation Satellite System</td></tr>
-  <tr><td>GNU</td><td>GNU's Not Unix</td></tr>
-  <tr><td>GPL</td><td>General Public License</td></tr>
-  <tr><td>GPRS</td><td>General Packet Radio Service</td></tr>
-  <tr><td>GPSWD</td><td>GPS Week and Day</td></tr>
-  <tr><td>GSM</td><td>Global System for Mobile Communications</td></tr>
-  <tr><td>GUI</td><td>Graphical User Interface</td></tr>
-  <tr><td>HP MSM</td><td>High Precision Multiple Signal Messages</td></tr>
-  <tr><td>HR URA</td><td>High Rate User Range Accuracy</td></tr>
-  <tr><td>HTTP</td><td>Hypertext Transfer Protocol</td></tr>
-  <tr><td>HTTPS</td><td>Hypertext Transfer Protocol Secure</td></tr>
-  <tr><td>IAG</td><td>International Association of Geodesy</td></tr>
-  <tr><td>ICECAST</td><td>Streaming Media Server</td></tr>
-  <tr><td>IGS20</td><td>IGS Reference Frame 2020</td></tr>
-  <tr><td>IGS</td><td>International GNSS Service</td></tr>
-  <tr><td>IOD</td><td>Issue of Data</td></tr>
-  <tr><td>IP</td><td>Internet Protocol</td></tr>
-  <tr><td>ITRF2020</td><td>International Terrestrial Reference Frame 2020</td></tr>
-  <tr><td>L3</td><td>Ionosphere-Free Linear Combination Of Phase Observations</td></tr>
-  <tr><td>LAN</td><td>Local Area Network</td></tr>
-  <tr><td>LC</td><td>Linea Combination</td></tr>
-  <tr><td>M-GEX</td><td>Multi GNSS-Experiment</td></tr>
-  <tr><td>MAC</td><td>Master Auxiliary Concept</td></tr>
-  <tr><td>MJD</td><td>Modified Julian Date</td></tr>
-  <tr><td>MSI</td><td>Microsoft Installer, File</td></tr>
-  <tr><td>MSM</td><td>Multiple Signal Messages</td></tr>
-  <tr><td>MW</td><td>Melbourne W&uuml;bbena Linear Combination</td></tr>
-  <tr><td>NAD83</td><td>North American Datum 1983</td></tr>
-  <tr><td>NAREF</td><td>IAG Reference Frame Sub-Commission for North America</td></tr>
-  <tr><td>NMEA</td><td>National Marine Electronics Association Format</td></tr>
-  <tr><td>Ntrip</td><td>Networked Transport of RTCM via Internet Protocol</td></tr>
-  <tr><td>OSM</td><td>OpenStreetMap</td></tr>
-  <tr><td>OSR</td><td>Observation Space Representation</td></tr>
-  <tr><td>PDOP</td><td>Positional Dilution Of Precision</td></tr>
-  <tr><td>PNG</td><td>Portable Network Graphics</td></tr>
-  <tr><td>PPP</td><td>Precise Point Positioning</td></tr>
-  <tr><td>Qt</td><td>Cross-Platform Application Framework</td></tr>
-  <tr><td>REQC</td><td>RINEX Editing and Quality Checking</td></tr>
-  <tr><td>RINEX</td><td>Receiver Independent Exchange Format</td></tr>
-  <tr><td>RTCM SC-104</td><td>Radio Technical Commission for Maritime Services, Special Committee 104</td></tr>
-  <tr><td>RTK</td><td>Real Time Kinematic</td></tr>
-  <tr><td>RTKPLOT</td><td>View and Plot Positioning Solutions Software, Part of RTKLIB</td></tr>
-  <tr><td>RTNET</td><td>Real-Time Network Format</td></tr>
-  <tr><td>RTP</td><td>Real-Time Transport Protocol</td></tr>
-  <tr><td>RTSP</td><td>Real-Time Streaming Protocol</td></tr>
-  <tr><td>SBAS</td><td>Space Based Augmentation System</td></tr>
-  <tr><td>SINEX TRO</td><td>Troposphere Solution Independent Exchange Format</td></tr>
-  <tr><td>SINEX</td><td>Solution Independent Exchange Format</td></tr>
-  <tr><td>SIRGAS2000</td><td>Geodetic Datum for Latin America and Caribbean 2000</td></tr>
-  <tr><td>SIRGAS</td><td>IAG Reference Frame Sub-Commission for Latin America and Caribbean</td></tr>
-  <tr><td>SP3</td><td>Standard Product # 3</td></tr>
-  <tr><td>SPP</td><td>Single Point Positioning</td></tr>
-  <tr><td>SSL</td><td>Secure Sockets Layer</td></tr>
-  <tr><td>SSR</td><td>State Space Representation</td></tr>
-  <tr><td>SVN</td><td>Subversion, Revision Control System</td></tr>
-  <tr><td>TCP</td><td>Transmission Control Protocol</td></tr>
-  <tr><td>TEQC</td><td>Translation, Editing and Quality Checking</td></tr>
-  <tr><td>TLS</td><td>Transport Layer Security</td></tr>
-  <tr><td>UDP</td><td>User Datagram Protocol</td></tr>
-  <tr><td>UMTS</td><td>Universal Mobile Telecommunications System</td></tr>
-  <tr><td>URA</td><td>User Range Accuracy</td></tr>
-  <tr><td>VRS</td><td>Virtual Reference Station</td></tr>
-  <tr><td>VTEC</td><td>Vertical Total Electron Content</td></tr>
-</table>
+    <p>
+    <h4 id="links">3.3 Further Reading</h3>
+      </p>
+
+      <b>Links:</b><br>
+      <table>
+        <tr>
+          <td>Ntrip &nbsp;</td>
+          <td><a href="https://igs.bkg.bund.de/ntrip/index" target="_blank">https://igs.bkg.bund.de/ntrip/index</a></td>
+        </tr>
+        <tr>
+          <td>IGS Real-Rime Service (RTS) &nbsp;</td>
+          <td><a href="https://igs.org/rts/" target="_blank">https://igs.org/rts/</a></td>
+        </tr>
+        <tr>
+          <td>Ntrip Broadcaster overview &nbsp;</td>
+          <td><a href="https://rtcm-ntrip.org/home" target="_blank">https://rtcm-ntrip.org/home</a></td>
+        </tr>
+        <tr>
+          <td>Ntrip Open Source software code &nbsp;</td>
+          <td><a href="https://software.rtcm-ntrip.org" target="_blank">https://software.rtcm-ntrip.org</a></td>
+        </tr>
+        <tr>
+          <td>Radio Technical Commission for Maritime Services &nbsp;</td>
+          <td><a href="https://www.rtcm.org/" target="_blank">https://www.rtcm.org/</a></td>
+        </tr>
+      </table>
+      <br>
+
+      <b>Publications:</b><br>
+      <table border="1">
+        <tr>
+          <td>Caissy, M., L. Agrotis, G. Weber, M. Hernandez-Pajares and U. Hugentobler (2012)</td>
+          <td>The International GNSS Real-Time Service. GPS World, June 1, 2012.</td>
+        </tr>
+
+        <tr>
+          <td>Estey, L. H. and C. M. Meertens (1999)</td>
+          <td>TEQC: The Multi-Purpose Toolkit for GPS/GLONASS Data. GPS Solutions, Vol. 3, No. 1, pp. 42-49, 1999.</td>
+        </tr>
+
+        <tr>
+          <td>Huisman, L., P. Teunissen and C. Hu (2012)</td>
+          <td>GNSS Precise Point Positioning in Regional Reference Frames Using Real-time Broadcast Corrections. Journal
+            of Applied Geodesy, Vol. 6, pp15-23, 2012.</td>
+        </tr>
+
+        <tr>
+          <td>Mervart, L., Z. Lukes, C. Rocken and T. Iwabuchi (2008)</td>
+          <td>Precise Point Positioning With Ambiguity Resolution in Real-Time. ION GNSS 2008.</td>
+        </tr>
+
+        <tr>
+          <td>RTCM SC-104 (2011)</td>
+          <td>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.</td>
+        </tr>
+
+        <tr>
+          <td>Rupprecht, W. (2000)</td>
+          <td>DGPS-IP. <u>http://www.wsrcc.com/wolfgang/gps/dgps-ip.html</u>, 2000.</td>
+        </tr>
+
+        <tr>
+          <td>St&uuml;rze, A., L. Mervart, W. Söhne, G. Weber, G. Wübbena (2012)</td>
+          <td>Real-Time PPP using open CORS Networks and RTCM Standards. 3rd International Conference on Machine Control
+            & Guidance, March 27-29, 2012 </td>
+        </tr>
+
+        <tr>
+          <td>Weber, G., D. Dettmering and H. Gebhard (2005a)</td>
+          <td>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.</td>
+        </tr>
+
+        <tr>
+          <td>Weber, G., D. Dettmering, H. Gebhard and R. Kalafus (2005b)</td>
+          <td>Networked Transport of RTCM via Internet Protocol (Ntrip), IP-Streaming for Real-Time GNSS Applications.
+            ION GNSS 2005.</td>
+        </tr>
+
+        <tr>
+          <td>Weber, G., and M. Honkala (2004)</td>
+          <td>The future is talking Ntrip. Newsletter, Trimble GmbH Raunheim, Germany, 2004.</td>
+        </tr>
+
+        <tr>
+          <td>Weber, G. and L. Mervart (2009)</td>
+          <td>The BKG Ntrip Client (BNC), Report on EUREF Symposium 2007 in London. Mitteilungen des Bundesamtes fuer
+            Kartographie und Geodaesie, Band 42, Frankfurt, 2009.</td>
+        </tr>
+
+        <tr>
+          <td>Weber, G. and L. Mervart (2010)</td>
+          <td>Real-time Combination of GNSS Orbit and Clock Correction Streams Using a Kalman Filter Approach. ION GNSS
+            2010.</td>
+        </tr>
+
+        <tr>
+          <td>Weber, G, L. Mervart, Z. Lukes, C. Rocken and J. Dousa (2007)</td>
+          <td>Real-time Clock and Orbit Corrections for Improved Point Positioning via Ntrip. ION GNSS 2007.</td>
+        </tr>
+
+        <tr>
+          <td>Weber, G., L. Mervart, A. St&uuml;rze, A. R&uuml;lke and D. St&ouml;cker (2016)</td>
+          <td>BKG Ntrip Client, Version 2.12. Mitteilungen des Bundesamtes f&uuml;r Kartographie und Geod&auml;sie, Vol.
+            49, Frankfurt am Main, 2016.</td>
+        <tr>
+      </table>
+
+      <p>
+      <h4 id="abbrev">3.4 Abbreviations</h3>
+        </p>
+        <table>
+          <tr>
+            <td>AC</td>
+            <td>Analysis Center</td>
+          </tr>
+          <tr>
+            <td>AFREF</td>
+            <td>IAG Reference Frame Sub-Commission for Africa</td>
+          </tr>
+          <tr>
+            <td>ANTEX</td>
+            <td>Antenna Exchange Format</td>
+          </tr>
+          <tr>
+            <td>APC</td>
+            <td>Antenna Phase Center</td>
+          </tr>
+          <tr>
+            <td>APREF</td>
+            <td>IAG Reference Frame Sub-Commission for Asia and Pacific</td>
+          </tr>
+          <tr>
+            <td>ARP</td>
+            <td>Antenna Reference Point</td>
+          </tr>
+          <tr>
+            <td>BKG</td>
+            <td>Bundesamt f&uuml;r Kartographie und Geod&auml;sie</td>
+          </tr>
+          <tr>
+            <td>BNC</td>
+            <td>BNK Ntrip Client</td>
+          </tr>
+          <tr>
+            <td>BSW</td>
+            <td>Bernese GNSS Software</td>
+          </tr>
+          <tr>
+            <td>CC</td>
+            <td>Combination Center</td>
+          </tr>
+          <tr>
+            <td>CLI</td>
+            <td>Command Line Interface</td>
+          </tr>
+          <tr>
+            <td>CoM</td>
+            <td>Center Of Mass</td>
+          </tr>
+          <tr>
+            <td>DGNSS</td>
+            <td>Differential GNSS</td>
+          </tr>
+          <tr>
+            <td>DGPS-IP</td>
+            <td>Differential GPS via Internet Protocol</td>
+          </tr>
+          <tr>
+            <td>DMG</td>
+            <td>Disk Image, File</td>
+          </tr>
+          <tr>
+            <td>DREF91</td>
+            <td>Geodetic Datum for Germany 1991</td>
+          </tr>
+          <tr>
+            <td>ECEF</td>
+            <td>Earth-Centred-Earth-Fixed</td>
+          </tr>
+          <tr>
+            <td>EDGE</td>
+            <td>Enhanced Data Rates for GSM Evolution</td>
+          </tr>
+          <tr>
+            <td>ETRF2000</td>
+            <td>European Terrestrial Reference Frame 2000</td>
+          </tr>
+          <tr>
+            <td>EUREF</td>
+            <td>IAG Reference Frame Sub-Commission for Europe</td>
+          </tr>
+          <tr>
+            <td>EoE</td>
+            <td>End of Epoch</td>
+          </tr>
+          <tr>
+            <td>FKP</td>
+            <td>Fl&auml;chen-Korrektur-Parameter</td>
+          </tr>
+          <tr>
+            <td>FTP</td>
+            <td>File Transfer Protocol</td>
+          </tr>
+          <tr>
+            <td>GDA2020</td>
+            <td>Geodetic Datum Australia 2020</td>
+          </tr>
+          <tr>
+            <td>GNSS</td>
+            <td>Global Navigation Satellite System</td>
+          </tr>
+          <tr>
+            <td>GNU</td>
+            <td>GNU's Not Unix</td>
+          </tr>
+          <tr>
+            <td>GPL</td>
+            <td>General Public License</td>
+          </tr>
+          <tr>
+            <td>GPRS</td>
+            <td>General Packet Radio Service</td>
+          </tr>
+          <tr>
+            <td>GPSWD</td>
+            <td>GPS Week and Day</td>
+          </tr>
+          <tr>
+            <td>GSM</td>
+            <td>Global System for Mobile Communications</td>
+          </tr>
+          <tr>
+            <td>GUI</td>
+            <td>Graphical User Interface</td>
+          </tr>
+          <tr>
+            <td>HP MSM</td>
+            <td>High Precision Multiple Signal Messages</td>
+          </tr>
+          <tr>
+            <td>HR URA</td>
+            <td>High Rate User Range Accuracy</td>
+          </tr>
+          <tr>
+            <td>HTTP</td>
+            <td>Hypertext Transfer Protocol</td>
+          </tr>
+          <tr>
+            <td>HTTPS</td>
+            <td>Hypertext Transfer Protocol Secure</td>
+          </tr>
+          <tr>
+            <td>IAG</td>
+            <td>International Association of Geodesy</td>
+          </tr>
+          <tr>
+            <td>ICECAST</td>
+            <td>Streaming Media Server</td>
+          </tr>
+          <tr>
+            <td>IGS20</td>
+            <td>IGS Reference Frame 2020</td>
+          </tr>
+          <tr>
+            <td>IGS</td>
+            <td>International GNSS Service</td>
+          </tr>
+          <tr>
+            <td>IOD</td>
+            <td>Issue of Data</td>
+          </tr>
+          <tr>
+            <td>IP</td>
+            <td>Internet Protocol</td>
+          </tr>
+          <tr>
+            <td>ITRF2020</td>
+            <td>International Terrestrial Reference Frame 2020</td>
+          </tr>
+          <tr>
+            <td>L3</td>
+            <td>Ionosphere-Free Linear Combination Of Phase Observations</td>
+          </tr>
+          <tr>
+            <td>LAN</td>
+            <td>Local Area Network</td>
+          </tr>
+          <tr>
+            <td>LC</td>
+            <td>Linea Combination</td>
+          </tr>
+          <tr>
+            <td>M-GEX</td>
+            <td>Multi GNSS-Experiment</td>
+          </tr>
+          <tr>
+            <td>MAC</td>
+            <td>Master Auxiliary Concept</td>
+          </tr>
+          <tr>
+            <td>MJD</td>
+            <td>Modified Julian Date</td>
+          </tr>
+          <tr>
+            <td>MSI</td>
+            <td>Microsoft Installer, File</td>
+          </tr>
+          <tr>
+            <td>MSM</td>
+            <td>Multiple Signal Messages</td>
+          </tr>
+          <tr>
+            <td>MW</td>
+            <td>Melbourne W&uuml;bbena Linear Combination</td>
+          </tr>
+          <tr>
+            <td>NAD83</td>
+            <td>North American Datum 1983</td>
+          </tr>
+          <tr>
+            <td>NAREF</td>
+            <td>IAG Reference Frame Sub-Commission for North America</td>
+          </tr>
+          <tr>
+            <td>NMEA</td>
+            <td>National Marine Electronics Association Format</td>
+          </tr>
+          <tr>
+            <td>Ntrip</td>
+            <td>Networked Transport of RTCM via Internet Protocol</td>
+          </tr>
+          <tr>
+            <td>OSM</td>
+            <td>OpenStreetMap</td>
+          </tr>
+          <tr>
+            <td>OSR</td>
+            <td>Observation Space Representation</td>
+          </tr>
+          <tr>
+            <td>PDOP</td>
+            <td>Positional Dilution Of Precision</td>
+          </tr>
+          <tr>
+            <td>PNG</td>
+            <td>Portable Network Graphics</td>
+          </tr>
+          <tr>
+            <td>PPP</td>
+            <td>Precise Point Positioning</td>
+          </tr>
+          <tr>
+            <td>Qt</td>
+            <td>Cross-Platform Application Framework</td>
+          </tr>
+          <tr>
+            <td>REQC</td>
+            <td>RINEX Editing and Quality Checking</td>
+          </tr>
+          <tr>
+            <td>RINEX</td>
+            <td>Receiver Independent Exchange Format</td>
+          </tr>
+          <tr>
+            <td>RTCM SC-104</td>
+            <td>Radio Technical Commission for Maritime Services, Special Committee 104</td>
+          </tr>
+          <tr>
+            <td>RTK</td>
+            <td>Real Time Kinematic</td>
+          </tr>
+          <tr>
+            <td>RTKPLOT</td>
+            <td>View and Plot Positioning Solutions Software, Part of RTKLIB</td>
+          </tr>
+          <tr>
+            <td>RTNET</td>
+            <td>Real-Time Network Format</td>
+          </tr>
+          <tr>
+            <td>RTP</td>
+            <td>Real-Time Transport Protocol</td>
+          </tr>
+          <tr>
+            <td>RTSP</td>
+            <td>Real-Time Streaming Protocol</td>
+          </tr>
+          <tr>
+            <td>SBAS</td>
+            <td>Space Based Augmentation System</td>
+          </tr>
+          <tr>
+            <td>SINEX TRO</td>
+            <td>Troposphere Solution Independent Exchange Format</td>
+          </tr>
+          <tr>
+            <td>SINEX</td>
+            <td>Solution Independent Exchange Format</td>
+          </tr>
+          <tr>
+            <td>SIRGAS2000</td>
+            <td>Geodetic Datum for Latin America and Caribbean 2000</td>
+          </tr>
+          <tr>
+            <td>SIRGAS</td>
+            <td>IAG Reference Frame Sub-Commission for Latin America and Caribbean</td>
+          </tr>
+          <tr>
+            <td>SP3</td>
+            <td>Standard Product # 3</td>
+          </tr>
+          <tr>
+            <td>SPP</td>
+            <td>Single Point Positioning</td>
+          </tr>
+          <tr>
+            <td>SSL</td>
+            <td>Secure Sockets Layer</td>
+          </tr>
+          <tr>
+            <td>SSR</td>
+            <td>State Space Representation</td>
+          </tr>
+          <tr>
+            <td>SVN</td>
+            <td>Subversion, Revision Control System</td>
+          </tr>
+          <tr>
+            <td>TCP</td>
+            <td>Transmission Control Protocol</td>
+          </tr>
+          <tr>
+            <td>TEQC</td>
+            <td>Translation, Editing and Quality Checking</td>
+          </tr>
+          <tr>
+            <td>TLS</td>
+            <td>Transport Layer Security</td>
+          </tr>
+          <tr>
+            <td>UDP</td>
+            <td>User Datagram Protocol</td>
+          </tr>
+          <tr>
+            <td>UMTS</td>
+            <td>Universal Mobile Telecommunications System</td>
+          </tr>
+          <tr>
+            <td>URA</td>
+            <td>User Range Accuracy</td>
+          </tr>
+          <tr>
+            <td>VRS</td>
+            <td>Virtual Reference Station</td>
+          </tr>
+          <tr>
+            <td>VTEC</td>
+            <td>Vertical Total Electron Content</td>
+          </tr>
+        </table>
 
 </body>
+
 </html>
Index: trunk/BNC/src/bncutils.cpp
===================================================================
--- trunk/BNC/src/bncutils.cpp	(revision 11018)
+++ trunk/BNC/src/bncutils.cpp	(revision 11019)
@@ -203,4 +203,17 @@
 //
 ////////////////////////////////////////////////////////////////////////////
+double decimalYear(const bncTime& time) {
+
+  unsigned int year, month, day;
+  time.civil_date(year, month, day);
+
+  bncTime jan1;
+  jan1.set(int(year), 1, 1, 0, 0, 0.0);
+
+  return year + (time.mjddec() - jan1.mjddec()) / 365.25;
+}
+
+//
+////////////////////////////////////////////////////////////////////////////
 void currentGPSWeeks(int& week, double& sec) {
 
Index: trunk/BNC/src/bncutils.h
===================================================================
--- trunk/BNC/src/bncutils.h	(revision 11018)
+++ trunk/BNC/src/bncutils.h	(revision 11019)
@@ -71,4 +71,5 @@
 
 void         currentGPSWeeks(int& week, double& sec);
+double       decimalYear(const bncTime& time);
 
 QDateTime    currentDateAndTimeGPS();
Index: trunk/BNC/src/pppCrdFile.cpp
===================================================================
--- trunk/BNC/src/pppCrdFile.cpp	(revision 11018)
+++ trunk/BNC/src/pppCrdFile.cpp	(revision 11019)
@@ -40,4 +40,5 @@
  * -----------------------------------------------------------------------*/
 
+#include <cstdlib>
 #include <fstream>
 #include <sstream>
@@ -82,4 +83,30 @@
     in >> staInfo._xyz(1) >> staInfo._xyz(2) >> staInfo._xyz(3);
 
+    // Optional 'EPOCH:<decimalYear>' and 'VEL:<vx>,<vy>,<vz>' keyword tokens
+    // (ITRF reference epoch and velocity in m/year of the coordinate above),
+    // may appear in any order before the antenna eccentricity / name fields.
+    while (!in.eof()) {
+      streampos posBeforeToken = in.tellg();
+      string token;
+      if (!(in >> token)) {
+        break;
+      }
+      if (token.compare(0, 6, "EPOCH:") == 0) {
+        staInfo._epoch = atof(token.substr(6).c_str());
+      }
+      else if (token.compare(0, 4, "VEL:") == 0) {
+        string velStr = token.substr(4);
+        for (string::iterator it = velStr.begin(); it != velStr.end(); ++it) {
+          if (*it == ',') *it = ' ';
+        }
+        istringstream velIn(velStr);
+        velIn >> staInfo._velocity(1) >> staInfo._velocity(2) >> staInfo._velocity(3);
+      }
+      else {
+        in.seekg(posBeforeToken);
+        break;
+      }
+    }
+
     if (!in.eof()) {
       in >> staInfo._neuAnt(1) >> staInfo._neuAnt(2) >> staInfo._neuAnt(3);
Index: trunk/BNC/src/pppCrdFile.h
===================================================================
--- trunk/BNC/src/pppCrdFile.h	(revision 11018)
+++ trunk/BNC/src/pppCrdFile.h	(revision 11019)
@@ -13,6 +13,8 @@
    public:
     t_staInfo() {
-      _xyz.ReSize(3);    _xyz    = 0.0;
-      _neuAnt.ReSize(3); _neuAnt = 0.0;
+      _xyz.ReSize(3);      _xyz      = 0.0;
+      _neuAnt.ReSize(3);   _neuAnt   = 0.0;
+      _velocity.ReSize(3); _velocity = 0.0;
+      _epoch = 0.0;
     }
     std::string  _name;
@@ -21,4 +23,6 @@
     ColumnVector _xyz;
     ColumnVector _neuAnt;
+    ColumnVector _velocity; // ITRF velocity Vx, Vy, Vz [m/year], zero if unused
+    double       _epoch;    // reference (decimal year) epoch of _xyz, zero if unused
   };
 
Index: trunk/BNC/src/pppMain.cpp
===================================================================
--- trunk/BNC/src/pppMain.cpp	(revision 11018)
+++ trunk/BNC/src/pppMain.cpp	(revision 11019)
@@ -238,4 +238,8 @@
           opt->_neuEccRover[1] = staInfo._neuAnt[1];
           opt->_neuEccRover[2] = staInfo._neuAnt[2];
+          opt->_velRover[0]    = staInfo._velocity[0];
+          opt->_velRover[1]    = staInfo._velocity[1];
+          opt->_velRover[2]    = staInfo._velocity[2];
+          opt->_refEpochRover  = staInfo._epoch;
           opt->_antNameRover   = staInfo._antenna;
           opt->_recNameRover   = staInfo._receiver;
Index: trunk/BNC/src/pppOptions.cpp
===================================================================
--- trunk/BNC/src/pppOptions.cpp	(revision 11018)
+++ trunk/BNC/src/pppOptions.cpp	(revision 11019)
@@ -52,4 +52,6 @@
   _xyzAprRover.ReSize(3); _xyzAprRover = 0.0;
   _neuEccRover.ReSize(3); _neuEccRover = 0.0;
+  _velRover.ReSize(3);    _velRover    = 0.0;
+  _refEpochRover = 0.0;
   _aprSigCrd.ReSize(3);   _aprSigCrd   = 0.0;
   _noiseCrd.ReSize(3);    _noiseCrd    = 0.0;
Index: trunk/BNC/src/pppOptions.h
===================================================================
--- trunk/BNC/src/pppOptions.h	(revision 11018)
+++ trunk/BNC/src/pppOptions.h	(revision 11019)
@@ -76,4 +76,6 @@
   ColumnVector                  _xyzAprRover;
   ColumnVector                  _neuEccRover;
+  ColumnVector                  _velRover;     // ITRF velocity Vx,Vy,Vz [m/year] of _xyzAprRover, zero if unused
+  double                        _refEpochRover; // reference (decimal year) epoch of _xyzAprRover, zero if unused
   std::string                   _recNameRover;
   std::string                   _antNameRover;
