Notifications
Clear all

switching from geoid 12b to geoid 18

26 Posts
10 Users
0 Reactions
3 Views
(@casualsurveyor0192)
Posts: 21
Registered
Topic starter
 

Hello all. I recently worked with a surveyor who let me know that geoid 12b is being phased out for geoid 18. I am beggining to start this process but have a few general questions on repercussions. My workflow is essentailly, Do a static survey that is corrected with opus in with a 12b geoid, design a plan based on those coordinates in autocad (i dont think geoid is relevant in cad for this purpose but i could be wrong), put my design points in my controller and stake it in the field.?ÿ

1.) what do i do with all my old data that is in geoid 12b? If I have a design elevation at 800.3 feet that was based on 12b, and I update my controller job settings to 18, wont that through off my elevations??ÿ

?ÿ

2.) Can I get a general overview of how NAVD and geoid 12b/18 interact with regards to elevation? I work in napa county and use their contours as a reference for projects where I do not need to be very precise (I topo a site myself for more exact jobs). their meta data is here . http://gis.napa.ca.gov/giscatalog/viewXML.asp?Name=maingis.GIS.cont_02_200&meta_style=fgdc Their altitude datum is the north american vertical datum of 1988, how much difference is that elevation relative to geoid 12b and 18??ÿ

3.) How do I stay up to date on these changes? I also heard that the US survey feet may be going away and a new coord system is coming out in 2022.?ÿ

 
Posted : 04/02/2020 8:42 am
(@spmpls)
Posts: 656
Registered
 

The differences in geoid heights between 12B and 18 vary by location, primarily because of the densification of available data used for GEOID18 resulting from the GPS on Bench Marks campaign(s). You can use this tool to compute a GEOID18 geoid height (N) for your project location, then compare that to what the geoid height was for 12B. The difference will be the amount your derived orthometric height will change depending on which geoid model you apply to the ellipsoid height(s).

https://www.ngs.noaa.gov/GEOID/GEOID18/computation.html

The area where you work has almost no NAVD88 bench marks, so it is unlikely any GPS on BM observations were done that would have changed the geoid heights in your area between 12B and 18.?ÿ

 
Posted : 04/02/2020 9:03 am
(@casualsurveyor0192)
Posts: 21
Registered
Topic starter
 

@spmpls i got an output N of -31.095 M, or about 102 feet for a random spot on my drawing where i inserted a point. what does that number represent? elevation? Because both in the contours provided by napa county and our seperate survey data, the elevation we have is around 112 feet. both use navd88 i believe

 

 
Posted : 04/02/2020 9:35 am
(@spmpls)
Posts: 656
Registered
 

@casualsurveyor0192

H (NAVD88 elevation) = h (NAD83 ellipsoid height) - N (geoid height).

Your computation returned a GEOID18 geoid height for your entered location of -31.095 meters. You need to compare that value with what the 12B geoid height was for the same location. The difference, if any, will be the change in your derived NAVD88 orthometric height (elevation).

?ÿHere is the GEOID12B computation utility:

https://geodesy.noaa.gov/GEOID/GEOID12B/computation.html

?ÿ

 
Posted : 04/02/2020 9:44 am
(@casualsurveyor0192)
Posts: 21
Registered
Topic starter
 

@spmpls thank you very much. Lastly, is there a magazine or publication I can use to stay up to date on changes? I heard that opus may stop processsing data for 12b, is there any truth to that?

 

 
Posted : 04/02/2020 9:51 am
(@spmpls)
Posts: 656
Registered
 

The best place to stay informed on these issues is right here:

https://geodesy.noaa.gov/

?ÿ

?ÿ

 
Posted : 04/02/2020 10:03 am
(@casualsurveyor0192)
Posts: 21
Registered
Topic starter
 

@spmpls thanks again. Looks like depending on my location, I tried one on the valley floor and one up on our highest project, the difference is about .08 ft (valley floor) and .12 feet (higher EL.) does this change in geoid height directly correlate to what the change in elevation would show had i been using geoid 18 in my surveying equipment?

 

 
Posted : 04/02/2020 10:14 am
(@spmpls)
Posts: 656
Registered
 

@casualsurveyor0192

Yep: H=h-N. 

 

 
Posted : 04/02/2020 10:20 am
(@dave-karoly)
Posts: 12001
 

-----------Ellipsoid

^

|

N = a negative distance in most of California

|

-----------Geoid

 
Posted : 04/02/2020 12:05 pm
(@spmpls)
Posts: 656
Registered
 

@dave-karoly

Actually, negative in all of California and the rest of the Conterminous U.S.

When grading the California PLS exam years ago, one of the questions was something like "at your project location, which is higher, the ellipsoid or geoid?" An examinee answered "ellipsoid", which was correct, but then went on to state "Because the geoid is below the ellipsoid in all of the United States", which is not correct. Last I checked Alaska is in the US. They got zero points for that answer because of that incorrect statement. I always told people taking the exam to just answer the question and move on. Don't spend any time fortifying your answer and I used that situation as an example. All risk and no reward.

 

 
Posted : 04/02/2020 12:33 pm
(@mightymoe)
Posts: 9920
Registered
 

When I apply Geoid 18 in my area to NAD83 (2011) ellipsoid heights I tend to be closer to NAVD88 elevations than using Geoid 12b.

I normally correct the ellipsoid height to NAVD88 elevations with which ever flavor of Geoid I'm using.

In other words I fix my elevation and let the Geoid model move the ellipsoid height up or down.

Most people use the ellipsoid height and shift the elevation which causes you to have different elevations for each Geoid model, 90, 96, 99, 03, 09, 12, 18. So there would be at least seven different elevations for the same point through the last 28 years of GPS usage, or a change every four years or so. Of course each Epoch also changes the ellipsoid height and that adds to the number of elevation changes, 86, 93, 01, 07, 11. So mixing the seven Geoid model heights with the five ellipsoid heights can produce a large number of different elevations for the same point.?ÿ

Basically, you need to stay on top of the changes, if you have an ongoing design like many engineering designs are, keep good records of how you derive elevations and let the next guy know where it all came from.?ÿ

?ÿ

?ÿ

?ÿ

 
Posted : 05/02/2020 1:06 pm
(@rover83)
Posts: 2346
Registered
 

@casualsurveyor0192

OPUS has been returning GEOID18 on results for a while now - as of September, I believe.

Keep tabs on the NGS homepage, they will always post up changes to products and services, often long in advance.

Or, if you don't mind being notified by email, I highly recommend signing up for NGS alerts.

 

 

 
Posted : 05/02/2020 1:27 pm
(@rover83)
Posts: 2346
Registered
 
Posted by: @mightymoe

Basically, you need to stay on top of the changes, if you have an ongoing design like many engineering designs are, keep good records of how you derive elevations and let the next guy know where it all came from.

For sure. I can't tell you how many times I have seen design surveys and plansets stating "Vertical datum is NAVD88" with absolutely no other information.

 
Posted : 05/02/2020 1:34 pm
(@bill93)
Posts: 9834
 

The lesson is, "Pick a datum realization and geoid and stick with them for your whole project."?ÿ Later ones will be self-consistent over a larger area, but any recent one will probably do for most projects.

 
Posted : 05/02/2020 1:42 pm
(@geeoddmike)
Posts: 1556
Registered
 

On the question of which model of ellipsoid-geoid separation, I always recommend the most recent be used. In any event, the choice of which model to use, like which horizontal and which vertical datums are used must be included in the documentation of the work.

Note that I use the term ellipsoid-geoid separation rather than geoid height. The value labeled ƒ??geoid heightƒ? represents the linear distance from the surface of the reference ellipsoid to the geoid.?ÿ

While the relationship is often expressed otherwise, I always use h - H - N = 0 (+ errors in h, H and N).Note that the NGS datasheets do not use this relationship to sum to zero. It extracts the three quantities separately from their database.

I obnoxiously include an annotated datasheet. I forgot to label H which is the distance from the geoid to the terrain.

371728DF 2DCE 4662 A237 AA985A1C833A
 
Posted : 05/02/2020 1:43 pm
Page 1 / 2