1 / 15

ArcGIS HEC-HMS Interface Data Model

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.

adam-williamson
Download Presentation

ArcGIS HEC-HMS Interface Data Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ArcGIS HEC-HMS Interface Data Model July, 2003

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

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

  4. Project Goals: 3 • To store watershed (spatial) data in a manner that can be easily viewed in ArcMap.

  5. Project Goals: 4 • To store timeseries data in a manner that will be compatible with the latest timeseries tool kits.

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

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

  8. UML Components: 1 • Abstract & Object Classes Abstract Class Object Classes

  9. UML Components: 2 • Relationship Classes Relationship Classes

  10. UML Components: 3 • Coded Value Domains Coded Value Domain Object Class

  11. Schema Tables for the LCRA/Halff HMS Model

  12. Some Results: 1

  13. Some Results: 2

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

More Related