Flood Modeling Challenges¶
The flood modeling industry has a workflow problem. Engineers spend the majority of their time on setup and data management, not on the engineering decisions that actually matter.
Where Time Goes¶
Research into hydraulic modeling workflows consistently shows:
| Activity | % of Project Time | Notes |
|---|---|---|
| Model setup & data processing | ~40% | DEM processing, mesh generation, boundary definition, friction mapping |
| Calibration & validation | ~16% | Adjusting parameters to match observed data |
| Quality assurance | ~15% | Checking inputs, reviewing outputs, documentation |
| Reporting | ~12% | Formatting results for regulators, clients, stakeholders |
| Running simulations | ~8% | The actual compute — often the easiest part |
| Other | ~9% | Project management, meetings, coordination |
68% of time is spent before a simulation runs. Cloud compute addresses the 8%. Hydrata addresses the 68%.
Pain Points¶
Mesh Generation Takes Days, Not Hours¶
Mesh generation is "the most important and time-consuming task" in 2D flood modeling. It relies on repetitive manual work and subjective decision-making. If the mesh is regenerated, all hand editing is lost.
How Hydrata helps: Upload a DEM and define mesh regions in the browser. ANUGA generates the triangular mesh automatically. Adjust resolution per region without starting over.
The Learning Curve Is Measured in Years¶
"It takes years to really become an expert in any software." There is a "sharp learning curve from model to model." Junior engineers routinely make serious mistakes — incorrect boundary conditions, ignored friction values — without knowing they've made them.
How Hydrata helps: Guided scenario configuration with sensible defaults. Input validation before simulation. The same senior engineer's workflow, accessible to a team.
Collaboration Means Emailing Files¶
Flood modeling has no standardized way for stakeholders to exchange data. Models are files on individual machines. A single incorrect number can change model outputs. Knowledge leaves when staff leave.
How Hydrata helps: Team members work on the same project. Every input versioned, every result published as a WMS layer with a shareable URL. No "which DEM did you use?" confusion.
Report Generation Is Manual¶
Consultants must produce extensive documentation for regulatory submissions. Current tools produce raw output, not submission-ready reports. Engineers spend significant time manually formatting results.
How Hydrata helps: Results are published as OGC WMS layers and downloadable datasets. Flood depth maps, velocity fields, and extent polygons are ready to embed in reports or share with stakeholders.
Data-Scarce Regions Need Modeling Most¶
89% of the world's flood-exposed population lives in low- and middle-income countries — the places with the least data, fewest tools, and most expensive software licences.
How Hydrata helps: Cloud-based, no expensive desktop licences. Works with available data — even coarse DEMs. Free tier available for evaluation.
The Workflow Hydrata Replaces¶
Before (Traditional Desktop Workflow)¶
- Download DEM from data provider, convert format in GIS
- Export DEM to modeling software's proprietary format
- Define computational domain and boundary conditions manually
- Generate mesh — iterate for days until quality is acceptable
- Set friction values by hand-drawing polygons
- Transfer files to compute machine
- Run simulation (hours to days on local hardware)
- Transfer results back, import into GIS
- Create maps, extract statistics, format for report
- Email files to team for review
After (Hydrata)¶
- Upload DEM — Hydrata handles format and projection
- Define boundaries and friction maps in the browser
- Configure scenario parameters
- Submit to cloud compute — results in minutes
- Results published as WMS layers — share via URL
- Team reviews in the same platform
Steps reduced from 10 to 6. Time reduced from weeks to hours. Every step tracked and reproducible.