1. ArcGIS Hydro Data Model
Design principles for the data model
Data model components
Time series
Arc Hydro tools

2. GIS in Water Resources Consortium
CRWR
GIS in Water Resources Consortium
GIS
Water Resources
Bringing together these two communities by using a common geospatial data model

3. Trends During 1990’s
Standardized GIS data sets were produced for hydrology
Internet became a major conduit for data distribution
Most US hydrologic models had GIS interfaces constructed for them
Microsoft COM protocol became a standard (Word, Powerpoint, Excel, Visual Basic for Applications)
ESRI adopted COM for ArcGIS

4. Trends during 2000’s
Relational databases (Access, Oracle,…) will be the standard for data storage
Geospatial and temporal data for hydrology will be more formally synthesized
Use of component technologies will blur the line between applications (hydrology-hydraulics-water quality)
Increasing use of real-time applications
More use of terrain surfaces e.g. LIDAR

5. ArcGIS Data Models Facilitate a process with the user community
Capture the essential, common data model for each discipline
Build a database design template that works well with ArcGIS
Build on experience, not a standards exercise
Share the model on ArcOnline

6. Essential Data Model Organization B Organization A Organization D
Organization C
Something in common
The data model for a business organization tends not to change greatly over time unless the business organization changes the fundamental way that it does business

7. Model Definition
Develop a data model to support Hydrology and Hydrography
Link the vector and raster worlds
Understand producer and consumer needs
Exercise with real data to validate the model
Use a geometric network for faster tracing and data quality validation

8. Evolution of the Model Hands-on experience was key to evolution
We have somehow struggled through the process and found new ways of managing Hydro Data
Consistent structure
Varying detail
Multi-purpose
Common tools and techniques (Patterns)
You will hear interest and excitement about this in the presentations today

9. Acknowledgements CRWR – ESRI team
Many people and organizations have contributed to the development of Arc Hydro. We thank you!!
CRWR – ESRI team
BYU, CDM, DHI, Dodson, EPA, HEC, LCRA, NHD, TNRCC, TWDB, USGS
Many individuals in academia, government and industry

10. ArcGIS Hydro Data Model
Hydrography
Hydrology

11. ArcGIS Hydro Data Model
Drainage
Network
Flow
Time
Time Series
HydroFeatures
Hydrography
Channel

12. Data Model Based on Inventory
NHD Points
Make an inventory of all features of a given type in the region
NHD Lines
NHD Areas
Gages
What is it?
Where is it?
Dams
Bridges

13. Data Model Based on Behavior
Follow a drop of water from where it falls on the land, to the stream, and all the way to the ocean.

14. Integrating Data Inventory using a Behavioral Model
Relationships between
objects linked by tracing path
of water movement

16. Arc Hydro Implementation
Geodatabase
Feature Dataset
Feature Class
Geometric
Network
Object Class
Relationship
Workspace

17. Arc Hydro Design Principles
Classification
Partitioning, typing, and naming of classes
Attribution
Feature description, including time series
Association
Relating features using key attributes
Navigation
Following water movement from feature to feature

18. Classification Partitioning Typing Naming
Like features are grouped into components (Network, Drainage, …)
Typing
Object, Feature, Network feature
Naming
Common names if possible, defined by a glossary

19. Classification Hierarchy
Text descriptor e.g. FType
Coded Value Domain e.g. FDir
Subtypes – separate classes with same attributes e.g. HydroEdge
Subclasses - separate classes with different attributes e.g. HydroPoint
FType = “Stream/River”
1 = “WithDigitized”, 2 =“AgainstDigitized”,..
EdgeType = 1 for Flowline, = 2 for Shoreline
Dam, Bridge, Monitoring Point, …
Light
Heavy

20. Two-Way Classification: FTypes of Subtypes
EdgeType = 1 FlowLine
FType =
“Stream/River”
“Canal/Ditch”
“Pipeline”
“Connector”
“Waterbody FlowLine”
EdgeType = 2 Shoreline
FType =
“Bankline”
“Shoreline”
“Coastline”

21. Attribution Minimal attribution in the model
Assume user will add more
Attribute Names are all 10 characters or less so they are not truncated when exported to Shapefiles
Standard conventions
ID is a long integer
Code is a string

22. Hydro Features
Every Arc Hydro feature is a Hydro Feature with a HydroID and HydroCode
HydroID = Class Number + ObjectID e.g is object 13 in class 12 (unique within a geodatabase)
HydroCode = HydroID + Geodatabase name e.g. Mybasin (unique within a set of geodatabases)

23. Association
An association is established using key fields in two separate tables
Can build relationship if necessary
Hydro Assocation – HydroID of one class is an attribute of another class
JunctionID (Drainage Outlets)
FeatureID (Time Series)
NextDownID (Downstream feature)

24. Navigation
Navigation means tracing the movement of water downstream or upstream
Dendritic Navigation – using NextDownID within a single feature class
Network Navigation – using Network Analyst tracing tools on Hydro Network
Schematic Navigation – using SchematicLink and SchematicNodes to connect features in several classes

25. National Hydro Data Programs http://www. crwr. utexas
National Elevation Dataset
(NED)
National Hydrography Dataset
(NHD)
Elevation Derivatives for
National Applications (EDNA)
Watershed Boundary Dataset

26. How do we combine these data?
Digital Elevation
Models
Watersheds
Streams
Waterbodies

27. An integrated raster-vector database

28. Where Does the Raindrop Go?
Dale Honeycutt’s concept, May 2000

29. Water Flows from an Area to a Line
Problems with this:
Areas and lines are not always consistent with one another.
Sometimes many lines within one area.

30. How to Connect Areas to the Hydro Network? Areas connect
Regardless of where the drop falls in the area,
its runoff is on the network at the outlet point
Areas connect
to lines at points
Outlet Points

31. Area to Stream Outlet Connectivity

32. ArcHydro and ArcFM Water
Water Infrastructure
Water distribution
Wastewater collection
Storm sewers
Arc Hydro
Natural water system
Catchments drain to storm sewer inlets
Storm sewers discharge to streams

33. Area to Sewer Inlet Connectivity

34. Schema A schema is the structure or design of a database.
A schema specifies the feature and object classes -- including their attributes and relationships -- of the geodatabase.

35. Repository
A repository is database that contains the schema information needed to create a geodatabase from a UML model created using a CASE tool.

36. ArcGIS Hydro Data Model
Design principles for the data model
Data model components
Time series
Arc Hydro tools

38. Arc Hydro Implementation
Geodatabase
Feature Dataset
Feature Class
Geometric
Network
Object Class
Relationship
Workspace

39. GIS in Water Resources Consortium ArcGIS Hydro Data Model
Network

40. Example - Holland

41. GIS in Water Resources Consortium ArcGIS Hydro Data Model
Hydrography

42. River networks
for 8-digit HUC
watersheds

44. GIS in Water Resources Consortium ArcGIS Hydro Data Model
Hydrography

45. GIS in Water Resources Consortium ArcGIS Hydro Data Model
Drainage

46. Watersheds of the US 2-digit water resource regions
8-digit HUC watersheds

47. Watershed Hierarchy Digit # 2 4 6 8 HUC 10 12 EDNA Available
In Progress

48. Watershed Boundary Dataset
National Program by USGS and USDA (NRCS)
Boundaries for 10- and 12- digit watersheds
First cut is by automated delineation from NED
Hand checked and edited
10-digit watersheds

49. National program by USGS and NWS
Elevation Derivatives for National Applications (EDNA
National program by USGS and NWS
5000 cell threshold on a 30m DEM (~ 8 km2 average drainage area)
~ 1 million catchments for US when completed
Includes grid derived products e.g. topmodel index

50. Area to Area Connectivity: SchematicLinks built using NextDownID

51. GIS in Water Resources Consortium ArcGIS Hydro Data Model
Channel

52. Pecan Bayou: Flood Hydrology and Hydraulics Study
by David Anderson (CRWR)

53. Pecan Bayou: Data Development Process
Hydrology
& Hydraulics
HEC-RAS
CRWR-
PrePro
HEC- HMS
Terrain
Model
HEC-
GeoRAS
Floodplain
Terrain Model
David Anderson, 2000

54. 3-D Polyline Z Measure (m) and Elevation (z) Values on Cross Sections

55. Channel Geometry using Arc Scene
Extract ProfileLines
and CrossSections
Begin with Contours
Build a Triangulated
Irregular Network
(TIN)
Demo

56. ArcGIS Hydro Data Model
Design principles for the data model
Data model components
Time series
Arc Hydro tools

57. Time Series Objectives
Store Metadata about each collection of time series values
What is measured
What units are used
Display and store Time Series Views
Rainfall for Gage
All data between years 2000 and 2001

58. Time Series Classes

59. TimeSeries Attributes
FeatureID – ID of spatial feature
TSTypeID – Identifies TS properties
TSDateTime - Timestamp
TSValue - Value
TSDesc – Property of particular record

60. TimeSeries Example

61. TSTypeInfo Attributes
TSTypeID – Identifies a set of TS properties
Variable – What is being measured or recorded
Units – The units that the data values are in
IsRegular – Values spaced at regular or irregular time intervals
TSInterval – Time interval between values (if regular)
DataType – The type of time series data
Origin – Values recorded or generated

62. More on DateType Inst-Value Inst-Cumulative Step-Cumulative
Step-Average
Step-Maximum
Step-Minimum

63. TSTypeInfo Example

64. Time Series Views Use Query Builder in ArcGIS
Save
Load
Provides Selective Views of Entire TS Table
Requires no extra functionality

65. Connecting to Time Series
DrainagePoint
Junction
Flow
HydroID
FeatureID
Time
TimeSeries
HydroPoint
CrossSection
FeatureID of time series
is HydroID of feature the
time series describes

66. National Water Information System (NWIS) http://water.usgs.gov
Web access to USGS water resources data in real time

68. ArcGIS Hydro Data Model
Design principles for the data model
Data model components
Time series
Arc Hydro tools

69. Arc Hydro Tools Code development being done jointly by ESRI and CRWR
Uses a standardized application framework for VB tools in ArcGIS
Fills in standard attributes in Arc Hydro data model
Will be published on GISWR web page and freely available

70. Application Framework
Tool for developers
Eases routine ArcGIS programming tasks
Provides standard look and feel to applications

71. Anatomy of Code

72. Streamlining Routine Tasks
Vs.

73. User-Interface Capabilities
Handles Basic Input/Output
Reduces development time by up to 50%
Provides a standard look and feel across different applications

74. Tool Updates “Repaired” NWIS tool (released)
Improved accuracy of NextDownstream Tool (development)
Added “Shortest Path to Sink” algorithm to LengthDownstream tool (development)
Exercise on ArcHydroLite being presented in class next week.

75. Overview Introduction Conceptual Framework Subtyping of Time series
Properties of Time series class
Applications

76. Arc Hydro NWIS Application
Custom Tool Retrieves NWIS Data
Time Series Table Built Automatically
Operates Within ArcMap GUI
Demo

77. ArcGIS Hydro Data Model
Drainage
Network
Flow
Time
Time Series
HydroFeatures
Hydrography
Channel

78. Open Architecture for Water Modeling
Interface 1
ArcGIS
Interface 2
Excel
Process
Engines
Temporal Data
Geospatial data
Interface 4
Custom Designed
Interface 3
Hydrologic Model

79. ArcGIS Interface to Model
LibHydro:
An HEC-1
subroutine
library converted
to a .dll
Interface written using VBA for ArcGIS

80. Excel Interface to Model
constructed
using VBA for
Excel

81. Hydrologic Model Hydrologic model constructed using
with a Visual Basic
interface calls
ArcObjects to
access Arc Hydro
data

82. Custom Interface e.g. Basins

83. Custom Interface (for several hydrologic models)

84. TIWSS Texas Integrated Water Simulation System
WRAP
Water Availability
SWAT
Water Quality
Arc Hydro
Geospatial and Temporal Data
Modflow
Groundwater
HEC Models
Flooding & Water Management