Skip to content
Back to skills

Docs

ASecurity

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.

  • 231 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 11, 2026
testing

Security analysis

A100/100

Pro scans all 13 files and shows the line behind each finding

Scanned September 11, 2026

npx -y skills add lzwei196/KISS---Knowledge-Infrastructure-for-Scientific-Simulation --skill docs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Docs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Docs
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lzwei196-docs-0a8afbb1/badge)](https://www.skillsdirectory.com/skills/lzwei196-docs-0a8afbb1)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# 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.md1.5 KB
  • format_spec.yaml44.1 KB
  • papers.json5.8 KB
  • s1_domain_skill.md2.5 KB
  • s2_topobathy_skill.md3.4 KB
  • s3_roughness_skill.md2.1 KB
  • s4_forcing_skill.md4.2 KB
  • s5_structures_skill.md2.1 KB
  • s6_config_skill.md2.7 KB
  • s7_execution_skill.md2.6 KB
  • s8_postprocess_skill.md3.1 KB
  • validation_convention.yaml8.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in testing →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.