Kansas Land Surveyors Conference OPUS, OPUS-RS, and OPUS-DB Dave Zenk NGS Advisor October 29, 2010 Wichita, 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 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) minutes »$$$ receiver, minutes of data OPUS-DB (database) share results »$$$ receiver, hours of data, share results OPUS-Projects – not released »Multiple »Multiple $$$ receivers, share results OPUS-GIS – not released »¢¢ receiver »¢¢ receiver, minutes of data OPUS-Leveling – not released

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 - in minutes –Fast, easy, consistent access to NSRS

OPUS Guidelines 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)

OPUS Screen Layout GPS file antenna type antenna height options OPUS-S (2 hr) OPUS-RS (15 min)

OPUS Inputs – 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 – TRM (choose from list) Antenna Ht – vertical measure from mark to ARP Options – next 2 slides…

OPUS Inputs (OPTIONS 1 & 2) specify SPCS specify CORS

OPUS Inputs (OPTIONS 3, 4, & 5) Specify GEOID model: Auto GEOID09 GEOID03 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: DATE: October 29, 2007 RINEX FILE: x.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:brdc n OBS USED: 1962 / 2082 : 94% ANT NAME:ASH A QUALITY IND / ARP HEIGHT: 0.0 NORMALIZED RMS:0.307 REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.005(m) (m) 0.005(m) ORTHO HGT: (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 NGS OPUS-RS SOLUTION REPORT USER: DATE: October 29, 2007 RINEX FILE: x.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:brdc n OBS USED: 1962 / 2082 : 94% ANT NAME:ASH A QUALITY IND / ARP HEIGHT: 0.0 NORMALIZED RMS:0.307 REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.005(m) (m) 0.005(m) ORTHO HGT: (m) 0.026(m) [Geoid03 NAVD88] *

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 NGS OPUS-RS SOLUTION REPORT USER: DATE: October 29, 2007 RINEX FILE: x.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:brdc n OBS USED: 1962 / 2082 : 94% ANT NAME:ASH A QUALITY IND / ARP HEIGHT: 0.0 NORMALIZED RMS:0.307 REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.005(m) (m) 0.005(m) ORTHO HGT: (m) 0.026(m) [Geoid03 NAVD88] * *

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-DB

OPUS-DB

OPUS-DB 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

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 “The following contribution has been submitted to OPUS for publication in the OPUS 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 or withdraw your contribution. An action must be taken for the datasheet to be published or withdrawn.” The OPUS Team. RINEX FILE: DESIGNATION: BARB RESET

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.

Recent OPUS Results on a Real Project 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.

Recent OPUS Results on a Real Project Project Area

Recent OPUS Results on a Real Project

MONIQUE BEAST DIVA BUD

Recent OPUS Results on a Real Project MethodMONIQUE_LatMONIQUE_LonMONIQUE_EllHtMONIQUE_OrthoHt OPUS-Static 175A m m OPUS-Static 278A m m OPUS-RS 278B m m OPUS-RS 278C m m MNCORS-RTRN m m Traverse m TBC Network Solution m m Leveling - VOILY m Note: sec = 0.01 feet (approx) Delta Lat = +/ feet Delta Lon = +/ feet Delta EllHt= +/ feet Delta Elev= +/ feet

Recent OPUS Results on a Real Project MethodBUD_LatBUD_LonBUD_EllHtBUD_OrthoHt OPUS-Static 175A m m OPUS-Static 278A m m OPUS-RS 278B m m OPUS-RS 278C m m MNCORS-RTRN m m Traverse m TBC Network Solution m m Leveling - VOILY m Note: sec = 0.01 feet (approx) Delta Lat = +/ feet Delta Lon = +/ feet Delta EllHt= +/ feet Delta Elev= +/ feet

Recent OPUS Results on a Real Project MethodDIVA_LatDIVA_LonDIVA_EllHtDIVA_OrthoHt OPUS-Static 175A m m OPUS-Static 278A m m OPUS-RS 278B m m OPUS-RS 278C m m MNCORS-RTRN m m Traverse m TBC Network Solution m m Leveling - VOILY m Note: sec = 0.01 feet (approx) Delta Lat = +/ feet Delta Lon = +/ feet Delta EllHt= +/ feet Delta Elev= +/ feet DIVA was “in the trees” for session 175A !

Recent OPUS Results on a Real Project MethodBEAST_LatBEAST_LonBEAST_EllHtBEAST_OrthoHt OPUS-Static 175A m m OPUS-Static 278A m m OPUS-RS 278B m m OPUS-RS 278C m m MNCORS-RTRN m m Traverse m TBC Network Solution m m Leveling - VOILY m Note: sec = 0.01 feet (approx) Delta Lat = +/ feet Delta Lon = +/ feet Delta EllHt= +/ feet Delta Elev= +/ feet

Sample OPUS-RS Results for MONIQUE BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) DK6380 PNR6 PINE RIVER 6 CORS ARP N W DL6147 MNTF THIEF RIVER FALLS CORS ARP N W DK7743 MNGP GRAND RAPIDS CORS ARP N W DK6503 MNEM EMILY CORS ARP N W DM2668 MNRV ROOSEVELT CORS ARP N W DI0729 MORH CLAY COUNTY COOP CORS ARP N W DK6509 MNJC JACOBSON CORS ARP N W DK6505 MNFF FERGUS FALLS CORS ARP N W DM2664 MNDN DONALDSON CORS ARP N W

Sample OPUS-RS Results Residuals of position determined by individual baselines from the final position (meters) East North Up pnr mntf mngp mnem mnrv morh mnjc mnff mndn

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 phone fax mobile (NGS ) (MNDOT ) (personal )