1 / 24

Parts of the NHD

2006 Network Users’ Meeting Chesapeake Bay Program Regional Exchange for Non Point Source Best Management Practices April 18, 2006 Nancie L. Imler PA DEP Chief Information Officer. Parts of the NHD. Waterbody. Watersheds. Streams. Junctions. Benefits of the NHD.

sancho
Download Presentation

Parts of the NHD

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. 2006 Network Users’ MeetingChesapeake Bay ProgramRegional Exchange for Non Point SourceBest Management PracticesApril 18, 2006Nancie L. ImlerPA DEP Chief Information Officer

  2. Parts of the NHD Waterbody Watersheds Streams Junctions

  3. Benefits of the NHD • The NHD eliminates competing stream layers. • Commonwealth has streams outside of Pennsylvania. • The NHD provides easier integration with Federal partners and surrounding states. • The NHD is better at using the Geographic Names Information System (GNIS) to properly name stream segments. • Data models utilizing the NHD can be used with limited additional development. • PROVIDES THE FOUNDATION FOR INTEGRATING LAND AND WATER ON SAME MAPS! Critical for water quality issues.

  4. Conflation – Moving Existing Enterprise Data to the NHD NHD Locator Tool (tool for existing software applications to call and provide visual of where point is placed and then stored on NHD) Instream Comprehensive Evaluation (ICE) Tool (tool for data not normally in enterprise applications to be enterprise and placed on the NHD )

  5. Data Prioritized for Placement on the NHD Framework • 305(b) 303(d) Stream Impairment Data • TMDLs • MacroInvertebrates • Fish • Chapter 93 Water Quality Standards (Existing and Designated Uses • Act 220 State Water Planning • NPDES Permitting and electronic Discharge Monitoring Reports

  6. Tying Non-Point Source Best Management Practices (BMPs) with NHD • Chesapeake Bay Model • Coastal Zone Management • Total Maximum Daily Loads (TMDLs) • Tributary Strategies • EPA 319 Grants • Growing Greener Grants • Department of Agriculture Programs • Private Conservation Programs • Nutrient Trading

  7. Implementation Occurs by Personnel at Many Organizational Levels • County Conservation Districts (CCDs) Technicians • NRCS State Conservationists • River Basin Commissions • Regional Office Teams • Central Office • Mineral Resources • Local Watershed Groups

  8. Implementation Occurs at Various Geographical Levels on Paper and Some IT Tools • County • Watershed • Regional • Tributary • Commonwealth-wide

  9. 2004 EPA National Environmental Information Exchange Network Challenge Grant • Challenge Grant Partners: • MD Department of Natural Resources • MD Department of the Environment • MD Department of Agriculture • VA Department of Conservation and Recreation • VA Department of Environmental Quality • USEPA Chesapeake Bay Program Office • PA DEP (challenge grant lead)

  10. Resident Agencies for State EPA Nodes • PA – PA DEP • VA – VDEQ • MD – MDE • DC – Department of Health State Agencies Responsible for NPS BMP Collection and Reporting • PA – PA DEP • VA – VDCR • MD – MDA, MDNR • DC – Unknown

  11. Grant Objectives: • Build an EPA Network Node at the CBPO to support environmental information exchanges in an automated fashion. • Develop standard templates to be used on the NEIEN to move tabular and spatial data for NPS BMP. • Map jurisdictional NPS BMP data from state sources into the templates. • Transfer the NPS BMP data from the CB jurisdictions to the CBPO network node for assembly into the model deck and for use in Geographic Display Tools for the region.

  12. Orientation Meeting January 2005 • NEIEN 101 – What is it? What templates exist now? What exchanges are occurring? (Molly O’Neill) • Brief explanation of the Chesapeake Information Management System. • What are Web Services? • Review of CB jurisdictions’ proposal to EPA and its objectives. • Why select NPS BMPs ? • NRCS as a Federal Partner for NPS BMP data standards. • What will be the Governance Model for the Grant activities?

  13. Why NPS BMPs? • the most difficult business process • that has no set standard template to send to the Bay • that has no set technology to deliver the data to the Bay and arrives in various file formats • that requires manipulation prior to its use in the model due to disparate spatial scales and processing discrepancies • that is not easily imported into regional graphical tools • that has federal and state financial and business processes involved • that could be reusable by all states and other regional groups

  14. Requested 2-Year GrantTotal Funds Requested: $395,424Total Project Cost: $395,424

  15. Breakdown of Funding • PA DEP -- $111,576 for Travel; Contractual Services for BMP repository work in state; and regional node support at CBPO • VA -- $141,924 for BMP and Node Personnel and Travel • MD -- $141,924 for BMP and Node Personnel and Travel

  16. DEP Grant Agreement • Between DEP and the Maryland Department of the Environment • Between DEP and the Commonwealth of Virginia Department of Conservation and Recreation • Scope of work and budget

  17. Scope of Work • Each jurisdiction provides a “Network Readiness Assessment Report” • Status of State Node, standards for building web services; security and exchange tools; and its ability to handle the BMP Flow • “AS IS” business processes for BMP reporting to the Bay • “TO BE” business processes for BMP reporting to the Bay

  18. Scope of Work • Build the Network Node at the CBPO to facilitate the exchanges “from” and “to” the CB states. • Modify the CIMS Memorandums of Agreement (MOA) with its partners to further define the standard node catalog of available information with its metadata. CIMS will need to have its enterprise architecture documented for the distributed data system and released to its partners. The MOA could be the Trading Partnership Agreement.

  19. Scope of Work • Diagram of current data flows of BMP with list of problems and issues • Design of the Data Exchange Template with Headers and Subsets for NPS BMPS • QA functionality defined • Test Plan and Results • Use of Exchange Protocol • Project Report • Presentation Materials • Updates to the DET Registry, DET Repository, Flow Configuration Document Registry and Service Description Repository

  20. Governance Model

  21. NPS BMP Workgroup • Identify and prioritize NPS BMPs for template development • Identify common and unique data elements for NPS BMPs for headers and subsets • Determine vocabulary • Develop the taxonomy • Request review from ECOS/EPA

  22. Technical Workgroup • Build the CBPO network node under EPA specifications • XML technology applied to NPS BMP Workgroup’s templates taxonomy • Support taxonomy • Quality Assurance • Training needs

  23. Questions? ? Questions? Questions? Questions? Questions? Questions?

More Related