1 / 30

A Vision for Stewardship of the Watershed Boundary Dataset (WBD)

A Vision for Stewardship of the Watershed Boundary Dataset (WBD). Overview of WBD Philosophy of WBD stewardship Differences and commonalities with NHD USGS roles for WBD integration with NHD Challenges Current stewardship initiatives

oma
Download Presentation

A Vision for Stewardship of the Watershed Boundary Dataset (WBD)

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. A Vision for Stewardship of the Watershed Boundary Dataset (WBD) • Overview of WBD • Philosophy of WBD stewardship • Differences and commonalities with NHD • USGS roles for WBD integration with NHD • Challenges • Current stewardship initiatives • SUMMARY-Value, implications, goals of NHD/WBD integration NHD/WBD Stewardship Conference April 2009 Karen Hanson, USGS Dan Wickwire, BLM

  2. Need for one common (authoritative) hydrologic unit dataset • Delineations of hydrologic unit boundaries prior to 2000 were “stove pipe” type efforts • State and federal agencies were expending large budgets to create often redundant and inconsistent datasets • One nationally consistent, hierarchical, and larger scale dataset was needed that would meet both federal and state requirements for both analysis and programmatic reporting • Guidelines were developed by NRCS and USGS along with other interagency partners to support the certification program to achieve this goal

  3. The Watershed Boundary Dataset • Defines the aerial extent of water drainage to a point • Establishes a base-line drainage boundary framework, accounting for all land and surface areas • Topographically defined dataset impartial to administrative units, special projects, particular programs, or any one agency • Delineates and georeferences the hydrologic units to USGS topographic maps, meeting the National Standards for Spatial Data Accuracy (NSSDA) • 1:24,000 scale, lower 48 states and Hawaii • 1:25,000 scale, Puerto Rico and the Virgin Islands • 1:63,360 scale, Alaska • Uses Digital Orthophoto Quarter Quadrangles (DOQQs) orhigher resolutionimagery, contours of elevation, stream locations and other relevant data to improve the accuracy or currency of the hydrologic unit boundaries

  4. www.ncgc.nrcs.usda.gov/products/datasets/watershed

  5. Federal Guidelines, Requirements, and Procedures for the National Watershed Boundary Dataset Techniques and Methods 2008 http://pubs.usgs.gov/tm/tm11a3/

  6. WBD Delivery of “certified” data http://datagateway.nrcs.usda.gov/

  7. National (managerial component) Steering Committee: • USGS • CHAIR-Katherine Lins(Chief Office of Water Information-Headquarters) • Jeff Simley(NHD Program Manager) • David McCulloch(Office of Water-Headquarters) • NRCS • Jerry Harlow(Director of National Cartography & Geospatial Center (NCGC)-Ft. Worth) • Steven Nechero(Technology Application Team Leader, NCGC-Ft.Worth) • EPA • Wendy Blake-Coleman(Office of Environmental Information-Headquarters) • Tommy Dewald (USEPA Office of Water-Headquarters) • USFS • Ted Geier(Staff Hydrologist Air, Water, Lands, Soils, Minerals & Environmental Services, Region 9) • BLM • Jim Renthal(Soil, Water, Air Program Leader-Headquarters)

  8. USGS Project manager; national technical coordinator: • USGS • Karen Hanson(Physical Scientist-Salt Lake City) • National Technical Review office: • NRCS • Laura Davenport(Geographer-National Cartographic and Geospatial Center, Ft. Worth, TX) • Mid Atlantic Coordinator: • EPA • Don Evans(GIS Team Leader-EPAR3) • National liaison: • EPA • Milo Anderson(GIS Coordinator-EPAR5) • Other: • NCGC-NRCS • USGS-Salt Lake City, EPA R3-R5, WYGISC-U of WY • USGS Administrative staff • USGS staff, Wendy Danchuk and others, in Madison Wisconsin, working on the updated standards

  9. Agencies with WBD Stewardship lead

  10. WBD Stewardship Philosophy(A few years ago our stakeholders started asking for this) A need……. For continuedconsistency, data integrity, and quality of this “certified dataset” that adheres to national guidelines in order to meetprogrammatic and reporting needs For continued coordination to ensure that WBD remains the single recognizedhydrologic unit dataset vs. multiple stove piped datasets To enhance WBD by recognizing the importance of, and incorporating local on-the-ground knowledge as the dataset is used To protect an estimated $20 million investment and keep maintenance costs down

  11. WBD Stewardship Philosophy (cont’d) A plan that……. Recognizes stewardship roles and responsibilities at both the national and in-statelevels NATIONAL: Provides program leadership and management Works with state stewards to ensure success of WBD stewardship objectives Ensure “certification” integrity is maintained Assist with technical issues Support successful integration of NHD and WBD stewardship STATE: Coordinate all stewardship activities within state Local stewards, interagency partners Work with national data set managers and stewards to ensure success of WBD stewardship objectives Support successful integration of NHD and WBD stewardship More details on Thursday (Dan, Mark)………..

  12. WBD Stewardship Philosophy (cont’d) A plan that…….. • Fosters communication and collaboration at all levels of stewardship • Ensures availability of dataset for stewardship, analysis, mapping, and reporting activities • Works with the NHD stewardship community to implement integration of stewardship for the NHD and WBD • Facilitates integrationwith other data framework layers

  13. WBD Stewardship Challenges Develop a common understanding of roles and responsibilities, and sustainable agency support of those roles Look at synchronizing terminology with A-16 supplemental guidance Design and implement a fully integratedapproach to stewardship of NHD and WBD both at the national and state level Implement a stewardship program that: Meets stakeholder needs duringNHD/WBD integration phase Prepares stakeholders for the fully integrated environment Satisfies the certification requirement of the WBD Satisfies the needs of the 50 states, and U.S. territories

  14. WBD and NHD StewardshipDifferences • WBD is a nationally “certified” dataset where national guidelines need to be applied to ensure a high level of national consistency for the user community • NRCS and USGSshare joint national responsibility for the WBD, whereas USGS is the national steward for the NHD • The in-state NHD and WBD stewardship agencies and organizations are not always the same

  15. Percentage of states which have a dual WBD/NHD Steward

  16. WBD and NHD StewardshipDifferences (cont’d) WBD provides a consistent programmatic framework for many agencies. Impact to ongoing reporting systems must be considered with any changes to the data Edgematching-there are as many polygons on borders as internal to states All linework placement within the WBD is highly coordinated and negotiated between in-state partners For example…………..

  17. WBD and NHD StewardshipCommonalities Both have state based principal stewardship Both rely on collaboration between partners at the local, state and national level Both have the goal of maximizing return on investment of development and stewardship costs Both benefit by increased level of vertical integration and spatial integration Both benefit from a synergistic implementation of stewardship

  18. WBD Maintenance Simplified Process Workflow WBD User Determines That Edit is Needed WBD User Submits Change Request To State Steward State Steward Coordinates with All Partners State Steward Submits Edit to National Steward State Steward Performs Edit on National Database State Steward Accepts or Rejects Proposed Change USGS/NRCS National Stewards Performs QA/QC Accepts or Rejects Edit National Database Steward Posts Successful Edits to WBD National Steward Notifies State Steward and WBD User Community

  19. Delivery • Once fully integratedthe NHD and WBD will be jointly housed in Denver, and Denver will be the interface node for stewardshipmaintenance transactions • The NRCS will house a replicate of this database for distribution only • Sites that customers will obtain NHD and/or WBD data through (1) The National Map, (2) the NRCS Data Gateway, and (3) a hydrography specific web site (http://nhd.usgs.gov), (4) state repositoriesthat are developed to meet state based requirements • Users will have several options for downloading from the national repositories. This will include (1) NHD-WBD options, (2) areas of coverage, and (3) levels of hierarchy • Added value attributes may be available within WBD datasets residing on State delivery sites

  20. USGS Personnel Structure to accommodate integration of WBD with NHD NHDProgram Manager:Jeff Simley • Overall project decisions • Keep projects on track • Ensure program objective are met • Keep stakeholders abreast of progress • Define resource needs • Responsible for programmatic long-term planning and implementation

  21. USGS WBD Personnel (cont’d): WBD Project Lead:Stephen Daw, NGTOC-Denver • Technical implementation, transaction posting and update and editing processes and software • Manage day-to-day activities of the project and will assure milestones are met • Assist with Stewardship activities • WBD edit training WBD Program Manager:Karen Hanson, USGS Water Resources • Assureobjectives of the WBD programare maintained • Along with NRCS, provide National QA/QC review on WBD edits • Implementation of a WBD stewardship program combined with the NHD stewardship program • Supplemental guidance protocol development Hydrography Section Chief:Paul Kimsey,USGS-NGTOC • Responsible for maintaining the integrity of the NHD stewardship program • Assuring that WBD stewardship operations are fully assimilated into a joint program Others…

  22. State Stewardship Work Group (SSWG) Meet Bi-monthly to discuss all aspects of Stewardship: Dave BrowerDan Wickwire Natural Resources Conservation Service Bureau of Land Management State of Washington State of Oregon Linda DavisKaren Hanson Idaho Department of Water Resources U.S. Geological Survey State of Idaho National WBD Technical Coordinator Ann FritzDavid Anderson North Dakota Department of Health NHD POC (previous Florida State Department of Environement) Steve Nechero Natural Resources Conservation Service National Cartography & Geospatial Center

  23. Stewardship issues being addressed by SSWG: • WBD Issue Paper • NHD/WBD Stewardship Roles and Responsibilities • Using High Resolution for WBD improvement • Hydrologic unit names • 7th and 8th level umbrella guidance • Spatial integration of WBD with NHD • Coastal Pilot

  24. Geospatial Line of Business-Data Lifecycle Stages April 6, 2009 completed the evaluation documentation criteria for WBD-requirements Define Archive Inventory/ Evaluate Business-driven User needs Obtain collect/create Use/Evaluate Validate/Enhance Access Maintain

  25. SUMMARYBenefits of a joint WBD/NHD NHD and the WBD naturally complement each other Both are used extensively in hydrology, biology, resource management, and pollution control Improves interoperability of the two datasets, and for users A single hydrography geodatabase facilitates all aspects of joint stewardship of the two feature databases-NHD and WBD Joint data distribution services Joint stewardship operations Joint program management Combined operations to the extent possible Many positive outcomes to have WBD become part of The National Map (TNM) NHD GeoEdit tool could accommodate WBDeditsand provide feature levelmetadatatracking

  26. SUMMARYGoals of a joint NHD/WBD Integration at all levels: Programmatic Operational Technical Science Ensure future efforts are planned and implemented in tandem

More Related