Arc Hydro for the Watershed Management Program at

  • Slides: 23
Download presentation
Arc Hydro for the Watershed Management Program at the Southwest Florida Water Management District

Arc Hydro for the Watershed Management Program at the Southwest Florida Water Management District Presenters: Gordon Mc. Clung, 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

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 (Arc. Info - 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

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 Arc. GIS Version 9 • Current • Revisions to database design • Standardization of terminology • Identification of workflow

Arc Hydro Database Design • 4 feature datasets • 21 feature classes • 29

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

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

Arc Hydro Application Development Four “critical” tools identified: • Management of Hydro. ID between

Arc Hydro Application Development Four “critical” tools identified: • Management of Hydro. ID between PGDB and SDE • Geo. RAS import/export from PGDB/SDE to define future import/export tools • Ingest of One. Rain data • Internally drained connectivity

Arc Hydro Application Development

Arc Hydro Application Development

Arc Hydro and GIS Implementation Other activities: • Development of Arc. Map template for

Arc Hydro and GIS Implementation Other activities: • Development of Arc. Map 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 One. Rain data from 1993

Arc Hydro and GIS Implementation

Arc Hydro and GIS Implementation

Li. DAR SWFWMD Import of Terrain deliverables into GDB format Dealing with. 5 to

Li. DAR 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 = Geo.

Terrain Geodatabase Current Terrain = Coverage and TINS Future with Terrain Geodatabase = Geo. Database Feature Dataset and Terrain

Workflow and Initial GIS Layers Aerial NWI Roads Soils Water

Workflow and Initial GIS Layers Aerial NWI Roads Soils Water

Terrain – DEM or TIN 5 feet cell size raster

Terrain – DEM or TIN 5 feet cell size raster

Subbasins & Connectivity Generated from Arc. Hydro Tools

Subbasins & Connectivity Generated from Arc. Hydro Tools

Subbasins & Connectivity

Subbasins & Connectivity

Connectivity – A hydronode, in pink, is placed here manually identifying a hydraulic structure

Connectivity – A hydronode, in pink, is placed here manually identifying a hydraulic structure during Watershed Evaluation phase

Field Reconnaissance

Field Reconnaissance

Hydro. Points – Additional xyz information collected

Hydro. Points – Additional xyz information collected

Should a new TIN/DEM be generated? ? ?

Should a new TIN/DEM be generated? ? ?

Field Photo

Field Photo

Hydraulic Elements Hydro. Element. ID = 118 Node. ID = 7 Hydro. Element. ID

Hydraulic Elements Hydro. Element. ID = 118 Node. ID = 7 Hydro. Element. ID = 117 Node. ID = 7 Hydro. Node Hydro. ID = 7 Culvert Node. ID = 7 Hydro. ID = 117 Hydro. Element. ID = 119 Node. ID = 7 Culvert Node. ID = 7 Hydro. ID = 119 Culvert Node. ID = 7 Hydro. ID = 118 Hydro. Element. ID = 117 Node. ID = 7 Hydro. Element. ID = 118 Node. ID = 7 Hydro. Element. ID = 119 Node. ID = 7 Hydro. Node identifies a structure. The structure is made up of multiple hydraulic elements. Hydraulic Elements are made up of multiple hydropoints.

Model Specific Reach/Junction

Model Specific Reach/Junction

Questions?

Questions?