report of the architecture and data committee (adc) r.shibasaki (adc, japan)

22
Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Upload: riley-king

Post on 27-Mar-2015

221 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Report of the Architecture and Data Committee (ADC)

R.Shibasaki

(ADC, Japan)

Page 2: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Strategic Targets of Architecture and Data Management (ADM)

• Target of ArchitectureAchieve sustained operation, continuity and interoperability of existing and new systems that provide essential environmental observations and information, including the GEOSS Common Infrastructure (GCI) that facilitates access to, and use of, these observations and information.

• Target of Data ManagementProvide a shared, easily accessible, timely, sustained stream of comprehensive data of documented quality, as well as metadata and information products, for informed decision-making.

Page 3: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Strategic Targets of Architecture and Data Management (ADM)

• Target of ArchitectureAchieve sustained operation, continuity and interoperability of existing and new systems that provide essential environmental observations and information, including the GEOSS Common Infrastructure (GCI) that facilitates access to, and use of, these observations and information.

• Target of Data ManagementProvide a shared, easily accessible, timely, sustained stream of comprehensive data of documented quality, as well as metadata and information products, for informed decision-making.

Page 4: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Contribution of GEO

members

Contribution of GEO

members

Users

GCI

Page 5: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Contribution of GEO

members

Contribution of GEO

members

Users

GCI

?

How many data sets that meet requirements?

How easily discovered and used?

Operation is sustained?

Page 6: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Growth of Registered/Accessible Resources

DataData setssets

year

Number

Earth Earth Observation Observation SystemsSystems

ServicesServices

2010

500

141

1,000

1,500

191 43

10,000

1,000,000

100,000

10,000,000

Page 7: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Growth of Registered/Accessible Resources

DataData setssets

year

Number

Earth Earth Observation Observation SystemsSystems

ServicesServices

2010

500

141

1,000

1,500

191 43

2011 (Sept.)

90,909

1,492

381

10,000

1,000,000

100,000

10,000,000

Page 8: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Growth of Registered/Accessible Resources

DataData products*products*

year

Number

Earth Earth Observation Observation SystemsSystems

ServicesServices

2011(Nov.)2010

500

141

28,000,000+

1,000

1,500

191

1500+

43

500+

2011 (Sept.)

90,909

1,492

381

10,000

1,000,000

100,000

10,000,000

100,000,000

*via CEOS CWIC client integration(CWIC:CEOS WGISS Integrated Catalogue)

*via CEOS CWIC client integration(CWIC:CEOS WGISS Integrated Catalogue)

DataData setssets

Page 9: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

GCI

Why have resources increased so rapidly?

resources

Page 10: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

GCIBroker

Why have resources increased so rapidly?

resources

Page 11: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Why have resources increased so rapidly?

11

GCI

catalogue

Broker

catalogue

cataloguecatalogue

catalogue

resources

Page 12: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Why have resources increased so rapidly?

12

GCI

catalogue

Broker

catalogue

cataloguecatalogue

catalogue

resources

Page 13: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Semantic Issue in Search

13

GCI

catalogue

Broker

catalogue

cataloguecatalogue

catalogue

resources

rainfall precipitation

Page 14: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

GEOSS Earth Observation Vocaburaly

14

GCI

catalogue

Broker

catalogue

cataloguecatalogue

catalogue

Earth Observation

(EO) vocabulary

resources

Page 15: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

15

Passive to Active

Renewing GCI with Broker

GEOSS EO vocabularyDiscoverable data set or resources

can really meet users’ requirements?

Page 16: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Critical Earth Observation(EO) Priorities

Page 17: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Critical Earth Observation Parameters

Page 18: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Societal Benefit Areas

Used

Notused

Precipitation

Soil moisture

Surface air temperature

Surface wind speed

Land cover

How many of

the parameters

are covered by

downloadable

data sets?

Page 19: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Critical EO Parameters Covered by “Downloadable” Data Sets Through GCI

146 Critical Earth Observation

(EO) Parameters Top 25Importantparameters

121

23

88

EO parameters covered by “downloadable” data sets through GCI.

33

2

As of Nov, 2011

EO parameters not covered by datasets available on-line

111 or 76 % of

Critical EO parameters

are now covered.

111 or 76 % of

Critical EO parameters

are now covered.

Page 20: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

ADC Achievements 2011• Discovery and access (e.g. download) of broader and more

heterogeneous EO data products with current technology– “Sprint to Plenary (StP)”

• Prototyping of New GCI with EuroGEOSS and GENESI DEC.• Facilitating access to GEOSS Data CORE

– AIP-4: supporting StP• Access to critical EO data sets (direct data access)• EO vocabulary (ontology team)• Software tools to access and exploit EO data

– Standards and Interoperability Forum (SIF) and AIP-4• Tutorial; “How to use GEOSS”

• “Interoperability Assessment White Paper” by SIF– Based on analysis on GCI uses, identified ways to improve GCI

functionality to better support interoperability.

Page 21: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

Next Steps• Enhance work plan with clear definitions of targets and

milestones for ADC tasks, ensuring that the strategic targets are achieved by 2015.

• Evolve GCI– Enable access and exploitation of data discovered via GCI,

including mobile applications

– Support cross SBA applications (e.g. water + health ) for development of earth data products and information

• Facilitate the expansion of interoperable Earth Data Sets and their incorporation into GEOSS

• Better Communication– Create and implement a communication plan (e.g. Tutorial on

“How to use GEOSS”)

Page 22: Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)

END

22