Purpose of this Document
Purpose of this Document
Embedded Files
This document provides a walk-thru on creating a Topobathymetric Surface using AutoRoute and FloodSpreader. The test case provided is in Casper, WY, but the datasets used (DEM, Land Cover, GeoGLoWS) are available globally.
The idea is that this script will create a Topobathymetric Surface that can REPLACE the DEM in future AutoRoute simulations for the domain of interest.
Conceptual Design
Conceptual Design
AutoRoute simulates a bathymetric profile for each stream cell, recoding the information within the VDT file as well as a raster (tiff, img) file.
FloodSpreader takes the bathymetry data and creates a continuous bathymetric surface, which is then "burned into" the original DEM to create a topobathymetric dataset (tiff, img). This topobathymetric dataset can then be used in future AutoRoute/FloodSpreader models or used within 2D hydraulic models.
Data Collection (Example Model provided in GoogleDrive link below)
Data Collection (Example Model provided in GoogleDrive link below)
DEM, land cover, streamlines, and flow rates are all needed to run an AutoRoute / FloodSpreader 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
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
The FlowFile is not used in this example, but is written out for future applications.
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.
SetUp Script (AutoRoute_Process_Geospatial_Datasets_Bathy.py)
SetUp Script (AutoRoute_Process_Geospatial_Datasets_Bathy.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_Bathymetry/
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_Bathy.py
AutoRoute_Process_Geospatial_Datasets_Bathy.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_Bathy.py
AutoRoute_Process_Geospatial_Datasets_Bathy.py (Continued)
AutoRoute_Process_Geospatial_Datasets_Bathy.py (Continued)
The script builds the required folders (Bathymetry, 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.
Simulating AutoRoute
Simulating AutoRoute
The AutoRoute code is written in C and is provided as an executable.
The main outputs from the AutoRoute code are:
A VDT file that is stored in the VDT folder.
A Bathymetry raster (AR_Bathy.tif) that is stored in the Bathymetry folder.
Within the Anaconda Command Prompt, type the following:
AutoRoute_w_GDAL.exe AutoRoute_InputFiles/AR_Input_File_Bathy.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 in the "FloodMap" folder.
A Topobathymetric raster (FS_Bathy.tif) that is stored in the Bathymetry Folder.
Shown on the left, the topobathymetric raster is very similar-looking to the DEM. FloodSpreader combines bathymetric data (processed from AutoRoute) with the DEM to create the topobathymetric raster
FS_Bathy.tif is the final product from this exercise, which can be used in future AutoRoute/FloodSpreader models or within 2D hydraulic models.
Within the Anaconda Command Prompt, type the following:
FloodSpreader.exe AutoRoute_InputFiles/AR_Input_File_Bathy.txt
Evaluating Bathymetry within GIS Software
Evaluating Bathymetry within GIS Software
Here we use the GIS Software to see how the new topobathymetric dataset (FS_Bathy.tif) compares to the original DEM (CasperWY_DEM.tif).
The Profile Tool within QGIS is one way to show the comparison
On the left shows a simple cross-section profile across the North Platte River.
The DEM is shown in Black
The Topobathymetry data is shown in Red.
It is clear that the FS_Bathy.tif is effectively a DEM with bathymetry data burned into it.
Page updated
Report abuse