- 12 Aug 2022
- 14 Minutes to read
- Print
How to setup my damage calculator depth damage curve data
- Updated on 12 Aug 2022
- 14 Minutes to read
- Print
Damage Calculator has been developed in collaboration with the Flood Hazard Research Centre (FHRC), who are part of the University of Middlesex, UK (https://www.mdx.ac.uk/our-research/centres/flood-hazard). The approaches in the tool follow FHRC’s 2013 publication: Flood and Coastal Erosion Risk Management: A Manual for Economic Appraisal more usually referred as the Multi-Coloured Manual (MCM). To support MCM approaches, FHRC publish an annual Handbook for Economic Appraisal (usually referred to as Multi-Coloured Handbook (MCH) and updates of property depth damage data referred to in the MCM. With the appropriate licence these data can be downloaded from the website; https://www.mcm-online.co.uk/ in a format that can be used directly in Damage Calculator.
The Damage Calculator tool must be associated to a set of depth damage curve data in order to perform any analyses. These data are a combination of the data files provided by FHRC as part of the MCM and a series of additional files provided as part of Flood Modeller. All data are text files with a comma separated (csv) format, which enables you to view or edit (in a text editor or MS Excel). Your data files should be set up in a single folder, ideally with no additional files or sub-folders present in the folder (although Damage Calculator may still be able to read the data even when extra files are present).
This section explains the content and format of each required and optional data file. This will enable you to define new data files using depth damage data from a source other than MCM or to view/edit existing files.
Damage Calculator expects each file specified here to have the column headers specified EXACTLY as specified here. The tool will not accept datasets with incorrectly defined column headers, missing columns or extra columns. If the tool encounters an invalid file it should report the fact (and then abort starting up).
MCM Depth Damage Curve Scenario.csv
This file is provided by Flood Hazard Research (FHRC). Dataset is part of the UK Multi-Coloured Manual (MCM). This file lists the scenarios for which depth damage data are provided, e.g. Short_NoW_storm, which represents a short duration storm event (<12hrs) with no warning. Other options to include in scenarios are contaminated water, saline water, wave impacts or sewerage. Note and example of this file (with just two property types included) is provided by Flood Modeller.
Required columns are:
CurveID – Numeric index for listed scenarios, i.e. 1, 2, 3, etc.
CurveName – Text describing the storm scenario. Note: FHRC use abbreviated terms, e.g. “Short_NoW_storm” represents a short duration storm event (<12hrs) with no warning.
Version – Year the data is valid for (i.e. numeric entry).
Duration_hours_indicative – storm duration in hours. MCM storms are usually 12, 24 or 504 hours long.
Duration_comments – text describing specified duration.
Warning – flag signifying if a warning is provided (flag = 1) or not provided (flag = 0).
Warning Lead Time – text describing lead time before warning issued, MCM storm data can be defined with no lead time, less than 8 hours (“<8h”) greater than 4 hours (“>4h”) or greater than 8 hours (“>8h”).
Storm – flag set to 0 or 1. If set to 1 then data represents standard fluvial flooding.
Sewage - flag set to 0 or 1. If set to 1 then data represents flooding containing sewage.
Contaminated - flag set to 0 or 1. If set to 1 then data represents flooding containing contaminated water.
Saline - flag set to 0 or 1. If set to 1 then data represents flooding of saline water.
Waves - flag set to 0 or 1. If set to 1 then data represents flooding including effect of waves (overtopping).
The columns representing properties of flooding are used together with the curve name field in the Damage Calculator interface to help you select the appropriate data for your analysis. They appear in the dropdown lists of available depth damage datasets to provide complete descriptions of each dataset, as shown below:
In addition, the version of the data files is displayed in the interface (on the Settings tab).
The curve IDs are used within the analysis process to look up the associated depth damage values within the other files within the data folder (see below for descriptions of these).
RP_DD_curves.csv
This file is provided by FHRC as part of MCM. This file lists the depth damage relationships for different types of residential properties. Curves are provided for some or all defined storm scenarios. Note an example of this file (with just two property types included) is provided by Flood Modeller.
Required columns are:
CurveID – Numeric index cross referencing to scenarios listed in “MCM Depth Damage Curve Scenario.csv”, i.e. 1, 2, 3, etc.
Scenario - Text describing the storm scenario. The same text appears in “MCM Depth Damage Curve Scenario.csv” for the selected “CurveID”. Note: FHRC use abbreviated terms for their scenarios, e.g. "Short_NoW_storm" represents a short duration storm event (<12hrs) with no warning.
Year - Year the data is valid for (i.e. numeric entry). This references to the “Version” field in “MCM Depth Damage Curve Scenario.csv”.
MCM_code – numeric entry that defines the residential property type the data entry applies to. This code is cross referenced to residential property descriptions in “MCMCode.csv”.
Depth – numeric entry. Assumed to be in same units as the depth grids used in your Damage Calculator analyses, i.e. no conversions performed in tool (for MCM, depths specified in metres).
Domestic_CleanUp – numeric entry specifying domestic clean-up cost at specified flood depth. This value is provided for information only and is not used by the Damage Calculator tool.
Household_Inventory_Damage – numeric entry specifying household inventory damage value at specified flood depth. This value is provided for information only and is not used by the Damage Calculator tool.
Building_Fabric_Damage – numeric entry specifying building fabric damage value at specified flood depth. This value is provided for information only and is not used by the Damage Calculator tool.
Total_Damage – numeric entry specifying overall damage at specified flood depth.
Total_Damage_Square_Metre – numeric entry specifying overall damage at specified flood depth converted to a per square metre value (could equally be a per unit area value). This field will be utilised by Damage Calculator, combining with property areas (or default areas – specified in another file, see below) to calculate total damages for each flooded property.
NRP_DD_curves.csv
This file is provided by FHRC as part of MCM. This file lists the depth damage relationships for different types of non-residential properties. Curves are provided for some or all defined storm scenarios. Note an example of this file (with just two property types included) is provided by Flood Modeller.
Required columns are:
CurveID – Numeric index cross referencing to scenarios listed in “MCM Depth Damage Curve Scenario.csv”, i.e. 1, 2, 3, etc.
Scenario - Text describing the storm scenario. The same text appears in “MCM Depth Damage Curve Scenario.csv” for the selected “CurveID”. Note: FHRC use abbreviated terms for their scenarios, e.g. "Short_NoW_storm" represents a short duration storm event (<12hrs) with no warning.
Year - Year the data is valid for (i.e. numeric entry). This references to the “Version” field in “MCM Depth Damage Curve Scenario.csv”.
Cellar – text entry signifying whether cellar damages are included within data. Entry can be “Cellar” or “NoCellar”.
Band – text entry set to “Indicative” by default.
MCM_code – numeric entry that defines the non-residential property type the data entry applies to. This code is cross referenced to non-residential property descriptions in “MCMCode.csv”.
Depth – numeric entry. Assumed to be in same units as the depth grids used in your Damage Calculator analyses, i.e. no conversions performed in tool (for MCM, depths specified in metres).
Total_Damage_Square_Metre - numeric entry specifying overall damage at specified flood depth as a per square metre value (could equally be a per unit area value). This field will be utilised by Damage Calculator, combining with property areas (or default areas – specified in another file, see below) to calculate total damages for each flooded property.
MCMCode.csv
This file is provided by Flood Modeller (in the FloodModeller_ExampleData zip file included in the GUI installation folder – look in folder; “MCM example damage data folder”). This file lists the possible housing types that may be in your MCM depth damage curve files, with a cross reference to MCM code.
Required columns are:
- MCMCode – numeric entry that lists MCM code values for all possible residential and non-residential property types. This code is cross referenced to residential and non-residential depth damage curve data in “RP_DD_curves.csv” and “NRP_DD_curves.csv”.
- LandUse – text description of property type corresponding to each MCM code specified.
Both of these data will be displayed in the Damage Calculator tool on the Depth/Damage Curves tab, enabling you to select a property type (for a user selected residential or non-residential curve set) and review the associated depth damage data (in the adjacent chart and table):
DefaultFloorArea.csv
File is provided by Flood Modeller (in the FloodModeller_ExampleData zip file included in the GUI installation folder – look in folder; “MCM example damage data folder”). This file provides a default floor area for each property type (residential and non-residential). These data can be used to calculate damages for properties with no floor area specified in the property file. Note using this file is an option, alternatively you can opt to consider zero damage for properties with no floor area specified.
Required columns are:
strMCMCode – numeric entry that defines the residential or non-residential property type the data entry applies to. This code is cross referenced to property descriptions in “MCMCode.csv”.
dblMeanArea – numeric entry that represents the area value to be used by Damage Calculator for properties that have no total floor area specified (in the property data file used in your analysis). Damage Calculator will use the appropriate area value with the calculated damage per square metre for a property to calculate the total damage figure for the property.
Occupancy.csv
File is provided by Flood Modeller (in the FloodModeller_ExampleData zip file included in the GUI installation folder – look in folder; “MCM example damage data folder”). This file provides average occupancy figures for each property type. These data are utilised in the optional risk to life calculation within Damage Calculator (note this option also requires additional input data to be prepared, i.e. flood inundation data and flood hazard data).
Required columns are:
strMCMCode - numeric entry that defines the residential or non-residential property type the data entry applies to. This code is cross referenced to property descriptions in “MCMCode.csv”.
blnPerBuilding – this is a TRUE / FALSE entry. It signifies whether the associated occupancy rate for the building type represents a total number of people (entry = “TRUE”) or an area per person value (entry = “FALSE”). For the latter, the number of people in a property is then calculated by dividing the specified property floor area by the occupancy rate.
dblOccupancyRate – this is a numeric entry that represents either the discrete number of people assumed in the associated building type or an area per person value (depends on blnPerBuilding value above). If the value is the latter, then the number of people expected in a property is calculated by dividing the specified property floor area by the occupancy rate. Note the area units assumed here should be the same as those used for property floor area data, which might not always be m2 (i.e. no unit conversions are performed in the tool).
dblOccupancyFactor – the occupancy factor is a numeric entry representing a percentage value. This factors the calculated people per property values. Accounts for not all occupants being in all properties at the time of flooding.
PLPMeasures.csv
An example of this dataset is provided by Flood Modeller. This file defines one or multiple property level protection measures. The description of the measure is listed here and the associated adjustment factors (in the PLPfactors file) are referenced. If you have these data in your data folder you have the option of calculating the effect of property level protection on damages.
Required columns are:
- numPLPMeasure – numeric entry providing an index for each measure defined. This is used to cross reference to property level protection factors listed in the “PLPFactors.csv” file.
- strPLPMeasure – text entry providing a (descriptive) name for each specified property level protection measure listed. The entries in this field will be listed in the Property Level Protection tab of the Damage Calculator interface, enabling you to select a measure to include in your analysis.
- Comments – text entry for user to optional provide additional descriptions of each specified measure. Field is required in csv file but entries can be left blank.
PLPFactor.csv
An example of this dataset is provided by Flood Modeller. This file defines adjustment factors to be applied to depth damage data for one or multiple property level protection measures. The same factors will be applied to all property types if you choose to analyse the effect on damages of a particular property protection measure (if you have these data in your data folder).
Required columns are:
numPLPMeasure - numeric entry specifying the measure index each data entry is part of, as listed in “PLPMeasures.csv”.
numDepth – numeric entry. Assumed to be in same units as the depth grids used in your Damage Calculator analyses, i.e. no conversions performed in tool (for MCM, depths specified in metres).
numFactor – numeric entry. This is the factor to be applied at the associated depth to adjust the damage to account for the selected property protection measure. The impact of this factor can be seen in the Damage Calculator tool prior to starting a calculation. After switching on property level protection (by ticking check box on Calculation Information tab), two curves will be shown for each highlighted property type on the Depth / Damage Curves tab. One will be the original depth damage dataset and one will be the adjusted curve to account for the selected property level protection measure (selected in the Property Level Protection tab).
Note: All damage figures have no associated currency data specified. The Damage Calculator contains no functionality to carry out currency conversions, so the damages calculated will assume the same currency as the specified depth damage datasets.
If you are running Damage Calculator for the first time it is likely it won’t have a location stored for your depth damage curves data. In this case the tool will prompt you to specify a folder which should contain ONLY the required data files defining depth damage relationships for different property types plus some associated data.
EvacuationCosts.csv
An example of this dataset is provided by Flood Modeller. The table needs to provide evacuation costs corresponding to all possible residential property types (within your analysis) and for all possible flood depths. Each evacuation cost is associated to a specified flood depth range.
Required columns are:
Max depth range in property > From / To - numeric entries specifying a flood depth range.
Property type – first row below this header lists available residential property types as separate column headers.
These types are all those available in the property type attribute of typical UK property data shapefiles. This list is currently:
Det – detached property
Sdet – semi-detached property
Terr – terraced property
Flat
Below each property type numeric entries are required to specify the evacuation cost associated to each defined depth range.
During an analysis, the tool will cross reference the type of any residential property for which a flood depth is calculated with the types in this table. The tool then determines which depth range the calculated flood depth is within to ascertain the associated evacuation cost. The cost is assumed constant for any flood depth occurring within a range, i.e. “from” value < flood depth <= “To” value.
Note: The example evacuation cost data provided with Flood Modeller is from the 2018 Multi-Coloured Manual (MCM). It is recommended that you check MCM online for any updates if you are including evacuation costs in your analyses.
MentalHealthCosts.csv
An example of this dataset is provided by Flood Modeller. The table needs to provide mental health costs corresponding to all possible residential property types (within your analysis) and for all possible flood depths. Each mental health cost is associated to a specified flood depth range.
Required columns are:
Max depth range in property > From / To - numeric entries specifying a flood depth range.
Property type – first row below this header lists available residential property types as separate column headers. These types are all those available in the property type attribute of typical UK property data shapefiles. This list is currently:
Det – detached property
Sdet – semi-detached property
Terr – terraced property
Flat
Below each property type numeric entries are required to specify the mental health cost associated to each defined depth range.
During an analysis, the tool will cross reference the type of any residential property for which a flood depth is calculated with the types in this table. The tool then determines which depth range the calculated flood depth is within to ascertain the associated mental health cost. The cost is assumed constant for any flood depth occurring within a range, i.e. “from” value < flood depth <= “To” value.
Note: The values in the example provided are from the UK environment agency document ‘Advice for Flood and Coastal Erosion Risk Management Authorities – Mental Health Costs of Flooding and Erosion’ (published 17/04/2020). It is recommended that the Environment Agency website is checked for updates before undertaking an analysis.