5.4. GNSS Observation Logs Naming ConventionΒΆ

  • GNSS observation logs provide important metadata for all GNSS observations taken in the field.

Caution

If continuous GNSS data files are uploaded into your project as observation files, you will not have corresponding field logs, but rather Site Info files, which will need to be uploaded in lieu of field logs.

  • GNSS observation logs document exactly how the GNSS occupation was set up and taken down. These logs include information on equipment, antenna heights, start and stop times, and many other pieces of information critical to proper quality assurance and quality control of a GNSS project. For this reason, they are required for submission of a project to NGS. More information on GNSS observation Logs can be found here. GNSS observation logs have to be in *.pdf or *txt or *.doc

  • GNSS observation log file name should generally match its corresponding RINEX file. As an example, say the RINEX file named g287009q.03o is stored in OP. Then:

  • g287-009-q-2003.pdf should be used for corresponding GNSS observation log PDF file

    • g287 = four-character Mark ID for the observed user mark. In this way, both the GNSS observation files and the GNSS observation logs will start with the same respective Mark ID.

    • 009 = calendar day of the year of the occupation in GNSS Time.

    • q = starting hour of the occupation in GNSS Time where a = 00:00 and x = 23:00 (this is meant to deal with multiple occupations on the same user mark per day; letters identical to how OPUS automatically assigns hours for uploaded RINEX file names).

    • 2003 = year (note that log files specify the year as yyyy).