K.I.S.S. GPS hello.

WHAT IS OPUS? On-line Positioning User Service Fast & easy access to the NSRS (National Spatial Reference System) for GPS users

National Geodetic Survey National Ocean Service National Oceanic and Atmospheric Administration G. L. Mader - 3 CORS Forum Sep. 25, 2007 Why do we need OPUS? Recognize most positioning done with GPS Recognize most positioning done with GPS Want to provide fast, accurate, consistent, reliable access to NSRS Want to provide fast, accurate, consistent, reliable access to NSRS CORS data alone does not ensure consistency CORS data alone does not ensure consistency OPUS OPUS NGS computersNGS computers NGS softwareNGS software Standard parameterizationStandard parameterization Standard coordinates/velocitiesStandard coordinates/velocities Your machine talks to our machineYour machine talks to our machine

Quick Link to OPUS from NGS Home Page

You’ve got mail! OPUS solution

1191 National CORS 190+ Cooperative CORS National CORS CORS Network: Where We are Today

Baseline Plot National

VDatum Vertical Datum Transformation Tool

CORS solution 1 solution 3 solution 2 How does OPUS compute your position? 3 single baselines computed 3 positions averaged — simple mean (equal weights)

How Does OPUS Pick Base Stations? 1.Estimate position for remote station 2.Compute distance to every available CORS 3.Sort CORS by increasing distance 4.Select the 5 closest CORS 5.Look at 1 st 3 CORS with TEQC program. Criteria: ● data cover time span for remote station ● > 80% of data available ● low multipath ● if not, replace with 4 th CORS (then 5 th ) 6. Start single baseline solutions using 1 st 3 CORS ● check solution quality ● if bad solution, replace CORS with 4 th (then 5 th )

HOW IS THE ANTENNA HEIGHT MEASURED? ARP MARK The height is measured vertically (NOT the slant height) from the mark to the ARP of the antenna. The height is measured in meters. The ARP is almost always the center of the bottom-most, permanently attached, surface of the antenna. See GPS Antenna Calibration for photo’s and diagrams that show where the ARP is on most antennas: / If the default height of is entered, OPUS will return the position of the ARP.

WHY DO I NEED THE ANTENNA TYPE? The antenna phase centers are located somewhere around here. The Antenna Reference Point (ARP) is almost always located in the center of the bottom surface of the antenna. The antenna offsets are the distance between the phase centers and the ARP You do not need to know these offsets. They are passed to the processing software through the antenna type Incorrect or missing antenna type  big vertical errors ARP phase ctr.

How Can I Improve My Results? Consider observing a longer session Avoid conditions that perturb the GPS signal— unsettled weather, solar flares, multipath (nearby reflective surfaces) Data sets of at least four hours have been shown to produce more reliable results

FILE: corv o NOTE: Antenna offsets supplied by the user were zero. Coordinates 1008 returned will be for the antenna reference point (ARP) NGS OPUS SOLUTION REPORT ======================== USER: DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc n OBS USED: 4228 / 4314 : 98% ANT NAME: ASH700936B_M NONE # FIXED AMB: 25 / 29 : 86% ARP HEIGHT: 0.0 OVERALL RMS: 0.013(m) REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) X: (m) 0.018(m) (m) 0.018(m) Y: (m) 0.021(m) (m) 0.021(m) Z: (m) 0.024(m) (m) 0.024(m) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.034(m) (m) 0.034(m) ORTHO HGT: (m) 0.043(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] Easting (X) [meters] Convergence [degrees] Point Scale Combined Factor US NATIONAL GRID DESIGNATOR: 10TDQ (NAD 83) BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N W AJ6959 CHZZ CAPE MEARS CORS ARP N W DH4503 P376 EOLARESVR_OR2004 CORS ARP N W NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N W OPUS Output - Standard

Allowable Data Formats Compressed archive of multiple files. Archive must contain RINEX “site123h.04o” or Hatanaka “site123h.04d” Compressed individual files.“Site123h.zip”must contain “site123h.06o” or “site123h.06d” Manufacturer’s native / raw (binary) —uncompressed--as long as UNAVCO’s teqc program can process it RINEX Receiver Independent Exchange-- uncompressed

Select or exclude base stations including Cooperative CORS Select state plane coordinate zone Extended Output Set user profile Associate antenna type, antenna height, SPC code, selected base stations and extended option choices with your address

Report Options + extended report + XML report + select state plane Sharing Options + add to database + add to campaign Solution Options + set user profile + select CORS + select software

FILE: corv o NOTE: Antenna offsets supplied by the user were zero. Coordinates 1008 returned will be for the antenna reference point (ARP) NGS OPUS SOLUTION REPORT ======================== USER: DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc n OBS USED: 4228 / 4314 : 98% ANT NAME: ASH700936B_M NONE # FIXED AMB: 25 / 29 : 86% ARP HEIGHT: 0.0 OVERALL RMS: 0.013(m) REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) X: (m) 0.018(m) (m) 0.018(m) Y: (m) 0.021(m) (m) 0.021(m) Z: (m) 0.024(m) (m) 0.024(m) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.034(m) (m) 0.034(m) ORTHO HGT: (m) 0.043(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] Easting (X) [meters] Convergence [degrees] Point Scale Combined Factor US NATIONAL GRID DESIGNATOR: 10TDQ (NAD 83) BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N W AJ6959 CHZZ CAPE MEARS CORS ARP N W DH4503 P376 EOLARESVR_OR2004 CORS ARP N W NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N W OPUS Output Standard

USER: DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc n OBS USED: 4228 / 4314 : 98% ANT NAME: ASH700936B_M NONE # FIXED AMB: 25 / 29 : 86% ARP HEIGHT: 0.0 OVERALL RMS: 0.013(m) Reading OPUS Output The version of PAGES software used for processing The antenna type you selected and height of antenna reference point height you entered. Confirm that these are correct. The ephemeris used (OPUS will use the best available): “igs” final post-fit orbit--better than 1 cm (10-14 days wait) “igr” rapid post-fit orbit--better than 2 cm (17 hours wait) “igu” ultra-rapid predicted orbit--better than 20 cm (available immediately) Navigation file used Your address & observation file. Solution run date & time

USER: DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc n OBS USED: 4228 / 4314 : 98% ANT NAME: ASH700936B_M NONE # FIXED AMB: 25 / 29 : 86% ARP HEIGHT: 0.0 OVERALL RMS: 0.013(m) Start & end dates & times of your file Ratio and % of observations used in solution Ratio and % of fixed/total ambiguities Overall RMS of the solution Reading OPUS Output con’t.

Guidelines for Good Solution  Make sure antenna type and height are correct  Review statistics: at least 90% of observations should be used OBS USED: 4228 / 4314 : 98% at least 50% of the ambiguities should be fixed # FIXED AMB: 25 / 29 : 86% overall RMS should seldom exceed m OVERALL RMS: 0.013(m)  In case of bad statistics, try choosing different CORS and re-submit.

REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) X: (m) 0.018(m) (m) 0.018(m) Y: (m) 0.021(m) (m) 0.021(m) Z: (m) 0.024(m) (m) 0.024(m) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.034(m) (m) 0.034(m) ORTHO HGT: (m) 0.043(m) Reference frames. Epochs Position, xyz Peak-peak errors, xyz (range, max-min) Peak-peak errors may vary between NAD83 & ITRF Orthometric ht. is based on current geoid model Reading OPUS Output con’t. Solution/Coordinates [Geoid03 NAVD88] Position, lat / long / eh / oh Peak-peak for lat/long etc

How does OPUS estimate errors? peak to peak Example from ITRF x coordinate of corv059 output. The decimal portions of the three solutions in the extended output are:.8690,.8709 and.8861 m. The simple mean of these values as displayed in the output is.875. Sigma is.009. The peak-peak (max-min) distance is.017. The peak-peak can perhaps be thought of as approximating 2 sigma, but is not intended to be relied on in that fashion. It is intended simply as a conservative estimate of the solution accuracy. Mean +/-1 σ (.009 m) Peak-peak error =.017 m Conservative accuracy estimate, ~ 2 σ Peak-peak should seldom exceed 5 cm Vertical is typically at least twice horizontal mean p376-corv newp-corv chzz-corv Mean +/-2 σ (.018 m) meters

 CORS solution 1 solution 2 your peak-to-peaks: scaled from the spread of the 3 CORS solutions solution 3 your position: averaged from the 3 CORS solutions h

UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] Easting (X) [meters] Convergence [degrees] Point Scale Combined Factor US NATIONAL GRID DESIGNATOR: 10TDQ (NAD 83) Universal Transverse Mercator (UTM) coordinates State Plane coordinates (if requested) US National Grid OPUS Output con’t. Grid Coordinates

BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N W AJ6959 CHZZ CAPE MEARS CORS ARP N W DH4503 P376 EOLARESVR_OR2004 CORS ARP N W NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N W This position and the above vector components were computed without any knowledge by the National Geodetic Survey regarding the equipment or field operating procedures used. READING OPUS OUTPUT (control) Disclaimer Base Stations--NAD83 position--distance away The closest published station in the NGS data base In case you didn’t know it was there

Areas Covered by OPUS

DEFAULTS: $$$ receiver hours of data one receiver no archive no delimiters US only GPS only OPUSOPUS in the works ¢¢ ¢¢ receivers * OPUS mapper OPUS mapper minutes minutes of dataOPUS-RSOPUS-RS multiple multiple receivers * OPUS-projects OPUS-projects share share results * OPUS-DB OPUS-DB delimited delimited resultsOPUS-XML global global results * OPUS-global GNSS GNSS signals * OPUS-GNSS  heights * OPUS-leveling Operational components are available at * Prototype components are available at

OPUS-RS Accuracy for 15-minute data sets

OPUS-RS Coverage Interpolative Dilution of Precision (IDOP) Values

FILE: corv o NOTE: Antenna offsets supplied by the user were zero. Coordinates 1008 returned will be for the antenna reference point (ARP) NGS OPUS SOLUTION REPORT ======================== USER: DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc n OBS USED: 4228 / 4314 : 98% ANT NAME: ASH700936B_M NONE # FIXED AMB: 25 / 29 : 86% ARP HEIGHT: 0.0 OVERALL RMS: 0.013(m) REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) X: (m) 0.018(m) (m) 0.018(m) Y: (m) 0.021(m) (m) 0.021(m) Z: (m) 0.024(m) (m) 0.024(m) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.034(m) (m) 0.034(m) ORTHO HGT: (m) 0.043(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] Easting (X) [meters] Convergence [degrees] Point Scale Combined Factor US NATIONAL GRID DESIGNATOR: 10TDQ (NAD 83) BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N W AJ6959 CHZZ CAPE MEARS CORS ARP N W DH4503 P376 EOLARESVR_OR2004 CORS ARP N W NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N W OPUS Output - Standard FILE: corv o NOTE: Antenna offsets supplied by the user were zero. Coordinates 1008 returned will be for the antenna reference point (ARP) NGS OPUS SOLUTION REPORT ======================== USER: DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc n OBS USED: 4228 / 4314 : 98% ANT NAME: ASH700936B_M NONE # FIXED AMB: 25 / 29 : 86% ARP HEIGHT: 0.0 OVERALL RMS: 0.013(m) REF FRAME: NAD_83(CORS96)(EPOCH: ) ITRF00 (EPOCH: ) X: (m) 0.018(m) (m) 0.018(m) Y: (m) 0.021(m) (m) 0.021(m) Z: (m) 0.024(m) (m) 0.024(m) LAT: (m) (m) E LON: (m) (m) W LON: (m) (m) EL HGT: (m) 0.034(m) (m) 0.034(m) ORTHO HGT: (m) 0.043(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] Easting (X) [meters] Convergence [degrees] Point Scale Combined Factor US NATIONAL GRID DESIGNATOR: 10TDQ (NAD 83) BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N W AJ6959 CHZZ CAPE MEARS CORS ARP N W DH4503 P376 EOLARESVR_OR2004 CORS ARP N W NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N W February 19, :16:22 UTC zzyy o page master3.pl igs14293.eph [precise] brdc n TRM NONE /05/30 00:00: /05/30 23:59: NAD_83(CORS96) m m m ITRF00 (EPOCH: ) m m m <PLANE_COORD_SPEC TYPE="SPC" ZONE="4204(TXSC )"> RTP (NAD 83) DE5999 ADKS ADDICKS 1795 CORS ARP N W DJ8995 ROD1 ROD1 CORS ARP N W DH3612 TXLI LIBERTY CORS ARP N W AA9861 LAKE HOUSTON 2050 CORS L1 PHS N W This position and the above vector components were computed without any knowledge by the National Geodetic Survey regarding the equiqment or field operating procedure used. OPUS Output - XML

NGS-modeled antenna OPUS website your datasheet QA/QC OPUS Concept antenna type, height control station photo * control station description * control station monument register your agency public datashee t review OPUS  Datasheet Concept * optional for “existing” stations. GPS data (4+hr, good stats )

Stable Permanent Unique Recoverable Safe Z |-- control station monument control station requirements

GPS data requirements “OPUSable” 4+ hours of dual frequency data NGS-calibrated antenna OPUS must achieve: ≥ 90% observations used ≥ 80% ambiguities fixed ≤ 0.02m peak-to-peak horizontal ≤ 0.04m peak-to-peak vertical NGS-modeled antenna GPS data (4+hr, good stats )

* optional for “existing” stations. control station description * control station photo * metadata requirements observation notes Simplified bluebooking antenna type, height

USER OPUS GPS DATA SOLUTION In the usual OPUS procedure, the user submits his GPS data and receives a solution via . OPUS-Projects

USER OPUS GPS DATA SOLUTION Project Management, etc. Project GPS DATA In OPUS-Projects the OPUS solutions can be ed to any number of persons associated with the project, allowing data collection and quality to be closely monitored. The data is also delivered to the project directory for network processing as data collection for each day is completed. OPUS-Projects ADJUSTED SOLUTION

From the Field Point of View Observer submits all data to OPUS 1 st Data Submission –Completes main page (antenna type & ARP hgt.) –Selects options –Enters project ID & sets profile All subsequent data submissions –Needs only to enter address and data –Profile values fixed to address

From the Project Managers Point of View Receives OPUS solution s from all observers Monitor data collection Monitor data quality Data file management is provided Daily network solutions while project is still underway Near real time feedback to project personnel

OPUS-RS (Rapid Static) Became operational February 2007 Allows data spans as short as 15 min. Uses software developed at OSU providing rapid ambiguity resolution

mmcmdmmdamhmkm # of People Who Care Position Accuracy NGS Works Here GIS Works Here

OPUS-GIS Accepts single frequency data Accepts kinematic data Differential range solution to CORS Kinematic trajectory report Static occupation report Shape files are coming

Why do we need OPUS-GIS? Centimeter accuracy not appropriate for all objects Lower grade receivers can deliver usable results Recover kinematic traverses Consistent application to NSRS across accuracy spectrum

NN SS EEWW Effect of Differential Positioning Point positioningDifferential Positioning

2005/12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: /12/ 3 17: 1: Date & Time RDOP RMS XYZXYZ RMSLAT, LON, EL HGT NEU RMS OPUS–GIS Kinematic Trajectory Report

Station #: 1 File: zzyy337r.05o 2005/12/ 3 17: 1: /12/ 3 17: 3: #sec: 103 #pts: Station #: 2 File: zzyy337r.05o 2005/12/ 3 17: 4: /12/ 3 17: 7: #sec: 162 #pts: Station #: 3 File: zzyy337r.05o 2005/12/ 3 17: 9: /12/ 3 17:12: #sec: 155 #pts: Station #: 4 File: zzyy337r.05o 2005/12/ 3 17:14: /12/ 3 17:14: #sec: 10 #pts: OPUS–GIS Static Occupation Report …

OPUS-GIS output Station #: 1 File: zzyy o 2006/ 8/11 1: 1: / 8/11 2:15: #sec: 4440 #pts: Station #: 2 File: zzyy o 2006/ 8/11 2:15: / 8/11 2:20: #sec: 270 #pts: Station #: 3 File: zzyy o 2006/ 8/11 2:33: / 8/11 2:38: #sec: 300 #pts: Station #: 4 File: zzyy o 2006/ 8/11 2:41: / 8/11 2:52: #sec: 630 #pts: Station #: 5 File: zzyy o 2006/ 8/11 2:52: / 8/11 3:35: #sec: 2550 #pts:

OPUS Extended Output

BASE STATION INFORMATION STATION NAME: newp a 10 (Newport; Newport, Oregon USA) ANTENNA: ASH700936B_M S/N=CR16197 XYZ (M) XYZ VEL (M/YR) NEU MON TO ARP (M) NEU ARP TO L1 PHASE CENTER (M) NEU ARP TO L2 PHASE CENTER (M) XYZ VEL TIMES YRS XYZ MON TO ARP XYZ ARP TO L1 PHASE CENTER XYZ L1 PHS XYZ XYZ ADJUSTMENTS XYZ NEW L1 PHS XYZ NEW XYZ NEW LLH NEW L1 PHS LLH NEW LLH NEW OPUS Extended Output: Base Station Information Each CORS has a section like the one above, with ITRF xyz coordinates computed using HTDP velocities for the epoch of the observations (mid-point of the session). Note the above CORS has a monument separate from the ARP (positions coincide but ellipsoid heights are different). Base station and antenna used Monument starting ITRF coordinates. NEU offsets ITRF XYZ at mid-pt of session ITRF lat long EH at mid-pt of session XYZ offsets and position Position offsets at mid-pt of session Velocity in XYZ. These values are usually for CORS (as they are here). The differences between initial and computed positions These values are larger for the unknown station as we will see. Time interval to multiply times velocity = decimal year at mid-pt of session minus = yrs

REMOTE STATION INFORMATION STATION NAME: corv 1 ANTENNA: ASH700936B_M SNOW S/N=UNKNOWN XYZ (M) NEU MON TO ARP (M) NEU ARP TO L1 PHASE CENTER (M) NEU ARP TO L2 PHASE CENTER (M) XYZ MON TO ARP XYZ ARP TO L1 PHASE CENTER XYZ L1 PHS OPUS Extended Output: Remote Station Information The initial ITRF xyz position for the station being solved for is displayed for the mid-point of the observation time span. A similar position is obtained for the L1 phase center based on the antenna type selected. The antenna height is here because we are solving for the Antenna Reference Point position. Typically, however, you will have entered a non-zero antenna height.

OPUS Extended Output: Remote Station cont  Final positions based on this first vector. The XYZ adjustments are the difference between the initial and final positions. XYZ L1 PHS BASELINE NAME: newp corv XYZ XYZ ADJUSTMENTS XYZ NEW L1 PHS XYZ NEW XYZ NEW LLH NEW L1 PHS LLH NEW LLH NEW Preliminary ITRF coordinates for the remote station incorporating velocities computed for mid-point of session in the previous section  Final remote station ITRF latitude, longitude and ellipsoid height for this vector. Similar for the two remaining vectors. The first of 3 baselines being solved

OPUS Extended Output: gfiles G-FILES Axx B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0595ACORVX0595ANEWP D Axx B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0595ACORVX0595ACHZZ D Axx B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0595ACORVX0595AP376 D Each of the three baselines has a section of A, B, I, C and D records. The specific record formats are listed in Bluebook Annex N, The C record contains dx, dy, dz vector components and related standard deviations. The D record contains correlations. The gfiles can be combined to do NGS-style adjustment with gfile and bfile (next slide).

OPUS Extended Output: user-constructed composite gfile Axx **first session, first vector:** B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0605ACORVX0605ANEWP D **first session, second vector:** B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0605ACORVX0605ACHZZ D **first session, third vector:** B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0605ACORVX0605AP376 D **second session, first vector:** B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X1525ACORVX1525ANEWP D **second session, second vector:** B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X1525ACORVX1525ACHZZ D **second session, third vector:** B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X1525ACORVX1525AP376 D Example of two occupations of a station. Gfile constructed by deleting all but first “Axx2005…” lines from the extended output, then appending the two baselines’ gfiles to the first one, then adding second session results to the first session. Extra lines inserted to show file structure

OPUS Extended Output: Post-fit RMS…. POST-FIT RMS BY SATELLITE VS. BASELINE OVERALL newp-corv| newp-corv| NGS’ baseline processor “PAGES” (Program for the Adjustment of GPS Ephemerides) develops statistics such as the above to aid in analyzing solution quality. In the spirit of automated processing that is fundamental to OPUS, there is no option to disable specific satellites. Each baseline has a section like the one shown above.

OPUS Extended Output: Observations summary OBS BY SATELLITE VS. BASELINE OVERALL newp-corv| newp-corv| OVERALL chzz-corv| chzz-corv| OVERALL p376-corv| p376-corv| Each baseline has a summary of the observations received from each satellite. OBS USED: 4228 / 4314 : 98% As discussed on slides 14 & 15 (Reading OPUS output, Guidelines for Good Solution), the Standard Output summarizes the total percent of observations used over all three baselines.

OPUS Extended Output: Covariance Matrices Covariance Matrix for the xyz OPUS Position (meters2) Covariance Matrix for the enu OPUS Position (meters2) Horizontal network accuracy = meters. Vertical network accuracy = meters. Additional statistics developed by PAGES for use in commercial adjustment software: Diagonal elements: Variance of x: Variance of y: Variance of z: Off-diagonal elements: Covariance of x-y: Covariance of x-z: Covariance of y-z: Similar for enu. Estimates of network accuracy. These may be optimistic here, given that peak-peak errors are in the 1-3 cm range.

OPUS Extended Output: NAD 83 quantities Derivation of NAD 83 vector components Position of reference station ARP in NAD_83(CORS96)(EPOCH: ). Xa(m) Ya(m) Za(m) NEWP CHZZ P Position of reference station monument in NAD_83(CORS96)(EPOCH: ). Xr(m) Yr(m) Zr(m) NEWP CHZZ P Velocity of reference station monument in NAD_83(CORS96)(EPOCH: ). Vx (m/yr) Vy (m/yr) Vz (m/yr) NEWP CHZZ P Vectors from unknown station monument to reference station monument in NAD_83(CORS96)(EPOCH: ). Xr-X= DX(m) Yr-Y= DY(m) Zr-Z= DZ(m) NEWP CHZZ P The above quantities are derived by transformation from similar ITRF quantities.

OPUS Extended Output: SPC—Disclaimer--End STATE PLANE COORDINATES - International Foot SPC (3601 OR N) Northing (Y) [feet] Easting (X) [feet] Convergence [degrees] Point Scale Combined Factor This position and the above vector components were computed without any knowledge by the National Geodetic Survey regarding the equipment or field operating procedures used. State Plane Coordinate quantities Disclaimer End of OPUS Extended Output. Next: example of adjusting several sessions submitted to OPUS for the same station

Files for sample adjustment Upper part of skeleton Bfile (no *25*, *27*, *70*, *72* records): *OR*HZTLOBS NGS NATIONAL GEODETIC SURVEY *10*TEST OPUS SOLUTIONS TO CORVALLIS CORS *12* JROJEFF OLSEN *13*NORTH AMERICAN DATUM-83 GRS *80*0001NEWPORT CORS ARP N W ORAA *86*0001 N88 A A *80*0002CAPE MEARS CORS ARP N W ORAA *86*0002 N88 A A (*80* and *86* records for two stations not shown) *OR* Serfil : NEWP 0001 CHZZ 0002 P CORV 0009 DDSN 0005 Upper Part of composite Gfile. Four 2-hr sessions for CORV at different times of 2005 were sent to OPUS. Vectors for one of the four sessions shown. Axx B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0605ACORVX0605ANEWP D B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0605ACORVX0605ACHZZ D B page5 v IGS NGS IFDDFX Iant_info.003 NGS C X0605ACORVX0605AP376 D Afile : CC N W 20780E DD3 II (Coordinates and EH for NEWP constrained) MM3NYfrebbk

Adjustment statistics NATIONAL GEODETIC SURVEY PROGRAM ADJUST ADJUSTMENT PROGRAM PAGE 15 VERSION 4.30 N RMS MEAN ABS CONTRIB. RESIDUAL RESIDUAL NORTH (METERS) EAST (METERS) UP (METERS) DEGREES OF FREEDOM = 24 VARIANCE SUM = STD.DEV.OF UNIT WEIGHT = VARIANCE OF UNIT WEIGHT = 9.77

Output Bfile Bfile from free adjustment : *CO*HZTLOBS NGS NATIONAL GEODETIC SURVEY *10*TEST OPUS SOLUTIONS TO CORVALLIS CORS *12* JROJEFF OLSEN *13*NORTH AMERICAN DATUM-83 GRS *80*0001NEWPORT CORS ARP N W ORAA *86*0001 N A A *80*0002CAPE MEARS CORS ARP N W ORAA *86*0002 N A A *80*0003EOLARESVR OR2004 CORS ARP N W ORAA *86*0003 N A A *80*0009CORV CORS ARP BY OPUS N W ORAA ( Pub =.91082,.51926) *86*0009 N A A ( Pub = ) *80*0005DDSN N W ORAA *86*0005 N A A *AL* (No orthometric or geoid heights computed in this example)

Example of using HTDP from NGS Tool Kit NEWP position computed for day of year 059, 2005