Jump to content

NGS releases beta tool for obtaining geodetic information


Recommended Posts

NGS has developed a new beta tool for obtaining geodetic information about a passive mark in their database. This column will highlight some features (available as of Oct. 5, 2020) that may be of interest to GNSS users. It provides all of the information about a station in a more user-friendly format. The box titled “Passive Mark Lookup Tool” is an example of the webtool. The tool provides a lot of information so I have separated the output of the tool into several boxes titled “Passive Mark Lookup Tool — A through D.”

I will highlight several attributes that I believe will be very useful to users, especially users of leveling-derived and GNSS-derived orthometric heights. I’ve highlighted several attributes in the box titled “Passive Mark Lookup Tool — A” that are important to users such as published coordinates, their datum and source, Geoid18 value, GNSS Useable, and the date of last recovery. All of these values are available on a NGS datasheet but, in my opinion, this provides the information in a more user-friendly format.



One calculation that the user can easily compute for marks that have been leveled to and occupied by GNSS equipment, is the difference between the published leveling-derived orthometric height and the computed GNSS-derived orthometric height. This may indicate that the mark has moved since the last time it was leveled to or that its height coordinate has been readjusted since the creation of the published geoid model.

The table below provides the calculation using the data from the box titled “Passive Mark Lookup Tool — A.” The calculation [HGNSS = hGNSS — NGeoid18; Difference = HGNSS — HNAVD 88] has been described in several of my previous columns



In this example, the difference between the GNSS-derived orthometric height and the Published NAVD 88 height is 6.1 cm. NGS is looking for comments on this beta webtool so if users would like this computation added to the tool, they should send a comment to NGS using the link provided on the site (This is a beta product. NGS is interested in your feedback concerning its function and usability as well as how users would like to interact with NGS datasheet information in the future. Email us at [email protected].) So, the user should ask the question, did the station move since the last time it was leveled?

Another attribute that would be nice to be part of this tool is was the station used to create the hybrid geoid model. As of Oct. 5, 2020, users have to go to the Geoid18 webpage to get the information. The excel file and shapefiles provides whether the station was used to create the Geoid18 model. In the case of this example, KK1531, CHAMBERS, the mark was not used in the creation of Geoid18 so NGS felt that the station may have moved and/or the GPS on Bench Mark residual was large relative to its neighbors. See NGS’s technical report on Geoid18 for more information on the creation of Geoid18. The GPS on Bench Mark residual analysis was described in several of my previous columns (see “The differences between Geoid18 values and NAD 83, NAVD 88 values” and “NGS 2018 GPS on BMs program in support of NAPGD2022 — Part 6” for examples).

The webtool provides a map depicting the location of the station, photos (if available), and previously published, superseded values of the mark. See the box titled “Passive Mark Lookup Tool — B.”





  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.



If you enjoy our contents, support us by Disable ads Blocker or add GIS-area to your ads blocker whitelist