Figure 3: navcom input file naming convention, Table 1: rinex output file naming convention – NavCom Rinex Utility Rev.D User Manual
Page 10
RINEX Utility
– Rev D
9
Table 1: RINEX Output File Naming Convention
File Name
Field
Definition
ssssdddf.yyt
ssss: 4-character station name designator
ddd: Julian date of the year; i.e. March 23, 2007 = Julian date 082
f: file sequence number within day
0: file contains all the existing data of the current day
yy: year
t: file type:
O: Observation file
N: Navigation file
M: Meteorological data file
G: GLONASS Navigation file
H: Geostationary GPS payload nav mess file
B: Geostationary GPS payload broadcast data
C: Clock files (see separate documentation)
If the input files start with the same four characters, the resulting output files will have problems.
For example:
Input file: ANT34_13045.DAT becomes: ANT31841.11O
Input file: ANT35_13045.DAT becomes:
ANT31841.11O.
This will overwrite the previous file
Input file: ANT36_13045.DAT becomes:
ANT31841.11O.
This will overwrite the previous file
This is important because the standard naming convention of internal data logging files on
NavCom products is
“datalog_YYYY_MM_DD_HH_MM.dat”. If the “data” portion of the file
name is not changed when multiple files are selected to process, the result will be that all the
files with the same date information will be over-written with content of the last file processed.
Figure 3: NavCom Input File Naming Convention