APPENDIX C: DATA PROCESSING AND ORGANIZATION

C1. Settings of Flood Scenarios The flooding scenario A1b is characterized by 3 aspects: Topography, Inlet location and initiation types. In the selected scenario for this study, topography is specified as type A: current situation, in which all remnants of existing dike elements and modern linear landscapes are kept as they are, shown as Fig. 1.

Fig. 1 Topography A: Current Situation1

There are overall 5 inlets locations specified, as shown in figure below. They are Weurt, Deest and Druten along river Waal, Overasselt and Batenburg along river Maas. Choice of inlets locations is mainly based on three principles: Locations are scattered along rivers from quite some distance so as to get distinctive variance between scenarios Locations are not too far downstream otherwise inlet position comes to be in low elevation that maximum volume of water inside the dike-ring area is not sufficient for the water of the river to influence. They are positioned in a way that no buildings directly locate behind the inlet.

Weurt is selected as the location analysed in this study because in 1805, a recorded dike breach really occurred here , as shown in the historical map Fig. 3.

Source: Alkema & Middelkoop, 2005

Fig. 2 Five Inlet Locations along River Waal and River Maas2

Fig. 3 Historical Map Showing Scour hole formed after the 1805 dike breach3

2 3

Source: D. Alkema, 2003. On the map, a plan for repair of the dike breach is plotted over the dike breach scour hole. Note that south is up. Source: Hesselink, A. W., et al. (2003).

Fig. 4 Width and Depth at the Breach Weurt4

Finally, the breach in the Waaldijk (dikes along river Waal) at Weurt is a reconstruction of the historical breach incident in 1805. In the morning of February 13, an accumulation of ice floes in river Waal deterred the flow of water and caused a rapid rising of river level, then at 5:00 AM, a major river dike broke and flushed away 190m-wide section of the dike . The breach profile is constructed based on Hesselink et al.s thesis data, shown in Fig. 4. It is assumed that the formation of the breach lasts for 3 hours after which the shape of breach no longer changes . C2. Organization of flood characteristics datasets in ArcGIS

Different from normal raster dataset, Raster Catalog can contain a pool of interrelated flooding datasets in a uniform data scheme. As shown in Fig. 5, each row in a Raster Catalog represents flood characteristics at specific time. As highlighted in Fig. 5, the most important properties, time can be easily manipulated in a classical relational database fashion.

Source: Alkema & Middelkoop, 2005.

Fig. 5 Snapshot of Data structure of Raster Catalog used for organizing water depth data

C3.

Specification of road attributes by road types

Tab. 1 Road Attributes Specification and Google Street View Images

Road Types

Total Length (km) 75.9

Lanes

Speed (km/h)

Sample | Street View5

highway

80

highway linking

23.9

40

truck

18.6

80

primary

81.3

60

primary linking

0.7

30

secondary

90.5

40

Source: Google Street View Screenshots.

secondary linking

0.0

20

tertiary

255.9

30

tertiary linking

0.1

15

unclassified

1115.8

30

C4. Organization of datasets about dynamic availability of road network and exits Road network data with different availability properties over time are stored in Geodatabase in two different forms: 1) independent time-sliced dataset which is used for efficient evacuation routing analysis, as shown in Fig. 6 and 2) aggregated temporal data that amalgamate all time-sliced datasets, as shown in Fig. 7. The second form is used for data visualization.

Fig. 6 Snapshot of Time-Sliced Network datasets

Fig. 7 Snapshot of Data structure of Dynamic Network Availability

Fig. 8 Snapshot of Data structure of Dynamic Exit Availability