Retrieve a station's tidal datums (MLLW, MHW, MSL, etc.) from the NOAA CO-OPS Metadata API to convert a marina's charted depths to a usable local reference.

domain: api.tidesandcurrents.noaa.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Identify the target station ID via the CO-OPS Metadata API (api.tidesandcurrents.noaa.gov/mdapi/prod)
  2. Call the Metadata API's datums resource at https://api.tidesandcurrents.noaa.gov/mdapi/prod/webapi/stations/{station_id}/datums.json - the Data API's older datums product has been retired and no longer serves datum values
  3. Parse the returned datum values (MLLW, MHHW, MSL, etc.) and their relation to the station's benchmark
  4. Convert marina bulkhead/chart depths using the appropriate datum for navigation vs construction use
  5. If the station's current datum set was superseded, check the Metadata API's supersededdatums expansion for prior epoch values

Known gotchas

Related routes

Transform vertical datum values (e.g., NAVD88 to MLLW) at a coastal survey point using the NOAA VDatum web API
vdatum.noaa.gov · 5 steps · unrated
Discover the nearest NOAA CO-OPS stations to a marina's coordinates
api.tidesandcurrents.noaa.gov · 5 steps · unrated
Pull station datum, bin, and sensor metadata before querying tide/current data
api.tidesandcurrents.noaa.gov · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans