U.S. Environmental Protection Agency Central Data Exchange Pilot Project Promoting Geospatial Data Exchange Between EPA and State Partners. April 25, 2007

2 Outline Introduction –What is the Geo-Exchange project? –How does this relate to the ENDS project? –Why is this important? Search and Discovery Effort –Approach –Conceptual Model –Overview Geospatial Data Exchange Effort Next Steps

April 25, Introduction What is the Geo Exchange Pilot Project? –Effort involving EPA, State, and Private Partners to: Search and Discover Geospatial Metadata from Distributed Catalogs Support Geospatial Data Flows (GML, SGML) –Using a Standards-Based approach through the Exchange Network Team Members –EPA Region 5 –Wisconsin Department of Natural Resources New Team Members –Michigan, Minnesota, Great Lakes Commission, Ohio, New York

April 25, Introduction How does this relate to ENDS? –ENDS Purpose is to discover Exchange Network Services Search tool connects to CDX database which stores information about nodes and supported services at CDX ENDS data flow is an Exchange Network schema for loading the database and retrieving data. –Geo-Exchange Purpose is to find geospatial assets stored across distributed partners’ offices Search tool connects directly to distributed metadata catalogs to find geospatial information stored across the country Search & Discovery effort uses the FGDC schema for EN purposes.

April 25, Why is the Geo-Exchange Project Important? Search and Discovery Effort –WI State Cartographer’s Office maintains valuable geospatial assets –EPA Offices Maintain a number of valuable geospatial assets –Others do too! This service makes these visible to participating partners A step towards improved environmental analyses Geospatial Data Exchange Effort –Regional offices update EPA Facility data (e.g., point locations, boundaries) –These should be submitted to EPA databases so they are up to date –Geospatial data transfers are not simple flat files (lines, polygons, etc.) Transfer of geospatial data is not your typical data flow This service allows geospatial data to be transferred to backend databases

April 25, Approach – Search & Discovery Development Approach –Maximize reuse of existing standards and components –Minimize data replication Standards –Relies on Geospatial Metadata Standards –Z39.50 [Protocol and GEO Attribute Set] Utilize Existing Components and Technologies –Existing catalogs (EPA, WI, and new partners) –Existing Geo-coding services and Google map interface –Existing Geospatial Standards (FGDC CSDGM, Z39.50) –Existing EN web services (solicit/query search request) Data not replicated to central catalog –Exchange network provides direct query access to partnering catalogs Result: Participation is expandable and flexible

April 25, Conceptual Model Architecture – Search & Discovery

April 25, 20078

9 Search Interface Design Clicking the “Use Map Interface” button, the user will see the screen below.

April 25,

April 25, Search Result Interface Design List of search Results: selecting one produces the metadata record to the right Multiple online linkage options to data access

April 25, Link to Data Using Web Based Map Viewers

April 25, Link to Data Using Standard GIS Desktop Tools

April 25, Next Steps Broader Participation with Additional States –Initial Focus on Great Lakes States –Currently Includes: State of Michigan Minnesota New York Ohio Great Lakes Commission –Expansion for catalog types, access capabilities Different types of open-standards based catalog interfaces (CS-W, ZING/SRU) Different types of geospatial information (geo-referenced documents, etc) Access to data from metadata – use existing download or return Web Service request - Publishing

April 25, Approach – Geospatial Data Submission Overview –Allow offices to flow geospatial data and metadata (GML /SGML) to EPA repositories How does this relate to other EN data flows? –Allows geospatial data to be transferred to backend databases –Lays out a protocol for publishing geospatial data. Components –EPA Region 5 Partnership –Map GML/SGML data to EPA’s LRT backend repository –Client tool interface (‘GeoToolkit’) used to upload, map and submit data Source data can be mapped to target schema via ‘mapping aliases’ Interface allows user to select defaults and override information

April 25, Design Data Provider CDXDestination

April 25, What? Geospatial Data View – Boston, MA

April 25, Export Data from local geospatial database to GML Overview – Geospatial Data Submission

April 25, Overview – Geospatial Data Submission Export Metadata from local database to SGML

April 25, Overview – Geospatial Data Submission Load GeoToolkit and Map Source to Target Fields using Configuration Editor

April 25, Submit via conversion service – loads mapped data to backend database Overview – Geospatial Data Submission

April 25, View Target File in transfer schema format Overview – Geospatial Data Submission

April 25, Next Steps Generalize Geospatial Schema for Consistency for New Flows –Determine more generic approach that will allow for a more diverse set of conformant transfers –Provide oversight and direction for new geospatial flows being considered for the Exchange Network Update GeoToolkit –Validation checking on front end –Additional Help for errors

April 25, Publishing Capabilities Convert to KML?