Find your next source.

Useful for

Use cases llm-inferred

Validate and normalise client or site postcodes before importing into GIS or project records · Bulk reverse-geocode survey or site coordinate lists to nearest postcode areas · Derive administrative area and region for a site as context for a planning or consultation pack · Autocomplete postcode entry in site-survey or client intake forms

Audience llm-inferred

GIS analysts · planners · civils and drainage engineers · ecologists · consultancy data and admin teams

Limitations

Constraints llm-inferred

Postcode-level data only; DOCS do not mention rooftop geocodes, UPRNs or property-level precision (offered by the paid Ideal Postcodes service) · DOCS position Ideal Postcodes for broader coverage and fresher address data, implying postcodes.io is less broad and less current · Update timing depends on upstream OS and ONS releases, with no fixed schedule · Dedicated support is offered via Ideal Postcodes, not described for postcodes.io · No rate limits or uptime guarantees stated in DOCS

Useful for

Use cases llm-inferred

Flood extent and depth baseline for a Flood Risk Assessment using return-period flood maps · Site-specific flood risk screening at property or postcode level · Climate change flood risk scenario comparison for drainage or development design inputs

Audience llm-inferred

flood risk consultants · hydrologists · drainage engineers · planners

Limitations

Constraints llm-inferred

Commercial licence; pricing and terms not stated in docs · No numeric spatial resolution or update frequency stated in docs · File formats beyond WMTS and browser/API access not specified · Docs are marketing-level; no API specification or technical documentation provided · Bespoke consultancy and single-site assessments are separate paid services

Useful for

Use cases llm-inferred

Property-level flood risk screening for a site or development portfolio · Flood hazard exposure screening for asset portfolios (utilities, critical infrastructure) · Future flood risk context for climate resilience and planning assessments

Audience llm-inferred

flood consultants · planners · GIS analysts · civils engineers

Limitations

Constraints llm-inferred

Commercial licence required · Access is quote or trial based; no open tier described beyond the free quick scan · Docs do not state spatial resolution, temporal coverage or data formats · Docs focus on financial services, insurance and utilities rather than consultancy workflows

Useful for

Use cases llm-inferred

Protected and notable species screening for a planning or development site desk study · Species context for a BNG habitat baseline · Ecological constraints review at the start of a drainage or civils scheme

Audience llm-inferred

ecologists · planners · environmental consultants · GIS analysts

Limitations

Constraints llm-inferred

No documentation was retrieved, so API endpoints, formats, and record-level detail are unverified · Licence is CC per record, so attribution and licence terms must be checked for each record used · Desk-study records are not a substitute for a field survey; recording effort and gaps are not described

Useful for

Use cases llm-inferred

Model QA before design coordination: list Revit warnings and the affected element IDs · Parameter corrections on drainage or structural elements, applied only after human-approved plans · Read-only IFC storey and property checks on consultant models without opening Revit

Audience llm-inferred

BIM coordinators · BIM managers · BIM/civils engineers

Limitations

Constraints docs-verified

Pre-release: nothing has been verified in a live Revit session yet · Describes the dev branch; the latest GitHub release may not include all features · Live Revit work limited to Windows and Revit 2024 to 2027 · Approving a plan changes the open model; test on a copy first · Snapshot QA/QC and report modules need snapshot_id; model_bloat lacks the guard · Advanced tools (revit_execute_python, revit_invoke_method) have the full permissions of the Revit process · Navisworks support is in progress · No UK-specific standards, datasets or civils tooling described in the docs

Useful for

Use cases llm-inferred

Validate consultant-issued IFC models against IDS requirement sets before design sign-off · Extract door, wall or space schedules from IFC for quantity or asset checks · Clash-check and federate architectural, structural and MEP IFC models into one file · Give an AI agent read and edit access to BIM properties via the MCP server

Audience llm-inferred

BIM coordinators · BIM/civils engineers · software developers building BIM tooling

Limitations

Constraints llm-inferred

Browser viewer depends on WebGPU support · Covers building models (IFC) only, not GIS, alignment or terrain data · Exact-arithmetic booleans are slower than approximate engines on boolean-heavy models · Very large files (500 MB+) are directed to the desktop build path · MCP tool names and schemas are not given in the supplied docs and need checking before use

Useful for

Use cases llm-inferred

Cut/fill earthwork volumes between existing ground and finished grade surfaces · Watershed delineation and Rational Method runoff checks for site drainage · Pipe network layout and hydraulic analysis for drainage design · Plan/profile sheet production and PDF publishing for design submissions

Audience llm-inferred

civil/highway design engineers · drainage engineers · hydrologists · BIM/civils engineers

Limitations

Constraints docs-verified

Requires a licensed local Civil 3D 2026 installation and Autodesk API references; Autodesk binaries are not shipped with the repo · Setup docs are Windows-focused (PowerShell commands, Civil 3D plugin built with .NET 8 on Windows) · The Civil 3D plugin must be loaded in a running Civil 3D session for drawing operations · Default MCP surface exposes 34 tools; the full 219-tool surface needs CIVIL3D_ENABLE_TOOL_ALIASES enabled · Entry lists 180 tools, which does not match the 34 public / 219 registered counts in the docs · Destructive or file-writing actions require the preview, approval-token, retry flow · Autodesk-hosted tutorial video playback requires internet access

Useful for

Use cases llm-inferred

Completeness check of IFC element and property coverage via SPARQL queries on exported LBD · Revision comparison between successive IFC model issues · Generating LBD identifiers to link IFC elements to asset or sensor records in a client data platform

Audience docs-verified

BIM practitioners · data engineers · researchers · developers

Limitations

Constraints docs-verified

Java distribution requires Java 21 · Beginner workflow is pinned to release 2.49.0; some features exist only in development version 2.55.0 · No prebuilt MCP package in release 2.49.0; MCP server must be built from source · Converter does not create external links to asset records, products, sensors or other datasets · Windows CLI executable in 2.49.0; Linux and macOS users use the Java app · MCP tool names are not published in the entry or docs

Useful for

Use cases llm-inferred

Stormwater drainage model build from GIS inputs with QA and audit trail · Peak-flow and rainfall-runoff screening for drainage strategy options · Reproducible SWMM run handover with provenance records for client review

Audience llm-inferred

drainage engineers · hydrologists · stormwater modellers · GIS analysts

Limitations

Constraints llm-inferred

Pre-1.0 (v0.9.4), so interfaces may change · Real storm networks only for 35 Canadian cities via SWMMCanada; elsewhere SWMManywhere synthesis, which is not a calibrated or validated network · Validation rows are evidence-bounded: GIS preprocessing concept, prepared-input path and uncertainty smoke are not calibrated performance claims · Raw GIS path handles structured layers only, not arbitrary CAD/GIS recognition · ENTRY lists region as United States, but DOCS do not describe US or UK coverage, so UK suitability is unverified · Agent features need an LLM provider; one-line installers run a remote script · ENTRY auth says no credentials documented, but DOCS describe API key configuration · No MCP tool names or transport documented in DOCS; ENTRY tools list is empty · One evidence row (v0.7.1) states calibration is next-milestone scope

Useful for

Use cases llm-inferred

Pre-issue model check before sheet issue (revit_pre_issue_check) · Model audit of a Revit project for QA (revit_model_audit) · Drawing and sheet layout automation for issue sets (revit_drawing_layout) · Stair modelling and checks (revit_stairs)

Audience llm-inferred

BIM coordinators · BIM/civils engineers · Revit modellers

Limitations

Constraints llm-inferred

Windows only: the installer and PowerShell setup target a Windows machine · Revit must be open with a model, and MCP must be started from the ribbon each session · Revit versions limited to 2022–2027 · Early implementation, researched and implemented since March 2026 · Family Editor authoring is out of scope · Local only: no remote access; connects to Revit via localhost TCP (≤2024) or a named pipe (≥2025)

Useful for

Use cases llm-inferred

Model QA: list levels and elevations to check floor levels and invert assumptions against drainage or civils design · Parameter completeness check: colour-splash elements by parameter value to spot missing data before issue · Coordination drawings: export named Revit views as images for design review or client markup

Audience llm-inferred

BIM/civils engineers · BIM coordinators · Drainage and civils engineers using Revit · Python developers extending Revit automation

Limitations

Constraints docs-verified

Not yet Autodesk Marketplace certified · Requires desktop Revit running with pyRevit Routes active · Bridge accepts loopback hosts only; remote VM/LAN not supported · Docs status table marks 10 of the listed tools as Pending (e.g. create_line_based_element, delete_elements, modify_element) · Docs say the review candidate has 20 tools, but catalogue metadata lists 30 · pyRevit Routes API is in draft form and subject to change · execute_revit_code runs arbitrary Python; model-changing requests need in-Revit review

Useful for

Use cases llm-inferred

Room and space schedule QA: count spaces per storey and check recurring room names in an IFC model before a design review · Opening schedule check: count doors and windows per storey as an input to an egress or fire-strategy review · Federated model census: count elements contributed by each discipline model in a coordination pack · Repeatable model checks: rerun a saved graph on a new model export and keep a run record of inputs and outputs

Audience llm-inferred

BIM coordinators · BIM/civils engineers · computational designers · GIS analysts working with building data

Limitations

Constraints llm-inferred

Host build is Windows only (docs) · IFC and BOS loaders, the 3D pane and building rule checks live in BIM Open Toolkit, not this repository · Building sample graphs need the bim-open-data samples and the toolkit's bim profile · Tool names in this entry (schependomlaan-*, digitalhub-*) do not appear in DOCS; DOCS describe different server tools (listModels, evaluate, getResult, etc.) · Building-model focus only: no UK water, hydrology, flood or environmental datasets are covered in DOCS · No loops or conditionals inside a graph; large graphs need many small tool calls · Effect nodes (file writes, IFC property sets) stay pending until an explicit Run · Beta or maintenance status not stated

Useful for

Use cases llm-inferred

Build a drainage or sewer network model from GIS/GeoJSON data with ModelBuilder for a drainage strategy · Assess surcharge and flooding in combined sewer systems for capacity checks · Compare LID and SuDS treatment-train scenarios for pollutant load and runoff volume · Run hot-start forecasts and scenario comparisons for operational sewer networks

Audience llm-inferred

drainage engineers · flood consultants · hydrologists · water quality modellers · Python developers and GIS analysts

Limitations

Constraints llm-inferred

Several capabilities are roadmap work plans, not shipped: spatially explicit groundwater, multispecies LARD water quality, heat transport, LID as storage nodes; spatially explicit inlets are in development · Licence conflict: ENTRY says 'Other', DOCS badge says MIT · GPU/threaded 2D backends ship as separately loaded plugins, not in the base build · v6.0.0 is new; SWMM 5 models need migration per the Python docs · DOCS do not mention UK-specific parameters, units or design standards; UK applicability is unverified · Software library, not a hosted service or MCP server; C/C++ requires building from source with vcpkg/CMake

Useful for

Use cases llm-inferred

Pre-issue QA: audit view and sheet naming conventions across a drainage or civils model · Schedule checks: pull schedule rows and compare schedules for quantity reconciliation · Parameter QA: read element properties and flag missing values before exporting data · Visual review: export a view image of a drainage run or structure for markup in a design review

Audience llm-inferred

BIM/civils engineers · BIM managers and coordinators · drainage engineers · BIM/CAD technicians

Limitations

Constraints llm-inferred

Needs a live Revit session with a project open; no offline or file-based access · Requires pyRevit and the Revit Routes server enabled · Web UI binds to 127.0.0.1 by default; LAN sharing is for trusted networks only · Claude Desktop local MCP runs on one machine only · Schedule formula text is unsupported (public Revit 2024 API only) · Install instructions are Windows-specific · Tool argument schemas are not documented in DOCS

Useful for

Use cases llm-inferred

Batch-editing IFC property sets and bulk classification of Vectorworks BIM models · Generating criteria-driven schedules and reports from a Vectorworks drawing for civils or drainage deliverables · Georeferencing a drawing and converting lat/lon to drawing coordinates via EPSG codes for site layouts

Audience llm-inferred

BIM and civils engineers using Vectorworks 2026 · GIS analysts · CAD/BIM technicians scripting Vectorworks

Limitations

Constraints docs-verified

Every vs.* call runs on the Vectorworks main thread, so long operations block the UI · Export/import verbs (e.g. export_pdf, import_dwg) open Vectorworks modal settings dialogs with no headless path · File-IPC path is Windows-only; macOS/remote use needs the legacy TCP bridge (VWX_TRANSPORT=tcp) · Bridge runs only while the Vectorworks palette is open; closing or pausing it stops the bridge · Multi-step one-time Windows setup: native C++ palette build, menu command and shortcut

Example tool calls docs-verified

{
  "tool": "ping",
  "arguments": {}
}

Useful for

Use cases llm-inferred

Cut/fill earthwork estimate for a linear corridor scheme (computeCorridorEarthwork) · Draft site grading and cut/fill balance for a development platform (optimizeGrading) · Batch editing of layers, blocks and entities across a drawing from natural language · Converting a raster site plan or sketch into CAD linework for further design

Audience llm-inferred

civil design engineers using Civil 3D · drainage engineers · BIM and civils CAD technicians

Limitations

Constraints docs-verified

Windows only · Needs a licensed AutoCAD/Civil 3D session open; plugin DLL is locked while C3D runs · Not an Autodesk product and not endorsed by Autodesk · Docs and default UI are Chinese; English UI added in v1.4.0 · No UK datasets, standards or geographic coverage stated · Docs cite both 270 and 274 MCP tools, so tool count may be inconsistent · 12 methods use a command channel with a 25 s timeout; some C3D features are not exposed to the AI · Corridor regeneration can take 30 s to 10 min and queues other requests (HOST_BUSY) · Grading optimisation is a draft generator; multi-level walls and pipe avoidance need manual review · Not a data API: no hydrology, gauge or DEM feeds documented

Example tool calls docs-verified

{
  "tool": "summarizeDrawing",
  "arguments": {}
}

{
  "tool": "computeCorridorEarthwork",
  "arguments": {}
}

{
  "tool": "optimizeGrading",
  "arguments": {}
}

Useful for

Use cases llm-inferred

Share a drainage or civils DWG/DXF layout with a client as one offline HTML file · Review and annotate site plans in the browser without a desktop CAD licence · Embed a DWG/DXF survey or floor plan on a project website via iframe · Export drawing sheets to PDF or SVG for planning or design submissions

Audience llm-inferred

civils engineers · BIM/civils engineers · drainage engineers · planners · web developers integrating CAD viewers

Limitations

Constraints llm-inferred

Viewer/editor, not a data API: offers no geospatial, hydrological or survey datasets · Entry lists tools: []; docs only link a gitmcp.io MCP endpoint, with no tool names or transport stated · Docs do not state supported DWG/DXF versions or entity coverage · Building from source requires Node.js >= 24 and pnpm >= 10 · OneDrive and Google Drive data source plugins require sign-in · AI agent plugin needs user-supplied LLM API keys held in browser localStorage

Useful for

Use cases llm-inferred

Scripting buffer, clip and intersect geoprocessing on drainage or site boundary layers · Diagnosing CRS mismatches when combining BIM/IFC site models with GIS data · Generating print-ready site plan layouts and PDF exports for consultation documents · Computing hillshade, slope and aspect from DEMs for civils terrain review

Audience llm-inferred

GIS analysts · drainage engineers · hydrologists · BIM/civils engineers · QGIS plugin developers

Limitations

Constraints llm-inferred

Teaches Claude how to write PyQGIS code; it does not control a running QGIS instance (runtime control needs a separate MCP server) · Targets QGIS 3.44 LTR; QGIS 4.0 is covered only by compatibility notes · Not a data source: provides no UK datasets, gauges, DEMs or rainfall data · No UK-specific guidance (for example British National Grid) is documented · Install instructions point to the OpenAEC-Foundation repository, which differs from the listed URL (Impertio-Studio) · Requires a local Claude Code setup and a local QGIS installation to run the resulting code

Useful for

Use cases llm-inferred

Prioritise open Navisworks clashes before a coordination meeting · Collapse repeated clashes to root-cause groups for trade discussions · Compare issue status between successive federated model deliveries · Prepare coordination work packages with trade ownership and PDF report images

Audience llm-inferred

BIM coordinators · BIM/civils engineers · design coordination managers

Limitations

Constraints docs-verified

Live coordination requires Windows and a licensed Autodesk Navisworks Manage 2024, 2025 or 2026 · Engineering approval and edits remain with the project team · Movement alternatives use element bounds and must be checked against surrounding geometry and design constraints · Revit and Power BI handoff relies on separate Horizun MCP servers

Useful for

Use cases llm-inferred

Preflight-checked inspection and summary of existing DWG drawings before civils or drainage design review · Guarded, dry-run-verified layer, annotation and dimension clean-up of CAD deliverables before issue · Generating PDF plot and PNG visual evidence of drainage or civils layouts for internal QA

Audience llm-inferred

civils engineers · drainage engineers · BIM and CAD technicians · GIS and CAD analysts

Limitations

Constraints docs-verified

Beta software, intended for controlled local use with operator review rather than unattended changes to production drawings · Windows only; requires AutoCAD running as the same Windows user · Not claimed to comply with formal ISO, GB or ASME standards · Requires a local MCP client; no hosted or remote operation

Useful for

Use cases llm-inferred

Convert client-supplied DXF building plans into SVG previews and room/area schedules for a design report · Extrude DXF building walls to STL for 3D massing or visualisation review · Export wall geometry as IFC-shaped JSON for a BIM handoff · Batch-run plan_info or plan_analyse across a depot of drawings for a quick QA pass

Audience llm-inferred

BIM engineers · civils engineers · architects · CAD technicians

Limitations

Constraints llm-inferred

Many tools (plan_dimension, plan_text, plan_hatch, plan_block_insert, plan_array, plan_convert, plan_wall_data, plan_render, plan_script, plan_exec, plan_agentic, plan_transpile) need QCAD Pro installed; the rest rely on the ezdxf engine. · Install and path guidance is Windows-oriented (Claude Desktop installer, start.ps1, %LOCALAPPDATA% depot); Linux and macOS setup is not documented. · Tool inventory mismatch: docs claim 42 tools and list plan_obj and plan_glb, which are absent from the ENTRY tool list (35 tools). · No authentication documented; plan_script and plan_exec run arbitrary ECMAScript in QCAD Pro, so expose only to trusted local clients. · The raster-to-DXF pipeline is marked Planned and is not available. · Default MCP client config points at a local SSE endpoint (localhost:11966/sse), so the backend must be running. · Companion servers (blender-mcp, freecad-mcp) are optional and only unlock extra features. · The docs table marks qcad_shutdown as READ-only despite it shutting the server down; check annotations before auto-approving tools. · Tool argument schemas are not in the docs; example argument names are inferred.

Useful for

Use cases llm-inferred

Work item rate lookup for cost estimates via CWICR semantic search · Extracting BIM quantities from IFC models to Excel for takeoff checks · Budget vs actual cost tracking with scheduled comparisons

Audience llm-inferred

cost estimators · BIM and civils engineers · construction project managers · data and ETL analysts

Limitations

Constraints llm-inferred

Skills are instruction files (SKILL.md) that generate code; they are not a hosted data service and the entry lists no MCP tools · Generated code must be reviewed and adapted to your own data before running · Requires Python 3.9+ and basic Python knowledge; some skills need Docker, PostgreSQL/SQLite or an OpenAI API key · Construction-focused; no UK water, drainage or environmental data stated in DOCS · Entry is typed as mcp but tools list is empty

Useful for

Use cases llm-inferred

Audit a Revit model for untagged and undimensioned elements before issuing drawings (find_untagged_elements, find_undimensioned_elements) · Export element or room data from a model to Excel for drainage or civils quantity checks (export_elements_data) · Generate per-room floor plan views for a drainage or civils design package (create_views_from_rooms) · Push model schedules and selected elements to Power BI for live project reporting

Audience llm-inferred

BIM/civils engineers · BIM coordinators · Drainage engineers · Revit power users

Limitations

Constraints docs-verified

Windows 10 or 11 only · Revit LT not supported · Revit must be running with a document open · MCP TCP server is off by default and must be switched on in the Revit ribbon · Tools auto-hide when the active document does not support them · Destructive operations show a Revit confirmation dialog, which may need a user to respond · DOCS reference some tool names not in the ENTRY tool list (e.g. export_to_excel, workflow_model_audit)

Useful for

Use cases llm-inferred

Drafting site and drainage layout plans in DXF for exchange with design teams · Annotating civils drawings with dimensions, hatching and title blocks · Exporting plotted PDF and SVG sheets from drawings for client issue

Audience llm-inferred

civils engineers · drainage engineers · CAD technicians · BIM/civils engineers

Limitations

Constraints docs-verified

Early development status · CAD drafting tool only: no geospatial, hydrology or UK-specific datasets · DWG write limited to R2000; DWG read covers R13–2018 · Entities CADCraft does not model yet are dropped on save · ENTRY licence is Apache-2.0 only; DOCS state MIT OR Apache-2.0 · MCP tool names not given in ENTRY or DOCS

Useful for

Use cases llm-inferred

Parametric wall, slab and roof creation in an IFC model from natural-language prompts · Scene and object property review of an IFC model via get_ifc_scene_overview and get_object_info · Converting Trimesh-generated custom geometry into native IFC elements for civils BIM models · Screenshot-based QA of BIM model state in Blender

Audience llm-inferred

BIM/civils engineers · BIM coordinators · architects

Limitations

Constraints llm-inferred

Requires a local Blender 4.4+ installation with the Bonsai add-on and the BlenderMCP add-on connected · An empty IFC file must be saved before operations, otherwise changes do not reach the Blender scene · The general execute_code tool is unreliable for IFC operations and may be disabled · Knowledge base features need a local ChromaDB index and an embedding server · The author points users to a newer repository (bonsai-mcp) with a stronger code-generation focus, so this repo may receive less maintenance · Not an official Blender, Bonsai or IfcOpenShell project

Useful for

Use cases llm-inferred

Greenfield runoff rate estimate for SuDS design of a development site · Infiltration volume estimate to inform a drainage strategy · Surface water storage volume estimate for sizing attenuation features

Audience llm-inferred

drainage engineers · civils engineers · SuDS designers

Limitations

Constraints llm-inferred

ENTRY kind is 'dataset', but DOCS describe web calculation tools, not downloadable data · DOCS describe no API, export or machine-readable output · ENTRY lists no tools, so no MCP or programmatic access is catalogued · DOCS do not state the geographic extent or time span of the tools' inputs or outputs

Useful for

Use cases llm-inferred

Regional landslide susceptibility screening of a linear infrastructure corridor from a DEM and geology layer · Critical rainfall estimation for slope hazard zoning · Comparative stability assessment of natural slopes under dry versus fully saturated conditions · Risk prioritisation of shallow-landslide-prone slopes across a study area

Audience llm-inferred

geotechnical engineers · engineering geologists · civils engineers · hydrologists · GIS analysts

Limitations

Constraints docs-verified

Not suitable for deep-seated landslides · Cannot predict exact timing of failure · Requires high-quality input data · Probability output is relative, not absolute · MCP support is in the development branch (v1.1.0.dev0) and needs pip install -e ".[mcp]" for local development · MCP features require Python >= 3.10 · Only standard I/O (stdio) transport is documented

Useful for

Use cases llm-inferred

Nearest-gauge river level and flow context for FRA baseline · Check live flood warnings and alerts for a site's catchment · Pull recent level and flow readings for hydrological baseline review · Locate monitoring stations within a set radius of a project site

Audience llm-inferred

flood consultants · hydrologists · drainage engineers

Limitations

Constraints docs-verified

No service level guarantee; not suitable for safety-critical applications · Upstream Environment Agency API is Beta · Responses may be cached for short periods · List tools capped at 500 items (default 50; readings default 100), 60 KB truncation; use limit/offset to paginate · Coverage conflict: docs say UK, ENTRY metadata says England

Useful for

Use cases llm-inferred

Screening private warehouse layers for proximity to road or utility networks (e.g. features within 5 km of a motorway) for constraint mapping · Sanity-checking polygon area and line length of GIS query outputs before using them in a report · Joining site or asset points to Overture Maps building or road layers for baseline context · Rendering spatial query results as a map for client or peer review

Audience llm-inferred

data scientists · analysts · GIS analysts · spatial data engineers

Limitations

Constraints llm-inferred

Requires access to a supported warehouse (PostGIS, BigQuery, Snowflake or Wherobots) and its local CLI credentials · BigQuery queries are capped at a 10 GiB scan by default · Benchmark suite covers only London, Berlin and Paris cases (8 assertions) · Map-feedback loop needs the optional Dekart CLI · ENTRY notes no credentials documented in README, while the docs rely on local bq/snow/dekart auth · Not UK-specific; no UK datasets are named in the docs · Version check telemetry is on by default (disable with DO_NOT_TRACK=1)

Useful for

Use cases llm-inferred

Wave climate inputs for coastal defence and shoreline management design · Observed wave data for coastal scheme appraisal and feasibility studies · Regional coastal monitoring context for estuary or marine works baselines

Audience llm-inferred

coastal engineers · coastal and shoreline management planners · civils engineers · environmental consultants

Limitations

Constraints llm-inferred

Access appears to require login or registration despite auth 'none' in metadata · Docs describe England regional programmes only; other coverage is not described · Data formats, time span, resolution and update frequency are not stated in the docs · Page footer reads 'updated 8 August 2024', so currency of the site is uncertain