GEOSS Architecture Implementation Pilot
Water Information Services with
GEOSS Interoperability
Arrangements
George Percivall
Open Geospatial Consortium
Task lead AR-09-01B
April 2011 ISRSE Sydney
A process, elaboration of GEOSS Architecture
SBA Tasks,
UIC, CBC,
STC
requirements
User
Needs,
Scenarios
Design,
Develop,
Deploy
support
ADC activities
including:
Architecture
Implementation
Pilot (AIP)
Task AR-09-01b
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-01b
Architecture Implementation Pilot
• Support SBAs by developing new process
and infrastructure components for GCI and
the broader GEOSS architecture
• Demonstrate and document results to inform
GEOSS Development Baseline progress
“fostering interoperability arrangements
and common practices for GEOSS”
AIP-3 Results - February 2011
• SBAs Areas
– Energy
– Disaster Management
– E-Habitat
– Arctic SDI
– Air Quality
– Water - Drought
Global Drought Monitor Portal
EDO Drought Index
• Informatics Areas
– Engineering Use
Cases
– Data Harmonization
– Data Sharing
– Semantics
Water Ontology
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
GEOSS Common
Infrastructure
Main GEO
Web Site
Registered Community Resources
Client Tier
Registries
GEO
Web Portal
Community
Portals
Client
Applications
Components
& Services
Standards and
Interoperability
Best Practices
Wiki
Mediation Tier
GEOSS
Clearinghouse
User
Requirements
Community
Catalogues
Search
Brokers
Alert
Servers
Workflow
Management
Processing
Servers
Test
Facility
Access Tier
GEONETCast
Long Term
Archives
Access
Brokers
Sensor
Web
Model
Web
AIP Use Cases
Drought Scenario and Use Cases (simplified)
Step Description
1
2
Use Case
1. Register Resources
Obtain Drought Indices
4. Search for Resources
Process drought index and calculate 6. Interact with Services (WCS)
11. Execute Processing Service (WPS)
drought hazard
3
Get Drought Hazard Related Information 13. Conduct semantic search
5. Present Services and Alerts
Discovery using Ontology
6. Interact with Services
4
Visualization and Assessment of drought 5. Present Services and Alerts
hazard information datasets, combining 7. Exploit Data Visually and Analytically
them with the potential hazard layer
5
Decision maker assesses drought hazard
impact
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 GEOSS
GEO 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 broker
Arabian search string
"‫“( "مناخ‬climate”) is
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 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
Supporting 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 Percivall
percivall@myogc.org