The Catchment Arrives in Square Meters, the Formula Wants km²
You trace a watershed off a digital elevation model, the attribute table fills in, and the polygon reports 3,450,000 m². Nothing downstream of that step is written that way. The design storm is a depth in millimetres, the gauge below the confluence reports specific discharge in litres per second per square kilometre, and the runoff spreadsheet asks for an area in km² before it returns anything at all.
So the first thing that happens to a delineated boundary is a change of scale: 3,450,000 m² becomes 3.45 km², and from there 25 mm of rain across the whole surface is 86,250 m³ of water heading for a single outfall.
Why Drainage Work Carries Two Area Scales
Rainfall is a depth, not a volume
Gauges normalise flow per km²
Delineation hands back raw metres
The hectare occupies the middle
Getting a Delineated Area into the Runoff Sheet
Convert once, at the moment the boundary leaves the mapping software, then carry that same square-kilometre figure through every later step so the volumes and the flow rates stay consistent with each other.
Paste the digitised area in
Drop the value from the attribute table into the m² box — 3450000, or 3 450 000 if it came across with spacing, since spaces are ignored and a comma works as the decimal mark just as a dot does. The result appears as you type.
Read the basin figure
The km² value is what the rainfall-runoff method, the gauge comparison and the report summary all expect. Keep two or three decimals on a small catchment; rounding 3.45 down to 3 throws away 13 % of the volume.
Step back down for the site works
Pond volumes, pipe areas and impermeable surfaces stay in metres. Press swap (↔) or type into the right-hand field — both boxes are editable — to bring a basin-scale number back to the scale the drainage details are drawn at.
Move the value without retyping
Each field carries a copy button that returns the number on its own, free of unit text and thousands spacing, so it lands in a hydrology spreadsheet as a number. Ctrl + C over a selection does the same.
Catchment Size, Rainfall Depth and the Water It Delivers
The volumes below are gross rainfall — everything that lands on the surface, before losses. Multiply by a runoff coefficient for the share that actually reaches the outlet, which on dense paving is most of it and on grassland over permeable soil may be a quarter.
| Digitised area | In square kilometers | Rain volume at 25 mm | Typical of |
|---|---|---|---|
| 5,000 m² | 0.005 km² | 125 m³ | Roof and driveway of one property |
| 20,000 m² | 0.02 km² | 500 m³ | Car park with its access road |
| 100,000 m² | 0.1 km² | 2,500 m³ | Ten-hectare housing estate |
| 500,000 m² | 0.5 km² | 12,500 m³ | Piped urban sub-catchment |
| 1,000,000 m² | 1 km² | 25,000 m³ | The unit gauge records use |
| 3,450,000 m² | 3.45 km² | 86,250 m³ | Delineated headwater catchment |
| 10,000,000 m² | 10 km² | 250,000 m³ | Rural stream above a village |
| 50,000,000 m² | 50 km² | 1,250,000 m³ | Tributary with a gauging station |
| 250,000,000 m² | 250 km² | 6,250,000 m³ | Split into sub-basins |
The middle of that table is where the reporting unit changes hands. Below roughly half a square kilometre nearly every drainage document stays in hectares and metres, because the surfaces being designed are roofs, roads and swales. Above a few square kilometres the paperwork switches for good, and a boundary still quoted in millions of square metres starts to look like an oversight even when the arithmetic is right.
What Helps When Checking a Runoff Figure
One page, both reporting scales
Basin figures travel up the scale and drainage details come back down it, so having both fields editable saves reloading the page halfway through a review.
Hectares in the same dropdown
The searchable unit list holds all 13 area units, so an impermeable-area return quoted in hectares can be dropped in without a second conversion step.
Values ready for the model input
The copy button strips the unit and the thousands spacing, so a figure goes straight into a sub-basin parameter table without a manual tidy-up afterwards.
Small fractions stay readable
Up to 8 decimals are shown before scientific notation takes over below 1e-6, keeping a 5,000 m² roof legible as 0.005 km² instead of collapsing to zero.
Catchment Area and Runoff Volume Questions
How much water falls on one square kilometer in a 25 mm storm?
A depth of 25 mm is 0.025 m and the surface is 1,000,000 m², so the gross total is 25,000 m³, or twenty-five megalitres. The building block behind it is that one millimetre over one square kilometre is 1,000 m³, so any depth and any basin size can be worked out in your head from there. Only part of it reaches the outlet: with a coefficient of 0.9 for dense paving expect roughly 22,500 m³, while pasture on free-draining soil might yield 6,000 m³ or less.
At what point should a catchment be reported in km² rather than hectares?
There is no rule, only a convention that follows the method in use. Site drainage and attenuation design stay in hectares because the things being sized are individual roofs, car parks and permeable strips. Once a boundary is delineated from terrain data and set against a river gauge, square kilometres take over, and in practice that happens somewhere between 0.5 and 1 km², which is 50 to 100 ha. A safe habit is to keep the raw square-metre value in the model and quote the km² version in the text, so the audit trail retains precision the report does not need.
What does a specific discharge of 10 L/s/km² mean for a small catchment?
Multiply it by the basin size: 10 L/s/km² across 3.45 km² gives 34.5 L/s, a flow you could step across. Expressing discharge this way lets a rate measured on a gauged basin be carried onto an ungauged neighbour without pretending the two are the same size. It also converts into a depth over time — 10 L/s/km² sustained for a year comes to roughly 315 mm of runoff, which can be tested against the local rainfall record for plausibility. When a computed value sits far outside the range of nearby gauges, suspect the area figure before you suspect the hydrology.
Does the rational method take the catchment area in km² or in m²?
Neither, in the sense that it depends which arrangement of the formula sits in front of you — and mixing them is a classic way to be out by a factor of a hundred. In the metric form Q = C i A / 3.6, peak flow Q is in m³/s, intensity i is in mm/h and A is in square kilometres. A second common arrangement, Q = C i A / 360, is identical except that A is in hectares. For a 3.45 km² basin with C = 0.35 and i = 50 mm/h the result is 0.35 × 50 × 3.45 ÷ 3.6 = 16.8 m³/s. Most drainage manuals also restrict the method to small areas, often a few square kilometres at most.
Why does time of concentration grow more slowly than catchment area?
Travel time follows the longest flow path, and path length grows roughly with the square root of the surface rather than in step with it. Doubling a basin from 3.45 to 6.9 km² lengthens that path by about 40 %, and empirical expressions such as Kirpich raise length to a power below one, so the resulting time typically rises by only a quarter to a third. The practical consequence is that a larger basin is paired with a longer, gentler design storm at a lower intensity, which is why peak flow per unit of surface falls as basins grow even though the total volume climbs in direct proportion.
No comments yet. Be the first to comment!