OPUS Projects User Guide Logo
v2.0
  • Abstract
  • Revision History
  • Acknowledgements
  • Conventions Used Throughout the Document
  • Disclaimer
  • List of Figures
  • Quick Start Guide
  • 1. Introduction
  • 2. NGS Survey Proposal
  • 3. Create Your Project in OP
  • 4. Review and Edit Project Preferences
  • 5. Naming Files Correctly for Best Results in OP
  • 6. Loading GNSS Observation Files
  • 7. Walking Through OP Visualizations
  • 8. Selecting CORS
  • 9. Upload GVX Vectors
  • 10. Mark Descriptions
  • 11. Session Processing
  • 12. Network Adjustments
    • 12.1. Recommended Network Adjustment Sequence for Alignment with the NSRS
    • 12.2. Recommended Network Adjustment Sequence Without NGS Project Tracking ID
    • 12.3. Verifying Constraints Prior to an Adjustment
    • 12.4. Setting up a Network Adjustment
    • 12.5. Network Adjustment Results
    • 12.6. Analyzing Network Adjustment Results
    • 12.7. Sequential Adjustments with Tracking ID
  • Acronyms and Glossary

Appendices

  • A. WinDesc Module for OPUS Projects
  • B. How OP Arranges GNSS Observations into Sessions
  • C. Coordinates Shifts
  • D. How OP Assigns Sigmas on Constrained Marks
  • E. FAA Airport Surveys
  • F. Tying a Real-Time Network to the NSRS
OPUS Projects User Guide
  • 12. Network Adjustments
  • 12.2. Recommended Network Adjustment Sequence Without NGS Project Tracking ID
  • View page source

12.2. Recommended Network Adjustment Sequence Without NGS Project Tracking ID

There are any number of reasons why a user may opt not to submit a campaign-style GNSS project to NGS. A project may lie outside the United States and its territories; a project may, for scientific reasons, prefer to be tied to the ITRF; alignment to the NSRS reference frame is not wanted; alignment to a local network/datum may be required, etc. Furthermore, GPSCOM attempts to resolve a larger number of error sources than ADJUST. To support the widest possible client base, OP allows users to remain entirely in GPSCOM. Since the project will not be submitted to NGS, there is no need to have users follow the same sequential processing steps as presented in Section 12.1. However, OP will suggest an initial minimally constrained adjustment which is exactly the same as the Preliminary Adjustment shown in Figure 12.1. This will enable the user to evaluate how all sessions fit together without any confounding influence of multiple constraints which may end up being inconsistent. Refer to 12.1 for additional guidance on setting up and analyzing the results from this adjustment. After verifying the correctness of all sessions and observations, the user can then proceed to conduct another (or more) adjustment(s), if needed, with additional constraints. If a user wishes to align the network to a vertical datum in the NSRS, NGS recommends using a project tracking ID (or using the default value of “0000”) and following the sequential adjustments presented in Section 12.1. This will allow running the vertical free and vertical constrained adjustments.


Previous Next

© Copyright Questions or comments, contact the OPUS Projects Team at ngs.opus.projects@noaa.gov.

Built with Sphinx using a theme provided by Read the Docs.