HydraStorm's companion application HydraLink provides stormwater hydrology modeling including rainfall-runoff analysis, detention pond design, and culvert analysis. Import HydraLink results directly into HydraStorm to drive your storm drain hydraulic design.
| Extension | Description | Contents |
|---|---|---|
.hyd |
HydraLink native project file | Basins, junctions, ponds, storm events, full model definition |
.hlresults |
Pre-computed results export | Peak flows, outflows, volumes, stages |
.hyd or .hlresults file using the file picker..hyd file contains multiple plans.
HydraStorm uses a multi-step pipeline to match HydraLink elements (basins, junctions, ponds) to Civil 3D pipe network structures. The matcher tries each strategy in order and stops at the first successful match:
HydraLink models often include both basins (drainage areas) and junctions (confluence points that accumulate basin flows). HydraStorm handles this intelligently:
Different HydraLink element types provide flow data from different result fields:
| Element Type | Flow Field | Description |
|---|---|---|
| Basin | peak_flow_cfs |
Peak runoff from the drainage area |
| Pond | peak_outflow_cfs |
Routed outflow after detention |
| Culvert | peak_outflow_cfs |
Outflow from the culvert analysis |
HydraStorm monitors the linked HydraLink file for external changes. When HydraLink saves an update to the file, HydraStorm displays a notification in the status bar prompting you to reload the updated data.
This enables a live workflow: make changes in HydraLink, save, then reload in HydraStorm without manually re-importing.
In rational-method modes (HydraLink, Parcels, Manual), HydraLink can provide basin parameters — drainage area, runoff coefficient C, and time of concentration Tc — rather than just peak flows. This allows HydraStorm to perform its own Tc accumulation through the pipe network and interpolate rainfall intensity from local IDF data.
This is particularly useful when the pipe network layout differs from the HydraLink junction network, since HydraStorm will recompute travel times based on actual pipe lengths and velocities.
Note: If your HydraLink project uses detention ponds, make sure to match pond outflows (not basin inflows) to the downstream pipe network structures. HydraStorm will use the routed peak_outflow_cfs value, which accounts for detention attenuation.