arcgis hec-hms interface data model

15
ArcGIS HEC-HMS Interface Data Model July, 2003 CRWR CRWR CRWR

Upload: adam-williamson

Post on 31-Dec-2015

47 views

Category:

Documents


5 download

DESCRIPTION

ArcGIS HEC-HMS Interface Data Model. July, 2003. Project Goals: 1. To provide a database for all HMS data, so that the data may be queried and retrieved efficiently. Project Goals: 2. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: ArcGIS HEC-HMS  Interface Data Model

ArcGIS HEC-HMS Interface Data Model

July, 2003

CRWRCRWRCRWR

Page 2: ArcGIS HEC-HMS  Interface Data Model

Project Goals: 1

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

Page 3: ArcGIS HEC-HMS  Interface Data Model

Project Goals: 2

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

HMS files HMS geodatabase

Page 4: ArcGIS HEC-HMS  Interface Data Model

Project Goals: 3

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

Page 5: ArcGIS HEC-HMS  Interface Data Model

Project Goals: 4

• To store timeseries data in a manner that will be compatible with the latest timeseries tool kits.

Page 6: ArcGIS HEC-HMS  Interface Data Model

Project Goals: 5

• To maintain a relationship between features in the ArcHydro model and features in the HMS Interface model.

Arc Hydro

HydroID

HMS Interface

FeatureID

Page 7: ArcGIS HEC-HMS  Interface Data Model
Page 8: ArcGIS HEC-HMS  Interface Data Model

Geodatabase Design

Purpose: To provide a HMS data storage structure that will meet the requirements of the 5 project goals

Visio 2000 UML

ArcGIS Repository

Geodatabase Schema

Page 9: ArcGIS HEC-HMS  Interface Data Model

UML Components: 1

• Abstract & Object Classes

Abstract Class

Object Classes

Page 10: ArcGIS HEC-HMS  Interface Data Model

UML Components: 2

• Relationship Classes

Relationship Classes

Page 11: ArcGIS HEC-HMS  Interface Data Model

UML Components: 3

• Coded Value Domains

Coded Value Domain

+FieldType = esriFieldTypeString+MergePolicy = esriMPTDefaultValue+SplitPolicy = esriSPTDefaultValue+None = None+Kinematic Wave = Kinematic Wave+Lag = Lag+Modified Puls = Modified Puls+Muskingum = Muskingum+Muskingum Cunge 8 Point = Muskingum Cunge 8 Point+Muskingum Cunge Standard = Muskingum Cunge Standard+Straddle Stragger = Straddle Stragger

«CodedValueDomain»RouteType

-From_X : esriFieldTypeDouble-From_Y : esriFieldTypeDouble-Route : RouteType-DownCode : esriFieldTypeString

HMSReach{GeometryType = esriGeometryPolyline}

Object Class

Page 12: ArcGIS HEC-HMS  Interface Data Model

Schema Tables for the LCRA/Halff HMS Model

Point feature classHMSDiversion

Point feature classHMSJunction

Line feature classHMSReach

Point feature classHMSReservoir

Point feature classHMSSink

Point feature classHMSSource

Polygon feature classHMSSubbasin

TableBasinModelParameters

TableDSSPairedValues

TableDSSPVType

TableDSSTimeSeries

TableDSSTSType

TableHMSGage

TableLossRate_InitialConstant

TableMeteorological_ModelHeader

TableMeteorological_UserHyetograph

TableRoute_ModifiedPuls

TableTransform_Snyder

Basin File

DSS File

Met File

Gage File

Page 13: ArcGIS HEC-HMS  Interface Data Model

Some Results: 1

Page 14: ArcGIS HEC-HMS  Interface Data Model

Some Results: 2

Page 15: ArcGIS HEC-HMS  Interface Data Model

Future Work• Expand schema to incorporate more HMS subroutines

including additional transform and routing options, and model calibration.

• Improve and expand upon codes for transferring data between the Interface Geodatabase and HMS files.

• Further exploration of the DHI timeseries toolkit, and how it can be used to aid in the viewing of DSS timeseries data.

• Explore ArcGIS Model Builder, and how it might be used to aid in data transfer and running HEC-HMS.