The vulnerability mapping represents the relationship between hazards and impacts and, if applicable, risk reduction measures. It is typically based on the vulnerability relationships in the CVI library developed in task 2.2, but any other source, e.g. from literature or expert opinion, can be used as well.
The mapping defines the state of the impact variable conditional on a combination of states of its parents. Such a mapping for an impact variable can be best made in a spreadsheet following the steps 1-4.
- Create a row column each parent node in the same order in which they have been specified as "parents" in the Cnodes.json
- Write out all combinations of parent states. The states must change in the order in which they have been specified in their respective "bins" fields. Moreover, the states of the last parent must change fastest, then the ones of the second last, and so on until the first parent, whose states must change slowest.
- Indicate for each combination of parent nodes in which state the impact variable of interest should be in terms of its state index
- Copy the state indexes as a 1D array into the field "mapping" of that impact variable in the vulnerabilties.json files
Below are two examples with from the demoBN. Refer to the Cnodes.json file to verify the order of parent nodes, and to the Hnodes.json file, Rnodes.json file and Mnodes.json file for the order of states.
Example 1: Relative damage to residential buildings
In the demoBN relative damage to houses is influenced by the max. inundation depth at the house as well as the effective implementation of the measure "Protect buildings with sandbags":
The vulnerability mapping is based on the flood damage curve for Belgium in the CVI library. Additionally the assumption has been made that sandbags can withstand a flood depth of 50cm, which means that depths less than 50cm do not lead to damage, because the building itself is kept dry, while depth higher than 50cm lead to the same damage as before, because the bags overflow. The node "Implementation" does not need to be taken into account. Its influence is fully specified by the "effectiveness" in the Mnodes.json file. In other words full effectiveness can be assumed when determining the mapping.
The mapping [1,1,3,4,1,2,3,4] (cf. the vulnerabilities.json file) can be obtained from the following table:
| State of "Sandbags" | State of "I_ResBuildings" | State Index of "RelDamage_ResBuildings" |
| Yes | [0, 0.01] | 1 |
| Yes | [0.01, 0.5] | 1 |
| Yes | [0.5,1] | 3 |
| Yes | [1,2] | 4 |
| No | [0, 0.01] | 1 |
| No | [0.01, 0.5] | 2 |
| No | [0.5,1] | 3 |
| No | [1,2] | 4 |
Example 2: Risk to Life
Risk to Life is influenced by the max. flux people are experiences, the distribution of people and the measure evacuation being in place or not, see below illustration.
This mapping is based on the risk to life matrix for the UK from the CVI library. The assumption is made that Area1 and Area2 have low vulnerability, Area3 has medium vulnerability and Area4 has high vulnerability.
The mapping [1,2,2,3,3,5,1,1,1,1,1,1,1,2,2,3,3,5,1,1,1,1,1,1,1,2,3,3,4,5,1,1,1,1,1,1,1,2,3,4,5,5,1,1,1,1,1,1] can be obtained from
| State of "People" | State of "Evacutation" | State of "v_People" | State index of RiskToLife_People |
| Area1 | No | [0,0.01] | 1 |
| Area1 | No | [0.01,0.25] | 2 |
| Area1 | No | [0.25,0.5] | 2 |
| Area1 | No | [0.5,1.1] | 3 |
| Area1 | No | [1.1,7] | 3 |
| Area1 | No | [7,10] | 5 |
| Area1 | Yes | [0,0.01] | 1 |
| Area1 | Yes | [0.01,0.25] | 1 |
| Area1 | Yes | [0.25,0.5] | 1 |
| Area1 | Yes | [0.5,1.1] | 1 |
| Area1 | Yes | [1.1,7] | 1 |
| Area1 | Yes | [7,10] | 1 |
| Area2 | No | [0,0.01] | 1 |
| Area2 | No | [0.01,0.25] | 2 |
| Area2 | No | [0.25,0.5] | 2 |
| Area2 | No | [0.5,1.1] | 3 |
| Area2 | No | [1.1,7] | 3 |
| Area2 | No | [7,10] | 5 |
| Area2 | Yes | [0,0.01] | 1 |
| Area2 | Yes | [0.01,0.25] | 1 |
| Area2 | Yes | [0.25,0.5] | 1 |
| Area2 | Yes | [0.5,1.1] | 1 |
| Area2 | Yes | [1.1,7] | 1 |
| Area2 | Yes | [7,10] | 1 |
| Area3 | No | [0,0.01] | 1 |
| Area3 | No | [0.01,0.25] | 2 |
| Area3 | No | [0.25,0.5] | 3 |
| Area3 | No | [0.5,1.1] | 3 |
| Area3 | No | [1.1,7] | 4 |
| Area3 | No | [7,10] | 5 |
| Area3 | Yes | [0,0.01] | 1 |
| Area3 | Yes | [0.01,0.25] | 1 |
| Area3 | Yes | [0.25,0.5] | 1 |
| Area3 | Yes | [0.5,1.1] | 1 |
| Area3 | Yes | [1.1,7] | 1 |
| Area3 | Yes | [7,10] | 1 |
| Area4 | No | [0,0.01] | 1 |
| Area4 | No | [0.01,0.25] | 2 |
| Area4 | No | [0.25,0.5] | 3 |
| Area4 | No | [0.5,1.1] | 4 |
| Area4 | No | [1.1,7] | 5 |
| Area4 | No | [7,10] | 5 |
| Area4 | Yes | [0,0.01] | 1 |
| Area4 | Yes | [0.01,0.25] | 1 |
| Area4 | Yes | [0.25,0.5] | 1 |
| Area4 | Yes | [0.5,1.1] | 1 |
| Area4 | Yes | [1.1,7] | 1 |
| Area4 | Yes | [7,10] | 1 |
