geoss architecture implementation pilot water information services with geoss interoperability...

GEOSS Architecture Implementation Pilot

Water Information Services with GEOSS Interoperability Arrangements

George PercivallOpen Geospatial Consortium

Task lead AR-09-01B

April 2011 ISRSE Sydney

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-01bArchitecture Implementation Pilot

“fostering interoperability arrangements and common practices for GEOSS”

Water Ontology

Global Drought Monitor Portal

EDO Drought Index

AIP-3 Results - February 2011

• Informatics Areas– Engineering Use

Cases– Data Harmonization– Data Sharing

– Semantics

• SBAs Areas– Energy– Disaster Management– E-Habitat– Arctic SDI– Air Quality

– Water - Drought

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

Drought Scenario and Use Cases (simplified)

Reference: “Global Drought Monitoring Service through the GEOSS Architecture”, Drought and Water Working Group, Engineering Report, GEO AIP-3, February 2011

European Drought Observatory use of EuroGEOSS

Contact: Stefano Nativi

Semantics applied to Water in GEOSSGEO Tasks: Semantics, DIAS, AIP

• Ontology Engineering• Integration of independent thesauri that are sharing

the same data format, SKOS • Integrate more general ontologies created with

primitives in schema languages (e.g. SWEET)• AIP-3 development of an ontology of water-related

terms, based on CUAHSI ontology – using the CMap2 visual tool. – OWL ontology for grounding broker's search

Land Surface Module of the Water Ontology

Semantic Enabled Search Use Case

• GI-DAC broker implemented Semantic Search UC– Leverages GENESIS vocabulary service for

generating multiple, multilingual queries to be issued to remote catalogs.

• Multi-lingual searching: Language-dependent search patterns against language-neutral URIs.

• “Advanced search” allows user to navigate thesauri, define a set of terms and queries to catalogs.

Architecture for semantic augmentation

Advanced search with the GI-DAC brokerArabian search string is (”climate“) "مناخ"found in the definitions of six terms from GEMET.

DIAS Ontology Browser in GEO URR prototype

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 2011Supporting ADC “Sprint to Plenary”

http://www.earthobservations.org/geoss_call_aip.shtml

Water Information Services with GEOSS Interoperability Arrangements

• 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