Implementing GEOSS architecture with-and-for Users

George PercivallOpen Geospatial Consortium

Task lead AR-09-01B

OperationalCapability

OperationalCapability

UserNeeds,

Scenarios

UserNeeds,

Scenarios

Design, Develop,Deploy

Design, Develop,Deploy

ADC activities including:

ArchitectureImplementation

Pilot (AIP)Task AR-09-01b

GEOSS CommonInfrastructure (GCI)Task AR-09-01a

support

persistentimplementation

requirements

SBA Tasks,UIC, CBC, STC

A process, elaboration of GEOSS Architecture

GEOSS Interoperability ArrangementsGEOSS Interoperability Arrangements- From the GEOSS 10 Year Plan Reference Document - - 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-01b

Architecture Implementation Pilot

“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

GEOSSClearinghouse

GEO Web Portal

GEOSS Common Infrastructure

Components & Services

Standards andInteroperability

Best PracticesWiki

User Requirements

Registries

Main GEOWeb Site Registered Community Resources

Community Portals

Client Applications

Client Tier

Mediation Tier

CommunityCatalogues

AlertServers

WorkflowManagement

ProcessingServers

Test Facility

SearchBrokers

Access Tier

GEONETCastAccess Brokers

Sensor Web

ModelWeb

Long Term Archives

Components Interact thru Services

AIP Use Cases

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

12

Flood Tasking and Product Generation in AIP-2

Aid levels for disaster relief funding can be released within days, in advance of on-site damage assessment.

From portal select desired theme(s) and area of interest

Wizard picks appropriate workflow for desired result

Wizard

Mozambique

Disaster Management Information System (DMIS)

Workflows

Estimated rainfall accumulation and flood prediction model

Flood Model

Selected workflow automatically activates needed assets and models

Baseline water level, flood waters and predicted flooding

Emergency Routing in AIP-3

14Contact: Lan-Kun Chung, GIS FCU

Route updated as flood expands and blocks roads

EuroGEOSS in GEOSS AIP – Habitat calculation with WPS

Contact: Stefano Nativi

Air Quality in AIP-3Visualizing uncertainty in AQ information

AIP Coordination with SBAs and CoPs.

GEOSS AIP Phase 4 (AIP-4)

Activity #1:  Access to Priority EO Data Sources1a. Thesaurus for EO Observation Parameters

1b. "EO Priority Data Sources” list

1c. Getting EO Data Online

Activity #2:  Clients and Mediated Access Enablers2a. Coordination with GCI

2b. Coordination of Enabler Components

2c. Integration and Usability Testing of Enablers Components

AIP-4 CFP responses requested by 6 May 2011http://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 Percivallpercivall@myogc.org