USING GIS FOR A COUNTY STORM DRAIN MARKING PROGRAM. Tom Maggard. Senior Technician City of Greenwood

Transcription

1 USING GIS FOR A COUNTY STORM DRAIN MARKING PROGRAM Tom Maggard Senior Technician City of Greenwood

2 Using GIS for a County Storm Drain Marking Program OUTLINE 1. Brief NPDES Overview 2. Getting Started 3. Through the Years Helping with a local company's Storm Drain Marking Project 5. Next/Future Steps??

3 NPDES (NATIONAL POLLUTANT DISCHARGE ELIMINATION SYSTEM) NPDES Overview Introduced in 1972 Authorized by the Clean Water Act to control water pollution by regulating point sources that discharge pollutants into waters of the United States. Point sources are discrete conveyances such as pipes or man-made ditches. Individual homes that are connected to a municipal system, use a septic system, or do not have a surface discharge do not need an NPDES permit; however, industrial, municipal, and other facilities must obtain permits if their discharges go directly to surface waters. Water pollution degrades surface waters making them unsafe for drinking, fishing, swimming, and other activities. In most cases, the NPDES permit program is administered by authorized states.

4 NPDES Storm Drain Marking Storm drain marking involves labeling storm drain inlets with plaques, tiles, painted, or pre-cast messages warning citizens not to dump pollutants into the drain The messages are generally a simple phrase or graphic to remind those passing by that the storm drains connect to local water bodies and that dumping will pollute those waters Some storm drain markers specify which water body the inlet drains to or name the particular river, lake, or bay Common messages include: No Dumping. Drains to Water Source, Drains to River, and You Dump It, You Drink It. No Waste Here In addition, storm drain markers often have pictures to convey the message, including common aquatic fauna or a graphic depiction of the path from drain to water body.

5 MARION COUNTY STORM DRAIN MARKING DPW implements Marion County NPDES Storm Drain Marking activities Marking Storm Drains since mid 2000s Volunteer groups coordinated by DPW Mostly schools and neighborhood groups 2007 map showing number of storm drains marked from NPDES Annual Report City of Bloomington IN Storm Drain Marking

6 MARION COUNTY STORM DRAIN MARKING UNITED WATER S INVOLVEMENT United Water is the Storm and Sanitary Sewer contractor for DPW/CEG Contract obligation to place at least 2,000 Storm Drain Marking Stickers per year starting in , , , Duty falls to the GIS Dept We perform asset management by physical inspection of storm sewer system 169,407 points in STORMSTRUCTURES shapefile (as of April 2013) Logical for us as we are visiting individual inlets Started working at UW in fall 2008 Helped finish Storm Drain Marking for that year Worked on project the following year Took company lead in 2010

7 GETTING STARTED When I started with United Water they were using these types of maps for marking This map would be given to a crew member who would use a marker to highlight any point where a storm drain marker was placed

8 GETTING STARTED When they were done with an area it would look roughly like this

9 GETTING STARTED As you can imagine, it is hard to decipher which of these are actual inlets that need marking If not put a number down by highlight, might be difficult to determine how many markers were placed

10 2009 Storm Drain Marking Program Continued with the same format of maps for storm drain marking Start a method of tracking where markers were placed Created layer called Subdivision Sticker Marking Used existing shapefile (PLATTEDSUBDIVISION) from City of Indianapolis SDE Database Exported shapefile, changed name and created new fields These fields were HAS_STICK, YEAR, GROUP Fields were populated with data from numerous groups/agencies Populated these fields with following data HAS_STICK used following breakdown YES has sticker NO need stickers NN stickers not needed VISIT need physically check YEAR of placement GROUP used the following breakdown UW - United Water OES/ERMC - volunteer groups

11 2009 Storm Drain Marking Program Create map that shows if a subdivision had been marked

12 2009 Storm Drain Marking Program the year a subdivision was marked

13 2009 Storm Drain Marking Program who marked the subdivision for the yearly NPDES Report

14 2009 Storm Drain Marking Program Problems arise?? Are there really markers placed??? maps next to each other, areas not line up Have areas on left map that show where markers have been placed but they don t show up on the right map Frustrating to go to area thinking there were no markers only to find markers I still had no way to know an exact amount markers placed easily Still using previous year method Make maps and mark where placed markers Write total markers placed on sheet after completion Keep this total in excel file for the reporting year

15 2009 Storm Drain Marking Program Problems arise?? Hansen database stores data Not possible transfer marking data from GIS to database Data supposed to be entered into database NOT EVERYONE DILIGENT ENTERING DATA

16 2010 Storm Drain Marking Program Decided it was time to address the issue of knowing the specific location of storm drain markers Created a File Geodatabase (Storm Drain Marking Project) to store data This allows for stability & continuity of data from city SDE database Exported existing Subdivision Sticker Marking shapefile into geodatabase Storm Drain Marking point shapefile was then created Used existing shapefile (STORMSTRUCTURES) from city Exported shapefile into file geodatabase & changed name Deleted existing data Just wanted fields Allow consistency between shapefiles Able join excel data Then created new fields These fields were Sticker Placed and YR Stick placed Populated these fields with following data Sticker Placed Yes or No Yr Stick placed year

17 2010 Storm Drain Marking Program Populating Storm Drain Marking fields Started by looking at Subdivision Sticker Marking feature class where UW had placed markers in 2009 Would zoom to area and select points from STORMSTRUCTURES layer Next copy/paste these points into the Storm Drain Marking feature class Not the most efficient but most accurate Then populate the newly created fields Sticker placed YES and Year stick placed 2009

18 2010 Storm Drain Marking Program Populating Storm Drain Marking fields While performing this task, I also looked for areas that were listed in the Subdivision Sticker Marking feature class as Stickers Needed When I would see those areas, I would perform the same copy/paste as I did before Only difference being that I would not populate the new fields This would give me areas to visit in coming summer months for 2010 and beyond

19 2010 Storm Drain Marking Program After placing markers that summer and obtaining data from DPW I was able to produce a map that showed me the following [ YES, 2010 [ YES, <2010 YES, <Null> 2010 <2010

20 2011 Storm Drain Marking Program Continued with same plan from 2010 One change - Ownership of contract switched from DPW to CGE Meant less communication about where other storm drains marked - organizational changes getting worked out Only known storm drains marked done by UW Produced map that showed up-todate Storm Drain Marking

21 2012 Storm Drain Marking Program Continue to refine shapefiles to gain better understanding of where storm drain markers are & when they were placed Plan for the year was the same as year before Started by placing little over 800 stickers when asked to STOP placing markers UW management was contacted by DPW because a local company was planning a project of and wanted to know if this was even possible I was referred to the leaders of this project as I had the only known data set in the county referring to individual storm drain markers

22 Company Storm Drain Marking Project Before I had my first meeting with this company they had a change in mind for the scope of the project They decided to only place around 1,000 markers and focus on one Township in Marion County I chose Pike Township as it fit into the parameters the company requested

23 Company Storm Drain Marking Project Pike Township was chosen and I began data analysis of storm drains Wanted to have know exactly where markers were/were not within this boundary Was able to gain a little more information on where/when hen markers placed Able obtain excel report from Hansen Created Join based on UNITID field to find all storm drain markers listed in Hansen This allowed me to update my Storm Drain Marking feature class Started to look at how the maps were going to look ing with project leader on map design Producing maps for people who not use on daily basis What scale would work the best??

24 Company Storm Drain Marking Project Couple months after the initial meeting, I was informed that the company had changed there minds again Because of the drought they were not going to be able to perform many of their other planned activities Morse Reservoir July 2012 Indianapolis 2012 People e painting grass us-worse_n_ html nting_spreads_as_drought_ravages_lawns/ They were then switching those volunteers to storm drain marking We were now back to wanting to mark every storm drain in Marion County I had lost a some months in data analysis for the county storm drain marking situation Also had a short turn around from finding out change to project day Had to make some quick decisions

25 Company Storm Drain Marking Project Company wanted to place at least 8,000 markers and field verify areas Some of these areas had not been assetted or assetted correctly Previously I would correct or asset a non-assetted subdivision when placing markers This severely limited the time I had to do either The decision was made to find as many points as possible for the project and worry about assigning a UNITID later I used Subdivision Sticker Marking feature class to update Storm Drain Marking feature class Just started copy/paste points from STORMSTRUCTURES layer while looking at aerials If point was inside polygon that showed need sticker, it was classified NO, <Null> If point was inside polygon that showed field verify, it was classified YES, <Null>

26 Company Storm Drain Marking Project After more than a few days of looking through aerials trying to identify possible storm drain marking project locations, I was able to create the following map Storm Drain Marking Project [ Field Verify = 13,053 [ No Marker = 7,618

27 Company Storm Drain Marking Project Next step involved producing maps Unfortunately I had to pass map creating to DPW My boss & DPW, with my input, agreed that I had put in enough hours to meet contractual obligations I had continued to do my regular duties in addition to the time spent obtaining data for the storm drain marking project I then became a resource for the project Data was passed to DPW GIS Department who created maps Gave a copy of Storm Drain Marking Project geodatabase I gave any needed information about data and how I had created maps in past Kept communication for any questions that arose during map production Maps were produced using Data Driven Pages I was still using Arc 9.3 at this time so I did not have capabilities of Data Driven Pages

28 Company Storm Drain Marking Project The number of maps created for the project were = 1,091

29 Company Storm Drain Marking Project An example of a Township Map produced for the project

30 Company Storm Drain Marking Project The were some of the volunteers for the day marking project They seemed to really enjoy placing the markers

31 Company Storm Drain Marking Project As you could imagine, the data crunch after a project like this is arduous Over 1,000 paper maps Shapefile with over 20, points Must decipher work done by volunteers and not have follow up with volunteers who were in the field What do marks on maps mean? Did they put a marker in that spot or not What do descriptions mean? Why does an area listed as needing markers have description of not placed?? Populate and create new fields in GIS Starting to track areas where follow up visits were done Enter data into Hansen

32 Company Storm Drain Marking Project As of the middle of March, this map represents the data compiled for the 7,618 locations needing markers: [ Marker Placed = 2,112 [ Data not entered = 5,404 [ No Marker Placed = 102

33 Company Storm Drain Marking Project As of the middle of March, this map represents the data compiled for the 13,053 locations needing field verified: [ Data Not Entered = 11,925 [ Put Down Marker = 702 [ Verified Marker Present= 426

34 Next/Future Steps of the Storm Drain Marking Program Getting all company project data entered into GIS and Hansen Labor intensive All data entry being done by 1 DPW technician Focus on entering data for areas that classified as needing markers Next move on to field verify areas Look at plan for follow up field verification NPDES calls for re-visiting an area with markers every 5 years Currently not a system in place to perform this task or track No staff Just created follow up field(s) because of project Continued modification of field(s) to find best method Does UW s work now fall into this category instead of marker placement May not be 2,000 markers to place this year Continued collaboration with DPW & CEG Ensure data is accurate and consistent Eventually join data into existing STORMSTRUCTURES layer??

35 domanda frage QUESTIONS вопрос pregunta