6.5.2 Capacity Building Component

6.5.2 Capacity Building Component

6.5.2 Capacity Building Component

The Capacity-Building SBA Component primary goal is educational.

The Capacity Building AIP6 has just started to support both data providers and data users

by establishing a server code repository locus for GCI (GEOSS Common Infrastructure) and GeoDAB component software in the Best Practices Wiki located at

It will specify where to find resources, as links, that data providers and data users may

follow in order to discover, upload or download GEOSS data and services.

According to the recommendations proposed by the GEOSS AIP-4, AIP-5 participants, a server

code repository will be deployed and made available for the GCI components software

GeoTasks. GEOSS AIP-6 will leverage the lessons learned from both the AIP-4 and 5 approach (see

Figure xx) and the AIP-3 use cases-driven scenarios in such a way to make more

discoverable, accessible and usable the GEOSS components developed. Although we expect that it will be the responsibility of each GEOSS Users and or each Data Providers to keep up with the latest geospatial standard and interoperable interface, the Best Practices Wiki will be an additional resource in the challenge of becoming familiar to the GEOSS environment. If you have a suggestion or a feedback to give about it, please contact the person in charge of the Capacity Building. We appreciate your feedback at any time.

Slide1

Figure XX: Results coming from AIP4 and AIP5 – Summary Engineering Report version 0.12. It indicates three of the main areas of activity within Capacity Building WG (the Tutorials have been developed separately, as indicated in the following section of the Engineering Report).

The Capacity Building AIP6 moved during the year 2013 on two levels: at one level, the Capacity Working Group continued with their biweekly activity and formulated two possible scenarios as its contribution for AIP7; at another level, the Capacity Building continued its operational outreach toward developing counties, particularly to Chile.

The outcome of the Capacity Building Working Group can be summarized by the following two scenarios. As mentioned previously, these two scenarios can be seen as propositive in their nature and subject of further discussion and refinement. We are a mean of new ideas and we want to avoid duplication of effort: so these scenarios must be seen as indicative of future directions, not exhaustive and operational scenarios.

Scenario One

Citizen Observatory/ Crowd sourcing Monitoring:

The goal is to make available GEOSS web services and other GEOSS data-CORE from Data Providers, often supplier of a large volume of geospatial data, to people and GEOSS Users, specifically GEOSS Users from their mobile platforms. GEOSS Users will access, search and discover data and web services supplied by the Data Providers.

GEOSS Users will also be allowed to contribute with data collected by their mobile devices, to the GEOSS web services through customized applications. The applications will work either in a browser or through other means (peer-to-peer or others). Applications that are open source and/or within an open source, interoperable framework will be welcomed and encouraged. Such open-source, interoperable applications will be tested in different environments and geographic regions so to encourage a varied feedback and a resilience in the GEOSS solutions recommended.

The date will be stored into the cloud and other mediums as well as analyzed to detect pattern in the area of study. The topical areas are any of the nine Societal Benefit Areas ( agriculture, biodiversity, climate, disaster, ecosystems, energy, health, water, weather). Data Used: the GEOSS data-Core and other geospatial data coming from mobile sensor platforms.

Scenario Two:

Capacity Building Metrics: listening to the GEOSS User

The goal of this scenario is to start evaluating the performance of the data and web services with respect to one of the nine Societal Benefit Areas (agriculture, biodiversity, climate, disaster, ecosystems, energy, health, water, weather) in order to capture emerging GEOSS metrics, define more accurately the GEOSS User habits (by holding his/her privacy and anonymity), improve the performance, use of GEOSS data and web services, formulating additional Capacity Building policies and supplying possible different business models to Data Providers.

This scenario does not want to replicate any of the scenarios proposed and underway in the AIP- Data Sharing Working Group: please refer to them if you want to explore the authorization and accessibility to specific data and web services provided by different Data Providers, Internet Identity Providers within the GEOSS Framework).

The development of a performance metrics will give operational insights into the efficiency of the customer service. It will include average speed of answer (ASA), average handle time (AHT), hold time, abandon rate, wrap-up time, count of downloads per month (ftp, downloads over web browser or others), and other parameters (for example, for social media, number of Facebook events, twitters, hash tags during an event).

Depending on the location-time of the data and web services used, medium used, desktop, mobile sensor platforms (some related to social media), and topical area, the Capacity Building Metric may change, although we expect that open source and interoperable interfaces are recommended, so to be used in different geographic regions and countries of the world.

As previously mentioned, we also worked to build capacity in developing counties, both in South America and in Africa (mainly South Africa). We made most improvements with Chile, particularly in the development of a national infrastructure and in the international collaboration with GEOSS. Capacity Building helped GEO Chile during many initiatives, from building web pages to develop reports, presentations and collaborations both nationally and internationally to test data and web services to access satellite data, and make Chilean web services registered to GEOSS GCI, accessible, searchable and discoverable. For 2014, the future of AIP7, we plan to continue to test Chilean web services and to further the reaching out of GEOSS in South America and other developing countries.