Mission of the project
Mission of the project
Embedded Files
This document provides a walk-thru on running a basic AutoRoute and FloodSpreader model to create Ensemble-Based Flood Maps
Conceptual Design
Conceptual Design
AutoRoute simulates several different flow rates for each stream cell, recording the information within the VDT Database. This only needs to occur once.
FloodSpreader is more for operational use. When a flow scenario needs to be simulated, FloodSpreader uses the VDT Database to assign a depth, topwidth, and velocity to each stream cell, and then maps the flood inundation map. For Ensemble Flood maps multiple flow rates need to be input for each stream segment.
Data Collection
Data Collection
DEM, land cover, streamlines, and flow rates are all needed to run an AutoRoute simulation.
Example Dataset (URLs are where the files in the example dataset came from)
Example Dataset (URLs are where the files in the example dataset came from)
DEM from the 1/3 Arc Second National Elevation Dataset (https://apps.nationalmap.gov/downloader/)
Land Cover is from the National Land Cover Database 2011 (https://www.mrlc.gov/data/nlcd-2011-land-cover-conus)
Streamlines were obtained from GeoGLoWS (http://geoglows-v2.s3-website-us-west-2.amazonaws.com/#streams/)
Flow rates were obtained from return period from GeoGLoWS (http://geoglows-v2-retrospective.s3-website-us-west-2.amazonaws.com/#return-periods/)
GeoGLoWS Data in General: https://data.geoglows.org/available-data
Folder Setup
Folder Setup
Downloaded Data
DEM - houses all the DEM files that are to be analyzed
LandCover - houses the NLCD 2011 dataset. Also includes Manning
StrmShp - Streamlines obtained from GeoGLoWS
FlowData - Recurrence interval flow data from GeoGLoWS
EnsembleFlowData - Houses the ensemble flow data.
Formatted Data (these will be created using provided scripts)
LAND - This will be the land cover that AutoRoute uses.
STRM - Rasterized version of the streamline.
FLOW - Contains file(s) with all GeoGLoWS flow data formatted for use in AutoRoute
FlowFile - Contains file(s) with flow data to be simulated within FloodSpreader
AutoRoute Output (these will be created using provided scripts)
VDT - Stores the Velocity-Depth-TopWidth datasets produced by AutoRoute
FloodMap - Output flood inundation maps in raster format.
Bathymetry - Output bathymetry and topobathymetry in raster format.
Ensemble Flow Data
Ensemble Flow Data
To run ensemble-based flood maps there are no changes to the input/output cards within the Main Input File. The only changes are made within the “Comid_Flow_File” file. Within the Main Input File, the “Comid_Flow_File” file is identified with the following input card:
Comid_Flow_File EnsembleFlowData/OH_EnsembleFlows.txt
In the above example, the “Comid_Flow_File” file is “OH_EnsembleFlows.txt” located in the “EnsembleFlowData” folder. In previous FloodSpreader models the “Comid_Flow_File” file listed each river reach by unique identifier (such as COMID or Rivid) followed by a single flow rate. In the updated version of the FloodSpreader code up to 100 flow rates can be specified for each river reach. For example, the left image shows a list of unique river reach identifiers (COMID) followed by a low-, median-, and high-flow value. In this model all three flow rates will be simulated within FloodSpreader.
For the example in this document there will be 14 different flow rates.
(Optional) Gather your own Data (Optional)
(Optional) Gather your own Data (Optional)
DEM, land cover, streamlines, and flow rates are all needed to run an AutoRoute simulation.
DEM
DEM
There are several sources of Digital Elevation Model (DEM) data. In the U.S., the National Elevation Dataset (NED) is an often-used source for DEM data (https://apps.nationalmap.gov/downloader/).
AutoRoute has been simulated using spatial resolutions from sub-meter to approximately 90-m. In general, it is best to have spatial resolutions less than 30-m.
AutoRoute and FloodSpreader can operate in both geographic and projected coordinate systems. Typically, geographic coordinate systems are used.
LAND
LAND
The National Land Cover Database (NLCD) (https://www.mrlc.gov/data/nlcd-2011-land-cover-conus) is a rasterized land cover map.
The NLCD data may need to be converted to the projection of the DEM data.
You may also want to clip the data to the area of interest.
StrmShp
StrmShp
GeoGLoWS has streams in Geopackages (http://geoglows-v2.s3-website-us-west-2.amazonaws.com/#streams/).
Convert the GeoGLoWS streams to a shapefile format with the same projection as the DEM data.
You may also want to clip the streams to just the area of interest.
FlowData
FlowData
GeoGLoWS also provides recurrence-interval flow data (http://geoglows-v2-retrospective.s3-website-us-west-2.amazonaws.com/#return-periods/).
Download the file that corresponds to your streams.
ALL DATASETS MUST BE IN THE SAME PROJECTION!!!!!!!!!
ALL DATASETS MUST BE IN THE SAME PROJECTION!!!!!!!!!
SetUp Script (AutoRoute_Process_Geospatial_Datasets_Ensemble.py)
SetUp Script (AutoRoute_Process_Geospatial_Datasets_Ensemble.py)
These steps will use the Anaconda (https://www.anaconda.com/download)
Set-Up the Python Environment
Set-Up the Python Environment
Open Anaconda Command Prompt and Change Directory to where your model resides.
cd ModelTestSite_Ensemble/
Create the pygdal_36 environment
conda env create -f conda_environment_pygdal_36.yml
Activate the pygdal_36 environment
conda activate pygdal_36
AutoRoute_Process_Geospatial_Datasets_Ensemble.py
AutoRoute_Process_Geospatial_Datasets_Ensemble.py
This script will help build an AutoRoute/FloodSpreader model for you.
On Line 14 there is a variable called "Main_Directory".
YOU MUST CHANGE THE FOLDER PATH TO THE FOLDER PATH WHERE THE MODEL FILES ARE ON YOUR COMPUTER.
Simulate the script from Anaconda Prompt:
python AutoRoute_Process_Geospatial_Datasets_Ensemble.py
AutoRoute_Process_Geospatial_Datasets_Ensemble.py (Continued)
AutoRoute_Process_Geospatial_Datasets_Ensemble.py (Continued)
The script builds the required folders (STRM, LAND, FLOW, VDT, FloodFolder, FlowFile, AutoRoute_Input_Files, etc.)
The script formats the landcover to the same spatial resolution as the DEM.
The script converts the streamlines to a raster format.
The script formats flow data from GeoGLoWS into a format that AutoRoute and FloodSpreader can use.
The script DOES NOT create the ENSEMBLE FLOW DATA for you. You must write your own script to do this. However, as part of the GoogleDrive (see above) an example file is provided that has 14 flow rates for each stream reach in the example.
Simulating AutoRoute
Simulating AutoRoute
The AutoRoute code is written in C and is provided as an executable.
The main output from the AutoRoute code is a VDT_Database file that is stored in the VDT folder.
Within the Anaconda Command Prompt, type the following:
AutoRoute_w_GDAL.exe AutoRoute_InputFiles/AR_Input_File_Ensemble.txt
Simulating FloodSpreader
Simulating FloodSpreader
The FloodSpreader code is also written in C and is provided as an executable. Within the Anaconda Command Prompt, type the following:
FloodSpreader.exe AutoRoute_InputFiles/AR_Input_File_Ensemble.txt
The main outputs from the AutoRoute code are ensemble-based flood inundation maps, which are saved in the "FloodMap" folder.
If a single flow rate is given in the “Comid_Flow_File” file, then the output flood raster will have a value of 0 or 1, with the value of 1 indicating flood inundation. If multiple flow rates are given in the “Comid_Flow_file” file (as is done in the example provided), then the output flood inundation raster values will be between 0 and 100.
Each cell value represents the percentage of flow values that indicate flooding in that cell. For instance, a cell value of 50 indicates that 50% of the flow rates simulate result in flooding in that cell.
Page updated
Report abuse