Transform a hydrographic survey's ellipsoidal heights into a local tidal datum (e.g., Mean Lower Low Water) for a waterfront boundary determination.
domain: vdatum.noaa.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review VDatum API documentation at https://vdatum.noaa.gov/docs/services.html (current release VDatum 4.8).
Call the REST conversion endpoint at https://vdatum.noaa.gov/vdatumweb/api/convert with source/target datum codes and point coordinates.
For coastal/tidal work specifically, use the VDatum Tidal API variant to go from ellipsoidal or orthometric heights to tidal datums (MLLW, MHW, etc.).
Validate output against the interactive web tool at vdatum.noaa.gov/vdatumweb/ for a handful of spot-check points before trusting a batch run.
Confirm regional coverage — VDatum's tidal transformation grids are not uniform nationwide and gaps exist in some inland/estuarine zones.
Known gotchas
VDatum is a distinct NOAA product line from NCAT/NGS geodetic tools even though it's developed jointly by NGS, Office of Coast Survey, and CO-OPS — don't assume NCAT's datum list covers tidal datums.
Results are returned in JSON but the API is versioned to the desktop VDatum release; a locally installed older VDatum version can disagree with the live web API by design.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?