NivaarExam PrepOfficial exam papers ↗

16-Civ-B4 Engineering Hydrology · May 2015

Question 2 of 7: Runoff Hydrographs, Unit Hydrographs and Conceptual Models

Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)

Notes on this paper

Paper format. National Examination, May 2015, 98-Civ-B4 Engineering Hydrology, three hours’ duration, closed book with one two-sided candidate-prepared aid sheet (8½″ × 11″) and an approved Casio or Sharp calculator whose model must be declared in the work book. Seven problems are printed; page-1 Note 4 states that any five (5) questions constitute a complete paper and that only the first five answers appearing in the work book are marked. Each problem is weighted at twenty (20) points, so the examinable total is 5 × 20 = 100 points. The page-6 marking scheme gives the sub-part split for every problem. All seven problems are solved here, because this set is a study resource rather than a timed sitting; the sub-part mark values shown below are the printed ones.

Reference texts. V. T. Chow, D. R. Maidment and L. W. Mays, Applied Hydrology (hydrologic cycle, unit hydrographs, routing, frequency analysis, infiltration); L. W. Mays, Water Resources Engineering, 3rd ed. (design application, rainfall–runoff, reservoir operation); W. Viessman and G. L. Lewis, Introduction to Hydrology, 5th ed. (measurement, areal precipitation, energy budget); V. T. Chow, Open-Channel Hydraulics (1959) (flood-wave propagation, dam-break and gradually varied unsteady flow); C. W. Fetter, Applied Hydrogeology, 4th ed. (Darcy’s law, hydraulic conductivity, advective transport). Canadian practice references: Environment and Climate Change Canada / Water Survey of Canada HYDAT archive and the ECCC Engineering Climate Datasets (IDF curves and the IDF_CC climate-adjustment tool); ISO 1100 / WMO Manual on Stream Gauging (stage–discharge rating practice); and the Canadian Dam Association Dam Safety Guidelines (inflow design flood, dam-break inundation mapping).

Check — Problem 7(i) source data are internally inconsistent. As printed, the 10 000 km2 basin receives 50 mm of rain in a year while its river carries 200 m3/s, which is a runoff depth of 630.72 mm — about 12.6 times the stated rainfall. No basin can discharge more water than it receives, so the printed precipitation is in error (almost certainly a lost order of magnitude), not the discharge. Problem 7(i) below boxes the runoff depth first, demonstrates that the balance cannot close, and then adopts a declared corrected annual precipitation of 1000 mm/a to complete the estimate. Every number is flagged where the correction is used.

Question 2: Runoff Hydrographs, Unit Hydrographs and Conceptual Models (20 marks)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

(i) How a runoff hydrograph is generated, and two controlling watershed properties (6 marks)

A runoff hydrograph is generated by two successive operations on a storm: a loss operation at the land surface that decides how much of the rain runs off, and a routing operation that decides when it arrives at the outlet. Rain first satisfies interception by canopy, depression storage in surface hollows, and infiltration into the soil at the prevailing infiltration capacity. What remains is effective rainfall. That excess moves as sheet flow, concentrates into rills and swales, enters the channel network, and is translated and attenuated down the channels to the gauge. On a large watershed each elementary area contributes with its own travel time; the hydrograph at the outlet is the superposition of all those delayed contributions, which is exactly why it has a smooth rising limb, a single broad crest and a long recession rather than reproducing the shape of the storm. Groundwater discharge from bank and aquifer storage continues after the storm and forms the baseflow underneath the whole event.

Compact, steep, urbanised basin outlet Elongated, flat, forested basin Qt high, early peak low, late, drawn-out peak same rainfall volume → same area under both curves
Figure 2.1 — Two basins of equal area and equal storm depth. Shape/slope and land cover redistribute the identical runoff volume into very different hydrographs.

Property 1 — basin shape, size and slope (the geometry that sets travel time). A compact, steep basin delivers all of its area to the outlet at nearly the same moment, so the time of concentration is short and the same runoff volume is compressed into a high, early peak. An elongated or flat basin spreads arrival times, producing a lower, later, broader hydrograph. Since the area under the direct-runoff hydrograph is fixed by the effective rainfall volume, anything that shortens the response necessarily raises the peak.

Property 2 — soil type and land cover (the surface that sets the loss rate). The infiltration capacity of the soil and the degree of impervious cover determine what fraction of the rain becomes effective rainfall. A sand or well-drained forest soil may absorb most of a moderate storm, whereas a clay till or a 60 %-impervious subdivision converts most of it to runoff. Urbanisation acts on both properties at once — it raises the runoff coefficient and shortens travel time through gutters and storm sewers — which is why development typically multiplies the peak of a frequent event several-fold. Antecedent moisture condition modulates this: the same storm on a saturated basin produces far more runoff than on a dry one.

(ii) An engineering application of the unit hydrograph, and two limitations (7 marks)

The unit hydrograph (UH) is the direct-runoff hydrograph produced by one unit depth (1 cm or 1 in.) of effective rainfall falling uniformly over the basin in a specified duration. Its engineering value is that it converts a rainfall statistic — which is what long records and IDF curves give — into a discharge hydrograph.

Application: deriving a design flood for a spillway, culvert or detention pond on an ungauged or short-record basin. The procedure is standard Canadian practice: take the design rainfall depth for the required return period from the ECCC IDF data, distribute it in time with a design storm profile, subtract losses (SCS curve number, Horton, or Green–Ampt) to obtain effective rainfall, then convolve that hyetograph with the basin’s unit hydrograph and add baseflow. The result is a complete design inflow hydrograph — peak, volume and shape — which is what a detention pond or reservoir routing calculation actually needs. A single peak flow from a rational-method calculation cannot size a storage facility; a hydrograph can.

As a numerical illustration, if a basin’s 2-hour unit hydrograph has a peak ordinate of 45 m3/s per cm and a design storm yields 2.5 cm of effective rainfall in one 2-hour block, linearity gives a direct-runoff peak of

$$Q_{p,\text{direct}} = 45 \times 2.5 = 112.5\ \text{m}^3/\text{s}, \qquad Q_{p,\text{total}} = 112.5 + 15 = \boxed{127.5\ \text{m}^3/\text{s}}$$

with 15 m3/s of baseflow. Multi-block storms are handled by lagging and summing the scaled copies.

Limitation 1 — the basin is assumed linear and time-invariant. Doubling the effective rainfall is assumed to double every ordinate (proportionality), and separate rainfall blocks are assumed to superpose without interaction. Real basins are not linear: at high flows the floodplain engages, channel velocities and storage change, and the response speeds up or slows down. A UH derived from moderate storms therefore tends to under-predict the peak of a very large event. Time-invariance fails too — a UH derived before urbanisation, channelisation or a wildfire no longer describes the basin, so UHs must be re-derived after significant land-use change.

Limitation 2 — uniform rainfall over the basin in the stated duration. The UH assumes the effective rainfall is spread evenly in space and constant in time over its duration. That is defensible on a small basin under a frontal system; it fails badly on a large basin (say, above a few hundred square kilometres) and under convective storms, where a cell covers a fraction of the area. The remedy is to subdivide the watershed into sub-basins, each with its own UH and its own rainfall input, and route the sub-basin outputs downstream. Related practical constraints: the method describes direct runoff only, so baseflow must be separated and re-added by judgment, and a UH cannot be derived at all without at least one well-gauged storm with concurrent rainfall — on ungauged basins a synthetic UH (Snyder, SCS dimensionless, Clark) must be substituted, importing the parameter uncertainty of the regional relations it is built on.

(iii) Three tasks in building a watershed conceptual model, and two limitations for decision makers (7 marks)

A conceptual model is the agreed, documented description of how water and contaminants move through the watershed — the stores, the fluxes between them, and the boundaries — written before any numerical model is built. For a rapidly developing watershed it is the instrument that lets a council, a regional district or a First Nation compare development scenarios on a common technical basis.

Task 1 — delineate the system and compile the baseline data. Establish the surface-water divide from a DEM and, separately, the groundwater flow system, which need not share the same boundary; identify sub-catchments, the channel network, wetlands, lakes and the aquifer units with their confining layers. Compile the baseline record: precipitation and climate normals from ECCC, streamflow from the Water Survey of Canada HYDAT archive, water levels and lithologs from the provincial well database, water-quality sampling, soils, surficial geology, and a current land-use/land-cover layer. This step also fixes what “existing conditions” means — the datum against which every development scenario will later be judged.

Task 2 — construct the water and mass balance and identify the dominant processes. Quantify each term of the balance — precipitation, evapotranspiration, surface runoff, infiltration and recharge, groundwater discharge to streams, and abstractions and discharges — at an annual and a seasonal time step, and check that it closes within a stated uncertainty. Alongside it, build the contaminant conceptual model: sources (septic systems, road salt, agricultural nutrients, construction sediment), pathways (overland flow to streams, infiltration to the water table, advective transport to wells), and receptors (drinking-water wells, fish habitat, recreational waters). The output is an explicit statement of which processes control the outcomes that matter, which is what tells the modeller what the numerical model must represent.

Task 3 — formulate scenarios, indicators and thresholds, then test the model. Define the development scenarios to be examined (build-out under current zoning, a low-impact-development alternative, a no-growth reference) and the indicators that will be reported — peak flow for a given return period, annual recharge volume, baseflow in the low-flow month, chloride or nitrate concentration at receptors — each with a threshold drawn from provincial water-quality guidelines or habitat requirements. Then calibrate against the observed record and confirm the model reproduces both flow and quality behaviour under conditions it was not fitted to (Problem 4(ii)). Document assumptions, data gaps and uncertainty in the same report, and set up the monitoring that will confirm or refute the model as development proceeds.

Limitation 1 for decision makers — it is a simplification calibrated to the past. The conceptual model lumps heterogeneous soils, aquifers and land uses into a manageable number of units, and its parameters are fitted to a historical record. It therefore carries real uncertainty that is rarely reported as a single number, and it is weakest exactly where decisions are most consequential — extrapolation to conditions outside the calibration range, such as a build-out land use that has never existed or a design storm larger than any in the record. Under a changing climate the assumption of a stationary rainfall regime is itself a limitation. Decision makers should treat model output as a comparison between scenarios rather than an absolute prediction, and should ask for the uncertainty band with every number.

Limitation 2 — it answers hydrologic questions only, and only at the resolution it was built for. A watershed conceptual model does not weigh economic, social or jurisdictional trade-offs, and cannot decide policy; it also cannot resolve site-scale questions — a single lot’s drainage, a particular well’s capture zone — if it was assembled at sub-catchment scale. Using it below its resolution produces confident-looking numbers with no support. Practically, it is also a living document: it goes stale as development proceeds and must be revisited on a stated cycle, and the monitoring that would keep it current is the first item cut from a budget.