Transcript ESRINW2004 Arc Hydro Presentation - UT Web

Arc Hydro: An Introduction
Dean Djokic
ESRI
Review of geodatabase issues





Adding shapefiles and coverages into an ArcMap session does not
make a geodatabase
Loading shapefiles and coverages into a geodatabase does not
make a (efficient) geodatabase.
Ignoring geodatabase capabilities increases cost of development
and ownership
When developing data, ignore spatial reference issues at your own
peril
SDE and versioning (including disconnected editing) do not
replace the need for careful workflow development
Arc Hydro Data Model
Template Data Models
Project Data Models
FEMA
HEC
…
GIS/IT Standards
ISO
Template Data Models
FGDC
Arc Hydro
Parcel
…
OGC
ArcGIS Core Data Model
Industry
Object
Feature
Topology
Templates
Provide an
Important Link
Between Project
Teams,
Standards, and
ESRI Software
Development
Arc Hydro




Extension of geodatabase model for support of water
resources applications (template data model)
Culmination of a three year process led by D.R.
Maidment through GIS in Water Resources Consortium
(Arc Hydro book) – second phase in progress
Collection of tools for support of Arc Hydro geodatabase
design and basic water resources functions
Starting point for water resources database and
application development
Basic idea: Transition from …
Streams
Drainage Areas
Hydrography
Channels
Terrain Surfaces
Rainfall Response
Digital Orthophotos
Data Model
Based on
Inventory
… and …
Follow a drop of water from where it falls on the land, to the
stream, and all the way to the ocean.
Data Model
Based on
Behavior
… to Arc Hydro data model
Integrate Data Inventory using a Behavioral Model
Relationships between
objects linked by tracing path
of water movement
Basic Concepts
Define core feature classes for water resources
analyses
 Establish relationships between core feature classes
 Use geometric network for tying pieces together
 Mobilization of standard ArcGIS functionality
 Custom tools for some of the attribute management
 Custom tools for advanced “water resources”
functionality

Data Model Purpose
Target audience: Water resources (surface)
community interested in quick start in ArcGIS
implementation
 Starting point for project model design
 Not a “do all” design
 Not implementation/application specific, but
provides the key components to develop on top of

Template Data Model Approaches
Water Resources
Floodplain
WQ
Arc Hydro
Permitting
Arc Hydro Database Definition
A geospatial and temporal data model for water
resources that operates within ArcGIS
 Five key conceptual areas

–
–
–
–
–
Drainage
Flow network
Hydrography
Channel description
Time series
Arc Hydro Schema
Drainage
Network
Flow
HydroFeatures
Time
Time Series
Hydrography
Channel
Arc Hydro Data Model
Arc Hydro Data Model Details
Arc Hydro
Framework
!(
!(
!(
!( !(!(
!( !(
!( !(
!(
!(
!(
!( !(
!(
!(
!( !(
!(
!(
!(
!( !(
!(
!(
!(
!(
!(
!(
!(
!(
!(
!(
!(
!( !(
!(
!(
!(
!(
!(
!(
!(
!(!(
!(
!(
!(!(
!(
!(!(
!(
!(
!(
!(
!(
!(
!(
!(!
(!(
!(
!(
(!
(!!(
!(
!(
!(
!(
Arc Hydro Key Fields

Few predefined fields/attributes
– Identification/relates
» HydroID, NextDownID, DrainID, JunctionID,
FeatureID, …
» HydroCode, ReachCode, CSCode, …
– Measures
» LengthKm, AreaSqKm
» LengthDown, DrainArea
– Auxiliary
» FType, Name, Flowdir, …
Relationships

Establish a formal (geodatabase) relationship
between two feature (object) classes using
predefined ID properties.
– HydroID-based (e.g. NextDownID, JunctionID,
DrainID)
» “HydroJunctionHasWaterbody”
» “HydroJunctionHasWatershed”
» “HydroJunctionHasMonitoringPoint”
» “MonitoringPointHasTimeSeries”
Relationships (an example – “HydroJunctionHasWaterbody” - definition)
Relationships (an example – “HydroJunctionHasWaterbody” - design)
Relationships (an example – “HydroJunctionHasWaterbody” - use)
Geometric Network
Establishes connectivity between core feature
classes
 Hydro edges (lines through which water flows) and
junctions (confluences, other points of interest)
 Other feature classes connected to junctions
through relationships (e.g.
HydroJunctionHasWatershed)
 Allows upstream/downstream tracing (and other
out of box ArcGIS network functionality)

Connecting to time series
Flow
Junction
DrainagePoint
HydroID
FeatureID
Time
TimeSeries
HydroPoint
CrossSection
FeatureID of time series
is HydroID of the feature
the time series describes
Time Series Data Structure
Nexrad Radar Rainfall
Arc Hydro data in Space and Time
Additional Time Series Components
Arc Hydro Tools
Extending Arc Hydro Data Model
Arc Hydro is by design a starting point for
complex database design
 Arc Hydro data model can be extended with
additional feature classes and/or attributes (or
some Arc Hydro feature classes can be ignored)
 Use additional GIS data sources (GRID & TIN)
 (Basically use anything available in ArcGIS)
 Use all existing IDs and tools to minimize
duplication of effort

Extending Arc Hydro Data Model
More application
specific “stuff”
GeoRAS Data Model - Schema
Numeric modeling support
Embedded modeling (external dlls, VB, …)
 Direct db modeling support
 XML driven import/export process

Generic data exchange principle
N
RAS
SWMM
MIKE 11
FLDWAV
MIKE 21
XML
HMS
Other …
GIS
2*N
Bi-directional
Where’s Arc Hydro ?

Hydro model page at:
support.esri.com/datamodels

Arc Hydro home page at GIS Water
Resources Consortium at:
www.crwr.utexas.edu/giswr/hydro

Dr.Maidment’s home page at:
www.ce.utexas.edu/prof/maidment
Phase II of Arc Hydro

More Tools
– Time series, ID management, Terrain preprocessing, ...
Data model changes – update to time series component,
groundwater
 Training (14 so far)
 Status

– Self-sustaining

Get involved into Consortium activities
– Meetings
– Contributors
– Personal communication
– Projects
Describing the hydrologic cycle
Atmospheric –– Land surface
Arc Hydro
surface water
Drainage System
Hydro Network
Flow
Hydrography
Channel System
Time
Arc Hydro
groundwater
Hydrogeologic unit
Layers
Borehole
Solid
Time Series
Arc Hydro GW data model objective

Extend Arc Hydro data model to include representation
of groundwater systems

Goals:
–
–
–
–
Support representation of regional groundwater systems
Support representation of site scale groundwater studies
Enable the integration of surface water and groundwater data
Connect to groundwater modeling software
Integration of surface water and
groundwater models
Applying Arc Hydro
Many Aspects of Arc Hydro
Database design
Marketing
Tools
Application
“Standard”
Development environment
Saxe, John Godfrey, 1963, “The Blind Man and the
elephant”, New York: Whittlesley House
Elephant illustration ©2002 Jason Hunt
www.naturalchild.org/jason
Applying Arc Hydro
Extension of Arc Hydro data model for support of
water resources applications
 Addition of features and feature classes
 Addition of functionality (tools)
 Various entities

– ESRI
– CRWR (SFWMD, SARA, WAM, …)
– Other (DHI, USGS, OMNR, SJRWMD, …)
Applying Arc Hydro (ESRI)

Current activities:
– River hydraulics & hydrology
» HEC-GeoRAS and FLDWAV
» HEC-GeoHMS
–
–
–
–
–
–
StreamStats
So.Cal fires debris flow predictions
DEM Editing tools
NHD in Arc Hydro
SWFWMD
ApFramework
River Hydraulics in 8.*

Work with HEC on porting the ArcView 3
GeoRAS solution to ArcGIS platform.
– Fully support RAS 3.0 functionality
– New (improved) UI
– Additional spatial data input
» Levees, ineffective flow areas, …
» Terrain definition by TIN and GRID
– XML data I/O
Will be released as HEC “product”
 Extension of Arc Hydro data model

River Hydraulics in 8.*

Finalized initial development
– Beta 6 released

To be done
– Final tweaks
– Documentation and online help
Support for FLDWAV (NWS)
 TIN intersection issues (TIN building with
close-by nodes)

River Hydraulics in 8.*
Export
Modeling
Preprocessing
GeoRAS
Visualization
Postprocessing
Import
Hydrology in 8.*

Work with HEC on porting the ArcView 3
GeoHMS solution to ArcGIS platform.
–
–
–
–

Fully support HMS functionality (GeoHMS 1.1)
New (improved) UI
Geodatabase implementation
XML data I/O
Status
– GeoHMS – work in progress, May timeframe for beta AWRA in Nashville)
StreamStats (USGS)
Implementation of USGS regression equations for
flow computations at ungaged locations (WDNR
ArcView 3 implementation)
 Web based application (and desktop)
 Status – prototype for ID completed, work on
several other States
 Phase II contracted
 Full implementation in Arc Hydro – all additional
GIS functionality is rolled-into Arc Hydro

StreamStats (USGS)
Functionality:
–
–
–
–
–
Select point of interest
Delineate watershed
Extract watershed characteristics (area, CN, …)
Send to NFF and get results back
“Publish” results
StreamStats (USGS)
2) Delineate watershed
1) Select area
3) Get results
So.Cal Fires Debris Flow Predictions

Implement USGS debris flow prediction model
within ArcGIS environment
– Peak flow
– Probability of occurrence
– Custom regression calculator

Built on top of Arc Hydro and StreamStats
functionality for watershed delineation and
characterization
– Generalization of characteristics extraction

New functionality rolled-into Arc Hydro
So.Cal Fires Debris Flow Predictions
DEM Editing Tools (HEC)

Tools for micro-editing of DEM (grid)
– Develop “hydrologicaly”-correct DEM
Status – application delivered to HEC
 Functionality

–
–
–
–
Raise or drop a point of interest
Burn/fence local lines/polys
DEM QC functions
DEM assembly
DEM Editing Tools (HEC)
NHD in Arc Hydro (FS/USGS)

Editing application for NHD data (NHDinGeo)
– Process-driven (workflow)





Status – development underway, completion by
end of May
NHDinGeo data model completed
NHDinGeo and NHDinGeoARC data being
generated
Return to coverage model required
(NHDinGeoARC)
Work on making NHDinGeo Arc Hydro compliant
NHD in Arc Hydro (FS/USGS)
SWFWMD
Implementation of Watershed Modeling
Database in Arc Hydro framework (from
coverages into geodatabase)
 Key elements:

– GIS database design for support of watershed
management program
– Additional Arc Hydro tools for management of
“bombing range” terrain type
– Enterprise – project geodatabase interaction
issues
Common threads
Use of existing data model, tools, and techniques
(Arc Hydro) as a base for development
 Economy in development

–
–
–
–
Existing tools (functionality consolidation)
Same coding core (ApFramework)
Same configuration methodology (XML)
Same model I/O approach (XML)
Q&A