Basin Assignment

Basin assignment maps drainage basins (HydraLink basins or Civil 3D parcels) to the inlet structures that capture them. HydraStorm enforces a one-inlet-per-basin rule to prevent double-counting and aggregates parameters using engineering-standard formulas when multiple basins drain to a single inlet.

One Inlet Per Basin

Every basin maps to at most one inlet. This constraint prevents the most common rational-method mistake: counting the same drainage area at multiple structures, which inflates downstream flows. HydraStorm flags any unassigned basin as a warning so you don't lose drainage area by accident.

One inlet, on the other hand, can capture many basins. The aggregation rules below apply.

Multi-Basin Aggregation

When N basins drain to one inlet, HydraStorm aggregates parameters as follows:

Drainage Area

A_total = Σ Ai

Total area is the sum of contributing basin areas.

Runoff Coefficient (Weighted C)

C_weighted = Σ(Ci × Ai) / Σ Ai

C is area-weighted across contributing basins. This is the standard rational-method aggregation rule and gives the area-correct combined runoff response.

Time of Concentration (Maximum Tc)

Tc_inlet = max(Tci) for i in basins

The longest contributing Tc controls — this is the time after which the entire combined area is contributing flow simultaneously. Using a shorter Tc would overstate the design intensity.

Assigning Basins

Open the Hydrology Table. Each row corresponds to a basin or parcel. The Inlet column lets you pick the structure that captures it.

  • Pick from the dropdown of network nodes
  • Or drag the basin onto a node in the profile/plan view (when supported)
  • Set to Unassigned to drop the basin from the analysis (with a warning surfaced in the calc-messages banner)

HydraLink Basin Mapping

When using HydraLink mode, basin-to-inlet mapping comes from name matching first (exact, then normalized, then fuzzy / Levenshtein), then spatial proximity (configurable radius in Project Settings, default 5 ft), then manual mapping. The HydraLink Integration page describes the full pipeline.

HydraLink Junction Intelligence

HydraLink junctions can be near inlets and represent already-accumulated basin parameters. When this happens, HydraStorm uses the junction's accumulated values directly and marks the contributing basins as consumed so they aren't double-counted.

Persistence

Assignments are persisted in your .hsp project file. They survive C3D drawing closes and parcel reloads. If a basin is removed (parcel deleted, HydraLink basin renamed beyond fuzzy match), HydraStorm flags the orphaned assignment so you can clean it up.

Tip: When a single inlet captures many basins of varying surface types, the weighted C is essentially a composite C — equivalent to manually computing a composite C for the impervious-pervious split.