Purpose of this Document
Purpose of this Document
Embedded Files
This document provides a walk-thru on running a basic AutoRoute /FloodSpreder model using ERDC-provided executables.
Conceptual Diagram
Conceptual Diagram
Multiple flow modeling systems are now available. The AutoRoute/FloodSpreader models are used to quickly convert this flow data into flood inundation maps. The users of AutoRoute/FloodSpreader are generally those who need quickly-simulated flood inundation maps over large domains.
**Note that this example uses the AutoRoute and FloodSpreader executables that are available from ERDC.
AutoRoute simulates a flow rate for each stream cell using a simple volume-fill Manning approach. The information information (depth, topwidth, and velocity) are then recorded within the VDT File (the released version of AutoRoute from ERDC does not have the VDT Database option).
FloodSpreader uses the VDT File to assign a depth, topwidth, and velocity to each stream cell, and then maps the flood inundation map.
What is not covered in this document:
Bathymetry simulation
Ensemble flood map simulation
Forecast flow simulation
Step 1. Data Collection
Step 1. Data Collection
DEM, land cover, streamlines, and flow rates are all needed to run an AutoRoute simulation.
Test Case for Gardiner, MT
Test Case for Gardiner, MT
(Download all files into a directory)
Links to AutoRoute and FloodSpreader Executables
Links to AutoRoute and FloodSpreader Executables
(These executables are already provided in the GitHub repository you just downloaded)
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
Downloaded Data
DEM - houses all the DEM files that are to be analyzed
LandCover - houses the NLCD 2011 dataset
StrmShp - Streamlines obtained from GeoGLoWS
FlowData - Recurrence interval flow data from GeoGLoWS
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. This folder WILL NOT BE USED in this example.
AutoRoute Output (these will be created using provided scripts)
VDT - Stores the Velocity-Depth-TopWidth dataset produced by AutoRoute
FloodMap - Output flood inundation maps in raster format.
Step 2. Obtain Anaconda, Set-Up Environment, and run model set-up code (AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.py)
Step 2. Obtain Anaconda, Set-Up Environment, and run model set-up code (AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.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 CIROH_TestCases/
Create the autoroute environment
conda env create -f environment.yml
Activate the autoroute environment
conda activate autoroute
AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.py
AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.py
This script will help build an AutoRoute/FloodSpreader model for you.
On Line 25 there is a variable called "Main_Directory". If you leave this blank the model will run in your local directory. Alternatively, you can change the folder path to where you want the model to run on your computer.
Lines 25 - 44 are already set-up for the test case in Gardiner, MT, but can be modified for future model simulations.
Simulate the script from Anaconda Prompt:
python AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.py
AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.py (Continued)
AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.py (Continued)
The script builds the required folders (STRM, LAND, FLOW, VDT, FloodFolder, FlowFile, AutoRoute_Input_Files, etc.)
The script builds a model input file in the "AutoRoute_Input_Files" folder.
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.
Step 3. Simulate AutoRoute and FloodSpreader
Step 3. Simulate AutoRoute and FloodSpreader
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 file that is stored in the VDT folder.
The VDT File contains the velocity, depth, and top-width for a single flow event (this is different than the VDT Database file that is available in future model versions).
Within the Anaconda Command Prompt, type the following:
autoroute.exe AutoRoute_InputFiles/Gardiner_AR_Input_File.txt
Simulating FloodSpreader
Simulating FloodSpreader
The FloodSpreader code is also written in C and is provided as an executable.
The main outputs from the AutoRoute code are flood inundation maps and flood depth rasters, which are both saved in the "FloodMap" folder.
Within the Anaconda Command Prompt, type the following:
floodspreader.exe AutoRoute_InputFiles/Gardiner_AR_Input_File.txt
Step 4. Gather your own data and build a model for a location of interest.
Step 4. Gather your own data and build a model for a location of interest.
Gather your own geospatial datasets (see links below). You can save these in the existing directory, or create your own.
Update to the set-up script (AutoRoute_Process_Geospatial_Datasets_ERDC_Codes.py) for your location, specifically lines 27-44
Run the AutoRoute and FloodSpreader codes to see what results you get.
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!!!!!!!!!
Helpful hint - Always set-up your model to use the same projection as your DEM. When using National Elevation Datasets it is typically EPSG:4269 - NAD83.
Page updated
Report abuse