19.07.2013 Views

London scoping - ukcip

London scoping - ukcip

London scoping - ukcip

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Final Report<br />

71<br />

The question naturally arises as to what extent the Thames water resource strategy (EA, 2001c)<br />

might be affected by climate change? This can only really be answered through an integrated<br />

regional water resource modelling exercise, that incorporates more climate change detail within<br />

the Agency’s four socio-economic scenarios. Alternatively, research could be targeted at<br />

critical elements in the strategy, such as modelling the reliable yield of a new reservoir, or levels<br />

of leakage, under the full set of UKCIP02 scenarios.<br />

5.5 Flood Risk<br />

5.5.1 Context<br />

Both observations (Frei and Schar, 2001; Karl and Knight, 1998; Osborn et al., 2000) and<br />

climate models (Jones and Reid, 2001; McGuffie et al., 1999; Palmer and Räisänen, 2002)<br />

support the view that the frequency and intensity of heavy rainfall increased during the 20 th<br />

Century, and will continue to increase in coming decades, particularly during the non-summer<br />

seasons. However, there have been very few credible studies of riverine flood risk in relation to<br />

climate change. This is a reflection of the difficulties associated with adequately modelling<br />

high-intensity precipitation (or snowmelt) events at catchment-scales, and of representing landsurface<br />

controls of storm runoff generation (Bronstert et al., 2002).<br />

Assessing flood risk for <strong>London</strong> is problematic, not least because of the extent of the urban<br />

drainage system, and the localised effects of blocked culverts (open watercourses which have<br />

been covered over i.e. at road crossings, culverts may also run under buildings) and/or<br />

exceedance of hydraulic capacity of sewers. In addition, future flooding of the Thames estuary<br />

will require consideration of complex interactions between sea level rise, runoff from land areas<br />

and storminess (Holt, 1999; Lowe et al., 2001; Von Storch and Reichardt, 1997). Accordingly,<br />

flood risk will be considered from three overlapping perspectives: 1) riverine flood risk; 2) the<br />

design capacity of urban drainage systems and; 3) tidal surges/sea level rise.<br />

5.5.2 Case Study<br />

Riverine flood risk in the Thames Region<br />

A simplistic climate change impact assessment – illustrated below – is to infer future riverine<br />

flood risk from future changes in extreme precipitation events. For example, in a recent pilot<br />

study, the regional climate model HadRM2 (the predecessor of the model used in UKCIP02)<br />

predicted future increases in the magnitude of rainfall extremes of 30- and 60-day duration (as<br />

experienced in the flooding of October/November 2000) over catchment areas influencing river<br />

levels in Lewes, Shrewsbury and York (CEH and Meteorological Office, 2001). Other studies<br />

have examined changes in effective rainfall (as a proxy for discharge) obtained directly from<br />

global climate models for large river basins (e.g., Milly et al., 2002), or downscaled<br />

meteorological variables to the scale of an experimental watershed for hydrological modelling<br />

(e.g., Pilling and Jones, 2002).<br />

Government estimates suggest that the value of protected land and property within the Thames<br />

region tidal Thames flood risk area is £80 billion giving a flood damage estimate of the order of<br />

£30 billion (DEFRA, 2001). With growing demand for new housing in <strong>London</strong> and the<br />

preferred use of brownfield sites (often situated within the floodplain), these figures are set to<br />

increase notwithstanding changes in climate. The river defences of central <strong>London</strong> are designed

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!