terrain-hydrology
SolidAlways invoke for terrain, drainage, viewshed, or visibility analysis from elevation, even before the DEM or correct surface is chosen. Covers DTM-versus-DSM selection, slope, aspect, curvature, hillshade, conditioning, flow direction/accumulation, streams, watersheds, and catchments. Use point-cloud-lidar first only when an elevation surface must be created from LiDAR or photogrammetric points.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- muend
- Repository
- muend/geoai-skills
- Created
- 1 weeks ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
point-cloud-lidar
LiDAR and point cloud processing: PDAL pipelines, LAS/LAZ/COPC handling, ground classification, DTM/DSM/CHM generation, canopy and building metrics, and photogrammetric (SfM) point clouds. Use when the primary input is LAS, LAZ, COPC, LiDAR, or an unstructured 3D point cloud. Route analysis of an already derived DEM, DTM, DSM, or CHM to terrain-hydrology unless point-level classification or metrics remain in scope.
remote-sensing-analysis
Always invoke for classical analysis, classification, validation, or comparability of satellite, aerial, or drone imagery. This skill owns sensor/product/processing-level harmonization, including multi-date inputs; add change-detection only after comparable observations exist. Covers spectral indices, masking, compositing, SAR, land cover, and accuracy assessment. Route neural methods to geo-deep-learning and planetary server-side execution to google-earth-engine.
swmm-gis
GIS/DEM preprocessing for SWMM experiments using the user's own QGIS/GRASS layers. Use when the user asks to (1) delineate subcatchments through QGIS/GRASS (standard or entropy-guided), (2) preprocess QGIS-derived subcatchment polygons into builder-ready CSV, (3) identify high-entropy hotspot subcatchments, or (4) expose QGIS/GRASS-backed preprocessing as MCP tools for reproducible workflows. For bbox-only inputs WITHOUT real pipe data, use `swmm-anywhere` instead (it synthesises a plausible network from OSM streets + DEM).