OPUS Online Positioning User Service

Information about OPUS Online Positioning User Service

Published on December 18, 2009

Author: palmettoequipment

Source: authorstream.com

Content

OPUS:Online Positioning User Service : OPUS:Online Positioning User Service http://www.ngs.noaa.gov/OPUS/ [email protected] WHAT IS OPUS? : WHAT IS OPUS? On-line Positioning User Service Fast & easy access to the NSRS (National Spatial Reference System) for GPS users How Does OPUS Work? : How Does OPUS Work? Data submitted through NGS web page Processed automatically with NGS computers & software Position with respect to 3 suitable CORS (or IGS sites if 1) no NAD 83 positions are available and 2) the host country has an agreement with NGS. In these international cases, ITRF coordinates only are returned, and there are no state plane or US grid coordinates Solution via email (usually in minutes) OPUS Guidelines : OPUS Guidelines Dual-frequency data (L1/L2) [recommended] Minimum 2 hrs of data (maximum 48—only cross midnight once) No kinematic data No Glonass. Galileo will be discussed as the constellation becomes available Accurate height requires: correct antenna type correct antenna height How Does OPUS Compute Position? : How Does OPUS Compute Position? 3 single baselines computed 3 positions averaged — simple mean (equal weights) Differences between positions include any errors in CORS coordinates Time-series plots, 60-day and long-term : Time-series plots, 60-day and long-term web page 60-day time series Long-term time series The time series plots provide a means of evaluating the small changes in position of a CORS. How Does OPUS Pick Base Stations? : How Does OPUS Pick Base Stations? Estimate position for remote station Compute distance to every available CORS Sort CORS by increasing distance Select the 5 closest CORS Look at 1st 3 CORS with TEQC program. Criteria: ● data cover time span for remote station ● > 80% of data available ● low multipath ● if not, replace with 4th CORS (then 5th) 6. Start single baseline solutions using 1st 3 CORS ● check solution quality ● if bad solution, replace CORS with 4th (then 5th) Slide 8: CORS Selection (example = CORV solved from CHZZ, NEWP, P376) Slide 9: Quick Link to OPUS from NGS Home Page www.ngs.noaa.gov Using the OPUS Web Page : Using the OPUS Web Page Allowable Data Formats : 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 Slide 12: 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 email address Slide 13: FILE: corv0590.05o 000416827 1008 NOTE: Antenna offsets supplied by the user were zero. Coordinates 1008 returned will be for the antenna reference point (ARP). 1008 NGS OPUS SOLUTION REPORT ======================== USER: [email protected] DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page5 0601.10 master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc0590.05n 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:2002.0000) ITRF00 (EPOCH:2005.1596) X: -2498423.165(m) 0.018(m) -2498423.872(m) 0.018(m) Y: -3802822.048(m) 0.021(m) -3802820.836(m) 0.021(m) Z: 4454737.695(m) 0.024(m) 4454737.792(m) 0.024(m) LAT: 44 35 7.91054 0.002(m) 44 35 7.92698 0.002(m) E LON: 236 41 43.48129 0.014(m) 236 41 43.42434 0.014(m) W LON: 123 18 16.51871 0.014(m) 123 18 16.57566 0.014(m) EL HGT: 107.485(m) 0.034(m) 107.108(m) 0.034(m) ORTHO HGT: 130.010(m) 0.043(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] 4936954.907 105971.557 Easting (X) [meters] 475821.322 2277335.385 Convergence [degrees] -0.21381402 -1.98897497 Point Scale 0.99960719 0.99994603 Combined Factor 0.99959034 0.99992918 US NATIONAL GRID DESIGNATOR: 10TDQ7582136955(NAD 83) BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N443506.072 W1240342.736 60138.7 AJ6959 CHZZ CAPE MEARS CORS ARP N452911.437 W1235841.187 113322.4 DH4503 P376 EOLARESVR_OR2004 CORS ARP N445628.313 W1230608.100 42648.2 NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N443507.910 W1231816.519 0.0 OPUS OutputStandard Reading OPUS Output : USER: [email protected] DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page5 0601.10 master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc0590.05n 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 email address & observation file. Solution run date & time Reading OPUS Output con’t. : USER: [email protected] DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page5 0601.10 master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc0590.05n 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 : 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 0.030 m OVERALL RMS: 0.013(m) In case of bad statistics, try choosing different CORS and re-submit. Reading OPUS Output con’t. Solution/Coordinates : REF FRAME: NAD_83(CORS96)(EPOCH:2002.0000) ITRF00 (EPOCH:2005.1596) X: -2498423.165(m) 0.018(m) -2498423.872(m) 0.018(m) Y: -3802822.048(m) 0.021(m) -3802820.836(m) 0.021(m) Z: 4454737.695(m) 0.024(m) 4454737.792(m) 0.024(m) LAT: 44 35 7.91054 0.002(m) 44 35 7.92698 0.002(m) E LON: 236 41 43.48129 0.014(m) 236 41 43.42434 0.014(m) W LON: 123 18 16.51871 0.014(m) 123 18 16.57566 0.014(m) EL HGT: 107.485(m) 0.034(m) 107.108(m) 0.034(m) ORTHO HGT: 130.010(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 Compute Errors? : How Does OPUS Compute Errors? E W S N 1 σ standard deviation peak-to-peak error more conservative ~ 2 σ peak-to-peak distances OPUS Output con’t. Grid Coordinates : UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] 4936954.907 105971.557 Easting (X) [meters] 475821.322 2277335.385 Convergence [degrees] -0.21381402 -1.98897497 Point Scale 0.99960719 0.99994603 Combined Factor 0.99959034 0.99992918 US NATIONAL GRID DESIGNATOR: 10TDQ7582136955(NAD 83) Universal Transverse Mercator (UTM) coordinates State Plane coordinates (if requested) US National Grid OPUS Output con’t. Grid Coordinates READING OPUS OUTPUT (control) : BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N443506.072 W1240342.736 60138.7 AJ6959 CHZZ CAPE MEARS CORS ARP N452911.437 W1235841.187 113322.4 DH4503 P376 EOLARESVR_OR2004 CORS ARP N445628.313 W1230608.100 42648.2 NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N443507.910 W1231816.519 0.0 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 How Can I Improve My Results? : 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 Distribution of Horizontal Offset from Accepted Values : Distribution of Horizontal Offset from Accepted Values 0.8 cm N-S RMS 1.4 cm E-W RMS > 200 CORS 2 hours of data Distribution of Vertical Offset from Accepted Values : Distribution of Vertical Offset from Accepted Values 1.9 cm RMS All mean offsets < 1 mm > 200 CORS 2 hours of data How do I get help? : How do I get help? Study the Guidelines under “Using OPUS” Submit specific questions, comments or suggestions using “Contact OPUS” link Study the answers under “FAQs” The RSGPS program andOPUS - RS : The RSGPS program andOPUS - RS Getting There Faster – OPUS-RS : OPUS-RS Uses RSGPS program instead of PAGES Uses P1 and P2 as well as L1 and L2 obs Resolves all ambiguities with LAMBDA Geometry free linear combination used to determine DD ionospheric delays OPUS-RS search algorithm : OPUS-RS search algorithm Sort stations in CORS network by distance from rover. Select up to nine CORS that are less than 250 km from rover and that have suitable data. No solution is attempted if fewer than three CORS selected. No solution attempted if distance from rover to polygon enclosing selected CORS is greater than 50 km. 250 km limit <50 km OPUS-RS : OPUS-RS OPUS-RS uses RSGPS in two modes: Network and Rover In network mode, at least one hour of data from the selected CORS are used to solve for ambiguities, tropospheric refraction, and double difference ionospheric delays at these CORS. The positions of the CORS are held fixed. In rover mode, ionospheric delays and troposphere parameters are interpolated (or extrapolated) from the selected CORS to rover. Then the delays at the rover are constrained to solve for the position of the rover. Again, the positions of the CORS are held fixed. RSGPS is based (conceptually) on the MPGPS program developed at the Ohio State University. OPUS-RS : OPUS-RS Produces solution with 15 minutes of data (vs. 2 hours for current OPUS) Slide 31: To improve accuracy and reliability: Collect observations for more than 15 minutes Perform multiple observing sessions Avoid conditions that perturb the GPS signal—unsettled weather, solar flares, multipath (nearby reflective surfaces) OPUS-RS : OPUS-RS User interface is almost identical to regular OPUS, including Options page Output report is similar to regular OPUS, but with quality indicators based on the W-ratio from the LAMBDA validation tests The normalized RMS is a unitless measure of the scatter in the data misfits No peak-to-peak variations OPUS-RS Output Report : NGS OPUS-RS SOLUTION REPORT ======================== USER: [email protected] DATE: March 16, 2007 RINEX FILE: vari045a.07o TIME: 11:40:07 UTC SOFTWARE: rsgps 1.06 RS26.prl START: 2007/02/14 00:00:30 EPHEMERIS: igs14143.eph [precise] STOP: 2007/02/14 00:59:30 NAV FILE: brdc0450.07n OBS USED: 2784 / 2994 : 93% ANT NAME: TRM41249.00 QUALITY IND. 21.91/ 64.08 ARP HEIGHT: 2.0 NORMALIZED RMS: 0.295 REF FRAME: NAD_83(CORS96)(EPOCH:2002.0000) ITRF00 (EPOCH:2007.12086) X: 1108081.771(m) see 1108081.069(m) see Y: -4958243.092(m) accuracy -4958241.626(m) accuracy Z: 3843038.534(m) note 3843038.407(m) note LAT: 37 17 23.88604 37 17 23.91389 E LON: 282 35 51.40742 282 35 51.39258 W LON: 77 24 8.59258 77 24 8.60742 EL HGT: -10.287(m) -11.624(m) ORTHO HGT: 23.244(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 18) SPC (4502 VA S) Northing (Y) [meters] 4129746.071 1106727.888 Easting (X) [meters] 287042.763 3597320.710 Convergence [degrees] -1.45603091 0.66616871 Point Scale 1.00015868 0.99994631 Combined Factor 1.00016029 0.99994793 OPUS-RS Output Report OPUS-S vs. OPUS-RS : 34 OPUS-S vs. OPUS-RS What are the fundamental differences between OPUS-Static (OPUS-S) and OPUS-Rapid Static (OPUS-RS)? OPUS-S vs. OPUS-RS : 35 OPUS-S vs. OPUS-RS OPUS-S requires at least two hours of GPS data from the rover, together with the same amount of data from 3 CORS (preferably located within 600 km of the rover), to solve for * the rover’s coordinates, * atmospheric refraction parameters at both the rover and the 3 CORS, and * integer ambiguities (in the doubly differenced phase observations). OPUS-S vs. OPUS-RS : 36 OPUS-S vs. OPUS-RS OPUS-RS involves a 3-step process: * Use at least one hour of GPS data from 3 to 9 CORS (located within 250 km of the rover) to solve for atmospheric refraction parameters at these CORS. * Interpolate (or extrapolate) these refraction parameters to predict corresponding refraction parameters at the rover. * Use at least 15 minutes of GPS data at the rover, together with the same amount of data at the nearby CORS to solve for: - the rover’s coordinates and - integer ambiguities. OPUS-S vs. OPUS-RS : 37 OPUS-S vs. OPUS-RS What is IDOP? : 38 What is IDOP? The interpolative dilution of precision (IDOP) is a unitless number that quantifies the local geometric strength of the CORS network relative to the rover’s location in terms of how well atmospheric conditions at nearby CORS can be interpolated (or extrapolated) to predict corresponding atmospheric conditions at the rover. What is IDOP? : 39 What is IDOP? If there are several (at least 3) CORS located within 250 km of the rover and we have estimated an atmospheric parameter for each of these CORS with a standard error of σ, then the corresponding atmospheric parameter at the rover can be predicted with a standard error of σR = (IDOP) • σ . Hence, the smaller the value of IDOP the better. What is IDOP? : 40 What is IDOP? Let (xi , yi) denote the location of the i-th CORS in the xy-plane for i = 1,2,3,…,n and let (x0 , y0) denote the location of the rover in the xy-plane, then IDOP = (R/Q)0.5 where R = (∑∆xi2)(∑∆yi2) – (∑∆xi∆yi)2 and Q = nR + 2(∑∆xi)(∑∆yi)(∑∆xi∆yi) – (∑∆xi)2(∑∆yi2) – (∑∆yi)2(∑∆xi2) Here ∆xi = xi – x0 and ∆yi = yi – y0 for i = 1,2, 3,…,n. IDOP VALUES AS A FUNCTION OF LOCATION EXAMPLE FOR THE CASE OF 4 CORS LOCATED AT THE CORNERS OF A SQUARE : IDOP VALUES AS A FUNCTION OF LOCATION EXAMPLE FOR THE CASE OF 4 CORS LOCATED AT THE CORNERS OF A SQUARE Best IDOP = 1/√ N where N denotes the number of CORS. Best IDOP occurs at the centroid of the CORS. With these 4 CORS, the best IDOP = 0.5 and IDOP increases as the distance of the rover from the centroid increases. With 9 CORS, IDOP would equal 0.33 at the centroid of the CORS. OPUS-RS Accuracy Depends on both IDOP and RMSD : 42 OPUS-RS Accuracy Depends on both IDOP and RMSD RMSD = Root mean square distance = [ ( ∑ di2 ) / n ]0.5 where di is the distance between the rover and the i-th CORS, and n equals the number of CORS being used. STDERR(north) ≈ [ (1.8cm•IDOP)2 + (0.05ppm•RMSD)2 ]0.5 STDERR(east) ≈ [ (1.8cm•IDOP)2 + (0.05ppm•RMSD)2 ]0.5 STDERR(up) ≈ [ (6.7cm•IDOP)2 + (0.15ppm•RMSD)2 ]0.5 Vertical standard error achievable in CONUS when a user submits 15 minutes of GPS data to OPUS-RS : Vertical standard error achievable in CONUS when a user submits 15 minutes of GPS data to OPUS-RS Vertical Standard error achievable in Alaska when a user submits 15 minutes of GPS data to OPUS-RS : Vertical Standard error achievable in Alaska when a user submits 15 minutes of GPS data to OPUS-RS Vertical standard error achievable in Hawaii when a user submits 15 minutes of GPS data to OPUS-RS : Vertical standard error achievable in Hawaii when a user submits 15 minutes of GPS data to OPUS-RS Vertical standard error achievable near Puerto Rico when a user submits 15 minutes of GPS data to OPUS-RS : Vertical standard error achievable near Puerto Rico when a user submits 15 minutes of GPS data to OPUS-RS OPUS (Online Positioning User Service) : OPUS (Online Positioning User Service) combined OPUS add-ons : DEFAULTS: $$$ receiver hours of data one receiver no archive no delimiters US only GPS only OPUS add-ons ¢¢ receivers OPUS mapper minutes of data OPUS-RS multiple receivers OPUS-projects share results OPUS-DB delimited results OPUS-XML global results OPUS-global GNSS signals OPUS-GNSS D heights OPUS-leveling Operational components are available at http://www.ngs.noaa.gov/OPUS/ Prototype components are available at http://beta.ngs.noaa.gov/OPUS/ Slide 51: FILE: corv0590.05o 000416827 1008 NOTE: Antenna offsets supplied by the user were zero. Coordinates 1008 returned will be for the antenna reference point (ARP). 1008 NGS OPUS SOLUTION REPORT ======================== USER: [email protected] DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page5 0601.10 master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc0590.05n 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:2002.0000) ITRF00 (EPOCH:2005.1596) X: -2498423.165(m) 0.018(m) -2498423.872(m) 0.018(m) Y: -3802822.048(m) 0.021(m) -3802820.836(m) 0.021(m) Z: 4454737.695(m) 0.024(m) 4454737.792(m) 0.024(m) LAT: 44 35 7.91054 0.002(m) 44 35 7.92698 0.002(m) E LON: 236 41 43.48129 0.014(m) 236 41 43.42434 0.014(m) W LON: 123 18 16.51871 0.014(m) 123 18 16.57566 0.014(m) EL HGT: 107.485(m) 0.034(m) 107.108(m) 0.034(m) ORTHO HGT: 130.010(m) 0.043(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] 4936954.907 105971.557 Easting (X) [meters] 475821.322 2277335.385 Convergence [degrees] -0.21381402 -1.98897497 Point Scale 0.99960719 0.99994603 Combined Factor 0.99959034 0.99992918 US NATIONAL GRID DESIGNATOR: 10TDQ7582136955(NAD 83) BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N443506.072 W1240342.736 60138.7 AJ6959 CHZZ CAPE MEARS CORS ARP N452911.437 W1235841.187 113322.4 DH4503 P376 EOLARESVR_OR2004 CORS ARP N445628.313 W1230608.100 42648.2 NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N443507.910 W1231816.519 0.0 OPUS Output - Standard FILE: corv0590.05o 000416827 1008 NOTE: Antenna offsets supplied by the user were zero. Coordinates 1008 returned will be for the antenna reference point (ARP). 1008 NGS OPUS SOLUTION REPORT ======================== USER: [email protected] DATE: January 13, 2006 RINEX FILE: corv059f.05o TIME: 19:08:14 UTC SOFTWARE: page5 0601.10 master3.pl START: 2005/02/28 05:00:00 EPHEMERIS: igs13121.eph [precise] STOP: 2005/02/28 06:59:30 NAV FILE: brdc0590.05n 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:2002.0000) ITRF00 (EPOCH:2005.1596) X: -2498423.165(m) 0.018(m) -2498423.872(m) 0.018(m) Y: -3802822.048(m) 0.021(m) -3802820.836(m) 0.021(m) Z: 4454737.695(m) 0.024(m) 4454737.792(m) 0.024(m) LAT: 44 35 7.91054 0.002(m) 44 35 7.92698 0.002(m) E LON: 236 41 43.48129 0.014(m) 236 41 43.42434 0.014(m) W LON: 123 18 16.51871 0.014(m) 123 18 16.57566 0.014(m) EL HGT: 107.485(m) 0.034(m) 107.108(m) 0.034(m) ORTHO HGT: 130.010(m) 0.043(m) [Geoid03 NAVD88] UTM COORDINATES STATE PLANE COORDINATES UTM (Zone 10) SPC (3601 OR N) Northing (Y) [meters] 4936954.907 105971.557 Easting (X) [meters] 475821.322 2277335.385 Convergence [degrees] -0.21381402 -1.98897497 Point Scale 0.99960719 0.99994603 Combined Factor 0.99959034 0.99992918 US NATIONAL GRID DESIGNATOR: 10TDQ7582136955(NAD 83) BASE STATIONS USED PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m) AH2489 NEWP NEWPORT CORS ARP N443506.072 W1240342.736 60138.7 AJ6959 CHZZ CAPE MEARS CORS ARP N452911.437 W1235841.187 113322.4 DH4503 P376 EOLARESVR_OR2004 CORS ARP N445628.313 W1230608.100 42648.2 NEAREST NGS PUBLISHED CONTROL POINT AH2486 CORVALLIS CORS ARP N443507.910 W1231816.519 0.0 <?xml version="1.0" encoding="UTF-8"?> <OPUS_SOLUTION> <USER_INFORMATION> <USER_EMAIL> [email protected] </USER_EMAIL> <SOLUTION_DATE> February 19, 2008 </SOLUTION_DATE> <SOLUTION_TIME> 01:16:22 UTC </SOLUTION_TIME> <RINEX_FILE_NAME> zzyy1500.07o </RINEX_FILE_NAME> </USER_INFORMATION> <DATA_INFORMATION> <SOFTWARE> <PAGES_VERSION> page5 0612.06 </PAGES_VERSION> <OPUS_VERSION> master3.pl </OPUS_VERSION> </SOFTWARE> <EMPHEMERIS> igs14293.eph [precise] </EMPHEMERIS> <NAV_FILE> brdc1500.07n </NAV_FILE> <ANTENNA_NAME> TRM41249.00 NONE </ANTENNA_NAME> <ARP_HEIGHT> 0.0 </ARP_HEIGHT> <START_TIME> 2007/05/30 00:00:00 </START_TIME> <END_TIME> 2007/05/30 23:59:00 </END_TIME> <OBS_USED> <NUMBER_USED> 52955 </NUMBER_USED> <TOTAL_OBS> 55069 </TOTAL_OBS> <PERCENTAGE> 96 </PERCENTAGE> </OBS_USED> <FIXED_AMB> <NUMBER_FIXED> 218 </NUMBER_FIXED> <NUMBER_AMB> 242 </NUMBER_AMB> <PERCENTAGE> 90 </PERCENTAGE> </FIXED_AMB> <OVERALL_RMS UNIT="m"> 0.021 </OVERALL_RMS> </DATA_INFORMATION> <POSITION> <REF_FRAME> NAD_83(CORS96) </REF_FRAME> <EPOCH> 2002.0000 </EPOCH> <COORD_SET> <RECT_COORD> <COORDINATE AXIS="X" UNIT="m" UNCERTAINTY="0.003"> -496255.901 </COORDINATE> <COORDINATE AXIS="Y" UNIT="m" UNCERTAINTY="0.022"> -5510741.494 </COORDINATE> <COORDINATE AXIS="Z" UNIT="m" UNCERTAINTY="0.017"> 3162058.243 </COORDINATE> </RECT_COORD> <ELLIP_COORD> <LAT> <DEGREES> 29 </DEGREES> <MINUTES> 54 </MINUTES> <SECONDS> 48.44070 </SECONDS> <UNCERTAINTY> 0.003 </UNCERTAINTY> <UNCERTAINTY_UNIT>m </UNCERTAINTY_UNIT> </LAT> <EAST_LONG> <DEGREES>264 </DEGREES> <MINUTES>51</MINUTES> <SECONDS>15.31122</SECONDS> <UNCERTAINTY>0.002</UNCERTAINTY> <UNCERTAINTY_UNIT>m</UNCERTAINTY_UNIT> </EAST_LONG> <EL_HEIGHT> <VALUE>-7.199</VALUE> <UNCERTAINTY>0.027</UNCERTAINTY> <UNCERTAINTY_UNIT>m</UNCERTAINTY_UNIT> </EL_HEIGHT> </ELLIP_COORD> </COORD_SET> </POSITION> <POSITION> <REF_FRAME>ITRF00 (EPOCH:2007.4096)</REF_FRAME> <EPOCH>2007.4096</EPOCH> <COORD_SET> <RECT_COORD> <COORDINATE AXIS="X" UNIT="m" UNCERTAINTY="0.003">-496256.585</COORDINATE> <COORDINATE AXIS="Y" UNIT="m" UNCERTAINTY="0.022">-5510740.027</COORDINATE> <COORDINATE AXIS="Z" UNIT="m" UNCERTAINTY="0.017">3162058.057</COORDINATE> </RECT_COORD> <ELLIP_COORD> <LAT> <DEGREES>29</DEGREES> <MINUTES>54</MINUTES> <SECONDS>48.45813</SECONDS> <UNCERTAINTY>0.003</UNCERTAINTY> <UNCERTAINTY_UNIT>m</UNCERTAINTY_UNIT> </LAT> <EAST_LONG> <DEGREES>264</DEGREES> <MINUTES>51</MINUTES> <SECONDS>15.28092</SECONDS> <UNCERTAINTY>0.002</UNCERTAINTY> <UNCERTAINTY_UNIT>m</UNCERTAINTY_UNIT> </EAST_LONG> <EL_HEIGHT> <VALUE>-8.505</VALUE> <UNCERTAINTY>0.027</UNCERTAINTY> <UNCERTAINTY_UNIT>m</UNCERTAINTY_UNIT> </EL_HEIGHT> </ELLIP_COORD> </COORD_SET> </POSITION> <ORTHO_HGT UNCERTAINTY="0.037" UNIT="m" SOURCE="[Geoid03 NAVD88]">20.154</ORTHO_HGT> <PLANE_COORD_INFO> <PLANE_COORD_SPEC TYPE="UTM" ZONE="15"> <NORTHING UNIT="m">3311130.625</NORTHING> <EASTING UNIT="m">292843.826</EASTING> <CONVERGENCE UNIT="deg">-1.07044705</CONVERGENCE> <SCALE>1.00012949</SCALE> <CF>1.00013062</CF> </PLANE_COORD_SPEC> <PLANE_COORD_SPEC TYPE="SPC" ZONE="4204(TXSC )"> <NORTHING UNIT="m">4236668.327</NORTHING> <EASTING UNIT="m">972105.452</EASTING> <CONVERGENCE UNIT="deg">1.88824726</CONVERGENCE> <SCALE>0.99991407</SCALE> <CF>0.99991520</CF> </PLANE_COORD_SPEC> <USNG>15RTP9284411131(NAD 83) </USNG> </PLANE_COORD_INFO> <BASE_STATION_USED> <PID>DE5999</PID> <STATION_ID>ADKS</STATION_ID> <DESIGNATION>ADDICKS 1795 CORS ARP</DESIGNATION> <LATITUDE>N294727.47185</LATITUDE> <LONGITUDE>W0953511.04262</LONGITUDE> <DISTANCE>44692.309</DISTANCE> </BASE_STATION_USED> <BASE_STATION_USED> <PID>DJ8995</PID> <STATION_ID>ROD1</STATION_ID> <DESIGNATION>ROD1 CORS ARP</DESIGNATION> <LATITUDE>N300420.45377</LATITUDE> <LONGITUDE>W0953136.45801</LONGITUDE> <DISTANCE>40769.489</DISTANCE> </BASE_STATION_USED> <BASE_STATION_USED> <PID>DH3612</PID> <STATION_ID>TXLI</STATION_ID> <DESIGNATION>LIBERTY CORS ARP</DESIGNATION> <LATITUDE>N300321.18092</LATITUDE> <LONGITUDE>W0944615.67967</LONGITUDE> <DISTANCE>39457.656</DISTANCE> </BASE_STATION_USED> <NGS_PUBLISHED_CONTROL_POINT> <PID>AA9861</PID> <DESIGNATION>LAKE HOUSTON 2050 CORS L1 PHS </DESIGNATION> <LATITUDE>N295448.44005</LATITUDE> <LONGITUDE>W0950844.68949</LONGITUDE> <DISTANCE>0.000</DISTANCE> </NGS_PUBLISHED_CONTROL_POINT> <NOTE> 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. </NOTE> </OPUS_SOLUTION> OPUS Output - XML OPUS Concept : OPUS websitehttp://geodesy.noaa.gov/OPUS yourdatasheet QA/QC OPUS Concept antenna type, height control stationphoto * control station description * control station monument register your agency ------public datasheet review OPUS  Datasheet Concept *optional for “existing” stations. GPS data (4+hr, good stats) Slide 53: Stable Permanent Unique Recoverable Safe US COAST & GEODETIC SURVEY --|-- control station monument control station requirements GPS data 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 GPS data (4+hr, good stats) metadata requirements : *optional for “existing” stations. control station description * control stationphoto * metadata requirements Simplified bluebooking antenna type, height Slide 56: Demonstration Application II Img from sample datasheet : Img from sample datasheet CONTROLLING A BRIDGE SURVEY : CONTROLLING A BRIDGE SURVEY The accompanying slides were presented at the 2002 CORS Forum by Gary Thompson of the North Carolina Geodetic Survey. Using OPUS to control Bridges : Using OPUS to control Bridges On a typical bridge job, NCDOT Sets an azimuth pair ( ) Uses approximately 6-7 control panels ( ) Controls the site with 2 receivers Slide 60: P1 P2 P3 P4 P5 P6 Slide 61: B9999-1 B9999-2 P1 P2 P3 P4 P5 P6 Field Work is now complete. : Field Work is now complete. The following steps need to be taken to finish the process: Slide 63: Office Process Download the Raw Data and RTK dc files Convert both blocks of raw data to RINEX format using Trimble’s utility Upload the files to: http://www.ngs.noaa.gov/OPUS/ Receive the results from OPUS via email in minutes Slide 64: Continued... Import the dc file into Trimble Geomatics Office Update the initial base position for the first base to the coordinates provided by OPUS1 After a recompute, everything in the dc file should be corrected relative to the first base location (OPUS1) Slide 65: Continued ... The position for OPUS2 is only used for comparison to what was derived from OPUS1 Coordinates can now be utilized as needed Slide 66: OPUS & RTK Savings to NCDOT * The cell phone listed in the OPUS & RTK surveying comparison was not used in the survey work, but was available for contacting the office. HOW IS THE ANTENNA HEIGHT MEASURED? : HOW IS THE ANTENNA HEIGHT MEASURED? WHY DO I NEED THE ANTENNA TYPE? : 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 Slide 69: Antenna Calibration Facility in Corbin, Virginia Slide 70: Note that SV elevation and varying phase patterns affect signal interpretation differently . . . . . . . . . . . . SV 14 SV 14 SV 20 SV 20 Antenna Type A Antenna Type B Antenna Phase Center Variation Slide 71: . . . . . . . . . . . . SV 14 SV 14 SV 20 SV 20 Antenna Type A Antenna Type B Different Phase Patterns Note that SV elevation and varying phase patterns affect signal interpretation differently Antenna Phase Center Variation Slide 72: ELECTRONIC PHASE CENTER Elevation Angle (deg.) Phase Center Variation (mm) Recent Solutions : Recent Solutions “OPUS Projects”—under construction : “OPUS Projects”—under construction OPUS files identified as belonging to a project are directed to appropriate directories Project data submission organized Reports sent to project managers Station data checked and edited as needed PAGES software used to process each GPS observing session individually Consistent coordinates for all occupied reference stations are determined by a rigorous least squares adjustment of all GPS data observed during the project , together with selected CORS data.

Related presentations


Other presentations created by palmettoequipment

Sokkia SRX Product Introduction
16. 04. 2008
0 views

Sokkia SRX Product Introduction

Working with MMC and ARCPAD
16. 04. 2008
0 views

Working with MMC and ARCPAD

SC VRS Geodedic Survey Slideshow
16. 04. 2008
0 views

SC VRS Geodedic Survey Slideshow

GSR2700IS
17. 04. 2008
0 views

GSR2700IS