-BNC lets you introduce RINEX header skeleton files that contain the header records you would like to see instead of a default header. You may like to derive RINEX skeleton files from the information given in sitelogs. A file in the 'RINEX directory' with the 'RINEX skeleton extension' is interpreted by BNC as a RINEX header skeleton file for the affected stream. -
--Example: RINEX files for mountpoints WETTZELL, FRANKFURT and FRANCE (same 4Char Station ID), BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net (same 4Char Station ID, identical mountpoint stings) would accept skeleton files named
+BNC retrieves information needed for RINEX headers from so-called public RINEX header skeleton files as derived from sitelogs. An HTTP link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See http://www.epncb.oma.be:80/stations/log/skl/BRUS.skl for an example for a public RINEX header skeleton file concerning the EPN station Brussels. + ++However, it may happen that public RINEX header skeleton files are not available, its contents is not up to date or you need to have additional/optional records in the RINEX header. For that BNC lets you introduce personal skeleton files that contain the header records you would like to see. You may derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the 'RINEX directory' with the 'RINEX skeleton extension' is interpreted by BNC as a personal RINEX header skeleton file for the affected stream. +
++Example for file name convention: RINEX files for mountpoints WETTZELL, FRANKFURT and FRANCE (same 4Char Station ID), BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net (same 4Char Station ID, identical mountpoint stings) would accept personal skeleton files named
WETT.skl
@@ -258,15 +261,25 @@
-Note the following conditions regarding RINEX header skeleton files: -