AR-07-01 Status Report

Doug Nebert

U.S. Geological Survey

Task POC

AR-07-01 Status

• Subtasks:– Registries deployment– Strategic and Tactical Guidance documents– Standards and Interoperability Forum (SIF)– IP3 subtask

AR-07-01: Registries

• Define and deploy GEOSS Registries– Component and Service Registry: operational– Standards and Special Arrangements Registry: operational– Online capabilities referenced in Tactical Guidance, as of

May 2008, Tactical Guidance document is still not visible on the GEO Website

– Connection points between Requirements Registry and other Registries being identified (Feb 2008)

• User Requirements Registry prototype online for testing by UIC, published draft May 2008

• Best Practices Wiki, online April 2008

IOC and review of component registry

• Per Task plan:– May 2007: IOC online, completed June 2007– September 2007: Review and refinement

(September 2007, Continued updating, maintenance contract in place with Registry developers)

– January 2008: Redundant hosting of Component and Service Registry, completed May 2008

– January 2008: Integration with the Standards and Interoperability Registry, to be completed late May-June 2008

GEOSSComponents

GEOSSStandards

GEOSS Special Arrangements

expose

maybecome

nominate

GEO Members and

ParticipatingOrganizations

offer

U.S.A. IEEE

UDDI ebRSOGCCSW

Z39.50/SRU Web UIWeb UI

SIFExternal

StandardsBodies

Subject Matter

Experts

JAXRZ39.50/

SRU

GEOSS Componentand Service

Registry

GEOSSServices

GEOSS Standards Registry

Registries Interaction

reference

GEOSSStandards & Special

Arrangements Registry

Users

GEOSS CommonInfrastructure

GEONETCast

GEO Main Web Site

GEOSS Common Infrastructure

GEOSSComponent Registry

Service Registry

GEOSSClearinghouse

GEOSSClearinghouse

GEOSSClearinghouse

GEO Web PortalGEO Web PortalGEO Web Portal

Requirements Registry

Best Practices Wiki

External Resources

Catalogue

ServicesWebsites/Web

portals

Documents

RSS

GEOSS Registered Components

Catalogue

ServicesWebsites/Web

portals

Documents

RSS

references

linksaccess

accesses

searches

links

Accesses all RegisteredCommunity Resources

Links to OtherCommunity Resources

External Resources Access Clearinghouse

All Common Components support external search and retrieval interfaces

searches

cd Data Model

Objects

*PK «column» object: CHAR(10)* «column» description: VARCHAR(50) «column» reference: VARCHAR(50) «column» type: VARCHAR(10) «column» units: VARCHAR(50)

+ «PK» PK_Properties(CHAR)

UserTypes

*PK «column» usertype: CHAR(10) «column» description: VARCHAR(50) «column» class: VARCHAR(50)

+ «PK» PK_UserTypes(CHAR)

Applications

*PK «column» application: CHAR(10) «column» field: VARCHAR(50) «column» benefit: VARCHAR(50) «column» description: VARCHAR(50)

+ «PK» PK_Applications(CHAR)

Requirements

*PK «column» number: INTEGER* «column» description: VARCHAR(50) «column» type: CHAR(10) «column» quality: VARCHAR(10) FK «column» object: CHAR(10) «column» spat_res: REAL «column» temp_res: REAL «column» rel_acc: REAL «column» abs_acc: REAL «column» time_acc: REAL «column» latency: REAL «column» length: REAL «column» ref_frame: CHAR(10) «column» repro: CHAR(10)

+ «FK» FK_Requirements_Properties(CHAR)+ «PK» PK_Requirements(INTEGER)

LinkAU

FK «column» application: CHAR(10) FK «column» usertype: CHAR(10)* «column» description: VARCHAR(50) «column» type: CHAR(10)

+ «FK» FK_LinkAU_Applications(CHAR)+ «FK» FK_LinkAU_UserTypes(CHAR)

LinkRA

FK «column» req_number: INTEGER FK «column» application: CHAR(10)* «column» description: VARCHAR(50) «column» type: CHAR(10)

+ «FK» FK_LinkRA_Applications(CHAR)+ «FK» FK_LinkRA_Requirements(INTEGER)

Specifications

*PK «column» specification: CHAR(10) FK «column» product: CHAR(10) FK «column» req_number: INTEGER «column» description: VARCHAR(50) «column» level: CHAR(10)

+ «FK» FK_Specifications_Products(CHAR)+ «FK» FK_Specifications_Requirements(INTEGER)+ «PK» PK_Specifications(CHAR)

Observ ations

*PK «column» observation: CHAR(10) FK «column» technique: CHAR(10) FK «column» object: CHAR(10) «column» description: VARCHAR(50) «column» units: CHAR(10) «column» spat_res: REAL «column» temp_res: REAL «column» rel_acc: REAL «column» abs_acc: REAL «column» time_acc: REAL «column» latency: REAL «column» length: REAL «column» ref_frame: CHAR(10) «column» repro: CHAR(10)

+ «FK» FK_Observations_Objects(CHAR)+ «FK» FK_Observations_Techniques(CHAR)+ «PK» PK_Observations(CHAR)

Techniques

*PK «column» technique: CHAR(10) «column» output: VARCHAR(50) «column» reference: VARCHAR(50) «column» status: CHAR(10)

+ «PK» PK_Techniques(CHAR)

LinkPO

FK «column» product: CHAR(10) FK «column» observation: CHAR(10) «column» description: VARCHAR(50) «column» type: VARCHAR(10)

+ «FK» FK_LinkPO_Observations(CHAR)+ «FK» FK_LinkPO_Products(CHAR)

Products

*PK «column» product: CHAR(10) «column» description: VARCHAR(50) FK «column» object: CHAR(10) «column» type: CHAR(10) «column» units: CHAR(10) «column» spat_res: REAL «column» temp_res: REAL «column» rel_acc: REAL «column» abs_acc: REAL «column» time_acc: REAL «column» latency: REAL «column» length: REAL «column» ref_frame: CHAR(10) «column» repro: CHAR(10)

+ «FK» FK_Products_Objects(CHAR)+ «PK» PK_Products(CHAR)

0..*+FK_Specifications_Products

«FK»

(product = product)

1+PK_Products

«FK»

(object = object)

«FK»

(technique = technique)

«FK»

(observation = observation)

«FK»

(product = product)

«FK»

(object = object)

«FK»

(req_number = number)

«FK»

(req_number = number)

«FK»

(application = application)

«FK»

(application = application)

«FK»

(usertype = usertype)

«FK»

(object = object)

User Requirements Registry

• Need to formalize UIC commitment for the operation and interaction with the registry – significant governance issue

• Web-form upload by privileged individuals anticipated• Batch upload from existing requirements systems also

anticipated• Architectural tie-points exist between the “observations”

(observable parameters) and the Services and Standards Registries

• Continued web services and database support to be offered by this Task to UIC during IOC

AR-07-01: ADC Standards and Interoperability Forum Status Report

ADC Co-Chair Meeting 19 May 2008

Siri-Jodha Singh Khalsa

Recent Meetings

• Regular meetings by WebEx, approx. every 2 weeks in 2008– Jan 10th (12 participants)– Jan 24th (7 participants)– Feb 19th (9 participants)– March 6th (10 participants)– March 20th (8 participants)– April 4th, (11 participants)– April 17th (10 participants)– May 9th (10 participants)

• In addition, 2 special meetings with NASA ECHO representative M. Burnett– to discuss ECHO entries in the service and standard

registries

Focus of Activities

• Correcting and evaluating entries for standard and special arrangement (SA)

• Process for promotion of SA to GEOSS-registered standard• SIF task workflow process

– how SIF tasks get assigned, worked, approved, tracked, and made publicly available

– SA entry will automatically create SIF task• Establishing Subject Matter Expert (SME) database• Oral presentation at ISPRS Beijing by Zhang

– Paper at: http://cires.colorado.edu/~khalsa/SIF_ISPRS_Beijing.htm

Formation of Regional Teams

• European team has a funded initiative, GIGAS, to contribute to GEOSS– Question of whether it will participate in routine

SIF work• Japanese team?• Patricia Alvarez is forming the South American team• Participants in N. America team have been identified• Someone to head an Indian regional team?• African participants team-up with the European team

for the moment, until their membership gets going

SIF Future Plans

• Monitoring of new entries into Components & Services Registry– Not a SIF responsibility– Who will check whether declared standards and

SAs are used as stated?• Survey of all existing and proposed GEO Tasks for

issues related to standards• SIF workflow management system • Interaction with Best Practices Registry• Meeting RT leads

AR-07-01: The Interoperability Process Pilot Projects (IP3)

Stefano Nativinativi@imaa.cnr.it

GEO Architecture & Data Committee23 May 2008

Content

• Origins and goals• 2007 accomplishments• 2008 activities & evolution of IP3 framework• The Model Web• Schedule• Summary & Conclusions

EGU GA 4/08 # 16

Origins and Goals of the IP3

• In 2006 the GEO Architecture and Data Committee produced a document outlining the “Process for reaching interoperability arrangements”

• The “Interoperability Process Pilot Project” (IP3) was conceived as a way to begin implementing the GEOSS infrastructure and testing the GEOSS interoperability process

• A series of projects involving several initially identified GEOSS components was initiated, with the aim of producing a suite of demonstrations for the GEO Summit in November.

Sources

• The ADC identified four areas as sources for the pilot projects.

• This selection was based on– the desire to involve diverse disciplines– commitments of representatives from the

disciplines to actively support the process• Recommendations for additional communities to

participate are welcome

Interoperability Process Pilot Project (IP3) Status

• Report on 2007 IP3 activities now available• Plan for IP3-2008 submitted as Position Paper to

Architecture Workshop under Biodiversity area– But will involve other disciplines as well

EGU GA 4/08 # 19

The Challenge

• Utilization of earth observation data for cross-disciplinary basic and applied research requires infrastructure that supports diverse data sources

• The key to GEOSS’ utility and effectiveness is the implementation of interoperability process for integrating data and information systems

• Interoperability must be addressed not only through conceptual solutions but through prototypes and demonstration of functionality

EGU GA 4/08 # 20

FDSN

Exotic event catalog

Surface melt, ice velocity

Seismic Trigger

Precip, soil moisture (TIGGE)

IPCC model data (NCAR)

Species data

Precip (TIGGE), Land Use

2007 IP3 Scenarios and Data Flows

CEOP centers

Seismic Events from Ice Sheet Disintegration

Scenario

Landslide Risk Scenario

Meningitis Early Warning System

Seismic Events from Ice Sheet Disintegration

Scenario

Species Response to

Climate Change ScenarioGBIF

WHO

NSIDC

WISWGISS Test Facility

EGU GA 4/08 # 21

Evolution of IP3 Framework

• We will develop additional multi-disciplinary use cases where

1. Users interact with a Geo-portal to submit queries

2. Query is passed to Catalog service able to distribute the query against the following standard resource types:• International Standard (OGC CS-W, WMS, WCS)• Community Standards (THREDDS/OPeNDAP, GBIF,

MerSea SeaDataNet CDI)

3. The discovered and downloaded datasets are ingested into a model server

4. The model server generates output which is served through a standard resource server (becoming searchable)

Dataset resource Provider

… .

… .

OGC Access Standards

THREDDS/OPeNDAPArrangements

CSW/ebRIM.

CIM

Catalog server(GI-cat)

Dis

trib

uti

on

Mediation

Services:- Distribution˗ Message Mangmnt;˗ Messaging;˗ Persistence˗Mediation

.. .

Other InternationalStandards

GEO Portal

users

11

22

33

4a4a

ProcessingComponent

Discipline….

ModelServer

. ...

Discipline….

ModelServer

OtherDiscipline

ModelServers

ClimateChange ModelServer

ClimateChange ModelServer

ENMServerENM

Server

Model Resource Provider

ProcessingComponentworkflow

Component

4b4b

workflowComponent

GEOSS Components

GEOSS Components

GEOSS Components

GEOSS Components

CSW/ISO

CS-W Appl. Profiles

GBIF Arrangements

Other specific Arrangements

GEOSS Components

GEOSS Components

The Multidisciplinary Interoperability Process• Registering a new disciplinary component:

1. Resource provider registers component which instantiates well-known services (standard / best practice)

2. The infrastructure catalog component discovers the new service instance and associates specific mediation and access capabilities with it

3. The infrastructure catalog register is updated adding the new registered resource and the new mediation functionalities -where needed

Service Registry

Interoperability Process

International Standard / Special Interoperability Arrangement Registry

Distributed catalog

Earth System Science

Community

PROCESSPROCESS

11 22 33

EGU GA 4/08 # 25

Model Interoperability

• Simulation models are generally built in isolation and do not easily interoperate with others

• Result: lost opportunities to address important questions • Barriers to interoperability are both technical and cultural • For IP3 we will develop and register model

interoperability arrangements along with specific mediation solutions and possibly recommendations for new standards.

April 2008

The Model Web initiative

or

or

• Improve existing models

• Create new models

• Increase model interoperability

Model Web

Model A

Model B

Model CDataset 1

Dataset 2

Model D

Model E

Model F

Dataset 3

Dataset 4

Model G

Gary GellerNASA JPL California Institute of Technology

• Distributed network of interoperating models (and datasets and sensors)

• Using Service-Oriented Architecture

• Data format and terminology issues resolved

• Multi-disciplinary scope

• Grows organically within framework of broad goals and data exchange standards

• Models and datasets maintained, operated, and served independently

• Web access provided to researchers, managers, public…

Model Web: 5-10+ Year Vision

CC and Species Distribution

Global ClimateModel

RegionalClimate Model

FireModel

LandscapeModel

Species distribution

As the climate changes, can rare species Xstill exist within my park in 2057?

TOPS

Species Distribution Model

Human Health

Global ClimateModel

RegionalClimate Model

InfectionRate Model

Human Population Density and Distribution Model

Vector NicheModel

Infection Rates

How will CC affect infection rateof dengue fever in Vietnam?

SocioeconomicFossil Fuel UseModel

Deforestation/Disturbance Model

Observational Data(environment &vector distribution)

Schedule

• July 2008 - Initial prototype

• September 2008 – Report to ADC

• November 2008 – Demonstration to GEO Plenary

Successes

• Component registration forms completed for FDSN, CEOP, WIS• In addition to WIS, forms also completed for these subsystems:

– World Weather Watch Global Observing System - GOS– Global Atmosphere Watch - GAW– World Hydrological Cycle Observing System - WHYCOS– World Climate Programme - WCP– Global Climate Observing System - GCOS– Global Ocean Observing System - GOOS– Global Terrestrial Observing System - GTOS

Other Successes

• Document Successful Data Integration Projects– CEOP presentation to follow

• GEOSS Standards Register created– Web query form functional– ISO 29350 interface shortly

• Also pending– Collection of service information from the

candidate systems awaits availability of prototype service registry.

Meeting, Presentation, Workshop

• At the European Geosciences Union (EGU) General Assembly 2007 Vienna, Austria– IP3 Meeting: Monday, 15 April 2007, 10:30 – 12:00, Room

SM4– IP3 Paper: Session US10, Thursday, 19 April 2007, 11:30,

Lecture Room 29 on• At the International Symposium on Geosciences and Remote

Sensing (IGARSS) 2007 Barcelona, Spain– GEOSS Workshop: Sunday 22 July 2007, 08:30 – 18:30– The User and the GEOSS Architecture XIV, Topic: GEOSS

Interoperability and Applications to Biodiversity

Meeting, Presentation, Workshop

• At the American Geophysics Union (AGU) Fall Meeting, 2007 San Francisco, USA

– Processes for Achieving Interoperability in GEOSS, Thursday 13 December 2007, 13:30 – 15:30

• At the European Geosciences Union (EGU) General Assembly 2008 Vienna, Austria

– IP3 Paper: Session ESSI10, Wednesday, 17 April 2008, 14:00 - 18:00

• The manuscript “Predicting the Impact of Climate Change on Biodiversity – a GEOSS scenario” was published on the Full Picture book (GEO editor)

• The manuscript “The GEOSS Interoperability Process Pilot Project (IP3)” was submitted to IEEE TGRS

Summary & Conclusions

• The Interoperability Process Pilot Projects are performing a vital function in GEOSS development by exercising the core GEOSS components and processes

• Possible only through the efforts of individuals contributing their time and expertise to the process.

• Input and participation from other GEO committees invited• Innovative information technologies are required to fully realize

potential of contributions to GEOSS• The IP3 is demonstrating the benefits of engaging diverse

disciplinary communities in the building of infrastructure to support interoperability

GI-Cat

Discovery&Query

getC ontentgetM etadataquery

1

Messaging

publishsubscribeunsubscribe

Session

com m itin itlogin

Distribution

addrem ove

Persistency

purgestore

Mediation&Access

getM appingsetM apping

logoutrollback

0..1 0..1 0..1 0..1 0..1

• Extended model for Distributed Catalog service (federated architecture)

– Extended functionalities

Extended General Model for distribution & mediation

Stateful behaviorTransaction

Asynchronous interaction

Caching Federation of new service instances

Mappingheterogeneous service modesl to the federation one

Distributed Catalog Service

GI-Cat

Discovery & Query

getC ontentgetM etadataquery

1

Messaging

publishsubscribeunsubscribe

Session

com m itin itlogin

Distribution

addrem ove

Persistency

purgestore

Mediation & Access

getM appingsetM apping

logoutrollback

0..1 0..1 0..1 0..1 0..1

Distributed Catalog Service

CSW/ISOserver

CSW/ISOserver

CSW/ebRIMFGDC serverCSW/ebRIMFGDC server

CSW/ebRIMCIM server

CSW/ebRIMCIM server

THREDDSserver

THREDDSserver

WMSserverWMS

serverGBIF

serverGBIF

serverWCS

serverWCS

server

Resource Access

CDI catalogserver

CDI catalogserver

WMS Access WCS AccessCSW/ebRIM Access CSW/ISO Access THREDDS Access GBIF Access CDI Access