Integrating ArcHydro and HEC Models

by David R. MaidmentCenter for Research in Water Resources

University of Texas at Austin

• Arc Hydro and hydrologic models• Interface Data Model for HEC-HMS• Implementation in San Antonio using Model Builder

Integrating Arc Hydro and HEC Models

• Arc Hydro and hydrologic models

• Interface Data Model for HEC-HMS

• Implementation in San Antonio using Model Builder

Hydrologic Information System

Modeling

Geodatabase

A hydrologic information system is a combination of geospatial and temporal hydrologic data with hydrologic models that supports hydrologic practice, science and education

Database

GeoHMS

GeoRAS

InterfacePrograms

HMS

RAS

GIS

GIS Preprocessors for Hydrologic Models

HMSIDM

RASIDM

Interfacedata models

HMS

RAS

GIS

GeoDatabase

Arc Hydrodata model

Connecting Arc Hydro and Hydrologic Models

HMSIDM

Interfacedata models

HMS

RAS

GIS

GeoDatabase

Arc Hydrodata model

GeoRAS

Connecting Arc Hydro and Hydrologic Models

GeoHMS

RASIDM

Integrating Arc Hydro and HEC Models

• Arc Hydro and hydrologic models

• Interface Data Model for HEC-HMS

• Implementation in San Antonio using Model Builder

Basin

Interface

Data

Model

Project

Interface

Data

Model

IDM Performance Goal

• To provide a database for all HMS data, so that the data may be queried and retrieved efficiently.

IDM Data Transfer Goal

• To store data in a manner so that it is readily transferable from geodatabase to HMS files, and visa versa.

HMS files HMS geodatabase

IDM Spatial Analysis Goal

• To store watershed (spatial) data in a manner that can be easily viewed and analyzed in ArcMap.

• To create a data structure that is logical to the HEC-HMS user

IDM Intuitive Use Goal

IDM Arc Hydro Compliance Goal

• Arc Hydro connectivity and naming conventions

Arc Hydro Geodatabase

HydroID

IDM Geodatabase

FeatureID

HEC-HMSProgram files

Element NamesHMSCode

The HMSCode.basin HMS text file

HMSSubbasin attribute table

HMSInitialConstant tableIDM

Connection between HMS feature classes and parameter tablesConnection

between HMS and IDM elements

Flow Network

IDM Geodatabase Design

Purpose: To provide a HMS data storage structure that meets IDM design goals

Visio 2000 UML

ArcGIS Repository

Geodatabase Schema

UMLThe Unified Modeling Language

-HydroID : esriFieldTypeInteger-HydroCode : esriFieldTypeString-FType : esriFieldTypeString-Name : esriFieldTypeString-AreaSqKm : esriFieldTypeDouble-JunctionID : esriFieldTypeInteger

Waterbody{GeometryType = esriGeometryPolygon}

+Shape : esriFieldTypeGeometry

ESRI Classes::Feature

UML Diagram

UML

Geodatabase Table

Basin

GDB

Project

GDB

Importing HMS Data

Use Visual Basic to develop codes for transferring data.

Constant Loss Rate (inches/hour)

Llano at Junction Model

Rainfall lost to infiltration

Snyder Time to Peak (hours)

Llano at Junction Model

Time to Peak

Modified Puls Storage (ac-ft)

Llano at Junction Model

Storage required to produce 5000

cfs flow

Integrating Arc Hydro and HEC Models

• Arc Hydro and hydrologic models

• Interface Data Model for HEC-HMS

• Implementation in San Antonio using Model Builder

Regional Storm Water Regional Storm Water Modeling Program and Modeling Program and

Master Plan for San Master Plan for San AntonioAntonio

City ofSan Antonio

Modeling System

Rainfall Data:Rain gagesNexrad

Calibration Data:FlowsWater Quality

Geospatial Data:City, CountySARA, other

FloodplainManagement

IntegratedRegional Water

Resources planning

CapitalImprovemen

tPlanning

FloodForecasting

Water qualityplanning

San Antonio Regional Watershed Modeling System

“Bring the models together”

• Historical Nexrad data – NWS and TNRIS archive

• Design rainfall maps – 2, 5, 10, 25, 50, 100 year design rainfalls as used for FEMA floodplain studies

• Real-time Nexrad data using web services (Tom Wesp)

Sources of Rainmap data

NEXRAD WSR-88D Radars in Central Texas(Weather Surveillance Radar-1988 Doppler)

scanning range = 230 km

Stage I: Just Radar

Stage II: gages, satellite, and surface temperature

Stage III: Continuous mosaic from radar overlaps

NEXRAD Products:

Source: PBS&J, 2003

EWX – NEXRAD Radar in New Braunfels

Digital Rain Maps from National Weather Service (03/04/2004)

Digital Rain Maps from National Weather Service (03/29/2004)

Reading Historical Archives of NEXRAD Datasets from Internet

FTP Server

Local

Internet

Design Rainfall Maps

100yr 24h

100yr 06h 100yr 12h

Real-Time NEXRAD Datasets from Web Services

FEMA 100-year flood plain map in Bexar County

RC1 RU

09R CO

08R CO

07R CO06R CO

04R CO03R CO

01R CO

02R CO

05R CO

Regional Watershed Modeling System Case Study

Rosillo Creekwatershed

• Arc Hydro Geodatabasefor whole watershed• HEC-HMS hydrology modelfor whole watershed• HEC-RAS hydraulic model for Rosillo Creek

Salado Creek watershed

Components:

Bexar County

Arc Hydro and HEC-HMS

Arc HydroSchematic Network

HEC-HMSHydrologic

Model

Calculates Flows

Arc Hydro and HEC-RAS

Arc HydroChannel

Cross Sections

HEC-RASHydraulic

Model

Calculates Water Surface

Elevations

HEC Data Storage System (DSS)(binary data file system shared by HEC models)

• An exact replica of the binary DSS files is stored in the ArcGIS geodatabase

• An Arc 9 Toolbox exchanges data between DSS and the geodatabase

Time series catalog

Many time series

Flow Change PointsModels communicate with

one another through Arc Hydro at designated points

Nexrad Map to Flood Map in Arc 9 Model Builder FLO

ODPLAIN MAP

Flood map as output

Model for flood flow

Model for flood

depth

HMS

Nexrad rainfall map as input

Conclusions

• An interface data model provides a convenient way of storing and visualizing the content of a hydrologic model

• Combination of interface data models and ArcGIS Model Builder provides a very efficient means of work flow automation