Transcript Document
Arc Hydro for the Watershed Management Program at the Southwest Florida Water Management District Presenters: Gordon McClung, P.E. Diana Burdick Jamison Janke, E.I. Nam Nguyen, E.I. Arc Hydro and GIS Implementation • Developed the SWFWMD’s Guidelines and Specifications for the establishment of standardized procedures for the Watershed Management Program and GIS (ArcInfo - ESRI) database for storing/maintaining data. Coverage/shapefile Related tables Establishes data standards for data acquisition, spatial identification and storage of data. Arc Hydro and GIS Implementation • September 2002 – March 2003: •Internal requirements analysis • March 2004: •Database design workshop •Application prioritization workshop •Critical tools overview • December 2004 •Database Design •Begin loading Database • February 2005 •Tools Delivered •Begin Testing on Small Watersheds • Spring/Summer 2005 •Migrate to ArcGIS Version 9 • Current •Revisions to database design •Standardization of terminology •Identification of workflow Arc Hydro Database Design •4 feature datasets •21 feature classes •29 object classes •Domains/relationship classes Arc Hydro Database Design Database design issues: • Reviewed current coverage/shapefile format for migration to GDB • “Enterprise” maintains the current environment while project information is maintained by PGDBs. Index layer maintained in Enterprise that points to project PGDB location Index Personal (project) Geodatabase GIS Production Geodatabase SDE/Oracle Arc Hydro Application Development Four “critical” tools identified: • Management of HydroID between PGDB and SDE • GeoRAS import/export from PGDB/SDE to define future import/export tools • Ingest of OneRain data • Internally drained connectivity Arc Hydro Application Development Input Data (OneRain, Model Results) Generic XML Export XML Control Structure Intermediate Output XML XSLT Transform XLST (1) Generic GDB XML Generic Import GeoDatabase Arc Hydro and GIS Implementation Other activities: • Development of ArcMap template for current projects so migration to geodatabase easier • Testing and training • Coordinating with ESRI for terrain data in geodatabase •Implementation of historical 15 minute OneRain data from 1993 Arc Hydro and GIS Implementation LiDAR SWFWMD Import of Terrain deliverables into GDB format Dealing with .5 to 1.5 million points per Sq. Mile Terrain Geodatabase Current Terrain = Coverage and TINS Future with Terrain Geodatabase = GeoDatabase Feature Dataset and Terrain Workflow and Initial GIS Layers Generate Terrain Products Initial Data Layer Edits Aerial 3.0a GIS Analysis 4.10 Identify Hydraulic Elements Update Terrain 7.10 Model Input Format NWI Roads Soils Water Model Terrain – DEM or TIN 5 feet cell size raster Subbasins & Connectivity Generated from ArcHydro Tools Legend Low Pt. of Basin/Boundary HydroEdge_5ft Catchment_5ft Subbasins & Connectivity Legend Low Pt. of Basin/Boundary HydroEdge_5ft Catchment_5ft Connectivity – A hydronode, in pink, is placed here manually identifying a hydraulic structure during Watershed Evaluation phase Field Reconnaissance HydroPoints – Additional xyz information collected Should a new TIN/DEM be generated??? Field Photo Hydraulic Elements HydroElementID = 118 NodeID = 7 HydroElementID = 117 NodeID = 7 HydroNode HydroID = 7 Culvert NodeID = 7 HydroID = 117 HydroElementID = 119 NodeID = 7 Culvert NodeID = 7 HydroID = 119 Culvert NodeID = 7 HydroID = 118 HydroElementID = 117 NodeID = 7 HydroElementID = 118 NodeID = 7 HydroElementID = 119 NodeID = 7 HydroNode identifies a structure. The structure is made up of multiple hydraulic elements. Hydraulic Elements are made up of multiple hydropoints. Model Specific Reach/Junction Questions?