1. ICT Tool Design Evan Fedorko et al, WVGISTC 1

2. Outline What is it? Why is it needed? How does it work? Summary and Conclusions 2

3. What is it? Interagency Coordination Tool Agencies in question: WVDNR, FWS (WV) and NRCS (WV) Coordination in question: Potential impacts on populations or habitat of endangered species due to NRCS funded on-the-ground projects 3

4. Why is it needed? NRCS funds farmers (and others) to implement new projects on their properties ESA compliance is required Currently a bottleneck 4

5. Requirements ES data must remain confidential Secure website Must be intuitive and easy to repeat Must provide a format that meets specific specs High uptime for multiple users Users need to review previously generated content Admin/user differentiation 5

6. Enter the ICT Tool! Capabilities: – User management system – Spatial analysis engine that answers complex, dependent inquiries via geoprocessing – ES report generation system – Document tracking and review – Metadata tracking* 6

7. How to ICT Log In Launch the ICT 7

8. How to ICT (2) 8

9. …and in return: 9

10. How Does It Work? Web front end, user management and report management system (.NET); Arc Server mapping application built in Flex; Python scripting for geoprocessing Geoprocessing explained: 10

11. 11

12. How… continued Several types of endangered species data. This is NEVER VISIBLE in the tool. Two types of vector data, point and polygon; each is checked independently. Raster habitat suitability data; checked via buffer and spatial statistics. 12

13. Quick and Dirty 13 1. Large buffer to note all species in the area Bald Eagle nest Sheepnose Mussel bed Indiana Bat Running Buffalo Clover Bald Eagle nest Indiana Bat Bald Eagle nest Sheepnose Mussel bed

14. 14 2. For each practice and each species, run a buffer. Indiana Bat Bald Eagle nest Sheepnose Mussel bed 3. Sheepnose mussel + Fence (382) = 400 meters

15. 15 Indiana Bat Bald Eagle nest INCLUDE 4. Bald Eagle + Fence = 200 meters

16. 16 Indiana Bat Bald Eagle nest INCLUDE Indiana Bat + Fence (382) = 1 meter

17. Report Query So for Fence (382) we have only the Bald Eagle; query tables and get: B11 = This practice may have a beneficial effect if implemented near bald or golden eagle nesting sites or eagle habitat and where appropriate buffers are maintained, enhanced or constructed. 17

18. Full Analysis 18 User input Find all local species Execute prac/spec buffers against points Execute prac/spec buffers against polygons Execute buffer check against each habitat model Check if certain practices are > 17 acres (Indiana bats) Determine report type – species/interactions, Species/no interactions, no species Compile codes Query codes for report content Organize content into XML for report generation Flex ArcPy Python Generate Report.NET

19. Notable features Suite of web map features; address locator, nav tools, lots of bg data, etc. User management and authentication system Each user has access to a report management system Dynamic – easy to implement new species, new recommendations, new spatial data, etc. Fire and forget Fast performance (avg time is ~8 minutes) 19

20. Conclusions Geoprocessing can greatly streamline permitting (and similar processes). Complexity of analysis isn’t necessarily a limiting factor… …so long as the client has a strong grasp on that complexity! Confidentiality of data can be maintained. 20