Water Models 2

41
Interface data models Model 1 Model 2 Model 3 GIS Geo Database Arc Hydro data model raphically Integrated Hydrologic Modeling Sy

Transcript of Water Models 2

Page 1: Water Models 2

Interfacedata models

Model 1

Model 2

Model 3

GIS

GeoDatabase

Arc Hydrodata model

Geographically Integrated Hydrologic Modeling Systems

Page 2: Water Models 2

Arc Hydro — Hydrography

Page 3: Water Models 2

Arc Hydro — Hydrology

Page 4: Water Models 2

Geographic Data Model

• Conceptual Model – a set of concepts that describe a subject and allow reasoning about it

• Mathematical Model – a conceptual model expressed in symbols and equations

• Data Model – a conceptual model expressed in a data structure (Logical data model, physical data model)

• Geographic Data Model – a data model expressed in a GIS database

Page 5: Water Models 2

Data Model Data Model based on based on Inventory of Inventory of data layersdata layers

Page 6: Water Models 2

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.”

R.M. Hirsch, USGS

Page 7: Water Models 2

Flow

Time

Time Series

Hydrography

Hydro Network

Channel System

Drainage System

Arc Hydro Components

Page 8: Water Models 2

Streams

Watersheds Waterbody

Hydro Points

Arc Hydro Framework Input Data

Page 9: Water Models 2

!(

!(

!(!(

!( !(!( !(!( !(!(

!(!(

!(!(!(!( !(!( !(!( !(

!( !(!( !( !(!(!(

!(

!(!( !(!(!( !(

!(!(

!(!( !(!(!( !( !(!(!( !(!(

!( !(!(!( !(!(

!(!(!(!(!(

!(

!(!(

!(

!(!(!(

!(

!(

!(

!(!(!(

!(

Feature

Waterbody

HydroIDHydroCodeFTypeNameAreaSqKmJunctionID

HydroPoint

HydroIDHydroCodeFTypeNameJunctionID

WatershedHydroIDHydroCodeDrainIDAreaSqKmJunctionIDNextDownID

ComplexEdgeFeature

EdgeType

Flowline

Shoreline

HydroEdge

HydroIDHydroCodeReachCodeNameLengthKmLengthDownFlowDirFTypeEdgeTypeEnabled

SimpleJunctionFeature

1HydroJunction

HydroIDHydroCodeNextDownIDLengthDownDrainAreaFTypeEnabledAncillaryRole

*

1

*

HydroNetwork

*

HydroJunction

HydroIDHydroCodeNextDownIDLengthDownDrainAreaFTypeEnabledAncillaryRole

HydroJunction

HydroIDHydroCodeNextDownIDLengthDownDrainAreaFTypeEnabledAncillaryRole

Arc Hydro FrameworkData Model

Page 10: Water Models 2

Hydro Network(NHD)

Basins Waterbody(NHD)

Arc Hydro Framework For South Florida

Hydro Points

Page 11: Water Models 2

Nexrad Radar Rainfall Map

Page 12: Water Models 2

Extended Arc Hydro Framework for South Florida

Arc HydroFramework

Extended Arc Hydro

RegionalSimulation

Model

OperationsDecision SupportSystem

Flood Modelingand

Management

HydroPeriodAnalysis

Framework for South Florida

Page 13: Water Models 2

1. Define the Data Themes in the Core Model

• Hydrographic lines• Water bodies• Drainage areas• Structures• Gages+ ……..

Who will produce and verify these data?Will National Hydrography Dataset be used?

Page 14: Water Models 2

2. Define the ODSS GIS Framework

• Select the ODSS waterbodies and structures from the core GIS framework

• Integrate water control units in GIS

• Define drainage area for each WCU

• Build interface data model for ODSS

• Build tools for 2-way linkage between ArcGIS and ODSS

Page 15: Water Models 2

Extended Arc Hydro Framework

Water body

Canal Segment

Lake Marsh Tidal

HydroEdge

HydroJunction

UncontrolledJunction

ControlledJunction

Structure

WCU Schematic Node

1..* 1

1..*

1

1

1..*

Arc Hydro UML for ODSS

Subtypes

Subtypes

1

WCU Schematic Link

Hydronetwork

Water Control Network

MonitoringPoint

Basin1..*

1

Page 16: Water Models 2

3. Define the Flood Modeling Framework

• Define drainage areas, channels and control structures to be included

• Define flood simulation model(s) to be used

• Design ArcGIS interface data model, if necessary

• Populate models with GIS data (Watershed analyst)

• Build tools for 2-way linkage between ArcGIS and Flood Models, if necessary

Page 17: Water Models 2

4. Define the RSM GIS Framework• Generalize GIS data needed

for RSM (linear referencing and event themes)

• Generate triangular mesh• Represent canal segments and

pseudocells in GIS• Define ArcGIS interface data

model for RSM• Build tools for 2-way linkage

between ArcGIS and RSM

Page 18: Water Models 2

5. Define GIS Functionality for Hydroperiod

• Define conceptual framework

• Convert to mathematical form

• Define data structures needed

• Build tools to execute model• Check against observed

points to verify analysis• Train the District staff!

Page 19: Water Models 2

6. Build the District Arc Hydro Framework

• Build the HydroNetwork

• Connect the drainage areas

• Connect the structures and monitoring points

• Integrate other themes (e.g. District RSM mesh?)

Page 20: Water Models 2

7. Define the Water Inputs

• Connect to the Nexrad data

• Connect to dbHydro for gage information

• Satellite information?• Climate information?• Water quality?

Page 21: Water Models 2

8. Build Information Flows Among Applications

Arc HydroFramework

Extended Arc Hydro

RegionalSimulation

Model

OperationsDecision SupportSystem

Flood Modelingand

Management

HydroPeriodAnalysis

Framework for South Florida

Page 22: Water Models 2

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

Master Plan for San Master Plan for San AntonioAntonio

Page 23: Water Models 2

Regional Watershed Modeling Master Plan Goals

• Develop new or incorporate existing hydrology, hydraulic and water quality models (“Bring the models together”)

• Provide GIS-based interfaces for models• Provide for maintenance of models and geospatial data• Develop standards for modeling and geospatial data• Regional Watershed Modeling System to assist in:

– flood mitigation planning– capital project prioritization

Page 24: Water Models 2

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

Page 25: Water Models 2

Arc Hydro and HEC-HMS

Arc HydroSchematic Network

HEC-HMSHydrologic

Model

Calculates Flows

Page 26: Water Models 2

Arc Hydro and HEC-RAS

Arc HydroChannel

Cross Sections

HEC-RASHydraulic

Model

Calculates Water Surface

Elevations

Page 27: Water Models 2

Flow Change PointsModels communicate with

one another through Arc Hydro at designated points

Page 28: Water Models 2

Nexrad Map to Flood Map in Model Builder FLO

ODPLAIN MAP

Flood map as output

Nexrad map as input

Model for flood flow

Model for flood

depth

HMS

Page 29: Water Models 2

Hydrologic Modeling within ArcGIS

• Reverse engineer the parameter values from calibrated hydrologic simulation models into the interface data model

• LibHydro – a library of hydrologic processing functions callable as a dll

• Schematic network processor to execute functions in the right order

Page 30: Water Models 2

Schematic Network

• Standard Arc Hydro data structure– Schematic Links– Schematic Nodes

• Type 1 Nodes and Links for Watersheds

• Type 2 Nodes and Links for Streams

• Type 3 for …..

Page 31: Water Models 2

Schematic Network Processes• Node processes

– Rainfall-runoff and pollutant loads on watersheds

– Summing flows or loads on streams

– Water quality in water bodies

• Link processes– Routing flows in streams– Pollutant losses in streams

Page 32: Water Models 2

LibHydro

• A Fortran subroutine library of hydrologic processes developed from HEC-1

• Packaged in LibHydro.DLL for operation under Visual Basic

• Transforms input time series to output time series• More details on GISHydro 2003 CD

Page 33: Water Models 2

Excess Calculation• Initial Loss and Constant Loss Rate function

Pick up a watershed HydroID = 2346 ImperviousAreaRatio = 0.0001 InitialLoss = 1.6 (mm) ConstantLossRate = 0.38 (mm)

Simulation Period: 7/21/97 – 7/23/97 (3 days) Time Interval: 15 minutes Time step: 4 * 24(hour) * 3(days) = 288

Excess calculation in Llano basin

0

2

4

6

8

10

7/21 7/22 7/23 7/24

Date

Prec

ipita

tion,

Exc

ess

(mm

/hr) Precip (mm)

Excess (mm)

Page 34: Water Models 2

Runoff Calculation• Snyder Unit Hydrograph

Pick up a watershed Watershed area: 266.5 (km2) SnyderCp: 0.8 SnyderTp: 5.58 (hr)

Hydrograph for Llano Basin

0

2

4

6

8

10

7/21

7/22

7/23

date

Prec

ipita

tion,

Ex

cess

(mm

/hr)

0

20

40

60

80

100

Runo

ff (m

3/s)

Runoff (m3/s)

Precip (mm)

Excess (mm)

Simulation Period: 7/21/97 – 7/23/97 (3 days) Time Interval: 15 minutes

Page 35: Water Models 2

Outflow Calculation• Add Baseflow module• Outflow = runoff + baseflow• Recession Ratio = 0.95, Threshold value = 2 (m3/s)

Hydrograph for Llano Basin

0

2

4

6

8

10

7/21

7/22

7/23

date

Prec

ipita

tion,

Ex

cess

(mm

/hr)

0

20

40

60

80

100

Runo

ff (m

3/s)Runoff (m3/s)

Outflow(m3/s)

Precip (mm)

Excess (mm)

Page 36: Water Models 2
Page 37: Water Models 2

Looping Through the Schematic Network

Get Upstream Features

Get Upstream

ValuesProcess

Upstream Values

Process Value to

Pass

Update Value

Collection

Topology Collection Value

Collection

ReceiveProcess

HydroID Upstream HydroIDs HydroIDs Values

Feature, Values

Feature, Value

Processed Value

PassProcess

Processed Value

HydroID, New Value

See GISHydro2003 CD for details

Page 38: Water Models 2

Schematic Network Process Implementation

Geodatabase

DLL(MBSchematic.dll)

Script(ProcSchematic.vbs)

ArcToolboxScript Tool

(ProcessSchematic)

Process DLL 1 Process DLL n

GIS

Script and DLLs

Page 39: Water Models 2

Strengths of ArcGIS for Modeling

• Integration with the COM environment, use of Visual Basic, and accessibility of models through dlls is great step forward

• Network topology a big help for water resources networks

• Geodatabase design process is important for modeling system architecture

• Model Builder is great for handling work flow sequences

Page 40: Water Models 2

Limitations of ArcGIS for Modeling

• No data model and tools for time series in core software

• Graph plotting is inadequate for displaying time series

• Relationships are critical in geodatabase design but can’t be created in ArcView – separate toolkits for ArcInfo and ArcView implementation of modeling systems?

• No scheme for scenario management

Page 41: Water Models 2

Overall Assessment

• Geographic framework: solid

• Model connections: good architecture, needs development

• Time series: being improved with current research

Hydrologic Information System