AI Assistant
Notifications
Clear all

NGS Data Sheet Vertical Accuracy

8 Posts
8 Users
0 Reactions
1,056 Views
Larry P
(@larry-p)
Posts: 1121
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I have an NGS Data Sheet that shows the vertical accuracy as "Vert Order Third ?".

Don't think I've ever seen the accuracy listed as "Third ?" Very odd.

I have long hours GPS occupation of the point for 4 days this week. The OPUS reports are fairly consistent. The elevation range on our OPUS points is .15 feet. But, that range differs from the published elevation (Third ?) by right at 1 foot.

I called NGS and they told me that it wasn't unreasonable for my data to vary ~ 1 foot for a "Third ?" order elevation.

That brings up two questions.

One, is a difference of 1 foot really reasonable?

Two, when I publish my final data how much should I emphasize the difference between my answer and the existing NGS elevation?

Thoughts?

Larry P


 
Posted : August 23, 2013 2:13 pm
jhframe
(@jim-frame)
Posts: 7465
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Datum difference? VERTCON error? Subsidence/uplift?


 
Posted : August 23, 2013 2:31 pm
foggyidea
(@foggyidea)
Posts: 3462
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

NGVD vs, NAVD? that's about the difference we're finding around here...


 
Posted : August 23, 2013 2:33 pm
Tom Adams
(@tom-adams)
Posts: 3453
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Am I mistaken, or wouldn't that mean that the elevation on the point was determined based on a 3rd-order level run? Wouldn't that mean it has nothing to do with the datum or that sort of factor? I must be wrong if you are talking about being +/-1 foot.


 
Posted : August 23, 2013 3:23 pm
spledeus
(@spledeus)
Posts: 2757
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

3rd order is 0.05' per root mile. This should not be the cause of your headache.

You can convert the metric if you want:

From Benchmark Reset Procedures Manual, Curtis L. Smith, NGS, May, 2007.

Good luck, Thadd


 
Posted : August 23, 2013 3:42 pm

bill93
(@bill93)
Posts: 9977
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I don't think most NGS data sheets give ellipsoidal heights, which is what GPS inherently measures. There is a geoid model involved in getting from ellipsoidal to orthometric. How good is the geoid model in your area?

The order of the point is defined as others have mentioned by relative accuracy to other nearby benchmarks, and not by accuracy relative to ellipsoidal and geoid. So it's apples and pomegranates.


 
Posted : August 23, 2013 7:26 pm
geeoddmike
(@geeoddmike)
Posts: 1556
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Howdy,

It would be helpful if you had provided the PID. Nonetheless, the answer to questions about all elements on a data sheet are found in the file: dsdata.txt

It can be viewed/downloaded at: http://www.ngs.noaa.gov/cgi-bin/ds_lookup.prl?Item=DSDATA.TXT

The relevant section is copied below:

ORDER AND CLASS: ORTHOMETRIC VERTICAL
*************************************
Vertical station order and class for first-, second-, and
third-order stations are defined in the Federal Geodetic Control
Committee publication "Standards and Specifications for Geodetic
Control Networks". In addition:

Normal bench marks with unknown order will display a '?'.
Vertical control which were determined only for the purpose of
supplying a height for Horizontal Distance Reductions are
assigned an order of 'THIRD'. If these types of heights do
not have supporting observations then the Order is displayed
as 'THIRD ?'.

Obviously these heights are not intended for use as benchmarks, i.e. not the origin of height projects nor as checks on benchmarks.

Cheers,

DMM


 
Posted : August 23, 2013 11:00 pm
Cliff Mugnier
(@cliff-mugnier)
Posts: 1220
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I never knew that; thanks for the explanation.


 
Posted : August 24, 2013 12:36 pm