Geo-Services Integration Application
From Exchange Network Wiki
Contents |
Exchange Network - Geo-services Integration Application
Draft description, objectives, and software requirements document
Please comment on this application directly on this page or by using the discussion thread.
EN-Geo Services Pilot Demo slides
Initial Requirements for Interoperability and Geo Demonstration
Note: These need to be complemented by some “business driven” requirements, such as the ability to view this data across jurisdictions, and the ability to juxtapose tabular and rich GIS output as well.
High priority
- Accept a polygon as an input parameter; Show EN/GML XML fragment encoding of the polygon
- Parse query along existing state boundaries and forward query to existing state nodes with simple bounding box. Use the HERE node states as the testbed if possible.
- Parse query and forward to other geo data sources.
- Receive results from state nodes and filter out results that are inside bounding boxes but outside original query polygon. Aggregate remaining results into single result set and return to client.
- Demonstrate WMS and provide EN key from WMS. (Already done.)
- Show/describe native EN services in CSW; Show wrapped EN services and other services in CSW; Demonstrate spatial query of CSW; Think about demonstrating spatially aware ENDS 2.0.
- EN data in GeoRSS feed (permit issuance, new sampling data available etc.) People able to see RSS feed working and how it looks. Find someone to generate from their web server.
- The application needs to provide opportunities for tech users to peek under the hood to see how things are done (e.g., provide the ability to view API/service definitions and XML instances). [A debug mode]
- The service should be up for 6 months to a year. (It could eventually live in the staging environment of CDX or www.beta.epa.gov.)
- In a few key places, we need to show some real tools on real platforms which produce/consume GeoRSS GML (and maybe a few others), so we can directly assess what ESRI does or does not support.
Medium priority
- Demonstrate an inherent geospatial function like buffering that would be much harder to accomplish using a relational database.
- EN to KML translation and invocation through an easy style sheet
- Demonstrate concept of services integration registry where compatible data sources, style sheets, and application/services are displayed for invocation. (This could be a mock-up and Jerry has written something like this previously.)
- Request and receive EN GML payload from WFS
Low priority
- Request and receive EN payload from a WFS-Simple Service
- Execute method
