Arc GIS Hydro Data Model David R. Maidment Director, Center for Research in Water Resources University of Texas at Austin CRWR

Arc GIS Hydro Data Model

David R. MaidmentDirector,

Center for Research in Water Resources

University of Texas at Austin

CRWR

GIS in Water Resources Consortium

Bringing together these two communities by using a common geospatial data model

http://www.crwr.utexas.edu/giswr

GIS

CRWRCRWR

Water Resources

ArcGIS Hydro Data Model

Hydrography Hydrology

Hydrography

“The description, study,and charting of bodies of water, such as rivers, lakes and seas”

Hydrology

“A science dealing with the properties, distribution, and circulation of water on the surface of the land, in the soil and underlying rocks, and in the atmosphere”

Geodatabase Book Series

General Geodatabasein ArcInfo 8

Geodatabasemodels forapplicationareas

CD-ROM at back of book

ArcGIS Hydro

UML diagrams, Repository,Example Geodatabases

UML

Jacobson

ObjectoryMeyer Pre- and post-conditions

Harel State charts

Wirfs-Brock Responsibilities

Fusion Operation descriptions, message numbering

Embly Singleton classes

Gamma et al. Frameworks, patterns, notes

Schlaer-Mellor

Object life cycles

Odell Classification

Rumbaugh

OMT

Booch Booch method

Unified Modeling Language

Source: T. Quatrani, Visual Modeling with Rational Rose and UML, p.6.

ESRI Provides Vanilla Objects

esriCoreRow.1esriCoreObject.1esriCoreFeature.1esriCoreSimpleJunctionFeature.1esriCoreComplexJunctionFeature.1esriCoreSimpleEdgeFeature.1esriCoreComplexEdgeFeature.1

Feature

NetworkFeature

JunctionFeature EdgeFeature

SimpleJunction ComplexJunction SimpleEdge ComplexEdge

Object

Row

2..* *

Encapsulation

X: 79 W

Y: 34 N

Z: 185 m

PointFeature

setCoords( X, Y, Z )queryCoords( X, Y, Z )

Example of user interaction with an object --

ArcGIS Hydro Components

«FeatureDataset»ArcGIS Hydro Features

ArcGIS Hydro Features::Relationships

Hydro Objects

ArcGIS Hydro Features::Channel Features

ArcGIS Hydro Features::Hydro Features

ArcGIS Hydro Features::Hydro Network

Hydro Domains

ArcGIS HydroCore

Model Packages

HydroFeatures

Hydro Feature classes are sets of points, lines or areas that describe water features of the landscape.



Hydro Objects




Hydro Domains

HydroFeaturesHydrofeatures inherit from the ESRI Feature class

+Shape : esriFieldTypeGeometry

ESRI Classes::Feature«SubtypeField» -FType : esriFieldTypeInteger-Name : esriFieldTypeString

HydroFeature

Hydro Points, Lines, AreasThese are subclasses of HydroFeature

Abstract superclass (has no objects)

Instantiable Subclasses (can have objects)


ESRI Classes::Feature«SubtypeField» -FType : esriFieldTypeInteger-Name : esriFieldTypeString

HydroFeature

-LocationID : esriFieldTypeInteger-IncludeOnNetwork : IsNetworkFlag = 1

HydroPoint{GeometryType = esriGeometryPoint,

HasZ = True}

-ReachID : esriFieldTypeInteger-IncludeOnNetwork : IsNetworkFlag = 1

HydroLine{GeometryType = esriGeometryPolyline,

HasM = True,HasZ = True} -ReachID : esriFieldTypeInteger

-OutletOID : esriFieldTypeInteger-IncludeOnNetwork : IsNetworkFlag = 1

HydroArea{GeometryType = esriGeometryPolygon,

HasZ = True}



HasZ = True}

-OutletOID : esriFieldTypeInteger

SeedPoint

MonitoringPoint

Structure

UserPoint

FlowChangePoint

HydroPoints

SeedPoint – outlet cell for DEM watershedMonitoringPoint – Gage or sampling locationFlowChangePoint – Withdrawal or dischargeStructure – Dam, bridge, wier, ….UserPoint – any other point of interest

Add more attributes

Attributes of HydroPoint



HasZ = True}-LocationOID : esriFieldTypeInteger-TSDateTime : esriFieldTypeDate-TSValue : esriFieldTypeDouble

TimeSeries

Point with (x,y,z) coordinates (default z = 0)

LocationID links points toassociated time series of measured or calculated data

IsNetworkFlag = 1 means pointis included in the HydroNetwork,(converse is IsnetworkFlag = 0)

Seedpoint

A seedpoint locates the center of the outlet cell of a DEM

watershed

OutletOID links this point to thecorresponding OutletJunction on

the Hydronetwork

Since the seedpoints are just upstream of the confluence,they unique identify separate upstream drainage areas 1 and 2

1

1

2

2

confluence

Feature Types – Coded Value Domains

«SubtypeField» -FType : esriFieldTypeInteger-Name : esriFieldTypeString

Hydro Features::HydroFeature


Hydro Features::HydroLine

-FType : StreamRiverType = 46000

StreamRiver«Subtype»

A coded value domain is anattribute which can take ononly one of a specific set of coded values

The ArcGIS Hydro data model has no fixed Ftype definitionsThose shown here are from the National Hydrography Dataset

NHD Feature Types


Hydro Features::HydroLine

-FType : PipelineType = 42800

Pipeline

-FType : StreamRiverType = 46000

StreamRiver

«Subtype»

«Subtype»

+FieldType = esriFieldTypeInteger+MergePolicy = esriMPTDefaultValue+SplitPolicy = esriSPTDefaultValue+Default = 42800+WaterAquaductAtOrNearSurface = 42801+WaterAquaductElevated = 42802+WaterAquaductUnderground = 42803+WaterAquaductUnderwater = 42804+WaterGeneralCaseAtOrNearSurface = 42805+WaterGeneralCaseElevated = 42806+WaterGeneralCaseUnderground = 42807+WaterGeneralCaseUnderwater = 42808+WaterPenstockAtOrNearSurface = 42809+WaterPenstockElevated = 42810+WaterPenstockUnderground = 42811+WaterPenstockUnderwater = 42812+WaterSiphon = 42813

«CodedValueDomain»PipelineType

NHD has ~ 52 Feature types, two of which are Stream/River and Pipeline

HydroLines

• ReachID – label for addressing and linear referenceing• IsNetworkFlag = 1 means include this line in the network


HydroFeature


HydroLine{GeometryType = esriGeometryPolyline,

HasM = True,HasZ = True}

SyntheticStream

Hydrolines inherit Ftype and Name

A special class of Hydrolines for storing thevectorized streams delineated from DEMs

HydroArea«SubtypeField» -FType : esriFieldTypeInteger-Name : esriFieldTypeString

HydroFeature

-ReachID : esriFieldTypeInteger-OutletOID : esriFieldTypeInteger-IncludeOnNetwork : IsNetworkFlag = 1

HydroArea{GeometryType = esriGeometryPolygon,

HasZ = True}

WaterbodyA Waterbody is a special class of HydroArea defining water bodies.A single water body Reach may

contain many HydroArea Features

Outlet to HydroNetwork

Drainage Areas

-ReachID : esriFieldTypeInteger-BasinID : esriFieldTypeInteger

Catchment

-HRUID : esriFieldTypeInteger-WatershedID : esriFieldTypeInteger

HydroResponseUnit

-BasinID : esriFieldTypeInteger-WatershedID : esriFieldTypeInteger

Watershed

-BasinID : esriFieldTypeInteger

Basin

-OutletOID : esriFieldTypeInteger-AreaInSquareMeters : esriFieldTypeDouble

DrainageArea{GeometryType = esriGeometryPolygon,

HasZ = True}


HydroFeature

DrainageArea is a superclass For any kind of drainage area• OutletOID defines the outlet to theHydroNetwork• AreaInSquareMeters specifies areaindependent of map projection

Subclasses: Catchment, Watershed,Basin, HydroResponseUnit

Catchment


Catchment

A catchment is the localdrainage area of a Reach

Shoreline Catchment-ReachID : esriFieldTypeInteger-BasinID : esriFieldTypeInteger

Catchment

The local drainage area of a shoreline reach

Its drainage enters a waterbody directly without passing through a river or stream

Waterbody Catchment

Waterbody is a catchmentand separate catchmentsare defined for shorelines

A single catchment polygonincludes both the waterbody and its local drainage area

Two ways of defining catchments for water bodies


Catchment

Watershed

Watersheds defined for pointson the HydroNetwork

Watershed defined for a Waterbody


Watershed

The Watershed class is used for any subdivision of the landscape into drainage units

Basin-BasinID : esriFieldTypeInteger

Basin

A standardized set of watersheds defined for the purposes of formal subdivision of the landscape into labeled drainage areas e.g. Watershed Boundary Dataset

This example shows 8-digit HUC boundaries so BasinID = HUC8

Basin Outlet

Basins contain Catchments and Watersheds


Catchment


Watershed

HydroResponseUnit-HRUID : esriFieldTypeInteger-WatershedID : esriFieldTypeInteger

HydroResponseUnit

The HydroResponseUnit class be defined by soil or land use polygons, by climate or rainfall cells, by political or administrative boundaries, by aquifer or drainage boundaries, or by any combination of such areas.

HRUs definedby intersectingNexrad rainfall cellsand catchments

HRU’s account for the vertical water exchange between the atmosphere, surface water and groundwater

HydroNetwork «FeatureDataset»ArcGIS Hydro Features


Hydro Objects




Hydro Domains

The Hydro Network is the backbone of the ArcGIS Hydro data model. It defines the connections among points, lines and areas to describe the pathways of water flow through the landscape

HydroNetworkThe HydroNetwork is built from ESRI Network Feature classes

ESRI Classes::ComplexEdgeFeature ESRI Classes::SimpleJunctionFeature

-ReachID : esriFieldTypeInteger-LengthInMeters : esriFieldTypeDouble-LengthDownstream : esriFieldTypeDouble-FlowDirection : HydroFlowDirections = 1«SubtypeField» -HydroEdgeType : esriFieldTypeInteger = 1

HydroEdge{GeometryType = esriGeometryPolyline,


OutletJunction{GeometryType = esriGeometryPoint,

HasZ = True}

-NetworkType : esriNetworkType = esriNTUtilityNetwork

«GeometricNetwork»HydroNetwork

Two key classesHydroEdge and OutletJunction

Geometric Network

A Geometric network is defined by:• geometry – (x, y) of edges, junctions• connectivity – junction-edge-junction

-NetworkType : esriNetworkType = esriNTUtilityNetwork

«GeometricNetwork»HydroNetwork

Generic junctions(created automatically)

OutletJunctions

HydroEdges

HydroEdgeESRI Classes::ComplexEdgeFeature




Color andSelect edges

A HydroEdge is a ComplexEdge Feature so it can haveinterior junctions

OutletJunction

The OutletJunction of a Watershedis located on the Hydronetwork asclose as possible to the seedpointlocation on the DEM

OutletJunction{GeometryType = esriGeometryPoint,

HasZ = True}

Seedpoints as OutletJunctions

10-digit watersheds19 seedpoints

NED-H Catchments (~ 8km2)1026 seed points

The same concept can be used to connect drainageareas to the Hydronetwork regardless of spatial scale

OutletJunction to Watershed Relationship

Hydro Network::OutletJunction -Outlet

1

-Watershed

1

OutletToWatershed -BasinID : esriFieldTypeInteger-WatershedID : esriFieldTypeInteger-OutletOID : esriFieldTypeInteger

Hydro Features::Watershed

1 1

Outlets are 1:1 related to watersheds through the ObjectId of the Outlet (OutletOID).

Traces on the HydroNetwork identify OutletJunctions, and by invoking the relationship, the associated Watersheds are identified

HydroEdgeTypes-ReachID : esriFieldTypeInteger-LengthInMeters : esriFieldTypeDouble-LengthDownstream : esriFieldTypeDouble-FlowDirection : HydroFlowDirections = 1«SubtypeField» -HydroEdgeType : esriFieldTypeInteger = 1



-HydroEdgeType : esriFieldTypeInteger = 1

FlowEdge«Subtype»


VirtualFlowEdge«Subtype»


ShorelineEdge«Subtype»

HydroEdges have three subtypes: FlowEdges, VirtualFlowEdges and ShorelineEdges

Flow Lines for Water Modeling

A Flow Line isa linear sequence offlow edges and/orvirtual Flow Edges

Strictly speaking, the flowline is located at theCenter of Flow but its locationis usually approximated to the channel centerline or thalweg

Equations of motion are written in termsof flow distance for 1-D flow models

Flow Network

HydroNetwork = Flow Network + Shorelines

A flow network is a connected set of flow lines

When a waterbody is placed on the network, it can berepresented by Virtual Flow Edges, by Shoreline Edgesor by both edge types

Flow Direction

2

1




+FieldType = esriFieldTypeInteger+MergePolicy = esriMPTDefaultValue+SplitPolicy = esriSPTDefaultValue+Unknown = 0+WithDigitized = 1+AgainstDigitized = 2+Bidirectional = 3

«CodedValueDomain»Hydro Domains::HydroFlowDirections

Flow Direction in the HydroNetworkis downstream toward a sink

Flow direction can be storedas an edge attribute by comparingit with the direction in which the edge was digitized as given by the order of its vertices

HydroEdge Attributes




• ReachID labels the HydroEdges for linear referencinge.g. RchComID linked to Rch_Code in NHD• LengthinMeters stores the length of the edge irrespectiveof map projection• LengthDownstream stores the length to a downstreamreference point, such as the mouth of the river or the basin outlet

Hydro Objects

An object has an ObjectId and attributes but no spatial coordinates

• HydroNetwork Objects – Reaches and

Hydrographic Units

– Point and Line events

• CrossSection Objects– Point and Line events

• Temporal Objects



Hydro Objects




Hydro Domains

+OBJECTID : esriFieldTypeOID

ESRI Classes::Object

Reach +OBJECTID : esriFieldTypeOID


-ReachID : esriFieldTypeInteger-HydroUnitOID : esriFieldTypeInteger

Reach

A Reach is an expanse of water uniquely labeled for hydrographic purposes (a river reach, waterbody or shoreline).

Reaches inherit from ESRI class Object

ReachID

Reach to HydroEdge Relationshipconnects Reach to HydroEdge to identify Features in the Reach

1294798


Hydro Objects::Reach-ReachID : esriFieldTypeInteger-LengthInMeters : esriFieldTypeDouble-LengthDownstream : esriFieldTypeDouble-FlowDirection : HydroFlowDirections = 1«SubtypeField» -HydroEdgeType : esriFieldTypeInteger = 1

Hydro Network::HydroEdge

-Reach1 -HydEdge *

RchToHydEdge

A reach is an Object, which means that it has an ObjectID andattributes but does not have spatial coordinates

1 * (many)


Reach


Catchment

Waterbody Reach catchment

River Reach catchment

Reach Catchmentsdeveloped using the NED-H Flow Direction Grid, and Reach

Features as outlet zones in the Grid Watershed function

Hydrographic Unit



-Name : esriFieldTypeString

HydrographicUnit

A HydrographicUnit is an object describing a set of connected reaches, such as a river, or a section of coastline

East Fork of the Trinity River


Hydro Objects::Reach

-Name : esriFieldTypeString

Hydro Objects::HydrographicUnit

-HydroUnit1

-Reach*

RchCollectionHydrographic Units are connected to Reaches through a 1 to many relationship

Linear Referencing(Requires ArcInfo 8.1)

Where are we on a line?

0%

100%

Linear Referencing usingPercent distance frombottom end of reach

(NHD approach)

Linear Referencing using “Chainage” from the Upper End of the Reach in meters (European approach)

Measure in kilometers

pMSeg.SetAndInterpolateMsBetween 0, ([Shape_Length] /1000)

Measure in km frombottom end of line(like river miles or Kilometers)

HydroEvent Objects



-EdgeOID : esriFieldTypeInteger-ReachID : esriFieldTypeInteger-GroupID : esriFieldTypeInteger-GroupName : esriFieldTypeString

HydroEvent

-PointMeasure : esriFieldTypeDouble

HydroPointEvent-FromMeasure : esriFieldTypeDouble-ToMeasure : esriFieldTypeDouble

HydroLineEvent

Events can be definedusing measure defined on each HydroEdge or eachReach (easiest if eachReach is one Edge)

Sets of points orLine events can formGroups

Displaying Events

Channel Featuresrepresent 3-D river morphology



Hydro Objects




Hydro Domains

Mainly designed by MichaelBlongewicz, DHI, Nawajish Nomanand Jim Nelson, BYU, Tom Evans, HEC

Channel Features


ESRI Classes::Feature

-ReachID : esriFieldTypeInteger«SubtypeField» -ProfileLineType : esriFieldTypeInteger

ProfileLine{HasM = True,HasZ = True,

GeometryType = esriGeometryPolyline}-CrossSectionID : esriFieldTypeString-ReachID : esriFieldTypeInteger-CrossSectionType : esriFieldTypeInteger-ReachMeasure : esriFieldTypeDouble

CrossSection{GeometryType = esriGeometryPolyline,


ProfileLinesrun along the channel

CrossSections runtransverse to the channel

Each vertex has(x, y, z, m)

ProfileLines and CrossSections sharegeometry, for ease of editing the Z

value (elevation) at their intersection.

ProfileLinesHydroEdge = “Thalweg” ProfilelineReachID links Channel to Network

-ReachID : esriFieldTypeInteger«SubtypeField» -ProfileLineType : esriFieldTypeInteger

ProfileLine{HasM = True,HasZ = True,

GeometryType = esriGeometryPolyline}

-ProfileLineType : esriFieldTypeInteger = 1

Thalweg«Subtype»


RightBank«Subtype»


LeftBank«Subtype»


RightFloodLine«Subtype»


LeftFloodLine«Subtype»

“Left” and “Right” are determinedlooking Downstream

5 Subtypes

CrossSections-CrossSectionID : esriFieldTypeString-ReachID : esriFieldTypeInteger-CrossSectionType : esriFieldTypeInteger-ReachMeasure : esriFieldTypeDouble

CrossSection{GeometryType = esriGeometryPolyline,


+FieldType = esriFieldTypeInteger+MergePolicy = esriMPTDefaultValue+SplitPolicy = esriSPTDefaultValue+3DType = 0+PolyLineType = 1+LineType = 2+PointType = 3+LocationType = 4

«CodedValueDomain»Hydro Domains::CrossSectionTypes

• ReachID and ReachMeasuregive the River Stationing or Chainage for Hydraulic Models• CrossSectionType specifies how it was developed

CrossSection Geometry+OBJECTID : esriFieldTypeOID


-CrossSectionID : esriFieldTypeInteger-PointMeasure : esriFieldTypeDouble-PointElevation : esriFieldTypeDouble

CrossSectionGeometry

CrossSectionGeometryObject stores (m,z) coordinates when (x, y)are unknown

Large amounts of historical CrossSection data in this form

CrossSectionEvents



-CrossSectionID : esriFieldTypeString

CrossSectionEvent

-PointMeasure : esriFieldTypeDouble

CSPointEvent

-FromMeasure : esriFieldTypeDouble-ToMeasure : esriFieldTypeDouble

CSLineEvent

Objects with attributes ofpoints or linear segments of the CrossSection

# U.S. Geological Survey NWIS data# Created on Thu Jul 20 14:39:35 2000# Columns in this file (modified from original) include:# station USGS station number# datetime Date or date and time of reading# discharge Stream discharge, in cubic feet per second# stage Water surface elevation above station vertical datum, in feet# 08176500 STREAM GAGE FOR GUADALUPE RIVER AT VICTORIA, TXstation datetime discharge stage08176500 20000701 647 6.4608176500 20000702 610 6.3308176500 20000703 596 6.2908176500 20000704 577 6.2208176500 20000705 480 5.8508176500 20000706 419 5.62

Time Series Objects

• LocationID links to the Feature• TSDateTime specifies date (and time of day)• TSValue gives the data value (may be multiple data values)

-LocationID : esriFieldTypeInteger-TSDateTime : esriFieldTypeDate-TSValue : esriFieldTypeDouble

TimeSeries



Mainly designed by Scott Morehouse and David Arctur, ESRI, and Michael Blongewicz, DHI

TimeSeriesFeature Class - CatchmentStations

F_ID Shape CatchmentName

101 Point Catchment1



Time Series Class - CatchmentRainfall

Feature_ID TimeStamp Rainfall103 1989-03-30 01:00:00 0.23103 1989-03-31 01:00:00 0.02103 1989-03-01 01:00:00 3.65103 1989-04-02 01:00:00 0.00103 1989-00-03 01:00:00 0.00103 1989-04-04 01:00:00 1.12



Time Series Class - CatchmentEvaporation

Feature_ID TimeStamp Evaporation103 1989-03-30 01:00:00 0.055103 1989-03-31 01:00:00 0.067103 1989-03-01 01:00:00 1.198103 1989-04-02 01:00:00 1.101103 1989-00-03 01:00:00 0.719103 1989-04-04 01:00:00 0.011



Feature Class - MonitorPoints

F_ID Shape Station_ID

101 Point 08154700

102 Point 08154709

Time Series Class - Discharge

StationID DateTime Discharge08154700 2000-07-01 12:00:00 580.0008154700 2000-07-02 12:00:00 591.00

StationID DateTime Discharge08154709 2000-07-03 12:00:00 477.0008154709 2000-07-04 12:00:00 465.0008154709 2000-07-05 12:00:00 461.00

-LocationID : esriFieldTypeInteger-TSDateTime : esriFieldTypeDate-TSValue : esriFieldTypeDouble

TimeSeries



HasZ = True}

Sources of Time Series DataTime Item

SQLDatabases

Time ItemTime Item

ItemTime

Internet WebServers

SQL

GeoDatabase

Time Item

Text filesTimeSeries

Connection

SQ

L

SQL

SQ

L

ArcGIS Hydro USGS NWISEPA Storet

Paper on this on Wednesday by Tim Whiteaker

Documents

Arc GIS Hydro Data Model David R. Maidment Director, Center for Research in Water Resources University of Texas at Austin CRWR