5. Naming Files Correctly for Best Results in OP

Processing a GNSS campaign for submission to NGS requires strict adherence to some file naming conventions. All naming conventions revolve around the assignment of unique four-character IDs to each user mark in your project. Ideally, this assignment is done at the onset of the project (and probably during the project planning stage of the project). That way, photos, GNSS observation logs, and GNSS observation files can be named and labeled according to these IDs. This will reduce confusion for both the user and the NGS project reviewers and will make everything consistent throughout the project. The user may want to check the four-character IDs with the IDs of surrounding CORSs: if the same IDs are used for both, the user may become confused between a user mark and a CORS. However, this will not cause any problems within OP. Note that GNSS observation files are uploaded into the project from the main OPUS home page, while the other file types need to be submitted from within OP.

---

• 5.1. RINEX Files Naming Convention for GNSS Observations
• 5.2. Description Files and Naming Conventions
• 5.3. Photos
• 5.4. GNSS Observation Logs Naming Convention
• 5.5. Naming Problem Examples