1 / 27

NHD Demonstration Application NHD Stewardship Conference New Orleans March 30, 2012

NHD Demonstration Application NHD Stewardship Conference New Orleans March 30, 2012. Andy Weiss: WA Dept. of Fish and Wildlife Rick Jordan: WA Dept. of Ecology Arleta Agun: WA Dept. of Fish and Wildlife. Rick, in response to Kevin Roth’s un-retirement. “When pigs fly and hell freezes over,

blaise
Download Presentation

NHD Demonstration Application NHD Stewardship Conference New Orleans March 30, 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NHD Demonstration ApplicationNHD Stewardship ConferenceNew OrleansMarch 30, 2012 Andy Weiss: WA Dept. of Fish and Wildlife Rick Jordan: WA Dept. of Ecology Arleta Agun: WA Dept. of Fish and Wildlife

  2. Rick, in response to Kevin Roth’s un-retirement “When pigs fly and hell freezes over, When elephants rumble on the ocean floor, and trained bears twirl and twirl some more When purple kitties jump and fly, and 50 foot mice touch the sky, When fish are talking and snakes are walking, Then about working with the NHD I’ll consider talking” If Jeff paid his way AND got him courtside Final Four Tickets, he would attend

  3. Why LLIDs ? • NHD already has a single stream identifier: the GNIS ID. Not universal, and tied to GNIS. • LLID = Lat-Long ID = the long/lat in Decimal Degrees of the outlet of the ‘single stream’. Can be generated automatically once you determine the single stream. • Most of our thematic data contains the LLID to reference the stream. Built in QA/QC for batch transforms. • Presents linear referenced data in terms that our bios and end-users know (RM 43.2 to RM 50.9 on the Yakima River) compared to NHD relative reach measures. • Allows reporting out as river miles on a single stream, and bios to provide data in terms that they understand. We provide hatched measures on single streams, and measures for key landmarks. Easy to compute river distance between 2 points. • Regional partners such as StreamNet use LLIDs for data management

  4. Assigning LLIDs to NHD as events • WDFW stream data had GNIS ID and GNIS names • Match GNIS_IDs between WDFW str24 and NHD and xfer to NHD copy • Gets 90% of fish-bearing streams • Manually conflate fish streams with no GNIS_ID • Send all the little streams to Ecology (their LLIDS match NHD really well)

  5. US / Canada trans-boundary routes

  6. Maintenance database and Publication Dataset • NHD reaches • LLID as multi-reach HEM events => LLID routed single stream featureclass (river miles) • FishDist as multi-reach NHD HEM events => events on LLID routes (river miles) • FishDist as a featureclass (stream lengths) • Similar stacks for all other NHD events • HEM not required for end-users

  7. GNIS Issues

  8. Consistent Physical Stream Attributes • NetMap / NetTrace: Dan Miller, Lee Benda (ex-UW geomorphologists) • http://earthsystems.net/ • State of the art geomorphology and hydrology. • NetTrace: DEM derived gradients, bankful width, valley width, upstream contributing area, mean annual flow. • NetMap: Erosion / sediment delivery models, habitat suitability models (Intrinsic Potential), wood accumulation • Currently being used for watershed characterization, fish distribution logistic regression models, and GRTS sampling designs.

  9. The NHD Application Demo Originally presented in December 2010 to the State of Washington’s Geographic Information Technology Board, a subcommittee of the State of Washington Information Services Board that set’s state agency IT policies. NHD adopted as the state’s framework hydrography Layer in January 2011

  10. Goals • Show the multi-agency hydrographic datasets now registered to the NHD in the Lower Skagit. • Demonstrate the power of the NHD data model, networking capabilities, events, and shared applications. • Perform a variety of analytictasks on these integrated and coincident hydrographic datasets.

  11. Dirty Laundry: WDFW, WDNR, and WECY all use and maintain different hydro linework. USGS and WDOH Partnership Project: Test technology, business processes, and applications to achieve a unified hydrography.

  12. Improving Mainstem Rivers • 2D representation of Streams • Ecology Shorelines of the State, DNR S-type waters • Contributions from Skagit County GIS shop

  13. Agency Data Sources (Used in Demo) WDFW • FishDist • LLID • SaSI • Facilities • Barriers / Culverts WDNR • Water Typing WDOH • Drinking Water Sources USGS • Dams • Stream Gauges WECY • Water Quality Assessment (303d / 305b) • Water Quality Standards • Regulated Facilities • Monitoring Stations NOAA • Steelhead Intrinsic Potential Model WDOT • Bridges • Road x stream crossings NWIFC • Fish Distribution

  14. Applications • Spill response and impacts • Downstream Trace • Impacted Drinking Water Sources (DOH) • Impacted Salmon habitat (DFW) • Upstream Trace to identify potential pollution sources • Culvert removal (DFW Barriers) • New habitat opened in DNR Water Type F • Summarize newly opened NOAA predicted Steelhead habitat • Exposure of ESA listed species to Water Quality Impairments • Overlay DFW FishDist with DOE 305(B) list • Comparison of DFW FishDist with DNR water type codes • Find inconsistencies between the 2 datasets

  15. 1) Spill response and impacts Bad Crash on the Bridge Anacortes Water Intake Highway 9 Bridge Nasty Stuff Flowing Downstream

  16. 1) Spill response and impacts • Input Data: • FishDist: DFW Observational data on Salmonid Distributions • DOH surface water intake points • USGS Stream Gauges • NPDES pollution sources • Downstream Trace from HWY 9 bridge over the Skagit R. • Find all water intakes and USGS stream gauges • Find Salmonid spawning and rearing areas • Use distance from spill and instantaneous flow for transport and attenuation models • Upstream trace from Anacortes surface water intake to identify NPDES sites as potential pollution sources

  17. Demo # 1

  18. 2) Culvert Removal (DFW Barriers) • Input Data: • DFW Fish Passage and Diversion Screening Inventory (culverts, irrigation diversions, …) • DNR Water Types • NOAA Intrinsic Potential habitat model for Winter Steelhead • Trace upstream from a blocking culvert • Summarize length of DNR Water Type F reaches that have been opened up • Summarize Steelhead Intrinsic Potential above barrier

  19. Demo # 2

  20. 3) Exposure of Salmonids to Water Quality Impairments • Input Data: • FishDist: DFW observational data on Salmonid Distributions • 305D list: ECY stream reaches with Water Quality Impairments • Use Event Overlays to intersect the 2 data sets • Fast. Really Fast • Map areas of concern • Output event table => Excel Pivot Table • Flexibly summarize results

  21. Demo # 3

  22. 4) Comparison of DFW FishDist with DNR Water Type Codes • Input Data: • FishDist: DFW observational data on Salmonid Distributions • DNR Water Typing: Observed and Modeled distributions of any fish bearing stream reaches • Use Event Overlays to intersect the 2 data sets • Fast. Really Fast • Identify reaches with FishDist but no DNR type F • Map areas of concern • Output event table => Excel Pivot Table • Flexibly summarize results

  23. Demo # 4

  24. Progress as of March, 2012

  25. Fish Passage Barriers (USGS grant 2013)

  26. Shout outs • USGS POC: Hank Nelson • USGS Geospatial Liaison: Tom Carlson • USGS NHD leadership ($$$) • EPA node exchange ($$$) • PNWHF: Dan Wickwire and friends • Stewardship (Dan) • Workflows (Jay Stevens) • LiDAR: (Craig Ducey) • WBD trans-boundary: Karen Hansen • Gray beard wise-man: Rick Jordan (emeritus)

More Related