leveraging gis applications to enhance municipal …...leveraging gis applications to enhance...
Post on 19-Jul-2020
14 Views
Preview:
TRANSCRIPT
Leveraging GIS Applications to Enhance Municipal Stormwater Management
Neal Banerjee, PE, CFMWater Resources Dept. Manager
ESP Associates, Inc.
Chris Costner, PEStormwater Supervisor
City of Monroe
Regional Stormwater Partnership of the Carolinas | Tech Talk: GIS Mapping | October 23, 2018 | Charlotte, NC
2
Outline
Monroe Stormwater Overview
Managing Stormwater Assets
Stormwater Inventory GIS Applications – Case Study Monroe, NC
Other Stormwater Management GIS Applications
Summary and Conclusions
Takeaways
3
City of Monroe Overview
County seat of Union County Population: 35,000 ± Size - 24.9 Sq. miles Watersheds
Stewarts Creek Bearskin Creek Richardson Creek
NPDES Permit No.NCS000482
4
EngineeringDepartment
Engineering DirectorJim Loyd, P.E.
Land Development & Infrastructure EngineerSarah McAllister, P.E.
Plan ReviewConstruction Inspector IIErosion Control Inspector
Plat Review / Addressing Tech.Infrastructure Tech.
Stormwater SupervisorChris Costner, P.E.
NDPES CoordinatorStormwater Tech. II
Street SuperintendentTerrell Jackson
Stormwater Maintenance CrewSpecial Project Crew
Concrete CrewAsphalt Maintenance CrewAsphalt Reclamation Crew
Street Signs
Stormwater Program Organization
5
Purpose: Meet EPA’s NPDES, Phase II requirements Enhance existing stormwater system Protect water resources
Protect our streams/creeks Water Supplies Recreation Use Future generation
Programs: Program Administration NPDES, Phase II Compliance Stormwater Operation/Maintenance Stormwater Capital Improvement Projects Stormwater Inventory Stormwater Master Planning/Water Quality
Strmwater Utility Prgram
6
Stormwater Utility Fee Schedule
Budget: FY16: $2,100,900 FY17: $2,261,900 FY18: $2,200,000 Fund Balance: $1,050,800 (reserve)
Residential Rate – Single Family Detached / Mobile Homes Tier – Impervious Area (square feet)
0 to 2,010 - $3.15/month 2,011 to 3,289 - $4.50/month 3,288 and beyond - $6.30/month
Other Residential Units Town Homes - $2.25/month Multifamily - $2.70/month Condominiums - $2.25/month
Non-Residential Rate 1 Equivalent Residential Unit (ERU) per Impervious Area - $4.50/ERU/month 1 ERU equal to 2,618 square feet of impervious surface
Began collecting stormwater fees in January 2009
7
Stormwater Maintenance Crew Dedicated 6-person crew Street Sweeping Program 2 Street Sweepers
Work Orders/Projects: Replace/repair/clean
storm drain pipes Replace/repair/clean
drainage structure Re-grade/clean/construct
swales/ditches
Capital Improvement Project 14 CIP completed
Assistance from Street Maintenance Crew
Stormwater Maintenance Program
8
Stormwater Inventory NPDES, Phase II requirements Updating City’s drainage maps
Global Positing System (GPS) Hand Held Trimble units Engineering staff
Drainage structures and pipes Public property Private property NC DOT R/W
Stormwater BMPs / SCMs Stormwater Outfalls Constantly Updating
Repairs to drainage system New system New stormwater BMP
Stormwater Inventory
9
Inventory (Identify/Locate the Asset)
What do we have? Where is it?
Field Condition Assessment (Assess the Asset)
What condition is it in?
System Evaluation (Assess the Asset System)
What deficiencies do I have in my system? What current and projected needs do I have to meet level of service?
Maintenance and Life-Cycle Management (Manage the Asset System)
What are most effective short- and long-term strategies managing system?
Building Blocks of AM - Recap
10
System inventory is most fundamental building block of not only AM, but also stormwater management Need to know what you have, where it is Even if you don’t “do” asset management, still need to know where water goes for about any SWM
application
Common methods for developing inventory As-Builts/Design Drawings GPS Collection Full Surveys
In practice inventory often combination of methods Piece-meal compilation of separate individual efforts in which mindset collection of individual
features rather collection of system Can save on “re-collection” costs, but may have data integrity/usability challenges
Inventory
11
If You Don’t Have Any Inventory Check again – you probably do have something
Review business processes, check with other departments – chances are data is being captured by someone for some purpose
Figure out what is available, what condition it is in, and who collects/maintains it NPDES compliance, street improvements/maintenance, etc
Figure out what you need and what resources/expertise you have to dedicate to this Be practical – avoid the temptation to go “big” just for sake of going big
Leverage existing tools/technology Existing Data Templates/Models (ESRI, other municipalities, etc.) Integrated mobile collection (e.g. Arc Collector)
Inventory – Tips and Tricks
12
What You Think You Need
What Your Budget is Based On
Where You Can Get with Some Ingenuity
13
Data / Framework Solutions ESRI has data models and tools specific to SW inventory as part of “Local
Government” Solutions that can be downloaded. See http://solutions.arcgis.com/
Ask the “community”– leverage ideas other municipalities or organizations that have gone through same discovery process Google, ArcGIS Online, Web Services
Inventory – Tips and and Tricks
ArcGIS Solutions
14
ArcGIS Stormwater Solutions
15
Field Collection ESRI has suite of integrated “field mobility” mobile apps that can be used
directly collect data in field Arc Collector and Survey123 are primary Requires organizational account
https://www.esri.com/en-us/arcgis/field-mobility/overview There are a number of open source data collection app and GIS software
with surprising functionality QGIS / QField: https://qgis.org GRASS Others…
Other commercial solutions – Trimble, etc.
Inventory – Tips and and Tricks
16Mobile Inventory Collection Tools
17
If You Do Have Inventory (or once you get inventory) Perform data review and needs assessment
Take the time to clean/standardize data if need to Figure out why it is not being used as would be envisioned
Leverage existing tool/technology with data and “smarts” Bring out the true value of the data
Look for relatively simple things that you can do to enhance data that are not time/resource intensive Enhanced attribution Geometric enhancements
Inventory – Tips and Tricks
18
Geometric Feature snapping Flow direction enforcement Connectivity / Geometric networks
Attribution (Automated / Psuedo-Automated) Sensible ID Scheme Location (Watershed, Address, Grid Schemes) Feature-Level metadata (data source, update history, etc.) Connectivity and connection valency (#feature connections to structures) LiDAR-Based elevation and 3D characteristics (slope, volume, etc.) Ownership Drainage area Attachments (photos, documents) Relates (Inspections, maintenance history, etc)
Example Inventory Enhancements
19
Longitudinal XS and Automated Volume Determination of Dry Detention from LiDAR
LAS Dataset Plan/Profile and Feature Elevation Extraction
Automated Drainage Area Enabled Drainage Network
20
Similar to inventory, there a number of good tools/resources for conditions assessments
Framework Methodology depends on level of sophistication NASSCO PACP is robust scoring system for pipelines that can be applied to
stormwater systems
Field Assessments In addition to mobile apps and software, there are a number of field
instruments that facilitate/enhance assessments (e.g. pole cameras)
Condition Assessment
21
PACP Assessment Scheme
Spike Phone Attachmentfor Phone Measurements
Dioptra Mobile App Annotates Photos
QuickView Pole Camera
22Example Referencing of Defects
Separated Joint22.6’ from US
Debris48.7’ from DS
23
This is step where leveraging data and smarts can greatly enhance system evaluation.
Evaluations can be largely automated or pseudo-automated. Degree depends on availability and accuracy of data.
Example 1: Age Susceptibility Assessment (Pre-Field Assessment)Objective: Identify timeline for pipe life-cycle replacement needsSteps: Extract “year built” from parcels and categorize in to generalized “year developed” categories Associate generalized year developed with inventory Update records of known improvements, as-builts, etc. (if available) Compare estimate age of inventory with pipe material life expectancy, and flag systems where age
exceeds life expectancy Compute preliminary system replacement needs by age
System Evaluation
24
Pipe Material Expected Average Service
LifeCorrugated Metal 25 - 50
Plastic 40 - 60Concrete / Clay /
Iron70 - 100
Example Age Analysis and Replacement Assessment
25
Simplified Pipe Outfall Capacity AssessmentObjective: Assess capacity of closed pipe systems at outfalls and determine preliminary upsizing requirementsSteps: Extract pipe system outfall pipes with target threshold drainage area (DA) using terrain generated
DA-enabled drainage network Calculate simplified peak flow based on Rational method with DA-based rainfall intensity estimates
and estimated C coefficient values Calculate Manning’s based pipe capacity (based on size, material, slope) For pipes not meeting capacity, back calculate required pipe size Identify outfall pipes that may not be meeting capacity and further investigation
System Evaluation
26Psuedo-Automated Outfall System Capacity Check
27
Culvert Sufficiency CheckObjective: Identify culverts that do not meet HW/D requirements and determine preliminary upsizing requirementsSteps: Extract culverts from inventory
Calculate simplified peak flow based on Rational method for smaller drainage areas and Regression flows for larger DAs
Can leverage both DA rasters and impervious weighted rasters
Extract estimate culvert inverts from LiDAR (lowest point proximity)
Extract top of road from LiDAR
Compute HW/D from culvert shape, size, material, flow, and inlet type using FHWA nomograph equations
Identify culverts not meeting HW/D (max 1.2) criteria
Compare HW vs road SAG to identify potential road overtopping
For pipes not meeting requirements back adequate size
System Evaluation
28
FHWA Hydraulic Capacity Nomograph Extraction
29
Example Interactive HW/D Calculator
30
Batch HW/D Calculator Prototype
31
Stormwater Inventory Case Study
NPDES Outfall Inspections/Reporting
Stormwater Control Measure (SCM) Inspections/Reporting
GIS Applications Case Study – Monroe, NC
32
Collected in-house last 8 years Mapping-grade GPS survey and
extraction from design/ as-built plans
“Complete”, but constantly changing
14,000± “features”: 4,900± drainage structures 6,150± pipes (100± miles)
150± SCMs 2,900± pipe ends
– 140± “major outfalls”
Stormwater Inventory
33
Non-uniform data Inconsistent nomenclature (e.g. structure types) Variable feature classification
Lack of connectivity Non-enforced flow direction No attribute connectivity between pipes and structures
Limited attributes No depth/elevation data with pipes Limited tracking/metadata No reference/context data (watershed, drainage area, etc.)
Inventory Challenges
34
Non-scalable structure Stored as separate shapefiles (no network connectivity, etc.) Not designed with long-term vision/use in mind
Data maintenance and use Editing/Updating in the field difficult, tedious, and error-prone Limited data accessibility to managers and potential end users
Inventory Challenges
35
ESP tasked by City in 2017 to update inventory and provide tools to facilitate and enhance management of inventory
Guiding framework Standardize and “clean up” existing data Enhance data for more robust and longer term use, but keep it simple Provide means to update existing feature data and collect new features in field Provide means to view/manage data by managers
Stormwater Inventory Update
36
Review and assessment Assess current workflows and characteristics/condition of existing data
Functional requirements Determine needs and desire of City for inventory data
Stormwater data model development Design data model to meet requirements
Data processing and migration Perform data processing/manipulation and migrate existing data into model
Enhanced processing/attribution Perform geospatial processing to add enhanced attributes
ArcGIS Collector and AGOL development Build ArcGIS-based applications to collect, manage, and utilize data
Inventory Update Process
37
Existing Feature Attribute SummariesData Model Development andX-Ray Documentation
38
Standardized/Simplified attribute fields and created domains 11 domains – structure type, material, ownership, accuracy, etc.
Mapped existing data fields into data model
Performed systematic geometry checks/edits Feature snapping Flow direction Multi-Part or irregular geometry
Basic Attribution FeatureIDs, US/DS connectivity, data source, migration comments, etc.
Processing/Migration Summary
39
Ownership Important in asset management for identified maintenance responsibilities Created ROW layer from parcels, reference with Powell Bill map
Watershed Important for classification in NPDES monitoring/reporting
Elevation estimates Obtained from new high-resolution (8ppm) LiDAR (created .lasd) Most suitable for structures in pavement Added depth/elevation/slope estimates to pipes
Enhanced Processing/Attribution
40
Geometric Network US/DS tracing Accumulated attribute calculation
User Tracking Created/Edited usernames and dates
Attachments Reference as-builts, inspection reports, etc.
Enhanced Processing/Attribution
41
ROW Layer and Powell Bill Map for Ownership Pipe Data with Enhanced Attributes
42
LAS Dataset Plan/Profile and FeatureElevation Extraction
43
Example Upstream Flow Trace with Utility Network Toolbar
44
Published feature services
Designed AGOL web map and associated web application Consume inventory data and referenced layer Allow in-office viewing, editing, reporting
ArcGIS Collector Support mobile editing and collecting Linked to webmap for real-time tracking
ArcGIS Application Development
45
ArcGIS Online Web Map
46
ArcGIS Online Web App with Reporting Functions
Customized Widgets
47
Basemap / Layers / Measure Tools
Bookmarks
Search Address / Feature ID
Add Feature
Zoom to Location
ArcGIS Collector App
48
Pick from List
Pick by Voice
Feature Collection/Editing in Collector
49
NPDES permit requires regular inspection and reporting of major outfalls Generally collect inspect one watershed per year City had paper forms
Post-Construction ordinance requires SCMs be inspected annually City used paper forms Inspections generally performed by 3rd party
Developed NPDES/SCM inspection forms in Survey123 Form-Centric tool/application to collect, share, and characterize information Three components/aspects – website, Connect, app Designed with Connect for more flexibility
NPDES Outfall / SCM Inspections
50Example SCM Paper Form
51
NPDES Outfall Inspection Collection ApplicationCurrent Field Collection Form Form Converted to Collection
Application
52
NPDES Outfall Inspection Collection Application
Download Survey
53
NPDES Outfall Inspection Collection Application
Can designate required fields
Can populate drop downs with predetermined choices
Can have certain sections appear only when applicable
54
Survey123 Forms for NPDES and SCM Inspection
55
City manages proactive stormwater program with relatively modest budget and resources
Two key needs Stormwater inventory update and editing/collection NPDES/SCM inspections
Leveraged suite of ArcGIS software, tools, applications to streamline and much more efficiently share/use stormwater data Standardized data Real-time mobile collection and desktop viewing Added value attribution
Summary and Conclusions
56
If you have an organizational account, lots of “free” resources/tools to help manage your data Generally require configuring vs. programming
Leveraging these tools with available data (e.g. high-res LiDAR) help do things you couldn’t do before
Things to keep in mind (not covered here): Data storage/hosting User credentials
Potential future enhancements: Assisted editing – Attribute Assistant and tools More advanced web geoprocessing and reporting Integration with Asset Management and other apps
Takeaways and Looking Ahead
57
Questions?
Chris Costner, P.E.Stormwater Supervisor
ccostner@monroenc.org704-282-4537
top related