Back to skills
SKILL.md
Docs
ASecurityAdd thin dams (levees, embankments), weirs, and drainage structures to the SFINCS model. This stage is OPTIONAL — only needed for domains with significant hydraulic infrastructure that affects flood routing.
- 231 stars
- 0 votes
- 0 copies
- 3 views
- Added September 11, 2026
Security analysis
100/100Pro scans all 13 files and shows the line behind each finding
npx -y skills add lzwei196/KISS---Knowledge-Infrastructure-for-Scientific-Simulation --skill docs --agent claude-codeAre you the author of Docs?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lzwei196-docs-0a8afbb1)# S5: Hydraulic Structures — Skill Document
## Purpose
Add thin dams (levees, embankments), weirs, and drainage structures to the SFINCS model. This stage is OPTIONAL — only needed for domains with significant hydraulic infrastructure that affects flood routing.
## Prerequisites
- sfincs.dep and sfincs.msk from s2_topobathy
- GIS data for levees, weirs, or drainage structures (shapefiles or coordinates)
- Knowledge of structure dimensions (height, crest width, discharge capacity)
## Inputs
| Input | Type | Required |
|-------|------|----------|
| Levee polylines | .shp or coordinates | No |
| Weir locations | coordinates + params | No |
| Drainage points | coordinates + capacity | No |
## Procedure
1. **Thin dams (sfincs.thd)**: Represent levees, embankments, sea walls as infinitely thin barriers at cell edges. Format: one line per dam segment with start/end coordinates and crest elevation.
2. **Weirs (sfincs.weir)**: Represent spillways, overflow structures. Include location, crest elevation, discharge coefficient.
3. **Drainage (sfincs.drn)**: Represent drainage outfalls, pump stations. Include location and capacity (m3/s).
4. **When structures matter**:
- Urban areas with levee protection: YES, critical
- Rural floodplains without embankments: NO, skip this stage
- Coastal areas with sea walls: YES
- Mountain valleys: Usually NO (natural terrain dominates)
## Expected Outputs
| Output | Path | Verification |
|--------|------|-------------|
| sfincs.thd | `{output_dir}/sfincs.thd` | Valid coordinates and elevations |
| sfincs.weir | `{output_dir}/sfincs.weir` | Valid parameters |
| sfincs.drn | `{output_dir}/sfincs.drn` | Valid capacity values |
## Validation Checks
1. Structure coordinates fall within the computational domain
2. Crest elevations are above surrounding terrain (otherwise useless)
3. Drainage capacity is reasonable (typical pump: 1-50 m3/s)
## Common Pitfalls
- Thin dam crest elevation lower than surrounding DEM — structure has no effect
- Drainage capacity too high — artificially prevents flooding
- Missing gaps in levee representation — water cannot enter protected area during overtopping
Files in this skill
- REFERENCES.md
- format_spec.yaml
- papers.json
- s1_domain_skill.md
- s2_topobathy_skill.md
- s3_roughness_skill.md
- s4_forcing_skill.md
- s5_structures_skill.md
- s6_config_skill.md
- s7_execution_skill.md
- s8_postprocess_skill.md
- validation_convention.yaml
Attribution
Related skills
View all in testing →Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.