1. Session 3 Breakout Report GCI/DMP/DSP GEO Work Program Symposium Osamu Ochiai GEO Secretariat May Tshwane, SA

2. GEOSS Data Sharing Principles 2016-2025
data, metadata and products will be shared as Open Data by default, by making them available as part of the GEOSS Data Collection of Open Resources for Everyone (Data-CORE) without charge or restrictions on reuse, subject to the conditions of registration and attribution when the data are reused;
where international instruments, national policies or legislation preclude the sharing of data as Open Data, data should be made available with minimal restrictions on use and at no more than the cost of reproduction and distribution; and
all shared data, products and metadata will be made available with minimum time delay.
Changes from the Data Sharing Principles of last decade:
Sharing EO as open data by default = the GEO norm
Sharing with restrictions : perceived as an exception
Alignment with the International Open Data Charter
Refrains from imposing charges that exceed the cost of reproduction and distribution
For any purpose by anyone (last DSPs promote data sharing for non-commercial use)

3. Volume – Variety – Veracity Value – Velocity – Visualisation …
Shall consider:
Different providers/heterogeneous data
different sensors (satellites, airplanes, drones, in-situ)
different quality and provenance
different scales (global, regional, local, ..)
different volume
Wide Variety of Users from data scientists to decision and policy makers, within the public and private sector, and considers as well citizens as part of their target community – as well as users from different application domains…
Volume – Variety – Veracity
Value – Velocity – Visualisation …
Challenge
a SHORT INTRODUCTION GEOSS – the Global Earth Observation System of Systems.
Its MAIN MISSION is to FACILITATE SHARING of EO data, information and other resources
FROM Heterogeneous Data Resources
FOR many DIFFERENT TYPES of USERs or USAGES
It does so via the GEOSS Common Infrastructure
a set of coordinated, independent Earth observation, information and processing systems that interact and provide access to diverse information for a broad range of users in both public and private sectors.
links these systems to strengthen the monitoring of the state of the Earth. It facilitates the sharing of environmental data and information collected from the large array of observing systems contributed by countries and organizations within GEO.
ensures that these data are accessible, of identified quality and provenance, and interoperable to support the development of tools and the delivery of information services.

4. GCI Different providers/heterogeneous data
different sensors (satellites, airplanes, drones, in-situ)
different quality and provenance
different scales (global, regional, local, ..)
different volume
Wide Variety of Users from data scientists to decision and policy makers, within the public and private sector, and considers as well citizens as part of their target community – as well as users from different application domains…
GUI
M2M
So actually the GCI is trying to CONNECT the USERS with the DATA PROVIDERS (– considering the requirements just mentioned.)
And as mentioned this is done via the GCI, and two of its MAIN COMPONENTS are the GEOSS PORTAL – its FRONT-END and the GEO-DAB the MIDDLEWARE
And these provide the INTERFACES to ESTABLISH this HANDSHAKING.
GCI

5. x
Map-based, single Internet access point/GUI providing generic as well as more community-specific search capabilities supporting as well users interested in particular societal benefits of application of Earth observations.
The GEO DAB brokering framework interconnects hundreds of heterogeneous and autonomous supply systems (the enterprise systems constituting the GEO metasystem) by providing mediation, harmonization and transformation capabilities.
GEO DAB APIs can be used to discover and access GEOSS resources via the GCI.
Three types of APIs:
Standard Web Services: standard interfaces which comply with de-iure and de-facto geospatial standards such as OGC CSW, WCS, WMS, WFS, OAI-PMH, etc.
Client-side APIs: high level client-side library, designed and developed to facilitate the development of web and mobile applications, presently available as a Javascript library.
Server-side APIs: a set APIs, including OpenSearch and RESTful APIs.
In summary:
- The GEOSS PORTAL provides the Graphical User Interface
The GEO-DAB provides the brokering framework connecting the different providers on the one hand and as well providing a SET of APIs for Machine-to-Machine interaction and of course to interface with the PORTAL.
Some are more generic – others more SPECIFIC which can be used to RESPOND to MORE thematic/SBA community specific needs. – Implemented via VIEWs.
The APIs are used as well to define and utilize SBA-specific views of the GEOSS resources, i.e. a customized subset of GEOSS resources targeting the needs of the SBA communities.

6. GCI Trade-Off
The GCI needs to offer both generic and specific capabilities x
Simple, intuitive map-based user-interface
Key-word-based search
With multi-criteria search capabilities
With generic filtering capabilities
With smart filters which are datatype-dependent (Sentinel-1/2 and Landsat) or community-dependent (views) – (e.g. for Disaster Resilience and Water Resource Management)
Reusable components are offered for community portal implementations

7. Current focus User-centric, considering various user communities:
GEO Flagships and Global initiatives
ESA Thematic Exploitation Platforms
Copernicus Core Services: Atmosphere (CAMS), Marine (CMEMS), Land (CLMS), Climate (C3S), Emergency (EMS), Security
Additional enhancements considered include:
My workspace evolution;
Multi-modality and responsive web-design;
Statistics;
GEOSS Portal Reuse: Widgets and Mirroring;
Visualisation services (e.g. layers, legend, …);
GEO Like and social collaboration;
Processing services
Number of users and sessions
Geographical Distribution
Use per browser & devices
Most searched terms / locations/ …
Resources viewed / loaded on map / downloaded
ONGOING and UPCOMING developments
 Focus on users and their requirements – what you see are examples of such communities – in particular the GEO Flagships and Global Initiatives, ESA Thematic Exploitation Platforms, as well as Copernicus Services
Opacity in layers
Layers order
Windows moving
Evolving interface

8. >>
Because of effort s in CEOS/WGISS Workinggroup and others for which we should NOW be already close to a Billion resources!

9. Capacity Building & GCI Updates
2017
Today
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Stakeholder Involvement of
Outmost Importance
GCI-Updates
GEO-Workshops/Events
GEO-Portal Workshops
Overview of the different activities represented as calendar view for Information regarding these dates can be found as well via GEO web-pages.
Today we are here of course.
User-Community Workshops

10. Framing the Evolution
Acknowledgement of past achievements in developing data sharing and data management principles, and common infrastructure focused on search, discovery and access.
Recognition that we need to be more user driven and focused e.g. by linking better to priorities given by Plenary (SDG, Paris climate change agreement, Sendai framework for disaster risk management) and GEO initiatives and flagships.
Emergence of GEO regional implementations is an opportunity to link better to national and local needs. This needs to be reflected in the evolution of the architecture and governance (relationships among regional nodes)

11. Evolving landscape
The world around us is constantly changing with new political priorities (economy, migration, security, resilience etc. )
New actors and business models in EO data collection and consumption (private sector, Internet of Things, the general public…)
Greater emphasis from accessing data, to analytics and information products (answers to questions) i.e. from data search and discovery to linking data, analytics, and processing on platforms > interoperability of platforms becomes an issue
Multidimensional data cubes as organising principles from business analytics increasingly adopted for EO.
Etc…..

12. Implications for GEOSS-EVOLVE
The group started a reflection on the trends and needs outlined above
Will present a document summarizing the view of the group and identifying directions for future work of the GEOSS-EVOLVE initiative to be included in the revised Work Programme for
If you are interested in contributing to this activity advancing the GEOSS architecture and evolution, please join us!