Implementing GEOSS architecture with-and-for Users George Percivall Open Geospatial Consortium Task lead AR-09-01B
A process, elaboration of GEOSS Architecture SBA Tasks, UIC, CBC, STC User Needs, Scenarios requirements Design, Develop, Deploy ADC activities including: Architecture Implementation Pilot (AIP) Task AR-09-01b support Operational Capability GEOSS Common Infrastructure (GCI) Task AR-09-01a persistent implementation
GEOSS Interoperability Arrangements- From the GEOSS 10 Year Plan Reference Document - • Interoperability through open interfaces • Interoperability specifications agreed to among contributing systems • Access to data and information through service interfaces • Open standards and intellectual property rights • GEOSS adopting standards; agreed upon by consensus, preference to formal international standards • GEOSS will not require commercial or proprietary standards • Multiple software implementations compliant with the open standards should exist • Goal is that at least one of the implementations should be available to all implementers "royalty-free"
GEO Task AR-09-01bArchitecture Implementation Pilot • Support SBAs by developing new process and infrastructure components for GCI and the broader GEOSS architecture • Evolutionary Development thru AIP Phases • Demonstrate and document results to inform GEOSS Development progress “fostering interoperability arrangements and common practices for GEOSS”
AIP-3 Focus Areas • Technology Areas • Services Use Cases • Data Harmonization • Data Sharing • Semantics • SBAs addressed • Energy • Disaster Management • Climate Change and Biodiversity • Water Drought • Health: Air Quality
AIP Interaction with Users • User scenarios drive development • Implemented through use cases • Scenario WG interaction with CoPs • Scenario demonstrations recorded for later se • AIP support of UIC Usability Testing • GCI came from AIP-1 • AIP supported GCI usability testing • Recommend usability testing for AIP-4 results • AIP-4 focus on data to users • Increase access to UIC priority observations • Usability testing of access enablers
AIP Architecture Elements • Components • Manageable units hardware, software, networks • Services • Methods for components to interact using GEOSS Interoperability Arrangements • Use Cases • Describe what can be done with Services, e.g., Discovery, Access, Workflow, etc. • Scenarios • Meet SBA User needs; accomplished with Use Cases
Components Interact thru Services Main GEO Web Site GEOSS Common Infrastructure Registered Community Resources Client Tier Registries GEO Web Portal Community Portals Client Applications Components & Services Standards and Interoperability Mediation Tier Best Practices Wiki Community Catalogues Search Brokers Alert Servers GEOSS Clearinghouse User Requirements Workflow Management Processing Servers Test Facility Access Tier GEONETCast Long Term Archives Access Brokers Sensor Web Model Web
Energy Scenario and Use Cases (simplified) Reference: “Energy Scenario” Engineering Report, GEO AIP-3, Lionel Menard, January 6, 2011.
Energy Scenario and Use Cases (not simplified) Reference: “Energy Scenario” Engineering Report, GEO AIP-3, Lionel Menard, January 6, 2011.
Mine Paris Tech in GEOSS AIP – Solar Energy WPS Contact: Lionel Menard
From portal select desired theme(s) and area of interest Selected workflow automatically activates needed assets and models Flood Tasking and Product Generation in AIP-2 Disaster Management Information System (DMIS) Mozambique Aid levels for disaster relief funding can be released within days, in advance of on-site damage assessment. Workflows Wizard Wizard picks appropriate workflow for desired result Estimated rainfall accumulation and flood prediction model Baseline water level, flood waters and predicted flooding Flood Model
Emergency Routing in AIP-3 Route updated as flood expands and blocks roads Contact: Lan-Kun Chung, GIS FCU
EuroGEOSS in GEOSS AIP – Habitat calculation with WPS Contact: Stefano Nativi
GEOSS AIP Phase 4 (AIP-4) Activity #1: Access to Priority EO Data Sources 1a. Thesaurus for EO Observation Parameters 1b. "EO Priority Data Sources” list 1c. Getting EO Data Online Activity #2: Clients and Mediated Access Enablers 2a. Coordination with GCI 2b. Coordination of Enabler Components 2c. Integration and Usability Testing of Enablers Components AIP-4 CFP responses requested by 6 May 2011 http://www.earthobservations.org/geoss_call_aip.shtml
Implementing GEOSS architecture with-and-for Users • GEOSS bold vision endorsed 5 years ago • Architecture vision now realized for several societal applications • Get involved: GEOSS ADC, SIF, AIP, CoPs www.ogcnetwork.net/geoss/aip-3/
References • GEO • earthobservations.org • GEO Architecture Implementation Pilot • www.ogcnetwork.net/AIpilot • GEOSS registries and SIF • geossregistries.info George Percivall firstname.lastname@example.org