5.5. Naming Problem Examples

  • OPUS takes the first four characters of the uploaded data file (proprietary data file or RINEX file) as the four-character mark ID

  • GNSS receiver manufacturers often use different naming schemes

  • Trimble files (for two different stations) 1A_NBS9_27342580.t01 and 1A_NGP9_47252580.t01 were converted to RINEX files 1A_NBS9_27342580.23o and 1A_NGP9_47252580.23o

  • For 1A_NBS9_27342580.23o we have the following naming convention:

    • 1 = day 1

    • A = session A

    • NBS9 = station

    • 2734 = last four digits of GNSS receiver serial number

    • 258 = calendar day of year

    • 0 = daily data file number (0, 1, 2, 3… consecutively for each GPS day)

  • Attempt to upload two files whose names start with the same four-characters and whose data’s starting hour is n (13) results in the following outcomes:

    • 1A_NBS9_27342580.23o is converted to the RINEX standard name 1a_n258n.23o

    • 1A_NGP9_47252580.23o is converted to the RINEX standard name 1a_n258n.23o

  • Two different Trimble files were converted to the same RINEX standard name!

  • If these two files are uploaded to OP, the first file would create a point marked “1a_n,” but the second file might end up with another user mark called “a001.”

  • If OPUS cannot convert the file to RINEX successfully, an error message will be displayed. You may have to convert the file yourself using software from your receiver vendor.