Build a terrain shortlist for hydraulic model ground levels and overland flow routes. Compare listed sources, access requirements and evidence for lidar for flood risk assessments.
Check survey date, vertical datum and whether the raster is a DTM or DSM before using levels.
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.
Environment Agency survey portal for LiDAR terrain and surface models and other survey data.
What's in it
Data offered llm-inferred
LiDAR terrain model · LiDAR surface model · other survey data
Coverage llm-inferred
England
Useful for
Use cases llm-inferred
Flood risk assessment: ground-level inputs for hydraulic model topography · Drainage strategy: surface levels for catchment and overland flow delineation · Civils design: existing ground model for earthworks and levels
Catchment terrain and slope analysis for an FRA study area from a bbox DEM · Topographic levels for drainage strategy and earthworks setting-out inputs · Terrain base layer for GIS site analysis
Which listed sources support LiDAR for flood risk assessments?
Start with Defra Data Services Platform LiDAR, OpenTopography API, Copernicus DEM. Build a terrain shortlist for hydraulic model ground levels and overland flow routes.
What should I check before using these sources for lidar for flood risk assessments?
Check survey date, vertical datum and whether the raster is a DTM or DSM before using levels.
How do I inspect Defra Data Services Platform LiDAR through MCP?
Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug defra-data-services-platform-lidar. 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.