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

2. 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.

3. 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

4. OPUS has been popular

6. Areas covered by OPUS

9. 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

10. 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

11. 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

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

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

14. OPUS Inputs Email – dave.zenk@noaa.govdave.zenk@noaa.gov 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…

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

16. OPUS Inputs (OPTIONS 3, 4, & 5) Specify GEOID model: Auto GEOID09 GEOID03 Choose OUTPUT type Choose XML or not

17. OPUS Inputs (OPTIONS 6, 7, & 8) OPUS-Projects Keyword Set USER Profile Choose PUBLISH and Submit

18. ARP MARK Antenna Height true vertical distance measured in meters

19. 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

20. OPUS Report

21. 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

22. 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

23. 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

24. OPUS-RS geographical coverage (15 minute session) Don’t use OPUS-RS outside areas where insufficient CORS exist.

25. OPUS-RS geographical coverage (60 minute session) Don’t use OPUS-RS outside areas where insufficient CORS exist.

26. 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: william.stone@noaa.gov 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.91 ARP 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] *

27. 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: william.stone@noaa.gov 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.91 ARP 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] *

28. 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: william.stone@noaa.gov 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.91 ARP 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] * *

29. OPUS-RS Station Selection

30. 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

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

32. OPUS-RS Usage

33. OPUS-RS Questions

34. 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

35. OPUS-DB http://www.ngs.noaa.gov/OPUS/

36. OPUS-DB

37. 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

38. OPUS-DB Upload

39. OPUS-DB Upload/Option #7

40. 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

41. OPUS-DB Step 2

42. 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)

43. OPUS-DB Step 3 existing mark

44. OPUS-DB Step 3 new mark

45. OPUS-DB Step 4

46. OPUS-DB Approval Email “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 http://beta.ngs.noaa.gov/OPUS/getFeedback.jsp?id=000478336

47. OPUS-DB Final Approval and Sample Datasheet Last Chance to Abort

48. OPUS-DB Usage

49. 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.

50. 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.

51. Recent OPUS Results on a Real Project Project Area

52. Recent OPUS Results on a Real Project

54. MONIQUE BEAST DIVA BUD

55. Recent OPUS Results on a Real Project MethodMONIQUE_LatMONIQUE_LonMONIQUE_EllHtMONIQUE_OrthoHt OPUS-Static 175A473428.93182950515.94684405.776 m433.716 m OPUS-Static 278A473428.93142950515.94688405.813 m433.754 m OPUS-RS 278B473428.93176950515.94696405.781 m433.722 m OPUS-RS 278C473428.93162950515.94715405.810 m433.751 m MNCORS-RTRN473428.93140950515.94713405.865 m433.753 m Traverse 433.757 m TBC Network Solution473428.93185950515.94673405.848 m433.736 m Leveling - VOILY 433.737 m Note: 0.0001 sec = 0.01 feet (approx) Delta Lat = +/- 0.02 feet Delta Lon = +/- 0.02 feet Delta EllHt= +/- 0.06 feet Delta Elev= +/- 0.05 feet

56. Recent OPUS Results on a Real Project MethodBUD_LatBUD_LonBUD_EllHtBUD_OrthoHt OPUS-Static 175A473427.64726950518.51979406.254 m434.195 m OPUS-Static 278A473427.64761950518.52069406.255 m434.196 m OPUS-RS 278B473427.64762950518.52091406.210 m434.151 m OPUS-RS 278C473427.64748950518.52103406.265 m434.206 m MNCORS-RTRN473427.64821950518.52084406.297 m434.184 m Traverse 434.198 m TBC Network Solution473427.64763950518.52067406.288 m434.176 m Leveling - VOILY 434.177 m Note: 0.0001 sec = 0.01 feet (approx) Delta Lat = +/- 0.02 feet Delta Lon = +/- 0.02 feet Delta EllHt= +/- 0.05 feet Delta Elev= +/- 0.05 feet

57. Recent OPUS Results on a Real Project MethodDIVA_LatDIVA_LonDIVA_EllHtDIVA_OrthoHt OPUS-Static 175A473424.99563950524.52729404.474 m432.414 m OPUS-Static 278A473424.98881950524.52642403.745 m431.685 m OPUS-RS 278B473424.98909950524.52523403.819 m431.759 m OPUS-RS 278C473424.98912950524.52558403.865 m431.805 m MNCORS-RTRN473424.98914950524.52529403.877 m431.764 m Traverse 431.774 m TBC Network Solution473424.98913950524.52527403.880 m431.767 m Leveling - VOILY 431.750 m Note: 0.0001 sec = 0.01 feet (approx) Delta Lat = +/- 0.02 feet Delta Lon = +/- 0.06 feet Delta EllHt= +/- 0.22 feet Delta Elev= +/- 0.12 feet DIVA was “in the trees” for session 175A !

58. Recent OPUS Results on a Real Project MethodBEAST_LatBEAST_LonBEAST_EllHtBEAST_OrthoHt OPUS-Static 175A473424.00496950530.77123402.985 m430.924 m OPUS-Static 278A473424.00475950530.77069403.000 m430.939 m OPUS-RS 278B473424.00506950530.77131402.979 m430.918 m OPUS-RS 278C473424.00504950530.77159402.997 m430.936 m MNCORS-RTRN473424.00492950530.77192403.072 m430.958 m Traverse 430.931 m TBC Network Solution473424.00524950530.77143403.025 m430.911 m Leveling - VOILY 430.911 m Note: 0.0001 sec = 0.01 feet (approx) Delta Lat = +/- 0.02 feet Delta Lon = +/- 0.04 feet Delta EllHt= +/- 0.10 feet Delta Elev= +/- 0.06 feet

59. 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.9 DL6147 MNTF THIEF RIVER FALLS CORS ARP N480708.945 W0961226.664 103381.6 DK7743 MNGP GRAND RAPIDS CORS ARP N471324.958 W0932902.622 127200.3 DK6503 MNEM EMILY CORS ARP N464116.993 W0935716.192 130803.9 DM2668 MNRV ROOSEVELT CORS ARP N484721.797 W0950304.460 135098.2 DI0729 MORH CLAY COUNTY COOP CORS ARP N465303.127 W0964549.588 148333.0 DK6509 MNJC JACOBSON CORS ARP N465841.840 W0931625.269 152435.1 DK6505 MNFF FERGUS FALLS CORS ARP N461624.936 W0960320.668 162350.5 DM2664 MNDN DONALDSON CORS ARP N483420.485 W0965452.722 175605.3

60. Sample OPUS-RS Results Residuals of position determined by individual baselines from the final position (meters) East North Up pnr6 -0.001 -0.001 -0.005 mntf -0.001 -0.004 -0.010 mngp 0.005 0.005 -0.003 mnem 0.002 0.002 -0.012 mnrv 0.010 0.003 -0.009 morh -0.018 0.005 0.024 mnjc 0.000 -0.000 0.036 mnff -0.006 0.002 0.025 mndn 0.005 -0.008 0.003

61. 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 dave.zenk@noaa.gov (NGS email) dave.zenk@dot.state.mn.us (MNDOT email) zenkx002@umn.edu (personal email)