geoss common infrastructure (gci) & gci-coordination team (gci-ct) ivan petiteville, gci-ct...

16
GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do Jordão, Brazil 28 Feb. 2011 – 3 Mar. 2011

Upload: amanda-harrison

Post on 17-Jan-2016

223 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

GEOSS Common Infrastructure (GCI)& GCI-Coordination Team (GCI-CT)

Ivan Petiteville, GCI-CT Co-chair

GEO Architecture & Data Committee meetingCampos do Jordão, Brazil28 Feb. 2011 – 3 Mar. 2011

Page 2: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

GEOSS Common Infrastructure (GCI)

Page 3: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

GEO Contributors of GCI Components

• GEO Web Portal:

– European Space Agency (ESA) / UN Food and Agriculture Organisation (FAO)

• GEOSS Clearinghouse:

– US Geological Survey (USGS)• Component & Service Registry:

– US Geological Survey (USGS)• Standards & Interoperability Registry:

– Institute of Electrical and Electronics Engineers (IEEE)• Best Practices Registry:

– Institute of Electrical and Electronics Engineers (IEEE)• User Requirements Registry:

– U.S. Environmental Protection Agency (US EPA)

Page 4: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

GCI Status & Current Activities

• Recommendations for Clearinghouse & GEO Web Portal selection approved by ExCom (Jul. 2010)

• GCI operated with relatively low number of visitors (~18,000 visitors per month)– Geospatial information not always easy to find (GWP, CL and

CSR). Problems regularly encountered by users from GCI-CT, GEO SEC, GEO Web Portal team

– Not acceptable. Urgent actions are needed.

• Suggestions for improvement already received and some are being discussed with some GCI Providers but need for better organisation to ensure proper coordinated operations and enhancements

Traffic Rank (from Alexa)*          1 google.com [Google]        879 weather.gov [U.S. National Weather Service]       2,750 usgs.gov [United States Geological Survey]       3,257 ieee.org [Institute of Electrical and Electronics Engineers]      20,114 esa.int [European Space Agency]      73,655 wmo.ch [World Meteorological Organization]    281,664 opengeospatial.org [Open Geospatial Consortium]    307,994 gbif.org [Global Biodiversity Information Facility]     354,497 ciesin.org [Center for International Earth Science Info. Network]     980,752 geodata.gov [Geospatial One-stop]  1,672,258 earthobservations.org [GEO Web site]   1,903,683 geoportal.org [GEO Portal]

** Alexa Traffic Rank is calculated using a combination of average daily visitors and pageviews over the past 3 months.

Page 5: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Future GCI Operations

Routine operations tasks by GCI Component Providers* are being organized:– GCI-component application software and hardware

platform monitoring, maintenance and administrative tasks

– Problem correction– Reporting

*: CSR, SIR, BPW, CL and GWP

Page 6: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Future GCI Enhancements

• Suggestions for improvements coming from multiple sources:– Data Sharing Task Force, GEO Task Teams, GEOSS

Contributors, GEO User Community, GEO Committees, AIP, etc …

• Assessment of suggestions: need, urgency, resources needed for implementation, etc ..

• Relevant GCI Providers shall work in a coordinated manner for implementation before transfer to operations

Page 7: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Operations and Enhancement Process

• “GCI Operations & Enhancements” document under preparation.

– aim at defining the necessary organisation and process to be put in place

– still divergences between GCI-CT members on the organisation:

• managed by AR-09-01a Task Team• managed by GCI-CT• managed by dedicated team • other ?

Page 8: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Who should be involved ?

• At least the following entities shall be involved in the GCI operations and enhancements process:

– Representatives from the GEO User Community– GCI Providers– Relevant GEOSS Contributors whenever needed– Experts with experience in operations and

management of complex systems

Page 9: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

GEOSS Common Infrastructure Coordination Team

(GCI-CT)

Page 10: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

GCI-CT Membership: Co-Chairs

Transitional Co-Chairs (from the IOC-TF to the GCI-CT),• Eliot Christian (WMO)• Ivan DeLoatch (USGS)• Ivan Petiteville (CEOS)

Page 11: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

GCI-CT Membership: Members

Page 12: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Current GCI-CT Activities

After having organized and concluded successfully the selection process (Summer 2010) on-going discussions on:

–Promotion of open source–Impact of data sharing action plan–High level discussions on some potential improvements of GCI

Page 13: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Issues still to be addressed by GCI-CT

• Formulation of recommendations for Reserve Fund– A special fund associated with the GCI. – GCI-CT needs to further explore the following issues:

• GCI special needs that cannot be covered by the selected GCI component providers ?

• Legal, policy, and existing GEO agreements that constrain the creation and administration of a GCI fund ?

• Other funding arrangements as alternative to GCI fund ?• If no funding arrangements feasible, are GEO Members and Participating

Organizations ready to make a voluntary contribution of funds or in-kind support if and when a particular need is manifest?

• Increase registered resources.– Number of EO systems, data sets, and services registered is a small fraction of

those operated by GEO Members and Participating Organizations. – Urgent operational need to populate a comprehensive catalog of EO resources

across GEO.

• Linkages to Community Portals to be enhanced

Page 14: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Attendance to GCI-CT telecons since May 2010

End selection process (end Jun.10)

Page 15: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

Way Forward for GCI Operations & Enhancements(ESA’s proposal for new GEO 2012-2015 WP )

(AR-09-01e): Operations, maintenance and enhancement of the GCI components

Facilitate and support the operations (including maintenance) and enhancement of the GCI components (namely GEO Web Portal, Clearinghouse and Registries).

Routine operations management will be carried out through proper monitoring, maintenance and administration of both the GCI-component application software and hardware platforms, through the management of problems (detection, analysis and correction) and through reporting mechanisms. GCI components enhancement will be based on coordinated collection of suggestions for enhancements (user needs) coming from multiple sources, their assessment (evaluate need, urgency, resources needed for implementation), their feasibility analysis (e.g. in terms of available resources) by individual GCI providers and, in case of positive analysis, their implementation in a coordinated manner among the different component providers and transfer to operations.

GCI evolution will be coherent with the overall GEOSS architecture strategy.

The GCI core service operators, some relevant GEO community data and service providers, and some users representing a diversity of SBAs and scientific interests for data access and integration will play a key role in the GCI operations and enhancement.

Page 16: GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do

The Gateway to GEOSS Data, Information & Services

Obrigado …

Thank you …