-RINEX file names in BNC follow the convention of RINEX Version 2.11. So far BNC does not support extended file names as defined in RINEX Version 3.02. File names are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named
-
-FRAN{ddd}{h}.{yy}O
+The default for RINEX file names in BNC follows the convention of RINEX Version 2. However, the software provides options to alternatively follow the file name convention of RINEX Version 3. RINEX Version 2 file names are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named
+FRAN{ddd}{h}.{yy}O
WETT{ddd}{h}.{yy}O
-
+
where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year.
-If there is more than one stream with identical 4Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX file name. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Observation files are named as
-
-FRAN{ddd}{h}_KFURT.{yy}O
-FRAN{ddd}{h}_CE.{yy}O.
-
-If several streams show exactly the same mountpoint name (example: BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net), BNC adds an integer number to the file name leading i.e. to hourly RINEX Observation files like
-
-BRUS{ddd}{h}_0.{yy}O
-BRUS{ddd}{h}_1.{yy}O.
-
-Note that RINEX file names for all intervals less than 1 hour follow the file name convention for 15 minutes RINEX Observation files i.e.
-+If there is more than one stream with identical 4Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX file name. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Version 2 Observation files are named as
+
+FRAN{ddd}{h}_KFURT.{yy}O
+FRAN{ddd}{h}_CE.{yy}O
+
++If several streams show exactly the same mountpoint name (example: BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net), BNC adds an integer number to the file name leading i.e. to hourly RINEX Version 2 Observation files like
+
+BRUS{ddd}{h}_0.{yy}O
+BRUS{ddd}{h}_1.{yy}O
+
++Note that RINEX Version 2 file names for all intervals less than 1 hour follow the file name convention for 15 minutes RINEX Version 2 Observation files i.e.
+
FRAN{ddd}{h}{mm}.{yy}O
-
+
where 'mm' is the starting minute within the hour.
++In case of RINEX Version 3 file names, the following convention holds: + +
+
| Parameter | # Char. | Meaning |
| Name | 9 | Site, station and country code |
| S | 1 | Data source |
| Start Time | 11 | YYYYDDDHHMM |
| Period | 3 | File period |
| Obs. Freq. | 3 | Observation frequency |
| Content | 2 | Content type |
| Format | 3 | File format |
| Compression | 2-3 | Compression method (optional) |
+Example for Mixed RINEX Version 3 GNSS observation file name, file containing 1 hour of data, one observation every second, 'MO' standing for 'Mixed Observations': +
+ALGO00CAN_R_20121601000_01H_01S_MO.rnx ++ +
+Note that file name details are produced from the streams mountpoint as well as corresponding BNC settings and meta data from the Ntrip Broadcaster source-table. +
+@@ -802,5 +831,5 @@
3.4.5 Skeleton Extension - optional
-Whenever BNC starts generating 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. A HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See http://www.epncb.oma.be:80/stations/log/skl/brus.skl for an example of a public RINEX header skeleton file for EPN station Brussels. Note that the download of RINEX skeleton files from HTTPS websites requires the exchange of client and/or server certificates. Clarify 'SSL' options offered in panel 'Network' for details. +Whenever BNC starts generating 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. A HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See http://www.epncb.oma.be:80/stations/log/skl/brus.skl for an example of a public RINEX header skeleton file for EPN station Brussels. Note that the download of RINEX skeleton files from HTTPS websites requires the exchange of client and/or server certificates. Clarify 'SSL' options offered through panel 'Network' for details.
@@ -808,11 +837,11 @@
-Examples for personal skeleton file name convention: RINEX Observation 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
-FRAN_KFURT.skl
-FRAN_CE.skl
-BRUS_0.skl
-BRUS_1.skl
+BRUS.skl +FRAN.skl +WETT.skl +
if 'Skeleton extension' is set to 'skl'.
@@ -835,5 +864,5 @@
- ANTENNA: DELTA H/E/N
- WAVELENGTH FACT L1/2 (RINEX Version 2)
-
- SYS / # / OBS TYPES (RINEX Version 3, will be ignored when writing Version 2 files)
+
- SYS / # / OBS TYPES (for RINEX Version 3 files, will be ignored when writing Version 2 files)
3.4.10 Version 3 File Names - optional
+Tick check box 'Version 3 file names' to let BNC create so-called extended file names following the RINEX Version 3 standard. +
+Default is an empty check box, meaning to still use file names following the RINEX Version 2 standard although the file contents is saved in RINEX Version 3 format. +
+-Broadcast Ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3 e.g. as message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (tentative, BDS/BeiDou). The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'BRDC' and the last character is -
-+For RINEX Version 2 Navigation files the last character is 'N' or 'G' for GPS or GLONASS ephemeris in two separate files. +
++Regarding RINEX Version 3 you will find all ephemeris data for GPS, GLONASS, Galileo, SBAS, QZSS, and BDS saved together in one Navigation file. +
++The following is an example for a RINEX Version 3 Navigation file name. The file contains one days data. 'MN' stands for 'Multi Constellation Navigation' data. +
+BRDC00DEU_S_20121600000_01D_MN.rnx ++
@@ -964,4 +1008,11 @@
Note that this does not concern the Broadcast Ephemeris output through IP port which is always in RINEX Version 3 format. +
+ +3.5.5 Version 3 File Names - optional
+Tick check box 'Version 3 file names' to let BNC create so-called extended file names following the RINEX Version 3 standard. +
+Default is an empty check box, meaning to still use file names following the RINEX Version 2 standard although the file contents is saved in RINEX Version 3 format.