5.4. GNSS Observation Logs Naming Convention
GNSS observation logs provide important metadata for all GNSS observations taken in the field.
GNSS observation logs are required for all project submissions to NGS. NGS provides a sample log that can be downloaded and digitally filled in or you can use your own but, it must include all information as shown in the NGS form. Logs provide critical information for quality assurance and quality control in the field and in the office when uploading data to OPUS Projects. Accurate documentation of field operations/procedures helps ensure a successful outcome with OPUS Projects. GNSS observation logs must be in PDF (*.pdf), Microsoft Word (*.doc), or ASCII (*.txt) format. There are two methods by which logs can be uploaded to OP. Which you use depends on how the information is collected in the field. Regardless of the method used, the logs should be organized before they are uploaded to OP by four-character ID - day of year (preferred) or day of year - four-character ID. Digitally collected field logs must be zipped into one file and uploaded to OP. Hard copies are scanned into one file and uploaded to OP.
GNSS observation log file name should generally match its corresponding RINEX file. As an example, say the RINEX file named g287009q.23o is stored in OP. Then:
g287-009-q-2023.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).
2023 = year (note that log files specify the year as yyyy).