List of Figures

Frontmatter

  • Fig. 1: OPUS Projects supports the submission of GNSS survey data to NGS for publication on Datasheets

Quick Start Guide

  • Fig. 2: NGS Survey Project Proposal Form

  • Fig. 3: Input screen to create a project in OPUS Projects

  • Fig. 4: Location of the Preferences button on the OP Manager’s Page

  • Fig. 5: OPUS GNSS data file upload page

  • Fig. 6: OPUS single file processing results are available under “Show File” and on the individual user mark page

  • Fig. 7: Add/Delete CORS pop-up window

  • Fig. 8: Location of Upload GNSS Vectors button on the OP Manager’s Page

  • Fig. 9: Upload a photo button on the user mark page

  • Fig. 10: Location of upload descriptions and field log buttons on the OP Manager’s Page

  • Fig. 11: Session processing sequence

  • Fig. 12: Network adjustment window showing sequence of five network adjustments when a NGS Tracking ID is used.

1. Introduction

  • Fig. 1.1: OPUS Projects Create, Session, and Manager access page

  • Fig. 1.2: Conceptual diagram of OPUS Projects workflow

2. NGS Survey Proposal

  • Fig. 2.1: NGS home page showing how to access NGS Survey Project Proposal Form

  • Fig. 2.2: The NGS Survey Project Proposal Form

3. Create Your Project in OP

4. Review and Edit Project Preferences

5. Naming Files Correctly for Best Results in OP

  • Fig. 5.1: RINEX File Header

  • Fig. 5.2: RINEX UTC hour naming convention

  • Fig. 5.3: Example Photos: Close-up, Eye-level and the Horizon

  • Fig. 5.4: Non-NCN CORS Example Photos: Close-up of the antenna serial number, Close-up of the receiver serial number, and the Horizon

6. Loading GNSS Observation Files

  • Fig. 6.1: OPUS processing customization options

  • Fig. 6.2: Project Identifier Option

  • Fig. 6.3: Options Customization Confirmation Report, “Skip Description” National Spatial Reference Network Inclusion or Not

  • Fig. 6.4: Data upload verification email indicating a project preference was not met

  • Fig. 6.5: Rejection of an upload to OPUS providing an explanation of probably cause

  • Fig. 6.6: Show File button to access all solution reports

  • Fig. 6.7: OPUS Solution results

  • Fig. 6.8: Manager’s Page, showing information on data files associated with a user mark

  • Fig. 6.9: Manager’s Page showing “Occupation” information from the “ALL OPUS Results” Report Table

  • Fig. 6.10: Click on a user marks for access to the corresponding Mark page

  • Fig. 6.11: User Mark web page

7. Walking Through OP Visualizations

  • Fig. 7.1: The Project Manager’s web page

  • Fig. 7.2: The Notices banner on the OPUS Projects Manager’s Page

  • Fig. 7.3: Drop-down menu location for displaying results on the Manger’s Page

  • Fig. 7.4: Map zooming toggles

  • Fig. 7.5: Map background options

  • Fig. 7.6: Mark ID shown by hovering over mark

  • Fig. 7.7: Mark data information shown when clicking on a user mark icon

  • Fig. 7.8: CORS ID shown when hovering over a CORS

  • Fig. 7.9: CORS data information shown when clicking on the CORS icon

  • Fig. 7.10: The Controls bar

  • Fig. 7.11: Top page control options

  • Fig. 7.12: Preferences button on the Controls bar

  • Fig. 7.13: Project List button on the Controls bar

  • Fig. 7.14: Solutions button on the Controls bar

  • Fig. 7.15: Manage Solutions pop-up window

  • Fig. 7.16: Add Tracking ID button on the Controls bar

  • Fig. 7.17: Attach NGS Project Tracking ID pop-up window

  • Fig. 7.18: Show File button on the Controls bar

  • Fig. 7.19: Pop-up window showing a sample solution from a processed session

  • Fig. 7.20: Send Email button on the Controls bar

  • Fig. 7.21: Send Email Message pop-up window

  • Fig. 7.22: Upload Description button on the Controls bar

  • Fig. 7.23: Choose WinDesc Description Files for loading into project (pop-up window)

  • Fig. 7.24: Upload Field Logs button on the Controls bar

  • Fig. 7.25: Choose Field Log to upload pop-up window

  • Fig. 7.26: Refresh PID Information button on the Controls bar

  • Fig. 7.27: Confirmation or Cancel PID Refresh

  • Fig. 7.28: Upload GVX Vectors button on the Controls bar

  • Fig. 7.29: Upload GVX vectors pop-up window

  • Fig. 7.30: Setup Adjustment button on the Controls bar

  • Fig. 7.31: Setup Adjustment Type, Include Available Solutions pop-up window

  • Fig. 7.32: Export Adjustments button on the Controls bar

  • Fig. 7.33: Export adjustments pop-up window

  • Fig. 7.34: Upload Project Report button on the Controls bar

  • Fig. 7.35: Review and Submit to NGS button on the Controls bar

  • Fig. 7.36: Delete Project button on the Controls bar

  • Fig. 7.37: Delete Project confirmation pop-up window

  • Fig. 7.38: MARKS and Sessions Table showing summary occupation data for all sessions

  • Fig. 7.39: Solution Statistics for All Sessions Table that can be displayed on the Manager’s Page

  • Fig. 7.40: Symbology for distinguishing between user marks, CORSs, and baselines

  • Fig. 7.41: Add Marks and Add/Delete CORS buttons on the Manger’s Page

  • Fig. 7.42: Reminder pop-up window for uploading observation files to the project through the OPUS upload page

  • Fig. 7.43: The Add/Del CORS management pop-up window

  • Fig. 7.44: Submitting Comments to & Asking Questions of the OPUS team

  • Fig. 7.45: Restricted access to session processing

  • Fig. 7.46: Sessions Page prior to session processing

  • Fig. 7.47: Solution Quality Indicators

  • Fig. 7.48: Session solution quality indicators showing a threshold exceeded

  • Fig. 7.49: Data Availability table

  • Fig. 7.50: The Set up Processing button on the Session page Controls bar

  • Fig. 7.51: Accessing a mark page from the Manager’s Page

  • Fig. 7.52: Example mark page

  • Fig. 7.53: Mark page toggling from the map

  • Fig. 7.54: Mark page zoom controls

  • Fig. 7.55: Datasheet Retrieval by way of a user mark with a PID in the NG database

  • Fig. 7.56: Show File button on the mark page Controls bar

  • Fig. 7.57: OPUS Solution Report for a user mark

  • Fig. 7.58: The Change Mark ID button on the Mark page Controls panel

  • Fig. 7.59: Change Mark ID pop-up window

  • Fig. 7.60: The Remove Mark button on the Mark page Controls bar

  • Fig. 7.61: Confirmation pop-up window for removing a mark from the project

  • Fig. 7.62: Mark Description Summary

  • Fig. 7.63: Upload A Photo button within the mark description summary

  • Fig. 7.64: Upload photos pop-up window

  • Fig. 7.65: Example showing successfully loaded photos on a mark page

  • Fig. 7.66: Save Description button within the mark description summary

  • Fig. 7.67: Occupation information on a mark page

  • Fig. 7.68: Manage Data Files button on the mark occupations table

  • Fig. 7.69: Manage a mark’s data file pop-up window

  • Fig. 7.70: Save Occupations button on the mark occupations table

  • Fig. 7.71: Manage Coordinates button on the mark processing results table

  • Fig. 7.72: Manage a mark’s coordinate pop-up window showing coordinates, reference frame, and assumed errors (sigmas)

  • Fig. 7.73: An example of the NEU scatter plots, visualizing the processing results of mark “bcc1”.

  • Fig. 7.74: Details about processing results, at 1x uncertainty and referenced to the “zero” point coordinates

  • Fig. 7.75: Clicking on a mark icon on the map allows viewing of static GNSS and/or GVX observations at that mark

  • Fig. 7.76: A list of GVX vectors associated with baseline e087-mas2 baseline is shown here when clicking anywhere on the baseline displaying on the map.

  • Fig. 7.77: Choosing Occupations From ALL SESSIONS will show uploaded GVX observation files (if available) for involved marks.

  • Fig. 7.78: A list of available GNSS Vectors (GVX) files (first row) and their occupied baselines (the first and the last columns)

  • Fig. 7.79: Statistics of GVX baselines

  • Fig. 7.80: A Mark Page of a GVX terminal point.

  • Fig. 7.81: An example of the scatter plots of a GVX Mark webpage

  • Fig. 7.82: GVX vector component table

  • Fig. 7.83: An example showing part of a GVX File Summary Page

  • Fig. 7.84: A portion of a GVX Baseline Summary Page

  • Fig. 7.85: An example of the baseline solution plots that aid in visualizing the spread between repeat vectors of the same baseline

8. Selecting CORS

  • Fig. 8.1: Add/Delete CORS button on the project map

  • Fig. 8.2: Add/Delete CORS pop-up window

  • Fig. 8.3: CORS information bubble on the Add/Delete CORS window

  • Fig. 8.4: List of all CORS included in the project as seen on the Manager’s Page

  • Fig. 8.5: Map of CORS stations on the CORS web page, showing a 250 km radius around a selected location

  • Fig. 8.6: Example of a spreadsheet used to help select the best CORSs for a project

  • Fig. 8.7: Data availability for the CORS “GODE” in early April 2021

  • Fig. 8.8: Data availability for a CORS not in the NOAA CORS network will appear blank

  • Fig. 8.9: Example coordinates page for the CORS LOY8 showing computed velocities

  • Fig. 8.10: Example of a CORS coordinates page showing reference to the CORS monument

  • Fig. 8.11: Example of a CORS position referencing the monument

  • Fig. 8.12: Example of a CORS position referencing the Antenna Reference Point (ARP)

  • Fig. 8.13: CORS network accuracy shown on the station’s datasheet

  • Fig. 8.14: Example of CORSs plotted with respect to a 250 km radius from the centroid of the project

  • Fig. 8.15: CORS map showing CORSs plotted with respect to a 250 km radius from the centroid of the project

  • Fig. 8.16: Example of a CORS short-term plot showing both bias and random error

  • Fig. 8.17: Example of a short-term CORS plot exhibiting little bias and low error

  • Fig. 8.18: Screen captures showing the steps used in adding a CORS from the Manager’s Page (see Section 7.1.7)

9. Upload GVX Vectors

  • Fig. 9.1: Upload GVX Vectors button from the Manager’s Page

  • Fig. 9.2: Upload GVX Vectors pop-up window that allows you to browse for .gvx files on your computer

  • Fig. 9.3: You may batch upload multiple files and then click the “open” button

  • Fig. 9.4: An example of the Upload GVX vector window showing the three selected files and the number of vectors contained in each file. The lower part of the window contains any GVX error messages.

  • Fig. 9.5: Clicking on the “Upload GNSS Vector (.gvx) File” button is the last step you need to perform to add GVX file(s) to your project.

  • Fig. 9.6: Updated Manager’s Page map displaying the newly uploaded GVX/GNSS vectors and highlighting the additional CORS added to the project (station “umbc”).

10. Mark Descriptions

11. Session Processing

  • Fig. 11.1: Accessing the Session Processing Page

  • Fig. 11.2: Example Session processing page

  • Fig. 11.3: Example session processing page noting the one hub constrained 3D under “User” selected network design

  • Fig. 11.4: Map showing an example of the USER/”hub-and-spoke” network design

  • Fig. 11.5: Map showing an example of a “CORS” network design

  • Fig. 11.6: Map showing an example of a “MST” network design

  • Fig. 11.7: The “Perform Processing” button at the top of the Session Processing Page

  • Fig. 11.8: The OP Session Processing confirmation window

  • Fig. 11.9: Manager’s Page showing six successfully processed sessions

  • Fig. 11.10: The seven email attachments (sent to the project manager) resulting from session processing

  • Fig. 11.11: Select “ALL SESSIONS” from the Manger’s Page to reveal the results of any/all session processing

  • Fig. 11.12: Clicking on the session of interest in the “Occupation” table showing “ALL SESSIONS” will open the session page

  • Fig. 11.13: Mark information displayed on at particular session page

  • Fig. 11.14: Session results presented on a Mark page

  • Fig. 11.15: Session Solution Statistics are available from the Manager’s Page

  • Fig. 11.16: Example of session solution statistics

  • Fig. 11.17: The Show File button on the Manager’s Page controls bar

  • Fig. 11.18: Example of a session solution processing report (*.txt file)

  • Fig. 11.19: Example solution statistics for all sessions

12. Network Adjustments

  • Fig. 12.1: Conceptual work flow for running adjustments in OP

  • Fig. 12.2: Set up Adjustment button on the Manager’s Page controls bar

  • Fig. 12.3: Network adjustment windows with NGS Tracking ID and without

  • Fig. 12.4: The Manage Solutions window, enabling the user to rename or delete any solution in the project

  • Fig. 12.5: Conceptual diagram of the relationships between session solutions and network solutions in OP

  • Fig. 12.6: Sample Network Adjustment window showing the OP recommended selections for a Preliminary Adjustment

  • Fig. 12.7: The “Perform Adjustment” button on the network adjustment page

  • Fig. 12.8: Sample network adjustment confirmation pop-up window

  • Fig. 12.9: Sample network solution selected from the individual user mark page

  • Fig. 12.10: Sample network solution processing report showing a “no check” mark

  • Fig. 12.11: The explanation of a solution processing report showing “MARK ESTIMATED - A PRIORI COORDINATE SHIFTS”

  • Fig. 12.12: Network solution processing report showing the coordinates of unconstrained marks

  • Fig. 12.13: Network solution processing report showing coordinates of a constrained mark and the coordinate shifts between computed and published coordinates

  • Fig. 12.14: Sample output from the PREPLT2 file

  • Fig. 12.15: Preliminary Network Adjustment window showing OP recommendation for a single hub 3D constraint

  • Fig. 12.16: Setting up the Horizontal free adjustment with both the Preliminary adjustment results and GVX files.

  • Fig. 12.17: Sample COMPVECS output showing: (1) a rejected vector; (2) a session (0987A) with large residuals; and (3) the large residual in the “Up” direction

  • Fig. 12.18: Example of a histogram plotting the unadjusted vector differences from the COMPVECS output

  • Fig. 12.19: Sample Horizontal Constrained Adjustment window showing 3-D constraints

  • Fig. 12.20: Processing Report from the Horizontal Constrained Adjustment showing the results of the F-Test

  • Fig. 12.21: Constraint Ratio Test as seen in the Processing Report of the Horizontal Constrained Adjustment

  • Fig. 12.22: Network solution processing report from the Horizontal Constrained Adjustment showing “MARK ESTIMATED - HORIZONTAL-FREE ADJUSTMENT COORDINATE SHIFTS”

  • Fig. 12.23: Network solution processing report from the Horizontal Constrained Adjustment showing “MARK ESTIMATED - PUBLISHED HORIZONTAL COORDINATE SHIFTS”

  • Fig. 12.24: Computed - Observed residual values shown in the processing log output for the Horizontal Constrained Adjustment

  • Fig. 12.25: Network accuracies as shown in the Processing Log

  • Fig. 12.26: Sample Vertical Free Adjustment constraint selection

  • Fig. 12.27: Sample Vertical Constrained Adjustment constraint selection

  • Fig. 12.28: Conceptual diagram showing relationship between adjusted heights from three different sources within OPUS Projects: the Horizontal Free Adjustment, the Horizontal Constrained Adjustment, and the published orthometric heights

  • Fig. 12.29: Upload Project Report button on the Controls Bar on the Manager’s Page

  • Fig. 12.30: The Review and Submit to NGS button on the Controls Bar on the Manager’s Page

  • Fig. 12.31: Example of the result of a project check where two items are missing or incomplete

Appendix A

  • Fig. A.1: For submitting a GNSS project to NGS for publication, a complete set of description files are needed. Mark descriptive summary as shown on the Mark Page is not sufficient.

  • Fig. A.2: Home screen WinDesc version 5.03.03, showing the initiation of a new description file

  • Fig. A.3: Sample description file for a fictitious project “GPS1234”

  • Fig. A.4: Accessing Project Data in WinDesc

  • Fig. A.5: Sample WinDesc Project Data screen

  • Fig. A.6: NGS Agency categories drop-down menu

  • Fig. A.7: Accessing the mark Descriptive Data in WinDesc

  • Fig. A.8: Sample mark description for a published mark (information downloaded from the NGS IDB)

  • Fig. A.9: Describe, Non-recover, or Recovery a mark options

  • Fig. A.10: Fully describe, Modify, or Totally re-describe a mark options

  • Fig. A.11: Pop-up window prompting user to import mark descriptive data from an existing mark in the NGS IDB (using the mark’s PID)

  • Fig. A.12: Additional mark attributes imported from the NGS IDB

  • Fig. A.13: Mark recovery information

  • Fig. A.14: Surface Mark Information

  • Fig. A.15: Underground mark information

  • Fig. A.16: Location of the “Position” button on the Description Entry Form

  • Fig. A.17: Mark Position data page

  • Fig. A.18: Click on the [Text} button to add descriptive text to a mark

  • Fig. A.19: New descriptive text associated with a mark recovery

  • Fig. A.20: The WinDesc Spell Check utility

  • Fig. A.21: Example of a misspelled word identified by the WinDesc Spell Check

  • Fig. A.22: Closing the WinDesc Spell Check

  • Fig. A.23: Save any changes made to the mark description

  • Fig. A.24: Original description of a newly set mark in WinDesc

  • Fig. A.25: Special application options for a new survey mark

  • Fig. A.26: Monumentation information for a newly described mark

  • Fig. A.27: Rod/Pipe and Reset information

  • Fig. A.28: Location of the “Position” button on the Description Entry Form

  • Fig. A.29: Mark Position data page

  • Fig. A.30: Click on the [Text} button to add descriptive text to a mark

  • Fig. A.31: Example of new descriptive text in the recommended three-paragraph form

  • Fig. A.32: The [Format] button on the mark descriptive text page

  • Fig. A.33: The WinDesc Spell Check utility

  • Fig. A.34: Example of a misspelled word identified by the WinDesc Spell Check

  • Fig. A.35: Closing the WinDesc Spell Check

  • Fig. A.36: Save any changes made to the mark description

  • Fig. A.37: Sample mark description for Non-NCN CORS station

  • Fig. A.38: Example of new descriptive text in the recommended three-paragraph form for a Non-NCN CORS station

  • Fig. A.39: Three buttons at the bottom of the Description Entry Form enable you to properly edit the three required photos for each mark in the project

  • Fig. A.40: Example showing the creation of a standard label for a survey mark close-up photograph

  • Fig. A.41: Using WinDesc to resize a survey mark photo

  • Fig. A.42: Saving and exiting the WinDesc photo editing window

  • Fig. A.43: The [Save] button at the bottom of the Description Entry Form

  • Fig. A.44: Accessing the “Neighbor for all Marks” check in WinDesc

  • Fig. A.45: Default maximum radius for checking neighboring marks in WinDesc

  • Fig. A.46: Option to include TBMs (Temporary Bench Marks) in the WinDesc neighbor analysis

  • Fig. A.47: The result of a neighbor analysis in WinDesc

  • Fig. A.48: Accessing the Discrepancy analysis in WinDesc

  • Fig. A.49: Sample Discrepancy report showing differences between the description file and information in the NGS IDB

  • Fig. A.50: Exporting the description file

  • Fig. A.51: WinDesc prompts the user to run a final error check after exporting the description file

  • Fig. A.52: Sample error (*.err) file

  • Fig. A.53: How to create the WinDesc index file

  • Fig. A.54: An example of a WinDesc index file showing the SSNs, PIDs, Designations,, coordinates, elevations, and other descriptive information

  • Fig. A.55: How to download network accuracies for all marks whose coordinates in the NGS IDB were based on GNSS observations

  • Fig. A.56: How to view position accuracies on marks in WinDesc

  • Fig. A.57: Network accuracies and correlations for marks in the description file whose positions in the NGS IDB were determined from GNSS observations

Appendix B

  • Fig. B.1: Scenario 1: Three marks observed twice in one day, one mark observed all day long

  • Fig. B.2: Session A, from 6 am to 12:00 noon

  • Fig. B.3: Session B, from 12:00 noon to 6 pm

  • Fig. B.4: Visualization of GNSS occupations with respect to CORSs 24-hour continuous data

  • Fig. B.5: Session A: 6 am to 12:00 noon

  • Fig. B.6: Session B: from 12:00 noon to 6 pm

  • Fig. B.7: Scenario 2: Three marks observed twice in one day, three other marks observed once later in the day, and one mark observed all day

  • Fig. B.8: Session A from Scenario 2

  • Fig. B.9: Session B from Scenario 2

  • Fig. B.10: Scenario 3: One mark observed at four different times in one day

  • Fig. B.11: Scenario 3 Session A

  • Fig. B.12: Scenario 3 Session B

  • Fig. B.13: Scenario 3 Session C

  • Fig. B.14: Scenario 3 Session D

Appendix C

  • Fig. C.1: The Show File selection bar providing access to all processing output

  • Fig. C.2: Table of coordinate shifts resulting from session processing

  • Fig. C.3: Coordinate shifts on a constrained mark shown in the results of session processing

  • Fig. C.4: Coordinate shifts between the Preliminary Network Adjustment and the a priori coordinates

  • Fig. C.5: Coordinate shifts between the Preliminary Network Adjustment and the a prior coordinates on a constrained mark

  • Fig. C.6: Coordinate shifts between the Horizontal Free and the Preliminary Network Adjustments

  • Fig. C.7: Coordinate shifts on a constrained mark shown in the results of the Horizontal Free Network Adjustment

  • Fig. C.8: Coordinate shifts between the Horizontal Constrained and the Horizontal Free Network Adjustments

  • Fig. C.9: Coordinate shifts between the Horizontal Constrained Adjustment and published positions

  • Fig. C.10: Coordinate shifts between the Vertical Free and the Horizontal Constrained Network Adjustments

  • Fig. C.11: Shift in the vertical dimension (orthometric height) shown for the mark held vertically constrained in the Vertical Free Network Adjustment

  • Fig. C.12: Shifts in the horizontal dimension shown for the mark held constrained horizontally in the Vertical Free Network Adjustment

  • Fig. C.13: Coordinate shifts between the Vertical Constrained and Vertical Free Network Adjustments

  • Fig. C.14: Shifts in Orthometric Heights between the Vertical Free and Vertical Constrained Network Adjustments

  • Fig. C.15: Orthometric Height shift for a mark held constrained vertically in the Vertical Constrained Network Adjustment

  • Fig. C.16: Geometric (3D) coordinate shifts for a mark held constrained geometrically in the Vertical Constrained Network Adjustment

Appendix E

  • Fig. E.1: Example using INVERS3D to compare two OPUS solutions from redundant observations

  • Fig. E.2: Example using INVERS3D to compare an initial OPUS solution to the published coordinates

  • Fig. E.3: Two, same-day sessions loaded into OPUS Projects (2020-021A and 2020-021B)

  • Fig. E.4: Coordinate shifts between a priori estimates and OP session processing for session 2020-021-A

  • Fig. E.5: Solution Statistics for all sessions

  • Fig. E.6: Coordinate shifts between a priori estimates and minimally constrained preliminary network adjustment

  • Fig. E.7: Setting up the Horizontal Free network adjustment

  • Fig. E.8: Coordinate shifts between horizontal free and preliminary network adjustments

  • Fig. E.9: Setting up the horizontal constrained network adjustment

  • Fig. E.10: Output from the Processing Report of the Horizontal Constrained network adjustment showing the result of the F-test

  • Fig. E.11: Shifts between Horizontal Constrained and Horizontal Free adjusted coordinates

  • Fig. E.12: Shifts between the Horizontal Constrained adjusted and Published coordinates

  • Fig. E.13: Output from Preplt2 showing the residuals from the Horizontal Constrained adjustment

  • Fig. E.14: Setting up the Vertical Free network adjustment

  • Fig. E.15: Shifts between the Horizontal Constrained and Vertical Free coordinates

  • Fig. E.16: Setting up the Vertical Constrained network adjustment

  • Fig. E.17: Processing Report (*.txt) from Vertical Constrained network adjustment highlighting the result of the F-test

  • Fig. E.18: Shifts between Vertical Free and Vertical Constrained adjusted coordinates

  • Fig. E.19: Shifts between Vertical Constrained and published orthometric heights

Appendix F

  • Fig. F.1: Example project which includes RTN base stations as user marks in OP