kansas land surveyors conference
Download
Skip this Video
Download Presentation
Kansas Land Surveyors Conference

Loading in 2 Seconds...

play fullscreen
1 / 61

Kansas Land Surveyors Conference - PowerPoint PPT Presentation


  • 208 Views
  • Uploaded on

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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Kansas Land Surveyors Conference' - kerryn


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
kansas land surveyors conference

Kansas Land Surveyors Conference

OPUS, OPUS-RS, and OPUS-DB

Dave Zenk

NGS Advisor

October 29, 2010

Wichita, KS

what is opus
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
Many Flavors of OPUS Planned
  • OPUS-S (static)
          • $$$ receiver, hours of data
  • OPUS-RS (rapid static)
          • $$$ receiver, minutes of data
  • OPUS-DB (database)
          • $$$ receiver, hours of data, share results
  • OPUS-Projects – not released
          • Multiple $$$ receivers, share results
  • OPUS-GIS – not released
          • ¢¢ receiver, minutes of data
  • OPUS-Leveling – not released
how does opus work
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-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
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
OPUS Website (all flavors)
  • http://www.ngs.noaa.gov/OPUS/
opus screen layout
OPUS Screen Layout

e-mail

GPS file

antenna type

antenna height

options

OPUS-S

(2 hr)

OPUS-RS

(15 min)

opus inputs
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
OPUS Inputs (OPTIONS 1 & 2)

specify

SPCS

specify

CORS

opus inputs options 3 4 5
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 Inputs (OPTIONS 6, 7, & 8)

OPUS-Projects Keyword

Set USER Profile

Choose PUBLISH and Submit

slide18

Antenna Height

  • true vertical distance
  • measured in meters

ARP

MARK

opus positions

CORS B

CORS A

+

CORS C

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

Average

opus report check results
OPUS Report – check results
  • > 90% observations used
  • > 50% ambiguities fixed
  • < 3 cm overall RMS
  • check ephemeris type
  • check antenna info
  • < 5 cm peak-to-peak errors

…and which CORS were used? …

resubmit later for better CORS scenario & ephemeris

opus extended output
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
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 60 minute session
OPUS-RS geographical coverage (60 minute session)
  • Don’t use OPUS-RS outside areas where insufficient CORS exist.
opus rs output
OPUS-RS Output

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

*

  • “#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
opus rs output1
OPUS-RS Output

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

*

  • “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 output2
OPUS-RS Output

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

*

*

  • 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 interpolative dilution of precision idop
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

opus db database
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 3 tabs
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 option 71
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 3
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 approval email
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

recent opus results on a real project
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 project1
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 project6
Recent OPUS Results on a Real Project

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

recent opus results on a real project7
Recent OPUS Results on a Real Project

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

recent opus results on a real project8
Recent OPUS Results on a Real Project

Note: 0.0001 sec = 0.01 feet (approx)

DIVA was “in the trees” for session 175A !

Delta Lat = +/- 0.02 feet

Delta Lon = +/- 0.06 feet

Delta EllHt= +/- 0.22 feet

Delta Elev= +/- 0.12 feet

recent opus results on a real project9
Recent OPUS Results on a Real Project

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

sample opus rs results for monique
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

sample opus rs results
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

questions
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)
ad