The accuracy of the flood inundation mapping (FIM) is critical for model development and disaster preparedness. The evaluation of flood maps from different sources using geospatial platforms can be tedious and requires repeated processing and analysis for each map. These preprocessing steps include extracting the correct flood extent, assigning the same projection system to all the maps, categorizing the maps as binary flood maps, removal of permanent water bodies, etc. This manual data processing is cumbersome and prone to human error.
To address these issues, we developed Flood Inundation Mapping Prediction Evaluation Framework (FIMPEF), a Python-based FIM evaluation framework capable of automatically evaluating flood maps from different sources. FIMPEF takes the advantage of comparing multiple target datasets with large benchmark datasets. It includes an option to incorporate permanent waterbodies as non-flood pixels with a user input file or pre-set dataset. In addition to traditional evaluation metrics, it can also compare the number of buildings inundated using a user input file or a pre-set dataset.
FIMPEF/
├── Input Rasters/
│ └── Case 1/
│ └── RG_benchmark.tif (Benchmark FIM (B-FIM) for Hurricane Mathew, Oct 09, 2016, North Carolina. Make sure to enter the name 'benchmark' while naming the raster)
│ └── OWP_09_NC.tif (Model FIM (M-FIM) for Hurricane Mathew, Oct 09, 2016, North Carolina. (NOAA OWP HAND FIM))
├── PWB/
│ └── PWB.shp (Shapefile of Permanent Water Bodies)
├── BuildingFootprint/
│ └── NC_bldg.shp (Geopackage of building footprints.The building footprint used is Microsoft release under Open Data Commons Open Database Liocence. Here is the link https://automaticknowledge.co.uk/us-building-footprints/ User can download the building footprints of the desired states from this link.)
├── FIMPEFfunctions.py (Contains all functions associated with the notebook)
├── FIMPEF.ipynb (The main notebook code to get FIM)
├── FIMPEF_package.ipynb (FIMPEF package version 0.1.2)
└── README.md (This file)
The main directory contains the main folder. Inside the main folder there are sub folders with individual case studies. For example, if a user has two case studies they should create two seperate folders. Inside each folder there should be a B-FIM with a 'benchmark' name assigned in it and different M-FIM in tif format.
In this work the 'USA Detailed Water Bodies' from ARCGIS hub is used. Here is the link https://hub.arcgis.com/datasets/esri::usa-detailed-water-bodies/about. User can input their own permanent water bodies shapefile as .shp and .gpkg format.
The building footprint used is Microsoft release under Open Data Commons Open Database Licence. Here is the link https://automaticknowledge.co.uk/us-building-footprints/ User can download the building footprints of the desired states from this link.
For directly using the package, the user can use the following code in a Jupyter notebook:
!pip install fimpef==0.1.2
For using the source code, simply run the FIMPEF.ipynb importing the FIMPEFfunctions.py.
The output from FIMPEF includes generated files in TIFF, SHP, CSV, and PNG formats, all stored within the "Case 1" folder. Users can visualize the TIFF files using any geospatial platform. The TIFF files consist of the binary Benchmark-FIM (Benchmark.tif), Model-FIM (Candidate.tif), and Agreement-FIM (Contingency.tif). The shp files contain the boundary of the generated flood extent. The png files include the Agreement map, Performance Metrics, and Building Footprint Statistics.
If you use this repository or its components in your work, please cite it as follows:
Dipsikha Devi, Supath Dhital, Dinuke Munasinghe, Anupal Baruah, Sagy Cohen. "FIMPEF" GitHub, 2024, .https://github.com/dipsikha-devi/FIMPEF
Contact Dr. Sagy Cohen (sagy.cohen@ua.edu) Dr. Dipsikha Devi, (ddevi@ua.edu) Supath Dhittal,(sdhital@crimson.ua.edu)