SERUG - Use of GIS for Stormwater Infrastructure Mapping
Use of GIS for Stormwater Infrastructure Mapping
Andy Renshaw City of Gainesville Public Works
National Pollutant Discharge Elimination System
Gainesville Clean Water Partnership City of Gainesville
Florida Department of Transportation
Alachua County
Why Map the Stormwater System?
Why Map the Stormwater System? • NPDES Requirements Map of Storm System in Urban Area
~ 78 sq miles
Why Map the Stormwater System? • NPDES Requirements •
Infrastructure Inventory
Why Map the Stormwater System? • NPDES Requirements • Infrastructure Inventory •
Modeling
Planning and Considerations Reduce time needed Avoid duplication of effort Create consistent quality of data Efficiently use labor assets
Cost: Fieldwork vs. Digitizing • Fieldwork: ~$16.33 per feature estimated over $600,000 to do UA
Cost: Fieldwork vs. Digitizing • Fieldwork: ~$16.33 per feature estimated over $600,000 to do UA
• Contracted Digitizing: ~$3.45 per feature estimated about $130,000 to do UA
Evolution of Data Collection 1) Migration of old Mylar storm maps
Last updated 1987 Diagram only Accurate Elev Data
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit
3) Plans and CADD files
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit 3) Plans and CADD files
4) LiDAR
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit 3) Plans and CADD files 4) LiDAR
5) Scan, georeference and digitize
Data Organization The GeoDataBase
The GeoDataBase Goals of our GDB: 1. Capture as much data as possible in an organized fashion
The GeoDataBase Goals of our GDB: 2. Comprehensive Inventory
The GeoDataBase Goals of our GDB: 3. Easy Extraction of Data
The GeoDataBase Started with ESRI Water Utilities Data model 1. 2. 3.
Provided basic framework Most “standard” model available for storm Provided framework for both network and non network features 4. Easy to modify as needed
Let’s take a tour…
Feature Classes Hyperlink Features: • Hyperlink Point
• Hyperlink Poly
Feature Classes
Feature Classes Sewer_Stormwater_Features • Non-Network Features • Polygon (ex. Retention basin) • Cartographic Features (ex. Headwall and weir shape) •Spatial location of event, work, etc.
Feature Classes Sewer_Stormwater_Features • ssSpatialOperationsRecord
• ssStormFeature
• ssStormStructure
Feature Classes Sewer_Stormwater_Network • ssGravityMain -Virtual GravityMain
• ssPresurizedMain
• ssOpenChannel
Feature Classes Sewer_Stormwater_Features • ssCatchBasin (Inlets)
• ssManhole
• ssDischargePoint
Feature Classes Sewer_Stormwater_Features • ssStormBasin
• ssNetworkStructure • Sediment traps •Spillways
• Other items…
•Control structures
Future…
Future…
1. Modeling
Future…
2. Pond and Outfall Permits
Future…
3. Work Orders and Inventory
Future…
4. Repository for Digital Plan Sets
Andy Renshaw 352-393-8522 [email protected]
Andy Renshaw City of Gainesville Public Works
National Pollutant Discharge Elimination System
Gainesville Clean Water Partnership City of Gainesville
Florida Department of Transportation
Alachua County
Why Map the Stormwater System?
Why Map the Stormwater System? • NPDES Requirements Map of Storm System in Urban Area
~ 78 sq miles
Why Map the Stormwater System? • NPDES Requirements •
Infrastructure Inventory
Why Map the Stormwater System? • NPDES Requirements • Infrastructure Inventory •
Modeling
Planning and Considerations Reduce time needed Avoid duplication of effort Create consistent quality of data Efficiently use labor assets
Cost: Fieldwork vs. Digitizing • Fieldwork: ~$16.33 per feature estimated over $600,000 to do UA
Cost: Fieldwork vs. Digitizing • Fieldwork: ~$16.33 per feature estimated over $600,000 to do UA
• Contracted Digitizing: ~$3.45 per feature estimated about $130,000 to do UA
Evolution of Data Collection 1) Migration of old Mylar storm maps
Last updated 1987 Diagram only Accurate Elev Data
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit
3) Plans and CADD files
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit 3) Plans and CADD files
4) LiDAR
Evolution of Data Collection 1) Migration of old Mylar storm maps 2) Use of GPS unit 3) Plans and CADD files 4) LiDAR
5) Scan, georeference and digitize
Data Organization The GeoDataBase
The GeoDataBase Goals of our GDB: 1. Capture as much data as possible in an organized fashion
The GeoDataBase Goals of our GDB: 2. Comprehensive Inventory
The GeoDataBase Goals of our GDB: 3. Easy Extraction of Data
The GeoDataBase Started with ESRI Water Utilities Data model 1. 2. 3.
Provided basic framework Most “standard” model available for storm Provided framework for both network and non network features 4. Easy to modify as needed
Let’s take a tour…
Feature Classes Hyperlink Features: • Hyperlink Point
• Hyperlink Poly
Feature Classes
Feature Classes Sewer_Stormwater_Features • Non-Network Features • Polygon (ex. Retention basin) • Cartographic Features (ex. Headwall and weir shape) •Spatial location of event, work, etc.
Feature Classes Sewer_Stormwater_Features • ssSpatialOperationsRecord
• ssStormFeature
• ssStormStructure
Feature Classes Sewer_Stormwater_Network • ssGravityMain -Virtual GravityMain
• ssPresurizedMain
• ssOpenChannel
Feature Classes Sewer_Stormwater_Features • ssCatchBasin (Inlets)
• ssManhole
• ssDischargePoint
Feature Classes Sewer_Stormwater_Features • ssStormBasin
• ssNetworkStructure • Sediment traps •Spillways
• Other items…
•Control structures
Future…
Future…
1. Modeling
Future…
2. Pond and Outfall Permits
Future…
3. Work Orders and Inventory
Future…
4. Repository for Digital Plan Sets
Andy Renshaw 352-393-8522 [email protected]
