Kansas Land Surveyors Conference OPUS, OPUS-RS, and OPUS-DB Dave Zenk NGS Advisor October 29, 2010 Wichita, KS

Kansas Land Surveyors Conference

OPUS, OPUS-RS, and OPUS-DB

Dave ZenkNGS Advisor

October 29, 2010Wichita, KS

What is OPUS?

• OPUS is an acronym for:– Online Positioning User Service (OPUS)

• It started as a service for Static GPS users and has grown from there to serve other users.

• Designed to work with minimal data input from user and be as fully automated as possible.

• Only a Web Browser and Email needed to use.• Fast, easy, consistent access to NSRS.

Many Flavors of OPUS Planned• OPUS-S (static)

» $$$ receiver, hours of data

• OPUS-RS (rapid static)» $$$ receiver, minutesminutes of data

• OPUS-DB (database)» $$$ receiver, hours of data, share resultsshare results

• OPUS-Projects – not released» MultipleMultiple $$$ receivers, share results

• OPUS-GIS – not released» ¢¢ receiver¢¢ receiver, minutes of data

• OPUS-Leveling – not released

OPUS has been popular

OPUS has been popular

Areas covered by OPUS



How does OPUS work?

• Each OPUS ‘flavor’ is a bit different

• Let’s start with OPUS-S

• Then, we’ll highlight the differences in – OPUS-RS – OPUS-DB– OPUS-Projects

OPUS-S

• OPUS-Static, (formerly just called OPUS and sometimes now called OPUS-CLASSIC)

• Basic Steps– Submit GPS data to OPUS Web site– Processed automatically on NGS computers

• Ties to 3 CORS stations– Solution via email - in minutes– Fast, easy, consistent access to NSRS

OPUS Guidelines

• Email address for results• Data file with 2 hrs to 48 hrs of GPS L1/L2 data

– Static GPS observations only– 30-second epochs processed– not approved for less than 2 hrs of data, but you can try

• Antenna type/phase model • Antenna height from mark-to-ARP vertical

OPUS Website (all flavors)• http://www.ngs.noaa.gov/OPUS/

OPUS Screen Layout

e-mail

GPS file

antenna type

antenna height options

OPUS-S(2 hr)

OPUS-RS(15 min)

OPUS Inputs

• Email – [email protected]• GPS file - .dat or Rinex (.obs)

– you may zip several files together – IF they all have same antenna type and antenna height. – Antennas need not be same serial numbers

• Antenna Type – TRM41249.00 (choose from list)• Antenna Ht – vertical measure from mark to ARP• Options – next 2 slides…

OPUS Inputs (OPTIONS 1 & 2)

specifySPCS

specifyCORS

OPUS Inputs (OPTIONS 3, 4, & 5)

Specify GEOID model:AutoGEOID09GEOID03

Choose OUTPUT type

Choose XML or not

OPUS Inputs (OPTIONS 6, 7, & 8)

OPUS-Projects Keyword

Set USER Profile

Choose PUBLISH and Submit

ARP

MARK

Antenna Height•true vertical distance•measured in meters

OPUS Positions

• NGS PAGES processing software

• Ionospheric-free solution

• Tropospheric scale height adjusted

• Fixed ambiguities

• Average of 3 unique CORS ties

• ITRF & NAD83 coordinates/errors

+

CORS A

CORS B

CORS C

Average

OPUS Report

OPUS Report – check results• > 90% observations used• > 50% ambiguities fixed• < 3 cm overall RMS

• < 5 cm peak-to-peak errors

• check antenna info

• check ephemeris type

…and which CORS were used? … resubmit later for better CORS scenario & ephemeris

OPUS Extended Output

• HTDP-transform CORS ITRF coordinates from published epoch to session midpoint

• remote station ITRF solution from each CORS• G-files – vector components, standard

deviations, & correlations for each vector • post-fit RMS & # observations per satellite/vector• solution covariance matrix-relates errors in each

coordinate to every other coordinate• network accuracies - H & V• summary of NAD83 derivation• SPC feet values, if available for user’s state

OPUS-RS (Rapid Static)

• 15-minute sessions minimum, 4 hr maximum• ties to 3 – 9 CORS (< 250km)• uses RSGPS vs. PAGES software• P1/P2 code & L1/L2 phase observations• resolves all ambiguities with LAMBDA• similar to Real-Time Network computations• RSGPS solution modes:

– network: solves ambiguities, tropo, iono– rover: tropo and ion interpolated to rover

• ~10,000 lines of code

OPUS-RS geographical coverage (15 minute session)

• Don’t use OPUS-RS outside areas where insufficient CORS exist.

OPUS-RS geographical coverage (60 minute session)

• Don’t use OPUS-RS outside areas where insufficient CORS exist.

OPUS-RS Output

“#Fixed Ambiguities” replaced by “Quality Indicator”•average of W-ratio (separation between candidate sets of ambiguities) of last 3 epochs•reported as network mode / rover mode•look for values > 3 for confidence in solution

NGS OPUS-RS SOLUTION REPORT USER: [email protected] DATE: October 29, 2007 RINEX FILE: 1207287x.07o TIME: 14:39:04 UTC

SOFTWARE: rsgps 1.09 RS11.prl 1.12 START: 2007/10/14 23:27:15 EPHEMERIS: igr14490.eph [rapid] STOP: 2007/10/15 00:00:15 NAV FILE: brdc2870.07n OBS USED: 1962 / 2082 : 94% ANT NAME: ASH701975.01A QUALITY IND. 34.21/ 37.91ARP HEIGHT: 0.0 NORMALIZED RMS: 0.307

REF FRAME: NAD_83(CORS96)(EPOCH:2002.0000) ITRF00 (EPOCH:2007.78627) LAT: 36 2 52.79767 0.008(m) 36 2 52.81498 0.008(m) E LON: 252 2 18.45532 0.013(m) 252 2 18.41156 0.013(m) W LON: 107 57 41.54468 0.013(m) 107 57 41.58844 0.013(m) EL HGT: 1974.304(m) 0.005(m) 1973.396(m) 0.005(m) ORTHO HGT: 1995.280(m) 0.026(m) [Geoid03 NAVD88]

*

OPUS-RS Output

“Overall RMS” replaced by “Normalized RMS”•unitless quantity, “expected” = 1•aka standard deviation of unit weight•if > 1, noisy data somewhere•typically <1, meaning noise less than expected




*

OPUS-RS Output

Peak-to-Peak replaced by Est. Standard Deviations•approximately 95% confidence•derived from scatter of single baseline solutions •formal standard deviations (optimistic) available in

Extended Output




* *

OPUS-RS Station Selection

OPUS-RS Interpolative Dilution of Precision (IDOP)

OPUS-RS accuracy is dictated by CORS geometry and distances

IDOP = local CORS geometry relative to rover location

[min = 1/sqrt(#CORS)]

RMSD – CORS distances

* Forthcoming paper in “GPS Solutions” –Accuracy Assessment of the NGS’s OPUS-RS Utility

By C. Schwarz, R. Snay, & T. Soler

Expected OPUS-RS Standard Error Values in E or N Dimension:

OPUS-RS Usage

OPUS-RS Questions

OPUS-DB (database)

• OPUS-DB recently let loose “in the wild”• Means you can use it now• Intended to be a way for surveyors to

– access NSRS, – maintain the existence of the mark, and – optionally share results with others.

• Works with OPUS or OPUS-RS

OPUS-DBhttp://www.ngs.noaa.gov/OPUS/

OPUS-DB

OPUS-DB --- 3 Tabs

• Upload– Similar to other OPUS flavors

• View– use to retrieve marks from the database

• About– wealth of detail on OPUS system

OPUS-DB Upload

OPUS-DB Upload/Option #7

OPUS-DB Upload/Option #7

• Choose YES, Publish or NO, Don’t Publish• The NO option is same as OPUS-S or OPUS-RS• The YES option followed by a choice of OPUS-S or

OPUS-RS button will bring up a Step 2 screen to identify your mark…

• Either Describe NEW or Describe Recovered Mark or Abort

OPUS-DB Step 2

OPUS-DB Step 3

• If you choose NEW, you must fill in the required fields and have 2 photos (small .jpg files)

• If you choose Existing you need to know the mark identity (PID)

OPUS-DB Step 3 existing mark

OPUS-DB Step 3 new mark

OPUS-DB Step 4

OPUS-DB Approval Email

“The following contribution has been submitted to OPUS for publication in theOPUS Database. Please visit the link below to verify that the information you provided is correctly presented on the new datasheet.

When the datasheet is viewed, two buttons will be displayed at the top of the new datasheet web page. Please select the appropriate button to accept orwithdraw your contribution. An action must be taken for the datasheet to bepublished or withdrawn.”

The OPUS Team.

RINEX FILE: DESIGNATION: BARB RESET http://beta.ngs.noaa.gov/OPUS/getFeedback.jsp?id=000478336

OPUS-DB Final Approval and Sample Datasheet

Last Chance to Abort

OPUS-DB Usage

Recent OPUS Results on a Real Project

• USGS is monitoring the long term effects of an oil spill in northern Minnesota.

• They had been using an assumed basis of coordinates for horizontal and vertical surveys.

• Their GIS analyst was having trouble combining the data with other maps in the area.

• They asked for NGS help in getting connected to the NSRS.


• We decided that the best end result would be – Bluebooked First Order horizontal project (GPS)– Bluebooked Second Order Class 1 vertical (leveling)

• But, we also wanted to compare OPUS and OPUS-RS results.


Project Area




MONIQUE

BEAST

DIVA

BUD


Method MONIQUE_Lat MONIQUE_Lon MONIQUE_EllHt MONIQUE_OrthoHtOPUS-Static 175A 473428.93182 950515.94684 405.776 m 433.716 mOPUS-Static 278A 473428.93142 950515.94688 405.813 m 433.754 mOPUS-RS 278B 473428.93176 950515.94696 405.781 m 433.722 mOPUS-RS 278C 473428.93162 950515.94715 405.810 m 433.751 mMNCORS-RTRN 473428.93140 950515.94713 405.865 m 433.753 mTraverse 433.757 mTBC Network Solution 473428.93185 950515.94673 405.848 m 433.736 mLeveling - VOILY 433.737 m

Note: 0.0001 sec = 0.01 feet (approx)

Delta Lat = +/- 0.02 feetDelta Lon = +/- 0.02 feetDelta EllHt= +/- 0.06 feetDelta Elev= +/- 0.05 feet


Method BUD_Lat BUD_Lon BUD_EllHt BUD_OrthoHtOPUS-Static 175A 473427.64726 950518.51979 406.254 m 434.195 mOPUS-Static 278A 473427.64761 950518.52069 406.255 m 434.196 mOPUS-RS 278B 473427.64762 950518.52091 406.210 m 434.151 mOPUS-RS 278C 473427.64748 950518.52103 406.265 m 434.206 mMNCORS-RTRN 473427.64821 950518.52084 406.297 m 434.184 mTraverse 434.198 mTBC Network Solution 473427.64763 950518.52067 406.288 m 434.176 mLeveling - VOILY 434.177 m




Method DIVA_Lat DIVA_Lon DIVA_EllHt DIVA_OrthoHtOPUS-Static 175A 473424.99563 950524.52729 404.474 m 432.414 mOPUS-Static 278A 473424.98881 950524.52642 403.745 m 431.685 mOPUS-RS 278B 473424.98909 950524.52523 403.819 m 431.759 mOPUS-RS 278C 473424.98912 950524.52558 403.865 m 431.805 mMNCORS-RTRN 473424.98914 950524.52529 403.877 m 431.764 mTraverse 431.774 mTBC Network Solution 473424.98913 950524.52527 403.880 m 431.767 mLeveling - VOILY 431.750 m



DIVA was “in

the trees” for

session 175A !


Method BEAST_Lat BEAST_Lon BEAST_EllHt BEAST_OrthoHtOPUS-Static 175A 473424.00496 950530.77123 402.985 m 430.924 mOPUS-Static 278A 473424.00475 950530.77069 403.000 m 430.939 mOPUS-RS 278B 473424.00506 950530.77131 402.979 m 430.918 mOPUS-RS 278C 473424.00504 950530.77159 402.997 m 430.936 mMNCORS-RTRN 473424.00492 950530.77192 403.072 m 430.958 mTraverse 430.931 mTBC Network Solution 473424.00524 950530.77143 403.025 m 430.911 mLeveling - VOILY 430.911 m



Sample OPUS-RS Results for MONIQUE

BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)DK6380 PNR6 PINE RIVER 6 CORS ARP N465148.582 W0944321.276 83771.9DL6147 MNTF THIEF RIVER FALLS CORS ARP N480708.945 W0961226.664 103381.6DK7743 MNGP GRAND RAPIDS CORS ARP N471324.958 W0932902.622 127200.3DK6503 MNEM EMILY CORS ARP N464116.993 W0935716.192 130803.9DM2668 MNRV ROOSEVELT CORS ARP N484721.797 W0950304.460 135098.2DI0729 MORH CLAY COUNTY COOP CORS ARP N465303.127 W0964549.588 148333.0DK6509 MNJC JACOBSON CORS ARP N465841.840 W0931625.269 152435.1DK6505 MNFF FERGUS FALLS CORS ARP N461624.936 W0960320.668 162350.5DM2664 MNDN DONALDSON CORS ARP N483420.485 W0965452.722 175605.3

Sample OPUS-RS Results

Residuals of position determined by individual baselines from the final position (meters)

East North Uppnr6 -0.001 -0.001 -0.005mntf -0.001 -0.004 -0.010mngp 0.005 0.005 -0.003mnem 0.002 0.002 -0.012mnrv 0.010 0.003 -0.009morh -0.018 0.005 0.024mnjc 0.000 -0.000 0.036mnff -0.006 0.002 0.025mndn 0.005 -0.008 0.003

Questions

• Dave Zenk PE, PLS• National Geodetic Survey Advisor• Office of Land Management, Geodetic Unit• 395 John Ireland Blvd., MS 641• Transportation Bldg.• St. Paul, MN 55155

• 651-366-3523 phone• 651-366-3444 fax• 612-414-9522 mobile• [email protected] (NGS email)• [email protected] (MNDOT email)• [email protected] (personal email)

Documents

Kansas Land Surveyors Conference OPUS, OPUS-RS, and OPUS-DB Dave Zenk NGS Advisor October 29, 2010 Wichita, KS