IDF (Intensity-Duration-Frequency) data drives the rainfall intensity calculations used by the Rational Method. HydraStorm supports multiple data sources and fits all IDF data to a standard three-parameter equation for interpolation.
Where:
The b, d, e coefficients are specific to the project location and return period. This is the same three-parameter form used by TxDOT and most published drainage criteria manuals, and the same one HydraLink uses.
The fastest way to get IDF data for any location in the United States.
If you have already downloaded IDF data tables from the NOAA Atlas 14 website:

When using HydraLink mode, IDF coefficients can be imported directly from the HydraLink project file. HydraLink supports both:
Many drainage criteria manuals publish a table of intensity against duration rather than equation coefficients, and require you to use it. Type it in directly:
You can also enter the b, d, and e coefficients directly, without a table, when the manual publishes its own IDF parameters, one row per storm in the coefficient grid.
All IDF data lives in the Project Settings > Hydrology > IDF Curves sub-tab: an editable duration/intensity table with one column per storm, the interpolation method radio buttons, the per-storm equation coefficients with a Generate from Table button, and a log-log IDF chart. Choose how HydraStorm looks up intensity for a given Tc:
i = b / (Tc + d)e within its fitted duration window, instead of interpolating the table. Below the shortest fitted duration the intensity is held at the fit-window value (with a warning) rather than extrapolated; above the longest fitted duration the lookup hands off to the intensity table when one covers the storm.In the two table-based modes (Log-Log, Linear), HydraStorm always reads from the intensity table, even if fitted coefficients also exist alongside it. In Coefficients mode, the fitted equation is the primary source inside its fitted duration window; the table serves the durations the equation shouldn't: storms with no coefficients, and durations beyond the fit window that the table covers.
A duration table has no data past its last row, and intensity must keep falling as Tc grows. Below the table's first duration, HydraStorm holds intensity at that first row's value (a standard short-duration clamp). Above the table's last duration it also holds flat — a longer Tc than the table covers gets the same intensity as the longest tabulated duration, never a lower one. A flat hold at the long end is not conservative: it over-states intensity for every Tc past the table, silently over-sizing everything downstream of a headwater basin whose Tc runs long. When this happens, HydraStorm raises one aggregate calculation warning naming the affected nodes. If a project routinely runs Tc past the table's longest duration, extend the table or switch to Coefficients mode, where the equation keeps decaying past the fit window instead of clamping.
Two things about the fit are worth knowing:
The R-squared value shown after fitting tells you how well the equation reproduces your data: values above about 0.99 are typical for Atlas 14 data. A noticeably lower value usually means the source table spans an unusually wide duration range or contains a bad row.
Each storm on the project's Storm Events list carries its own intensity column and its own b, d, e row, for design, check, and any additional analysis storms alike. Generate from Table fits every storm that has at least three durations, and names any it could not. For example:
| Storm | Return Period | b | d | e | Fit (R²) |
|---|---|---|---|---|---|
| Design | 10-year | 96.3 | 13.8 | 0.874 | 0.996 |
| Check | 100-year | 142.7 | 14.2 | 0.851 | 0.994 |
The grid's Fit (R²) column reads “—” for a row whose b/d/e were typed by hand rather than fitted — there's no residual to report against a table that was never used. Each storm event uses its own IDF curve for intensity interpolation.
After fitting or entering IDF coefficients, verify the results by checking:

Note: The IDF Curves sub-tab shows in every hydrology mode except Peak Flows Only, where flows are provided directly and no intensity lookup happens at all. In HydraLink mode the whole editing surface — table, coefficients, interpolation method, lat/lon, and every fetch/import/generate command — is read-only with a lock note, because the linked file is authoritative for this data (including which interpolation method HydraLink's own preferred_source setting implies, and the coefficient letters, which HydraStorm resolves against the exporting HydraLink version rather than reading positionally — older exports order b/d/e differently under the same file format). Switch to Manual to edit it directly.
Note: A rational hydrology mode needs a usable intensity source for every configured storm return period, not just design and check — see IDF Curve on the Rational Method page for what happens (an OK-gate block in Project Settings, and a calculation error if the data goes missing later) when one isn't.