1 / 21

Draft Report of the Architecture and Data Committee (ADC)

Draft Report of the Architecture and Data Committee (ADC). R.Shibasaki. Lis t of contents. Executive Summary Strategic Targets of Architecture and Data Management (ADM) Present Status of ADM ADC Achievements 2011 Next Steps. 1.Executive Summary. mmmmmmm. To be filled.

loren
Download Presentation

Draft Report of the Architecture and Data Committee (ADC)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Draft Report of the Architecture and Data Committee (ADC) R.Shibasaki

  2. List of contents • Executive Summary • Strategic Targets of Architecture and Data Management (ADM) • Present Statusof ADM • ADC Achievements 2011 • Next Steps

  3. 1.Executive Summary • mmmmmmm To be filled

  4. Strategic Targets of Architecture and Data Management(ADM) • Target of Architecture Achieve 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 Management Provide a shared, easily accessible, timely, sustained stream of comprehensive data of documented quality, as well as metadata and information products, for informed decision-making.

  5. Contribution of GEOSS members • ■Figure of Merits; • Completeness of functions • Sustainability • Operational availability • Content availability GCI Users

  6. Present status ofArchitecture and Data Management (ADM) Registered contents To be renewed 240 EO Systems 13,500 services 12,400 data sets (as of Sep. 2011) • Data products • Services Usability tests • User requirements ******* (as of Sep. 2011) • Standards, interoperability arrangements ******* (as of Sep. 2011)

  7. Present status ofArchitecture and Data Management (ADM) Registered contents Number of components Number of access… To be replaced with real values Data products Services year

  8. Monitoring and Evaluation (E&M) WG Report on ADM Planning and Management • No clear evidence that the ADM Strategic Targets will be met by 2015. • User Interface is difficult to use. • No uniform, consistent way that data are registered, stored and accessed. • Lack of Systems Engineering Rigor. • Technology employed is not current. • Data may exist but difficult to find. • No formal process for Gap Analysis between Targets and Tasks. • The present progress report does not allow for a quantitative evaluation of progress. • The GEOSS capabilities are not well communicated to global community. • Commercial and intellectual property rights are perceived as a barrier to publishing data in GEOSS. Technical Communication

  9. 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, GENESI DEC and FedEO. • Facilitating access to GEOSS Data CORE • AIP-4: supporting StP • Access to Priority EO Data Sources (direct data access) • Deployment of Clients and mediated components • Standard and Interoperability Forum (SIF) • Tutorial; “How to use GEOSS” • “Interoperability Assessment White Paper” based on GCI analysis to provide a sound basis for the improvement plan • looking at problems with, and recommending resolutions for, the ways in which the GCI functions.

  10. User query 1) All results incl. product collections 2) Products granules DATA DISCOVERY AND ACCESS DEMO SET-UP

  11. Demo Setup Data Handling Tools The downloaded product can be visualized by dedicated tools E.g. SST product in netCDF format as visualized by PANOPLY SW

  12. Progress of “Making Data on-Line through GCI” EO parameters actually covered by on-linedownloadable data through “StP” EO parameters potentially covered by on-line downloadable data 146 Critical Earth Observation Parameters 23? 23 Top 25 2? 2* 15 15? 121 No datasets available on-line 106 106? *Glacier/ice sheet *River Flow Obs. As of Oct 15, 2011 As of Oct 15, 2011

  13. Next Steps • Establish “Action Plan” for 2015 with clear definition of targets, milestones of ADM tasks. • Support the following overarching activities with the other committees or implementation boards • Improve task reporting system to enable quantitative evaluation of progress • Conduct Gap Analysis • ADC can provide a part of necessary information using registries of data/service resources and user requirements. • Create A communication plan (e.g. Tutorial on “How to use GEOSS”) • Enhance “raising-awareness” activities for the implementation of the GEOSS Data Sharing Action Plan.

  14. Progress of “Making Data on-Line through GCI” EO parameters actually covered by on-linedownloadable data through “StP” EO parameters potentially covered by on-line downloadable data 146 Critical Earth Observation Parameters 23? 23 Top 25 2? 2* 15 15? 121 No datasets available on-line 106 106? *Glacier/ice sheet *River Flow Obs. As of Oct 15, 2011 As of Oct 15, 2011

  15. Critical Earth Observation Priorities, Earth Observation Parameter

  16. Critical Earth Observation Priorities, Earth Observation Parameter Common EO Vocabulary

  17. Maintaining and Enhancing “Common EO Vocabulary” • Why? • “Interpreter” in Linking EO parameter names (vocabularies) to Facilitate Data Discovery • Progress indicator in “making EO data accessible on-line” • Need to maintain and enhancing Common EO Vocabulary based on GEO Task US-09-01a • Maintain and expand EO vocabulary • Determine associations with other vocabulary and ontology • Include SBA vocabulary for User Requirements Registry • Invite a group of reviewers from UIC/STC/ADC

  18. DB DB DB DB DB DB DB DB DB DB DB 农业 User’s vocabulary เกษตรกรรม biological terms 気象用語 Hydrology terms 농업 Search by terms Agriculture terms Producers’ vocabularies Climatology Landuse Classification scheme Health Science

  19. DB DB DB DB DB DB DB DB DB DB DB 农业 User’s vocabulary เกษตรกรรม biological terms 気象用語 Hydrology terms “Common Earth Observation Parameter” 농업 Agriculture terms Producers’ vocabularies Climatology Landuse Classification scheme Health Science

  20. Maintaining and Enhancing “Common EO Vocabulary” • Why? • “Interpreter” in Linking EO parameter names (vocabularies) to Facilitate Data Discovery • Progress indicator in “making EO data accessible on-line” • Need to maintain and enhancing Common EO Vocabulary based on GEO Task US-09-01a • Maintain and expand EO vocabulary • Determine associations with other vocabulary and ontology • Include SBA vocabulary for User Requirements Registry • Invite a group of reviewers from UIC/STC/ADC

  21. Linking EO parameter names (vocabularies) to Facilitate Data Discovery Common EO vocabulary Existing Producers’ EO vocabularies

More Related