Terrain & elevation

Useful for

Use cases llm-inferred

Desk-based site context screening: geocode an address, buffer 1-2 km, then pull OSM features (e.g. waterways, buildings) for a constraints check · Preliminary civils or drainage gradient checks: elevation profile along a proposed route or corridor · Terrain screening: sample and zonal stats of a client-supplied GeoTIFF DEM over a site boundary · Drive-time accessibility isochrones for planning or appraisal reports (requires OpenRouteService key)

Audience llm-inferred

GIS analysts · planners · drainage engineers · civils engineers · environmental consultants

Limitations

Constraints docs-verified

Release status: PyPI provides v0.3.0; the v0.4.0 release candidate (newest provider and hardening work) is not yet released · Default public providers have usage policies: Nominatim max 1 request/second, OSRM demo server not for production, Overpass fair use · Isochrones require GEO_MCP_ORS_API_KEY, which is unset by default · Docs are inconsistent on tool count (44 in places, 42 in CLI output) · Roadmap items not yet available: Mapbox/Google geocoding, WebSockets, batch file processing, reproject/clip/mosaic · No UK-specific datasets or hydrological time-series (gauge levels, rainfall) documented · Raster and vector tools operate on local files supplied by the user; no bundled datasets documented

Example tool calls docs-verified

{
  "tool": "geocode",
  "arguments": {
    "query": "Brandenburg Gate, Berlin"
  }
}

{
  "tool": "buffer",
  "arguments": {
    "point": {
      "lat": 52.5163,
      "lon": 13.3777
    },
    "distance_m": 1000
  }
}

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

Audience llm-inferred

flood consultants · drainage engineers · hydrologists · GIS analysts · civils engineers

Limitations

Constraints llm-inferred

No docs retrieved, so coverage, formats, resolution and access terms are unverified · Auth and licence not recorded in entry

Useful for

Use cases llm-inferred

FRA catchment context: delineate contributing catchment boundaries from HydroSHEDS basins · Drainage strategy: river network and lake layers for receiving-watercourse context · Ecology/BNG baseline: river and lake network mapping for habitat context

Audience llm-inferred

hydrologists · flood consultants · drainage engineers · GIS analysts · ecologists

Limitations

Constraints docs-verified

HydroSHEDS v2 is released for the Americas; the global v2 (TanDEM-X based) is still in development · Specific resolutions, update cadence and licence terms are not stated in DOCS

Useful for

Use cases llm-inferred

DEM and orthomosaic production from drone survey photos for site topographic baselines · Ground-classified point clouds and surface models from UAV photogrammetry for earthworks or cut-fill inputs · Survey-grade models controlled with ground control points and coded markers · Batch export of DEM, orthomosaic and point cloud deliverables as GeoTIFF or LAZ for GIS and BIM handover

Audience llm-inferred

drone survey and photogrammetry consultants · GIS analysts · civils and BIM engineers · terrain and heritage 3D modellers

Limitations

Constraints llm-inferred

Runs inside a licensed desktop Metashape Professional 2.3+ session; not a standalone data source · Viewport and screenshot tools are unavailable in headless mode · Direct HTTP connection from Claude Code times out after about 60 seconds; the stdio proxy is needed for long jobs and requires a separate FastMCP install · ENTRY tool names (aerial_survey_pipeline, close_range_pipeline, batch_export, diagnose_alignment, optimize_quality_settings) match the docs' guided workflow prompts, not documented callable tools · Tool argument schemas are not documented in the DOCS text · No credentials documented in README; the Metashape licence is separate from the MIT-licensed server

Useful for

Use cases llm-inferred

Bench-scale point-cloud capture of a flume or physical model test rig · Prototype obstacle or clearance sensing for an instrumented monitoring robot on a test bed · Quick 2D distance survey of a lab or enclosed space to check clearances

Audience llm-inferred

civils engineers building bench-scale test rigs · hydrologists with physical model or flume setups · GIS analysts processing 2D scan data · robotics and sensor prototyping engineers

Limitations

Constraints llm-inferred

2D sensor only: single scan plane, no 3D point cloud · Requires physical YDLIDAR hardware; no simulation or file replay is described · Quick-install example uses Windows paths and COM ports; other platform setup is not detailed · USB 3.0 recommended for G4/S2 high-rate modes · Web console requires v0.4+ and its feature set is version-dependent · Local install only; no hosted or remote service is described

Useful for

Use cases llm-inferred

Swiss site access and route appraisal using named hiking routes and elevation profiles · Public transport access check for Swiss field survey visits · Weather window forecasting at Swiss field survey sites for scheduling fieldwork

Audience llm-inferred

GIS analysts · planners · ecologists · field survey coordinators

Limitations

Constraints llm-inferred

Switzerland only; not applicable to UK sites · geo.admin.ch fair use is 20 requests/min on average · transport.opendata.ch has a soft, undocumented rate limit · Open-Meteo data requires CC BY 4.0 attribution · Commons Clause licence restricts selling the software; licence metadata reads Other · Windows binary is unsigned and may trigger SmartScreen; macOS needs a Gatekeeper workaround · Test suite stubs fetch with no committed fixtures; some behaviour was verified only with live probes during initial development · Hiking and weather data are not UK-relevant; not suited to the core UK water and civils workflows

Example tool calls docs-verified

{
  "tool": "forecast",
  "arguments": {
    "lat": 47.2494,
    "lon": 9.3434
  }
}

Useful for

Use cases llm-inferred

FRA baseline flows: find gauges within a buffered site polygon with hydro_find_gages and read drainage area (dasqmi) and NWIS linkage · Drainage strategy context: identify the HUC12 watershed and its downstream HUC for a site with hydro_identify_watershed · Watercourse and waterbody constraint mapping for planning or ecological screening using hydro_find_waterways and hydro_find_waterbodies · Outfall and culvert screening using modelled EROM flow and velocity from flowline attributes

Audience llm-inferred

flood consultants · hydrologists · drainage engineers · GIS analysts · ecologists · planners

Limitations

Constraints docs-verified

Each layer caps at 2000 records per request; results set truncated: true when the cap is hit · Feature geometry is not returned, so results are attributes only · Tools are geometry-intersection queries; routed upstream/downstream tracing is not yet implemented · Drainage-area units differ: gages use square miles (dasqmi), flowlines and watersheds use square km · Point and line layers need a Polygon or BoundingBox to reliably capture features · Covers the United States only

Useful for

Use cases llm-inferred

Search the STAC catalog for environmental raster layers to build a site-scale GIS baseline · Retrieve land cover or vegetation layers as inputs to a BNG habitat baseline · Gather historic environmental datasets for planning constraint mapping

Audience llm-inferred

GIS analysts · ecologists · hydrologists · planners

Limitations

Constraints llm-inferred

Dataset-specific licences must be checked before reuse · Asset downloads require signed URLs · No licence recorded in entry metadata · No documentation retrieved, so dataset contents and coverage are unverified

Useful for

Use cases llm-inferred

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

Audience llm-inferred

GIS analysts · hydrologists · drainage engineers · civils engineers

Limitations

Constraints llm-inferred

Licence varies by dataset · API key required · No docs retrieved, so capabilities and coverage are unverified