u.s. environmental protection agency central data exchange pilot project promoting geospatial data...
TRANSCRIPT
U.S. Environmental Protection AgencyCentral Data Exchange Pilot Project
Promoting Geospatial Data Exchange Between EPA and StatePartners.
April 25, 2007
April 25, 20072
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, 20073
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, 20074
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, 20075
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, 20076
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, 20077
Conceptual Model Architecture – Search & Discovery
Web UI
Geo-ExchangeWeb CDX user
System Users
CDX Node EPA RTP
CDX Node Database
Internet
Geo-ExchangeSearch and Discovery
FormsLogin
ArchiveLog
WI Node
Web Services
Web Services
Geo-ExchangeDataflow
Service Provider
Metadata Search
Connector
SCOCatalogServer(Isite)
Z39.50Connector
RTP Node
Metadata Search
Connector
RTPMetadata
Server(ESRI
Arc SDE)
Z39.50Connector
CDX NodeMetadata Catalog
Provider
· Provide search criteria· View search result
· Support mapping capability to define boundary;· Store the search request;· Solicit the search from the user defined catalog
providers;· Present search result to the user; and· Present search history.
· Receive the solicit search request from CDX Node;
· Communicate the search request to the search engine via the connector;
· Return the search result to CDX Node.
CDX Web Geo-Exchange User
Web Services
April 25, 20078
April 25, 20079
Search Interface Design
Clicking the “Use Map Interface” button, the user
will see the screen below.
April 25, 200710
April 25, 200711
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, 200712
Link to Data Using Web Based Map Viewers
April 25, 200713
Link to Data Using Standard GIS Desktop Tools
April 25, 200714
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, 200715
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, 200716
Design
Geospatial Database
Retrieve Metadata
WebServices
2.3 Submitdata
GeoToolkit
ConversionService
MetadataExport
Software
GEOSubmission
Users
1. Exportto local GML format
ExportedMetadata
(local GMLformat)
Export data into"local" GML
Format
2. GEO Submission
Toolkit UI
2.1.2 ReadExported data
2.1. Submitdata
2.1.3 Convert localexported metadata into
standard GML/SGML XMLwith Header
State/Regional Environment
WebServices2.4 GEO Submission
GeoDistributor
CDX NodeDatabase
CDX NODE
WebServices
Connector
FRS/LRTDatabase
EPA FRS
Archiving Archiving
Submission
BusinessLayer
Mapping/Conversion
Rules
2.1.1 Access localmapping/conversion
rules
SGMLGML
2.1.Convert data
Data Provider CDX Destination
April 25, 200717
What?
• Geospatial Data View – Boston, MA
April 25, 200718
• Export Data from local geospatial database to GML
Overview – Geospatial Data Submission
April 25, 200719
Overview – Geospatial Data Submission
• Export Metadata from local database to SGML
April 25, 200720
Overview – Geospatial Data Submission
• Load GeoToolkit and Map Source to Target Fields using Configuration Editor
April 25, 200721
• Submit via conversion service – loads mapped data to backend database
Overview – Geospatial Data Submission
April 25, 200722
• View Target File in transfer schema format
Overview – Geospatial Data Submission
April 25, 200723
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, 200724
Publishing Capabilities
• Convert to KML?