floodareahpc-desktop · arcmap the license file needs to be specified in the floodarea toolbar. you...

FloodAreaHPC-Desktop

ArcGIS- Extension for calculating flooded areas

USER MANUAL Version 10.3 – January 2017

Content -ii-

Version 10.3 – January 2017

Content Preface .................................................................................................................. 1 What’s new? ......................................................................................................... 2

10.1 ............................................................................................................................. 2 10.3 ............................................................................................................................. 2

What FloodArea Can Do For You .......................................................................... 3 Installing and Loading FloodArea ......................................................................... 4

System Requirements ................................................................................................. 4 Installation .................................................................................................................. 4 Demo data and demo ArcMap project ....................................................................... 4 Activating the FloodArea toolbar ................................................................................ 4 Activating your license ................................................................................................ 5

Using FloodArea .................................................................................................10 The FloodArea Main Menu ....................................................................................... 10 Available memory ..................................................................................................... 10 Calculate flooded areas (inundation zones) .............................................................. 11

Preconditions .................................................................................................................................... 11 Running a simulation ......................................................................................................................... 12 Calculation variants ........................................................................................................................... 12 Additional settings ............................................................................................................................ 25 Simulation pre-processing and processing ........................................................................................ 27 Post-Processing ................................................................................................................................. 28

Display simulation info / Continue simulation .......................................................... 28 Create animation ...................................................................................................... 29

Generation of JPEG images and animations in FloodArea ................................................................. 30 Practice for the design of FloodArea results ...................................................................................... 32

Unify legend .............................................................................................................. 33 Summarize raster values ........................................................................................... 34 Create shape of flow direction .................................................................................. 34 Choose language ....................................................................................................... 35 FloodArea License ..................................................................................................... 36 Info ............................................................................................................................ 36

FloodArea Toolbox .............................................................................................38 Background ............................................................................................................... 38 Installation ................................................................................................................ 38 64bit-Version ............................................................................................................. 38 Starting FloodArea .................................................................................................... 39 Additional parameters .............................................................................................. 40 Calculate Discharge ................................................................................................... 42 Hydrofiles erstellen Generate Hydrofiles .................................................................. 44

Command line ....................................................................................................46 Notice ........................................................................................................................ 47

Metadata management......................................................................................47 Calculation Method ............................................................................................48

Volume Budget ......................................................................................................... 51 Dam Failure ............................................................................................................... 51 Consideration of Model Edges .................................................................................. 53

Application Examples .........................................................................................54 Delineation of Flooded Areas Based Upon Flood Marks........................................... 54 Dam Failure Scenarios ............................................................................................... 54 Controlled Outlet of Flood Control Basins ................................................................ 54 Limitations................................................................................................................. 54

Content -ii-

Version 10.3 – January 2017

Demo Version and Demo Data ...........................................................................55 Notice ........................................................................................................................ 55 Data ........................................................................................................................... 55

Publications on FloodArea ..................................................................................57 Support ...............................................................................................................59 License Agreement .............................................................................................60

Copyright © geomer GmbH / RUIZ RODRIGUEZ+ZEISLER+BLANK, GbR, 2001-2015 ESRI, ArcGIS, SpatialAnalyst are registered trademarks of Environmental Systems Research Institute Inc., Windows 7 is a registered trademarks of Microsoft Corporation.

Preface / 10.1

Version 10.3 – January 2017 1

Preface

Floods are natural processes. Urbanization and increasing population density as well as a concentration of economic values in flood prone areas have increased the risks in many regions. Natural flood plains all over the world are being settled or used for industrial purposes. Perception of the flood hazard and the associated risks in many cases is low, if not inexistent, particularly in such areas considered to be safe, e.g. behind dams or levees.

New spatial planning approaches, though, try to cope with these developments and create suitable flood protection concepts. In this process, the delineation of flood prone areas is a very important first step. Additional information in this delineation process is achieved by the calculation of water levels at any given point at different times during a flood event. Such information delivers very important basic data for the determination of the risk potential. In addition the possibility to simulate the temporal dynamics of the flood event produces important information for disaster management plans.

FloodArea HPC-Desktop enables the user to do both types of analysis. This manual explains in detail the application of the software. Relevant examples are being given. The particularities of the computational algorithms are also explained in detail.

FloodArea HPC-Desktop is an ArcGIS extension, which is completely integrated in the graphical user interface of ArcGIS desktop, utilizing Spatial Analyst

functionality. No details of ArcGIS or Spatial Analyst are explained here. The user is assumed to be familiar with the use of ArcGIS in general and ArcMap and Spatial Analyst in particular. Reference is given in the respective manuals or via online help.

FloodArea HPC-Desktop is a joint product of geomer GmbH, Heidelberg, Germany, and Ingenieurgemeinschaft Ruiz Rodriguez + Zeisler +Blank, Wiesbaden, Germany.

What’s new? / 10.1


What’s new?

Here, essential innovations involved in the update to new FloodArea versions can be retraced in a listing:

10.1 FloodArea for ArcGIS Desktop now runs on the very same High

Performance Computing engine as FloodArea HPC. Thus much larger areas can be analyzed.

The new version now is equipped with an extensive logging system. By that the identification of faulty entries or incorrect calculations is simplified for the user.

FloodArea for ArcGIS now allows all supported raster data sources as input.

Calculation outputs are stored in GeoTIFF format, also the BigTIFF variant is supported. Thereby there are no more constraints in naming.

Several license options are available, based on the number of cores used.

The demo version does no longer have any limitations in size. Any size of data can be used with the demo version. However, the results will be watermarked.

The toolbox version of FloodArea can now be calculated with 64bit. By this, computable sizes of area are practically unlimited.

10.3 The graphical user interface of FloodArea for ArcGIS is now additionally

available in French, Italian and Chinese.

An improved handling of units has been introduced with an automatic readout of the coordinate system and thereby also map units of the terrain model. Thus, only the specification of elevation units (for all rasters consistently) is required.

The Toolbox option also allows the use of 64bit calculations.

What FloodArea Can Do For You / 10.3


What FloodArea Can Do For You

The main purpose of FloodArea HPC-Desktop is the delineation of flooded (inundated) areas. Calculations are based upon

a drainage network raster with water levels assigned to it. Though the water levels can vary spatially (e.g. along a river stretch) they remain constant during the simulation process. The water levels can be changed, however, by modifying them between single model runs, or

one or more hydrographs at user definable coordinates, or

a rainstorm simulation over a wider area, specified by a possibly weighted raster.

Model results are stored as rasters at user defined intervals, providing the possi-bility to reproduce the temporal aspect of the flooding process. The values of the resulting rasters can be stored as absolute height levels or as values relative to the surface. If needed, the flow direction vectors can be output for each individual raster.

Additional parameters can be specified for a simulation run. Flow barriers (e.g. road embankments), which are not represented by the elevation model, can be included. Locations of dam failures can also be defined determining at which points flow barriers fail, making dike break scenarios possible.

To adapt the flow velocities to real world conditions, the user can specify roughness values.

Installing and Loading FloodArea / System Requirements


Installing and Loading FloodArea

System Requirements Minimum requirements are ArcGIS Version 10.x and the Spatial Analyst extension, a Windows 7 or higher operating system and 2 GB RAM. Recommended are at least 4 GB RAM and 50 GB free disk space.

The maximum raster size for FloodArea depends on the free memory. Increasing the virtual memory is not an option, since disk swapping will reduce processing speed tremendously.

Disk space requirements depend directly on the number of intermediate simula-tion rasters (stored as GeoTIFFs).

The region of the computer or user who is using the FloodAreaHPC-Desktop have to be set to English. This prevents point-comma problems especially with the use of ArcGIS version 10.4 or higher. FloodAreaHPC-Desktop is using decimal points.

Installation The Installation of FloodAreaHPC-Desktop will be accomplished by using the install-setup utility.

Administration privileges are required.

Demo data and demo ArcMap project The installation procedure will install an ArcMap document (mxd-file) with associated data and also this manual. These files will be copied to the user’s User-Folder during the first start of FloodArea. The path of the User-Folder depends on the operating system. Please read additional explanations in the chapter Demoversion und Demo Data, on p. 55.

Activating the FloodArea toolbar Having installed FloodAreaHPC-Desktop and activated the extension (Customize, Extensions), a new toolbar can be activated in the customize dialog by clicking Customize, Customize mode.

Installing and Loading FloodArea / Activating your license


Activating your license The software is delivered with the license key file faDemoLicense.xml. The file is located in the installation directory.

To be able to make full use of FloodArea you need to put the USB hardware license key (dongle) in a free USB port and activate your license.



Wibu-Systems Dongle (Source: http://www.wibu.com/de/codemeter/cmdongle.html)

As long as no valid license key is used or no hardware license key is in place FloodArea will work in demo mode only.

The hardware must not be removed or put in during a model run. ArcMap must be restarted after the hardware key has been put in.

The required license file handed out in xml-format can be copied to any location on your computer. In order to make full use of FloodArea functionalities in ArcMap the license file needs to be specified in the FloodArea toolbar. You will reach the respective dialog by selecting FloodArea licence in the FloodArea menu.

In the subsequent dialog you can enter or display the license code.



After specifying a valid license key file for FloodArea the full functionality is available.

Please note: When using the FloodArea toolbox the license file needs to be specified as the respective parameter (s. FloodArea Toolbox).

Verifying the activation of the license The success of the license activation can be checked via the dialogue FloodArea license (s. above).

If a valid license file has been specified, a license key is displayed.

Please make sure that the license file covers the required validity period.

In case the license is not activated in spite of the specification of a valid license file, please check the status of the dongle. An approach and potential problems in this respect are described subsequently.

Verifying the software protection device (dongle) Wether the dongle has been recognized may be retraced via the CodeMeter Control Center, which can be accessed using the respective icon in the info area of your desktop (s. figure below). In case the CodeMeter icon is not being displayed,



check for the Codemeter using the search functionality of the windows start menu. If available, the software can be accessed via the search results.

If no Codemeter software exists, the dongle installation has not been executed successfully.

Please note: In many cases problems arise during license activation, if unrestricted administrator rights are not given for the respective computer. Please keep this in mind for the installation of FloodArea and the activation of the dongle for the license activation.

Via the CodeMeter Control Center (s. above) you can access the WebAdministrator. Here, you’ll get information on the dongle status and license entries (s. below).

Using FloodArea / The FloodArea Main Menu


Using FloodArea

The FloodArea Main Menu After loading FloodArea, its toolbar can be used like any other toolbar. The available sub-menus are shown in the figure below.

Available memory Use this option to check whether or not enough memory is available for the simulation. Please note that the given value is an estimate only, since all other running programs and the operating system itself use the available memory in concurrent operations. The given percentage is based on the physical memory only. Try to avoid using virtual memory. In this dialog you can select from a list of raster data layers from the active data frame or load one from the disk. In the latter case, the selected layer will be added to the data frame.

New Toolbar

Using FloodArea / Calculate flooded areas (inundation zones)


Avoid simulation runs requiring memory above the available real memory. Using virtual memory may increase processing time tremendously.

Calculate flooded areas (inundation zones) This is the core option of FloodAreaHPC-Desktop . Use this menu for hydrodynamic modelling of inundation areas for given water levels (e.g. from a 1D model).

Preconditions For calculating inundation areas using FloodArea a minimum of two input raster layers are needed:

a digital elevation model and

a rasterized drainage network

or

point(s) with attached hydrograph(s)

or

a rainstorm distribution raster with attached hydrograph

Please keep all the input raster layers in the same coordinate system. By that you ensure the use of uniform map - or linear units. Calculations with rasters in a geographic coordinate system are not possible.

The format of the input raster layers have to be GeoTIFF (.tif). Furthermore, the uniform spatial resolution (i.e. cell width) of all raster layers is a premise for the calculation.



Elevation units are specified in the main dialog of FloodArea based on the digital elevation model for all input data (s. figure below).

Running a simulation Start the definition of the simulation by choosing the option Calculate flooded areas from the main dialog:

The geographic extent of a model run is defined by the digital elevation model specified in the drop down field Elevation model.

Calculation variants The user has a choice of three variations of simulation. They differ in the way the water is induced into the simulation model.

Using the option Water level (elevation of drainage network) assumes that flooding is initialized by the entire drainage network (meaning from all raster cells other than NoData). Water levels can vary spatially, but remain temporally constant during the simulation process.



If using the option Hydrograph (input by individual point locations) water enters the model at defined locations. This option makes a temporal variation (hydrograph) of water levels possible.

The third option, Rainstorm (input by a defined area), is very similar to the second one. The difference between the second and the third option is that waterlevels here are defined by a raster layer.

Press Cancel to abort the model run.

Water level (elevation of drainage network)

Using this model option requires at least the specification of the following layers:

a digital elevation model, which represents the surface upon which the flow process takes place, including its elevation units

a rasterized drainage network containing elevation values of water levels (above sea level or above surface)

Both raster layers can be selected from a list of available layers or loaded from disk.



In addition two fields for specifying elevation units and map units are available. Elevation units for the elevation models must be given. Elevation units for the drainage network are optional and necessary only if they differ from the elevation model’s elevation unit. They will be ignored in cases where a calculation is based on a constant flood level (e.g. 1.5 meter above surface).

The water level (flood level elevations) is represented by the values of the input drainage network raster layer (box A is checked).

If the water level (flood level elevations) is represented by the values of the input drainage network raster, a constant value (specified in field C) can be added. Boxes A and B must be checked for this method. Elevation units are the same as for the elevation model.

It is also possible to specify only a constant value. In this case cell values of the drainage raster will be ignored. In this case checkbox B must be checked, filed C must be empty and checkbox A must not be checked.

At least one of the checkboxes A and B must be activated!

For all options the water level elevations can represent relative values above the surface (option D, left), or absolute values, e.g. above sea level (option D, right).

Before actually starting the model run, the plausibility of the user input is being checked. For example, FloodArea checks for missing or wrong specifications in the various input fields. It also checks for alignment problems between input rasters. In case of problems, the user is given some information about possible erroneous input. If plausibility is ascertained the Continue-button is activated.

Additional optional raster layers can be taken into account by clicking on Show optional properties.

A

D

B C



Flow barriers: All raster cells other than 0 (zero) or NODATA are considered to be flow barriers. The model algorithm uses diagonal transfer between raster cells. Thus, in order to function as a true flow barrier, raster cells must be edge-connected. Rasters generated by ArcGIS rasterizing of line shape files meet this requirement. No heights of dams can be specified here. If these are available and to be used in the simulation, they must be part of the elevation model. Use the standard SpatialAnalyst functions to modify your elevation model accordingly.

Dam failure: All raster cells other than 0 (zero) or NODATA are considered and assigned higher priority than flow barriers. This means that at any given location (i.e. raster cell) where both flow barrier and dam failure are set, the dam failure raster is superior. You can use this option for the simulation of dam failures or levee breaches.

Roughness: A raster layer representing roughness values according to Manning. The values have to be given as kSt (= 1/n), in units of m1/3/s. For non-specified roughness coefficients FloodArea uses a default value of 25.

Modification: With this option it is possible to raise or lower the complete water level during the simulation process. The ASCII-file to be selected here has to have



the same format as the hydrographs used within the other options (see page 17). The values will always be interpreted as the difference to the original water level and must be given in centimeters (cm). The values between the data in the input file will be linearly interpolated. The water level defined in the raster drainage network will be lifted or lowered by the value defined for the actual time step. With this function you can simulate, for example, the passage of a flood wave within a bigger river and the effects on the connected retention areas.

This selection is not available when the option water level has been chosen in combination with the option hydrograph.

Hydrograph (input by point locations)

Using this option implies that input for a drainage network with associated water level data does not apply and can be ignored. Water is fed into the model through a hydrograph data file at one or more locations. The name of this data file can be entered directly or selected from a file dialog.

Path to hydrograph data file Ganglinien-Datei



The hydrograph data file is simply an ASCII text file that can be created with any text editor. It must have the extension “.txt” and must be organized according to the figure below.

0.00 20.1 5.6

0.05 22.8 5.7

0.17 25.2 5.8

0.33 24.3 5.9

0.50 25.3 5.9

0.67 26.2 5.8

0.83 23.9 5.7

1.00 24.8 5.5

The file has at least two columns, one holding the time (in decimal hours), the second and all others holding the inflow (in m³/s). The decimal sign must be a dot. Columns may be delimited by a space, a tab stop, a comma, a semicolon or a colon. No empty lines or inline comments are allowed. Comments, though, may be added as separate columns. But they should not contain any numbers.

If values are negative, the corresponding amount of water at that point will be interpreted as being taken out of the model. The algorithm does not comply with situations, where the negative value is higher than the amount of water currently available in that particular raster cell. If not enough water is available, the cell is being emptied and the remaining quantity ignored. Such assumptions may produce errors in the overall budget.

Time steps need not be regular. The program interpolates linearly between the specified time steps. If simulation time (see Additional settings) is reached before all hydrograph data are processed, the model stops.

The hydrographs input locations are specified by input coordinates. The hydrographs are assigned to the input coordinates in the same order as the columns of the coordinate input file. Note that the numbering of the coordinates starts with 0 (zero). If either the column or the input coordinate is missing, the corresponding input will be neglected.

The input coordinates at which water is fed to the model are specified either by digitizing new locations (option A) or by loading a previously created coordinate

1. Column: Time in hours

2. and further Columns: Discharge in m³/sec

To separate the columns the following characters are admitted: empty space, tab, comma, semicolon or colon

decimal separator: point



file (option B). Loaded coordinate files can be modified using the digitizing tool. The filename extension of the coordinate file is .koo.

In case of using option A – “Create a new coordinate file”, a file name and

location for the new file must be given by clicking on the button .

In case of using option B – “Open an existing coordinates file for the hydrograph input” FloodArea will try to load the last loaded coordinate file. If there is no

coordinate file listed , the user can load one from the file dialog .

A maximum of 500 point locations can be specified in a coordinate file.

Using the checkbox the locations can be indicated on the map.

Option A

Option B



Using the buttons

add new

edit

delete

existing and new points can be managed.

With add new , new point locations can be digitized directly in the map layout, they will immediately show on the map.

The options edit and delete will only become active after selecting a coordinate from the list.

Having selected a point from the list, editing of existing points takes place directly on the map by clicking its new location. Deleting a point from the list must be confirmed.

For each location in the input coordinate file, one column with discharge data must be present in the hydrograph data file. The order of the locations in the list must be the same as that of the columns in the hydrograph data file. If there are fewer columns in the hydrograph data file than locations in the coordinate file, that location will be ignored, and vice-versa.

The coordinate file must be structured according to the following settings. When using existing coordinate files further specifications are possible.



The first two columns represent the input coordinates followed by a specification for the coordinate, which is supposed to be the target for extracted water. For the target coordinate the sequential number of the coordinate in the list is used, not the coordinate itself. Numeration starts from 0 (zero). The target cell of extracted water must always be listed subsequently to the coordinate of extraction as information in the file is handled sequentially.

If no water is being extracted in a certain cell or extracted water is to be removed from the system entirely, the target coordinate in this row must be specified by the value -1.

The last but one column contains the minimum water level in the respective cell. Indication must be given in cm (relative to surface). Other units must be converted equivalently. The specified minimum water level will be kept in the cell at all times. Extraction takes place only if this water level is exceeded.

The amount of inflowing or withdrawn water is specified by the hydrograph file. The first column contains the time in hours. The following columns contain the water quantities for the individual coordinates in the order in which they are listed in the coordinate file.

Example (see below): At coordinate 0 a constant quantity of 250 m³/s of water is induced. At coordinate 1 a constant quantity of 500 m³/s of water is extracted. Considering the use of the above displayed coordinate file, the extracted water of coordinate 1 is targeted to coordinate 3 and re-induced in this cell. If target cells are not specifically given by the user, the value will always be -1, so that extracted water will be taken out completely of the model.



The last column of the coordinate file contains a checkbox which specifies, wether the hydrograph file is to be used or a throughput (pump performance) shall be considered using a pump characteristic curve (see Special feature: pump characteristic curve). If the column contains a 0, the regular hydrograph file will be used. If it contains a 1, the value of the pump characteristic curve will be considered.

The hydrograph data file and the coordinate file must be specified in order to be able to continue the model run with the additional settings.

The optional properties are basically the same as for the option water level, with the exception of the modification file which is not relevant here.

Please note: the model stops either when the time specified in the dialog Additional settings has run out, or when the last record of the hydrograph data file has been processed, whatever comes first.

Special feature: pump characteristic curve

The pump characteristic curve is given as a data file named “floodarea.pkl” in the temp directory of preprocessed data for the simulation. The first column contains elevation differences in dm between the cell which water is taken from and the cell which water is fed into. This column only exists for better orientation during the generation process, the program itself ignores it. The feasible range lies between values of 0 and 100 (thus 0 to 10 m), negative values are set to 0 during the calculation process. For values higher than 100 (10 m), the same value as for 10 m is used.

The data file is structured as follows:



The first column contains the elevation difference in decimeter (dm). Every following column contains, if necessary, the characteristic values for the pump used at the respective coordinate. In this example only for coordinate 3 values are inscribed (Note: counting starts with 0).

The quantities actually withdrawn are saved in a data file with the ending „.pum“ (otherwise the name of the data file corresponds the name of the hydrograph data file). In this case, the first column contains time. The quantity withdrawn is listed in the following columns. Inflows are not displayed in this data file, so all columns contain negative values or 0. All of the maximum 50 possible input coordinates are listed, even if they are not used in the current calculation.

Referred to the example above this means, that water cannot be withdrawn at coordinate 1 up to the third time step (see figure below). Only then the water level exceeds the specified value of 50 cm as minimum water level. After that, water is withdrawn, but withdrawal never reaches the given value of 500 m³/s.

The output resolution of the time steps matches the temporal resolution of the input hydrograph. Hence for a resolution of one value per minute the input hydrograph has to be specified in one minute time steps.

Rainstorm (input by area)

This option is almost identical to the one described above, the most important difference being that the hydrograph is not given for one input coordinate but for an area specified by a raster layer. This area is defined by a raster layer. Thus, only one column in the input data file can be considered.

The format of the hydrograph data is the same as above. Values, however, must be given in units of mm/h.



Different from the option Hydrograph, instead of coordinates for input/output locations, a raster layer representing the area for the hydrograph data must be chosen. Raster cells containing the value “zero” (0) or “NODATA” are considered to be “dry” cells, i.e. cells without water input. All other values given will be multiplied with the value in the hydrograph data file allowing for a weighted input. If a weighted input is not desired, all values must be set to 1. No negative values should be used.

In general the two hydrograph options (punctual and areal input) are the same. When using the areal input with a raster containing only a single cell, the results of the simulation are the same compared to using the normal hydrograph option. However, before running the rainstorm option you have to consider the different input units. Pay attention to the fact that the conversion factor depends on the raster cell size. Here some examples:



An input of 1 m³/sec

at a cell size of: corresponds to an intensity of:

5 m * 5 m 144 000 mm/h 10 m * 10 m 36 000 mm/h 20 m * 20 m 9 000 mm/h

25 m * 25 m 5 760 mm/h

30 m * 30 m 4 000 mm/h

40 m * 40 m 2 250 mm/h

50 m * 50 m 1 440 mm/h 100 m * 100 m 360 mm/h

This conversion will be done automatically if Input hydrograph in m³/sec is switched on. In this case the amount of water described by the hydrograph file will be divided among all cells of the precipitation area raster. Values within the raster will be interpreted as weighting values, the total amount of water remains unchanged.

The optional settings are the same ones as for the option Hydrograph.

If the option Rainstorm is combined with the option Hydrograph, the hydrograph of the rainstorm option will be used and a text notice will become visible.



Additional settings All simulation methods will be controlled by additional settings. The dialog for these will be activated by clicking the continue button.

Output options

Use this dialog to specify a folder (field A) for the temporary data produced during the model run. Specify a folder for your output rasters (GeoTIFFs) in field B. The directory will be completed automatically by an additional folder named “output” where resulting rasters will be output. The model output rasters are named with a prefix (o) and a sequential number with four digits, i.e. the first raster will be named o0001.tif, the second o0002.tif, etc.. Please be aware that already existing rasters with identical names will be overwritten. Folders will be created if they do not exist already.

In option field C the model output values can be given in absolute elevation (in most cases this means above sea level) or it may indicate water depth above the surface. In any case the units will be the same as the units chosen for the elevation model.

The interval of the time steps (i.e. the interval for which intermediate rasters will be saved) can be chosen in field D. One time unit accounts for approximately one hour of time. This value is an estimate because the model cannot be calibrated.

A

B

C

D

E

F

G

H

I

J

K

L



The checkbox Output of flow direction (E) needs to be activated if you want to generate a shape file with the flow direction later on. Please note that this will generate three rasters instead of one for each output time step, so provide enough disk space if you intend to use this option.

The additional rasters will have the prefix “v” (velocity raster) and “d” (direction raster) in the output filename. They will also be placed in separate folders named “velocity” and “direction”.

Calculation options

Simulation period (field F) is the total simulation time in hours. If the model run is the continuation of a previous simulation, the simulation time will be extended by the given value.

The maximum exchange rate (field G) defines the maximum percentage of water volume present in the current raster cell to be distributed to the neighboring cells in one iterative step. If the given exchange rate is exceeded, the model decreases the internal iteration time step and by this also the exchange rate until the exchange rate will be below the given maximum.

As the value influences the time step the value has influence on the simulation speed. High values can result in wave instability, which will not stop the model but may produce undesirable results. Values between 1 and 5 % have proven to output best results. To determine the optimal value it is best to run some tests. If the resulting water surface is very smooth one may use a larger exchange rate. In flat areas with high flowing velocities (as for levee failures) usually values around 1% produce the best results. In steep areas values higher values can still produce good results. Larger exchange rates (a maximum of 10 % is possible) are useful only if the simulation time is to be reduced considerably, e.g. in sense of a preview. For that purpose a coarser resolution of rasters may serve additionally.

Metadata

In order to save information about the rasters produced by model runs, FloodArea makes use of the metadata concept of ArcGIS. Some of the metadata will be saved automatically (e.g. the simulation period), other information can be specified by the user. There is the possibility to insert an author name into the field Author (field H) and a Comment (field I).

Legend

In this section ArcMap-specific legend options for the output raster layers can be specified. NODATA values are set transparent by default. Choose between a classified or continuous smooth legend in option J and select a color ramp in L. If a classified legend is chosen, the number of classes can be given in field K.



The option Generate grouping will create a layer group of the model result rasters. The layer group name will be created from the name for their output raster followed by “Group”.

The option Calculate will start the simulation run. The input can be discarded using Cancel.

Simulation pre-processing and processing Prior to the actual simulation run a python script tool will be executed in order to prepare the data in a format suitable for the actual FloodArea processing core. The temporary rasters created during that step will be deleted after the simulation run.

After successful completion of the python script the FloodArea simulation run will start automatically. During the simulation run the user will see a window displaying information about the modeling progress.

Clicking the button Close window and quit the simulation during the simulation run aborts the calculation process after an additional confirmation has been requested.

Using FloodArea / Display simulation info / Continue simulation


Post-Processing After finishing the simulation run the created intermediate rasters will be deleted and the resulting rasters will be loaded to the active data frame.

Display simulation info / Continue simulation With this dialog you can display information about previous model runs or con-tinue a previous simulation run. The information is stored in the metadata of each model result raster.

The information is shown either for a raster layer present in the active view or for a raster stored on disk.

In the input section the specifications made for producing the rasters will be displayed. In the output section specifications made in the additional setting (see above) are shown.

A Yes means that a specific option was set, if a button was deactivated the info displays a No. Not all buttons are listed here, but there status can be derived from the given information.

In case of a continued simulation, the previously simulated time period represented by the continue raster (see additional settings) is interpreted as part of the specified simulation duration.

For example: As continue raster an output raster is used that was generated during a simulation at the time step of 2 h. The duration of the simulation is specified with 6 h. The simulation will then be continued from the continue raster and the respective time step of the simulation. Thus, the remaining 4 hours will be simulated.

Using FloodArea / Create animation


This is relevant particularly for the use of hydrographs in the calculation. When a hydrograph file is used for continuing a simulation, the software itself searches for the correct time step (i. e. the corresponding row in the hydrograph file), in order to continue the calculation from there. The simulation duration specified in additional settings, hence, is to be specified as total duration of the simulation.

The button load settings will read the specifications made for creating the continue raster from its metadata and write them to the dialog of the current calculation. Otherwise the settings of the last calculation run or already specified settings will be used. However, the additional settings of a simulation, e. g. legend settings and saving intervall, will be automatically adapted to the specified continue raster. The simulation parameters can be changed to continue a simulation with different settings if desired.

Create animation Using this option, a good visualization of model simulations can be achieved. A series of JPG images and an additional animation in AVI format can be produced with FloodArea.



Generation of JPEG images and animations in FloodArea

Raster layers to be included in an animation are managed in the list of selected layers (A2) to which layers from the list of available layers (A1) can be added (B). Similarly layers can be removed from the list. Selection or removal of all layers is possible by using buttons C1 and C2.

In the right list it is possible to modify the order in which the images will be

created. Modify the list with the up and down buttons or reverse the

list with . Multiple selections are possible in both lists by pressing the Shift- or Ctrl-Key.

The list of selected layers (A2) should only contain FloodArea layers. Other layers in the data frame will be displayed according to their visibility status in the data frame automatically. Thus, if you want a particular map background, switch the layers to be included on, those not to be displayed off.

A1

B

C1

D

E

F

H

A2

G

C2



The list of FloodArea layers appears in reversed order when compared to ArcMap layer ordering. The reason for that is, that for creating the animation the last entry in the list has to be exported as the last image.

Specify JPG quality, resolution and AVI speed (frames per second) in fields D. In field E the output name and directory for the images and movies can be defined.

With button F the option to include the simulation time of each individual raster layer in the image or movie is given. The time will be read from the metadata associated with each raster. If a movie is to be produced, this option will generate the effect of a running clock.

Pressing button G will start the creation of JPG images without producing an avi- movie. The number of generated images corresponds to the number of result rasters added to the list of selected layers.

Pressing button H is necessary for starting the creation of an animated movie. It can only be activated if the jpg images already exist. Various compression options (codecs) can be chosen in the following dialog.

Use your favorite video player software for showing the animated simulation.

H

G

F



Practice for the design of FloodArea results For the presentation of results of FloodArea simulations in form of an animation it is recommended to create the desired layout in the layout view of ArcMap. The demo ArcMap project, which is delivered with the installation of FloodArea, contains an exemplary layout, which may be used for the generation of fullHD animations. Subsequently a best practice for the generation of animations described. Specific settings need to be adapted individually to the respective conditions and requirements of a presentation (e. g. screen format).

Page and Print Setup

The format of the JPEG images to be generated is adopted from the page size and format of the layout view. This can be adapted as required by right-clicking on the page layout in the Page and Print Setup (s. below). Several default page formats are available, e. g. DIN formats as are frequently used for map and poster prints. In the example given here and in the FloodArea demo project, the page sizes are set to meet fullHD-format of 1920 x 1080 pixels. With a default setting of 96 dpi (dots per inch) this corresponds to a page formatting of 20 x 11,25 I (inches). Please note, that a manipulation of the page size requires the adaptation of the dpi when generating JPEGs and viceversa. For the creation of movies in HD or other common formats the respective ratio of pixels to page size and dpi settings needs to be considered.

Using FloodArea / Unify legend


The map frame in the page layout can be formatted as favored. This should be full-page for full screen animations.

Show simulation time

When activating the display of simulation time for presented layers, the time will be automatically placed as an object at the lower left edge of the simulation extent, which is determined by the extent of the digital terrain model. The object can be adapted (e. g. font, color) or replaced within the map frame by closing the animation dialog (prior to generating the JPEG images).

Please note: All layers that are activated in the TOC (and visible in the data frame accordingly) will be permanently visible in the generated JPEGs. Thus, the layers selected in the FloodArea dialog for the creation of JPEGs/animations should be deactivated in the TOC in order to be displayed only at the respective time of the simulation during the frame sequence. Please make sure, however, that group layers containing simulation results used in the process need to be activated (single layers, again, remain deactivated).

Unify legend Use this option to assign an identical symbology legend to selected raster layers. This is especially useful when results of different simulation runs are to be compared or displayed.

First, in the left list (A) select the FloodArea layers (or other raster layers) which are supposed to have the same legend, then, in the right dropdown box (B), select

A

B

Using FloodArea / Summarize raster values


the raster layer with the desired symbology to be used as a template for all others.

With OK the selection is applied and all selected layers are displayed with the same legend.

Summarize raster values Using this function all values of the active raster theme are being summarized. Given the case that for instance the flooding depth is given and horizontal and vertical units are identical, the present total volume of water will be shown. Thus volume balancing can be realized.

Create shape of flow direction By using this menu option it is possible to generate a shape showing the direction of flow. To create such a shape you have to select two raster layers: one representing flow direction, and one representing discharge or velocity. These raster layers can be produced during the model run by checking the correspondent option in the additional settings. The raster layers can be loaded from disk if they are not already loaded in the current data frame.

If the arrows showing the direction are displayed too large or small, this may be caused by the missing or wrong unit input within the data frame properties.

Using FloodArea / Choose language


Please refer to your ArcMap manual. The arrows are set to the scale 1:1000 to correspond to the demo data.

For presenting the flow direction display of 16 directions is possible, according to the internal relation of raster cells in FloodArea. This will produce a relatively uniform picture of flow direction. It must be considered that flow directions are snapshots of a dynamic process. Particularly in terrain with rapidly changing flow direction it is best to output several situations.

Choose language FloodArea offers the possibility to choose the language used for the dialogs, the help texts and the messages displayed during the model run. Currently available

Using FloodArea / FloodArea License


are German, English, Spanish, and Hungarian. The default is German. Use OK to switch to the chosen language. You do not have to restart the program or reload the extension.

FloodArea License Here, the license used for the FloodArea extension is being displayed. Also the specification of a license-file can be entered or changed.

Info Use the Info button to display the version number and service addresses.

Using FloodArea / Info


FloodArea Toolbox / Background


FloodArea Toolbox

Background Some users of FloodArea requested an option to integrate the FloodArea functionality in a batch process. For computing sequences like different recurrence intervals or different dike failures it is helpful to set up a sequence of simulations and start those in batch mode without having to use the interactive user interface.

Installation The installation of the toolbox takes place while installing the FloodArea extension. The toolbox will be installed in the same folder (see page 4). Use the regular ArcGIS Desktop method for loading the Toolbox.

64bit-Version The toolbox is available as 64-bit-version. This toolbox, in the same way as the 32-bit-toolbox, needs to be loaded from the FloodArea installation folder for use in ArcMap. Please make sure „ArcGIS for Desktop Background Geoprocessing (64-Bit)“ is installed.

The processing of the 64-bit-version differs from the regular version inasmuch as it runs in the background. The dialog is accessible via the results window in ArcMap, which can be opened via the menu Geoprocessing, Results.

FloodArea Toolbox / Starting FloodArea


Starting FloodArea All possibilities available for script tools can be used to start a FloodArea simulation run. In the tool dialog all parameters as described for the regular interactive user dialog can be specified. Use the tool help for reference.

FloodArea Toolbox / Additional parameters


Additional parameters The use of the FloodArea toolbox provides the possibility to specify additional parameters, which cannot be manipulated when using the GUI.

Pagesize

The parameter pagesize determines the partitioning of the study area into individual calculation tiles on the different cores.

The pagesize may be specified optionally. A manipulation of the value is reasonable only, if a reduction of calculation time can be obtained. The usual range of values is between 128 and 512. The default value in FloodArea is set to 256.

Backup Intervall

During every FloodArea calculation backup files are written at regular intervalls which store the current status of the calculation. If a calculation has not been terminated correctly, e. g. due to abortion by the user, a rerun of the simulation can be started from the most recent backup. If a backup file exists in the specified temp directory from a previous calculation, the file will be readout automatically and used to start the new calculation.

FloodArea Toolbox / Additional parameters


For example: A simulation was terminated at 80 %, the last backup file was written at 75 % of the calculation. A subsequent calculation will be continued based on the backup file at 75 % of the calculation. This is possible only if the same temp directory is specified for the subsequent calculation.

The default value for the backup intervall is 3600 and interpreted as seconds in real time of calculation. Only the current, i. e. most recent, backup file is kept in the temporary data. Depending on the simulation to be run it can be reasonable to adapt the backup intervall. In this case the value (in s) may be specified in the toolbox.

Delete backup files

When starting a calculation FloodArea checks the specified temp directory for an existent backup file. By the default setting of the toolbox, backup files are deleted from the temp directory and the calculation is started from zero. If an existent backup file should be used for a simulation run, the corresponding checkbox needs to be deactivated.

Keep temporary data

Activating this checkbox prevents that temporary data is being deleted from the temp directory during the termination of a simulation. Temporary data, e. g., may be used as basis for subsequent calculations on the same data basis, which avoids repeated preprocessing.

Skip preprocessing

Activating this checkbox makes FloodArea skip the preprocessing of input data before starting the modelling. This is useful, e. g., if temporary data from previous simulations exist and the current simulation is based on the same input data.

When skipping preprocessing, please make sure that the temporary data exists in the specified temp directory.

Execute

If the FloodArea calculation with the given specifications is not to be executed, this checkbox should be deactivated. Then, only the preprocessing is carried out, i. e. temporary data is generated and stored in the respective temp directory.

FloodArea Toolbox / Calculate Discharge


Calculate Discharge By using the function Calculate discharge in the FloodArea Toolbox you can do discharge curve calculations using your simulation results. These calculations are necessary for determining e.g. the necessity of possible flood retention measures (volume, maximum discharge amount).

Input Line Shape

Shapefile containing lines, along whom runoff shall be determinated. When digitalizing the discharge lines, you should pay attention to get a clear flow direction without strong turbulences. To clearly assign the discharge to a line, the shapefile requests a column with a distinct ID for each line (Output Graphname Field).

FloodArea Toolbox / Calculate Discharge


Select Input Raster

Discharge Calculation requires the simulated inundation depths in the right chronological order. With the Tool demanding the related flow velocities and flow directions, the folders output, velocity and direction have to be stored on the same level, just as they are generated by FloodArea.

Output Line Shape

A new shapefile containing the discharge lines is generated. The Tool writes the discharge volume (m³/s) for each time step into a new column in the attribute table of this shapefile.

Output Graphes

If you specify a data path at output directory graphes, a graph indicating discharge over the simulation duration is generated for each discharge curve. Via the data in the attribute table of the output line shape you can also calculate further/additional values (e.g. average and maximum discharge, total amount/sum of discharge).

Additional Options

The temporary sample points, which are to be set along the discharge curves and by whom the tool extracts the data, can also be saved by indicating a path under Output Directory Debug SamplePoint. The shapefile containing the flow velocities

FloodArea Toolbox / Generate Hydrofiles


and flow direction as well as the water depth respectively the cross section of the sample pojnts is generated for each time step.

AngleCorrection changes the flow directions sytematicly and should be set to 0.

TimeStep corresponds to the time step, in whom the raster layers of the simulation have been written to the output (default = 1, if for each minute of the simulation a rasterfile has been generated).

Generate Hydrofiles If FloodArea is used with a hydrograph/discharge curve (see chapter calculation variants) and the function pump (see chapter special feature pump characteristic curve), a hydrofile (Format .txt) and a coordinate data (Format .koo) are needed, which contains the discharge curve respectively the pump amount. The FloodArea Toolbox enables the automatic creation of both datasets with a line shapefile via the tool GenerateHydrofiles. The exact functioning of the datasets (e.g. the meaning of the rows and the columns) can be extracted from the chapters calculation method hydrograph (input by point location) and special feature pump characteristic curve.

As input a line shapefile is needed. Each line links the extraction coordinate in direction of a target coordinate (the direction is thereby decisive, otherwise the pump pumps in the wrong direction!). In the field discharge value the amount of water (m³) is specified, which can be extracted at most at the one coordinate at each time step of the simulation.

In a column in the attribute table (here: target) it can be defined, if the target coordinate should be used, or if the water should just be pumped out of the simulation (‘pump into nowhere’ – without target coordinate). For example you

FloodArea Toolbox / Generate Hydrofiles


can set 1 for the use of a target coordinate and 0 for the use without a target coordinate. If a pump has to be written into the hydrofile at all (Field specifying usage), can be defined in an additional field (here: dt. Verklausung/eng. log jam)

In the field Hydrograph text file an already existing Hydrograph text file can optionally be specified, to which the pump data should be written (Optionally containing an alredy existing discharge curve). The coordinate file is automatically newly generated.

Command line / Generate Hydrofiles


Command line

The usual rules for using script tools apply.

The following structure may be used as template for batch script calls, where all parameters are set as variables first, and then FloodArea is called using the respective arguments.

set pythonexe="C:\Python27\ArcGISx6410.2\python.exe" :: path to "python.exe" (64 bit inst.) set floodpy="C:\Program Files (x86)\geomer GmbH\FloodArea\floodareaPython\start_floodarea.py" :: path to "start_floodarea.py" in the FloodArea program directory set tempdir="D:\simulation" :: path to the working directory of the FloodArea calculation set calcopt=5 :: calculation option set terrain="D:\input\dtm.tif" :: DTM set drain="D:\input\drain.tif" :: drainage/rainfall raster set reldrain=false :: drainage network in water depth set draininput=false :: use waterlevel of drainage raster set constadd=0.0 :: add contant height set hydrograph="D:\input\hydrograph.txt" :: hydrograph file set coords="D:\input\coordinates.koo" :: coordinate file set roughness="D:\input\roughness.tif" :: roughness raster set flowbarrier="D:\input\barrier.tif" :: flow barrier raster set breach="D:\input\breach.tif" :: breach raster set contraster="D:\simulation\output\o0001.tif" :: continue raster set conttime=3600 :: simulation time of continue raster set contrelativ=true :: continue raster contains water depth set duration=7200 :: duration of simulation (incl. simulation time of continue raster) set savingivl=3600 :: saving intervall set outswitch=3 :: output rasters (relative/absolute, with(out) flow direction and - velocity) set elevunit=1 :: elevation unit (conversion factor to m) set maxexch=0.5 :: max. exchange rate set pagesize=# :: internal tilesize (optional, default 256) set backup=1800 :: intervall for writing backup files (default 1h) set outputdir=%tempdir% :: output directory :: FloodArea working directory: generally called "fa" set licfile="D:\floodarea\license.xml" :: license file set delbackup=true :: delete backup files, if existent set keeptemp=true :: keep temporary data on finishing calculation set skipprepro=false :: skip preprocessing set execute=true :: execute calculation (otherwise preprocessing only)

%pythonexe% %floodpy% %tempdir% %calcopt% %terrain% %drain% %reldrain% %draininput% %constadd% %hydrograph% %coords% %roughness% %flowbarrier% %breach% %contraster% %conttime% %contrelativ% %duration% %savingivl% %outswitch% %elevunit% %maxexch% %pagesize% %backup% %outputdir% fa %licfile% %delbackup% %keeptemp% %skipprepro% %execute%

Metadata management / Notice


Notice The script version of FloodArea does not support all the different internal checks for plausibility as the normal desktop version, so the user needs to make sure that the input data are in the appropriate format. This comprises:

Hydrograph files must have the extension “.txt” and be structured following the specified instructions (see Hydrograph, p. 16).

Coordinate files, too, must have the appropriate structure and have the extension “.koo”.

As decimal delimiter “.” must always be used.

A valid License of FloodArea as well as ArcGIS 10 and the Spatial Analyst Extension need to be installed.

Metadata management

FloodArea makes use of the metadata concept of ArcGIS for storing information about utilized input data and produced model results. The XML definitions of the ISO standard have been extended with specific FloodArea elements.

Additional Metadata can be added by using standard tools in ArcCatalog without losing the elements generated by FloodArea.

Calculation Method / Notice


Calculation Method

The calculation of inundation areas is based upon a hydrodynamic approach. All eight neighbors of a raster cell are considered. The discharge volume to the neighboring cells is calculated using the Manning-Strickler formula.

2/13/2IrkV

hySt , with

hyr being the hydraulic radius and I the gradient.

For looking up appropriate values of St

k (roughness) reference tables can be

used, which renders the use of this formula more practicable compared to others. The quality of simulation results depends very much on using appropriate roughness values, since flow velocity is linearly related to roughness.

The flow depth during an iteration interval is taken from the difference between water level and maximum terrain elevation along the flow path.

baa

elevationelevationwaterlevelflowdepth ,max

The inclination and the direction of the water table are re-calculated in every iteration step and the steepest slope used as the inclination in the Manning-Strickler formula.

slope =

22

y

z

x

z

aspect =

x

z

y

za ,2tan

2

360270

This method may fail though in exceptional cases. In cases of linear elements with a width of just one raster cell the steepest slope may be perpendicular to the actual direction of flow. This applies if the inclination of the river bed (e.g. in a small ditch) is lower than the surrounding topography. In order to avoid such errors slope calculations are internally tested for their plausibility by comparing the elevation of the central raster cell to the elevation cell of the slope direction (aspect). If the difference is exceeding a certain threshold, inclination is re-calculated by comparing it with the lowest neighboring cell.



For illustration purposes examine the simplified elevation model shown below, depicting a ditch, which has an inclination lower than the surrounding terrain.

79.0 79.0 79.0 79.0 79.0 79.0

78.0 78.0 78.0 78.0 78.0 78.0

72.9 73.0 73.1 73.2 73.3 73.4

75.0 75.0 75.0 75.0 75.0 75.0

74.0 74.0 74.0 74.0 74.0 74.0

Slope direction derived by standard GIS Spatial Analyst. In the line of the ditch, slope values are wrong:

Slope direction values in the ditch, as derived by FloodArea:

Flow velocity as derived by the formula is multiplied by the flow cross section and the iteration time step in order to get the exchanged water volume between cells for the current iteration.

The Manning-Strickler formula is usually valid only for normal discharge, i. e. friction loss equals the gain in potential energy. In other cases calculated velocity values may be too high. To control this, the velocity values are checked for the threshold criterion

hgV (velocity of propagation of interference waves).

Velocity values that are too high will be reduced accordingly.



Together with the volume also the velocity vectors are passed for the next iteration. Mean flow velocity is defined as the arithmetic mean of the current velocity calculation and the vector addition. By this, sudden changes in flow behaviour will be minimized and inertia effects rendered in a simplified way.

The smallest iteration time step is adjusted dynamically. An important control criterion for this adjustment is the amount of water available. If the discharge rates become too large compared with the available volume, the iteration time step will be reduced. Only water level changes exceeding 1 mm are considered by that control mechanism. If the volumes exchanged between cells are very small, the algorithm will increase the iteration time step. This permanent optimization keeps processing time at a minimum.

c a lc u la t io n o f

Δ t s ta r t

Va k t

>

Vm a x

n o

y e sV m a x =

th re s h o ld


V


Δ w a te r le v e l

a c tu a l Δ t

e x te n s io n o f

Δ t

re d u c t io n o f

Δ t

Δ w l >

th re s h o ld

y e s

n o

Calculation Method / Volume Budget


Volume Budget At the end of each iteration the computed discharge volumes are shifted between cells, thus no volume can be lost.

To feed water to the model the three options

drainage network or (raster)

hydrograph (point)

rain storm (raster)

are available.

Using the first option, the algorithm sets all cells of the initializing network back to their original values after each iteration.

Using the second option the amount of water fed to the model is defined by the hydrograph. The amount of water taken out from the model is specified by selecting an output location.

Using the rain storm option „pours“ water over the terrain with a temporal distribution defined by a file. Spatially the distribution is defined by a raster representing the portion at each cell location. A value of 1 is equal to 100 %.

Dam Failure In terms of a dam failure raster not only potential physical obstacles must be „broken“, but also appropriate flow depth values must be calculated. The assumption made is, that the lowest elevation in the area covered by the dam failure raster (red area) is the local elevation minimum. If water reaches that area, the elevation at that location will be reduced to that local minimum. If during the simulation an even lower elevation is detected, it will be considered as the new local minimum and will be applied also to the already flooded cells.

Calculation Method / Dam Failure


The figures show, in a schematic way, characteristic intermediate phases during a dam failure simulation. From figure 2 onwards, a reduction of the elevation values takes place, being one cell “ahead” of the water level (shown as a horizontal plane for simplification). From figure 4 onwards, the new, even lower minimum is applied also to the cells processed before. Figure 5 shows the final status.

Calculation Method / Consideration of Model Edges


Consideration of Model Edges Considering the edges of a model area may cause a problem because no infor-mation is available for the area beyond the study area. FloodArea assumes a continuing gradient of the water surface beyond the edge of the model. Based upon this assumption, the water is being taken out of the model according to the discharge volumes calculated. A piling up at the model edges is not possible. If the model run is controlled by a hydrograph data file, the water volume taken out at the model edges is written to a separate file named “*.out”, “*” being the name of the hydrograph data file. The volume is specified in m³ since the last time step in the input hydrograph. If a high temporal resolution is desired, this needs to be accounted for in the hydrograph data file. No “*.out” file is created for the option “water level”. Since no defined water volume is fed into the model, an output hydrograph would be meaningless.

Application Examples / Delineation of Flooded Areas Based Upon Flood Marks


Application Examples

Delineation of Flooded Areas Based Upon Flood Marks Quite often historical floods are only registered at individual locations but not to their overall extent. The levels taken from these locations can be used to run FloodArea. The simulation model uses these points (or lines) as initializing cells to flood the surrounding terrain. Elevation differences are interpolated appropriately in terms of the hydraulic model.

Dam Failure Scenarios Two possible scenarios can be modeled. The first describes a complete failure of a dam or a section of a dam. Using the option Water level (elevation of drainage network) it is assumed, that the dam failure will not influence the water level of the main stream. The second possibility describes a scenario with a defined inflow into the protected area (to one or more cells) using a hydrograph.

Controlled Outlet of Flood Control Basins Given the case that controlled outlet of a flood control basin is necessary, a flooding of other areas might occur. These areas can be delineated by using the designed hydrograph data for that particular location.

Limitations FloodArea is primarily intended to calculate areas affected by a flood. Essentially it is a simplified two-dimensional hydraulic model, integrated in a GIS. The simplifications made mainly affect the open channel hydraulics, which can be described only roughly with the available parameters (resolution of the elevation model in the channel, no cross sections). Furthermore the algorithms do not contain the impulse transfer, therefore some phenomena such as the sloping of a water level in a river bend is not described correctly.

Demo Version and Demo Data / Notice


Demo Version and Demo Data

Notice The demo version can be tested with any data. Rasters resulting from a calculation without a valid license key in combination with a USB hardware license key (dongle) will be watermarked.

Data The demo version is made available with an mxd-file for ArcView 10.x. When installing FloodArea it is dropped to the folder to which the system variable %ALLUSERSPROFILE% is pointing together with the corresponding demo data directory examples. With the first start of FloodArea it will be copied entirely to the active user’s USER directory.

Users of Windows 7 will find their demo data in the following folder

C:\Users\<Username>\AppData\Roaming\geomerGmbH\examples

The demo data comprise:

dtm: an elevation model (units are meters) with a horizontal resolution of 5 m and an extent of 200 rows and 200 columns (corresponding to an area of 1 km²).

Demo Version and Demo Data / Data


drainage: a raster representing a drainage network. Values represent water levels and are given in meters.

dike : an uninterrupted flow barrier.

breach: a raster representing a failure area (adapted to the dam raster).

strickler: a raster representing roughness coefficients (values are in 1/n). The legend contains the underlying land use.

rainfall: a raster representing weight factors for the option rainstorm (areal input).

A hydrograph data file (hydrograph.txt).

A coordinate file (floodarea.koo).

Publications on FloodArea / Data


Publications on FloodArea Assmann, A., Krischke, M., Höppner, E. (2009): Risk maps of torrential

rainstorms. In: Samuels, P., Huntington, S., Allsop, W., Harrop, J. (Hrsg.) (2009) Flood Risk Management: Research and Practice: 48. ISBN 978-0-415-48507-4.

Holzhauer, V., Müller, M., Assmann, A. (2009): RISK-EOS flood risk analysis service for Europe. In: Samuels, P., Huntington, S., Allsop, W., Harrop, J. (Hrsg.) (2009) Flood Risk Management: Research and Practice: 46. ISBN 978-0-415-48507-4.

Assmann, A. (2008) Einsatzgebiete und Erstellung von Starkregen-Gefahrenkarten. In: Strobl, J., Blaschke, T. & Griesebner, G. (Hrsg.) (2008) Angewandte Geoinformatik 2007, Beiträge zum 20. AGIT-Symposium Salzburg: 750-755. ISBN 978-3-87907-464-8.

Assmann, A. (2007) Starkregen-Gefahrenkarten und Schutzkonzepte. In: Verband Region Rhein-Neckar (Hrsg.) 5. Hochwasserschutzforum Rhein-Neckar, Heft 4.

Assmann, A. & Herrmann, S. (2007) Geoinformationstechnologien als Instrument in Beteiligungsprozessen - Anforderungen und Möglichkeiten. In: Kuratorium für Technik und Bauwesen in der Landwirtschaft e.V. (Hrsg.) Geoinformationstechnologien zur Umsetzung der Wasserrahmenrichtlinie. KTBL-Heft 62: 16-30. ISBN 978-3-939371-36-6.

Assmann, A. Schroeder, M. & Hristov, M. (2007) High Performance Computing für die rasterbasierte Modellierung. In: Strobl, J., Blaschke, T. & Griesebner, G. (Hrsg.) (2007) Angewandte Geoinformatik 2007, Beiträge zum 19. AGIT-Symposium Salzburg: 19-24. ISBN 978-3-87907-451-8.

Assmann, A., Grafe, M., Runge, I. & Thäger, F. (2006): Einflüsse des Berechungsverfahrens und der Qualität der Grundlagendaten auf die Ermittelung überschwemmungsgefährdeter Gebiete. In: Hydrologie und Wasserbewirtschaftung 50, H. 1: 19-24. ISSN 1439-1783.

Assmann, A. (2005): Simulation von Überflutungsflächen und Deichbrüchen auf der Grundlage von Rasterdaten. In: Wittmann, J. und Xuan Thinh, N. (Hrsg.) (2005) - Simulation in den Umwelt- und Geowissenschaften, S. 109-116.

Assmann, A. & Jäger, S. (2003): GIS-Einsatz im Hochwassermanagment. In: Strobl, J., Blaschke, T. & Griesebner, G. (Hrsg.) (2003) - Angewandte Geographische Informationsverarbeitung XV, Beiträge zum AGIT-Symposium Salzburg 2003, S. 7-14.

Assmann, A. (2003): GIS Einsatz bei der Planung dezentraler Hochwasserschutzmaßnahmen. - arcaktuell 1/2003: 28-29.

Publications on FloodArea / Data


Assmann, A. & E. Ruiz Rodriguez (2002): Modellierung im GIS - Erfahrungen beim Einsatz eines rasterbasierten Modells für Überschwemmungssimulationen. - GeoBIT 7/2002: 14-16.

Disse, M, Kamrath, P., Wilhelmi, J. und Köngeter, J. (2003): Simulation des Hochwasserwellenablaufes und der Ausbreitung von Überflutungsflächen unter Berücksichtigung von Deichbrüchen. - Wasserwirtschaft 5/2003: 24-29

Disse, M. & Assmann, A. (2003): Bestimmung der Überflutungsflächen infolge von Deichbrüchen mit GIS-basierten Werkzeugen. - Hydrologie und Wasserbewirtschaftung 47, H.6: 228-233.

Disse, M., Grätz D. & M. Hammer (2002):Auswirkungen von Deichbrüchen auf den Wellenablauf und die betroffenen Überflutungsflächen am Beispiel des Niederrheins. - 3. Forum Katastrophenvorsorge.

Disse, M., Hammer, M. & J. Wilhelmi (2003): Quantifizierung der Hochwassergefährdung für die Rheinanlieger unter Berücksichtigung von Deichversagen. - 4. Forum Katastrophenvorsorge.

Disse, M., Hammer,M., Merz, B., Thieken, A. & G. Blöschl (?):Vorsorgender Hochwasserschutz im Rheingebiet - welchen Beitrag leistet das DFNK? - Ergebnisse aus dem Deutschen Forschungsnetz Naturkatastrophen.

Jäger, S. (2002): Ein neuer Rheinatlas - Hydrodynamische Modellierung für eine bessere Hochwasservorsorge. - arcaktuell 2/2002: 38-39.

Gemmer, M. (2003): GIS/RS-Based Flood Risk Mapping for the Eastern Honghu Flood Diversion Area. - Journal of Lake Sciences 15: 166-172.

Gemmer, M. (2003): Transferability of European Flood Impact Estimation Techniques to the Yangtze River Catchment and Possible Adaptations. - Journal of Lake Sciences 15: 173-183.

Ruiz Rodriguez, E., Zeisler, P. & A. Assmann (2003): GIS-Einsatz zur Gefahrenabwehr im Hochwasserfall. - Hochwasserschutz und Katastrophenmanagment 4/03: 28-30.

Support / Data


Support

Support is given at the following address, according to your license agreement.

geomer GmbH Im Breitspiel 11 B D-69126 Heidelberg Germany

Fon: +49 (0)6221 89458-0 Fax: +49 (0)6221 89458-79 eMail: [email protected] Internet: www.geomer.de

http://www.geomer.de/

License Agreement / Data


License Agreement

Please read the following license terms prior to installing our software. By installing the software you irrevocably accept this License Agreement.

§ 1 Subject of the Contract

1. The following terms apply to software licenses granted by geomer GmbH (hereinafter called geomer).

2. Software in the sense of this GTB license includes data processing programs with or without accompanying software protection, data stocks or/and accompanying documentation in machine-readable and printed form, hereinafter referred to as licensed soft-ware. Licensed software also includes all copies made of this licensed software in its supplied or modified version.

3. We expressly point out that it is not possible with today's technology to rule out any errors in data processing programs under all application conditions.

§ 2 Scope of the License, Rights of Use

1. The licensed software is protected by copyright; protection by other legal provisions remains unaffected.

2. In accordance with the type of license purchased, geomer grants the licensee a non-transferable and non-exclusive right to simultaneous use of the licensed software in line with the number and functions agreed. The type of license defines the rights of use. There is a demo license (restricted use exclusively for test purposes) and a commercial license (unrestricted rights of use). If breach of the license terms is proven, twofold license fees are payable for wrongful use of the software licenses.

3. The right of use accrues on delivery of the licensed software. The licensee is entitled to use the licensed software for an unlimited period of time.

4. As per this GTB license, use includes copying the machine-readable licensed software permanently or temporarily, completely or in part, by loading, displaying, playing, transferring or saving it in order to process the instructions and data contained in it on appropriate hardware or to monitor, examine or test the program functions it includes.

5. The licensee is entitled to make a backup copy of the machine-readable licensed software, provided there is a need to do so. If the hardware on which the software has been installed is not operational, temporary use on different hardware is permitted.

6. The right of use does not include the right beyond the scope defined in §2. Clause 5 to copy the licensed software completely or in part, transfer or pass it on to third parties, disseminate it in any other way or grant licenses or sub-licenses to it. Third parties within the meaning of this Agreement are persons not employed by the licensee.

§ 3 Rights of Ownership and Secrecy

1. The rights to the licensed software, including the licensed software modified or copied by the licensee, remain with the holder of the right mentioned in the licensed software.

2. The copyright notes made by the holder of the right and contained in the delivered version of the machine-readable licensed software and its data carriers should be attached by the licensee to all copies of the machine-readable licensed software and its data carriers.

3. The licensor/copyright owner must be mentioned in all reports and publications concerning the application of the licensed software.

4. The licensee shall not make available the licensed software, including the copies made of it, to third parties for an unrestricted length of time, unless they are using the licensed software at the licensee's premises. The licensee undertakes to make his/her employees who are granted access to the licensed software aware of these terms and to put them under the same obligation as he/she is personally subject to.

5. The licensee shall delete any licensed software contained on any agreed hardware or other hardware or data carriers prior to giving it away or disposing of it.

§ 4 Performance

1. geomer fulfills its obligations to deliver the goods by handing over the data carriers with the machine-readable licensed software and, if available, the printed licensed software.

2. On dispatch, the risk passes to the licensee when the goods are transferred to the first carrier.

§ 5 Warranty

1. When delivering the licensed software to the licensee it is warranted that the programs have been thoroughly checked prior to delivery and are in line with the valid program specifications delivered to the licensee. However, geomer makes no warranty that the licensed software is without flaws for any specific instance of application. The responsibility for selecting and using the licensed software for any specific instance of application and the results achieved by it lies solely with the licensee.

2. The warranty does not cover defects caused by improper use of the licensed software.

License Agreement / Data


§ 6 Liability

1. geomer is not liable for damage caused by slight negligence. They are, however, liable for immediate damage caused by slightly negligent breach of significant contractual duties.

3. geomer is not liable for down times, damage and consequential damage caused by program errors, improper use of the licensed software or misinterpretation of the calculated results, regardless of the grounds to which they can be attributed.

4. The licensee is obliged to indemnify geomer against liability for all claims by third parties arising from the use of the licensed software.

5. Otherwise, the damages to be paid by geomer are limited to the agreed license fee and their applicability lapses after 6 months.

§ 7 Industrial Property Rights and Copyrights of Third Parties

1. geomer indemnifies the licensee against all claims by third parties made against him in the Federal Republic of Germany due to infringement of property rights by use of the licensed software in line with the contract, as long as the licensee has immediately notified geomer of such claims in writing and all protective measures and settlement negotiations are left to geomer. If such claims have been exercised or are anticipated, geomer can modify or replace the licensed material at the licensee's expense.

2. The provision as per § 7 Clause 1 does not apply, if claims of a third party can be attributed to the licensee modifying the licensed software.

§ 8 Miscellaneous

1. The place of jurisdiction for all disputes occurring due to and in the context of this Agreement is Heidelberg.

2. Should a provision of these General Terms of Business be or become null and void or anything be lacking, the validity of the remainder of the provisions remains unaffected. The parties to the Agreement agree to replace the invalid provision or make good the lack by means of a valid regulation which meets the economically desired purpose of the invalid provision as ideally as possible.

Heidelberg, July 2013

geomer GmbH

floodareahpc-desktop · arcmap the license file needs to be specified in the floodarea toolbar. you...

Documents