NavCom Rinex Utility Rev C - Manual (Page 11)

RINEX Utility – Rev C
9
9 These conversion options are available:
• User Input: Marker Name, Leap Seconds, and Antenna Height Above Marker
• Options: Marker Position, Output Start / End Times, Antenna Type, Output Interval, and
Ephemeris Output
‡
Refer to the sections below, User Input and Options, for details.
9 If no conversion options are desired, click the Start button to generate the RINEX files.
RINEX File Naming Conventions
RINEX requires the file naming convention to follow a specific format. The easiest way to relate
files is to use the same naming convention for all related files in a given directory and to use
separate directories for files recorded on the same date. The file naming convention is:
9 File names are limited to 8 characters followed by a 3 character extension (MS-DOS
compatible; ssssddd0.yyt)
9 ssss = a unique file identifier. All four characters must be used. If less than 4 characters are
used, enter “_” (underscore) to fill the space. Any alpha-numeric character is acceptable (A-
Z and 0 -9).
‡
If the name of the data file is longer than four characters, it is truncated when the
RINEX files are generated. For example, “cnav8b.DAT” becomes “cnav”.
9
ddd = the Julian date of the year; i.e. March 23, 2007 = Julian date 082
9 0 = required fill character
9 yy = last two digits of the calendar year
9 t = file type; the output files will be tagged as either O for observation or N for navigation, for
example, “cnav0820.07N” and “cnav0820.07O”.