16-Civ-B4 Engineering Hydrology · May 2017
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Paper format. 16-Civ-B4 Engineering Hydrology, National Exams May 2017. Three hours, CLOSED BOOK with one two-sided candidate-prepared aid sheet and an approved Casio or Sharp calculator. Seven Problems are printed; any five constitute a complete paper and only the first five answers in the work book are marked. Each Problem is worth twenty (20) marks for a total of 100, and the page-1 Marking Scheme gives the sub-part split for all seven — Problems 1 and 7 at (6)(6)(8), Problem 2 at (10)(10), Problem 3 at (7)(5)(8), Problem 4 at (8)(6)(6), and Problems 5 and 6 at (7)(7)(6). Note 1 invites the candidate to state any assumptions made where a question is open to interpretation; this sitting needs that licence twice, and both places are flagged in the callout below. All seven Problems are worked here, because this set is a study resource rather than a timed sitting. Five of the seven are pure discussion; the numerical content sits in Problem 2(ii) and Problem 7(i), with short illustrative calculations added elsewhere so that each method is shown working on real numbers.
Reference texts. V. T. Chow, D. R. Maidment and L. W. Mays, Applied Hydrology (hydrologic cycle, unit hydrograph theory, Horton infiltration, level-pool and Muskingum routing, frequency analysis); W. Viessman and G. L. Lewis, Introduction to Hydrology, 5th ed. (areal precipitation, hydrograph analysis, conceptual watershed models); P. B. Bedient, W. C. Huber and B. E. Vieux, Hydrology and Floodplain Analysis, 5th ed. (rating curves, reservoir and river routing, urban design storms); R. S. Gupta, Hydrology and Hydraulic Systems, 4th ed. (groundwater recharge and discharge, streamflow measurement); L. W. Mays, Water Resources Engineering, 3rd ed. (Rational Method, IDF design practice). For the Canadian frame: Environment and Climate Change Canada IDF curve files, the Water Survey of Canada Hydrometric Manual (mid-section gauging to ISO 748), and the Transportation Association of Canada Drainage Manual for design-storm and runoff-coefficient practice.
Check — two source-data issues and one declared convention.
(1) Problem 7(i) cannot be solved as printed. A basin of 10 000 km² draining at 2200 m³/s sheds a runoff depth of 6937.92 mm in a year, which is 115.6 times the 60 mm of rain the question supplies. The water balance then returns a large negative evapotranspiration, which is physically impossible. The runoff depth follows from the area and the discharge alone and is not open to interpretation, so the printed precipitation is the term in error. The answer boxes the runoff depth from the printed data, demonstrates that the balance cannot close, and then adopts a declared corrected precipitation under Note 1. Two admissible repairs are carried through with numbers so the assumption is auditable.
(2) Problem 2(ii) gives the IDF relation without units on the intensity. The relation i = 7.0 − 0.2t is read here in mm/h, which is the Canadian convention for IDF work; the alternative in/h reading is carried through as a one-line sensitivity, and it produces a peak flow 25.4 times larger that no 10 ha suburban storm sewer would ever be sized for.
(3) Problems 1, 3, 4, 5 and 6 are discussion questions with no data of their own. Where a numerical illustration makes the method concrete, the input values are the solver's own representative figures and are labelled as such. Every number in those illustrations, and every number taken from the real source data.
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.
A runoff hydrograph is a record of discharge against time at one gauged outlet, and every use made of it treats that single record as though it described the whole drainage area. Two assumptions carry that step.
Assumption 1 — the storm input is uniform over the basin and constant over its duration. The hydrograph is interpreted as the response to a rainfall depth that fell everywhere at once at the same rate. On a large watershed this is the weakest link in the chain: a convective cell may cover a tenth of the area, and a frontal system sweeping across a 1000 km² basin delivers its rain to the headwaters an hour or more before it reaches the outlet reach. The measured hydrograph then reflects the storm's movement as much as its depth, and a single areal average conceals it. This is why large basins are normally subdivided and routed rather than treated as one lumped unit.
Assumption 2 — direct runoff can be separated cleanly from baseflow, and the basin response is time-invariant. Interpreting a hydrograph means drawing a separation line under the rising limb and recession so that the area above it is the direct runoff volume attributable to this storm. The separation is a convention, not a measurement: it assumes groundwater discharge varies slowly and predictably during the event, and that the same basin will respond the same way to the same input next month and next decade. Antecedent moisture, frozen ground, seasonal vegetation and land-use change all violate the second half of that assumption, which is why hydrographs from one basin are stratified by season before they are averaged.
Two watershed properties dominate the shape that results.
Property 1 — size, shape and drainage density (the geometry of the flow paths). Area fixes the volume under the hydrograph for a given rainfall depth; shape and drainage density fix the timing. A compact, fan-shaped basin delivers water from all sub-areas at nearly the same instant and produces a short, sharply peaked hydrograph; an elongated basin of the same area spreads the arrivals over a longer window and produces a flatter, later peak with the same volume beneath it. A dense drainage network shortens overland-flow lengths, moves water into channels sooner, and raises the peak.
Property 2 — slope and surface condition (soil, land use and available storage). Relief and channel slope set the velocity and hence the time of concentration: steeper basins concentrate faster and peak higher. Soil infiltration capacity and land cover set how much of the rainfall becomes runoff at all — an urbanised basin with 60 per cent impervious cover converts a far larger fraction of a given storm into direct runoff than the same basin under forest. Lakes, wetlands and floodplain storage work in the opposite direction, absorbing the crest and releasing it slowly, which flattens and delays the peak without changing the volume.
The unit hydrograph is the direct-runoff hydrograph produced by one unit depth (1 cm or 1 mm) of effective rainfall falling uniformly over the basin in a specified duration. Two assumptions turn it from a description of one storm into a transfer function usable for any storm.
Assumption 1 — linearity (proportionality and superposition). The basin is assumed to behave as a linear system: doubling the effective rainfall depth doubles every ordinate of the direct-runoff hydrograph without changing its shape or its time base, and the response to a sequence of rainfall blocks is the sum of the individually lagged responses. This is what licenses the convolution $Q_n=\sum_{m} P_m\,U_{n-m+1}$ used to build a storm hydrograph out of a unit hydrograph. Real basins are not linear — higher intensities recruit flow paths and overbank storage that lower ones do not — so unit hydrographs are derived from storms of comparable magnitude to the design event.
Assumption 2 — time invariance, with uniform effective rainfall of the stated duration. The base time of the direct-runoff hydrograph is assumed constant for all storms of the given duration, and the basin's response is assumed not to change with season or with the years. This is inseparable from the requirement that the effective rainfall be uniform in space over the whole gauged area and uniform in time over the unit duration, which in practice restricts unit hydrograph derivation to isolated single-peaked storms on basins usually smaller than a few thousand square kilometres. A third assumption is often stated with these two and is worth remembering: effective rainfall excess is uniformly distributed across the basin, so the same loss rate applies everywhere.
[Figure not reproduced: The iterative framework of the source figure. Parameterization carries the real watershed into the conceptual model; model formulation carries the model into a numerical scheme; model results feed back into the model, and validation carries them back to the watershed. See the official exam paper.]
The figure is not a one-way calculation chain — it is a closed loop, and the loop is what makes it useful for risk work. Parameterization converts the physical watershed into a parameter set (areas, imperviousness, infiltration parameters, storage-discharge relations). Model formulation chooses the governing equations. Numerical model and analysis solves them. Model results return to the model, and validation compares them against what the real watershed actually did. Every quantity in that circuit is uncertain, and running the loop repeatedly — over an ensemble of parameter sets, storm inputs and formulations — converts a single deterministic answer into a distribution of answers. Reliability and vulnerability are two different readings of that distribution.
(1) Reliability is the probability that the engineered system performs its intended function over a stated period. For a retention pond built to attenuate downstream flooding, the performance function is something like peak outflow stays below the downstream channel capacity, or the water level stays below the emergency spillway crest. The framework delivers it in three moves. Parameterization is sampled rather than fixed, so the infiltration parameters, the runoff coefficients and the stage-storage curve are each drawn from their plausible ranges. The numerical model is then run over a long series of storms — a continuous simulation of decades of climate record, or a Monte Carlo set of design events — and each run is scored pass or fail against the performance function. Reliability is the fraction of runs that pass. Validation closes the loop by supplying the residual error distribution: comparing modelled and observed hydrographs for real events tells you how much of the spread is genuine hydrologic variability and how much is model error, and a model that cannot reproduce observed events has no standing to make a reliability statement at all.
A pond sized to pass the 100-year event has an annual failure probability of $p=0.01$ if the climate is stationary, so over a 50-year service life its reliability against that mode is
$$\mathrm{Rel}=(1-p)^{n}=(1-0.01)^{50}=\boxed{0.605}$$
— a 39.5 per cent chance of at least one exceedance in the design life. That number, not the return period, is what a client or an approving authority should be shown.
(2) Vulnerability is the consequence side of risk: given that the system is exceeded, how bad is it? Reliability alone cannot answer this, because two ponds with identical failure probabilities can fail very differently — one overtopping gently onto a grassed floodway, the other breaching. The same framework answers it by running the numerical model past the design point: force it with the 200-year and 500-year events, with an event on saturated antecedent conditions, or with a blocked outlet, and read from the results the depth, extent, velocity and duration of downstream flooding. Those are the quantities that convert into damage, and they are what a vulnerability assessment reports. Model formulation matters more here than anywhere else in the loop, because a model calibrated on in-bank events may have no valid representation of overbank spreading; the feedback arrow from numerical analysis back to model formulation exists precisely so the structure can be revised when the results are pushed outside the range in which they were validated.
Taken together the two readings give the standard risk statement risk = probability of exceedance × consequence of exceedance. The engineering value of the iterative framework is that both factors come out of the same calibrated model, so the design decision — how much freeboard, how large an emergency spillway, whether to add a second cell — can be defended on consequence as well as on frequency.
