GEOSS Architecture Status and Way-forward Unofficial presentation Just for brain Storming GEO Secretariat CEOS/WGISS, May 24 2007, Hanoi.

GEOSS ArchitectureStatus and Way-forward

Unofficial presentationJust for brain Storming

GEO SecretariatCEOS/WGISS, May 24 2007, Hanoi

GEO Status• Membership

– 69 Member Countries and European Commission– 46 Participating Organizations

• Concentrate the activities to Ministerial Summit in Nov. 30 in Cape Town, South Africa– Preparatory Task Forces have formed for Declaration, Report on

Progress, Communication and Logistics– Demonstration (e.g., Video), Exhibitions

• Near term schedule for Summit– Report on Progress Task Force meeting: June 4-5– GEO Committee Co-Chairs meeting: June 6– Communication Task Force meeting: June13– GEO Executive committee: July 3-4– One more iteration would be happened in September (Task

Force, Executive committee)– GEO Executive committee: Nov 27– GEO Plenary: Nov 28-29– Ministerial Summit: Nov 30

ADC meeting• ADC-V Sept. 12-13, Washington DC area,

US, chaired by I. Deloatch/USGS – with one or half day workshop of GEOSS data

policy workshop organized by ICSU/CODATA

• ADC-VI early Feb. 2008, Europe, Ispra, chaired by A. Annoni/EC

• ADC-VII May-early June 2008, Asia, chaired by R. Shibasaki/Japan

• ADC-VIII September 2008, America, chaired by J. Pearlman/IEEE

Model/Integration

GEO Web Portal

GEOSS Clearinghouse

GEONETCast

Uplink Center

Data CenterInformation system

...

Satellite Obs Systems In-Situ Obs Systems Airborne Obs SystemsCEOS CGMS GOS

Others

Argo HARON FluxTower

FDSN Others

Various

Data CenterInformation system

Data CenterInformation system

Users of 9SBAs

Data Archives

GEO Information System

Data Management

Data Access and Dissemination

GEOSS Technical Architecture (Not Official)

Model/Integration

Commercial

Two Core Architecture Tasks• AR-07-01 (Enabling Deployment of a GEOSS Architecture)• AR-07-02 (GEOSS Architecture Implementation Pilot)

System of Systems Activities

Strategic and Tactical Guidance Documents

Process for InteroperabilityArrangement

Component RegistrationProcess

Interoperability Process Pilot Projects (IPPP)

Component Linking Guideline

GEOSS Requirements

- 10YIP- CoP

GEO M&POs

Guidelines and Processes

Input

Refer/Register

AR-07-01 activities

Utilize as test cases

AR-07-02 GEO Web Portal, GEOSS Clearinghouse and Services

Participate

Access IPPP data ??

Participate

Japan

IEEE ADC

IEEE

IEEE

OGC

ADCSpatial Data Infrastructure

GSDI

Standard InteroperabilityForum IEEE

Apply Componentregistration

Registries

titledescriptionstandardTypecontactstatus

titledescriptionstandardTypecontactstatus

Special Arrangements

titledescriptionstandardsOrgstandardTypeURNstatus

titledescriptionstandardsOrgstandardTypeURNstatus

Standards

componentAbbrevcomponentContactcomponentCategorydescriptiononLineReferenceSBAstatus

componentAbbrevcomponentContactcomponentCategorydescriptiononLineReferenceSBAstatus

Component

serviceAbbrevserviceInfo (URL)latLongBoxtimePeriodagreementimplementationRef

serviceAbbrevserviceInfo (URL)latLongBoxtimePeriodagreementimplementationRef

ServiceInstanceIdentifiertitlecontactonlineRef

IdentifiertitlecontactonlineRef

GEOmembersPO

implementationReference

Memberoffers

May have service

(Partial Attribute Listing)

InteroperabilityArrangement

InteroperabilityArrangement

0..*

0..*

0..*

Hosted by IEEEHosted by GEOSec

Hosted by GMU (Temporary: 6-12months)

IPPP components and scenarios

WIS

GBIF

FDSN

CEOP

Species Response to Climate Change

ScenarioNativi

Fault Lubrication Scenario

Ahern

Landslide Risk Scenario

Thomas

Flood Risk Scenario

Burford

Seismic Events from Glacier/Ice

Sheet Disintegration

ScenarioAhern

Exotic event catalog

Terminus retreat

GLIMS

Event catalog

Precip (NCAR/TIGGE), stream gauge (CUAHSI /USGS)

Seismic Trigger

Precip, soil moisture (TIGGE)

Climate data (NCAR)

Species data

DEM (DEMIS)

Ancillary

Meningitis Early Warning System

Kelly

Precip, soil moisture (TIGGE)

Soil moisture, stream gage, etc.

Architecture Implementation Pilot (CFP)

• Pilot for GEO Web Portal, GEOSS Clearinghouse and Services

The proposed idea of GEO Web Portal by Secretariat

DisasterHealthEnergyClimateWater

WeatherEcosystemAgricultureBiodiversity

Direct AccessTo

Data & Services

CapacityBuilding

GEONETCast

AboutGEO

Search by location

Search by theme

A Portal to DATA and SERVICES

Current Status of GEOSS Architecture

• GEOSS Processes have been established– component registration process, process for reaching

GEOSS interoperability, component linking guideline– Strategic and Tactical guidance documents would be

essential but still in drafting

• Requirement driven ?– Engineering view point Focus on the process– Where is the requirement?

• 10 Year Implementation Plan + Reference Document • UIC Community of Practice, = subset of 10YIP, Reference

Document?

– Tactical guidance + Roadmap should be established based on the requirement

– Test cases and scenarios would be useful

GEOSS IP Targets - Water2006-2007 2008-2011 2012-2015

In-situ observation

Integration

Product

Model

User IF

Improve existing in-situ sys

Test global net of integrated in-situ sites

Test a fully integrated prototype data system with assimilation,

analysis & visualisation

Make integrated in-situ obs site operational

Operational integrated data system

Space-based observation

Study capabilities for:- surface water quality- streamflow and water storage (altimeters)

Integrated info on climate indices/ extreme events

Implementation plan for data integration system

Plan integrated in-situ network

3 hourly global precipitation

Integrated precip. and soil moisture products

(IGOS-P)

Int’l coord. mechanisms

GPM & Missions for surface & subsurface water stores

Plan water quality monitoring

System for monitoring WC changes

Data and info on water quantity and quality

to protoype expert decision support sys

Collaborative mechanism between obs and research community

Framework for ensemble hydro prediction

Gravity mission for ground water stores

New products for precipitation, soil moisture, evaporation and

evapotranspiration

Integrated water cycle data sets

Water level data collection sys

Planning Prototyping Operational

Routine watershed health indicators

How to look the real world? - Monitor by using the GEOSS Roadmap -

Global/Regional/National, Programs dimension

• Global: example components are WIS, FDSN, GBIF, Argo

• Regional: example components are HMA, Sentinel Asia

• National: many…• Enhanced Observing Programs: CEOP, IPY, …

• We may need to classify these components one by one?

How to look the real world?• How each organization to cover the GEOSS Architecture.• For example, “CEOS” world as one of Participating Organizations

Satellite Observing Systems

Data Archive

Data Center/Information System

Web Portal/Clearinghouse

NASA ESA JAXA USGS CNES NOAA etc

CEOS/WGISS CEOS/WGCV

CEOS/SIT

Capacity BuildingBy CEOS/WGEdu

GEONETCast/Uplink Center

EUMETSATESA

In-situ Network

How to look the real world?• How each organization to cover the GEOSS Architecture.• For example, EEA and UNEP, as a Participating Organization for In-situ network.

Satellite Observing Systems

Data Archive

Data Center/Information System

Web Portal/Clearinghouse

Capacity BuildingBy EEA, UNEP

GEONETCast/Uplink Center

EEA, UNEP

In-situ Network

How to look the real world?• How each organization to cover the GEOSS Architecture.• For example, EC, as a Member.

Satellite Observing Systems

Data Archive

Data Center/Information System

Web Portal/Clearinghouse

Capacity BuildingBy FP

GEONETCast/Uplink Center

GMES, FP

In-situ Network

How to look the real world?• How each organization to cover the GEOSS Architecture.• For example, China, as a Member.

Satellite Observing Systems

Data Archive

Data Center/Information System

Web Portal/Clearinghouse

Capacity BuildingBy National Program?

GEONETCast/Uplink Center

Way-forward• Near term: for the Ministerial Summit in November

– GEO Web Portal and GEOSS Clearinghouse– Interoperable Information Systems

• Registration process should start soon• What to show? Registries? + Use Cases? (discussed in ADC)• How to show? Through GEO Web Portal? (discussed in Outreach

team)

• Long term: – Establish and refine the Strategic and Tactical Guidance

documents– Refine the processes (component registration, etc)– Establish the sustainability of the Registry operation by the GEO

Secretariat and monitoring the status– System of Systems approach would be needed– Currently Architecture has only two years targets. It would be

necessary the 6 and 10 years targets.