Why Hydrata¶
Engineers spend most of a flood modeling project preparing and checking a model, not running it. On Hydrata's own estimate the simulation itself is about a tenth of the work. Hydrata is built to shrink the other nine tenths, not just to speed up the tenth.
The Problem¶
Flood model setup is the most time-consuming task in hydraulic engineering. It relies on repetitive manual work and subjective decision-making. If a mesh is regenerated, all hand editing is lost. Models live as files on individual machines with no version control, no collaboration, and no audit trail.
Meanwhile, ANUGA, one of the most capable 2D solvers available, has been locked behind a Python scripting interface for 20 years. Excellent physics, near-zero accessibility for practicing engineers.
What Hydrata Does Differently¶
| Traditional Workflow | Hydrata |
|---|---|
| Convert DEM in GIS, export, import to model | Upload DEM directly, Hydrata handles projection and tiling |
| Define boundaries in separate tools | Draw boundaries in the browser on your terrain data |
| Hand-edit mesh in desktop software | Mesh generated from your DEM and region definitions |
| Run simulation on local hardware | Submit to cloud compute, results in minutes |
| Post-process in GIS, format for reports | Results published as OGC WMS layers, shareable via URL |
| Email model files to colleagues | Team works on the same project, every change tracked |
Learn More¶
- Why ANUGA: the solver behind Hydrata, and why it matters
- Flood Modeling Challenges: industry-wide pain points and how Hydrata addresses them
- Validation: benchmark results and regulatory acceptance