d m a n d pl a t f o r m s f o r si n g l e pi l o t s€¦ · otakar Čerba karel charvat ccss mac...

Data MoDels anD PlatforM sPecifications for single Pilots

JUNE 2015

DELIVERABLE

Project Acronym: SDI4Apps

Grant Agreement number: 621129

Project Full Title: Uptake of Open Geographic Information Through Innovative

Services Based on Linked Data

D6.1 DATA MODELS AND PLATFORM

SPECIFICATIONS FOR SINGLE PILOTS

Revision no. 06

Authors: Anna Builo- Hoļme (Zemgale Planning Region)

Austra Irbe (Zemgale Planning Region)

Irena Koskova (Czech Centre for Science and Society)

John O'Flaherty (The National Microelectronics Applications Centre Ltd)

Martin Tuchyňa (Slovak Environmental Agency)

Otakar Čerba (University of West Bohemia)

Pavel Vlach (University of West Bohemia)

Karel Charvat (Czech Centre for Science and Society)

Project co-funded by the European Commission within the ICT Policy Support Programme

Dissemination Level

P Public X

C Confidential, only for members of the consortium and the Commission Services

D6.1 Data Models and Platform Specifications for Single Pilots

of 100 © SDI4Apps Consortium 2015

REVISION HISTORY

Revision Date Author Organisation Description

01 19/06/2015 Irena Koskova

John O'Flaherty

Martin Tuchyňa

Otakar Čerba

Karel Charvat

Anna Builo-Hoļme

Austra Irbe

CCSS

MAC

SAZP

UWB

CCSS

ZPR

ZPR

Initial draft based on discussions among SDI4Apps partners.


John O'Flaherty

Martin Tuchyňa

Otakar Čerba

Karel Charvat

CCSS

MAC

SAZP

UWB

CCSS

Partners input on the pilot

description.

03 27/06/2015 Austra Irbe ZPR

Formatting, minor changes

04 29/06/2015 Tor Gunar Øverli

Tomas Mildorf

AVINET

UWB Internal Review


John O'Flaherty

Martin Tuchyňa

Otakar Čerba

Karel Charvat

Michal Kepka

CCSS

MAC

SAZP

UWB

CCSS

UWB

Updates based on suggestions by

reviewers.

30/06/2015 Austra Irbe ZPR

Final Version

Statement of originality:

This deliverable contains original unpublished work except where clearly indicated otherwise. Acknowledgement of previously published material and of the work of others has been made through appropriate citation, quotation or both.

Disclaimer:

Views expressed in this document are those of the individuals, partners or the consortium and do not represent the opinion of the Community.



TABLE OF CONTENTS

Revision History ............................................................................................................... 3

Table of Contents ............................................................................................................. 4

List of Tables .................................................................................................................. 7

List of Figures .................................................................................................................. 9

Executive Summary ......................................................................................................... 10

1 Introduction ............................................................................................................ 11

2 Easy data access – pilot 1 ............................................................................................ 12

2.1 Use Cases .......................................................................................................... 12

2.2 User Engagement and Business Planning ..................................................................... 18

2.2.1 Stakeholders and their roles .............................................................................. 18

2.2.2 Engagement method ....................................................................................... 19

2.2.3 Incentives for engagement ................................................................................ 19

2.2.4 Timing, planning, indicators .............................................................................. 19

2.2.5 Business plan - market potential ......................................................................... 20

2.3 Data Acquisition .................................................................................................. 21

2.3.1 Datasets ...................................................................................................... 21

2.3.2 Data Models .................................................................................................. 23

2.4 Apps and Services ................................................................................................ 26

2.4.1 European Tourism Indicator System User Apps ........................................................ 27

2.4.2 Potential Monuments Ground Truthing App ............................................................ 28

2.4.3 Services ...................................................................................................... 29

2.4.4 Cloud properties ............................................................................................ 33

3 Open Smart Tourist Data – pilot 2 ................................................................................... 34

3.1 Use Cases .......................................................................................................... 35

3.2 User engagement and business planning ..................................................................... 42


3.3.1 Datasets ...................................................................................................... 42

3.3.2 Data Models .................................................................................................. 43


3.4.1 User Apps .................................................................................................... 45

3.4.2 Services ...................................................................................................... 47


4 Open Sensor network - Pilot 3 ....................................................................................... 50

4.1 Use Cases .......................................................................................................... 50





4.3.1 Datasets ...................................................................................................... 53

4.3.2 Data Models .................................................................................................. 54


4.4.1 User Apps .................................................................................................... 56

4.4.2 Services ...................................................................................................... 58


5 Open Land Use Map Through VGI - Pilot 4 ......................................................................... 60

5.1 Use Cases .......................................................................................................... 60



5.3.1 Datasets ...................................................................................................... 64

5.3.2 Data Models .................................................................................................. 65


5.4.1 User Apps .................................................................................................... 65

5.4.2 Services ...................................................................................................... 67


6 Open INSPIRE4Youth – pilot 5 ........................................................................................ 69

6.1 Use Cases .......................................................................................................... 70



6.3.1 Datasets ...................................................................................................... 75

6.4 Data Models ....................................................................................................... 76


6.5.1 User Apps .................................................................................................... 76

6.5.2 Services ...................................................................................................... 77


7 Ecosystem services Evaluation – Pilot 6 ............................................................................ 80

7.1 Use Cases .......................................................................................................... 80


7.2.1 Stakeholders and their roles .............................................................................. 83

7.2.2 Engagement method ....................................................................................... 83

7.2.3 Incentives for engagement ................................................................................ 83

7.2.4 Timing, planning, indicators .............................................................................. 83

7.2.5 Business plan - market potential ......................................................................... 84




7.3.1 Datasets ...................................................................................................... 84

7.3.2 Data Models .................................................................................................. 94


7.4.1 User Apps .................................................................................................... 96

7.4.2 Services ...................................................................................................... 97


8 Conclusion .............................................................................................................. 99



LIST OF TABLES

Table 1 Easy Data Access pilot Use case 1 .............................................................................. 15

Table 2 Easy Data Access pilot Use case 2 .............................................................................. 18

Table 3 Easy Data Access pilot Stakeholders and their roles ........................................................ 19

Table 4 Easy Data Access pilot Success Indicators ..................................................................... 20

Table 5 Easy Data Access pilot data set: European Tourism Indicator System .................................... 22

Table 6 Easy Data Access pilot data set: Potential Monuments Voluntary Geographic Information Dataset . 23

Table 7 Easy Data Access pilot European Tourism Indicator System user Apps ................................... 27

Table 8 Easy Data Access pilot Potential Monument Ground Truthing App ........................................ 29

Table 9 Easy Data Access pilot Enablers................................................................................. 30

Table 10 Easy Data Access pilot service: Advanced Visualisations .................................................. 30

Table 11 Easy Data Access pilot service: Data Harmonisation ....................................................... 31

Table 12 Easy Data Access pilot service: Integration of mobile Apps .............................................. 32

Table 13 Easy Data Access pilot service: Interoperability between local & global geospatial models ........ 32

Table 14 Easy Data Access pilot service: Linked Open Data ......................................................... 33

Table 15 Easy Data Access pilot Cloud Property requirements ...................................................... 33

Table 16 Open Smart Tourist Data pilot Use case 1 ................................................................... 36





Table 21 Open Smart Tourist Data pilot data set: SDI4Apps POIs ................................................ 43

Table 22 Open Smart Tourist Data pilot data set: Joint Road Data .............................................. 43

Table 23 Smart Open Tourist Data user App 1.......................................................................... 45



Table 26 Open Smart Tourist Data pilot service: Relational database ............................................. 47

Table 27 Open Smart Tourist Data pilot service: No-SQL database ................................................. 48

Table 28 Open Smart Tourist Data pilot service: No-SQL database ................................................. 49

Table 29 Smart Open Tourist Data pilot Cloud Property requirements ............................................ 49

Table 30 Open Sensor network pilot Use case 1 ....................................................................... 51



Table 33 Open Sensor Network pilot data set: Senslog Catalogue .................................................. 54

Table 34 Open Sensor Network pilot data set: Senslog Database ................................................... 54

Table 35 Open Sensor Network pilot App 1 ............................................................................. 57



Table 38 Open Sensor Network pilot service: Senslog ................................................................ 59

Table 39 Open Sensor Network pilot Cloud Property requirements ............................................ 59

Table 40 Open Land Use Map through VGI pilot Use case 1 .......................................................... 61



Table 43 Open Land Use Map through VGI pilot data set: Open Land Use ..................................... 65

Table 44 Open Land Use Map through VGI user App 1 ................................................................ 66

Table 45 Open Land Use Map through VGI user App 2 ................................................................ 67

Table 46 Open Land Use Map through VGI pilot service: Data editor ............................................... 67



Table 47 Open Land Use Map through VGI pilot Cloud Property requirements ............................... 68

Table 48 Open INSPIRE4Youth Pilot: Use case 1 ....................................................................... 72



Table 51 Open INSPIRE4Youth pilot data set: Protected sites ....................................................... 75

Table 52 Open INSPIRE4Youth pilot data set: Administrative boundaries ......................................... 75

Table 53 Open INSPIRE4Youth user App 1 ............................................................................ 77

Table 54 Open INSPIRE4Youth user App 1 ............................................................................ 77

Table 55 Open INSPIRE4Youth pilot service: Authorization and authentication .............................. 78

Table 56 Open INSPIRE4Youth pilot service: Maps services ....................................................... 78

Table 57 Open INSPIRE4Youth pilot service: Mobile Application................................................. 79

Table 58 Open INSPIRE4Youth pilot Cloud Property requirements .............................................. 79

Table 59 Ecosystem services Evaluation Pilot: Use case 1 ........................................................... 81

Table 60 Ecosystem services Evaluation Pilot: Use case 2 ........................................................... 82

Table 61 Ecosystem services Evaluation Pilot stakeholders .......................................................... 83

Table 62 Ecosystem services Evaluation Pilot success criteria ...................................................... 84

Table 63 Ecosystem services Evaluation Pilot Dataset: Corine land cover ......................................... 85

Table 64 Ecosystem services Evaluation Pilot Dataset: Protected sites ............................................ 85

Table 65 Ecosystem services Evaluation Pilot Dataset: Administrative boundaries (SVM 50) ................... 86

Table 66 Ecosystem services Evaluation Pilot Dataset: Livestock statistics ....................................... 86

Table 67 Ecosystem services Evaluation Pilot Dataset: Wood (Paper pulp) production ......................... 87

Table 68 Ecosystem services Evaluation Pilot Dataset: Number of livestock per hectare of pasture ......... 88

Table 69 Ecosystem services Evaluation Pilot Dataset: Carbon sequestration based on land types ........... 88

Table 70 Ecosystem services Evaluation Pilot Dataset: Landscape quality from tourism perspective ... 89

Table 71 Ecosystem services Evaluation Pilot Dataset: Biodiversity ............................................ 90

Table 72 Ecosystem services Evaluation Pilot Dataset: Overall assessment of ecosystem services ...... 90

Table 73 Ecosystem services Evaluation Pilot Dataset: Cultural sites interesting for tourism – Castles,

Chateaus and Ruins ........................................................................................................ 91

Table 74 Ecosystem services Evaluation Pilot Dataset: Natural sites interesting for tourism – spas,

thermal springs, caves and waterbodies .............................................................................. 92

Table 75 Ecosystem services Evaluation Pilot Dataset: Sites of UNESCO world natural and cultural

heritage ...................................................................................................................... 92

Table 76 Ecosystem services Evaluation Pilot Dataset: Tourism and recreation zones ..................... 93

Table 77 Ecosystem services Evaluation Pilot Dataset: Population density ................................... 94

Table 78 Ecosystem services Evaluation Pilot User App ........................................................... 96

Table 79 Ecosystem services Evaluation Pilot required Services ................................................ 98

Table 80 Ecosystem services Evaluation Pilot required Cloud Properties ..................................... 98

Table 81 Use cases of Single Pilots ..................................................................................... 99



LIST OF FIGURES

Figure 1 Burren National Park ............................................................................................. 12

Figure 2 ETIS data model .................................................................................................. 24

Figure 3 Ground-Truthing PS data Model ................................................................................ 25

Figure 4 Ground-Truthing PS Simple Application Schema ............................................................ 26

Figure 5 ETIS App Screens ................................................................................................. 28

Figure 6 Open Smart Tourist Data Roads data model ................................................................. 44

Figure 7 Open Sensor Network pilot data model ....................................................................... 55

Figure 8 Open Sensor Network pilot Apps basic schema .............................................................. 56

Figure 9 Open Land Use Map through VGI pilot Data model.......................................................... 65

Figure 10 Open INSPIRE4Youth pilot ..................................................................................... 69

Figure 11 Ecosystem Services evaluation pilot Data model .......................................................... 95

Figure 12 Ecosystem Services evaluation pilot User App ............................................................. 97



EXECUTIVE SUMMARY

SDI4Apps using and adapting experience from previous projects creates a cloud based framework with open API for data integration, easy access and prospects for further reuse. Six pilots are used to validate the created solution. Deliverable 6.1 contains information about data models, which will be used for single pilots, specifies the components of single pilots, as it is on the beginning of second year, and describes future developments. Use cases, user engagement and business planning, data acquisition, Apps and required services are described in separate chapter for every pilot.



1 INTRODUCTION

SDI4Apps aims to ensure that synergy between INSPIRE and various voluntary initiatives is mutually beneficial. SDI4Apps sets a goal to bridge government-related top-down managed spatial data infrastructures (SDI), and the world of voluntary individuals, initiatives, and small and medium enterprises (SMEs) developing applications (apps) based on geographic information. The sixth work package “Internal Pilot Applications” is devoted to SDI4Apps framework and tools evaluation through pilot deployment and demonstrations. To validate solutions created by SDI4Apps six pilots are used:

1. Easy Data Access,

2. Open Smart Tourist Data,

3. Open Sensor Network,

4. Open Land Use Map Through VGI,

5. Open INSPIRE4Youth,

6. Ecosystem services evaluation.

During the three years of the SDI4Apps project four deliverables are planned in WP6:

D6.1) Data Models and Platform Specifications for Single Pilots [this deliverable] D6.2) Initial Deployment of Single Pilot Platforms [month 18], D6.3) Progress Report and Pilot Platforms Update [month 24], D6.4) Progress Report and Final Pilot Platforms Release [month 36].

During the first year and the beginning of the second year, the project has undertaken work with defining methodologies, community building, preparation of architecture and required functionalities, and pilot development. The main focus of Deliverable D6.1 is set on use cases, user engagement, data models, platform services and final apps of single pilots.



2 EASY DATA ACCESS – PILOT 1

The aim of the Easy Data Access pilot application is to adapt an Open API which will support easy integration of new applications with existing SDIs. The pilot, which is focused on the Burren National Park in Ireland, is supporting the wider communities’ identification, reporting, and recording of tourist destinations and ground truthing of protected heritage sites datasets in collaboration with the Burren LIFE1 and SmartOpenData2 projects. The pilot is using the SDI4Apps cloud platform to enable mobile Apps and services that involve various targeted communities of users through awareness, using social media, crowd-sourcing and open map-based geospatial data.

2.1 Use Cases

The Burren National Park3, in which the Easy Acces Pilot will be operated, consists of 1,500 hectares, has been designated the Burren and Cliffs of Moher Geopark4, is located on the west coast of Ireland and is an unique area of high conservation value containing many habitats of international importance including limestone pavement, calcareous grassland, oligotrophic lakes, turloughs, hazel scrub & ash/hazel woodland. It is managed by the Irish National Parks and Wildlife Service, and involves many local communities, stakeholders and Europe-wide environmental issues.

Figure 1 Burren National Park

From initial Social Validation meetings and discussions with the various stakeholder groups in the Burren, as described in D2.2 (Social Validation Methodology), the following Use Cases were identified as being potentially most beneficial to them;

1. SDI4Apps enabled European Tourism Indicator System (ETIS) Webservice for the Burren and European GeoParks Network, to support Tourism for Conservation

2. SDI4Apps enabled App to Ground-Truth potential Protected Heritage sites.

1 See www.burren.ie 2 www.smartopendata.eu 3 www.burrennationalpark.ie 4 www.burrengeopark.ie

http://www.burren.ie/

http://www.smartopendata.eu/

http://www.burrennationalpark.ie/

http://www.burrengeopark.ie/

http://bioblitz.biodiversityireland.ie/wp-content/uploads/burren1.jpg





SDI4Apps will enable a European Tourism Indicators System (ETIS) Webservice and Apps for the Burren and European GeoParks Network. ETIS is a new EU standard5, that is a local community led process for monitoring, managing, and enhancing the sustainability of a tourism destination. SDI4Apps will enable streamlining and enhancing the current manual system by transforming the current manual system to Linked Open Geospatial Data. The Burren Geopark has adopted the ETIS for the Sustainable Management of Destinations to monitor and measure performance, and is one of 100 destinations in Europe that are currently piloting this system. In addition, Failte Ireland, the national tourism development authority, has expressed interest in using the Geopark’s work on the ETIS as a pilot for assessing for larger-scale, national projects.

The Geopark also manages the Burren Tourism for Conservation LIFE Project (LIFE11/IE/922)6. The aim of this LIFE project is to strengthen the integration of tourism and natural heritage, reconciling tourism development with conservation of geology, biodiversity and cultural heritage in the Burren area of County Clare. The innovative aspect of the Project is to advance tourism for conservation as a European model of value to local communities. This aims to be a strong demonstration project with pilot actions being stimulated to test the use of tourism for conservation in the Burren.

The SD4Apps platform enabled apps will directly contribute to the project’s objective “To show measurable environmental, social and economic benefits of the model”, and be part of the model that can be transferred to all European GeoParks, and thus enable its long-term sustainability and exploitation by MAC.

Use case ID: UC1.1

Use case Name: ETIS Webservice for the Burren & European GeoParks Network

Abstract: The SDI4Apps enabled European Tourism Indicators System (ETIS) webservice for sustainable management at destination level, will streamline and enhance the current manual system by transforming the ETIS Excel dataset into Linked Open Geospatial Data.

Description (all the steps that will be done by the user):

The Burren Geopark’s solidity as a destination is exemplified by its benchmarking and monitoring procedures. It has adopted the recently launched European Tourism Indicator System for the Sustainable Management of Destinations (ETIS) 7 to monitor and measure performance and is one of 100 destinations in Europe that are currently piloting this system. Further to this, Failte Ireland, the national tourism development authority, has expressed interest in using the Geopark’s work on the ETIS as a pilot for assessing for larger-scale, national projects.

The SDI4Apps enabled European Tourism Indicators System (ETIS) webservice for sustainable management at destination level, will streamline and enhance the current manual system by transforming the ETIS Excel dataset into Linked Open Geospatial Data, and enable the Burren GeoPark initially (and all other GeoParks subsequently) to:

1. Set up their destination with suitable indicators and targets (by its Local Destination Co-ordinator and Stakeholder Working Group).

5 Defined as an Excel Spreadsheet dataset and PDF Guide at http://bookshop.europa.eu/en/the-european-

tourism-indicator-system-pbNB3213182/ 6 See www.burren.ie 7 http://ec.europa.eu/enterprise/sectors/tourism/sustainable-tourism/indicators/index_en.htm

http://bookshop.europa.eu/en/the-european-tourism-indicator-system-pbNB3213182/


http://www.burren.ie/

http://ec.europa.eu/enterprise/sectors/tourism/sustainable-tourism/indicators/index_en.htm



2. Provide online data collection by each stakeholder group (including Destination management, Enterprise, Resident and Visitor Surveys) – this will include automatic updating from appropriate online source databases.

3. Review progress and results achieved to date at their destination by Monitoring Results and Charting Destination, Enterprises, Residents, Visitors Impressions, Spending and Time – this will include automatic geographic visualization by linking to appropriate Geospatial data sources. This will enable the Stakeholder Working Group and visualization by the various stakeholders to provide an ongoing community “crowdsourcing verification” that the results and data being entered matches the perceptions of the various stakeholders.

4. Provide benchmarking with other destinations (e.g. other GeoParks) through each of these views and access to their linked open datasets8.

5. The webservice will be accessible on PCs, Tablets and Smart Phones.

It is anticipated that as each destination’s use of the ETIS matures and the indicator data collected becomes more extensive, the webservice will enable comparisons of the destination’s progress against international benchmarks. This will give greater context to the achievements and give destination stakeholders motivation to take further actions to improve results. It will also encourage knowledge sharing between destinations. The intention is not to create competition between destinations, but to recognize that the results generated through the process are core to the decision making plans for each destination.

User groups/ stakeholders:

Public bodies – National Parks Wildlife Service (NPWS)

Experts – Researchers and management in the Burren GeoPark, GeoParks Network.

Enterprises, Companies and SMEs – Burren GeoPark

Citizens – visitors to the Burren National Park.

How and when will the users be involved in the design and development process?

Using the Social Validation approach and plans defined in D2.2 users have been engaged since very early in the project.

Criteria of success: Usage level & Social Validation of Services that use SDI4Apps

Easy collection of information using smart phones & LOD

Integration of VGI into existing SDIs & LOD

Increased access to harmonised & interoperable GI, L/OD & VGI data

Integrate data from users’, OD, crowd-sourced & social media.

8 The pilot may find that the ongoing community stakeholders’ crowdsourcing verification at point 3, may not be adequate for the Geoparks Network, who may prefer to include independent 3rd party verification of the data to ensure the integrity of the ETIS benchmarking across the Geoparks. This may require another visualisation option across the destinations to verify that the data being entered is good as basically the GeoParks will be competing with each other in the GeoParks Network benchmarking exercise.



Reuse & share tourist information resources, channels & tools

SMEs, Students & Researchers developing new Apps

New tourism activities, visitors & jobs, and SME developed services.

Interoperation with other SDI4Apps pilots:

Open Smart Tourist Data

Open INSPIRE4Youth

Ecosystem Services Evaluation

Performance: Standard user acceptable response and latency times for information retrieval of 2 seconds9, to be measured as defined in D3.5 (Technical Test Methodology).

App ID: A1.1.

Notes and issues: The Burren GeoPark Team will be able to:

Set up their destination with suitable indicators and targets (by its

Local Destination Co-ordinator and Stakeholder Working Group).

Provide online data collection by each stakeholder group (including

Destination management, Enterprise, Resident and Visitor Surveys) –

this will include automatic updating from appropriate online source

databases.

Review progress and results achieved to date at their destination by

Monitoring Results and Charting Destination, Enterprises, Residents,

Visitors Impressions, Spending and Time – this will include automatic

geographic visualisation by linking to appropriate Geospatial data

sources. This will enable the Stakeholder Working Group and

visualisation by the various stakeholders to provide an ongoing

community “crowsdsourcing verification” that the results and data

being entered matches the perceptions of the various stakeholders.

Provide benchmarking with other destinations (e.g. other GeoParks)

through each of these views and access to their linked open

datasets10.

Once proven by the Burren Team, further GeoParks will be able to implement similar activities, and provide benchmarking with other destinations (e.g. other GeoParks) through each of these views and access to their linked open datasets. The pilot may find that the ongoing community stakeholders’ crowdsourcing verification at point 3, may not be adequate for the Geoparks Network, who may prefer to include independent 3rd party verification of the data to ensure the integrity of the ETIS benchmarking across the Geoparks. This may require another visualisation option across destinations to verify that the data being entered is good as basically the GeoParks will be competing with each other in the GeoParks Network benchmarking exerecise.

Table 1 Easy Data Access pilot Use case 1

9 “A study on tolerable waiting time: how long are Web users willing to wait?”, Nah, F. Behaviour & Information

Technology, 2004, available at http://sighci.org/uploads/published_papers/bit04/BIT_Nah.pdf 10 The pilot may find that the ongoing community stakeholders’ crowdsourcing verification at point 3, may not be adequate for the Geoparks Network, who may prefer to include independent 3rd party verification of the data to ensure the integrity of the ETIS benchmarking across the Geoparks. This may require another visualisation option across the destinations to verify that the data being entered is good as basically the GeoParks will be competing with each other in the GeoParks Network benchmarking exercise.

http://sighci.org/uploads/published_papers/bit04/BIT_Nah.pdf



The SDI4Apps platform will enable the provision of an App service to mobilise a very motivated community, by enabling visitors and people interested in their local heritage, to seek out and ground truth11 potential monument sites in the Burren National Park and beyond. Verified sightings will be added to the Irish National Monuments Database12. In Ireland, the Irish Heritage Council13 is a statutory body that takes an integrated approach to heritage, with responsibilities that include both its cultural and natural aspects. The Heritage Council’s vision is that the value of heritage is enjoyed, managed and protected for the vital contribution that it makes to the community’s identity, well-being and future. In practical programmes across Ireland the Heritage Council is putting in place infrastructure and networks to enable communities to take responsibility for and participate in the development and conservation of their heritage assets. This Ground Truthing App will contribute directly to that, and in turn provide a means for its long-term sustainability and exploitation by MAC. The SDI4Apps platform will enable the provision of an App service to mobilise a very motivated community, by enabling visitors and people interested in their local heritage, to seek out and ground truth 14 potential Monument sites in the Burren and beyond.

Use case ID: UC1.2

Use case Name: App to Ground-Truth potential Protected Monument sites

Abstract: SDI4Apps enabled App to Ground-Truth potential Protected Monument sites.

Description (all the steps that will be done by the user):

The SDI4Apps platform will enable the provision of an App service to mobilise a very motivated community, by enabling visitors and people interested in their local heritage, to seek out and ground truth potential Monument sites in the Burren and beyond. At the end of the project, the Heritage Council and National Monuments Service will decide if the crowd-sourced ground truthing observations (both positive and negative) should be included as a permanent Voluntary Geographic Information (VGI) layer on the National Monuments map on their Mapping Viewer. This process will also initiate a process for the digital preservation of the VGI data concerning the features that were investigated, both those that are validated to be national monument sites, and those that are not, to avoid people wasting their time and resources in investigating them again. While the main users of the app service will be experienced archaeological users and visitors to the Burren who are motivated to record the local heritage, the app and process will be very educational and will probably be used by teachers and students to discover and contribute to their local heritage. For instance, it could complement the

11 Ground truthing is the process of gathering data in the field that either complements or disputes airborne

remote sensing data collected by aerial photography, satellite sidescan radar, or infrared images

(http://www.missiongroundtruth.com/groundtruth.html), see also http://en.wikipedia.org/wiki/Ground_truth 12 Mapped at http://webgis.archaeology.ie/NationalMonuments/FlexViewer/, and which is compliant to

INSPIRE Protected Site Theme – PS v3.2 -

http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PS_v3.0.pd 13 www.heritagecouncil.ie 14 Ground truthing is the process of gathering data in the field that either complements or disputes airborne remote sensing data collected by aerial photography, satellite sidescan radar, or infrared images (http://www.missiongroundtruth.com/groundtruth.html), see also http://en.wikipedia.org/wiki/Ground_truth

http://www.missiongroundtruth.com/groundtruth.html

http://en.wikipedia.org/wiki/Ground_truth

http://webgis.archaeology.ie/NationalMonuments/FlexViewer/

http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PS_v3.0.pd

http://www.heritagecouncil.ie/





courses and practical local environmental work carried out by BurrenBeo Trust15. The Burren is very well observed and recorded over many years, so few new National Monument sites are likely to be found. However other sites, such as Lough Derg and the Slieve Aughtry, which is also in the Mid-West Region of Ireland, is likely to yield many new national monuments. So further sites, beyond the Burren, are likely to be supported by this Application quite early during the WP5 pilot trials. The SDi4Apps enabled App may also help Burren farmers (as well as Irish farmers generally) to determine if their farm might contain a potential National Monument Site (especially field systems) on their land.

User groups/ stakeholders:

1. Public bodies – Heritage Council, National Monuments Service, Irish Government Department of Arts, Heritage and the Gaeltacht.

2. Experts – Field Monuments Advisors & Researchers 3. Enterprises, Companies and SMEs – Farmers. 4. Citizens – visitors and people interested in their local heritage

How and when will the users be involved in the design and development process?

Using the Social Validation methodology and plans defined in D2.2 users have been engaged since very early in the project.

Criteria of success: Usage level & Social Validation of Services that use SDI4Apps

Easy collection of information using smart phones & LOD

Integration of VGI into existing SDIs & LOD

Increased access to harmonised & interoperable GI, L/OD& VGI data

Integrate data from users’, OD, crowd-sourced & social media.



Open INSPIRE4Youth

Ecosystem Services Evaluation

Performance: Standard user acceptable response and latency times for information retrieval of 2 seconds16, to be measured as defined in D3.5 (Technical Test Methodology). The uploading of multiple large high-definition photographs may take longer.

App ID: A1.2.

Notes and issues: The Monuments Ground Truthing App will: 1. Introduce the National Monuments Service, and direct users to browse

open satellite map sources such as GoogleMaps17 and BingMaps18, to find potential archaeological sites in their chosen area (or their current locations if they are already on site). Later on, further Geographic Information sources from the Heritage Council Map Viewer, may also be included.

2. Allow the user to access a LOD database of previous ground truthing observations, and the Heritage Council’s Map Viewer to determine if a

15 http://geojson.org/ 16 “A study on tolerable waiting time: how long are Web users willing to wait?”, Nah, F. Behaviour & Information Technology, 2004, available at http://sighci.org/uploads/published_papers/bit04/BIT_Nah.pdf 17 www.googlemaps.com 18 www.bing.com/maps/


http://www.googlemaps.com/

http://www.bing.com/maps/



chosen site is already recorded by the National Monuments Service as a national monument or has been previously crowd-source reported. If so the user can continue to investigate their chosen area for other potential sites.

3. Support the user on-site to ground truth a potential archaeological site. This will involve using their phone or tablet to take a number of photographs, record notes, note the geo-location using their phone’s GPS, as well as their own identity.

4. The recorded information will be uploaded to a LOD database, that will be mainly CSV with the images and associated maps & GI.

5. Field Monument Advisers, National Monuments Service staff, and other experts (as well as people who may be interested in the app, such as members of the BurrenBeo Volunteers, Institute of Archaeology of Ireland, GeoPark/BFCP Team, etc) will have access to a webservice to authenticate each crowd-sourced ground truthing observation uploaded to the LOD database. They will be able to inform and/or post further queries to the person who uploaded the observations. They will also be able to delete any defamatory, malicious or frivolous observations. All other observations, will then be visible to the general public on a map, showing the protected monuments (via the Heritage Council’s Map Viewer), the crowd-sourced ground truthing observations that are potential national monuments, as well as those that are not (to avoid people wasting their time investigating them again).

6. After suitable further verification by the National Monuments Service (using the SDI4Apps enabled webservice), the validated new monuments will also be recorded in the National Monuments Service’s ESRI ArcGIS Map Viewer system.

Table 2 Easy Data Access pilot Use case 2

2.2 User Engagement and Business Planning

The Easy Data Access pilot is focused on the following services: 1. SDI4Apps enabled European Tourism Indicator System (ETIS) Webservice for the Burren and

European GeoParks Network. 2. SDI4Apps enabled App to Ground-Truth potential Protected Monument sites

2.2.1 Stakeholders and their roles

The pilot addresses all four of the SDI4Apps target groups: Public bodies, Experts, SMEs and Citizens. Their roles in the 2 services are as follows:

Users &

Stakeholders Use Case UC1.1 - ETIS Use Case UC1.2 – Ground Truthing

Public bodies National Parks Wildlife Service (NPWS)

Heritage Council,

National Monuments Service,

Irish Government Department of Arts, Heritage and the Gaeltacht.



Experts Researchers and management in the Burren GeoPark, GeoParks Network.

Field Monuments Advisors and Researchers

SMEs, Enterprises

and Companies

Burren GeoPark

Local Enterprises

Burren Farmers.

Local Enterprises

Citizens Tourists and Visitors to the Burren National Park

All local people.

Tourists and visitors

All People interested in their local heritage

Table 3 Easy Data Access pilot Stakeholders and their roles

2.2.2 Engagement method

Based on the Social Validation approach and plans defined in D2.2 (Social Validation Methodology) users have been engaged from early in the project using Social Validation/Co-design meetings and discussions with the GeoPark stakeholder groups, who have identified the Use Cases providing the most immediate benefit/added value for them.

2.2.3 Incentives for engagement

The GeoPark users and stakeholder groups themselves, identified the Use Cases providing them with the most immediate benefit/added value for the Burren Park. So they are very incentivized to ensure that the Apps and services are provided to meet their needs, so that they can be continued after the project ends.

2.2.4 Timing, planning, indicators

The Apps are currently being implemented and trialled with the stakeholders, and once the SDI4Apps Platform back-end services are available these will become fully operational and rolled-out as defined in task T6.1 to the end of the project in March 2017. So the upcoming technical work in T6.1 will be mainly addressing integration with the SDI4Apps platform backend and the current data models will be transformed to the SDI4Apps models that will be defined in WP5. The two services will be operated and evaluated (in WP6) with both internal and external stakeholders and users. From the Social Validation in D2.2, the criteria of success for this pilot’s services are as follows:

Easy collection of information using smart phones and LOD

Integrate data from users’, OD, crowd-sourced and social media.

Reuse and share tourist information resources, channels and tools

Integration of VGI into existing SDIs and LOD

Increased access to harmonized and interoperable GI, L/ODand VGI data

Usage level and Social Validation of Services that use SDI4Apps

New tourism activities, visitors and jobs, and SME developed services.

SMEs, Students and Researchers developing new Apps and Services Quantified in the following indicators:

Easy Data Access pilot

Scenarios

Success Criteria

Apps/

Svcs in

Operatio

n

No of

App/

Svc

Users

No GI/LOD

datasets in

use

No VGI

datasets

created

Monthly

accesse

s

New

Apps/

Svcs



1. SDI4Apps enabled ETIS Webservice for the Burren & European GeoParks Network.

1 15 10 1 100 1

2. SDI4Apps enabled App to Ground-Truth potential Protected Monument sites

1 10 5 1 50 2

Total for Irish Pilot 2 25 15 2 150 3

Table 4 Easy Data Access pilot Success Indicators

The Easy Data Access pilot will demonstrate achievement of its intended outcomes mainly through Social Validation, which has identified the above criteria and indicators of success according to the different standpoints of the actors represented in each usage scenario, as a framework for evaluating the added value of the services that conform to the standards proposed by SDI4Apps. This activity takes into account the taxonomy of social validation approaches elaborated in D2.2, i.e.:

1. Validation driven by the prospect of user engagement - In this case end-users are not yet directly involved in social validation, but the prospect of user engagement is already influencing institutional behaviour.

2. Validation through direct user interaction with the easy data access process - With the direct participation of (expert/non expert) users in data access.

3. Validation driven by the co-design of innovative “demand pull” services - This is the most user-driven approach, as it actually involves final end-users in the co-design of services (such as ETIS and Ground-Truthing) that use the SDI4Apps platform.

These indicators will be matched with evaluative questions that will be used throughout task T6.1 for the pragmatic assessment of impact generated by the Apps and services enabled by the SDI4Apps platform – and more broadly, on the environmental related activities in which users are involved.

2.2.5 Business plan - market potential

The sustainable operation of the 2 pilot services will be funded and extended by the public agencies involved, with MAC (the SME partner involved) exploiting the specific ETIS and Ground Truthing Use Case opportunities. The context and long term business or the 2 Use cases will be as follows:

1. ETIS Service The Burren, and all GeoParks, need an open common standard to track their progress towards their sustainability objectives in particular, and to benchmark their progress with other sustainable destinations. Currently the ETIS is the only such standard but being an offline Excel file it does not allow for real-time inputs or benchmarking across destinations. The SDI4Apps enabled service will address these as described above. The tangible benefits in the short term for the Burren and other GeoParks will be the ability to define their destination’s indicators and targets by its Local Destination Co-ordinator and Stakeholder Working Group, then track their progress in real-time through crowd-sourcing by the various stakeholders, and provide benchmarking with other destinations (e.g. other GeoParks) through each of the provided views and access to their linked open datasets. As well as the control, extra visitors and profile that this will provide to each GeoPark, this will also demonstrate and validate the ETIS approach for all of Europe. It is anticipated that as each destination’s use of the ETIS matures and the indicator data collected becomes more extensive, the web service will enable comparisons of the destination’s progress against international benchmarks. This will give greater context to the achievements and give destination stakeholders motivation to take further actions to improve results. It will also encourage knowledge sharing between destinations. The intention is not to create competition between destinations, but to recognize that the results generated through the process are core to the decision making plans for each destination. The monetization of these benefits will be expressed in the plans of the Burren and other GeoParks.



2. Heritage Ground-Truthing Service The SDI4Apps platform will enable the provision of an App service to mobilise a very motivated community, by enabling visitors and people interested in their local heritage, to seek out and ground truth potential Monument sites in the Burren and beyond. In the short-term the benefits will be increased special interest tourists visiting the Burren, and other supported sites, and greater awareness of the Irish Protected Monuments sites. For instance, the App may help Burren farmers (as well as Irish farmers generally) to determine if their farm might contain a potential National Monument Site (especially field systems) on their land. In addition, the app and process will be very educational and will probably be used by teachers and students to discover and contribute to their local heritage. For instance, it could complement the courses and practical local environmental work carried out by BurrenBeo Trust19. The crowd-sourced ground truthing observations (both positive and negative) may be included as a permanent Voluntary Geographic Information (VGI) layer on the National Monuments map on the Irish Heritage Council’s Mapping Viewer. This process will also initiate a process for the digital preservation of the VGI data concerning the features that were investigated, both those that are validated to be national monument sites, and those that are not, to avoid people wasting their time and resources in investigating them again. The Burren is very well observed and recorded over many years, so few new National Monument sites are likely to be found during the second iteration of the Irish pilot. However other sites, such as Lough Derg and the Slieve Aughtry, which is also in the Mid-West Region of Ireland, are likely to yield many new national monuments. So further sites, beyond the Burren, are likely to be supported by this Application quite early. These and other ground truthing requirements will provide further exploitation opportunities for MAC (the SME involved) and others.

2.3 Data Acquisition

2.3.1 Datasets

Dataset ID: DS1.1

Resource title: ETIS Dataset

Resource abstract:

The European Tourism Indicator System for the Sustainable Management of Destinations (ETIS) 20 to monitor and measure performance of destinations in Europe

Geographical coverage:

Burren GeoPark initially, but eventually can be scaled to all GeoParks across Europe/

Level of detail: ETIS dataset and manual process, as defined in

http://ec.europa.eu/enterprise/sectors/tourism/sustainable-

tourism/indicators/index_en.htm

Resource locator:

Not yet finalized.

Restrictions/ Licences:

ETIS Dataset license: To be determined later in collaboration with the Burren GeoPark, GeoPark Network and other stakeholders Likely to be Creative Commons Attribution (CC BY) or Attribution Non-Commercial (CC BY-NC)21

Format: Currently Excel offline.

Transformation:

Will be transformed from Excel/CSV to LOD RDF by MAC using the Enablers of the SDI4Apps Platform.

Ready to use: In the process of being published online.

19 www.burrenbeo.com 20 http://ec.europa.eu/enterprise/sectors/tourism/sustainable-tourism/indicators/index_en.htm 21 Creative Commons licenses consist of 4 major condition modules (see http://en.wikipedia.org/wiki/Creative_Commons_licenses



http://www.burrenbeo.com/


http://en.wikipedia.org/wiki/Creative_Commons_licenses



Size: <100kB at present.

Data update: Continuous by crowdsourcing.

Notes and issues

Transformation (Excel/CSV to RDF)

Storage (on SDI4Apps platform)

Search (on SDI4Apps platform, to include further GeoParks (including possibly other pilots) later.

Visualization (for all GeoPark Stakeholders)

Table 5 Easy Data Access pilot data set: European Tourism Indicator System

Dataset ID: DS1.2

Resource title: Potential Monuments Voluntary Geographic Information Dataset.

Resource abstract:

Dataset to record Voluntary Geographic Information (VGI) reports from a motivated community, of visitors and people interested in their local heritage, to seek out and ground truth22 potential Monument sites in the Burren and beyond.


Burren GeoPark initially, but eventually will be scaled to all of Ireland, and subsequently in other European locations.

Level of detail: As defined in the National Monuments Protected Sites Dataset23.

Resource locator:

Not yet finalized.

Restrictions/Licences:

Dataset license: To be determined in discussions with the Heritage Council,

and National Monuments Service. Likely to be Creative Commons Attribution

Non-Commercial No Derivatives (CC BY-NC-ND)24

Format: CSV with GI elements in ESRI Shapefile format. The National Monuments Parent dataset is compliant to INSPIRE Protected Site Theme – PS v3.225

Transformation: Various to RDF

Ready to use: In process of being published.

Size: To be determined in discussions with the Heritage Council and National

Monuments Service.

22 Ground truthing is the process of gather data in the field that either complements or disputes airborne remote sensing data collected by aerial photography, satellite sidescan radar, or infrared images (http://www.missiongroundtruth.com/groundtruth.html), see also http://en.wikipedia.org/wiki/Ground_truth 23 INSPIRE View Service (need to register to use) https://www.geoportal.ie/geoportal/catalog/search/resource/details.page?uuid={F6DE3EBB-FC5C-4D79-A00A-BC45AB9F55F6} INSPIRE “Predefined” download service https://www.geoportal.ie/geoportal/catalog/search/resource/details.page?uuid={F6DE3EBB-FC5C-4D79-A00A-BC45AB9F55F6} 24 Creative Commons licenses consist of 4 major condition modules (see http://en.wikipedia.org/wiki/Creative_Commons_licenses) 25 Define in http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PS_v3.0.pdf



https://www.geoportal.ie/geoportal/catalog/search/resource/details.page?uuid=%7bF6DE3EBB-FC5C-4D79-A00A-BC45AB9F55F6%7d




http://en.wikipedia.org/wiki/Creative_Commons_licenses

http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PS_v3.0.pdf



Data update: Continuous by VGI/Crowdsourcing.

Notes and issues Datasets will link the datasets provided by the Heritage Council Heritage

Maps that allow users to look at a wide range of heritage data sets on a

map26. Many of these data sets were collected by government departments

but many others have been collected by local authorities through the County

Heritage Plans. Coverage of some data sets is on an individual county basis,

rather than as a national coverage27, and some of the content, such as the

content of points of interest on maps, is not always consistent.

An INSPIRE compliant schema, “Protected Sites Data Specification”28, has been developed and implemented for the Irish National dataset of protected sites using the Geographic Markup Language (GML – Simple Features Profile) by the Irish Government Department of Arts, Heritage and Gaeltacht. They have already transformed a similar dataset of Irish place names to be LOD29, so they are interested to see if a similar transformation can be undertaken on the protected monuments using the INSPIRE Registry for persistent URIs30. The SDI4Apps platform may be used to publish that as LOD to ensure maximum reuse of its contents.

Table 6 Easy Data Access pilot data set: Potential Monuments Voluntary Geographic Information Dataset

2.3.2 Data Models

In line with the SDI4Apps iterative approach to user validation (as defined in D2.2), initial implementations

of the Easy Data Access pilot has further determined the requirements with users and an evolutionary

implementation of the following services in the Easy Data Access pilot to involve Burren citizens and

stakeholders:

1. SDI4Apps enabled European Tourism Indicator System (ETIS) Phone Apps for the Burren and

European GeoParks Network.

2. SDI4Apps enabled App to Ground-Truth potential Protected Monument sites

ETIS App

The Tourism for Conservation data model was developed based on the ETIS dataset31 to be as follows:

26 www.heritagecouncil.ie 27 http://heritagemaps.biodiversityireland.ie/#/Map 28 Defined in http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PS_v3.0.pdf 29 www.logainm.ie/en/ 30 http://inspire.ec.europa.eu/registry/ 31 Defined as an Excel Spreadsheet dataset and PDF Guide at http://bookshop.europa.eu/en/the-european-tourism-indicator-system-pbNB3213182/

http://www.heritagecouncil.ie/

http://heritagemaps.biodiversityireland.ie/#/Map

http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PS_v3.0.pdf

http://www.logainm.ie/en/

http://inspire.ec.europa.eu/registry/





Figure 2 ETIS data model



Ground Truthing App

The Ground-Truthing Heritage service data model uses the model of the Irish National Monuments dataset

to which it will need to seamlessly interact. This is compliant to the INSPIRE Protected Sites Data Model32

and Simple Applications Schema33, as follows:

Figure 3 Ground-Truthing PS data Model

32 http://inspire.ec.europa.eu/data-model/approved/r4618-ir/html/ 33 http://inspire.ec.europa.eu/applicationschema/ps

http://inspire.ec.europa.eu/data-model/approved/r4618-ir/html/

http://inspire.ec.europa.eu/applicationschema/ps



Figure 4 Ground-Truthing PS Simple Application Schema

2.4 Apps and Services

The initial iterations of the Easy Data Access Pilot Apps focused on developing the services’ user interfaces

and front-ends, by developing the two use cases as hybrid asynchronous apps written in open source



AngularJS34, using the open source IONIC HTML5 native app development framework35 compiled to native

code for the various mobile platforms (Android, IOS, Windows) using the open source Apache CORDOVA

plugins36. This framework approach decouples the client application from the backend SDI4Apps

architecture. By using angular JS it allows a common framework for both mobile development and web

portal clients.

2.4.1 European Tourism Indicator System User Apps

Application ID: A1.1

Name of the app: GeoPark ETIS Browser/App on PCs, Tablets and Smartphones to access the Webservice.

Application description: As described in UC1.1

Supported functionality /

capabilities:

As described in UC1.1

Related services: S1.1, S1.2, S1.3, S1.4, S1.5

Datasets required DS1.1

Timeplan for the development: Will be operational by the end of June 2015, and then continuously improved throughout the remainder of task T6.1 to the end of the project in March 2017

Responsibility for the development: Ed Keane, MAC. [email protected]

Detailed description of planned or

already carried out testing:

In process of being co-developed with the stakeholders. Will require SDI4Apps Platform for full functionality and user testing.

Role of the user: Will use the use App as described in UC1.1

Role of the administrator: Will use the use App as described in UC1.1

Offline use: Yes Apps can be used offline for data input, but not for data access.

Who will be responsible for the

application management?

MAC

Notes and issues Graphical user interface – Standard HTML5 browser.

Viewing the Burren ETIS dataset as progress charts,

and associated GI images.

Table 7 Easy Data Access pilot European Tourism Indicator System user Apps

34 https://angularjs.org/ 35 http://ionicframework.com/ 36 http://cordova.apache.org/

mailto:[email protected]

https://angularjs.org/

http://ionicframework.com/

http://cordova.apache.org/



The following are some current screens from the ETIS App:

Figure 5 ETIS App Screens

2.4.2 Potential Monuments Ground Truthing App


Name of the app: Potential Monuments Ground Truthing Application

Application description: As described in UC1.2


capabilities:

As described in UC1.2

Related services: S1.1, S1.2, S1.3, S1.4, S1.5

Datasets required DS1.2.

Timeplan for the development: Will be operational by end of July 2015, and then continuously improved throughout the remainder of task T6.1 to the end of the project in March 2017

Responsibility for the development: Ed Keane, MAC. [email protected]



In process of being co-developed with the stakeholders. Will require SDI4Apps Platform for full functionality and user testing.

Role of the user: Will use the use App as described in UC1.2

Role of the administrator: Will use the use App as described in UC1.2

Offline use: Yes, App can be used offline for data input, but not for data access.



MAC

mailto:[email protected]



Notes and issues Graphical user interface – Standard HTML5 browser.

Implementing the National Monuments VGI Ground-

Truthing process as indicated above for individual

users.

Viewing, searching, editing for the Heritage Council and National Monuments Service staff.

Table 8 Easy Data Access pilot Potential Monument Ground Truthing App

2.4.3 Services

As reported in D2.2 the services from the SDI4Apps infrastructure point of view that will be necessary for

the above mentioned apps, are as follows:

• Advanced visualisations

• Advanced Visualisation framework & API (of GI & non-GI components)

• Data harmonisation

• Scalable GI to LOD transformation & harmonisation service, from many heterogeneous

database sources, including HALE support.

• Integration of mobile apps

• Scalable crowdsourced/VGI real-time data collection with Open API.

• Interoperability between local & global geospatial models.

• Scalable Geo‐focused Crawler for automatic collection of OGC services endpoints

representing spatial content available via the deep web.

• Linked Open Data

• Scalable INSPIRE GI schema to LOD transformation & harmonisation service, with persistent

URIs.

• Scalable RDF Triple Storage service for LD (such as Virtuoso)

• Semantic indexing infrastructure to transform GI to LOD

• Scalable MapServer (or GeoServer) implementation

These map to the SDI4Apps Enablers defined in D3.1, D3.2.1 and D3.5, as follows

Services required from the SDI4Apps

Infrastructure

SDI4Apps Enablers that will be provided (defined

in D3.1, D3.2.1, D3.5)

1. Advanced Visualisation framework & API

(of GI & non-GI components) & mobile tools

2. HSLayers visualisation tools

3. HSLayers NG visualisation tools

2. Scalable GI to LOD transformation &

harmonisation service, from many

heterogeneous database sources, including

HALE support.

11.Scalable INSPIRE GI schema to LOD

transformation & harmonisation service,

with persistent URIs.

13.Semantic indexing infrastructure to

transform GI to LOD

Sesame/D2RQ/Postgres-XL-PostGIS.



3. Validation & integration tools 1. Cloud Platform - IaaS cloud operated by CERIT-SC,

based on the OpenNebula cloud management

system, KVM & Xen hypervisors, disk images with

preinstalled Debian Linux operating system, Perun

account management system, & powerful hardware

machines.

5. Scalable crowdsourced/VGI real-time data

collection with Open API.

4. Postgres-XL clustered database with PostGIS

extension, nginx web server with MapProxy caching,

HAProxy load-balancer, & Apache.

6. Scalable Geo‐focused Crawler for

automatic collection of OGC services

endpoints representing spatial content

available via the deep web.

5. Micka metadata catalogue management system,

supporting discovery of existing geospatial data &

services

12.Scalable RDF Triple Storage service for LD 6. Sesame triple store framework & D2RQ Platform.

7. Virtuoso

15.Scalable GeoServer implementation 8. MapServer Web Map Service

9. Geoserver

Table 9 Easy Data Access pilot Enablers

The tables for each of these services are as follows:

Service ID: S1.1

Name of the service: Advanced Visualisations

Service description: As defined in the WP3 and WP4.


capabilities:

Advanced Visualisation framework & API (of GI & non-GI

components)

Related apps: A1.1, A1.2

Timeplan for the development: As defined in the WP3 and WP4.

Responsibility for the development: As defined in the WP3 and WP4.



As defined in the WP3 and WP4.

Service run by the SDI4Apps

platform?

Yes

Notes and issues Will use the HSLayers and HSLayers NG SDi4Apps Enablers.

Table 10 Easy Data Access pilot service: Advanced Visualisations



Service ID: S1.2

Name of the service: Data Harmonisation



capabilities:

Scalable GI to LOD transformation and harmonisation service, from many heterogeneous database sources, including HALE support.








platform?

Yes

Notes and issues Will use the Sesame/D2RQ/Postgres-XL-PostGIS SDi4Apps Enablers as tabulated above.

Table 11 Easy Data Access pilot service: Data Harmonisation

Service ID: S1.3

Name of the service: Integration of Mobile Apps.



capabilities:

Scalable crowdsourced/VGI real-time data collection with Open API








platform?

Yes

Notes and issues Will use the SDi4Apps Enabler providing Postgres-XL clustered database with PostGIS extension, nginx web



server with MapProxy caching, HAProxy load-balancer, & Apache..

Table 12 Easy Data Access pilot service: Integration of mobile Apps

Service ID: S1.4

Name of the service: Interoperability between local & global geospatial models.



capabilities:

Scalable Geo‐focused Crawler for automatic collection of OGC services endpoints representing spatial content available via the deep web.



Responsibility for the development: Who is responsible for the development?





platform?

Yes

Notes and issues Will use the SDi4Apps Enabler providing Micka metadata catalogue management system, supporting discovery of existing geospatial data and services.

Table 13 Easy Data Access pilot service: Interoperability between local & global geospatial models

Service ID: S1.5

Name of the service: Linked Open Data



capabilities:

Scalable INSPIRE GI schema to LOD transformation &

harmonisation service, with persistent URIs.

Scalable RDF Triple Storage service for LD (such as

Virtuoso)

Semantic indexing infrastructure to transform GI to

LOD

Scalable MapServer and GeoServer implementation










platform?

Yes

Notes and issues Will use the following SDi4Apps Enablers:

Geoserver

MapServer Web Map Service

Sesame triple store framework & D2RQ Platform.

Sesame/D2RQ/Postgres-XL-PostGIS

Virtuoso

Table 14 Easy Data Access pilot service: Linked Open Data

2.4.4 Cloud properties

The following table provides information for deployment of the Easy Access Pilot Services to cloud

infrastructures, both CERIT-SC’s and commercial.

Cloud Property Easy Data Access Pilots Requirements

Operating system preferred for deployment

of server-side services, and why?

Linux, as it is open, stable and ubiquitous.

Can Ubuntu Linux 14.04 LTS be used as the

operating system?

Any objections against using it as the default

operating system for deployment?

Yes, Ubuntu Linux 14.04 LTS can be used as the

default operating system for deployment.

Requirements for data storage space in

gigabytes.

The Easy Data Access pilot is not data intensive,

but it includes images, maps and other objects

such as videos and audio files, so requirements are

likely to be under 10GB initially, and through

VGI/crowdsourcing grow perhaps to 20GB by the

end of the project.

Need for scalability of the application

regarding the amount of stored data, the

amount of data processing, the number of

concurrent users, or anything else?

(Scalability requirements make application

design and development more complex and

thus costly, but prepare the application for

future success.)

The Easy Access Pilot Use Cases’ initial scalability

requirements will be minimal.

However, as usage grows they will require the

inherent static and dynamic scalability of the

Cloud platform, as their VGI/crowdsourcing will

lead to increasing content and is likely to be

bursty as each targeted user group will tend to

input content at similar times.

Table 15 Easy Data Access pilot Cloud Property requirements



3 OPEN SMART TOURIST DATA – PILOT 2

The rapid growth of tourism and the tourist industry in the 20th century is related to changes in social structure of society and rights of labours. They contributed to the introduction (in developed countries) of weekends, eight-hour working day and holidays that strongly support tourism activities. Active tourism (contrary to passive tourism) is a special way to spend leisure time. It is a new life philosophy that combines adventure, sports, experience, discovering, events, and relations to nature, history, culture, habits or traditions. Active tourism is rapidly growing in popularity due to an unusual experience that are totally different from the typical in sea resorts. Elements of active tourism (such as excursions or offer of sport activities) are added to the traditional form of tourism. The new forms of tourism cover for example sport activities (e.g. rafting), nature tourism (e.g. trekking or hiking), rural tourism, congress tourism, adventure tourism (e.g. rock climbing) or experience tourism (e.g. mountaineering expeditions).

Another shift of paradigm of the tourist industry is in connection with collecting, sharing, spreading and propagation of information. Previous forms (personal recommendations, printed catalogues, reservation letters or phone calls) are in remission and they are replaced by electronic forms. But electronic forms are also changing. They are moving from centralized databases and big global providers to more personalized information created by local subjects of tourist industry. The main objective of this project is to support these local or regional subjects and their information management, because we believe that the combination of local and global information and systems represents the best added value for all participants of the tourist industry.

The Open Smart Tourist Data pilots will support related business subjects such as easy integration of the SDI4Apps platform into proprietary solutions (thanks to the implementation of standards), reusing and sharing of existing information resources, channels and tools. Open Smart Tourist Data will integrate users’ data, free and open global data, SDI4Apps Team’s data, crowdsourced data and social media

Data and information represents keywords of current society as well as contemporary tourism and the tourist industry. Both are major subjects of the tourist industry (participants and providers) that deal with data and information and need them mainly for communication within each group and also between both groups of tourism subjects. Data and information involve a huge number of varied items related to selection of destination or offer of services of the tourist industry. Data and information do not mean just spatial data sets, maps, web cameras, hand-outs or catalogues, but also personal information such as recommendations, comments on social media channels, published private photos or stories.

Existing solutions for the tourist industry based on information technologies (IT) are focused mainly on one component of information such as global information, local or regional data or social media and crowd-sourcing. The main problem of this approach is that various types of information are collected and managed at different levels. For example, it is possible to have a central database of roads on the European level, but it is not possible to maintain up-to-date uniform information about accommodation, services, events, etc.

On the other hand, there are local systems, which are collecting this information. These systems usually cover small regions or groups of service providers with up-to-date data, but the problem of such local information systems is their heterogeneity and usability. All users (including SMEs participating on the tourist industry and being not focused on information technologies) or such data and information are limited by their heterogeneities that cover various data models, data formats, types of information, level of detail, semantics (terminology), portrayal rules, geometry, coordinates and coordinate systems and above all the updating frequency. Travellers have their own requirements. They want to find interesting, attractive and credible information simply and fast without any difficulties.

The Smart Tourist Data will cover five different use cases:

Linked Open Data for tourism,

Crowdsourced data for tourism,

Cycle tourism,

Promotion of regions,

Advertisement of travel agencies focused on active tourism.



3.1 Use Cases

Use case ID: UC2.1

Use case name: SDI4Apps Point of Interest

Abstract: According Andrae et al. (2001) “POI provide an

essential data source for a wide range of

location-based applications. Having emerged

from in-car navigation systems the classic POI

are often linked to an address and relate to

businesses such as petrol stations, garages,

shopping centres, or common sense

information, such as the church, police station

or hospital in a city.”

The use case 2.1 deals with se POIs related to

cycling and biking tourism to provide relevant

information focused on a concrete situation.

POIs will be provided through a map portal. As

the data resource the RDF knowledge base will

be used. The original data will be collected

from OpenStreetMap, other POI resources and

from SDI4apps partners (UWB, Uhlava).

Description (all the steps that will be done by

the user):

In the application for cycling tourism a user will

be able to switch over layers representing

particular categories of POIs or click on a

button expressing concrete situation (for

example “I’m looking for accommodation.” or

“I’m hungry.”). These button will present pre-

defined set (compositions) of POIs.

User groups/stakeholders: Tourists

Citizens

Business providers

How and when will the users be involved in the

design and development process?

Data will be collected from VGI data

resource.

Application will enable to get a

feedback to authors.

In a later version users will be able to

add new POI as well as promote their

activities on the social media.

Criteria of success: Positive feedback

Interoperation with other SDI4Apps pilots: INSPIRE4Youth



Performance: The speed of uploading POI from a database

has to correspond with requirements on real-

time application.

App ID A 2.1

Notes and Issues

Table 16 Open Smart Tourist Data pilot Use case 1

Use case ID: UC2.2

Use case name: Crowdsources data for tourism

Abstract: The tourist will be have possibility to collect

their own data and manage this data as their

private or making this data publicly available

ant trough this contribute to the building of

database of PoI and tracks (cycling, hiking,

etc.). There will be developed APPS, which will

support collection of PoI only and also provide

track monitoring and collection of information

about tracks (cycle, hiking, ect.). User will

have possibility to make this data available for

selected groups of users or make this data

publicly available. Application should support

online and offline work.


the user):

The users will use Apps developed by SDI4Apps

for data collection and monitoring with

possibilities to make their data available for

certain group of users or making data openly

available. Restricted services will be limited,

there will be limited amount of storage

capacity, then it will be necessary to pay small

fee for additional space. Open data will be free

and will be reused of improvement of SDI4Apps

databases. After starting Apps user will have

next possibilities:

Registration and signing to application

Manage his friends groups (add or

remove persons, who will have access

to his/her personal data)

Manage his/her account for his private

space and potential access to

commercial data and services



Select maps, which will be available as

background maps for his/her traveling

from open maps, their own data, data

of his/her friends and eventually

commercial data

Data collection, which will have next functions:

User will decide, if data will be

publicly available or available only for

group of his/her friends

User could decide, if he will use

tracking mode, when all his tracking

will be monitored and select, which

mean will be used. If he will decide,

all movement will be recorded

User will collect different point of

interest with possibilities to use types

of PoI, publish description, publish

photos or videos.

User will store information. If he will

be online, information will be stored

automatically, if not, all information

will be stored, when he/she will

connect internet

User groups/stakeholders: Tourists

Citizens



Initial brainstorming will be provided with

selected group of users.

Application will be available during the

project. The user will be able to use

developer’s blog to make comments and

communicate with developers and contribute

to development. Advanced and relay interested

users will have access to Redmine to have

possibilities commented bugs and define new

features.

Criteria of success: Usage level & Social Validation of

Services that use SDI4Apps

Easy collection of information using

smart phones & LOD

Integration of VGI into existing SDIs &

LOD

Increased access to harmonised &

interoperable GI, L/OD & VGI data



Integrate data from users’, OD, crowd-

sourced & social media.

Reuse & share tourist information

resources, channels & tools

SMEs, Students & Researchers

developing new Apps

New tourism activities, visitors & jobs,

and SME developed services.

Interoperation with other SDI4Apps pilots: Easy Data Access

INSPIRE4Youth

Performance: Standard user acceptable response and latency

times for information retrieval of 2 seconds, to

be measured as defined in D3.5 (Technical Test

Methodology).

App ID A 2.2

Notes and Issues The use case will reuse data from first use case

as reference data.


Use case ID: UC2.3

Use case name: Cyclo tourism- routing

Abstract: Development of routing application taking into

consideration needs of cyclo tourism (from

example selection of specific type of way). The

application will deal with data from

OpenStreetMap and specific data file (such as

forest roads from FMI).


the user):

User connects to the application

(authorization procedure will be

solved)

User switch on appropriate road layers

User input starting and ending points of

the trip (if available also trasit points)

or the system recommend a suitable

route

User will use the application online or

will be able to export founded track to

any format for offline use.



User groups/stakeholders: Tourist

Business providers



Data will be collected from VGI data resource.

Application will enable to get a feedback to

authors.

In a later version users will be able to add new

POI as well as promote their activities on the

social media.

Criteria of success: Positive feedback

Interoperation with other SDI4Apps pilots: INSPIRE4Youth

Performance The speed of uploading POI from a database

has to correspond with requirements on real-

time application.

App ID A 2.1

Notes and Issues


Use case ID: UC2.4

Use case name: Promotion of regions

Abstract: The Promotion of region will be allow to

regions publish different tourist related data

about their regions (PoI, roads, biking, hiking,

etc. on SDI4Apps portal) using principles of PoI

and also Cycle tourism.

The Use case will also allow to display data

from Smart Tourist Data on their portal using

Embedded functionality and Open API.

The end users will have next possibilities:

Uploaded their existing data on the

server (PoI), treks

Integrate this data with existing data

sets. This functionality will be usually

outsourced to the external experts or

people. This service could be offered

ass commercial services

Integrated Smart Tourist Data into

regional or local web pages as

embedded objects with possibilities



to manage this data trough external

API. This could be paid service


the user):

The end users will have next possibilities:

Uploaded their existing data on the

server (PoI), treks

Integrate this data with existing data

sets. This functionality will be usually

outsourced to the external experts or

people. This service could be offered

as commercial services

Integrated Smart Tourist Data into

regional or local web pages as

embedded objects with possibilities

to manage this data trough external

API. This could be paid service

User groups/stakeholders: Public bodies



The development will be realised in

incremental manner, users will have

possibilities to provide bug tracking using Red

mine and also suggest new features

Criteria of success: Usage level & Social Validation of Services that

use SDI4Apps


smart phones & LOD


LOD



Integrate data from users’, OD,

crowd-sourced & social media.



New tourism activities, visitors &

jobs, and SME developed services.


INSPIRE4Youth

Performance For visualisation standard user acceptable

response and latency times for information

retrieval of 2 seconds, to be measured as

defined in D3.5 (Technical Test Methodology).

App ID A 2.3



Notes and Issues The use case will use results of previous use

cases.


Use case ID: UC2.5

Use case name: Advertisement of travel agencies focused on

active tourism

Abstract: The pilot will offer to travel agencies and

organisation with focus on active tourisms

promote their products (trips, etc}. Information

will be like interactive map catalogue, where

will be possible to see information about trips,

location, PoI, photos and others. Database will

be combined with data from previous

scenarios.

There will be also possible offer

accommodation and other services (horse

riding, farm products, etc).


the user):

The provider of service will have possibility to

publish information about his product trips etc

including geologised photos tracks, ets with

types of trips.

User groups/stakeholders: Travel agencies,

Providers of tourist services

Tourists



The development will be realised in

incremental manner, users will have

possibilities to provide bug tracking using Red

mine and also suggest new features.

Criteria of success: Usage level & Social Validation of Services that

use SDI4Apps


smart phones & LOD


LOD



Integrate data from users’, OD,

crowd-sourced & social media.





New tourism activities, visitors &

jobs, and SME developed services.


App ID A 2.3

Notes and Issues


3.2 User engagement and business planning

Open Smart Tourist Data pilot is focused on cycling and biking tourism and active form of tourism and adventure tourism. It provides relevant data resources following international standards and existing data set developed by open communities, regions and independent projects. The authors of these data sets represent the first group of stakeholders, which can influence the results of pilot. The second group consist of developers creating applications used data from SDI4apps project. In pursuance of the pilot the application for tourism will be developed as well. Third group of users will be travel agencies, regions and municipalities, which will use these applications for promoting their tourism attracts. The solution will allow running applications from their pages. This group will in future generate main incomes from advertisements and services related to them. Users of this application represents the third type of stakeholders.

It is expected, that the data sets and applications will be available during September 2015 for pilots, to be available for ISAF and Bratislava Hackathon, to attract external developers. During October, September will be available tools for crowdsourcing, which will be officially launched in November (VZP, ZPR and Uhlava). The first demonstration application for travel agencies will be prepared till February 2016. We already detect two travel agencies, for which we will prepare demo applications. This two demo applications will be prepared free of charge.


3.3.1 Datasets

Dataset ID: DS2.1

Resource title: SDI4Apps POIs

Resource abstract: POI data (related to cycling) integrated from heterogeneous resources (OpenStreetMaps, data from Local Action Group Posumavi, experimental ontologies from UWB, etc.).


Europe

Level of detail: Data corresponds to particular POI from national parks or ski resorts to buildings

or sights.

Resource locator: http://ha.isaf2014.info:8890/sparql


To be solved based on restriction of particular resources.



Format: RDF

Transformation: Harmonization processes from original resources include above all re-classification and transformation to the new data model.

Ready to use: Yes, but data will be added during the project.

Size: Contemporary version (June 2015) has 1.8 GB (as RDF file). It contains 3 291 295 POIs.

Data update: Based on updating of source data and adding new data.

Notes and issues

Table 21 Open Smart Tourist Data pilot data set: SDI4Apps POIs

Dataset ID: DS2.2

Resource title: Joint Road Data

Resource abstract: Road network data based on OpenStreetMap and other resources, which will be managed and used in SDI4apps project as well as in other project (Foodie, Open Transport Network) to reduce redundancy and make management much more easier.


Europe

Level of detail: Data corresponds to particular road of all level, including cycle routes and tracks.

Resource locator: tbd


To be solved based on restriction of particular resources.

Format: RDBMS

Transformation: Harmonization processes from original resources include above all re-classification and transformation to the new data model.

Ready to use: Yes, but data will be added during the project.

Size: 45 GB

Data update: Based on updating of source data and adding new data.

Notes and issues

Table 22 Open Smart Tourist Data pilot data set: Joint Road Data

3.3.2 Data Models

INSPIRE specifications do not deal with POIs, therefore the new data model based on Points of Interest Core (W3C Editor's Draft published in 2012) was created.

The data model of POI is composed of seven parts:

Identification – each POI is identified by a unique ID expressed as a URI.

Description – each POI is described by a label (name). In several cases, there are more labels differentiated by the xml:lang attribute and/or a text description.

Geometry – each POI is localized by two coordinates (WGS 84) expressed according to the W3C Basic Geo (WGS84 lat/long) Vocabulary.

Classification – categorization is realized through three various parameters – classification based on GPS-based geographical navigation Waze, which is primary, mandatory and used for visualization; and two types of classification used in OpenStreetMap.

Contact information – several POIs contain some contact information such as address, e-mail, homepage, fax or phone number.



Tourist information – currently there are only two types of tourist information (opening hours and access). This information is available for data from Posumavi.

Links – several objects include one or more of three types of links to external data – links to external non-linked data resources such as Wikipedia, Wolfram|Alpha or raster maps, links to an equivalent object in DBpedia or GeoNames.org, links to countries (in DBpedia and GeoNames.org) containing the POI. The last two links are mandatory for every POI.

Roads data model:

Figure 6 Open Smart Tourist Data Roads data model




3.4.1 User Apps


Name of the app: Open Smart Tourist Data Application

Application description: Application will provide useful information for cyclotourism in the form of routes and POIs. The application will enable searching of routes based on parameters (for example type of road) and switching among POI categories.


capabilities:

Routing Functions of traditional map portal (zooming, panning, layer switching)

Related services:

Datasets required DS2.1, DS2.2

Timeplan for the development: The application will be developed according to spontaneous and incremental Living Lab approach which require flexibility and continual communication with users.

Responsibility for the development: Ota Cerba (UWB), Dmitrij Kozuch (HSRS), Karel Charvat (CCSS)



See time plan for development.

Role of the user: User Feedback provider

Role of the administrator: Administrator Manager

Offline use: Yes



Administrator

Notes and issues

Table 23 Smart Open Tourist Data user App 1


Name of the app: Open Smart Tourist Crowdsourcing



Application description: Mobile application will support automatic tracking of roads and collection of POI.


capabilities:

Automatic tracking

Mobile displaying maps

Collection of PoI including photos

Related services:


Timeplan for the development: The application will be developed according to spontaneous and incremental Living Lab approach which require flexibility and continual communication with users.

Responsibility for the development: Premysl Vohnout (BOSC)






Offline use: Yes



Administrator

Notes and issues



Name of the app: Open Smart Advertisement

Application description: Application will allows to be embedded into Web pages of Travel Agencies, regional Agencies etc.


capabilities:

Embed

Open API

Routing

Functions of traditional map portal (zooming, panning, layer switching)

Related services:


Timeplan for the development: The application will be developed according to



spontaneous and incremental Living Lab approach which require flexibility and continual communication with users.

Responsibility for the development: Karel Charvat (CCSS)






Offline use: Yes



Administrator

Notes and issues


3.4.2 Services

Service ID: S2.1

Name of the service: Relational database

Service description: A relational database storing and providing spatial data and enabling SQL queries.


capabilities:

See above

Interconnection to map client

Related apps: A2.1

Timeplan for the development: The service is developed only an implementation is necessary. It will realized to the end of 2015.

Responsibility for the development: HSRS



There is implemented and tested MySQL database with selected datasets.


platform?

Yes

Notes and issues

Table 26 Open Smart Tourist Data pilot service: Relational database



Service ID: S2.2

Name of the service: No-SQL database

Service description: A no-SQL database storing and providing RDF triples and enabling SPARQL queries.


capabilities:

See above Interconnection to map client

Related apps: A2.1





There is implemented and tested Virtuoso database with selected datasets (POI knowledge base).


platform?

Yes

Notes and issues

Table 27 Open Smart Tourist Data pilot service: No-SQL database

Service ID: S2.3

Name of the service: Map portal

Service description: A service providing function of traditional map portal (zooming, panning, layer switching).


capabilities:

See above Possibility of combination of RDF data and spatial data.

Related apps: A2.1





The first version of map services is available and tested.


platform?

Yes



Notes and issues

Table 28 Open Smart Tourist Data pilot service: No-SQL database


Cloud Property Open Smart Tourist Data Pilots Requirements



Deployed, configured and tested on Debian Linux

operating system, but can run on any Linux Distro,

or Windows machine, platform independent


operating system?



Yes


gigabytes.

2 TB








future success.)

GeoServer open source used as a domain specific

enabler serving Web GIS server functionalities. It’s

scalability would be very valuable to be tested,

especially for a cloud approach used to establish

SDI node(s) comprising in a set of nodes with an

average computer resources (2GB of RAM, 2*CPU).

In such a configuration a clustered GeoServer

solution may improve the overall performance of

an SDI node significantly.

Maplog

HSLayers NG

Virtuoso

Postgres

Table 29 Smart Open Tourist Data pilot Cloud Property requirements



4 OPEN SENSOR NETWORK - PILOT 3

4.1 Use Cases

Agriculture requires the collection, storage, sharing and analysis of large quantities of spatially referenced data. For this data to be effectively used, it must be transferred between different hardware, software and organisations. These data flows currently present a hurdle to uptake of precision agriculture as the multitude of data models, formats, interfaces and reference systems in use result in incompatibilities. Management of huge amounts of data is a challenge. Spatio-temporal data is increasingly collected by remote or in-situ sensors rather than by field campaigns. The wireless communications have several benefits, but also pose challenges to the data exchange reliability and power supply. Sensor calibration and deployment as well as maintenance of sensors need resources and technical skills and increase the costs of data acquisition. Both increasing the amount of data and awareness of data quality issues highlight importance that metadata are attached to sensor data.

Use case ID: UC3.1

Use case name: OpenSensorNetwork data management

Abstract: The Open Sensor Network scenario will collect

and monitor data from in-field sensors. The

basic approach will be for web services to send

various sensors’ proprietary protocols to a

common database that is accessible with open

protocols. The scenario will be then extended

to use the SDI4Apps cloud based tools to

process/aggregate the data directly from the

sensors on the fly in real-time. In all cases the

end users will be able to monitor the ongoing

situation using their PCs, tablets or

Smartphones.


the user):

There will be next steps supported by system:

Registration of sensors uri (every single

sensor or WSN has to be registered) in

catalogue describing sensors,

measurement parameters, time period,

uri and protocol for accessing data

Discovery sensors in geographical

context, time period and also in

parameters for measurement

Accessing data from different sensor

through one interoperable protocol

User groups/stakeholders: Public bodies – National and Regional

Authorities providing meteorological

information.

Farmers – owners of sensors



Experts – Agricultural and environmental.

Enterprises, Companies and SMEs – particularly

farmers, growers, and agro-supply companies.



The users are involved on level of user

requirements and on level of testing.

Criteria of success: User satisfaction, easy access to data from

different providers


Performance: The solution will require large parallel access

to big data. Data stored on server will be

generated from different places. For some

data, solution will provide only brokerage,

transforming data into one format.

App ID A 3.1

Notes and Issues

Table 30 Open Sensor network pilot Use case 1

Use case ID: UC3.2

Use case name: OpenSensorNetwork Early Warning

Abstract: The use case will be focused on prediction of

critical situation like radiation frost or similar

events and sends early warning to farmers


the user):


Receiving early warning from WSN

Promptly delivering warning to farmer

Visualising data from sensors

measurement.



information.








requirements and on level of testing. There



also will be reused experiences from already

running systems.


different providers







App ID A 3.2

Notes and Issues


Use case ID: UC3.3

Use case name: OpenSensorNetwork Ground Water Monitoring

Abstract: The Ground water Scenario will allow to

provide monitoring of groundwater level and

display measurement and interactive maps

demonstrating development.


the user):


See measurements from sensors

See spatio-temporal maps derived from

groundwater measurement.



information.








requirements and on level of testing.


different providers









App ID A 3.3

Notes and Issues



The Pilot will connect two basic groups of users: On one side it will be data producers, this mean sensors owners or producers, who will

registere their sensors in system catalogue together with all necessary parameters and protocols for accessing of sensors.

Measurement users, who will have two possibilities of access to sensors measurement on the base of their selection through interoperable protocols or use SDI4Apps Apps. This second groups will be farmers, scientist, service organisations, advisors and public servant

Till now the main problem is interoperability. An important task for this is to define two issues: Catalogue for describing and cataloguing of sensors, till now none of commonly used

catalogue is suitable for this purposes Protocols for accessing sensors from different repositories of different providers, the problem

is, that most form data is offered through proprietary protocols We expected next time plan:

End of September 2015 to finalise selection and implementation of sensor catalogue Architecture for accessing data is already prepared, we expect to use three different protocols

based on OGC SWE, FI protocols and own GeoJSON based protocol. So the implementation of tools will be prepared till end of October 2015

Development of Apps till February 2016 The business will be mainly generated through Apps for final users and also for additional services and consultancy for other stakeholders, APPs development, sensors providers and service providers. Part of services will be also related to development of new customer oriented Apps


4.3.1 Datasets

Dataset ID: DS3.1

Resource title: Senslog Catalogue

Resource abstract:

The catalogue will manage information about different sensors coming from different providers


World Wide



Level of detail:

Resource locator:

Till now not fixed.


Common Creative

Format: TBD

Transformation:

Ready to use: From October 2015

Size: 500 GB

Data update: Daily

Notes and issues

Table 33 Open Sensor Network pilot data set: Senslog Catalogue

Dataset ID: DS3.2

Resource title: Senslog Database

Resource abstract:

Will store data from sensor measurement and also to this database will be provided harvesting of measurements for sensors, which will be not accessible through Interoperable protocols.


World Wide

Level of detail:

Resource locator:

Till now not fixed.


Common Creative

Format: REST API, OGC SOS, NGSI 9/10

Transformation:

Between different protocols

Ready to use: From January 2016

Size: >2 Terabytes

Data update: Continuously

Notes and issues

Table 34 Open Sensor Network pilot data set: Senslog Database

4.3.2 Data Models

The data model for data storage and access was prepared and agreed with other projects (FOODIE, OTN). It is depicted in Figure 7.



Figure 7 Open Sensor Network pilot data model


The basic tools for any Apps and service will be transforming tools, which will support translation from observation into potential standards for accessing data. Apps will be built on the base of this standards. See the basic scheme:



Figure 8 Open Sensor Network pilot Apps basic schema

4.4.1 User Apps


Name of the app: Catalogue for Publishing and Accessing

Application description: The catalogue will, support publishing of sensors with detail description and discovery of available sensors.


capabilities:

Publishing Discovering

Related services: S3.1


Timeplan for the development: Application will be developed till October 2015.

Responsibility for the development: Michal Kepka





The testing will start with existing applications in Czech and Latvian, from November also with other sensors providers.

Role of the user: Publish data Discover data

Role of the administrator: Manage database Plug sensors not using interoperable protocols

Offline use:



BOSC

Notes and issues

Table 35 Open Sensor Network pilot App 1


Name of the app: Alerting System

Application description: Alerting system will be based on events analysis and will send alerts to users. System will also support visualisation of observations from selected sensors.


capabilities:

Sensor alert Visualise observations



Timeplan for the development: Application will be developed till October 2015.

Responsibility for the development: BOSC



Not Yet tested.

Role of the user: Receiving alerts

Visualise observation

Role of the administrator: Prepare description of events

Manage database

Offline use:



BOSC



Notes and issues



Name of the app: Groundwater measurement

Application description: The application will provide modelling and visualisation of groundwater surface.


capabilities:

Model ground water in time and space

Visualise



Timeplan for the development: Application will be developed till February 2016.

Responsibility for the development: CCSS



Not Yet tested. The testing will start with existing applications in Czech and Latvian, from November also with other sensors providers.

Role of the user: Visualise groundwater surface in time and space

Role of the administrator: Manage database

Plug sensors not using interoperable protocols

Offline use:



CCSS

Notes and issues


4.4.2 Services

Services needed for Apps developed as part of pilot Opens Sensor Network:

Service ID: S3.1

Name of the service: Senslog

Service description: Senslog will integrate modules from previous development

and also FI to support accessing and transforming of data.




capabilities:

Access observation

Transform Observation

Publish Observation

Related apps: A3.1, A3.2, A3.3

Timeplan for the development: February 2016

Responsibility for the development: UWB, BOSC, CCSS



Not yet tested.


platform?

Notes and issues

Table 38 Open Sensor Network pilot service: Senslog


Cloud Property Open Sensor Network Pilots Requirements







operating system?



Yes


gigabytes.

>10 TB








future success.)

Senslog

Table 39 Open Sensor Network pilot Cloud Property requirements



5 OPEN LAND USE MAP THROUGH VGI - PILOT 4

Land use involves the management and modification of the natural environment or wilderness into the built environment such as fields, pastures, and settlements. It also has been defined as "the arrangements, activities and inputs people undertake in a certain land cover type to produce, change or maintain it" Land use practices vary considerably across the world. The United Nations' Food and Agriculture Organization Water Development Division explains that "Land use concerns the products and/or benefits obtained from use of the land as well as the land management actions (activities) carried out by humans to produce those products and benefits."[1] As of the early 1990s, about 13% of the Earth was considered arable land, with 26% in pasture, 32% forests and woodland, and 1.5% urban areas. Land use and land management practices have a major impact on natural resources including water, soil, nutrients, plants and animals. Land use information can be used to develop solutions for natural resource management issues such as salinity and water quality. For instance, water bodies in a region that has been deforested or having erosion will have a different water quality than those in areas that are forested. Forest gardening, a plant-based food production system, is believed to be the oldest form of land use in the world. Although the terms land cover and land use are often used interchangeably, their actual meanings are quite distinct. Land cover refers to the surface cover on the ground, whether vegetation, urban infrastructure, water, bare soil or other. Identifying, delineating and mapping land cover is important for global monitoring studies, resource management, and planning activities. Identification of land cover establishes the baseline from which monitoring activities (change detection) can be performed, and provides the ground cover information for baseline thematic maps.

5.1 Use Cases

Use case ID: UC4.1.

Use case name: Preparation of basic regional Land Use Maps

Abstract: To be possible provide VGI updating of Land

Use maps, it is necessary to have initial map

layers, which will be used for later VGI editing.

This will include sets of initial Land Use maps

in different scales and in different levels of

information and basic geometry, which will be

used for future classification, This basic

geometry will be initially classified on the base

of available data. All this layers will be

available for visualisation and for download.


the user):

There will be four steps, which will be

necessary to provide for every region. Often

this activities will be outsourced to SDI4Apps

team or external experts

Transform available data into Open

Land Use data model

Publish transformed data

Derive basic geometry

Provide classification of basic geometry



Table 40 Open Land Use Map through VGI pilot Use case 1

User groups/stakeholders: Public bodies

Service Company



The end users will be involved in design of

application and mainly in process of data

preparation.




smart phones & LOD


LOD




sourced & social media

Coverage of region with basic maps

Attracted investors


INSPIRE4Youth

Performance: This Use case will require scalable computing,

initial building of Open Land Use maps is time

consuming process, which will require large

computing capacity

App ID The data are prepared outside of SDI4Apps

system.

Notes and Issues

Use case ID: UC4.2.

Use case name: VGI for Land Use

Abstract: The use case will support updating of available

Open Land Use map by volunteers from their

computers or from terrain. It will require

interaction of volunteers and system

administrators, who will take responsibility for

open Land Use map validation.





the user):

There will be next possible tasks provided by

volunteers

Reclassified object in Open Land Use

Draw new objects into Open Land Use

maps

Make evidence from terrain (taking

photo) of error in Open Land Use map

From the side of system administrator update

of data will be provided on the base of

acceptance volunteers suggestions.

User groups/stakeholders: Volunteers

Students

Public bodies

Service organisations



End users, mainly regions are involved into

design of application. They will have also

chance to report bugs or make suggestion for

improvement use developers blog and Redmine

Criteria of success: User validation

Community of people updating maps

New Open Land Use and LOD


INSPIRE4Youth

Ecosystem Services Evaluation Pilot

Performance: For visualisation standard user acceptable




App ID A4.1

Notes and Issues

Use case ID: UC4.3.

Use case name: Brownfields, Greenfields

Abstract: Municipalities, region or owners will publish

information about their brownfields and

greenfield as part of Open Land Use map.

Municipalities and regions will have possibility




to display this maps as embedded on their Web

pages.


the user):

The brownfield owners will publish information

about their brownfields, Greenfields as part of

Open Land Use. This information will include:

Description of brownfields, Greenfields

Offer for potential usage

Location

Description

Owners including contacts

Eventual Urban/Spatial plan

Owners of brownfield will be able to use

Embedded services and run application from

their Web pages.

User groups/stakeholders: Brownfield owners

Public bodies

Service organisations



End users, mainly regions are involved into

design of application. They will have also

chance to report bugs or make suggestion for

improvement use developers blog and Redmine

Criteria of success: User validation

Community of people updating maps

New Open Land Use and LOD


INSPIRE4Youth

Ecosystem Services Evaluation Pilot





App ID A4.2

Notes and Issues




For this pilot, we expected next groups of users

Public bodies – National and Regional Authorities responsible for spatial planed and land use.

Experts – Planning and Land Use experts and decision makers.

Enterprises, Companies and SMEs – related to Land Use. and brownfields

Citizens – visitors and people interested in planning and land use in their local environment.

Students – interesting about thematic data

Farmers and forest owners – putting their information into the system

NGOs – interested in better information about land use mainly in sensitive areas

Researchers interested in Land use data analysis

Real estate business and investors interesting about land use analysis

System administrators – people responsible for managing data sets for certain regions.

Currently we have already basic Land Use maps based on CLC and Urban Atlas cross all Europe. We are now preparing detail maps based on cadastre for Czech Republic and till end of September 2015 such basic detail map will be prepared for Latvia. Preparation of details maps for other countries depends on availability of data.

The first version of Crowdsourcing application will be developed till September 2015 and some for publishing information about brownfields.

We are planning that Open Land Use will be combined with platform whatstheplan.eu managed now by the Plan4all association. The business model will be based on four pillars:

Services for municipalities, regions and brownfield users to harmonise their data.

To use embedded functionality for publishing data on web pages of cities, regions, brownfields owners.

On demand analysis for certain users like banks, real estate etc.

Consultancy for developers of applications.


5.3.1 Datasets

A brief description of input datasets of the Open Land Use Map through VGI pilot:

Dataset ID: DS4.1

Resource title: Open Land Use

Resource abstract:

Data containing a combination of various land use and land cover data sets, including local data, CORINE land cover or Urban Atlas. Data should provide the most detailed information on land use and land cover as possible.


Europe (prospectively global coverage)

Level of detail: Depend on the most detailed data in particular location. The current version uses Czech cadastral data as the most detail data.

Resource locator:




Depend on licenses of particular interconnected data.

Format: RDBMS

Transformation:

Transformation to the new data model

Re-classification and mapping of nomenclatures

Ready to use: There is a prototype of data set. for Czech Republic

Size: 5 TB

Data update: Continuously

Notes and issues

Table 43 Open Land Use Map through VGI pilot data set: Open Land Use

5.3.2 Data Models

Figure 9 Open Land Use Map through VGI pilot Data model


5.4.1 User Apps


Name of the app: OLU Crowdsourcing Apps



Application description: The crowdsourcing Apps will support next functionality:

Edit attribute of objects

Edit objects

Collect information demonstrating objects in terrain


capabilities:

Data collection

Data editing



Timeplan for the development: September 2015




The testing will start from September by users from Czech and Latvia.

Role of the user: Crowdsourcing of data

Role of the administrator: Validation of data

Offline use:



HSRS

Notes and issues

Table 44 Open Land Use Map through VGI user App 1


Name of the app: Brownfield publishing and searching

Application description: The Brownfield publishing and searching Apps will support next functionality:

Publish information about brownfield

Search and visualise brownfield


capabilities:

Registered on portal

Registered Brownfields

Search for brownfield

Visualise brownfield









The testing will start from September by users from Czech and Latvia.

Role of the user: Crowdsourcing of data

Role of the administrator: Validation of data

Offline use:



HSRS

Notes and issues

Table 45 Open Land Use Map through VGI user App 2

5.4.2 Services

Service ID: S4.1

Name of the service: Data editor

Service description: The editor will allow edit data using Web and mobile interface.


capabilities:

Edit attributes

Edit objects

Add objects






Testing will start from October.


platform?

Yes

Notes and issues

Table 46 Open Land Use Map through VGI pilot service: Data editor




Cloud Property Open Land Use Map through VGI Pilots

Requirements







operating system?



Yes


gigabytes.

>1 TB








future success.)

Geoserver

HSlayers NG

Senslog

Table 47 Open Land Use Map through VGI pilot Cloud Property requirements



6 OPEN INSPIRE4YOUTH – PILOT 5

The pilot will be focused on utilization of environmental data (maps) for educational and gaming purposes. The main components of the environment will be introduced - water, air, soil, forests, nature protection, climate information, landscape, waste management, forest management etc. Each component has its actual condition measured for the region. Depending on data availability this measured condition can be compared with a European standard. All this will be made available in an entertaining manner - no school textbooks.

The main user group for this Atlas are students - higher grades of elementary schools, high schools and universities. However it should be appealing also for any adult person interested in topic.

There will be use these foreseen cases:

Regional Atlas of Environment (Liberec Region)

Street Names (Uhlava)

From European Protected areas, landscape and habitats towards region (Europe)

Figure 10 Open INSPIRE4Youth pilot



6.1 Use Cases

Use case ID: UC5.1

Use case name: Regional Atlas of Environment

Abstract: Electronic version of Regional Atlas of

Environment. It is expected that the Atlas will

have four faces:

Classical Atlas, which will focus on "regular"

description of the components of the

environment and will be targeted at a

comprehensive view of the basic components of

the environment. Main components of

environment will be introduced: water, air, soil

and forests, nature and landscape, waste

management, forest management, flood

protection etc. For this functionality will be

used mainly web application.

Alive Atlas, which will be continuously added

to the contents of the current data, data from

sensors, data obtained from crowdsourcing.

Using form of web application.

Custom Atlas, which focuses on creating

custom mapping composition of acquiring

personal data and sharing. For this

functionality will be used web application and

also mobile application of atlas. Mobile app will

use geolocations to visualize actual data

related to the environment in user´s current

area.

Game Atlas, which will be focused on

presenting entertaining and appealing way of

submission facts. It will try to arrange an

interesting interaction between users and will

encourage to work with Atlas.

We are tipped sample tasks that could be

solved by means of Atlas:

Nature trails

Students would to map an existing nature trail.

Along the way, take pictures of nature stops

and give their content into context with the

appropriate thematic map (conservation, water

management ...). Advanced students will try to

propose a new nature trail in their

neighbourhood. They´ll pass route and enter it



into map. They´ll find some interested places

and try to propose educational boards using

maps from the app. They can attempt to find a

similar pathway in other parts of Europe and to

compare natural conditions.

Safely to School

Crowsourcing collecting data from students

who might have a real use. Students (or public)

track down its surroundings, where they feel

completely safe and conversely where they do

not feel safe. Subjective evaluation will only

have simple rules make it easy for the

operator. The result could be continuously

emerging heatmap that reveals the unpopular

or danger part of the city.

Another tasks for data collection:

outdoor signs on walking trails and signs with a

labels and information on protected areas,

mapping health condition and collecting

photographs of alleys, illegal landfills...


the user):

1. Logging into Atlas

2. Study a chapter of one of the

components of the environment

3. Choose some task

4. Solving task

5. Collect points for solving

User groups/stakeholders: Students (mainly in the age 12 – 15 or

15 to 18)

Public with the interest in environment



In the preparation process

Giving some feedback

Data acquisition through mobile

application



Collection of relevant dataset

resources



Reuse & share environmental

information resources, channels & tools





Performance:

App ID: A5.1

Notes and Issues

Table 48 Open INSPIRE4Youth Pilot: Use case 1

Use case ID: UC5.2

Use case name: Street Names

Abstract: People are moving along streets, but they

usually do not perceive that streets are named

after important persons, places, things or

events, which are often closely interconnected

to particular cities and its history. To know

detailed information on street names it means

to extend knowledge about the whole place

especially for young people.


the user):

To visit the web page (or to download

and use the mobile application later)

To search localization manually or by

GPS.

To click to relevant (symbolized)

street.

To find information and knowledge of

the street name.

To follow links (including links to the

streets named according the same

person or thing).

User groups/stakeholders: Citizens

Students

Visitors



To provide a feedback.

To provide new content or modified

existing content (in a later advanced

version).

To share information in social media.

Criteria of success: Number of data

Number of visitors

Positive feedback

Interoperation with other SDI4Apps pilots: Open Smart Tourist Data



Performance:

App ID: A5.2

Notes and Issues


Use case ID: UC5.3

Use case name: From European Protected areas, landscape and

habitats towards region

Abstract: The Use cases will prepare basic Pan European

Layers about Natura 2000, bio zones, climatic

zones, landscape and other relevant data.

Information will be interlinked with DBPedia

and other LOD sources. This pan European data

sets will be base for activities of students

collecting their relevant regional data and local

data, demonstrating different approaches to

environmental protection. Students will have

information search for relevant information

cross Europe, but also will actively collected

data related to their regions.


the user):

The students will have next possibilities:

to search for relevant map context

related to certain regions and certain

themes from computers and

smartphones

Students will have possibilities to use

advanced visualisation methods

explaining them different

environmental problems. Map data will

have possibility to be connected with

textual data, videos, images excel

tables, etc.

Students will have possibilities to

collect information directly in the

terrain and connected this information

with positions (photos, videos etc.)


publish other data like texts, tables

etc. and eventually connected this

information with position




prepare their own thematic maps

User groups/stakeholders: Students from secondary schools

Teachers

University students



To provide a feedback.

To provide new content or modified

existing content (in a later advanced

version).

To share information in social media.




smart phones & LOD


LOD







New tourism activities, visitors & jobs,

and SME developed services.






App ID: A5.1, A5.2

Notes and Issues



The stakeholder group is formed by next stakeholders groups:

Schools and students

Public bodies – European, National and Regional Education and Environmental Authorities.

Experts – Education and Environmental experts, Researchers & decision makers.



Enterprises, Companies, NGOs and SMEs – targeting and working with young people.

Citizens – young people.

The plan for implementations of Apps is January 2016.


6.3.1 Datasets

Dataset ID: DS5.1

Resource title: Protected sites

Resource abstract:

Protected sites of the Czech Republic


Czech Republic

Level of detail: 1: 10 000

Resource locator:


CC-BY

Format: SHP, WMS, KML, RDF

Transformation:

Not

Ready to use: Yes

Size: 500 GB

Data update: 2015

Notes and issues

Table 51 Open INSPIRE4Youth pilot data set: Protected sites

Dataset ID: DS5.2

Resource title: Administrative boundaries

Resource abstract:

Boundaries of administrative regions, counties, communes and cadasters of the Czech Republic - free dataset RUIAN


Czech Republic

Level of detail: 1: 2000

Resource locator:

Not ready yet.


OD

Format: SHP

Transformation:

Harmonization to format

Ready to use: No

Size: 1 GB

Data update: 2015

Notes and issues

Table 52 Open INSPIRE4Youth pilot data set: Administrative boundaries



6.4 Data Models

In the pilot activities there will be used following data models adopted from external resources (therefore there will be only references as sources of relevant information):

Data models from POIs and roads as they are published in the pilot 2

INSPIRE data models (above all protected areas) as they are published in relevant specifications. Potential modifications will be realized on the basis of user requirements during solution of pilot activities.

Local data models of the Liberec region data (data model are available now).


6.5.1 User Apps


Name of the app: Geoportal for education

Application description: The portal will be able to offer thematic maps with context and connected also with LOD to access educational materials about objects


capabilities:

Search for data

Visualise data

Access Educational content

Related services:

Datasets required

Timeplan for the development: January 2016

Responsibility for the development:



Not done yet.

Role of the user: Using educational material

Publishing VGI content

Role of the administrator: Management and validation of data

Offline use: No



CCSS

Notes and issues



Table 53 Open INSPIRE4Youth user App 1


Name of the app: Mobile application supporting geoportal

Application description: To display educational content in spatial context on the base of position


capabilities:

Search for data

Visualise data

Access Educational content

Related services: S5.1, S5.3


Timeplan for the development: January 2016




Not done yet.

Role of the user: Using educational material

Publishing VGI content

Role of the administrator: Management and validation of data

Offline use: No



CCSS

Notes and issues

Table 54 Open INSPIRE4Youth user App 1

6.5.2 Services

Service ID: S5.1

Name of the service: Authorization and authentication

Service description: Authorization and Authentication for Regional Atlas of Environment.


capabilities:

Single sign on



Related apps:

Timeplan for the development:





platform?

Notes and issues

Table 55 Open INSPIRE4Youth pilot service: Authorization and authentication

Service ID: S5.2

Name of the service: Maps services

Service description: Add map services (WMS, WFS…) to map

Prepare thematic map layer by including data to the shared table

Advanced cartography for thematic layer

Set up map service from geographic data

Generate heat map from crowdsource data


capabilities:

Visualise map

Add new objects

Related apps:

Timeplan for the development: December 2015




Not yet


platform?

Yes

Notes and issues

Table 56 Open INSPIRE4Youth pilot service: Maps services

Service ID: S5.3

Name of the service: Mobile application



Service description: Collecting data

Access data in terrain


capabilities:

Visualise map

Add new objects

Related apps:

Timeplan for the development: December 2015

Responsibility for the development: CCSS



Not yet


platform?

Yes

Notes and issues

Table 57 Open INSPIRE4Youth pilot service: Mobile Application


Cloud Property Open INSPIRE4Youth Pilots Requirements







operating system?



Yes


gigabytes.

>500 GB








future success.)

Geoserver

HSlayers NG

Senslog

Table 58 Open INSPIRE4Youth pilot Cloud Property requirements



7 ECOSYSTEM SERVICES EVALUATION – PILOT 6

Ecosystem services (ES) represents the direct and indirect contributions of ecosystems to the human well-

being. Action 5 of the EU Biodiversity Strategy to 2020 calls Member States to map and assess the state of

ecosystems and their services in their national territory. There are various types and classifications of ES

(e.g. The Economics of Ecosystems and Biodiversity (TEEB)37). ES evaluation represents one of the six pilots

built on top of the SDI4Apps framework, addressing identification of spatial representation of the outcomes

of ES evaluation with a focus on sustainable support of tourism and regional development.

Whereas ecosystem services and their values are present in almost any landscape, one of the most important

challenges is to assess the quality and quantity of the services provided in key natural areas such as protected

areas, since these are often the source area of environmental services characterized by an exceptionally high

productivity. Spatial representation in most suitable digital form will be made available respecting the SDI

requirements and recommendations and published via interfaces allowing presentation and further

comparison of available content.

Pilot is therefore focused on the development and integration of information resources on top of the SDI4Apps

framework for the ecosystem evaluation with visualisation of the ecosystem services values for particular

location of the interest.

7.1 Use Cases

Use case ID: UC6.1

Use case name: Ecosystem services evaluation support (ES evaluation)

Abstract: Use case is focused on integration information resources for ecosystem services evaluation with visualisation of the ecosystem services values for particular location of the interest.


the user):

Use case will primarily address development of ecosystem services dataset based on linking diverse resources mainly from the biodiversity, biophysical and economic domains. This dataset will provide information about value of the ecosystem in particular location in monetary or physical units form, which brings new dimension to perception of the evaluation on the state of the environment and the sustainable management of natural capital. Public sector representatives as well as researchers will be able to search for information resources serving as an input into the ecosystem services identification and evaluation their value for particular location. First type of actors will be able to address policy demand and is driven mainly by the Aichi Targets

37 http://www.teebweb.org/resources/ecosystem-services/

http://www.teebweb.org/resources/ecosystem-services/



(Strategic Goal D) and the EU Biodiversity Strategy to 2020 (Action 5) which promote consistent ecosystem assessments. Researchers will be able to improve existing methodologies in order to improve the current knowledge of ecosystem services in maintaining human well-being and prosperity. Citizens as well as potential investors are able to query concrete value of the particular ecosystem service for the area of their interest.

User groups/stakeholders: Public sector representatives – National and regional authorities responsible for nature and biodiversity conservation and maintenance.

Researchers – Research and academia bodies involved in improvement of the ESS evaluation methodologies.

How and when will the users be involved in

the design and development process?

Interaction with the users will be based on Social validation methodology (D2.2), taking into the consideration pilot specific conditions.

Criteria of success: Identification of appropriate ESS

Collection of relevant dataset resources

Selection of suitable methodology

Generation of basic and normalised layers

Availability of the the particular ecosystem services layers, including overall assessment of ecosystem services value layer

Availability of the machine (API) and human readable (GUI) interfaces to browse and display Valuation map of ecosystems

Outcomes of social validation

Interoperation with other SDI4Apps pilots: Easy Data Access Open Land Use Map Through VGI Open Smart Tourist Data Open INSPIRE4Youth


App ID: A6.1

Notes and issues:

Table 59 Ecosystem services Evaluation Pilot: Use case 1

38 “A study on tolerable waiting time: how long are Web users willing to wait?”, Nah, F. Behaviour & Information Technology, 2004, available at http://sighci.org/uploads/published_papers/bit04/BIT_Nah.pdf




Use case ID: UC6.2

Use case name: Ecosystem services utilisation (ES Utilisation)

Abstract: This use case will support the possibility to utilise the ES via comparison of evaluated ES datasets with another ES datasets on any level of detail.


the user):

Maintainer of the UC6.1 will identify the possibilities to link/upload ecosystem services layers into the system allowing comparison of these datasets with any other ES datasets. User will be able to compare this information with any other relevant information and to decide for the most suitable dataset.

User groups/stakeholders: 1. Citizens – contributors and consumers of the ES related information.

2. Private sector stakeholders – local producers, investors and developers

How and when will the users be involved in

the design and development process?

Interaction with the users will be based on Social validation methodology (D2.2), taking into the consideration pilot specific conditions.

Criteria of success: Possibility to compare the ES datasets from UC6.1 with other related ESS datasets

Interoperation with other SDI4Apps pilots: 1. Easy Data Access 2. Open Land Use Map Through VGI 3. Open Smart Tourist Data 4. Open INSPIRE4Youth


App ID: A6.1

Notes and issues:

Table 60 Ecosystem services Evaluation Pilot: Use case 2


User engagement will play important role in shaping and fine tuning of the ES pilot. Related activities will be associated with the underlying use-cases as well as maturation of the domain in time. The pilot therefore aims to address all identified SDI4Apps target groups:

39 “A study on tolerable waiting time: how long are Web users willing to wait?”, Nah, F. Behaviour & Information Technology, 2004, available at http://sighci.org/uploads/published_papers/bit04/BIT_Nah.pdf




Public bodies,

Experts,

SMEs

Citizens.

7.2.1 Stakeholders and their roles

These target groups will be represented in identified use cases via following stakeholders.

Users & Stakeholders

Use Case UC6.1 -ES Evaluation Use Case UC6.2 – ES Utilisation

Public bodies SAZP, Ministry of the environment of the Slovak Republic

SAZP, Ministry of the environment of the Slovak Republic, State nature

conservancy of the Slovak Republic

Experts SK MAES Working Group members

SMEs, Enterprises and Companies

Consultants in ES mapping and evaluation

Possible investors

Citizens Tourists and Visitors to the National parks and protected areas, All local people.

Anybody

Table 61 Ecosystem services Evaluation Pilot stakeholders

7.2.2 Engagement method

Based on the Social Validation approach and plans defined in D2.2 (Social Validation Methodology).

7.2.3 Incentives for engagement

Stronger engagement will be stimulated via presenting the foreseen concepts available data and technologies to the widest relevant community in order to receive multispectral feedback and adjust the pilot activities accordingly. Participation on the Based on the Social Validation approach and plans defined in D2.2 (Social Validation Methodology).

7.2.4 Timing, planning, indicators

Activities will be adjusted to the criteria and indicators defined in D2.2 (Social Validation Methodology. The criteria of success for this pilot’s services are as follows:

Availability of the Valuation map of ecosystems with UI and API

Usage level & Social Validation of Services that use SDI4Apps

Increased access to harmonized & interoperable GI, L/OD& VGI data

Sustainable support of tourism with the applied ES methodology & datasets.



Quantified in the following indicators:

Ecosystem services pilot Scenarios Success Criteria

Apps/ Svcs in Operation

No of App/ Svc

Users

No GI/LOD datasets in

use

No VGI datasets created

Monthly accesses

New Apps/ Svcs

1. ES Evaluation 1 10 10 6 100 1

2. ES Utilisation 1 15 6 6 50 0

Total for Slovak Pilot

2 25 16 12 150 1

Table 62 Ecosystem services Evaluation Pilot success criteria

7.2.5 Business plan - market potential

Potential to utilise the ES pilot outcomes will be identified in line with the development and implementation of the D8.5.1 Business Model.


7.3.1 Datasets

Dataset ID: DS6.1

Resource title: Corine land cover

Resource abstract: Corine means 'coordination of information on the environment' and it was a prototype project working on many different environmental issues. The Corine databases and several of its programmes have been taken over by the EEA. One of these is an inventory of land cover in 44 classes, and presented as a cartographic product.

Geographical coverage: Slovakia

Level of detail: 1:50 000

Resource locator: http://inspire.geop.sazp.sk/geoserver/wfs?request=GetFeature&version=1.1.0&outputFormat=gml32&typename=lcv:LandCoverUnit&cql_filter=%22lcv:inspireId/base33:Identifier/base33:namespace

Restrictions/Licences: CC-BY

Format: WFS

Transformation: Manual transformation for particular ecosystem services layers, including overall assessment of ecosystem services value layer (Schema “ESS process model”)



Ready to use: Yes

Size: 90 MB

Data update: 2015

Notes and issues

Table 63 Ecosystem services Evaluation Pilot Dataset: Corine land cover

Dataset ID: DS6.2

Resource title: Protected sites

Resource abstract: INSPIRE Protected sites of the Slovak republic



Resource locator: http://inspire.geop.sazp.sk/geoserver/wfs?request=GetFeature&version=1.1.0&outputFormat=gml32&typename=ps:ProtectedSite&cql_filter=%22ps:siteDesignation/ps:DesignationType/ps:designation

Restrictions/Licences: CC-BY

Format: WFS


Ready to use: Yes

Size: 20 MB

Data update: 2015

Notes and issues

Table 64 Ecosystem services Evaluation Pilot Dataset: Protected sites

Dataset ID: DS6.3

Resource title: Administrative boundaries (SVM 50)

Resource abstract: Boundaries of administrative regions, counties, communes and cadastres of the Slovak Republic


Level of detail: 1:50000

Resource locator:



Restrictions/Licences: Licensed, No distribution of the source possible

Format: ESRI Coverage or ESRI Shapefile


Ready to use: No - license restricted, not for public usage

Size: 6,5 MB

Data update: 1998

Notes and issues

Table 65 Ecosystem services Evaluation Pilot Dataset: Administrative boundaries (SVM 50)

Dataset ID: DS6.4

Resource title: Livestock statistics

Resource abstract: Export of Statistics of livestock population in counties of the Slovak Republic from database published by Statisical office of the Slovak Republic. The exported data were connected to spatial layer of administrative/statistical units (counties).


Level of detail: 1:50000

Resource locator:

Restrictions/Licences: Public

Format: XLS, SHP


Ready to use: yes

Size: 50 kB

Data update: 2014

Notes and issues

Table 66 Ecosystem services Evaluation Pilot Dataset: Livestock statistics

Dataset ID: DS6.5

Resource title: Wood (Paper pulp) production



Resource abstract: Layer was created on the top of the Corine Land Cover 2006, where forest categories were evaluated based on Corine classification. (Coniferous forest, deciduous forest, mixed forest). Individual cells of the layers were assigned with average value of forest growth in this type of forest per year.



Resource locator: http://147.251.252.167:8080/geoserver/sk_pilot_ess_rasters/wms http://147.251.252.167:8080/geoserver/sk_pilot_ess_rasters/wcs

Restrictions/Licences: CC- BY

Format: WMS/WCS


Ready to use: Yes

Size: 33,6 MB

Data update: 2015

Notes and issues

Table 67 Ecosystem services Evaluation Pilot Dataset: Wood (Paper pulp) production

Dataset ID: DS6.6

Resource title: Number of livestock per hectare of pasture

Resource abstract: Layer represents the number of livestock grazing on one hectare in a given district. Layer was formed as a combination of statistical data on number of animals in the various districts of Slovakia and suitable pastures for grazing livestock.





Format: WMS/WCS




Ready to use: Yes

Size: 31,5 MB

Data update: 2015

Notes and issues

Table 68 Ecosystem services Evaluation Pilot Dataset: Number of livestock per hectare of pasture

Dataset ID: DS6.7

Resource title: Carbon sequestration based on land types

Resource abstract: Layer defines the volume of CO2 sequestration in the country by tons per year. Layer was created by assessing landscapes types according the Corine Land Cover and assignment of values of CO2 sequestration for particular land type.





Format: WMS/WCS


Ready to use: Yes

Size: 67,3 MB

Data update: 2015

Notes and issues

Table 69 Ecosystem services Evaluation Pilot Dataset: Carbon sequestration based on land types

Dataset ID: DS6.8

Resource title: Landscape quality from tourism perspective



Resource abstract: Layer expresses potential of the area for tourism. Layer was evaluated as summary of areas and points potentially interesting for tourism. As inputs connected layers of protected areas evaluated according to their relevance were used. Taking into the consideration legal access restrictions (e.g. Restricted access to some small scale protected areas with the highest level of protection). In addition areas suitable for tourism (e.g. large water dams and local objects significant for tourism as castles, caves and other important cultural, landscape and natural sites) have been also added as input to the layer. The areas with the highest ratings (values) are the best from the tourism perspective.





Format: WMS/WCS


Ready to use: Yes

Size: 33,4 MB

Data update: 2015

Notes and issues

Table 70 Ecosystem services Evaluation Pilot Dataset: Landscape quality from tourism perspective

Dataset ID: DS6.9

Resource title: Biodiversity

Resource abstract: Layer reflects the quality of the territory in terms of biological diversity. The layer was created from layers of qualitative assessment of occurrence approx. 250 selected protected species and their mutual overlay. The areas with the highest ratings (values) are the best in the biodiversity.



Resource locator: http://147.251.252.167:8080/geoserver/sk_pilot_ess_rasters/wms



http://147.251.252.167:8080/geoserver/sk_pilot_ess_rasters/wcs


Format: WMS/WCS


Ready to use: Yes

Size: 33,4 MB

Data update: 2015

Notes and issues

Table 71 Ecosystem services Evaluation Pilot Dataset: Biodiversity

Dataset ID: DS6.10

Resource title: Overall assessment of ecosystem services

Resource abstract: After the overlay of the normalized layers over final layer was created defining the Landscape quality from the perspective of the provision of these ecosystem services.





Format: WMS/WCS


Ready to use: Yes

Size: 31,5 MB

Data update: 2015

Notes and issues

Table 72 Ecosystem services Evaluation Pilot Dataset: Overall assessment of ecosystem services



Dataset ID: DS6.11

Resource title: Cultural sites interesting for tourism - Castles, Chateaus, Ruins

Resource abstract: Point spatial layer with locations of tourism interesting historical buildings classified by attractivity.



Resource locator: http://globus.sazp.sk/atlassr/


Format: WMS


Ready to use: yes

Size: 50KB

Data update: 2002

Notes and issues

Table 73 Ecosystem services Evaluation Pilot Dataset: Cultural sites interesting for tourism – Castles,

Chateaus and Ruins

Dataset ID: DS6.12

Resource title: Natural sites interesting for tourism - spas, thermal springs,

caves, waterbodies

Resource abstract: Point spatial layer with locations of tourism interesting

natural sites classified by type and attractiveness.





Format: WMS



Transformation: Manual transformation for particular ecosystem services

layers, including overall assessment of ecosystem services

value layer (Schema “ESS process model”)

Ready to use: yes

Size: 50KB

Data update: 2002

Notes and issues

Table 74 Ecosystem services Evaluation Pilot Dataset: Natural sites interesting for tourism – spas,

thermal springs, caves and waterbodies

Dataset ID: DS6.13

Resource title: Sites of UNESCO world natural and cultural heritage

Resource abstract: Point spatial layer with UNESCO world natural and cultural

heritage sites





Format: WMS




Ready to use: yes

Size: 50KB

Data update: 2002

Notes and issues

Table 75 Ecosystem services Evaluation Pilot Dataset: Sites of UNESCO world natural and cultural

heritage

Dataset ID: DS6.14

Resource title: Tourism and recreation zones



Resource abstract: Polygon layer with zones important for tourism and

recreation classified by importance and type of recreation





Format: WMS




Ready to use: yes

Size: 50KB

Data update: 2002

Notes and issues

Table 76 Ecosystem services Evaluation Pilot Dataset: Tourism and recreation zones

Dataset ID: DS6.15

Resource title: Population density

Resource abstract: Polygon layer with population density (number of citizens /

1 square km). The source layer was evaluated regarding

the population density for recreational needs potential.





Format: WMS




Ready to use: yes

Size: 300KB



Data update: 2002

Notes and issues

Table 77 Ecosystem services Evaluation Pilot Dataset: Population density

7.3.2 Data Models

In order to create maps for selected ESS, including their transformation towards the map of the overall

assessment of the ESS set of processing routines documented via ESS process model (Figure 2) had to be

defined, tested and implemented. Each map was prepared based on input data following the rules defined

in set of tools has been applied, resulting in the layer with coverage spatial representation (ESRI Grid) layer.

Each target layer express volume of the benefits provided by a given ecosystem service in physical units as

they were evaluated. E.g. m3 of wood (paper pulp) or m3 of carbon in the layer of carbon sequestration in

different types of landscape, therefore these layers have been identified as basic ones.



Figure 11 Ecosystem Services evaluation pilot Data model

As in case of each layer, content is addressing different semantic and values were presented in various units

of measurements concept of normalised layers have been proposed. These layers were created based on the

basic layers of evaluated ESS, where the values in the individual layers have been transformed (normalized)

to the range between 0-1. Such normalizing by very simple method allows qualitatively compare and merge

different layers into the final overall assessment of ecosystem services. This phase have been executed with

the use of the desktop GIS ArcGIS suite.




7.4.1 User Apps


Name of the app: SK Pilot Ecosystem Services Evaluation

Application description: Application providing the visualisation and browsing options of individual layers produced for ecosystem services, including overall assessment of ecosystem services value layer.


capabilities:

Generic enablers Specific enablers for SDI domain Harmonisation toolset Semantic toolset for linked data harmonisation Analytical and modelling toolset Visualisation toolset


Datasets required DS6.1 – DS6.15

Timeplan for the development: Initial version to be operated by the month 15 and consequently updated based on the interaction with the stakeholders.

Responsibility for the development: Martin Tuchyna (SAZP) Zuzana Okanikova, Marek Hubáček (Pronatur) Tomáš Kliment (E-PRO)



Initial testing is foreseen in combination of SDI4Apps consortium members and selected stakeholders.

Role of the user: Use of the application by visualising and browsing the content. Later on contributing with the crowdsourcing data with real time integration into the app.

Role of the administrator: Maintenance and further development.

Offline use: Is it possible to use the app offline? NOT POSSIBLE, it’s a web application not a mobile app



Martin Tuchyna (SAZP) Zuzana Okanikova, Marek Hubáček (Pronatur) Tomáš Kliment (E-PRO)

Notes and issues Initial version of the app: http://skpilot-viewer.virt.ics.muni.cz/ol3/eng/

Table 78 Ecosystem services Evaluation Pilot User App



MockUp:

Figure 12 Ecosystem Services evaluation pilot User App

7.4.2 Services

Service ID: S6.1

Name of the service: WMS/WCS service for Ecosystem service pilot

Service description: An OGC Web map services providing the machine readable access to the particular ecosystem services layers, including overall assessment of ecosystem services value layer.


capabilities:

Visualisation, overlay

Related apps: A6.1

Timeplan for the development: brief, realistic

Responsibility for the development: Who is responsible for the development?



Initial version to be operated by the month 15 and consequently updated based on the interaction with the stakeholders.




platform?

Yes

Notes and issues Initial version of the web API: http://147.251.252.167:8080/geoserver/sk_pilot_ess_rasters/wms http://147.251.252.167:8080/geoserver/sk_pilot_ess_rasters/wcs

Table 79 Ecosystem services Evaluation Pilot required Services


Cloud Properties ESS Pilots Requirements







operating system?

Any objections against using it as the

default operating system for deployment?

Yes


gigabytes.

100GB








future success.)

TBD

1. GeoServer open source used as a domain specific

enabler serving Web GIS server functionalities.

It’s scalability would be very valuable to be

tested, especially for a cloud approach used to

establish SDI node(s) comprising in a set of nodes

with an average computer resources (2GB of RAM,

2*CPU). In such a configuration a clustered

GeoServer solution may improve the overall

performance of an SDI node significantly.

Table 80 Ecosystem services Evaluation Pilot required Cloud Properties



8 CONCLUSION

During the first year of the SDI4Apps project work with pilot development has successfully started. In most of the pilots stakeholders are involved already in early phases of pilot development by organising meetings to identify the needs, discuss use cases, roles and responsibilities of stakeholders. At least two use cases for each pilot are defined as being potentially most beneficial. Common stakeholders for most of the pilots are Public sector representatives, researchers and local volunteers. Depending on the pilot specification other stakeholders as tourists, students and business owners are included.

Pilot Use case 1 Use case 2 Use case 3 Use case 4 Use case 5

Easy data

access

Mobile Apps to

support

Tourism for

conservation

Mobile App for

protected

Heritage sites

Open Smart

Tourist Data

Linked Open

Data for

tourism

Crowdsourced

data for

tourism

Cyclo tourism Promotion of

regions

Advertisement

of tourism

agencies

focused on

active tourism

Open Sensor

network

OpenSensorNet

work data

management

OpenSensorNet

work Early

Warning

OpenSensorNet

work Ground

Water

Monitoring

Open Land Use

Map through

VGI

Preparation of

basic Land Use

Maps

VGI for Land

Use

Brownfields,

Greenfields

Open

INSPIRE4Youth

Regional Atlas

of Environment

Street names From European

Protected

areas,

landscape and

habitats

towards region

Ecosystem

Evaluation Pilot

Ecosystem

service

evaluation

support

Ecosystem

services

utilisation

Table 81 Use cases of Single Pilots

At this stage of pilot development business planning is based mainly on Apps for final users. For example in Open Smart Tourist Data pilot travel agencies, regions and municipalities are expected to generate main incomes from using developed Apps to promote their tourism products. But further Business plan and market potential will be identified in line of work with Deliverable 8.5.1 Business Model till March 2016.



At the beginning of second year most of the 24 identified basic datasets are ready to use, but few are still in the process of publishing. Prepared data sets are very different in both content and size. Data sets size varies from 50 KB to 5 TB. Accordingly varies the required data storage space between pilots – 20 GB till approximately 10 TB. Largest quantities of spatially referenced data that needs to be collected, storage, shared, analysed and easy accessed refers to Open Sensor network pilot. Managing huge amount of data and ensuring the reliability and quality is currently the main challenge of Open Sensor network pilot. Basic data sets for all pilots need to be deployed till September 2015, but additional data set preparation and information updating will be ongoing continuously.

Based on available datasets, experience form other projects as FODDIE and OTN, and objectives of each App data models have been prepared and illustrated.

Pilots have preferred deployment of server side services on Debian Linux operating system and all pilots can use Ubuntu Linux 14.04 LTS as the operating system and have no objections to it as the default operating system for deployment. Requirements for scalability of Cloud platform may grow with the usage level of Applications. Need for testing the scalability of Web GIS server is expressed.

So far pilot development has shown high potential of usage of SDI4Apps created solutions. As Apps are created in strong cooperation between stakeholders and developers they may fulfil the needs of stakeholders and be a good example for stimulating stronger engagement of external developers as well as promoting future use of SDI4Apps created platform.

This deliverable is an initial collection of use cases, apps, datasets and services. This information will be thoroughly analysed within next few months. Dependencies between the SDI4Apps platform and pilot applications will be identified and the initial deployment of pilot apps will be done in September 2015.

d m a n d pl a t f o r m s f o r si n g l e pi l o t s€¦ · otakar Čerba karel charvat ccss mac...

Documents