EN-GEOSS Interoperability Scope
From Exchange Network Wiki
Contents |
Exchange Network / GEOSS Interoperability Demonstration Project
Draft 3/11/08
Media:EP-GEO-Demonstration ls.ppt
Project Objectives:
- Demonstrate discovery of GEOSS data and service assets made available through EPA and its partners.
- Provide examples and lessons learned to help identify gaps in current EPA registration in GEOSS data and services catalogs, as well as opportunities for providing data / services to GEOSS that we may not yet be able to provide.
- Demonstrate the use of one or more flows of Exchange Network data outside the Network itself – through use of “wrappers” or similar approaches, open EN services to clients that are not on the Network.
- Show how the security model of the Exchange Network can be used to provide vetted access to clients using non-EN client technology.
- Utilize OpenGIS standards to demonstrate the benefits of this approach as a means to facilitate data discovery, access, integration and analysis.
- Use Commercial mapping APIs and consumer grade client GIS technology to illustrate the flexibility of Web Services Oriented Architecture (WSOA) for building operational environmental analysis capabilities.
Milestones / Deliverables:
- Through Exchange Network’s Geo Task Force, help finalize a final set of requirements and guidance for the adoption of standards compliant geographic encoding for EN data flows (GeoRSS GML).
- Develop sample schema fragments for existing flows to demonstrate the simplicity of this approach.
- Geospatially enable one or more Exchange Network flows in the Pacific Northwest / Puget Sound region using GML.
- This step requires building a wrapper or helper service that would perform the necessary XSL transformation without changing the existing data flow.
- Develop one or two comprehensive use cases that define the pilot scenario. These will utilize data from EPA, its Exchange Network and GEOSS to address a single environmental problem or set of problems.
- Select an existing, extensible client application as the basis for client development. Client should be compliant with the following OpenGIS specifications:
- GML
- WMS / WFS / WFS-T / WCS
- CS-W (capable of discovering resources on a CS-W)
- And ideally, WPS
- GML
- Customize the client application to facilitate discovery of Exchange Network, GEOSS and other data / services.
- Customize the client application to facilitate the access and integration of these data and services.
- Customize the client application to include one or more specialized geoanalytical processing capabilities as defined in the pilot scenario. These could be enabled as web services (i.e., WPS or ArcGIS Server), as capabilities built into the client, or some combination of both.
- Create and deliver a presentation and interactive demonstration for the 2008 Exchange Network Conference in Nashville, TN (April 28 – May 1).
- Using feedback from the presentation and EPA staff, incorporate final changes into the pilot client application.
Ideas on the attributes of a solid demonstration project expressed by the Task Force during March 26 call:
- Discovery across domains, ability to add context, federation on steroids.
- Flood/high water stuff---
- USGS NHD event data from MnRAD…model for other states?
- Showing data flow as package, e.g., field data flow in and out
- Real simple interface that could consume data from multiple sources
- So folk would not have to develop it
- Shared mapping resource that could be distributed
- So folk would not have to develop it
- Operational prototype
- Transformation service expose and demonstrate as service
- Demonstrate activity within EN data, e.g., ASIWPCA DW shared tools watershed analysis
- Filtering, scrounging data
- WQX rich data source
- Expand EN data into new areas of coverage
- Filtering, scrounging data
- Demonstrating interoperability
- Security
- Data exchange
- Discovery
- Security
- Show ability to add new resources, e.g., ability to plug and play
