1 / 20

GEOSS Interoperability for Weather Ocean and Water

EC Grant Agreement no. 282915. GEOSS Interoperability for Weather Ocean and Water. GEOSS Common Infrastructure Evolution. Roberto Cossu ESA Roberto.Cossu @esa.int. GEOWOW Partners. Technology Partners. Weather SBA. Ecosystem (Ocean) SBA. Water SBA.

keon
Télécharger la présentation

GEOSS Interoperability for Weather Ocean and Water

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. EC Grant Agreement no. 282915 GEOSSInteroperability for Weather Ocean and Water GEOSS Common Infrastructure Evolution Roberto Cossu ESA Roberto.Cossu@esa.int

  2. GEOWOW Partners Technology Partners Weather SBA Ecosystem (Ocean) SBA Water SBA

  3. High-level Project Information GEO Ministerial 2013: ‘Revised' architecture properly tested and demonstrated within GEOWOW SBA's January 2013 April 2014 August 2012 June 2014

  4. Objectives • To allow an easy and harmonised access to heterogeneous resources • To develop services for data discovery, access, and use establishing and promoting data sharing • Facilitate geo-resources sharing • Facilitate geo-resources access • Contribute to GCI enhancement • Develop GCI operational capabilities for the project’s SBAs

  5. A structuredsystemengineeringapproach User requirements Technology Base Constraints and recommendations From SBAs and GEOSS community From SBA systems and prior development efforts, including among others: From relevant initiatives and standardization bodies, including: AIP, StP SIF, IIB Current GCI Thorpex GOOS

  6. A structuredsystemengineeringapproach User requirements Technology Base Constraints and recommendations Requirements Analysis Functional Specification Design qualification Implementation acceptance validation and assessment GCI evolutions

  7. Towards a GEOWOW vision

  8. Communitiesin GEO-GEOSS MultidisciplinaryScientists / Decision Makers Domain specific scientists Data Scientists Data Providers Geo Web Portal Community portals Specialised toolkits Data Centers Observations Products Information Today, the GCI (GEOSS Common Infrastructure) is designed to support only a limited number of user typologies.

  9. Requirements • Initial set of user communities and multidisciplinary requirements identified by the GEOWOW partners: • MULTIDISCIPLINARY REQUIREMENTS • REQUIREMENTS FROM SBAs • Requirements from external sources, like projects and Architecture Implementation Pilot (AIP) processes

  10. Towards a GEOWOW vision • A long-term vision for the GCI evolution, in agreement with the IIB. • This will include not only components developed by GEOWOW itself, but also external elements.

  11. IIB meeting - Geneva

  12. Priority functionalities • Improved data discovery including results ranking; • Easier data access; • Interface of GCI components from external clients, including two ways communication; • Improved data usability, including harmonization and geoprocessing services; • New data registration mechanisms, including support for the GEOSS Data CORE • Solutions and tools for user registration authorization authentication including single sign-on.

  13. Landscape • GEOWOW has analysed important key technologies, establishing a pool of solutions and ideas • A preliminary analysis has been conducted to map identified requirements to analysed projects (EuroGEOSS, UncertWeb, GENESI-DEC, GeoViQua, Eye on Earth and the current GEOSS Common Infrastructure, …)

  14. Architectureflexibility • The landscape of technologies is in continuous evolution architecture flexibility is a key requirement. • The design of the GEOWOW Architecture shall therefore follow a modular approach. It shall result in a set of “GCI Evolutions”, i.e. interoperable components that respond to the community needs and are able to fit into the existing landscape, however rapidly this is evolving.

  15. Usage patterns • The proposed architecture will result as flexible as possible and different communities will benefit from it in different manners, according to their needs and their usual working habits.

  16. Usagepatterns • The proposed architecture will result as flexible as possible and different communities will benefit from it in different manners, according to their needs and their usual working habits.

  17. An example of use case Query of heterogeneous observations, products, information Semantic enriched search Just an example of use case from several usage patterns that will be possible according to user needs Satellite data In- Situ data Tools for geoprocessing Interferograms computed from satellite data (either on demand computation or discovery of previously generated products) Registration of results

  18. Preliminary identified components • Components for Enhancing Data Discovery and Access including: • Result Ranking; • Semanticenriched search; • Geoprocessing components; • User registration components and tools for authentication (user personal information will not be registered at GEOWOW side); • Resources Registration facilitators to improve the GEOSS Data CORE availability; • Components for enabling community specific clients to access GEOSS resources.

  19. In a nutshell: seamless discovery and access to… satellite data metadata airborne data documentation in-situ data processing services maps models …for all the identified GEOSS users according to different usage patterns… … with special focus on GEOSS Data CORE

  20. EC Grant Agreement no. 282915 Thankyou Project Web Site:http://www.geowow.eu/ Roberto Cossu Roberto.Cossu@esa.int

More Related