1. ArcGIS HEC-RAS IDM and Interface Tools The University of Texas at Austin Center for Research in Water Resources August, 2004 By Oscar Robayo

2. ArcGIS Interface Data Models Interface Data Models HEC-HMS HEC-RAS Flood Impact Analysis GIS Geo Database Arc Hydro data model Engineering Models

3. Map2Map’s Conceptual Workflow

4. ArcGIS HEC-RAS IDM CrossFeature LateralFeature AreaFeature Control Output PreProcess PostProcess Main Components:

5. ArcCatalog View

6. ArcCatalog View (Continued)

7. GIS Import/Export Workflow

8. XML-Based Data Exchange Platform Independent Application Independent Ready to share with many third party applications Updates do not require code recompilation

9. GIS Advantages of XML Approach GDB content will have shape-geometry after GIS import (implicit geometric definition) Transfer of geometric vertices goes to shape Faster Transfer operations of dense geometries Geometric structure includes X, Y, Z, and M Import to GIS goes to a new or existing GDB

10. Current Issues with GIS Transfer Current development only for ArcGIS 8.3 Only Spatial Extent is defined, Not full projection information (define projection after transfer) Import to GIS goes to existing GDB w/o projection Relies on Model’s exposure of complete Geospatial definitions

11. GIS Import/Export Data Exchange (Water Resources Team at ESRI)

12. XML Transformations XSLT Processor HTML pages XML docs Text files Input XML to be TransformedInput XSLT stylesheet (template rules) External Apps

14. Metadata Definition for Scenario Management System Header, RunID, and ProfileID Tables with corresponding relationships to components in geodatabase IDM Import Model related Metadata with expanded versioning elements: created and last modified dates, ProjectID, ScenarioID, Description, Author, Owner, purpose, Source Location, etc.

15. Scenario Management System

16. Scenario Management System (Continued) File Name & File Title

17. Acknowledgements Dean Djokic at ESRI Zhumei Qian at ESRI Zichuan Ye at ESRI Xinnong Zhou at ESRI