NO A A Technical M em orandum NO S NG S -58 G U ID ELIN ES FO R ES TA B LISH IN G G PS -D ER IVE D E LLIPS O ID H EIG H TS (STANDARDS:2 CM AND 5 CM ) VER SIO N 4.3 D avid B .Zilkoski Joseph D .D 'O nofrio Stephen J.Frakes Silver S pring,M D N ovem ber 1997 U.S.D E P A RTMENT OF NationalOceanic and N ationalO cean N ationalG eodetic COMMERCE Atm ospheric A dm inistration S ervice S urvey
34
Embed
B ≥ 4 H & V, KNOWN & TRUSTED POINTS? B LOCALIZATION RESIDUALS-OUTLIERS? B DO ANY PASSIVE MARKS NEED TO BE HELD? RT BASE WITHIN CALIBRATION (QUALITY TIE.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
N O A A T e c h n ic a l M e m o r a n d u m N O S N G S - 5 8
G U ID E L IN E S F O R E S T A B L IS H IN G G P S - D E R IV E D E L L IP S O ID H E IG H T S( S T A N D A R D S : 2 C M A N D 5 C M )V E R S IO N 4 .3
D a v id B . Z i lk o s k iJ o s e p h D . D 'O n o f r ioS t e p h e n J . F r a k e s
S i lv e r S p r in g , M D
N o v e m b e r 1 9 9 7
U . S . D E P A R T M E N T O F N a t i o n a l O c e a n i c a n d N a t i o n a l O c e a n N a t i o n a l G e o d e t i cC O M M E R C E A t m o s p h e r i c A d m i n i s t r a t i o n S e r v ic e S u r v e y
• B ≥ 4 H & V, KNOWN & TRUSTED POINTS?• B LOCALIZATION RESIDUALS-OUTLIERS?• B DO ANY PASSIVE MARKS NEED TO BE
HELD?• RT BASE WITHIN CALIBRATION (QUALITY TIE
TO NEAREST CALIBRATION POINT)?• B SAME OFFICE & FIELD CALIBRATION
USED?
CONSTRAINTS (OR NOT)
FYI: GNSS CAN PROVIDE GOOD RELATIVE POSITIONS IN A PROJECT WHILE STILL NOT CHECKING TO KNOWNS IN AN ABSOLUTE SENSE
TWO POINT CALIBRATION
RT DERIVED ORTHO HEIGHTS - LOCALIZE OR NOT?
• PASSIVE MARKS ARE A SNAP SHOT OF WHEN THEY WERE LEVELED OR DERIVED FROM GPS
• IF YOU BUILD FROM A MONUMENTED BM AND THE DESIGN WAS DONE REFERENCED TO IT, IT IS “THE TRUTH”, UNLESS IN GROSS ERROR.
• CONSTRAINING TO PASSIVE BMs IS A GOOD WAY TO NOT ONLY LOCK TO THE SURROUNDING PASSIVE MARKS, BUT ALSO TO EVALUATE HOW THE CONTROL FITS TOGETHER.
• HOW GOOD IS THE NGS HYBRID GEOID MODEL IN YOUR AREA? (SIDE NOTE: GEOID 09 IS THE CURRENT MODEL USED BY OPUS)
CALIBRATIONS/VERTICAL LOCALIZATIONS
HOW FAR CAN I GO BEFORE MY LEVELED DIFFERENCES ARE DIFFERENT FROM MY ORTHOMETRIC HEIGHT DIFFERENCES?
LVL_DH Program
Program LVL_DH converts the published orthometric height difference between two NAVD 88 bench marks into a leveled height difference by removing the orthometric correction from the published relative height. This process requires the exact gravity values at the two bench marks used in the NAVD 88 adjustment. These gravity values are maintained by NGS in its data base.
ROD & INSTRUMENT CORRECTIONS
ORTHOMETRIC HEIGHT CORRECTION
EXAMPLE
LVL_DH OUT
GNSS DERIVED HEIGHTS Summary of expected orthometric height precisions/accuracies- 95%
ConfidenceREMEMBER REDUNDANCY AND A CHECK ON KNOWN POINTS CORS = 0.05 m
OPUS-S = 0.05 m
OPUS-RS = 0.05 m
NGS 58/59 = 0.02 m local, 0.05 m to NSRS
SINGLE BASE REAL TIME = 0.02 m ≤ 10 Km, remember GIGO
RTN = 0.05- 0.08 m,
ELLIPSOID, GEOID & ORTHO HEIGHTS
H88 = h83 – N03
NAD 83 (HARN) USE GEOID O3NAD 83 (CORS 96) USE GEOID 09
ITRF USE SCIENTIFIC GEOID (USGG)
USING GNSS MANUFACTURER’S SOFTWARE- TGO
N O A A T e c h n ic a l M e m o r a n d u m N O S N G S - 5 8
G U ID E L IN E S F O R E S T A B L IS H IN G G P S - D E R IV E D E L L IP S O ID H E IG H T S( S T A N D A R D S : 2 C M A N D 5 C M )V E R S IO N 4 .3
D a v id B . Z i lk o s k iJ o s e p h D . D 'O n o f r ioS t e p h e n J . F r a k e s
S i lv e r S p r in g , M D
N o v e m b e r 1 9 9 7
U .S . D E P A R T M E N T O F N a t io n a l O c e a n ic a n d N a t io n a l O c e a n N a t io n a l G e o d e t icC O M M E R C E A t m o s p h e r ic A d m in is t r a t io n S e r v ic e S u r v e y
Available “On-Line” atthe NGS Web Site:
www.ngs.noaa.gov
SEARCH: “NGS 58”
Network / Local Accuracy
NSRS
HARN/Control Stations(75 km)
Primary Base(40 km)
Secondary Base(15 km)
Local Network Stations(7 to 10 km)
GPS ELLIPSOID HEIGHT HIERARCHY
DATA COLLECTION PARAMETERS
• VDOP < 6 for 90% or longer of 30 minute session– Shorter session lengths stay < 6 always– Schedule travel during periods of higher VDOP
• Session lengths for baselines ≤ 10 KM = 30 minutes & collect at 5 second data interval
• Session lengths for baselines 10 – 15 KM = 1 hour & collect at 15 second data interval
• Track satellites down to 10° elevation angle
REDUNDANCY
If extra measurements are included then a least squares adjustment will provide a check on the accuracy of control point coordinates and can also be used to identify bad observations.
More measurements should be included than the minimum - needed to determine the origin and possibly the orientation and scale of the survey
Redundant measurements taken with different satellites and satellite geometry provide a mitigation for multipath effects.
Each local station must have at least two acceptable baselines to its closest neighbor
Comparison of 30 Minute Solutions - Precise Orbit; Hopfield (0); IONOFREE(30 Minute solutions computed on the hour and the half hour)
HARDWARE BIASES, REDUCES NOISE PARAMETERS)• PRECISE EPHEMERIS (14 DAYS LATENCY)• 15° CUT OFF• FIX ALL INTEGERS FOR BASELINES LESS THAN 40 KM• USE A TROPO MODEL RATHER THAN FIELD MET DATA UNLESS
PROVEN BETTER• USE RELATIVE TROPO SCALE PARAMETER FOR STATIONS OVER
15 KM AND FOR LARGE INTERSTATION RELIEF• BASELINE RMS ≤ 1.5 CM• REDUNDANT BASELINES DIFFER BY ≤ 2.0 CM IN ELLIPSOID
HEIGHT
ADJUSTMENT OF PRIMARY NETWORK STATIONS FROM CONTROL
• Minimum Constrained [One fixed station]– Fix latitude, longitude and ellipsoid height at one station– Resolve all blunders and large residuals– Determine which Control and known Primary Base
Station coordinates should be fixed
• Constrained [All suitable stations fixed]– Fix latitude, longitude, and ellipsoid heights at Control
and known Primary Base Stations– Make sure the constraints did not distort the project
• Minimum Constrained [One fixed station]– Fix latitude, longitude and ellipsoid height at one station– Resolve all blunders and large residuals– Evaluate coordinates at Control and Primary Base
Station• should not be greatly affected by Local Station
baselines (similar to NAD 83 NSRS 2007 VS. CORS 96)
• Constrained [All suitable stations fixed]– Fix latitude, longitude, and ellipsoid heights at Control
and Primary Base Stations– Make sure the constraints did not distort the project
NOTE - Geoid model NOT applied at this time
Summary-Vector Processing Accomplished
• Elevation Mask - 15 degrees
• Ephemeris - Precise (typ. 14 days latency)• Tropospheric Correction Model• Iono Corrections - All baselines longer than 5
km.• Fix Integers
Baselines less than 5 km: L1 fixed solutionBaselines greater than 5 km: Iono free (L3) solution
• Baselines must have RMS values ≤ 1.5 cm• Baselines must have difference in “up”
ellipsoid height ≤ 2.0 cm
REPEAT BASELINE DIFFERENCES BY DISTANCE
0
1
2
3
4
5
6
0 5000 10000 15000 20000 25000 30000 35000 40000
BASELINE LENGTH (M)
RE
PE
AT
DIF
FE
RE
NC
ES
(C
M)
0113-H83A3.1
1933-01213.1 0092-1933
3.1
6669-00924.7
6669-6666 4.9
172 BASELINES - 3% Above 3 cm
Station pairs with large repeat base line differences also result in large residuals. NGS guidelines for estimating GPS-derived ellipsoid heights require user to re-observe these base lines.
Table 1. -- Summary of Guidelines
Table 1. -- Summary of Guidelines(continued)
Guidelines for EstablishingGPS-Derived Orthometric
Heights(Standards: 2 cm and 5 cm)
http://www.ngs.noaa.gov/ SEARCH: “NGS 59”
3 BASIC RULES:
A Guide for Establishing GPS-Derived Orthometric Heights
(Standards: 2 cm and 5 cm)
• USE NOS-NGS 58 – GPS DERIVED ELLIPSOID HEIGHTS
• USE PUBLISHED NAVD 88 CONTROL
• USE CURRENT HYBRID GEOID MODEL
29
ESTIMATING GPS-DERIVED ORTHOMETRIC HEIGHTS -FOUR BASIC CONTROL REQUIREMENTS
1-Occupy stations with known NAVD 88 orthometric heights (Stations should be evenly distributed throughout project)2-Project areas less than 20 km on a side, surround project with NAVD 88 bench marks, i.e., minimum number of stations is four; one in each corner of project3-Project areas greater than 20 km on a side, keep distances between GPS-occupied NAVD 88 bench marks to less than 20 km
4-Projects located in mountainous regions, occupy bench marks at base and summit of mountains, even if distance is less than 20 km
3-D Vertical Adjustment(Orthometric Heights)
• Minimum Constrained [One fixed station]– Fix latitude, longitude, and orthometric height at one station– Resolve all blunders and large residuals– Compare orthometric heights from adjustment with published
NAVD 88– Determine which NAVD 88 bench marks should be fixed
• Constrained [All suitable orthometric heights fixed]– Fix latitude, longitude at one station– Fix orthometric heights at all suitable stations– Make sure the constraints did not distort the project
COMBINED NETWORK VERTICAL ADJUSTMENT
Combined Network Horizontal Adjustment
• Perform combined adjustment
– Control and Primary Base network along with local network
– Latitude, longitude, and ellipsoid height
• Use GEOID model to obtain geoid heights
• Make sure combined adjustment did not distort the project
SUMMARY• Mistakes (blunders) and systematic errors must be
removed before the adjustment
• A least squares adjustment handles random errors and provides a single solution (Try to eliminate all systematic errors)
• The Minimally Constrained adjustment checks the internal consistency of the network
• The Constrained adjustment checks the existing control and references the network to the datum
• The vertical adjustment estimates GPS-derived Orthometric heights- Approaching 3rd order leveling accuracies
• OPUS with redundant observations can produce 5 cm orthometric heights in areas of high accuracy hybrid geoid coverage
Elevation publishedto centimeters
Orthometric heightdetermined by GPS
Identified as Height Mod survey station
BIG PICTURE ISSUES IN RT POSITIONING
• PASSIVE / ACTIVE – WHAT IS ‘TRUTH’?• GEOID + ELLIPSOID / LOCALIZE –
QUALITY OF GEOID MODELS LOCALLY. ORTHOMETRIC HEIGHTS ON CORS?