Skip to content
All engineering use cases

Coastal bathymetry and sea level data

Select regional bathymetry and sea-level products for coastal model scoping. Compare listed sources, access requirements and evidence for coastal bathymetry and sea level data.

3 sources · For coastal engineers, flood consultants, hydrologists, marine and civils engineers. Enrichment describes potential applications; review source evidence and limitations.

NOAA stations cover US coasts; bathymetry, tides and modelled sea levels require datum and coverage checks.

Discover sources with MCP

Add this server to an HTTP-compatible MCP client, then call get_source to inspect the first source. The tool call is shown separately from the client configuration. Review upstream access details before requesting data.

{
  "mcpServers": {
    "terramcp": {
      "url": "https://terramcp.earth/mcp"
    }
  }
}

// After connecting, call this discovery tool:
{
  "name": "get_source",
  "arguments": {
    "slug": "emodnet"
  }
}

Listed sources

data api
50/100Currency C

NOAA CO-OPS Tides and Currents API ↗

Coastal water-level observations, tide predictions and currents from NOAA CO-OPS stations.

What's in it

Data offered docs-verified
water level (6-minute, preliminary or verified) · hourly height water level (verified) · high/low tide water level (verified) · daily mean, daily max/min and monthly mean water level (verified) · 1-minute water level (preliminary) · tide predictions · meteorological: air and water temperature, wind, air pressure, visibility, humidity, conductivity, salinity · air gap at bridges · currents (6-minute default, or hourly), by bin · currents predictions · currents header · OFS model water level guidance (nowcast/forecast)
Coverage llm-inferred
United States (per ENTRY regions; CO-OPS stations, including Great Lakes and Columbia River) · Product-dependent; ofs_water_level data available from 2020 to present
Resolution docs-verified
Per-station. Temporal: 6-minute default for water level, meteorological and currents data; 1-minute and hourly options; predictions at 1, 5, 6, 10, 15, 30 or 60 minutes, hourly, or high/low
Update frequency docs-verified
Preliminary data near real time; verified data monthly (past month verified in the following month)
Access llm-inferred
Not stated in DOCS. ENTRY lists no auth and no licence (both null), so access and licence are unverified.

Useful for

Use cases llm-inferred
Coastal flood baseline: tidal range and extreme water levels from nearest station using verified high/low and daily max/min data · Tidal boundary conditions for coastal or estuarine flood models using 6-minute water levels and predictions · Long-term sea-level and datum context using verified monthly mean and daily mean water levels · Tidal current inputs for estuarine outfall or marine works design using currents_predictions
Audience llm-inferred
flood consultants · coastal engineers · hydrologists · marine and civils engineers

Limitations

Constraints llm-inferred
US stations only per ENTRY regions; not applicable to UK sites · Datum is mandatory for water level products, so every request must specify one · Per-request length limits: 1-minute 4 days; 6-minute 1 month; hourly and high/low 1 year; daily means and daily max/min 10 years; monthly means 200 years · Verified data is released station by station each month, with no specific date per station · Each verified interval is a separate product and cannot be selected with the interval parameter · Bin number is required for most current stations · Subordinate tide-prediction stations support only high/low intervals · Datums product is no longer available on this API; use the Metadata API · No auth or licence stated in ENTRY; check terms before commercial use
floodhydrology

United Statespage reachable

Frequently asked questions

Which listed sources support Coastal bathymetry and sea level data?

Start with EMODnet, Copernicus Marine Service, NOAA CO-OPS Tides and Currents API. Select regional bathymetry and sea-level products for coastal model scoping.

What should I check before using these sources for coastal bathymetry and sea level data?

NOAA stations cover US coasts; bathymetry, tides and modelled sea levels require datum and coverage checks.

How do I inspect EMODnet through MCP?

Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug emodnet. Review its provenance, access requirements and limitations before contacting the upstream service. Discovery does not make every listed source directly executable through the router.

Are these sources free and independently verified?

Access and licence terms belong to each upstream provider; some products require registration or payment. Open each listing for evidence, health status and enrichment provenance. A wrapper and its underlying API can refer to the same dataset and are not independent observations.