Flood Model Guidance v2
Flood Model Guidance v2
Responsible Authorities
Version 1.1
1 Executive Summary
Developing our knowledge of flooding and how we can effectively assess potential impacts
on our communities is essential in implementing effective and sustainable flood risk
management plans. Flooding is a complex natural process arising from a range of sources
(e.g. rivers, sea, surface water/pluvial) and from a range of mechanisms. Using information
on the characteristics of floods we are able to assess the potential impact of floods using
computer simulations. Computer flood models are key tools in assessing, testing and
informing the delivery of flood risk management actions; while there will remain inherent
uncertainty in representing natural systems, quality models enable the production of flood
maps and data that support communication with the public and enable key policy and
investment decisions.
Appendices
The flood hazard and flood risk information which underpins flood risk management
decisions is often derived from computer flood models. Flood models use simplifications and
assumptions to represent complex natural systems and this leads to inherent uncertainty,
which must be acknowledged when making decisions based on model results. This
document therefore seeks to provide guidance for Responsible Authorities on where
uncertainty may arise in flood modelling and how it may be managed through the modelling
process so that it can inform appropriate decisions. An important component of this is that
contractors work to a common set of best practice guidelines in building models and in
documenting the modelling process; Responsible Authorities are encouraged to refer their
contractors to this guidance document to promote compliance with best practice. For site-
specific Flood Risk Assessments (FRAs) to inform land use planning, guidance is provided
in SEPA’s Technical Flood Risk Guidance for Stakeholders (SEPA, 2015). Table 2-1 shows
where this guidance and the Technical Flood Risk Guidance for Stakeholders should be
followed.
(Chapter 14)
The discussion in these
sections aims to give Calibration Calibration and
Responsible Authorities technical sensitivity testing
sufficient background to note (Chapter 8)
critically assess contractor
modelling.
Design runs
Key points for contractors (Chapter 9)
to ensure a consistent
approach, and quality of
flood modelling in Flood Mapping
Flood Maps
Scotland are given in red (Chapter 13)
boxes.
The guidance covers fluvial, pluvial and coastal flood studies. Fluvial and coastal studies
are covered in detail; however, for pluvial studies where a detailed representation of the
surface water drainage network is required, Scottish Water and CIWEM Urban Drainage
Group2 (UDG) guidance for modelling sewer systems should be followed. For studies
covering combined pluvial and fluvial flooding or combined pluvial and coastal flooding this
guidance should be used for the fluvial and coastal components of the studies.
2
Formerly WaPUG
Responsible Authorities often appoint specialist modelling contractors to carry out some or
all aspects of a flood study. Where they consider it appropriate Responsible Authorities may
pass this guidance onto their contractors and ask them to consider the relevant aspects in
their work. To assist with this, key points for contractors are highlighted in red boxes while
key points for Responsible Authorities are highlighted in green boxes.
SEPA is able to provide support for modelling studies at the following stages:
Scoping stage – SEPA can advise on any known linkages with other studies and the
suggested study area.
Data Collection – Details of the data held by SEPA which can be supplied for use in a flood
study are given in Chapter 5. Data held by other organisations which may be required for a
flood study is also given in Chapter 5.
Review of draft outputs – SEPA may be able to assist with the review of the following draft
outputs where included in the project scope; technical notes on hydrology tidal/coastal
boundary conditions, calibration results, draft design maps and flood levels, draft models and
the draft model report. SEPA may consider an independent review or audit of hydraulic
models to support consistent quality in Responsible Authority studies.
Due to the number of studies identified, in the first Flood Risk Management cycle, SEPA’s
resource requirements for supporting modelling studies are likely to be significant. To
enable SEPA to plan and prioritise input to studies it would appreciate being informed of
planned delivery dates for key project outputs and notification of any significant changes to
these timescales
3.1 Introduction
The first task is to define the scope of the study. This will establish the purpose of the
assessment, the level of assessment and the data requirements to inform decisions.
Notifying SEPA that a study is planned for a particular area will allow SEPA to provide
advice to feed into the scoping phases. In particular SEPA can advise on known linkages
with other studies and can provide details of hydrometric and other data (held by SEPA) for
the study area. It is recommended that SEPA’s Strategic Flood Risk team
(strategic.floodrisk@sepa.org.uk) and the appropriate Regional Flood Risk Planning
Manager are contacted to advise that the study is taking place.
Further information on scoping Natural Flood Management (NFM) Studies or studies with an
NFM component is given in Chapter 12.
Potential future uses of the model and outputs should also be considered, as this may
enable the model to be built in such a way as to maximise reuse, and will ensure that
necessary outputs are supplied.
To help understand the interaction of different actions across catchments and coastlines, the
Responsible Authority should use the source–pathway-receptor–impact approach to build a
conceptual model of the key processes which need to be considered in the study (Figure
3-1). This approach is a well-established framework in flood risk management. It provides a
basis for understanding the causal links between the source of flooding, the route by which it
is transmitted and the receptor, which suffers some impact:
• Sources are the weather events or conditions that result in flooding (e.g. heavy
rainfall, rising sea level, waves etc.);
• Pathways are routes between the source of flood waters and the receptor. These
include surface and subsurface flow across the landscape, urban drainage systems,
wave overtopping;
• Receptors are the people, industries and built and natural environments that can be
impacted upon by flooding;
• Impacts are the effects on exposed receptors. The severity of any impact will vary
depending on the vulnerability of the receptor.
For any area there may be multiple sources, pathways and receptors which interact with
each other.
In developing the conceptual model historic flood information for the area, including any
anecdotal evidence, should be examined. A catchment walk-over in conjunction with a
desk top review of Ordnance Survey maps and aerial photography should be used to identify
physical features which may affect flood pathways and possible receptors. Previous studies
and SEPA’s national flood hazard maps http://map.sepa.org.uk/floodmap/map.htm can also
be used to identify possible flooding mechanisms and whether they are adequately captured
by the previous modelling approach. For coastal areas the National Coastal Change
Assessment http://www.dynamiccoast.com/ should be used to identify areas where coastal
change may be a factor influencing flooding. The historic flood datasets which may be
available to help with developing a conceptual model are discussed in Section 5.4.
Available data should be assessed during development of the conceptual model in order to
determine the need for any additional data collection. Responsible Authorities may consider
assessing available data for studies later in a Flood Risk Management cycle so that data
gaps can be identified and filled prior to commencement of the study. Information on
relevant data is given in Chapter 5. A list of available data, with a brief description, should
Knowledge of the catchment should be set out briefly in the SoR, including any key areas
and known flooding mechanisms which need to be considered. These key features should
also be marked on a location plan to be included with the statement of requirements.
The conceptual model described in section 3.2 should be used in setting the study extent.
Consideration should also be given to the area of interest, availability of calibration data,
future use of the model and cost and time for a study
The study extent should be sufficient to represent the assumed flooding mechanism (i.e. it
should cover the flood source, flood pathway and any receptors). Boundaries of the study
area should be sufficiently far away from the area of interest, considering flow controls, to
have no impact on the results. Good places to set study boundaries are areas where the
flood extents are relatively constrained for large events or where there is a hydraulic control
such as a weir or tidal boundary. SEPA’s flood hazard maps
http://map.sepa.org.uk/floodmap/map.htm can be used with large scale mapping to identify
constrained sections, which should be reviewed at a site visit.
Data available for calibration should be considered in setting the study extent, as extending
the study area to cover calibration data may significantly improve confidence in the study
output. For fluvial studies covering gauged rivers it is strongly recommended that the study
extent covers at least one and preferably two or more gauges to assist in calibration. This is
discussed further in section 5.8 and Chapter 8.
The availability of topographic data should not be used to constrain the study area where
other considerations suggest that a larger area would be more appropriate. The preference
should be for additional data collection rather than a reduced study extent.
SEPA will consider the study area in deciding whether Responsible Authority studies can be
used to update the national hazard maps. For inclusion in SEPA’s hazard maps, studies
should cover reaches so that they can be tied in smoothly with the national mapping. As
inconsistencies between different modelling approaches may be particularly evident in urban
areas, studies should not normally have boundaries within continuous urban areas as shown
by the Scottish Government Urban Rural Classification 3. SEPA’s hazard maps are
strategic level and small study areas inconsistent with this level of mapping will not
be considered for inclusion in SEPA’s national flood hazard maps, although they may
be suitable for site specific FRAs submitted in support of planning applications. In this case
the guidance in SEPA’s Technical Guidance for Stakeholders on Flood Risk Assessment
should be followed (SEPA, 2015). Figure 3-2 shows considerations in setting study extents
for a hypothetical catchment.
The study extent should be set out in a location plan included with the SoR.
There may be cost efficiencies and quality improvements resulting from a joint study either
with partner organisations covering nearby areas or with organisations with different
objectives in the same study area.
In order to identify these opportunities, effort should be made to speak to the following
organisations during the scoping phase:
• Local authorities upstream or downstream of a study area along the same
watercourse, or along the same stretch of coastline.
3
http://www.gov.scot/Topics/Statistics/About/Methodology/UrbanRuralClassification
Glasgow City Council, East Dunbartonshire Council and SEPA worked together to
commission the River Kelvin study. This enabled the model to be calibrated against two
gauges in the river Kelvin catchment, increasing confidence in the results and ensuring
flood maps were consistent across the local authority boundary.
SEPA’s modelling framework sets out a hierarchical approach with 3 levels of assessment
national or strategic, catchment or feasibility and local or design, Figure 3-3 and Table 3-1.
In any tender the contractor should set out which modelling software will be used and why it
is appropriate to meet the project objectives.
In addition to the ability of the selected software to meet the project objective the
Responsible Authority should consider:
• If there is a sufficient pool of people in the industry experienced in using the selected
software to enable the model to be reviewed and audited
• If use of the proposed software will restrict future use and development of the model
to specific contractors, either because the software is in-house to a particular
contractor or because there are limited skills.
• If there is support and training available for use of the software to allow any bugs or
issues to be addressed and for expert advice to be sought for difficult or unusual
schematisations.
• Licensing options and cost if the Responsible Authority either wish to rerun or update
the model themselves or to view the model schematisation and results. However it
should be noted that higher license costs may add functionality necessary for
meeting the project objectives or be offset by improved workflows, customer support,
SEPA has licenses and skills in a number of modelling packages, Table 3-4, and may be
able to review models or assist local authorities in viewing models and results and rerunning
models if necessary. Some modelling packages either have free versions with limited
functionality, or viewers available at a reduced cost when compared to the full license.
Information on this is available from the relevant software suppliers.
Coastal
Modelling
1D Sewer
Software Supplier
1D River
2D Land
Software
Waves
Surge
FloodModeller 4 https://www.floodmodeller.com/en-gb/
Delft 3d / SWAN https://www.deltares.nl/en/software/delft3d-
4-suite/
HECRAS http://www.hec.usace.army.mil/software/he
c-ras/
Infoworks ICM http://www.innovyze.com/
Infoworks RS 2D
JFLOW http://www.jbaconsulting.com
MIKE FLOOD 5 http://www.dhigroup.com/
TUFLOW/ ESTRY http://www.tuflow.com/
Table 3-4: Flood modelling software currently used by SEPA.
4
Formerly ISIS.
5
The MIKE suite is capable of modelling waves and hydrodynamic flows with estuaries, but SEPA’s flood risk
teams do not currently have a license for this functionality.
4.1 Introduction
Responsible Authorities have commissioned and managed flood studies successfully over a
number of years. The guidance in this chapter does not aim to replace Responsible
Authority expertise or procurement and project management procedures, however it
highlights some factors which Responsible Authorities should consider in commissioning a
study to ensure:
4.4 Resources
The project must be adequately resourced from both the contactor and Responsible
Authority sides.
The contractor should demonstrate that sufficient staff are available with the correct level of
experience to deliver the project in their tender. This should include identification of an
internal reviewer with sufficient experience who is not directly involved in the project.
Contractors should also be able to demonstrate that they have sufficient computational
resources and software available to deliver the project.
The Responsible Authority should ensure that appropriate staff will be available at key points
in the project to enable timeous supply of data and information, and so that outputs can be
reviewed within the stated timescale.
4.5 Timescale/Milestones
A proposed programme should be included with all tenders. The programme should show
times when input from client and other external stakeholders will be required. A minimum of
10 working days should be allowed for the commissioning body and other stakeholders to
review draft outputs.
Where requested by the Responsible Authority, SEPA will seek to support Responsible
Authority studies within its resources. Due to the number of studies identified, SEPA’s
resource requirements for supporting modelling studies are likely to be significant over the
first flood risk management planning cycle. To enable SEPA to plan and prioritise input,
SEPA should be informed of planned delivery dates for key project outputs and notified of
any significant changes to these timescales.
An inception meeting can be combined with a walk-over survey or site meeting with an
appointed contractor. This is advised to ensure that there is a shared understanding of the
study area at the outset of the project.
The use of progress reports alongside an agreed programme of works is key to effective
project management. These should be at a suitable frequency commensurate to the scale
and complexity of the project, however fortnightly to monthly reporting in any agreed format
are typical frequencies.
Where data is provided by 3rd parties for use in the study, appropriate licensing agreements
should be in place to ensure that use of the data does not affect future use of the model. If
this is not possible the benefits of collecting new data rather than using the 3rd party data
should be assessed.
5.1 Introduction
A wide range of data is used in flood modelling Point to Note:
studies. Data requirements depend on the
project objective including any requirements for Data underpins a modelling study.
quality, the level of detail and adopted modelling Data requirements will be informed by
approach. At the scoping stage the Responsible study objective, time and budget.
Authority should seek to understand the data However, good quality data provides a
available and whether any new data is likely to significant step towards a good quality
be required as this can significantly affect the model.
cost, quality and timescales for a modelling
project. General data requirements for different
modelling approaches are set out in Table 3-2
• Start data collection early to avoid project delays. SEPA may be able to prepare
data requests prior to a contract being awarded.
• Data registers should be kept by the Responsible Authority and the contractor.
• Data licencing agreements should be in place for all data used within the
modelling study.
For most modelling activities some data will already exist, while other data will need to be
generated.
It is necessary to remember that the data collection process can take some time and may be
seasonally dependent; this needs to be incorporated into the project plan. Delays in data
collection or in providing data to contractors can cause significant project delays.
Where SEPA holds the data being requested, it may be able to respond to data requests
prior to the contract being awarded.
5.3.2 Licensing
Data licensing agreements should be in place for all datasets used within the modelling
study. This for example should stretch to include site surveys, the digital terrain model, the
hydrology and all model outputs. Where possible, licences should not restrict the future use
of any models or any derived data by SEPA or Responsible Authorities. SEPA should be
consulted for advice about how to proceed if a comprehensive licence cannot be achieved.
Topographic and bathymetric data is used in the construction of hydraulic models and in the
production of flood maps from the subsequent model results.
• There have been no major changes to the study area since the data was collected
including significant erosion or deposition, vegetation growth, construction of new
structures or alteration or removal of existing structures.
• The datum used for the existing survey is the same as for any new survey and any
DTM used in the study.
• That the IPR for the existing data allows reuse in this study
• The original survey is of an appropriate quality for the modelling study.
If in doubt a check survey should be used to ensure that the existing survey is suitable for
further use. The appropriateness of data for reuse depends on the purpose of the modelling
for instance, older channel survey data may be appropriate for strategic level mapping, but is
unlikely to be appropriate for detailed design. Where older topographic data is in paper
format only it may add considerably to the time and cost associated with model building as
well as increasing the possibility of human error. It should be noted however that there may
still be significant value in original engineering drawings from flood defence schemes,
culverts etc. and, where possible, these should be provided for use even if other survey is
considered necessary.
Survey data may be contained within existing models however, where possible, original
survey plans, drawings, photographs, and any other datasets should be supplied together
with the existing hydraulic model as:
In addition to requesting data in the correct format for import into modelling software, it is
recommended that data is also requested in the following formats:
• Drawings and plans of the survey in CAD software. This allows key points to be
clearly marked and for measurements to be scaled of drawings,
• GIS layers showing section locations and survey points, this allows cross sections
to be mapped quickly using GIS software.
• Photographs of cross sections and survey locations.
6
Storm Georiver http://storm-georiver.com/ and MBS Survey Software RXS Tools http://surveymbs.com/our-
software/mbs-rxs-tools
Access to the river should also be considered when commissioning a new survey. While
SEPA and Local Authorities have powers of entry under the FRM Act (section 79(1)) 7 it is
recommended that access is pursued by mutual agreement with landowners, taking
cognisance of any constraints. Introductory letters may be provided to surveyors to facilitate
access
5.5.4.2 Cross-Sections
The appropriate cross-section spacing depends on the physical characteristics of the
channel and the scale and purpose of the study; for instance, cross-sections may be further
apart for a channel with a uniform cross section and slope, and more frequent cross sections
may be required for design of flood defences. It is therefore difficult to provide general
guidance on cross section spacing, however generally:
• For large rural rivers on low slopes the maximum cross-section spacing should be
around 200 m;
• For smaller streams, sleeper slopes, or within urban areas the maximum cross
section spacing should be around 50 m;
7
The FRM Act gives powers of entry to persons authorised by SEPA (79.1) and local authorities (79.2) for
carrying out certain functions including the production of flood hazard maps and the preparation of flood risk
management plans.
Where the DTM is not of sufficient quality, typically areas where only NEXTMap data is
available (see section 5.5.5.1), there are quality issues with the LIDAR or significant ground
changes have occurred since the LIDAR was flown, extending cross sections across the
entire floodplain width may be desirable. An initial estimation of floodplain width can be
made from SEPA’s flood maps and checked during a site visit.
continuous flow path culvert, survey of inlet and Flow attenuation should be
through the gate. outlet structures and walk Short lades may generally accounted for in the hydrology.
through or CCTV survey be omitted.
identifying constrictions may
be sufficient.
Should generally be Should generally be Should generally be included The main flow path and Embankments and the main
included. Footbridges and included, unless from cross section survey. opening should be controls should be represented
Intermediate
pipe bridges may be omitted drowned at low flows. included based on survey explicitly.
if they are considered to Manholes and sewer data. It may be appropriate
have a negligible impact on connections may be omitted. to omit minor flow paths. Flow attenuation should be
flow e.g. wooden plank accounted for in the hydrology.
footbridges and some pipe
bridges.
Should generally be included Should generally be Should be included from All flow paths through the Embankments and spillways
unless clear span. included. cross section survey. Mill should generally be should be represented
Detailed
Table 5-3: Information required for modelling different types of hydraulic structures.
Ground models may be bare earth where features such as buildings have been removed,
usually referred to as a Digital Terrain Model (DTM), or may contain the elevations of
surface features (e.g. buildings, vegetation), commonly referred to as a Digital Surface
Models (DSM). DTMs are more commonly used in flood modelling.
DTMs may be constructed from ground-based topographic survey, from remote sensing data
(e.g. LIDAR) or from a combination of these. The required resolution and accuracy for a
DTM depends on the modelling objective and approach, and the study area. The DTM
resolution determines the finest possible 2D model resolution, as the resolution cannot
practically be increased beyond that in the available DTM. Further discussion on the
required resolution for 2D models is given in Section 7.3.1.
The accuracy depends on the method of data capture, and how well surface features have
been removed from the DSM to create the DTM. In areas with dense vegetation or buildings
the accuracy of the DTM may be reduced due to the need to remove features from the DTM.
Table 5-4 provides a summary of the different datasets available for Scotland together with
comments on their use and limitations. Generally LIDAR collected from aeroplanes is the
best DTM for flood modelling. Figure 5-2 shows current LIDAR coverage for Scotland.
Whether linear features such as flood defences, agricultural embankments, railway and road
embankments and cuttings and small watercourses are picked up in a DTM depends on the
resolution as well as the size of the structure. For this reason a DTM should always be
supplied to modellers at the highest resolution available. It is however unlikely that any of
the available DTMs for Scotland are of sufficient accuracy to determine elevations of flood
defences or resolve local drainage networks.
5.5.5.2.1 LIDAR
High mobilisation costs for airborne LIDAR may be prohibitive for surveys of small areas. It is
generally more cost-effective (in terms of the cost per km2 of data collected) to survey larger
areas; working in partnership with other organisations can increase the size of survey areas
and reduce costs.
Ground control points should be compared with the elevations in the LIDAR data and if
possible a data validation exercise should be carried out following data collection.
LIDAR should be flown when there is no dense vegetation cover as this may obstruct the
laser from reaching the ground surface. Generally, data collection should be carried out in
the period following significant autumn leaf fall and before the main spring growing season.
Where data collection is to be carried out during the winter months issues with snow cover
should be considered. Snow cover prevents the laser from reaching the ground surface.
Data collection should also not take place when the ground is flooded, as this will also
prevent the laser from reaching the ground surface. Surveys should be planned with some
contingency time to allow for local conditions. For coastal studies LIDAR should be flown as
close to low tide as possible to allow for a detailed representation of the coastline to be
collected.
Ground-based LIDAR can be used to collect more detailed data, such as kerb heights, which
may be of use for detailed surface water studies. The data collected in these surveys can
also be used to develop 3D visualisations of flooding.
Where the data is targeted at particular features, modellers may be able to combine the
ground based survey with existing remotely sensed DTM to create a new DTM. However,
there may be issues resolving inconsistencies between the 2 datasets especially in areas
where LIDAR is unavailable.
The European Marine Observation and Data Network EMODnet has produced a 1/8th arc
minute 8 resolution bathymetric dataset of European waters (approximately 130 m east-west
resolution and 230 m north-south resolution at 56º north). The bathymetry uses data from
hydrographic offices, authorities responsible for management and maintenance of harbours,
coastal defences, shipping channels and waterways, and research institutes and industry,
and General Bathymetric Chart of the Oceans (GEBCO) bathymetry where no other data is
available. The bathymetry is freely available from the EMODnet bathymetry portal. This
data is unlikely to be at a sufficient resolution for detailed coastal studies but may be suitable
for regional models. There are some discontinuities in the data at the boundaries between
datasets.
Some gridded and point data from the United Kingdom Hydrographic Office (UKHO) is
available under the Open Government License and can be downloaded from the UKHO
inspire portal http://aws2.caris.com/ukho/mapViewer/map.action. However, note that the
data has not been processed to remove conflicts between datasets at boundaries.
Harbour authorities may also have datasets which they are willing to share for flood studies
and should be contacted directly.
8 th
An arc minute is 1/60 of degree.
Where there are flood defences, or other structures which may be operated during flood
events, control rules and procedures will be required for any detailed study. Where
structures are manually operated, information on when they were operated during any
events to be used for calibration will be required.
Information on known/frequent blockage locations and dredging and weed cutting regimes
can be used to inform model sensitivity tests.
SEPA and the Responsible Authority may be able to identify if any existing models cover the
study area. Where existing models are available it should be considered whether they can
satisfy the new study. However, it should be noted that sometimes the modification of an
existing model to meet the objectives of a new project is as much work as starting from
scratch. Questions which may need to be considered are:
• What was the purpose of the existing modelling? Are there assumptions and
limitations which make it unsuitable for the new purpose?
• Is the study area appropriate or would it need to be extended?
• Is it at a sufficient level of detail at the study location, or is it too detailed? Are there
any areas of the model with lower confidence?
• Have there been any significant catchment changes since the model was
constructed?
• What data was used for the original model? Is better data now available e.g. LIDAR
instead of NEXTMap for the out of bank DTM, or are there known issues with some
of the original data sets?
• Are there any reasons to suspect that the existing model does not provide a good
representation of the system? Is the model calibrated?
• Is the model numerically stable, or are run times excessive?
• What software and version was used for the original study. Will it run in more recent
versions? Are there any significant changes to results between old and new software
versions?
• If the model was built for a flood prevention scheme is it a design model or an as built
model?
• Is the model georeferenced to enable flood mapping?
• Does the model contain sufficient out of bank representation to model the range of
scenarios required for the project?
• Do intellectual property rights allow the model to be used for the new study?
• Can the model be obtained by the Responsible Authority?
Irrespective of whether an existing model is to be reused for the new study, reports from
existing studies should be referenced by the new study. These reports may provide
information on historic flood events, highlight issues with adopting particular approaches for
the study area, and identify flooding mechanisms which require further analysis in the new
study or help in identifying the reasons for any discrepancies between the existing and new
studies.
Responsible Authorities should consider the need for any additional hydrometric data as
early as possible in a Flood Risk Management Planning cycle, as the greatest benefits are
likely to be obtained from a longer period of monitoring.
• River flow data held in the NRFA for Scottish sites is not up-to-date. Data for any
Scottish gauges used in the study should be requested from SEPA.
• Complete time series should be requested for any sites used in model calibration.
• Rain gauge data should be requested for gauges within, and surrounding the
catchment.
• Any Met Office data (if required) should be requested directly from the Met Office
enquiries@metoffice.gov.uk. Government bodies should include the phrase
Government Enquiry in the subject line to avoid being charged commercial rather
than government rates.
AMAX or POT series of flows are required for design flow estimation for fluvial flood studies.
AMAX series are sufficient, unless it is necessary to generate flow estimates for events with
a recurrence interval < 2 years, or the record length is < 14 years in which case POT series
are desirable. Data is required for any gauges within the study area, gauges upstream or
downstream of the study area along the same watercourse, for any sites used in a pooling
group and for any donor sites. AMAX series should be generated based on UK water years
(1st October – 30th September) rather than calendar years.
Peak flow estimates are derived from a stage-flow relationship (rating) that is calibrated
from sample flow measurements (gaugings) through as much as the flow range as possible.
However, the derived flow from the rating can only be guaranteed up to the highest gauging,
which is often well below the highest recorded stage. Derived flows above the highest
gauging are based on a simple extrapolation of the rating and are only credible up to bank
full level or as a rule of thumb, 10% above the highest gauged flow. The exception to this is
where any floodplain flow has been modelled. The upper limit of sensible derived flow from a
rating needs to be understood and factored into how the data is used. The local hydrometric
team can advise on rating limits for each station.
AMAX and POT series for some SEPA gauges is Point to Note:
available from the National River Flow Archive
(NRFA) managed by held CEH. This includes the Early engagement with the local
Peak Flows dataset for use with the Flood SEPA Hydrometry team is
Estimation Handbook (FEH) discussed in Section essential to confirm the availability
6.3. The Peak Flow Database has not been and quality of gauged data.
updated with SEPA data since October 2006,
however, SEPA has recently transferred revised and up-to date data to the CEH for 30
stations and these should appear on the website by the end of 2016. SEPA will work to
update all the SEPA gauging stations in the Peak flows station pool, currently numbering
140 stations, over the new few years. In the meantime, up to date AMAX for the study area
for any Scottish sites used in a pooling group analysis, and for any donor sites, should be
requested directly from SEPA. It is critical to liaise with the local SEPA hydrometric team to
ensure that flows are derived using the most appropriate rating for flood estimation. SEPA is
currently working to ensure that all AMAX are derived from the most appropriate ratings and
until this exercise is complete, a check with the local team is necessary. On occasion it may
be simpler for SEPA to supply level data and a rating rather than derived flow data. The
exercise also aims to produce POT datasets for those sites contributing to the Peak Flow. It
should be noted that SEPA may have revised its rating curves since the last update to
HiFlows-UK. These discrepancies will be resolved in future updates as per the exercise
described above. Updates on this project can be obtained from SEPA.
Time series of both flow and level are required for model calibration. Calibration events may
be identified based on a number of factors including data availability at several gauges and
in, most cases, it is easier to request complete datasets rather than submit multiple requests
for chunks of the same dataset. Time series of flow are required for any gauges within the
study area and gauges upstream or downstream of the study area along the same
SEPA’s Hydrometry team is able to provide information about the reliability of particular
gauges and suitability for measuring high flows, including a history of the site. Rating curves
are also useful for investigating any discrepancies between the flow record and model
output.
Other organisations such as Local Authorities or water companies may also operate flow or
level gauges.
On large costly projects consideration should be given to installing additional flow monitoring
equipment to collect data. This would be of particular advantage on ungauged watercourses
and could prevent over-design with resulting cost savings.
Radar data is available from the Met Office and may also be useful in model calibration. To
avoid being charged commercial rather than government rates, government bodies
(including local authorities) should request radar data directly from the Met Office
enquiries@metoffice.gov.uk and include the phrase Government Enquiry in the subject line.
Contractors should not request data directly from the Met Office.
Time series of rainfall may be used for calibrating fluvial and pluvial models. For calibrating
models data will be required for gauges within and surrounding the study catchment as the
most representative gauge may not be within the catchment and rainfall applied to a model
may be from area weighting rainfall from the a number of different gauges. If it is necessary
to generate antecedent conditions for the calibration events rainfall data may be required for
a long period prior to the calibration event. Calibration events may be identified based on a
number of factors, including data availability at several gauges, and in most cases it is easier
to request complete datasets rather than submit multiple requests for chunks of the same
dataset.
The FEH Depth Duration Frequency (DDF) model is generally used for generating design
rainfall so annual maximum and POT series are not usually required. The FEH DDF model
gives rainfall depth as a function of return period and storm duration for all catchments > 0.5
km2 and on a 1 km grid across the UK. Example output from the FEH DDF model is shown
in Figure 5-3. A new version of the DDF model (FEH 2013) was released in 2015, and
replaced the existing DDF model (FEH 1999) for a complete range of return periods and
durations. Both the FEH 1999 and FEH 2013 DDF models are available through the FEH
web service at https://fehweb.ceh.ac.uk/. The FEH 1999 DDF model is also available
through the FEH CD-ROM.
FEH 2013 incorporates a significant amount of additional data to FEH 1999 and uses an
improved statistical model. In Scotland FEH 2013 includes 176 hourly rain gauges
compared to 58 in FEH 1999 which is a significant improvement in data coverage for the
Figure 5-3: Example output from the FEH Depth Duration Frequency Model (DDF).
Data from the national tide gauge network can be obtained free of charge from BODC
https://www.bodc.ac.uk/data/online_delivery/ntslf/. There are 43 gauges within this network
of which Leith, Aberdeen, Wick, Lerwick, Kinlochbervie, Ullapool, Stornoway, Tobermory,
Port Ellen (Islay), Millport and Portpatrick are in Scotland. Both the measured sea level and
the residual or surge (difference between the measured sea level and the astronomical tide)
are supplied. Time series and monthly extremes are available.
Time series of measured sea level are required for calibration of coastal models and for the
tidal areas of fluvial models. Extreme series of sea level are used to develop design water
levels, however in most cases design sea levels in the Environment Agency Report Coastal
Flood Boundary Conditions for UK mainland and islands (McMillan, et al., 2011), described
in section 5.8.5.3 are used. Extreme sea level series are therefore only needed if it is
wished to extend the analysis to sub-annual events or areas within estuaries or sea lochs
which are not covered by the study.
The SEPA Coastal Hazard Mapping Project (Royal Haskoning DHV and JBA, 2013)
extended the extreme sea level analysis from the CFB study to sea lochs and estuaries
within Scotland but did not derive representative surge shapes for these locations. Where
surge shapes are required within sea lochs and estuaries, a hydrodynamic model may be
required to model how the shape of the surge changes within the estuary, section 6.5.1.
In the absence of long duration wave observations time series data at wave model offshore
boundaries are typically taken from wave model hindcasts. Wave model hindcasts are also
used to generate AMAX and POT series for design event analysis and are available on
request from the organisations noted in Table 5-6.
Contractors should not request data directly from the Met Office to avoid being charged
commercial rather than government rates. The NOAA model also covers the UK and is
available from the NOAA website although it is not calibrated specifically for the UK.
The available data from these models is typically wind wave, swell and resultant (wave
and swell combined) waves, significant wave height, mean period and mean direction;
the complete frequency spectrum is not usually available.
On large, costly projects consideration should be given to installing additional wave buoys to
collect data, this can be expensive, but will may increase confidence preventing over-design
with resulting cost savings.
9
https://www.ordnancesurvey.co.uk/business-and-government/public-sector/mapping-agreements/one-
scotland-mapping-agreement.html
6.1 Introduction
Hydrological analysis is required to determine design flows and probability of a flood. These
are used as input boundary conditions for hydraulic models.
Estimates of probability are not static but may change over time due to changes in climate or
catchment and due to changes in the data record or best practice flood frequency analysis
techniques. This means that it is important to review the hydrology for any new flood study,
even if a hydrological analysis has been carried out for a previous study.
Hydrometric data in the UK are generally of high quality; however uncertainty is inherently
present when conducting flood frequency estimates due to the length of record compared to
typical design probabilities of interest, the range of different of analysis methods available,
and the coverage of the gauge network.
• Give a brief description of the methods which can be used for hydrological analysis of
fluvial, pluvial and coastal flooding.
• Describe the outputs which would be expected from a hydrological study.
• Describe the circumstances in which SEPA may seek to support a review of
hydrological analysis.
• All flood frequency estimates are inherently uncertain and subject to change.
• The hydrology should be reviewed for any new flood study.
6.2 Terminology
Key points for Contractors
• Where possible, flood studies should use the annual exceedance probability
terminology rather than return period.
Two terms are commonly used to describe the flood frequency in the UK, the return period
and the annual exceedance probability.
• The return period of an event is the average interval between years containing an
event of the same or greater magnitude. A similar measure is the average
recurrence interval, which is the average period between events of a same or
greater magnitude.
• The annual exceedance probability (AEP) is the probability that an event of the
same or greater magnitude will occur in any one year. This is the reciprocal of the
return period.
Use of the terms return period or average recurrence interval can cause some confusion
amongst non-specialists who can misinterpret it to mean that events occur at fixed intervals.
For this reason use of annual exceedance probability, rather than return period is preferred.
6.3 Fluvial
• Design flows should not be finalised or signed off by either the Responsible
Authority or SEPA before model calibration and reconciliation is complete, and
should be reviewed and revised as a modelling study progresses.
• Identify key locations (reconciliation points) where it is important for flows in a
hydraulic model to match hydrological estimates, and agree the locations at the
inception meeting.
• The variation in design flows along a catchment should be physically justifiable
and explained in the modelling report.
• It may be necessary to run multiple model scenarios for the same AEP event in
order to match the design flow at different points in the model.
• Ensure that contractors allow time for appropriately experienced staff to review
any hydrological analysis. Encourage use of the supplied check list in Appendix
C.2 .
• Determine the robustness of all hydrometric data in consultation with local SEPA
Hydrometric teams.
• Compare flow estimates from statistical (single site and pooling) and rainfall-runoff
methods.
• Consider the method used to derive hydrograph shape and run large catchment
models for multiple storm durations if required.
• The modelling report should include sufficient details of the analysis to enable an
experienced hydrologist to reproduce the flow estimates.
• Further detail on approach to hydrological analysis is available in SEPA’s
Technical Guidance for Stakeholders.
• Refer to specific guidance in the FEH.
• Document the approach used for reconciliation in the modelling report, and give
values for any scaling factors.
For all fluvial flood studies the hydrological analysis will need to produce design flow
estimates. For studies involving unsteady modelling the hydrological analysis will need to
produce design hydrograph shapes. For catchment scale studies the analysis will also need
to consider the distribution of inflows.
In most cases hydrological analysis should be based on the methods in the Flood Estimation
Handbook (FEH) (Institute of Hydrology, 1999) which provides the industry standard
methods and guidance for fluvial flood estimation within the UK. The FEH largely
supersedes the Flood Studies Report (Institute of Hydrology, 1975) and its associated
reports. The FEH provides a framework for flood estimation, however user expertise and
experience is required to judge the most appropriate methods / data to use in any individual
circumstance. No single method is considered superior to others for all situations and in
some cases other flow estimation methods than those in the FEH may be appropriate
depending on the catchment characteristics. However, if FEH methods are not used a
comparison with FEH methods should be made with justification provided as to why the FEH
methods were not considered appropriate.
Responsible Authorities should note that hydrological analysis may be more complicated or
uncertain in the following cases:
• Urbanised catchments;
• Small catchments < 25 km2;
• Catchments containing reservoirs, lochs and hydroschemes;
• Pumped catchments;
• Assessment of natural flood management measures (Chapter 12).
This means that more time may be required to be allowed for the analysis, and/or there may
be lower confidence in the results. Where these factors exist within a catchment the
approach taken to deal with these cases should be discussed in the report.
All data received to support a flood study should be independently reviewed and checked
against the quality statements and advice of the data provider. This also applies to
hydrometric data. Before undertaking a hydrological analysis any hydrometric data supplied
for the project should be reviewed in full. SEPA makes every effort to ensure that all
hydrometric data supplied by SEPA is accurate however it is possible that some issues and
inconsistencies may only become apparent through use in a detailed flood modelling study.
As a minimum the data review should cover:
- Robustness of the rating for any gauges used in the statistical analysis e.g. variation
of the rating with time, hysteresis, location of any discontinuities
- Catchment changes which may mean that sections of the data series are no longer
valid e.g. construction of reservoirs.
- Gaps in the hydrometric data series.
- Suitability of the data for use in hydrological analysis. This should include a review of
whether the NRFA FEH indicative suitability is correct.
Any apparent anomalies should be discussed with the local hydrometric team.
For catchment or local scale models flow estimates using both approaches should be
compared and the adopted method justified. For all methods sufficient details of the analysis
should be given in an appendix to the modelling report to enable an experienced hydrologist
to reproduce the flow estimates.
Design flow estimates are required at the upstream boundary of any modelled watercourses
and at reconciliation points where it is important for the flow in a model to match the
hydrological estimates. Reconciliation points are typically chosen at:
• All gauging stations in the model domain
• Downstream of major confluences
• Key receptors such as urban areas
• Any points where the SOP of a flood defences is required.
Reconciliation points should be agreed between the Responsible Authority and the
contractor at he inception meeting.
Design flow estimates should be reviewed and revised as a modelling study progresses and
should not be accepted or signed off by either SEPA or the Responsible Authority
commissioning the study until calibration and reconciliation of any models is complete.
Where possible a combined hydrological- hydraulic approach should be should adopted for
model calibration, as the following could indicate both problems with design flow estimates
or missing processes and errors in a hydraulic model:
For gauged locations QMED is typically estimated from the AMAX or POT series at the
gauge, and these data series are discussed in section 5.8. For ungauged locations QMED
is estimated using another, usually nearby, catchment with similar catchment characteristics,
a process known as donor transfer, or from catchment descriptors. Other less common
approaches include the use of channel dimension data or continuous simulation.
Where only short gauged records are available these may be used to support estimates of
QMED.
The method for estimating the growth curve depends on the length of the gauged record for
which data is available and the required return period, there are two methods a single site
analysis based on local gauged data, or a pooling group analysis which estimates QMED
and the growth curve from a group of gauging stations on other similar catchments. For
gauged catchments with a sufficient length of record a comparison of the single site and
pooling group analysis should be made. For ungauged catchments only the pooling group
method will be appropriate.
Where level only gauges are available, or where no high flow rating is available, it may be
possible to extract a rating from a hydraulic model provided that the gauge is surveyed and
modelled in sufficient detail. In this instance SEPA should be contacted to discuss survey
requirements, gauge history and available information for calibration.
A new conceptual rainfall-runoff model called the Revitalised Flood Hydrograph Model
version 2 (ReFH2) has been developed which supersedes the FSR/FEH Rainfall-Runoff
Method. Recent improvements to the method have now rendered it applicable for design
flow estimation within Scotland however the methodology has been calibrated to catchments
without significant storage (i.e. lochs and reservoirs). The methodology is still being
assessed and, like any other flood estimation methodology, it should only be used in
combination with others for comparison. Note that ReFH version 1 is not considered
suitable for use in Scotland due to the limited number of Scottish gauges and lack of Scottish
specific calibration.
As discussed in Section 5.8.2 a new version of the FEH DDF model FEH 2013 has recently
been published and should generally be used over the previous version, FEH 1999 due to
the improvements in data and techniques. The differences between FEH 2013 and FEH
1999 may also have implications for previous design flood estimates carried out using
rainfall-runoff models.
Both the FEH and ReFH2 rainfall models are lumped hydrological models (i.e. they use a
single unit to represent a catchment and model parameter values are averaged across the
catchment). More complicated distributed hydrological models allow factors such as soil
type or rainfall to vary across a catchment. Distributed hydrological models are not
commonly used for flood estimation in Scotland and would not usually be accepted by
SEPA for design flow estimates; however they are potentially useful for some NFM
studies. This is discussed in chapter 12.
For ungauged catchments the hydrograph shape should be generated using a rainfall-runoff
model, as in section 6.3.2.2
Where there is gauged data available close to the model boundary a hydrograph shape can
either be derived by either:
• standardising hydrographs by their peaks and averaging (Archer, Foster, Faulkner, &
Mawsdley, 2000),
• using a hydrograph from a large observed flood event or
• using a rainfall-runoff model
In order to identify a representative large observed event or suitable events for the averaging
approach, 15 minute times series data will be required as discussed in Section 5.8.1.
In all cases the hydrograph is forced to fit the design flow estimate, either by adjusting the
rainfall runoff model parameters or by scaling the derived hydrograph shape.
The method used to derive the hydrograph shape and why it was chosen should be
discussed in the hydrology report.
It is not physically realistic for different duration critical storms to occur at different points in
the same catchment at the same time. Where a catchment has been split into sub-
catchments the same design storm is applied to each sub-catchment, and the model is run
for a range of storm durations to find the critical storm duration which produces the worst
case flow or level at the site of interest.
For large catchments the AEP of a flood event may vary throughout the catchment. This
means it is not always possible to apply a consistent design storm across the catchment so
that the flow in a hydraulic model matches the design flow estimates at the reconciliation
points. In this case it is necessary to adjust the boundary conditions so that the flow in the
model matches the design flow at the reconciliation points. This process is termed flow
reconciliation, and should be undertaken after model calibration, chapter 8. There is no
single method to achieve this but typical approaches include:
Adjusting the storm duration: Different critical storm durations may be identified for
different parts of the catchment. Generally the critical storm duration will increase
downstream; any decreases in critical storm duration downstream should be justified in the
model report (e.g. confluence with major tributary with steeper/more urbanised catchment).
Scaling tributary inflows: Different scaling factors may be required for different
reconciliation points and for different storm durations. Typically the same scaling factor is
applied to all tributary inflows for the same model run for simplicity. In most cases scaling
factors will reduce the flood peak from the design flow estimates on the tributaries, as
downstream of a confluence the flood peak is likely to result from a combination of more
frequent events on the tributaries. Although in some instances design flows may decrease
downstream due to attenuation, and the AEP of a particular observed flood event may
increase downstream, it is not possible to require a lower probability flood event to occur on
a tributary in order to generate a higher probability flood event downstream.
Adjusting the phasing of tributary inflows: The start time of tributary inflows may be
adjusted to make them more or less coincident. This would typically be used where a
combination of gauged data and rainfall-runoff boundaries have been used for model
inflows.
It may be necessary to run multiple model scenarios for the same AEP event in order to
match the design flow at different reconciliation points. The confidence in hydrological flow
estimates and the ability of the hydraulic model to reproduce any attenuation in the design
flows should be considered in determining to what extent the flow in the hydraulic model
should be constrained to match the design flow. The approach used for reconciliation
should be described and justified in the modelling report.
6.4 Pluvial
Key points for Contractors
Boundary conditions for pluvial models need to consider how much rainfall falls on the
surface and how much of this rainfall is lost due to infiltration into the ground or is carried
away by the surface water drainage network.
Standard rainfall profile shapes are given in the FEH Point to Note:
and used to generate rainfall profiles from the DDF
model. The FEH provides two standard profiles; winter A summer storm profile
and summer (Figure 6-2), which do not vary with presents a shorter duration but
duration or location. The summer profile has a more higher intensity storm and is
pronounced peak, representative of the convective generally recommended for
storms more common in summer, and is generally application to urban
recommended for application to urban catchments catchments.
where a shorter period of high intensity rainfall is
generally more critical. The summer storm profile was used in SEPA’s pluvial hazard maps.
The choice of rainfall profile should be justified in the modelling report.
6.4.2 Losses
Two types of losses need to be
considered in surface water modelling; Point to Note:
infiltration into the ground and loss of
water into the urban drainage system. SEPA’s pluvial hazard maps use a
conservative approach in its assumptions.
Infiltration rates should vary between
urban and rural areas to account for the Runoff rates:
effect of extensive impermeable surfaces • 100% of the urban area is
in built-up regions. The FEH handbook impermeable
advocates the use of 70% runoff for • Urban runoff rate of 70% and rural of
impervious areas (Institute of Hydrology, 55%
1999). Within an urban area there will be
a component of the catchment which acts Drainage loss allowance:
as natural and has lower run off rate. The • National models: 12mm/h
percentage of the urban area which is • Regional models: average 20% AEP
impermeable varies according to the
(1 in 5) rainfall loss
An alternative approach is to assume a given service level for the drainage system. SEPA’s
national pluvial mapping assumed a 12 mm/hr loss to the drainage system whilst the
regional pluvial mapping assumed an average 1 in 5 year rainfall event loss (Figure 6-3).
Where a level of service is assumed, the loss applied may be constant or may vary with
time, Figure 6-4.
The approach taken to determine losses to the drainage system should be described and
justified in the modelling report. In general no loss to the drainage system should be
considered for rural catchments.
10
Urban areas in SEPA’s regional pluvial modelling are defined using the Land Cover Map 2007 (LCM2007) and
urban areas in the national pluvial maps are defined using the Scottish Government Urban/Rural Classification
6.5 Coastal
Coastal flooding is due to a combination of astronomical tides, surge and waves. The
combination of astronomical tide and surge is referred to as the still water level. Still water
levels and waves are often treated separately however, waves may increase still water
levels at the coast due to a process called wave setup. In turn still water levels influence
where waves break and hence the total amount of overtopping. The key processes leading
to coastal flooding for a particular study location should be identified through the conceptual
model of the study area; see section 3.3.
Section 5.8.5 describes available sea level data and section 5.8.6 describes available wave
data. Information on extreme still water levels is not generally available within lochs and
estuaries and wave data is usually only available offshore. This means that further
modelling is often required to bring boundaries inland and, in complicated areas, generating
boundary conditions for coastal inundation models may require:
• A hydrodynamic model to look at how surge and tide change as they move up sea
lochs and estuaries.
• A wave transformation model which looks at how waves change as they move inland.
• A wave overtopping model to look at the rate of water overtopping flood defences.
The SEPA Coastal Hazard Mapping Study mapped flooding due to extreme still water levels
only for the entire of the Scottish coast. This strategic level study was based on level
projection of these water levels only and did not consider the duration for which the levels
were high. It is expected that any coastal flood study undertaken by a Responsible Authority
will be more detailed; probably with time-varying still water boundaries and wave boundary
conditions. More information on coastal modelling techniques and their applicability to
Scotland is given in (Stokes, Masselink, & Conley, 2016).
• For the open coast use boundary conditions from the Environment Agency Project
Coastal Flood Boundary Conditions (CFB) for UK mainland and islands (McMillan,
et al., 2011).
• For sea lochs and estuaries review the method used to extend to the CFB dataset
inland for the SEPA Coastal Hazard Mapping Project (Royal Haskoning DHV and
JBA, 2013) to determine if it is appropriate for a more detailed study.
• The base year for the study levels should be documented in the report.
• Extreme water levels, surge and tide shapes on the open coast;
• The change in extreme water levels & surge and tide shapes within estuaries and
sea lochs;
The conceptual model of the study area should identify which of these factors are important,
and the modelling report should contain a discussion of the reasoning behind including or
excluding these factors from the study.
For locations on the open coast boundary conditions should be taken from the Environment
Agency Project Coastal Flood Boundary Conditions (CFB) for UK mainland and islands
(McMillan, et al., 2011). This gives extreme still water levels for 16 annual exceedance
probabilities at 2 km spacing around the open coast of Scotland, England and Wales and
provides guidance on developing standard storm tide curves to be used with extreme sea
levels at each location. These storm tide curves may be applied directly as a level boundary
for inland flood models for locations on the open coast if wind and wave set up are not
considered important. The report should state the CFB point used, which surge shape was
used to generate the boundary and how the base astronomical tide was derived.
The CFB dataset extends into the outer parts of some estuaries and sea lochs but not the
inner parts of estuaries because local bathymetric effects can significantly affect tide levels
within estuaries. The SEPA Coastal Hazard Mapping Project (Royal Haskoning DHV and
JBA, 2013) extended the analysis from the CFB study to sea lochs and estuaries within
Scotland using a combination of observed data not included in the CFB study, local
modelling studies and relationships between open coast and estuarine locations from
similarly shaped and aligned estuaries. For local flood studies in areas covered by the
SEPA Coastal Hazard Mapping Project a review should be undertaken of the method used
to extend the CFB dataset to determine both if the level of confidence in the levels is
appropriate for a more detailed study and if storm tide curves can be derived. This review
should be documented in the modelling report. The location of points taken directly from the
CFB study and the SEPA study are shown in Figure 6-6.
If the SEPA Coastal Hazard Mapping Project is not suitable for providing boundaries a
hydrodynamic model of the estuary or loch may be required. This will usually be 2D, but in
some instances a 1D model may be sufficient for narrow estuaries and it may also be
possible to include inland flooding within the same model. Detailed bathymetric data is
required for constructing a coastal hydrodynamic model and possible sources of data for this
are described in Section 5.5.6. Where possible the model should be calibrated against
observed tide levels or admiralty tide tables and this is discussed in Section 8.2.2. The
relevant CFB storm tide curve should be used as a boundary for the hydrodynamic model.
Construction and calibration of any coastal hydrodynamic model used to generate boundary
conditions should be documented in the modelling report.
The CFB boundaries and the SEPA Coastal Hazard Mapping levels include the effect of
storm surge but do not take into account wave setup which may increase sea levels on a
downwind coast. In some locations wind set up is also not accounted for. Where this effect
has been identified as important in the conceptual model it may be necessary to carry out a
joint probability analysis for surge and wave and wind setup, and to add wave and/or wind
boundary conditions to any hydrodynamic model used to bring surge inland. In this case
additional modelling may also be required for the open coast. Any analysis used to
determine the effect of wind and wave setup should be documented in the modelling report.
Sea levels in the CFB and SEPA Coastal Hazard Mapping study are referenced to 2008.
The base year for the study and the adjustment made for climate change since 2008 should
be documented in the report.
The sea state is the combination of wind waves and swell. Both components need to be
considered in wave overtopping studies..
A description of available wave data is given in section 5.8.6. There are few long time series
observations available so, in most cases, the best available data are hindcasts from wave
forecast models. Forecasts points from these models are some distance offshore, and need
to be transformed inshore, usually through use of a numerical wave transformation model.
Extreme still water levels and extreme wave conditions may occur independently however,
the worst case situation for flooding is likely to be when large waves occur at high tide or
during a high tide and surge, so a joint probability analysis of extreme waves and
extreme still water levels is required. Wave conditions inshore cannot be used as a direct
input into a hydraulic model, and run up and overtopping models are needed to determine
the rate of flow over the defences, which can then be used as an input to an overtopping
model. Developing wave boundary conditions for input into a flood inundation model
therefore requires:
• Offshore design wave conditions
• Joint probability analysis of still water levels and extreme wave conditions
• Wave transformation modelling
• Overtopping Modelling
Wave overtopping studies can be complex. The Scottish Borders Council Eyemouth
Wave Overtopping and Flood Study (Royal HaskoningDHV, 2013) used three models to
generate inflow hydrographs for a flood inundation model from the offshore results from
the Met Office wave model.
Waves were transformed inshore using a regional Firth of Forth wave model, and then
further inshore using a local Eyemouth wave model, both of which were developed for
SEPA’s Firths of Forth and Tay flood warning scheme. The results from the Eyemouth
model were used as boundary conditions for an overtopping model of the Eyemouth sea
wall.
Typically the Met Office wave model hindcasts are used for the UK. As with all models, wave
model hindcasts are not perfect and may systematically over or under estimate the extreme
wave conditions of interest for flood studies. Where possible the performance of any model
6.5.2.2 Joint probability of extreme still water levels and extreme wave conditions
Extreme still water levels are discussed in section 6.5.1. A joint probability analysis of
extreme still water level and wave height should be undertaken. Different approaches for
joint probability analysis are given in DEFRA guidance FD2308 (Hawkes & Svensonn, 2005)
(Hawkes, 2005), including a desk study approach which is simple to apply and will be
sufficient in many cases. However since publication of the DEFRA guidance new
techniques have been developed which may be more appropriate for complex areas or
where full uncertainty analysis is required (Gouldby, Méndez, Guanche, Rueda, & Mínguez,
2014).
Results from the extreme value analysis and joint probability analysis should be tabulated in
the report for the different wave direction sectors considered. Again sufficient details of the
analysis should be provided to allow the results to be reproduced. To obtain the worst case
flood extents it will generally be necessary to consider a number of different wave and SWL
scenarios, each with the same joint probability of occurrence.
Wave and water level boundary conditions used for the wave transformation modelling come
from the joint probability analysis discussed in Section 6.5.2.2. Wind boundary conditions
may also be required and are usually developed using a simple regression analysis between
wind speed and significant wave height from the wave model hindcast.
Development of a wave transformation model requires good quality bathymetric survey and
shore survey (see section 5.5.6). For complex regions multiple wave transformation models
may be required, with a coarse resolution regional model covering a larger area used to
provide boundary conditions for higher resolution nested models of inshore areas, Figure
6-7. In this case joint studies may be cost effective. SEPA has several wave models
developed for flood warning schemes which may be made available for Responsible
Authority studies.
Where possible the wave transformation model should be calibrated using observed data,
and the set up and calibration of any wave transformation model used should be described
in the modelling report.
Several different overtopping models are available (e.g. Pullen, et al., (2007), Hedges &
Reis, (1998)) and the most suitable model may change according to the defence and beach
type. (Stokes, Masselink, & Conley, 2016) provide a review of different approaches which
may be relevant to different types of coastline around Scotland. The modelling report should
justify the overtopping model used with reference to the available literature.
6.7 Groundwater
Currently there are few confirmed instances of groundwater flooding in Scotland and a
recent scoping project suggests that it is not as widespread a problem in comparison to
other parts of the UK. However, groundwater flooding is possibly underrepresented in
Scotland because of the difficulty of differentiating it from other types of flooding.
6.8 Uncertainty
All flood frequency estimates are inherently uncertain due to the length of record compared
to typical design probabilities of interest, the range of different of analysis methods available
and the incomplete data coverage. This can be one of the largest sources of uncertainty in a
modelling study and understanding this can help in making decisions such as the level of
freeboard to apply to a defence based on modelled water levels.
Where the analysis method permits, error bounds should be given on estimates of design
flows or levels; and design flows or levels should not be reported with a higher level of
precision than is justified by the data or analysis. The impact of the effect of uncertainty in
flood frequency estimates should be addressed through sensitivity testing. This is discussed
in chapter 8.
7.1 Introduction
This chapter provides guidance for Responsible Authorities wishing to critically review
models received from contractors. It describes:
• The options which can be considered when schematising different features within a
hydraulic model and how these may affect the results.
• Common errors and problems with hydraulic models.
• Expected good practice in model building.
• Comments should be added to the model giving the source of any data, the
reasons for any structure representation, and the location of structures and cross
sections.
• Sensitivity testing should be carried out for roughness, structure blockage, and
structure representation.
• The modelling report should explain the choice of flood plain representation, the
channel and floodplain roughness values
In a 1D model the channel is represented as a series of cross sections. A single flow and
level value is calculated for each of these sections and velocity is averaged over the depth
and cross section width. As there is only a single level at each cross section, all points
below the calculated water level are wet simultaneously, even if there is no connection
between one area of the cross section and another, Figure 7-2. This also means that 1D
models cannot be used directly to give flow velocity in the channel and on the floodplain, or
variations in level across a section for instance, due to superelevation at a bend. Where flow
is not predominately 1D, typically at structures, different equations have to be used to
calculate energy losses through the structure.
Key factors to consider in schematising a 1D model are the representation of the channel
between hydraulic structures, the representation of any hydraulic structures and the
floodplain representation.
For a cross section spacing ∆x, the following rules of thumb apply
1. ∆𝑥 ≈ 𝑘𝑘, where B is the top width of the channel, and k is a constant with a
recommended range from 10-20.
𝐷
2. ∆𝑥 < 0.2 where D is the bank full depth and s is the slope.
𝑠
𝑐𝑐
3. ∆𝑥 < where c is the speed of the flood wave, T is the period of the flood
𝑁𝑔𝑔
wave and Ngp is a constant between 30-50.
Figure 7-1: Rules of thumb for cross section spacing in hydraulic models (from Castellarin, Di
Baldassarre, Bates, & Brath, 2009).
If cross sections are too close together, this can also cause problems with numerical
stability and lead to long model run times as the model has to be run with a small time step.
This may mean that a modeller has to exclude some surveyed sections if the survey is very
closely spaced.
Braided channels or split flow paths can be modelled either as a single set of cross sections
covering both flow paths, as in Figure 7-2, or separate cross sections can be used for each
branch of the channel with some representation of the flow pathway between the cross
sections. Where a single section is used the 1D methodology means the calculated water
level in both channels is the same and the flow split between the channels is not calculated.
The approach taken will depend on the level of detail required and the local hydraulics. For
strategic or catchment level models use of a single section may be appropriate especially if
there is significant flow between the channels during all flood events of interest. For local or
design models, or where there are receptors between the flow paths, use of separate
sections may be more appropriate.
Comments should be added to the model giving the source of the cross section data
(including surveyed date) and any modifications made during the model build. This can
prevent or help identify potential problems if the model is reused in future, for instance, steps
in the bed due to a different survey datum or loss of channel capacity due to siltation
between surveys. Where it is not clear from looking at the model if a section is from survey
or has been interpolated, this should also be recorded. In addition, useful information such
as nearby street names or location identifiers should be included as comments where
available.
For new models in software which requires cross section names to be entered (e.g.
FloodModeller), names should be logical and based on the chainage from a downstream
confluence with a larger watercourse or the tidal limit. This can help in identifying errors with
22
21
20
Elevation (m AD)
19
18
17
16
15
14
13
12
11
0 10 20 30 40 50 60 70 80
x (m)
7.2.1.2 Roughness
Hydrodynamic models include estimates of the surface roughness for the channel and the
floodplain areas (right and left 11) at every cross section in the model (1D model) and for
every cell grid in the model (2D). The most common representation of roughness is in the
form of Manning’s coefficient (n). Factors that affect roughness include: the nature of the
channel bed material, channel bed forms, channel structure, any obstructions (e.g. debris)
and the time of the year (i.e. vegetation cover). For free open flowing rivers roughness
decreases with increased stage and flow but if the banks of the river are rougher than the
channel bottom then the composite ‘n’ value will increase with increased stage.
11
Right and left are defined as viewed downstream
Inclusion of all flow paths There may be multiple flow paths around a structure, particularly
during flood events. For instance there may be flow over a bridge deck or out of bank
around the side of a weir. All relevant flow paths should be represented. Where a particular
flow path has been excluded from the representation this should also be commented upon
(e.g. if the flow pathway over the bridge deck is not included as it is above the level of the
largest event modelled).
Level of detail The level of detail will determine which hydraulic structures are included in
the modelling. For a strategic or catchment level model it may be appropriate to omit some
structures such as small footbridges, however these may need to be included for a detailed
or design model. Further guidance on this is given in Table 5-2.
Angle to flow Where structures are skewed across the channel this should be accounted for
in the structure representation. If the modelling software cannot effectively account for the
decrease in effective length due to drowning then different models may be required for high
and low flows to ensure that both the drowned and the undrowned states are appropriately
captured.
Blockages Where structures have been identified as being at risk of blocking the effect of
blockages should be investigated through sensitivity testing; further details on this are given
in section 8.4.
Comments should be added to the model giving the location of the structure to aid
identification, the reasons for the structure representation used if several options are
available, the source of the structure data and how any parameter values were chosen or
calculated.
7.2.1.3.1 Bridges
Flow in the vicinity of bridges may be a combination of free surface flow where flow is
below the bridge deck, pressurised or surcharged flow where the flow is in contact with
the deck and weir flow over the bridge deck. The bridge schematisation should be sufficient
to represent all modes of flow which occur in reality. This may involve the use of multiple
model units to represent the bridge (e.g. a bridge unit and a weir or spill unit to represent
flow over the bridge). Most forms of hydraulic modelling software have several available
bridge representations for each mode of flow – a review of representations available in
different software packages is given in Samuels (2004). Typically there is no suitable
calibration data available and the choice of representation used is largely based on user
experience. If necessary, sensitivity tests to different bridge representations can be carried
out.
For detailed or local models it may be necessary to include representations of manholes and
surface water sewer connections although in most cases these can be omitted from
catchment level models.
Culverts can be particularly prone to blockage and for detailed or local studies sensitivity
testing to sedimentation of the culvert barrel and due to inlet blockage should be carried out
as set out in the Culvert Design Guide (Balkham, et al., 2010).
Short culverts, where the effect of friction along the length of the culvert can be neglected,
can also be modelled as an orifice. This can increase model stability in some cases.
Where the cross section survey does not cover the full width of the floodplain the floodplain
representation is typically based on a DTM (section 5.5.5). Difficulties may arise in all
methods if there is a discontinuity between the cross section survey and the DTM. Where
this occurs it is unlikely that it can be resolved without collection of further out of bank
survey.
embankment is overtopped.
Depth area relationships are Most suitable for flat areas with negligible out
defined for areas of the of bank flow. Only one elevation value is
floodplain. Flow between these calculated for the storage area so, if the areas
areas and the channel is are large or steeply sloped, other areas of the
controlled by the weir equation storage area may become wet before the
(Figure 7-4). areas next to the channel.
A separate 1D channel is added There may be stability issues associated with
channels
Parallel
parallel to the main river. Flow the parallel channel drying out, particularly at
between the main channel and the start of the modelled event.
the parallel channel is controlled
by the weir equation.
Table 7-1: Methods for floodplain representation in 1D models.
98 0.06
96
94
Elevation (m AD)
Mannings n
92
90
88
86
84 0.04
200 300 400 500 600 700 800 900 1,000 1,100
x (m)
Data entry errors 1D models can require significant amounts of manual data entry
particularly at structures as there is no single survey or input file format which can be used to
read structure data into all hydraulic modelling software 12. This is a potential source of
model error and a detailed check on structure data entry against the original survey data
should be carried out.
Glass walling Where 1D models exceed the maximum level in a cross section the modelling
software will automatically add a vertical wall at the end of the section to allow water to rise
above the section level. This leads to increased water levels within the section as the water
cannot spread over the floodplain. Where this occurs the floodplain representation should
be extended, unless there is a reason for allowing the model to glass wall (e.g. to represent
a very high defence).
Embanked sections If 1D model cross sections contain embankments the area behind the
embankment will become wet in the model before the embankment is overtopped. This may
be acceptable in some circumstances, for instance if the embankments provide a very low
standard of protection or if there is a small area behind the embankment in a catchment or
strategic level model. In HECRAS, for example, levees can be used to prevent areas behind
the levee becoming wet before it is overtopped. Other software may require the cross
sections to be cut back to the top of the embankment and a different representation for the
area behind the embankment.
12
The EACSD file format aims to address this issue, but uptake amongst software providers has been low.
7.3 2D models
Key Points for Responsible Authorities
• 2D models can give depth-averaged velocity on the floodplain but may not
represent channel flow well if the resolution is insufficient, particularly around
hydraulic structures.
• The model resolution affects the computational effort required to run a model.
Balance the need for increased detail due to higher resolution and understanding
uncertainty in the modelling through more sensitivity tests and scenarios.
• Future use of the model should be considered in choosing the software as this
affects whether the model resolution can vary through a model domain, whether it
can be linked with 1d model at a later date and how structures can be represented
within the model.
• There are several common issues with 2D models which need to be checked for
during a model review.
• Avoid representing buildings using mesh voids or full height buildings as these
representations cause problems when undertaking depth damage calculations
using the model results.
• The approach taken to represent any hydraulic structures or linear features in the
DTM should be described in the modelling report, together with the data used.
• The roughness values assigned to different land uses should be described in the
modelling report, together with the data used to determine the land use.
2D models calculate water level and depth-averaged velocity over a regular or an irregular
2D grid. Schematisation of 2D models is similar for coastal, fluvial and pluvial flooding, with
the main difference being in the type and location of boundary conditions applied.
Key factors to consider in schematising any 2D model are the grid type and resolution, the
representation of features within the DTM and the roughness. There are also several
considerations regarding schematisation which have to be made in choosing 2D modelling
software before deciding on the schematisation within a particular software package.
Grid Type – Models may have regular or irregular grids. Irregular grids allow resolutions to
vary across the model domain so that higher resolutions can be used only where required,
such as for urban areas, steep slopes and along channels, however regular grids may be
easier to set up.
Computational efficiency and software architecture – Different model codes use different
software architecture, which can affect model run times and the number of concurrent
simulations which can be run. Shorter model run times are beneficial if large numbers of
scenarios or multiple calibration runs are required.
Linkage with 1D models – If the model can be linked with a 1D model at a later date. This
is most likely to be a consideration for fluvial models.
DTM manipulation – The ease with which the DTM can be modified to produce a good
representation of the ground surface for modelling (e.g. to include buildings or walls can vary
significantly between software packages).
Adequate representation of detailed urban flow pathways (e.g. flows between buildings or
even obstructions to flow due to kerb heights) requires a finer spatial resolution. SEPA’s
fluvial hazard maps use a resolution of 5 m in urban areas and SEPA’s pluvial maps use a
resolution of 2 m or 5 m in urban areas.
The computational effort required to run a model is largely dependent on the resolution and
halving the grid cell size typically results in an increase of run times by a factor of 8. If
computing resources are limited it may be necessary to balance the desire for finer grid
resolution with the need to run multiple scenarios or sensitivity tests.
(a) (b)
Figure 7-5: Examples of locally increased resolution; (a) an irregular grid with higher
resolution along a watercourse and (b) an example of a regular nested grid, in this case a
higher resolution grid covers an urban area.
The available DTM also affects the model resolution, as the resolution cannot usefully be
increased beyond the DTM resolution. However, if other considerations identify that a
higher resolution model is required new data should be collected to increase the DTM
resolution.
7.3.2 DTM
The basis of the DTM should be stated in any modelling reports, as well as the date it was
collected. An assessment of accuracy should also be provided.
Voids Buildings are left as void polygons in the mesh where no values are calculated. This
is a conservative approach as storage within the buildings is not accounted for but it may
overestimate the obstruction to flow caused by a building. As the model does not calculate
within buildings, the depth outputs required for damage calculations are not available as a
model output. Instead, depths within buildings have to be interpolated from the water level
adjacent to the building and the threshold level which can be problematic if there are
differences in water level around the building. Due to the difficulties in interpolation to get
values at building centres, this method is not recommended where depth damage
calculations are required.
Full Height Buildings Buildings are represented as blocks at their actual height. This has
similar limitations to voids and the method is not recommended where depth damage
calculations are required.
High Roughness Buildings are represented by increasing the roughness over the building
footprint. This allows buildings to store water and gives depths within buildings. There is
limited guidance available on the appropriate roughness value to use however; values
Stubby Buildings Buildings are represented by raising the DTM within the building footprint
to the threshold level. Typically thresholds are assumed to be 0.3 m above the bare earth
DTM. The roughness may also be increased over the building footprint. The stubby
buildings approach without an increase in roughness was used for SEPA’s regional
pluvial hazard maps.
Porous Walls Buildings are represented as partially porous walls, with the porosity and
height of the walls specified by the modeller.
In most cases OS Mastermap data is used to identify building footprints however, other
datasets such as detailed ground-based survey may also be used. The method used to
represent buildings in the DTM should be stated in the modelling report together with the
data used to identify building footprints.
Consideration should be given to future use of the model when choosing the building
representation as both the void and full height building methods do not allow depth-damage
calculations to be carried out. In particular depth-damage calculations are required to inform
Flood Risk Management Strategies so models using these building representations will not
be used to inform future Strategies.
Bridges, culverts, underpasses and similar features are likely to appear as false blockages,
or complete obstructions to flow in the DTM. This can result in over estimation of flooding by
the model upstream of the structure but underestimation downstream as not enough flow is
passed forward. Some representation of these structures in the DTM is required. Depending
on the software, different options are available; a review of structure representation in
TUFLOW is given in Syme (2001).
Lowering DTM through the structure This allows flow to pass but does not represent a
constriction to flow due to the soffit of the structure. Depending on the scale of the structure
and grid resolution some changes in velocity due to constriction/expansion at the entrance
and exit may be captured, but constriction due to the soffit is not included. This method can
be implemented quickly with limited structure information and is appropriate for strategic
scale modelling.
It may also be necessary to modify the DTM to ensure there are flow paths between
buildings or other closely spaced structures and to ensure that forested or heavily vegetated
areas have not been picked up as obstructions in the DTM.
The approach taken to represent any hydraulic structures or linear features in the DTM
should be described in the modelling report together with the data used.
7.3.2.3 Roughness
In 2D models roughness can vary across the model grid. Typically the model domain is split
into different land use classes using information from land cover layers such as OS
Mastermap and a roughness value assigned to each class. The roughness for some land
use types may depend on resolution for example; if features such as buildings and walls are
not resolved in the DTM a higher roughness may be set for general urban areas to account
for this. The roughness values assigned to different land uses should be described in the
modelling report together with the data used to determine the land use.
False Blockages Blockages in the DTM which cause an obstruction to flow where in reality
there is a flow path.
Leaking Embankments Embankments or walls which are not picked up properly in the
DTM and allow flow through where, in reality, there is no flow path.
Glass walling Where 2D flows reach the edge of a model domain and no boundary
condition has been defined to allow the water to flow out, the model can insert a vertical wall.
This leads to ponding and increased water levels at the edge of the model domain.
Mass Balance Errors The model may gain or lose mass, particularly if there is frequent
wetting and drying, or if the inflow at each grid cell is small. The mass balance files should
be checked to ensure the mass balance is within acceptable limits, usually within ±1%
cumulative error.
• 1D-2D models can give a depth averaged velocity on the flood plain and are able
to represent channel flow well, but they can take significant time and resources to
set up.
• There are several common issues with 1D-2D models which need to be checked
for during a model review. In particular models can be prone to mass balance
errors and models should not be accepted without evidence of mass balance
checks.
Coupled 1D-2D models use a 1D model component to represent river channels and/or the
surface water drainage network and a 2D model component to represent the floodplain.
Flow is dynamically passed between the 1D and the 2D components. This approach is used
where there are complex floodplain flow paths which cannot be represented in 1D and where
increasing the grid resolution to resolve the channel in a purely 2D model would be
impractical or where there are hydraulic structures which can be best represented in a 1D
model. Coupled 1D-2D models are most commonly used for fluvial flood modelling or for
detailed surface water drainage network models; however they may also be used within
estuaries. Despite the advantages of 1D-2D models of representing both the channel and
floodplain, they are not recommended if a purely 1D or 2D model will deliver the
desired objective as they are complex to set up and prone to numerical instability which
can take significant time and resources to solve.
The guidance for 1D models in section 7.2 and 2D models in section 7.3 applies to the 1D
and 2D components of coupled models. The other considerations are the features
represented in the 1D and 2D components of the model and the type of link.
It is also possible to have a 1-way link using the output from a 1D model as the inflow into a
2D model. This approach is only suitable where flow is away from the system represented in
1D and is not as prone to numerical instability.
Elevation of links If the wrong link elevation is set for lateral links between 1D and 2D
models this may lead to flow across the link before the bank is overtopped.
Numerical stability can be a problem for 1D-2D models particularly if there is frequent
exchange of water across the link. This can show up as oscillations in velocity and water
level in both the 1D and 2D components. The model log file should be examined for any
reports or numerical instability and the results animated and examined for nonphysical flow
patterns.
A downstream boundary condition is required at the downstream end of any river reaches.
These conditions are generally specified as stage hydrograph, flow hydrograph, single
valued rating curve, normal depth or critical depth boundary. If the flow reaches the domain
boundary other than at the defined downstream boundary the model extent should be
examined.
Additional inflows can be added to models between upstream and downstream boundaries
to account for any increase in flow between the upstream and downstream boundary.
Lateral inflows trickle flow in gradually along a reach and are typically used to account for
the increase in catchment area along a reach while point inflows add flow at a specific point
and are typically used to represent tributary inflows.
Upstream and downstream boundary conditions should be located a sufficient distance from
the area of interest so that any errors in the boundary will not significantly affect predicted
water levels at the study area.
• A rule of thumb L=0.7D/S (where D= bank full depth and S= river slope) can be used
when considering the location of downstream boundary from the study site.
• If possible, the downstream boundary should be located where relationship between
level and flow is well defined e.g. weir
• If the downstream boundary is tidal; the downstream boundary should be located
where a tidal curve can be defined.
If the initial conditions are incorrect this may lead to instability at the start of the model run or
storage areas having the wrong volume of water in them at the start of a simulation. The
model initial conditions should be checked during review of the model. Particular care
should be taken in situations where there are significant amounts of storage or artificial
drainage.
8.1 Introduction
Model calibration and validation is important for determining the degree of confidence which
can be placed on model results. Sensitivity analysis is important for understanding the level
of uncertainty in the modelling. These affect the practical use the model can be put to and
the confidence in decisions which are based on the modelling. This chapter describes:
8.2 Calibration
Key Points for Responsible Authorities
• Specify the number of calibration events and target criteria for model calibration in
the SoR. A minimum of 3 calibration events and one validation event is
recommended.
• Additional sensitivity testing and uncertainty analysis should be carried out if
limited calibration data is available. In some cases installation of additional
gauging to enable a higher level calibration may be appropriate.
• Review model calibration reports critically to ensure common issues with model
calibration are avoided.
Calibration is the process of adjusting model parameters, such as the surface roughness,
within physically defensible ranges until the resulting predictions give the best possible fit to
a selected observed event. A model is said to be validated if it is able to provide accurate
predictions against other observed events (i.e. non-calibration events) within acceptable
limits. Model calibration and validation provides an understanding of the appropriateness of
the model considering observed flow/stage data. The main objective of model calibration and
validation is to provide a demonstration of the quality of model predictions. If calibration is
not carried out, confidence in the model application will be significantly reduced.
The level of calibration which would be expected for different levels of study is given in Table
8-1.
Table 8-1: Suggested level of calibration for gauged and ungauged catchments for different
levels of study. Target calibration levels for gauged study areas discussed for different
sources of flooding in section 8.2.1, 8.2.2 and 8.2.3 .
The main information required is recorded flows and/or water levels and flood extent from
observed events; however a range of different types of data may be used in calibration and
reality checks as listed below;
In some areas calibration data may only be available for a short period of time, with no
significant events. Calibration and validation of models under these circumstances can still
Target calibration acceptance criteria should be defined in the SoR or early in the project.
Typical requirements are set out in the template SoR which can be made available on
request, appendix A.
The calibration process should be fully documented in a report and should include calibration
event dates and measurements and locations of historic floods. Changes to parameters and
the rationale for revising must be clearly documented.
8.2.1 Fluvial
River models should be calibrated for flow and levels at gauging stations. It is strongly
recommended that, where possible, the study extent covers at least one and preferably two
or more gauges to assist in calibration.
The hydraulic parameters which are usually varied during model calibration are the surface
roughness (e.g. Manning’s n) and structure coefficients. Model boundaries, including
parameters in hydrological models, may also be varied, for instance the parameters in the
rainfall run off model. Where possible a combined approach to hydraulic-hydrological model
calibration should be undertaken.
The calibration events should cover both in-bank and out-of-bank scenarios to ensure that
both the channel and the floodplain are modelled correctly. Although inclusion of larger
events is important, not all the events need not have caused extensive flooding as it is also
valid to show the model correctly predicts water not reaching particular locations. Utilising
recent events may minimise the impact of recent changes in hydraulic structures or
catchment characteristics.
• 15 minute flow and level time series for any gauges within the study reach, including
tributaries. Particular care should be taken in extrapolating rating curves.
• 15 minute rain gauge data for any gauges within or surrounding the catchment.
• Tide gauge data if the downstream boundary of the model is tidal.
If the ReFHv2 rainfall run off model is used, the following are also required:
• MORECS/MOSES evapotranspiration and soil moisture data for 2 years prior to the
event.
• Daily rainfall for any gauges within or surrounding the catchment.
Selkirk has a history of flooding, with notable recent events in 1977, 2003, 2004, 2005,
and 2009. Following these events Scottish Borders Council categorised Selkirk as a high
priority for investment in flood protection measures and between 2002 and 2011 a phased
programme of modelling and investigation was undertaken in order to inform the flood
protection measures.
In order to have confidence in the hydraulic model predictions of flood levels, the model
was calibrated using a combination of gauged data and historic flooding information.
Four events were identified where there was suitable recorded data, observed flood levels
and/or anecdotal evidence to be used as calibration events; October 1977, January 2005,
October 2005 and November 2009 (Halcrow, 2011).
Flow records from the 2 gauges within the study reach were used to derive model inflows,
and the hydraulic model was calibrated by adjusting individual model parameters in order
to obtain a good correlation between predicted and observed water levels. The final
phase of the study reported a reasonable fit to observed data for all four events, with
discrepancies of less than 0.2 m recorded for the majority of locations across all
calibration events. In instances where larger discrepancies were noted, further
investigation was undertaken in the form of sensitivity testing. This helped to refine the
conceptual model of the catchment by identifying factors which could increase flood levels
which had not previously been considered. Once such case was at the Riverside
footbridge in the November 2009 event, where sensitivity testing identified that a 40%
blockage of a bridge was required in order to reproduce observed water levels, and whilst
this was initially considered high, this was supported by a review of the observed data for
this event.
The calibration was revisited at different phases of the work following updates and
expansion of the model. This ensured that confidence in the model outputs at each stage
was understood, and provided confidence in the use of the model for the design of the
Selkirk Flood Protection Scheme and alleviation.
Target accuracy in the calibration should be set using tolerances of both peak water level
(e.g. +/- ± X mm) or less and in the timing of peak level (e.g. within X hours or less).
For catchment scale studies it is recommended that tolerances for peak water level at
measured locations are in the order of +/-300 mm or less and that, for local scale or
detailed studies, it is recommended that tolerances for peak water level are in the order of
+/-150 mm or less depending on the application. This can be considered to correspond to
medium and high confidence in the outputs respectively.
Target accuracy in the timing of the peak level will depend on the hydrograph duration; for
most purposes a target accuracy of 30 minutes would be appropriate however a larger
tolerance may be acceptable for catchments with a long time to peak and a 15 minute
tolerance may be required for very quickly responding catchments.
Calibration plots can be produced comparing modelled flows with those recorded at the
gauging station for an event. Tables can also be used to present a comparison of observed
and modelled peak flow, time to peak and stage at particular locations.
8.2.2 Coastal
Hydrodynamic models used to bring extreme still water estimates inland should be calibrated
for level at tide gauges. Where tide gauges are not available performance should be
checked against tide tables over a spring neap cycle, while installation of additional
temporary gauging may be considered. The hydraulic parameters which are usually varied
during model calibration are the bed roughness and eddy viscosity. Changes may also
be made to model boundaries and bathymetry.
Wave transformation models should be calibrated for significant wave height at wave buoys.
Where these are not available, installation of temporary gauging should be considered.
Calibration should be over a sufficient period to cover all wave direction sectors. The
hydraulic parameter usually varied during model calibration is the bed roughness, although
boundary conditions may also be adjusted.
It is unlikely that sufficient data will be available for calibration of wave overtopping
and coastal inundation models.
The Environment Agency document Best Practice in Coastal Flood Forecasting (HR
Wallingford, 2004) classifies wave and surge models as having high, medium and low
confidence if predictions of height are within about ±20%, ±30% and ±40% respectively. For
8.2.3 Pluvial
A detailed pluvial model with explicit representation of the surface water drainage network
should be calibrated according to the UDG guidance (WaPUG, 2009), which is used in the
collaborative Scottish Water and Local Authority Integrated Catchment Studies (ICS). Data
requirements for calibration are also given in this guidance.
There is unlikely to be sufficient data available to calibrate strategic and catchment scale
models. In this case a reality check against observed data should be carried out.
Model calibration parameters should only be adjusted within published and accepted
ranges For instance accepted Manning’s roughness coefficients for cultivated areas are
between 0.020 and 0.050 depending on the crop condition (Chow, 1959); so changing the
roughness coefficient to 0.1 for areas covered by cropland would not be appropriate.
Data errors should be considered a possibility during model calibration For instance
an incorrect gauge datum would lead to a mismatch between model and data and although it
might be possible to adjust model parameters to improve the fit to data this would lead to an
error in the model.
Changes to parameter values should be appropriate given the available data For
instance if roughness classifications have been based on land use maps it would not be
appropriate to vary roughness between individual fields with the same land use class unless
other information such as a site visit or aerial photography provided evidence for different
roughness. It would however be appropriate to vary roughness for the entire land use class
within published and accepted ranges. Similarly changing bridge coefficients based on a
single wrack mark upstream of a bridge may be inappropriate, as several other parameters
may affect water levels upstream of the bridge.
Catchment changes since the recorded flood event should be considered For instance
if flood defences have been constructed at a location the model would not be expected to
reproduce flood extents prior to the defences being constructed. It may be necessary to
construct a model of the historical condition of the catchment to assist in calibration however,
where changes have been extensive, the resulting calibration may be of limited use for the
present day case. It should also be noted that not all catchment changes will be
documented.
Calibration runs should always be driven using observed data A comparison of a 0.5%
AEP design event against an observed 0.5% AEP event would be a useful reality check but
would not constitute calibration as the design event may differ from the observed event in
several ways (e.g. hydrograph shape, combination of waves and tides, etc.).
The possibility of several parameter combinations giving the same fit to the observed
data should be considered Typically with flood models there are many fewer
measurements available for calibration than there are model variables. For example, in a 1D
fluvial model variables include roughness at each cross section and coefficients at each
hydraulic structure, while in a 2D pluvial model, variables could include roughness and
evaporation loss at each grid cell. Conversely flow measurements may only be available for
a single point within the catchment. Where there are more variables than measurements,
the problem is said to be “underdetermined” and there may be more than one combination of
parameter values which gives the same fit to the calibration data. These combinations of
parameter values may exhibit different sensitivity and give different results for extreme
conditions outwith the range of the calibration data. Where this is considered a possibility,
sensitivity tests should be carried out to assess the impact of choosing different plausible
parameter sets. This is particularly important for some hydrological models which may have
many more parameters than either 1D or 2D flood models.
Calibration data are not always available and, in such circumstances, greater emphasis
should be put on understanding the model sensitivity and model uncertainties.
Model sensitivity tests should be undertaken in order to give the modeller, reviewer and
users an understanding of what parameters affect the model and in what ways. Sensitivity
testing involves varying an element of the modelling and assessing how this alters the model
results. This helps develop an understanding of the confidence in the model and its outputs.
Sensitivity analysis is particularly important where limited data is available to validate or
calibrate the model or where there is large uncertainty in model parameters or input data.
Additional sensitivity testing of the following may be required, depending on the specifics of
the model:
• Model resolution e.g. increasing or decreasing the cell size e.g. 20 m -> 5 m.
• Key structure coefficients e.g. at bridges and weirs.
• Banktop/floodplain spill coefficients
• Initial conditions/initial water levels in storage areas such as ponds and flood storage
reservoirs
• For pluvial modelling, testing the sensitivity of the model to the storm duration used may
be appropriate.
• Wind boundary conditions, particularly for coastal surge models.
• For wave overtopping models beach/defence profile and overtopping model parameters.
The required sensitivity tests should be specified in the project SoR. Where information is
missing or uncertain, additional sensitivity testing may be valuable such as for example
influence of floodplain embankments.
The following sensitivity tests were carried out on SEPA’s strategic level national fluvial
hazard mapping models. More detailed studies may consider a wider range of tests in
addition to these.
• Sensitivity to a 20% increase in flow for the 1 in 10 and 1 in 200 year defended and 1
in 1000 year undefended scenarios.
• Sensitivity to a 40% increase in roughness for the 1 in 10 and 1 in 200 year defended
scenarios.
• Sensitivity to blockages for the 1 in 10 year defended and 1 in 1000 year undefended
scenarios
Results from the sensitivity analyses should be presented in the modelling report. Sensitivity
analyses results can be presented in several ways. For 1D models the analyses are usually
presented by displaying the different sensitivity model run results on a long section plot.
Alternatively plots showing difference in water level against chainage for each of the
sensitivity runs or tables showing the predicted level at key locations or model nodes of
interest for each of the runs can be produced.
Uncertainty is inherent in all models. Uncertainty arises at each level or stage in the process
of modelling flood risk and from a range of sources. Figure 8-1 shows examples of potential
sources of uncertainty in flood risk models.
The level of confidence in the output will reflect the uncertainties within each of the stages
of assessment, such as within the input data, parameters, the model and the way the
outputs may be transformed (Walker, et al., 2003).
Guidance from the Scottish Government (Scottish Government, 2011) states that
“Uncertainty should be clearly presented in flood risk assessments showing what
approaches have been used to quantify them and how decisions have been influenced by
uncertainties. Any assumptions made should be clearly set out”.
The level of uncertainty analysis should be proportional to the costs and potential benefits.
Detailed uncertainty analysis, with associated resource and time implications, may be
justified where the level of confidence in the model predictions would affect the outcome of a
decision or where the product would be used in evaluation of significant investment, such as
construction of a major flood defence scheme (Beven, 2011).
Consideration of confidence should reflect the purpose of the model and the decisions which
it is intended to inform. It should also consider the level of detail and modelling methods
applied at each level of modelling. In this way, a risk-based approach should be followed
(i.e. the level of risk informs the level of modelling which then informs the level of uncertainty
analysis required).
There are a range of existing methods for analysing uncertainty including both qualitative
and quantitative methods. These range from simpler forms of analysis (e.g. sensitivity
analysis and approaches which qualitatively score uncertainty), to complex approaches (e.g.
formal, expert elicitation where the opinion of several authorities on the subject is used to
inform confidence intervals, Bayesian methods, regressions and approaches involving
defining distributions for propagating the effects of different sources of uncertainty to see
how these influence model output). The ability to conduct detailed evaluation of uncertainty
may be affected by the availability of data required.
13
Sources of uncertainty identified in: (Apel, Thieken, Merz, & Blöschl, 2004); (Apel, Aronica,
Kreibich, & Thieken, 2009) (Maier & Ascough, 2006), (Bales & Wagner, 2009)
At the catchment to local modelling scales, the decision flow diagrams contained within the
FRMRC Framework for addressing uncertainty in Fluvial Flood Risk Mapping (Beven, 2011)
may assist in determining which methods of uncertainty analysis are appropriate. It is
recommended that at the outset of the project there should be consideration of the form of
uncertainty analysis required for the project and this should be specified in the SoR.
For all studies a description of the uncertainty analysis undertaken should be provided,
together with identification of potential sources of uncertainty and an indication of the level of
uncertainty. Decisions or judgments made about the uncertainty, including any assumptions,
should be documented.
9.1 Introduction
The range and number of scenarios run through a model will depend on the use of a flood
study. For example, a flood risk assessment according to SEPA’s Technical Guidance for
Stakeholders only requires the 0.5% annual exceedance probability (1 in 200 year) event
while a minimum of 5 flood events spanning a range from high to low probability are required
for detailed damage calculations (Penning-Rowsell, et al., 2013). Natural flood management
techniques are expected to be most effective for frequent flood events so an NFM study may
require consideration of more frequent flood events than a design for a hard flood defence
scheme.
Running additional scenarios is likely to increase the cost of a flood study but future use of
the model and results should be considered when specifying the required scenarios as the
costs of contractors rerunning the model at a later date to produce additional scenarios is
likely to be greater due to;
Extending the range of scenarios to cover more frequent events may improve confidence in
the modelling, as there is more likely to be data available for validation including anecdotal
evidence on the frequency of flooding.
The science on how climate change may affect flooding is still developing and recommended
allowances for climate change may go up or down in future. Estimates of present day
extreme flows and levels may also change as new data is collected or analysis methods are
improved. A wider range of scenarios can provide a measure of future proofing for a study
as new flow estimates may correspond to a scenario which has already been run.
SEPA’s national hazard maps use a consistent set range of scenarios across each source of
flooding which provide a suitable spread for the damage calculations used to inform the
Flood Risk Management Strategies. To maintain consistency, SEPA requires the same
scenarios to be provided for any update to the national hazard maps. This chapter sets out
the minimum scenarios required for an update to SEPA’s hazard maps. Additional scenarios
may be required in some instances, depending on the study area and the purpose of the
study.
Manning’s n
Undefended
Exceedance
Probability
+20% Flow
sensitivity
Defended
Blockage
Change
Climate
Annual
+40%
(%)
50 2
20 5
10 10
3.33 30
2 50
1 100
0.5 200
0.1 1000
Table 9-1: Scenarios used in SEPA's national fluvial hazard mapping.
9.3 Coastal
The scenarios used for SEPA’s hazard maps are given in Table 9-2. To maintain
consistency these scenarios are required for any study used to update SEPA’s coastal
hazard maps.
SEPA’s coastal flood maps do not include the effect of waves. For wave overtopping studies,
a joint probability analysis of waves and extreme still water level should be undertaken as
there will be multiple combinations of wave and extreme still water level which could
constitute for example a 0.5% AEP event. This may mean that a range of combinations of
extreme water level and waves need to be run for each flood probability.
Annual Exceedance
Return Period Undefended Climate Change
Probability (%)
10 10
4 25
2 50
1 100
0.5 200
0.1 1000
0.01 10000
Table 9-2: Scenarios used in SEPA's national coastal hazard mapping.
9.4 Pluvial
The scenarios used for SEPA’s pluvial maps are given in Table 9-3. To maintain
consistency these scenarios are required for any study used to update SEPA’s pluvial
hazard maps.
10.1 Introduction
Key Points for Responsible Authorities
The Climate Change (Scotland) Act, 2009 places duties on public bodies regarding climate
change, including acting in the best way calculated to deliver the Scottish Government’s
adaptation programmes, and to act in the way they consider the most sustainable.
Consideration of climate change is also a key part of the FRM Act. An investigation of the
impact of climate change on flood risk should therefore be a component of any modelling
study.
Information now available on potential climate change and its impacts on flows in our rivers
and the sea level at our coasts provides a clearer consideration of the probable range of
change across Scotland’s regions than ever before. The provision of regional climate
impacts in a probabilistic manner represents a significant change from the long-term
approach of considering the impact of climate change as a single figure uplift applied flatly
across the country.
The new information provides greater flexibility to consider climate impacts in a risk-based
framework although it could, initially, appear confusing. The change of approach warrants
further, specific guidance which will be forthcoming. This chapter of this guidance,
however, deals specifically with the consideration of climate change for strategic
modelling issues in support of FRM actions and summarises the latest information on
climate change impacts on flows.
This chapter;
• Summarises available climate change information for changes in peak river flow,
short duration rainfall, and sea level rise
• Discusses the approach used for these variables in SEPA’s national hazard maps
and whether this is still considered appropriate.
Although the UKCP09 projections were published in 2009, the guidance document “Flood
and Coastal Defence Appraisal Guidance FCDPAG3 Economic Appraisal Supplementary
Note to Operating Authorities - Climate Change Impacts” (DEFRA, 2006) has continued to
be used in many cases in Scotland due to the difficulties of directly relating changes in river
flow and sub-daily duration rainfall to the UKCP09 results. Recent SEPA and UKWIR
projects provide updated guidance on these areas, making use of the DEFRA (2006) study
no longer appropriate to inform strategic decision making. There have also been recent
improvements in understanding how climate change may affect mean sea level since the
publication of UKCP09.
The Met Office is currently developing a new set of UK climate projections, UKCP18, which
will update UKCP09. The projections are expected to provide improved information on how
climate change may affect short duration rainfall and sea level rise. Publication is due in
March 2018, and this guidance will be updated to reflect this and any other improvements in
scientific understanding.
10.3 Fluvial
• New information on how climate change may affect river flows is available. This
information is probabilistic, and varies between river basin regions.
• SEPA’s fluvial hazard maps used the 2080 high emissions scenario 67th
percentile (i.e. uplifts in peak flow that are “unlikely to be exceeded”
SEPA commissioned CEH to assess the vulnerability of Scottish river catchments to climate
change (Kay, Crooks, Davies, & Reynard, 2011). The study comprised a sensitivity analysis
to determine how catchments would respond to changes in temperature and the amount and
seasonality of rainfall. Projections for rainfall and temperature from the UKCP09 projections
were combined with the sensitivity analysis to produce a set of probabilistic estimates for
change in river flow for river basin regions across Scotland. These cover high, medium and
low emissions scenarios for the 2020s, 2050s and 2080s time horizons. The UKCP09 river
basins used are shown in Figure 10-1, together with the corresponding hydrometric areas.
Results for the medium emissions scenario for the 2050s are shown in Table 10-1, and
results for the low, medium and high emissions scenarios for 2080s are shown in Table
10-2. It should be noted that uplifts for the medium emissions scenario 50th percentile
in 2080s in the west of Scotland are considerably higher than the 20% uplift
recommended by the DEFRA (2006) guidance. A full copy of the report is available from
SEPA’s website https://www.sepa.org.uk/media/219493/ceh_report_final_sepa.pdf together
with a non-technical summary https://www.sepa.org.uk/media/219494/ceh-cc-report-wp1-
overview-final.pdf.
SEPA’s fluvial hazard maps used the 2080 high emissions scenario 67th percentile;
this is a relatively conservative approach which is considered appropriate for strategic level
mapping. The choice of scenario and probability should be appropriate to the purpose of the
study for instance, a modelling study to inform the design of a flood defence around a site of
critical national infrastructure may wish to use a more conservative climate change
allowance. The scenario or scenarios used should be justified in the modelling report and,
For studies at the coast, climate change projections for sea level rise should be considered
as in section 10.5.1.
River
basin Hydrometric Areas
region
North
1,2,3,4,5,6,7,8
Highland
9,10,11,12,13
North east
(northern)
13 (southern),
Tay
14,15,16
17,18,19,20,21
Forth
(coastal)
Tweed 21
Orkney
and 107,108
Shetland
West
93,64,95,105,106
highland
87,88,89,90,91,92,104
Argyll
(Kintyre), 105
82,83,84,85,86,104
Clyde
(Arran)
Solway 77,78,79,80,81
Figure 10-1: UKCP09 river basin regions covering Scotland, for which probabilistic estimates
are available. The hydrometric areas falling within each river basin region are given in the
table.
67 29 20 31 15 31 18 23 20 21 17
exceeded
very unlikely to
90 34 29 42 21 42 27 32 29 30 24
be exceeded
Table 10-1: Percentage uplifts for the medium emissions scenario 2050s, results from Kay, Crooks, Davies, & Reynard (2011).
W Highland
N Highland
Shetland
Scotland
Orkney/
Solway
Tweed
Argyll
Clyde
Forth
Tay
NE
Scenario Probability (%) Exceedence Likelihood
10 very likely to be exceeded 15 7 12 2 12 4 8 5 6 5
33 likely to be exceeded 20 14 23 10 23 12 16 13 13 11
50 is as likely as not to be exceeded 27 18 30 13 30 16 20 17 18 14
67 unlikely to be exceeded 30 24 36 16 36 20 26 22 23 19
LOW
unlikely to be exceeded
90 very unlikely to be exceeded 53 50 >60 33 >60 50 60 54 60 45
Table 10-2: Percentage uplifts of the high, medium and low emissions scenarios for the 2080s, results from Kay, Crooks, Davies, & Reynard,
(2011). Values shown in bold are those used in SEPA’s national fluvial hazard maps.
• New information on how climate change may short duration rainfall events is
available.
• SEPA’s pluvial hazard maps used a 20% uplift for extreme rainfall for the 2080s.
The new information suggests a larger uplift may be appropriate for future,
strategic studies.
The models used to develop the UKCP09 climate projections did not have sufficient
resolution to analyse the type of rainfall events typically responsible for surface water
flooding. SEPA’s pluvial hazard maps therefore used a 20% uplift based on DEFRA
guidance (DEFRA, 2006), which represented the best understanding at that time.
A recent study by UKWIR, Rainfall Intensity for Sewer Design, provides new
recommendations for percentage uplifts in sub-daily duration rainfall depths for climate
change scenarios (Bennett, Blenkinsop, Dale, Fowler, & Gill, 2015). This study used two
approaches to estimate predicted changes in rainfall depths;
• A comparison of the present day rainfall with that at a “climate analogue”, another
location which has a current climate similar to the projected climate. This was
undertaken for selected locations only, and results for Glasgow and Newcastle are
advised for use in the west and east of Scotland respectively;
• Analysis of a high resolution climate model simulation which is of sufficient resolution
to resolve the type of rainfall responsible for pluvial flooding. The model used does
not cover Scotland or Northern England, but has similar results to the “climate
analogue” approach elsewhere.
The study provides low, central, and high projections. The central projection is an
average of the climate analogue and high resolution model projections, while the low and
high projections give the spread in projections from the different approaches (note that the
high and low projections do not constitute a full probabilistic assessment and may not
capture the full spread of possibly changes). Uplift values from the UKWIR study for use in
Scotland are given in Table 10-3.
Changes in mean sea level or river flows may have an impact on the duration and frequency
of tide locking of surface water drainage systems. If the conceptual model identifies tide
locking as important, it may be necessary to consider climate change projections for sea
level rise and river flows, section 10.5.1 and section 10.5.1.
10.5 Coastal
• Climate change can affect coastal flood risk through changes in mean sea level or
changes in storminess which affects storm surges and waves.
• Recent projections of global sea level rise are greater than those used for the
UKCP09 climate projections.
• SEPA used the 2080 high emissions scenario 95th percentile, relative sea level rise
for the national coastal hazard maps.
• There are large uncertainties in the projected change in the UK wave climate due
to climate change. It is not possible to recommend climate projections for waves
however, sensitivity analysis should be undertaken where appropriate.
• The projected impact of climate change on surge is small compared to projected
changes in mean sea level and can usually be ignored.
Climate change may impact coastal flooding through changes in mean sea level or through
changes in storminess, which affect surge and waves.
UKCP09 provides projections of absolute and relative sea level rise. The relative sea level
rise predictions are of most use in flood risk management and account for movement in the
land surface. Results are available for the 5th, 50th and 95th percentile, high, medium and
low emissions scenarios on a 12 km grid around the coast. Projected sea level rises are
provided for every year up to 2100 from a base year of 1990.
UKCP09 projections of trends in storm surge are less detailed than for sea level rise. Long
term linear trends in mm/yr are provided for the period 1951-2099 for the medium emissions
scenario 5th, 50th and 95th percentile only. In most locations the projected change in surge
in the UKCP09 results is small compared to the projected changes in mean sea level, and
may not be distinguishable from natural variability so that consideration of changes in mean
sea level only is sufficient.
The CFB boundaries suggested for use in section 6.5.1 have a reference year of 2008, so
the change between 1990 and 2008 in the UKCP09 results should not be included if the
CFB boundaries are used as a model input.
The UKCP09 sea level rise grids do not cover the upstream extent of some estuaries and
sea lochs. If hydrodynamic modelling of the loch or estuary is not undertaken to establish
extreme sea levels inland, the adjacent downstream UKCP09 sea level rise grid predictions
should be ‘borrowed’ and used directly at the estuary/loch site of interest. If hydrodynamic
modelling is undertaken, the sea level rise estimates should be applied to the offshore
boundary of the hydrodynamic model.
10.5.2 Waves
There are large uncertainties in the projected change in the UK wave climate due to climate
change; the UKCP09 projections have changes in the annual maxima of between –1.5 m
and +1 m (Lowe, et al., 2009). The Marine Climate Change Impacts Partnership report
“Impacts of climate change on storms and waves”. Woolf & Wolf (2013) reviews current
understanding and identifies knowledge gaps, including:
• How changes in the mid latitude storm tracks due to climate change.
• How results from global climate models can be best used to investigate local
changes in wave climate.
• How changes in offshore waves have an impact at the coast.
Due to the uncertainty it is not possible to recommend climate projections for waves,
however appropriate sensitivity analysis should be undertaken.
12.1 Introduction
Natural Flood Management (NFM) is an important component of the FRM Act, which
requires it to be considered in the development of flood protection measures. SEPA’s
Natural Flood Management Handbook (Scottish Environment Protection Agency, 2016)
provides a practical guide to the delivery of NFM measures. This chapter is intended to
compliment chapters 5 and 6 of the NFM handbook and the rest of this guidance document
by providing further information on how NFM may be included as part of a modelling study.
The relationship between the modelling process in this guidance and the NFM
implementation process outlined in the NFM handbook is shown in Figure 12-1. The
following discussion assumes that opportunity areas for NFM have already been identified
(step 3 in the NFM implementation process).
Despite recent research there are still gaps in scientific understanding of how the potential
effects of NFM measures may be assessed, particularly for measures in the wider
catchment. Dealing with these knowledge gaps may require innovative approaches to be
adopted for NFM studies other than those considered here, and this chapter will be
developed as scientific understanding improves.
• Any modelling should be proportionate to the study objectives, the likely scale of
impact of the NFM measures and the achievable confidence in the approach and
outcomes.
Modelling may be required at 3 stages of the NFM implementation process, short listing of
measures (part of the NFM scoping stage), options appraisal/detailed assessment and
detailed design. At all stages the investment in any modelling should be proportionate to the
study objectives, the likely scale of impact of the NFM 3 measures and the achievable
confidence in outputs.
Step 1 – Need/aspiration
Identification of NFM need or aspiration by Local
Authority in FRM Strategies and Local FRM Plans or
by land manager, NGO or local stakeholders.
Step 2 – Engagement
Land manager engagement to assess level of interest
and obtain buy in, plus wider stakeholder engagement
and awareness raising – will continue throughout
process.
Figure 12-1: Relationship between the modelling process as set out in this guidance document
and the NFM implementation process set out in the NFM handbook.
In some cases the same scenario testing process can also be used to inform short listing of
hard engineering measures.
For measures which are in or adjacent to a river channel, hydraulic modelling can be used to
provide a quantitative estimate of the effects of the NFM measure on water levels,
hydrograph timing, flood extents and damages relative to the baseline scenario.
For measures in the wider catchment, hydrological modelling can be used to provide a
qualitative indication of the effect of the NFM measure on peak flood flows and hydrograph
timing. Current limitations in scientific understanding and assessment tools mean that
a quantitative assessment of NFM measures in the wider catchment is not possible.
NFM should be considered at the scoping stage of flood modelling studies, as the location
and type of possible NFM measures may affect the modelling approach taken and the study
area. Developing a conceptual model of a catchment is particularly important for NFM
studies as measures designed with a poor understanding of catchment flooding mechanisms
could inadvertently increase flood risk, for example, through increasing the synchronicity of
flood peaks or increasing the risk of structure blockages. The study area should be sufficient
to cover all upstream and downstream effects of proposed NFM measures.
The Whitesands area of Dumfries experienced significant flooding from the River Nith in
1962, 1977, 1982, 2009 and 2013. There are extensive agricultural flood embankments
on the Nith upstream of Dumfries and breaching these to reconnect the flood plain and
provide additional storage was identified as a potential NFM option to reduce flood risk
within the town.
To assess this option a model of Dumfries was constructed covering the proposed areas
of flood plain reconnection and the town of Dumfries. The model showed that although
breaching the embankment reduced water levels in the town for 10% and 4% AEP events
they were increased for 1% and 0.5% AEP events. The breach in the embankments
allowed the water to flow into the storage area, behind the embankment before the peak of
the event so as the event peaked, the storage area, which was already full, was unable to
store more water, causing the water in the storage area to flow back into the watercourse.
Without the breach the area behind the embankments only flooded during the peak of the
event reducing water levels downstream during the peak (Mouchel, 2011).
Considering potential NFM options during scoping allowed the study area to be extended
to cover the area identified for the NFM measures. The unexpected detrimental effect of
this NFM option during larger flood events highlights the importance of developing a
conceptual model of the catchment flooding mechanisms in order to identify all possible
effects of a measure. In other situations the conceptual model may identify positive
impacts of NFM which otherwise may not have been identified during scoping.
• NFM is expected to be most effective for more frequent flood events so these
should be considered in the flood modelling study.
• Representation of some NFM measures in hydraulic models is uncertain so
additional sensitivity testing may be required.
• The hydrological analysis should be extended to cover flow events which occur
more than once a year on average.
• The scenarios run should be sufficient to determine if there is a change to the
frequency of out of bank flows or the depth or duration of flooding during frequent
events.
• The scenarios run need not include less frequent flood events if the measure has
no measurable effect for more frequent events (e.g. if a measure has no effect in
a 3.3% AEP event and a 2% AEP event it would not be necessary to model a 1%
AEP event. However, a 0.5% AEP event will usually be required for a flood risk
assessment at detailed design stage in line with (SEPA, 2015)).
• Results for the 50% AEP event and more frequent events should be mapped for
the baseline model. These maps should be compared with landowner or land
manager knowledge of frequent flooding.
• The schematisation used to represent NFM measures should be described in the
modelling report, and justified with reference to available research literature.
• Sensitivity tests should cover;
o The schematisation of each NFM measure. This should consider the full
range of plausible parameter values.
o Seasonality and maturity of the NFM measure, where relevant.
o Blockages at key structures downstream of the measure if the NFM
measure may increase debris supply.
The benefits of many NFM measures are likely to be greatest for more frequent events while
some will have no measurable impact during major flood events. Some NFM measures may
affect the frequency, depth or duration of flooding of agricultural land which is already
subject to frequent flooding; providing an indication of the scale of these effects may also
assist in consultations with landowners. Where data is available, calibration of the baseline
model without any NFM measures in place should be as described in chapter 8. Landowner
and land manager knowledge should be used as an additional source of historic flood event
data for model verification.
For many NFM measures there is a limited body of scientific research available to
support model schematisation, so modellers have to use expert judgment in choosing
how to represent NFM measures. For instance debris dams could potentially be
represented in a 1d hydraulic model by;
• a constriction in individual a cross section,
• increased roughness along a river reach,
• as a weirs, spill or gate
For each of these possible schematisations there are a range of parameter values which
may be appropriate (percentage constriction, roughness value, weir coefficients etc).
The level of confidence in the modelling of any particular NFM measure will depend on the
type of NFM measure being assessed and the body of scientific research available to
support model schematisations and the choice of parameter values. The effectiveness of
some NFM measures may depend on the season and the maturity of the measure. For
instance vegetation will increase roughness more in summer than in winter, and roughness
for established riparian woodland will be greater than for newly planted woodland. There
may be concerns that, in some cases, NFM may increase debris supply, which may in turn
lead to structure blockages.
• The additional cost associated with the use of more complicated approaches such
as development of bespoke tools or the use of distributed hydrological models
should be justified by an expected reduction in uncertainty.
• Contractors should be able to demonstrate sufficient experience in the use of any
models or techniques proposed and their application to NFM. This is particularly
important for distributed hydrological models which historically have been used
primarily for academic research and where engineering and modelling consultants
may have limited experience.
• Contractors should be able to demonstrate that any bespoke or new tools have
been checked and reviewed and are appropriate to the study.
With all types of hydrological models there is uncertainty regarding the application to NFM
and how model parameters should be modified to represent proposed catchment changes.
At present, the use of hydrological models is restricted to providing an indication of the
sensitivity to any proposed change and where in the catchment changes are likely to have
most effect. There is insufficient confidence in the application of hydrological models to
assessing NFM measures to provide predictions in the change in flow due to NFM for a
particular rainfall event. The NFM handbook gives examples of three approaches which
may be useful in NFM studies;
The approach adopted will depend on the purpose of the study, the available data, the size
of the project and the potential impacts. It should be noted that more complex approaches
may not necessarily lead to a significant reduction in uncertainty.
Uncertainty analysis is particularly important where hydrological models are used in NFM
studies. Uncertainties arise because:
• The relevant physical processes and inputs may vary over a much smaller scale
than the available data. There may also be gaps or inaccuracies in the required
input datasets.
• The model resolution may not be sufficient to capture local processes, for instance
,in a distributed model there may be several small incised channels within a model
grid square.
• Not all relevant processes may be included in a chosen model
• A large number of model parameters may be adjusted through calibration though,
typically, only a small amount of calibration data is available. Several choices of
parameters may give similar fits to data but they may respond differently to
change scenarios. Where models are well calibrated to current conditions, it is not
certain that they will remain well calibrated for the future condition with the
inclusion of the NFM measure.
• It may not be clear how input datasets should be altered to account for change
scenarios.
• Even physically based models which include a detailed representation of
hydrological processes involve some form of parameterisation, for example
vegetation may be divided into types and certain properties such as canopy
storage would be associated with a particular vegetation type. These
parameterisations may not be relevant to all catchments.
A further discussion of the issues involved is provided in (O’Donnell, O’Connell, & Quinn,
2004).
13.1 Introduction
Flood maps can be produced from hydraulic model results to spatially represent data such
as flood extent, depth, velocity and hazard for sources such as pluvial, fluvial, coastal and
sewer flooding. This chapter;
• describes how flood maps are produced from different types of model;
• describes some of the issues which can occur with different types of maps;
• suggests what should be considered in a review of flood maps;
• describes the post processing required for consistency with SEPA’s national hazard
maps.
13.2 Fluvial
The basic data requirements to create a flood extent map include maximum water levels, a
DTM and cross section locations. If the model includes reservoir or storage units then these
will need to be represented separately in order to represent the water level within the
reservoir unit as opposed to the cross section at this location and, in this case, a plan of the
reservoir locations is also required.
A triangulated irregular network (TIN) is created from the cross sections and reservoir areas
and the water level at each cross section is assigned to the relevant nodes (vertices) of the
TIN. This water level is then interpolated between the TIN nodes to create a water level
surface. The DTM is subtracted from the water level surface to produce a depth grid. Areas
with negative depth are dry and removed from the outputs. Flood extents are then produced
by contouring the processed depth grid.
The resolution of the DTM used determines the resolution of the flood maps. As such it
should be appropriate for the level of detail in the model and should not lead to excessively
large file sizes for the depth grids. It is recommended that 1D flood maps have a maximum
resolution of 5 m.
Due to the interpolation of level results between model cross sections several issues may
occur in 1D flood maps and a careful check against the 1D model results is required. The
maps should be examined for the following features and if, necessary, the model should be
amended accordingly.
• Isolated patches of flooding which are not well connected to the river;
• Flood extents which appear constrained by cross section extents or reservoir extents;
• Flood extents which are greater than the area covered by the cross section extents
or reservoir extents.
1D flood models do not have the functionality to produce hazard ratings or floodplain
velocity. Where these are required a 2D model should be used.
For 1D-2D models, flood extents and depth and level grids for the 1D component only
should be produced as for 1D models and added to the 2D grid. For consistency with
SEPA’s hazard mapping the 1D component should be assigned a value of ‘200’, velocity
for the 1D component should be assigned a value of ‘200’ for the magnitude and ‘-9999’ for
the direction.
13.5 Post-Processing
Post processing of flood maps is required to ensure an appropriate representation of flood
risk. The requirements of post-processing will vary dependent on the purpose and scale of
the flood map; however typically post processing is carried out to:
Remove dry islands below an area threshold as confidence in flood extents at a small
spatial scale is likely to be low and these areas would be isolated during a flood event.
Numerous small holes also increase the complexity of storing the data in GIS.
Remove puddles below an area threshold as confidence in flood extents at a small spatial
scale is likely to be low. However, the reason for the puddles should be understood before
any post processing as this can indicate incorrect initial conditions, frequent wetting and
drying of the model or general instability. Numerous small puddles also increase the
complexity of storing the data in GIS.
Show bridges as wet or dry depending on whether or not there is flow over the bridge
deck. This is used to assess flood risk to transport routes. Depending on the DTM, the
bridge representation in the model and the method of flood mapping this may require manual
post processing.
Depth threshold pluvial model results so that the entire model domain is not included in
the flood extent.
• Remove dry islands and isolated wet areas less than 200 m2 which are not
connected to the floodplain. Dry islands have been assigned a depth of 0.01 m, a
velocity of 0.01 ms-1 and a hazard of 0.1.
• Remove results below a depth threshold of 0.1 m for pluvial flooding
14.1 Introduction
Errors in data, model schematisation and analysis can have a major effect on study results.
At worst, if these errors are not identified, decisions can be made based on incorrect
modelling, for instance development could be permitted in areas at risk or flood defences
could be built to the wrong level. Where errors are identified during a project this can lead to
significant rework and result in time delays while, if errors are identified after a project is
finished and “accepted” by a Responsible Authority it can be difficult to get contractors to
revisit the work.
To ensure good quality output, quality control and quality assurance should be built in to all
stages of a modelling project, by both the Responsible Authorities and contractors Figure
14-1. This will require the Responsible Authority to review outputs and provide input at key
stages of modelling project.
This chapter recommends quality control and quality assurance activities which may be
carried out by contractors and Responsible Authorities at different stages of a modelling
project. However, it is does not seek to replace Responsible Authorities’ or contractors’
quality assurance and quality control procedures.
The Responsible Authority should consider the required quality criteria for the modelling in
terms of calibration tolerances, and this should be stated in the SoR.
The contractor should set out the quality control and quality assurance processes which will
apply to the project in their tender. Risks to quality should be included in the risk register.
The Responsible Authority should ensure that the appointed contractor is proposing to use
qualified and experienced staff for modelling, hydrology and project management.
Identification of less experienced staff as part of a project team is acceptable provided that
sufficient time is allocated for more experienced staff to provide technical input. In addition
to the core project team a contractor should identify an internal reviewer who is not directly
involved in the project.
Where the study involves development or use of novel tools of methodologies to meet
Responsible Authority requirements in developing areas of flood risk science such as NFM
or Climate Change additional levels of review are likely be required. The contractor should
set out how any novel tools will be or have been reviewed in their tender, including review of
the concept, coding and usage of the tool. If there is any concern regarding novel
approaches, please contact SEPA.
Agree contractor’s
conceptual model
and methodology Model Conceptual model and
Schematisation proposed methodology
Review hydrology (Chapters 6 and reviewed by experienced
technical note 7) staff.
Design runs
(Chapter 9)
Figure 14-1: Contractor and Responsible Authority QA and QC activities at different stages of
a modelling project.
The contractor should develop its own conceptual model for the study area and decide on an
appropriate methodology also considering the study purpose. The conceptual model and
proposed methodology should be reviewed and signed off by an experienced modeller and
agreed with the Responsible Authority. A review by suitably experienced staff at this stage
should ensure that an appropriate approach is adopted from the start of the study, that
potential problems are identified and appropriate mitigation is put in place. This should
include identifying key points in the study where an internal technical review of the modelling
and analysis by the contractor would be beneficial.
Available data should also be reviewed at this stage to determine if it is suitable to meet the
objectives of the study or if there are any issues with data quality and availability. Where the
available data is not sufficient to meet the study objectives and quality criteria the contractor
should make the Responsible Authority aware of the quality implications.
Errors in models and calculations can significantly affect study results. The contractor
should carry out an audit of the modelling and any calculations. This should be carried out by
an experienced modeller who has not been involved with constructing the original model or
models. The exact checks carried out will depend on the level of study and the methodology
used.
For strategic scale studies such involving multiple models, such as the nearly 3500 models
created for SEPA’s national fluvial hazard mapping project, it may not be feasible to carry
out a detailed review of all models. In this case it may be appropriate to use automated tools
to screen for numerically unstable models and any physically unrealistic or inconsistent
results. However, the method used and implementation of the method as well as the results
from any screening should be reviewed by an experienced modeller. If automatic checks
are used, detailed manual checks should also be carried out on a subset of models to
ensure that any systematic errors not identified by the automatic screening are detected.
The Responsible Authority should ask for evidence that this audit has been carried out; this
can be in the form of a signed technical review certificate, or a model audit report, with a
record of actions taken. An example review certificate from SEPA’s regional pluvial hazard
mapping is included in appendix C.1. A pro forma for a fluvial flood estimate review is given
in Appendix C.2.
Numerical solution – including mass balance, sensitivity to parameters which affect the
numerical solution, model convergence.
Documentation – log file documenting all model version and key assumptions, data
register, comments in model etc.
Results and sensitivity tests - behaviour of model as expected, results consistent between
different AEPs.
Due to potential problems with instability of 1D-2D models, Responsible Authorities are
advised not to accept models unless the mass balance for all model runs is reported in the
model audit and is within acceptable limits.
Review of interim outputs at key points by the Responsible Authority can help identify
potential problems. As a minimum it is recommended that Responsible Authorities review
the following outputs;
In reviewing outputs Responsible Authorities should use their local knowledge to check that
results are physically realistic however, they should be aware flood models can show the
correct behaviour for smaller events within Responsible Authority experience but may not
exhibit the correct sensitivity for larger events. Responsible Authorities should be satisfied in
their review of outputs that there is no evidence of the common problems for different types
of model described in sections 7.2.3, 7.3.4 and 7.4.1. SEPA may be able to assist with the
review of outputs if required.
It is important that complete model run and results files are provided by a contractor as set
out in Section 15.4 as it is not possible for a Responsible Authority, SEPA or any external
reviewer to review a model only from the modelling report. Any survey data or photographs
should also be provided to enable model schematisation to be checked against the survey.
14.4 Reporting
Key Points for Contractors
• The modelling report should clearly state the purpose of the modelling and any
limitation.
• There should be sufficient detail in the modelling report and appendices for any
experienced modeller to reproduce the analysis.
To avoid inappropriate future use of the study outputs, the modelling report should clearly
state the purpose of the modelling. Any limitations of the study, the data and the method
used which may affect use of the results should be highlighted, and recommendations for
future improvements to the modelling should be made.
The modelling report and appendices should comprise an audit trail for the modelling,
providing sufficient detail of the methods and datasets used for any experienced modeller to
reproduce the analysis.
15.1 Introduction
It is important that the correct deliverables are specified in the statement of requirement
(SoR). To enable future reuse of the data this should include all model outputs in a GIS
format, full model results, reports and run files. The details of what is required should be
explicitly stated in the SoR. Where historic flood events have been used for calibration,
results from the calibration models should also be supplied, together with the data used for
calibration. For projects involving 2D modelling it is likely to be necessary to supply a hard
drive for transfer of the data.
• Technical report
• Non-technical report or summary
• Model hand over report
• Model audit report
The report should include appropriate maps of the study area, cross-section locations and
plans of the model results. If a separate non-technical summary is not requested, this may
be included as a chapter within the main report.
The specific outputs which are to be received should be stated in the SoR. SEPA
recommends that the extent and depth, and hazard, velocity and flow direction (as
appropriate) is supplied as a minimum. This should be requested in the relevant proprietary
format the Responsible Authority uses and, if being sent to SEPA, ideally within the ESRI
shapefile/raster format. It is advised that ESRI geodatabases are not used as compatibility
issues with older versions of software may prevent data being shared easily between
Responsible Authorities.
These are standard outputs from hydraulic modelling packages commonly used in the UK,
and are absolute minimum required for interpreting model results.
To facilitate data sharing between Responsible Authorities, all data should be in a suitable
format for import into GIS either ESRI ascii grid format, GeoTIFF or .bil format, and -9999
should be used as no data value.
For direct rainfall (surface water) models where rainfall is applied to every point of the model
grid, large areas of the model will be covered by a shallow depth of water. In this case the
results should be requested with a 0.1 m depth minimum threshold in addition to the un-
thresholded depth results in order to remove large areas of very shallow flooding.
Flood depth and elevation grids should not contain no data values at building centroids in
order for depth damage calculations to be carried out. This is discussed in section 7.3.2.1.
15.3.1.2 Hazard
For consistency with SEPA’s national flood hazard maps, hazard should be calculated using
the flood hazard formula in Defra report FD2321/TR1 Flood Risks to People (HR
Wallingford; Flood Hazard Research Centre, Middlesex University; Risk & Policy Analsysts
Ltd., 2006).
HR = d(v+1.5)+DF
For consistency with SEPA’s flood hazard mapping and modelling the debris factor DF
should be 0.
15.3.1.3 Velocity
Grids of both speed and direction should be requested. The maximum velocity should be
‘maximum velocity’, not ‘velocity at maximum depth’. Where the models wetting and drying
is leading to high velocities for shallow depths of water, a depth threshold for tracking
maximum velocity may be applied.
• Flow for assessing the flow split between out of bank flow paths
• Froude number for assessing if flow is sub or supercritical. Some calculation
methods are less accurate as flows become supercritical so this may affect model
confidence, or help in identifying model issues.
• Duration of flooding for emergency planning or detailed damage calculations
• Time of onset for emergency planning
• Bed shear stress for assessing the potential for erosion.
If additional outputs are required this should be discussed with the contractor prior to starting
final model runs as if additional output is not selected at this stage the model may need to be
rerun in order to generate the output.
Flood extents and the Area of Benefit from a flood defence should be requested in ESRI
shapefile format, as well as any proprietary format required by the partner organisation’s GIS
format. ESRI shapefiles can be imported into most other GIS packages and this facilitates
sharing of data between Responsible Authorities.
Flood extents and Area of Benefit should not be simplified or smoothed and should match
the supplied depth grids.
Flood extents should not show bridge decks as flooded unless there is flow across the
bridge deck in the model.
Interactive PDFs can provide an improved visual representation of flood risk and
understanding into the mechanisms of flooding. They can allow users to click on different
scenarios and pre-defined storm durations to allow the user to visualise flood risk. Interactive
PDFs can be used for various applications such as flood protection scheme designs,
displaying model run information and even combined events i.e. a fluvial and coastal flood
events.
For 2D models it is possible to select time series output of level, depth and velocity at point
locations, and flow through cross section lines. As a minimum, the flow time series should
be extracted at all gauges. Locations where point output and flow through cross section
lines are required should be discussed with the contractor prior to final model runs. This is
because it can be difficult and less accurate to calculate these from the model output files.
A description of the files which would be expected to be received for modelling software
commonly used in Scotland is given in Appendix E. SEPA can provide assistance in
checking that all the expected files have been supplied if required.
A model log file should also be provided stating which run files were used to produce each
output.
Comments, including names, of all significant structures within the model should also be
provided together with comments on any modification to structure coefficients.
Derivation calculations (e.g. spreadsheets) used for any model inputs (e.g. for boundary
conditions) must supplied. The merged DTM used in construction of the model and for
production of flood maps must be supplied. This will allow the model to be re-run and
mapped for other scenarios at a later date if required.
15.6 Photographs
Any photographs taken in the course of the study (e.g. on site visits) should be supplied
along with an appropriate caption / commentary to establish what the photographs depict.
These should ideally be georeferenced to the OSGB 1936.
Once the deliverables have been approved by the reviewer and approver (i.e. project
executive) signoff of the products can be undertaken.
Please contact strategic.floodrisk@sepa.org.uk for a copy of the template flood study SoR in
an editable format. It is intended to include the SoR here in a later version of the guidance,
however SEPA wish to receive feedback on the usefulness and appropriateness of the
present version of the SoR prior to making it publically available.
Statement of Requirements
1 Background
2 Introduction
Responsible Authority Name wishes to carry out a topographic survey of a reach of the River
XXX, specifically between XXXX and XXXX, along with associated tributaries including the
XXXX and XXXX. Cross section spacing and length should be informed by best practice and
knowledge. Survey work should be carried out by the use of GPS surveying instruments and
methods. All survey work should be carried out in line with best practice and in line with the
Royal Institution of Chartered Surveyors (RICS) guidelines for surveying. The information
gathered will be used for constructing a computer model of the watercourses and will be
used in conjunction with existing LiDAR information to produce a 1D-2D model for the area.
The aim of this project is to undertake a topographic survey of a reach of the upper XXXX
catchment from XXXX to XXXX including the XXXX and the XXXX. The information gathered
will be used for constructing a computer model of the watercourses and will be used in
conjunction with existing LiDAR information to produce flood extents for the area.
The study area is outlined in the XXXX Study Location Map – see Appendix A. Costings for
the work should be produced.
The successful tenderer appointed in due course as the surveyor (the “Surveyor”) shall
provide all services required to satisfy the objectives of this study. The services will include,
but not necessarily limited to, the main task of undertaking a topographic survey.
5 Land Ownership
Prior to work commencing Responsible Authority Name will obtain the permission of each
landowner or tenant to undertake the survey. Responsible Authority Name will also provide
in writing, proof that the surveyor is working on their behalf.
6 Quality Assurance
The Surveyor shall apply quality management procedures to ensure that the information and
materials provided under this contract adhere to the Specifications and are fit for purpose in
terms of quality, completeness, standard of presentation and timely delivery.
The Surveyor shall be responsible for adopting full quality control and assurance procedures
at each stage of the work to ensure that mistakes, errors and omissions are identified and
corrected prior to the delivery of the results. The Survey shall not be considered delivered
until received in a form that complies with the specification.
Ecological sensitivities should be considered for the catchment and stated if required –
example below.
8 Survey Specification
The following specification should be adhered to, (any deviations not agreed with
Responsible Authority Name will possibly involve additional survey work by the surveyor at
their own time and cost). Reference should be made to the Environment Agency Survey
Specifications (Environment Agency, 2013, National Standard Contract and Specification for
Surveying Services Standard Technical Specifications Version 3.2).
• WATERCOURSE CENTRELINE is determined from the lowest point in the bed level;
• A CROSS SECTION is normal to the watercourse centreline;
• LEFT and RIGHT are determined either side of the watercourse centreline
when viewed toward the downstream direction of the watercourse;
• SKEW ANGLES are estimated clockwise from the direction of stream;
• CHANNEL WIDTH is determined between natural river bank edges;
• HARD BED LEVEL is that to which a staff, pole or rod with a base area of 0.0005 to
0.0025 square metres can be driven to refusal;
• SOFT BED LEVEL is that to which a staff, pole or rod first meets resistance
underwater;
• Levelled cross sections are to be taken across the channel. Cross sections should be
perpendicular to the channel/flow direction and viewed downstream. As a general
guide, cross sections should be undertaken at XXX m spacing reducing to XX-XX m
and X m and to capture physical changes to the river channel respectively (Insert
location map reference). All levels shall be accurate to +/- 10 mm. Cross channel
chainage shall be accurate to +/- 100 mm and longitudinal chainage between cross
sections to be accurate to +/ -1000 mm.
• Where it is not practical to survey a section at the prescribed position or interval the
position of the section may be moved. However, the interval between two adjacent
sections shall not exceed the prescribed interval.
• Cross section levels shall be taken at straight line normal to the watercourse
centreline with all changes in slope recorded. Section survey points should be taken
at each significant change in slope and at chainages not exceeding 2 m across the
channel
• Cross-sections are to be surveyed viewed downstream. The origin (zero chainage)
must be established on the left side of the section.
• Cross sections should extend both sides of the water courses to the true land level,
extending 5 m beyond bank top where possible. Where possible, it is essential that
all sections are measured into open spaces clear of trees and dense vegetation
cover to a maximum distance of 50 m to allow tie in with LIDAR data. In those
instances where a bank top is raised above the surrounding ground (flood plain),
sections should be measured to 5 m beyond the landward toe of the crest; the crest,
defined as the line along the bank top over which water will spill form the river onto
the surrounding ground.
• Water level should be recorded at each section on the day of the survey with the date
and time recorded each day. Channel bed levels and bank levels either side are to
be recorded.
• Bed levels will be measured directly whenever and wherever possible. Where direct
measurement is impossible, where, for instance, the water depth is too great or other
causes make it impractical, then other methods to be considered include
measurement by boat or reading the depth of water against a staff and relating these
readings to a measured water level.
• Where silt occurs both the hard bed and the silt top will be measured at the same
points. The hard bed will be shown as a pecked line and labelled "H" in the digital
data. The silt top will be shown as a solid line.
• Each individual cross-section, including structure sections should be given a unique
identifier.
• The sections will be plotted to a vertical scale of 1:100 and horizontal scale of 1:200.
• Any flood plain sections required are denoted in insert cross section location
reference. Flood plain sections will be taken normal to the centre line of the valley
Bridges
• For bridges, the springing level, soffit level, abutments, parapets, deck level and
internal arch or flow area dimensions should be recorded and marked on the cross
section plan. The Surveyor should survey the bed level where the structure enters
the bed. Details of any bridge piers must also be included and the length of the
bridge or tunnel is to be measured parallel to the watercourse.
• The downstream elevation will be presented as viewed looking downstream and is
required to be surveyed when specifically requested or where it is different from the
upstream side. Even when a downstream elevation is not required, the downstream
soffit, top of parapet, invert, bed level and bank crests are to be measured and added
to the longitudinal section
• Where structures are skewed across the channel, the skew span will be measured
together with the appropriate skew angle and marked on the associated topographic
drawing. The length of the bridge tunnel will therefore be the channel length through
the bridge, not the distance at right angles to the roadway.
• Where a structure extends 10 m beyond the top of bank then the complete elevation
will be surveyed with its cross section. Where a bridge spans the flood plain, then all
relevant flood arches (and other openings that could take flood water) must be
included in the cross section.
• In situations where the bridge is not going to be overtopped and/or reduce
conveyance with increasing water depth, a full bridge survey is not required; bridge
parapet, soffit and springing levels can be omitted. Bridges identified for survey will
be discussed at the inception meeting.
Culverts
• Complete dimensions of the inlet and outlet elevations of culverts are to be taken
alongside the channel section as done with the bridge structure. For pipe culverts,
internal pipe diameter, invert, soffit and crown of pipe levels should be recorded
upstream and downstream. The length of the culvert should also be measured if safe
to do so. Details of any trash screen and flaps, including dimensions, number of bars,
bar width and bar spacing should be recorded and noted on the cross section plan.
• A cross section will be taken along the crest of the weir and structure details will be
taken and annotated on the associated topographic drawing. For weirs that do not
cross the watercourse in a straight line perpendicular to the watercourse, the actual
length of the weir shall b stated clearly on the cross section drawing. A long section
of the weir will be produced extending both upstream and downstream to the natural
river bed. The weir long section will have the following information:
• A longitudinal survey is required along the top of both banks of all watercourses.
Levels will be taken at a minimum of 25 m (or as agreed) or where there are sudden
or pronounced changes in ground level e.g. collapsed embankment.
• Where flood defences or embankments are present, this should be taken as the top-
of-bank levels and general details on the condition of the flood defences or
embankment should be noted i.e. if there is a gap where water could escape.
• Where there is no embankment / wall the ground level should be given:
• An electronic copy of the survey on CD-ROM in PDF, CSV, 2D and 3D DWG (2013
or earlier) with each surveyed point to have an X, Y and Z value.
• All data to be presented graphically on key plan/section location maps, cross
sections, structure sections and long sections should be made available as a CSV
xyz file, in DWG format and in a format compatible with Flood Modeller/HEC-RAS
software (.txt/.dat and EACSD) – see Appendix B. This cross section data will contain
the following:
o The deepest bed level at each section, both hard bed (solid) and silt line
(pecked).
o The water level at each section.
o The bank crest levels derived from crest point levels shown on the cross-
sections, the left bank as a pecked line and the right bank as a bold line.
o The extent and level of any concrete sill or apron together with appropriate
label. The section number and chainage of each section and the altitudes of
each of the plotted points. The chainage shall be quoted to the nearest metre
except when the scale of the survey makes it appropriate to quote the
chainage to decimetres.
o All structure with their critical levels (soffit, invert, deck, crest etc.)
o Tributary channels should be included where surveyed
o Where changes in the levels of bank, bed or water level occur between cross-
sections, these changes are to be measured and added to the longitudinal
section. The longitudinal section should represent an accurate and complete
profile of the channel to ensure that low spot and level changes are identified.
• A GIS shapefile clearly showing the survey route, the uniquely identified cross
sections and any survey gaps.
• Digital copies of georeferenced photographs of cross section locations,
embankments and structures.
• A digital key plan based on suitable Ordnance Survey grid is to be produced showing
clearly the extent of survey. In addition, scale, a north point and sheet coordinates
are to be indicated.
9 Data
10 Security
• The highest classification of data for this contract will be OFFICIAL: COMMERCIAL.
• From the onset of the contract all Consultant staff (or any contractor or sub-
contractor appointed by it) who have access to Responsible Authority data must as a
minimum be fully compliant with the requirements of the Baseline Personal Security
Standard (BPSS).
• Responsible Authority require confirmation of the office location(s) from where the
work will be undertaken both by the Consultant and Sub Contractors for this contract.
• At tender stage details of how project data will be accessed, stored, transmitted and
handled within your organisation is required. This should include both electronic and
hard copy data and meet the Cabinet Office Security Policy Framework requirements
as a minimum.
11 Meetings
An allowance should be made for an inception meeting. Thereafter, contact will be made
primarily over email or telephone to discuss progress or any issues that have arisen which
may lead to a delay in the delivery date.
12 Delivery Timescales
The tender return should include a programme of work that takes the following milestones
and key dates into consideration:
Task
Main tasks Date
No.
The projected cost of the contract is expected to be within the range of £XXXX to £XXXX
including VAT.
• Fixed Price
The surveyor shall submit a fixed price. Each price shall be deemed to include, inter
alia, the following:-
o All travel and subsistence costs.
o All media and consumable costs.
o Field work and data processing.
o Traffic management and maintenance.
o Liaison with the landowners / tenants for access.
o Tender preparation costs.
o Weather downtime.
o All post, telephone, fax and e-mail costs.
o Controls established to OS GPS Network.
o Where reflector less total station is adopted the surveyor shall include for a
detailed visual inspection of the site to ensure all features (e.g. manholes,
gullies etc) are included. Any visual inspection and additional survey work
shall be deemed to adopt a safe system of work as noted above.
• The tender price should be made up based on the form of data being collected as
follows:
o Channel survey
o Topographical survey
14 Project Management
The appointed contractor will be responsible for taking and distribution of minutes and
agenda for all meetings and telecom’s.
Any compensation claim due to change in scope needs to be provided and agreed in writing
before commencing work.
Requests for changes to key project staff must be provided in writing for approval.
All copyright and Intellectual Property Rights (IPR) will be transferred to Responsible
Authority Name in accordance with the Terms and Conditions.
16 Sustainability
17 Tender Submission
• Methodology statement
All tender submissions should cover the above requirements in a maximum of 10 pages.
Schedule 2
Tender Evaluation
Schedule 3
Tenderers are required to submit a firm price for the service detailed in Schedule 1 excluding
VAT. All costs appropriate to the proposal must be included or summarised here. Costs
which appear elsewhere in the proposal but which are not summarised here will be
presumed to have been waived.
Price £
Activity Person Hours (excl. VAT)
Tenderers must also provide a breakdown of the staff involved in this contract.
Hours
Personnel Activity Hourly Rate
Input
£
£
£
£
£
£
Key
1. Project Details
Project Name
Report(s) being reviewed
Date and version of report
Author and Company
Reviewer
Date of review
Review Status
2. Concept Review
3. Review of Data
4. Calibration Events
6. Catchment Descriptors
7. Estimation of QMED
9. Rainfall-runoff approaches
11. Results
12. Conclusion
E.1 General
Model file paths should be kept below 50 characters where possible, whilst ensuring
meaning or logical structure is not lost.
A logical and descriptive naming structure for models and scenarios should be adopted. File
and scenario names should include the following information where appropriate.
• River reach identifier e.g. Tay. For long rivers abbreviate the name.
• Version
• Return period
• Storm duration
• Scenario identifiers – D for defended, ND for undefended, S_N for sensitivity to
roughness, S_Q for sensitivity to flow. Climate change scenarios to be labelled with
the scenario run e.g. 2080H.
Eg. Tay_V1_10yrs_10hrs_D.ied
E.4 HECRAS
E.5 FloodModeller 14 1D
14
Formerly ISIS.
E.6 FloodModeller 2D
Runs .xml Model run files. There should be one of these per
scenario run.
GIS .shp .asc There should be a GIS folder containing all model GIS
etc. inputs. The exact files required will be specified in the
.xml file. The same GIS folder and files should be
referenced by multiple scenarios
Boundaries .ied Hydrological boundary conditions if these are not
contained in the .xml file.
Results .asc, .dat, The results folder name matches the .xml file name
and check .sup, .2Dm and is created in the Run directory. Check files have
files the extension .chk*.asc and should be provided for all
runs to enable checking. Model results are in .dat, .sup
and .2Dm format. There is one .dat file for each output
and one .sup and .2Dm file for each model run. All 3
components of the results files are required.
E.8 FloodModeller-TUFLOW
Files are to be included as in the ISIS1D and TUFLOW descriptions above.
For models which require names to be entered for model cross sections the industry
standard [XX][CHAINAGE][CHAR] node naming strategy should be adopted where:
XX is the river identifier. This is usually some abbreviation of the river name e.g. Tay or F for
the River Tay or River Forth. Use a separate identifier for each tributary in the model.
CHAINAGE is the chainage. The chainage should be 0 at the d/s end of a river, or at a
confluence. Chainage should be measured along the centerline of the river from the tidal
limit.
CHAR is an optional additional descriptor that can contain letter or numbers. This is usually
used for structures such as bridges e.g. BrUp – upstream bridge node, Wr1Dn –
downstream node of weir one. Try to be consistent within a model, but there are no hard
and fast rules as some software restricts node name length, typical names are given in
Table 15-1, and an example of node naming around a bridge in an ISIS 1D model is given in
Figure 15-1.
Tributary inflows should be named after the tributary e.g. Pow for the Pow Burn or Devon for
the River Devon.
H Bibliography
Apel, H., Aronica, G., Kreibich, H., & Thieken, A. (2009). Flood risk analyses – how detailed
do we need to be? . Natural Hazards, 79-98.