EasyManua.ls Logo

CHCNAV CHC i83 - OPUS-Projects; OPUS Error Messages and Failures; Interpreting OPUS Results

CHCNAV CHC i83
72 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
CHC i83 User Manual 46
Prior to collecting data for OPUS-RS you can check the latest status map to ensure that OPUS-RS will work. The online
OPUS-RS resource:
http://geodesy.noaa.gov/OPUSI/Plots/Gmap/OPUSRS_sigmap.shtml
is updated routinely and reflects the probability that an occupation at a given location will be successful and predicts a
best-case accuracy for a 15-minute or 1-hour occupation.
In remote areas there is a risk that if a single CORS site is unavailable, your OPUS-RS job will not be processed.
25% of all submitted OPUS-RS occupations fail. Please read the “Best OPUS Practices for New and Experienced Users”
section of this User Manual on page 49. It will save you time and failed jobs.
OPUS-Projects
OPUS Projects is a relatively new online tool. Its use requires taking a NGS training class. OPUS-Projects will allow you to
combine the observation files from multiple receivers and multiple sessions.
There is an excellent article and video describing OPUS Projects in the October 2013 ‘American Surveyor’ magazine.
Search for OPUS-Projects: The Next Revolution in GPS” to find a full resolution PDF.
OPUS Error Messages and Failures
There are lots of possible error messages when processing OPUS solutions. It is our experience that almost all errors fall
into a single category:
“There is not enough nearby CORS data to effectively process your occupation…
yet
.”
In general, the resolution is nearly always the same:
“Wait until more data becomes available and resubmit your job.”
If you are processing OPUS-RS jobs in an area with very few CORS stations, and one CORS station was offline, waiting
may not help as more data may never become available. OPUS-Static is the solution for locations where OPUS-RS is not
dependable.
Interpreting OPUS Results
When you receive an OPUS solution by email from the NGS if formatted using a fixed space font it will look like this:
USER: testbench@igage.com DATE: May 06, 2014
RINEX FILE: p4490900.14o TIME: 16:08:35 UTC
SOFTWARE: page5 1209.04 master93.pl 022814
START: 2014/03/31 00:00:00
EPHEMERIS: igs17861.eph [precise] STOP: 2014/03/31 23:59:00
NAV FILE: brdc0900.14n OBS USED: 45735 / 47174 :97%
ANT NAME: TRM29659.00 SCIT
# FIXED AMB: 162 / 171 :95%
ARP HEIGHT: 0.0083 OVERALL RMS: 0.011(m)
REF FRAME: NAD_83(2011)(EPOCH:2010.0000)
IGS08(EPOCH:2014.2452)
X: -2184137.494(m) 0.003(m) -2184138.362(m) 0.003(m)
Y: -3839941.381(m) 0.001(m) -3839940.177(m) 0.001(m)
Z: 4585410.516(m) 0.005(m) 4585410.529(m) 0.005(m)
LAT: 46 15 35.23578 0.005(m) 46 15 35.25052 0.005(m)

Table of Contents

Related product manuals