1. GEOSS Architecture Implementation Pilot AIP-3 Engineering Use Cases Nadine Alameh & Josh Lieberman AIP-3 kickoff Frascati, Italy March 11-12 2010

2. Plan for Session 1: Discovery and Access Quick introductions of current 3 GEOSS Portals –ESA FAO –Compusult –ESRI Overview of use cases End-to-end discovery Open discussion –Use cases in scenarios –New uses ? –Mapping process Enterprise modelling recommendations

4. Use Cases in AIP-3 Apply/specialize AIP-2 use cases

5. https://sites.google.com/site/geosspilot2/Home/scenario-use-case-matrix

7. End to End to the End of Discovery Backwards: Forwards: Middle Outwards Users & Issues Vocabulary & Connections Applications & Queryables Publication & Registration Immediate view of relevant data Standard, fine- grained data access Drill-down to Evaluation Metadata User Questions & Concerns ConsumerIssue Vocabulary Concept Mapping & Inference Data Vocabulary Consumer

8. Publication and harvesting issues Need to further investigate need for Earth Observation Profile for the Clearinghouse(s) Need to capture best practices for catalog registration –Where to publish new data/services? In community catalog or GEOSS CSR? –How to search across registered catalogs? Need to capture best practices for dealing with duplicate (sometimes inconsistent) records, versioning, deleting entries, etc Need to keep working on documentation of the GCI for new participants Need to apply enterprise modeling process from the beginning Need to consider the mapping of INSPIRE components/metadata to GEOSS CSR classifications & interoperability arrangements

9. Discovery issues Consider renaming Search for Metadata use case or splitting it into –Search for data –Search for services (useful for integrator user) –Search for metadata (useful for integrator user) Add Integrator User in use case diagram Need more user representation

10. Plan for Session 2 Workflow and processing –Review of the relevant responses –Description and publication of WPS/workflows –Discovery of WPS/workflows –Use of WPS/workflows Integration of taskable sensors –Presentations by primary participants –Sensor Web use cases New use cases –Mediation/vocabularies –User identification –Data sharing –Collaboration

11. Responses - Processing & Workflow Genesis WPS (clipping, reprojection, generalization, format conversion on vector and raster data as well as overlay, contouring, spatial interpolation, …) Population estimation Web Processing Service (CIESIN) Kepler Scientific Workflow System (CSIRO) WPS for combining and comparing satellite time series with in situ and model data (PML) INTAMAP automated interpolation service (ifgi) ERCS Workflow service (SPOT Infoterra) Geospatial processing web services- GRASS (GMU CSISS) PBELPower Engine (GMU CSISS) e-habitat WPS (e-habitat) WPS for calculating drought hazard using EDO indexes (EuroGEOSS Genesis Drought)

12. Workflow and Processes Balancing need for processing details and options with level of description in WPS Capturing uncertainty propagation as result of workflow –Metadata as additional output Add construct workflow use case (with Integrator actor) How to describe WPS to be discovered appropriately? –Registering as virtual product Interaction with catalog in workflow creation Possibility of creating ontologies for WPS types (classification, reprojection, etc) –Improved discovery as well

13. Responses- Sensor Web SOS-based Hydrological Sensor Web for South Esk River (CSIRO); and Sensor Event Service for river flow alerts Improved discovery and binding to Sensor Web (Compusult) Combining SWE and geoprocessing in near real time system (ifgi) GIS FCU SWE services (SOS, SPS, SAS) for disaster management (GIS FCU)

14. Sensor Web Integration Additional responses –NOAA IOOS –EuroGEOSS – Genesis – 52 North SWE for drought Need extension to CSW for sensors? What are the user requirements for uncertainty and validity? –Provenance of data and models within hydrology domain –QA4EO?