A neW concept of pubLic administration based on citizen co-created mobile urban services Grant Agreement: 645845

D3.6 – TRENTO, BILBAO, FINNISH REGION AND NOVI SAD ENVIRONMENT V2

DOC. REFERENCE: WeLive -WP3 -D36-REP -17 12 15 -v10 RESPONSIBLE: FBK AUTHOR(S): TECNALIA, UDEUSTO, FBK, CNS, INF, DNET , TRENTO, LAUREA, EUROHELP DATE OF ISSUE: 15 /12 /2017 STATUS: FINAL DISSEMINATION LEVEL: PUBLIC

VERSION DATE DESCRIPTION v0.1 08/09/2017 Definition of the Table of Contents and distribution of tasks v0.2 28 /10/2017 Contributions from CNS v0.3 02 /11/2017 Contributions from Serbian task force v0.4 04 /11/2017 Contributions from LAUREA v0.5 08 /11/2017 Contributions from Spanish task force v0.6 1/12 /2017 Contributions from Trento task force v0.7 7/12/2017 Ready for review V1.0 15/12/2017 Final version

INDEX

1. EXECUTIVE SUMMARY...... 11 2. INTRODUCTION ...... 12 3. COMMON ENVIRONMENT FOR ALL WELIVE PILOTS ...... 14 4. TRENTO ENVIRONMENT ...... 17

4.1. PROCESS FOLLOWED IN TRENTO FOR PLATFORM POPULATION ...... 17 4.1.1. First Pilot Phase...... 17 4.1.1.1. Stakeholder Consultation Process ...... 17 Surveys ...... 18 Workshops ...... 18 Design Games ...... 19 4.1.1.2. Expectations and insights extraction ...... 19 4.1.2. Second Pilot Phase ...... 19 4.1.2.1. Stakeholders Consultation Process ...... 19 4.1.2.2. Expectations and insights extraction ...... 20 4.2. INTEGRATION WITH LOCAL INFRASTRUCTURE ...... 20 4.3. SERVICES, BUILDING BLOCKS, DATASETS ...... 22 4.3.1. First pilot phase...... 22 4.3.1.1. Services ...... 22 Trento Street Cleaning ...... 22 Trento Bike Sharing ...... 24 Trento Transport Timetables ...... 27 4.3.1.2. Building blocks ...... 28 4.3.1.3. Datasets ...... 29 4.3.2. Second Pilot Phase ...... 30 4.3.2.1. Services ...... 30 Trento Informer ...... 30 Trento Room Booking ...... 32 4.3.2.2. Building Block ...... 34 4.3.2.3. Datasets ...... 35 Dataset quality report ...... 36 Recommendations ...... 38 5. BILBAO ENVIRONMENT ...... 39

5.1. PROCESS FOLLOWED IN BILBAO FOR PLATFORM POPULATION ...... 39 5.1.1. Phase 1 - Stakeholders Consultation Process ...... 39 5.1.1.1. Surveys ...... 40 5.1.1.2. Workshops ...... 40 5.1.1.3. Idea Contest ...... 40 5.1.1.4. Game Design Session ...... 41

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 2

5.1.2. Phase 2 - Expectations and insights extraction ...... 42 5.2. INTEGRATION WITH LOCAL INFRASTRUCTURES ...... 44 5.3. SERVICES, BUILDING BLOCKS AND DATASETS ...... 45 5.3.1. Services ...... 45 5.3.1.1. Bilbozkatu ...... 45 5.3.1.2. Auzonet ...... 47 5.3.1.3. BilbOn ...... 49 5.3.1.4. Big Klub ...... 51 5.3.1.5. Bilbao Events ...... 53 5.3.2. Building blocks ...... 55 5.3.2.1. BB Citizens voting (Bilbozkatu) ...... 55 5.3.2.2. BB Users feedback ...... 56 5.3.2.3. BB Users Ranking ...... 56 5.3.2.4. Nearest Point Finder ...... 56 5.3.2.5. Image uploader ...... 56 5.3.2.6. Geonames ...... 57 5.3.2.1. Geoutilities ...... 58 5.3.2.2. Bilbao Ekintza Events ...... 58 5.3.2.3. In-app questionnaires ...... 59 5.3.2.4. Survey BB ...... 59 5.3.2.5. Bilbao Agenda BB ...... 60 5.3.2.6. Directions (eus-routes) ...... 61 5.3.3. Datasets ...... 61 5.3.3.1. Dataset quality report ...... 62 5.3.3.2. Recommendations ...... 63 6. HELSINKI-UUSIMAA ENVIRONMENT ...... 64

6.1. PROCESS FOLLOWED IN FINLAND FOR PLATFORM POPULATION ...... 64 6.1.1. Need and challenge identification ...... 66 6.1.1.1. Planning meetings and workshops ...... 67 6.1.1.2. Needs ...... 67 6.1.2. Idea generation ...... 69 6.1.2.1. Concepts...... 69 6.1.2.2. Design game session ...... 71 6.1.2.3. WeLive Design Game 2.0 ...... 73 6.1.3. Idea selection ...... 74 6.1.3.1. WeLive seminars ...... 74 6.1.4. Development ...... 75 6.1.4.1. Application development ...... 75 6.1.4.2. Citizen engagement...... 75 6.1.5. Implementation ...... 76 6.1.6. Exploitation/Dissemination...... 76 6.1.6.1. Datasets ...... 76 6.1.7. Stakeholders ...... 77 6.1.7.1. Citizens and developers ...... 77 6.1.7.2. Public administrations ...... 77 6.1.7.3. Laurea...... 77 6.2. DESIGN PRINCIPLES ...... 77 6.3. SERVICES ...... 79 6.3.1. Pilot phase 1 services ...... 79 6.3.1.1. My Polls ...... 80 6.3.1.2. My Opinion ...... 82 6.3.1.3. My Neighbourhood ...... 85 6.3.2. Pilot phase 2 services ...... 88

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 3

6.3.2.1. Sportit ...... 89 6.3.2.2. Helsinki City Museums ...... 91 6.3.2.3. Helsinki City Bikes ...... 92 6.4. BUILDING BLOCKS ...... 95 6.4.1. GeoPoll Answers ...... 95 6.4.2. GeoPoll Statistics ...... 95 6.4.3. GeoPoll Locations ...... 95 6.4.4. GeoPoll Polls ...... 96 6.4.5. GeoPoll Perspectives ...... 96 6.4.6. Geo Locations...... 97 6.4.7. GeoPoll Tags ...... 97 6.4.8. GeoPoll Attributes ...... 97 6.4.9. GeoPoll Users ...... 98 6.4.10. GeoPoll My ...... 98 6.4.11. GeoHeatmap ...... 99 6.4.12. GeoDB Match Matrix ...... 100 6.4.13. Geocoder ...... 100 6.4.14. Personal Data ...... 100 6.4.15. GeoDB Match Heatmap ...... 100 6.4.16. GeoPoll Heatmaps ...... 100 6.4.17. GeoPoll Density Heatmap ...... 100 6.4.18. Geo Areas ...... 101 6.4.19. Area datasets ...... 101 6.4.20. Citizen Data Vault API ...... 101 6.5. DATASETS ...... 101 6.5.1.1. Dataset quality report ...... 103 6.5.1.1.1. Recommendations ...... 106 7. NOVI SAD ENVIRONMENT ...... 107

7.1. PROCESS FOLLOWED IN NOVI SAD FOR PLATFORM POPULATION ...... 107 7.1.1. Surveys ...... 107 7.1.2. Workshops ...... 108 7.2. INTEGRATION WITH LOCAL INFRASTRUCTURE ...... 108 7.3. SERVICES, BUILDING BLOCKS, DATASETS ...... 109 7.3.1. Services ...... 109 7.3.1.1. Relocation Advisor ...... 110 7.3.1.2. Safe City ...... 113 7.3.1.3. Public Procurement Transparency ...... 116 7.3.1.4. My Local Community ...... 117 USER PART (L OCAL COMMUNITY ) ...... 117 ADMINISTRATION PART (L OCAL COMMUNITY PORTAL ) ...... 121 Create, Read, Update and Delete a local community post ...... 122 Create a topic for the local community post ...... 123 Adding a user...... 123 Viewing the posts as pins on the map ...... 124 MOJ GRAD ...... 125 REPORT COMMUNAL PROBLEM ...... 125 Review of the announced communal problems ...... 127 Detailed review of the reported problems ...... 128 Situation center ...... 128 Announcements of situation problems ...... 128 Review of the reported situation problems ...... 131

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 4

Detailed review of the reported situation problems ...... 131 7.3.1.4 Culture Key ...... 132 7.3.2 Building blocks...... 135 7.3.2.4 Water and air quality ...... 135 7.3.2.5 Traffic analyzer ...... 135 7.3.2.6 Citizen Data Vault API ...... 136 7.3.2.7 My Local Community API ...... 136 7.3.2.8 Events in Novi Sad ...... 136 7.3.2.9 Museums in Novi Sad ...... 136 7.3.2.10 Theaters in Novi Sad ...... 136 7.3.3 Datasets ...... 137 7.3.1.5. Dataset quality report ...... 137 7.3.1.6. Recommendations ...... 137 8. CONCLUSIONS ...... 138 9. ABBREVIATIONS ...... 140 10. REFERENCES ...... 141 11. COMMENTS FROM EXTERNAL REVIEWERS ...... 144

11.1. NOVI SAD ...... 144 11.1. LAUREA ...... 145 12. ANNEX I – ETHICAL COMPLIANCE CHECK ...... 146

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 5

ILLUSTRATIONS

Figure 1 - Population Process in Trento ...... 17 Figure 2 – Trentino Open Data Portal ...... 21 Figure 3 – Open Services Portal ...... 21 Figure 4 – List of street cleaning occurrences ...... 23 Figure 5 – Map of street cleaning occurrences ...... 23 Figure 6 – Search for street cleaning occurrences ...... 23 Figure 7 – Schedule of cleaning for a street ...... 23 Figure 8 – Details of a street cleaning occurrence ...... 23 Figure 9 – Favorite streets ...... 23 Figure 10 - Trento Street Cleaning in Google Play...... 24 Figure 11 - Trento Street Cleaning in WeLive Player ...... 24 Figure 12 - Trento Street Cleaning in WeLive Marketplace (Services) ...... 24 Figure 13 – Bikes availability within a shared bike station ...... 25 Figure 14 – List of shared bike station ...... 25 Figure 15 – Shared bike station on the city map ...... 25 Figure 16 – Favorite shared bike stations management ...... 25 Figure 17 - Trento Bike Sharing in Google Play ...... 26 Figure 18 - Trento Bike Sharing in WeLive Player...... 26 Figure 19 - Trento Bike Sharing in WeLive Marketplace (Services) ...... 26 Figure 20 – Bus line selector ...... 27 Figure 21 – Train line selector ...... 27 Figure 22 – Sample bus line timetable ...... 27 Figure 23 – Bus stops on the city map ...... 27 Figure 24 – Next runs at a given bus stop ...... 27 Figure 25 – Favorite lines, stops and stations ...... 27 Figure 26 - Trento Transport Timetables in Google Play ...... 28 Figure 27 - Trento Transport Timetables in WeLive Player ...... 28 Figure 28 - Trento Transport Timetables in WeLive Marketplace (Services) ...... 28 Figure 29 - List of information ...... 31 Figure 30 - Filter by themes ...... 31 Figure 31 - Favorites ...... 31 Figure 32 - Trento Informer in Google Play ...... 32 Figure 33 - Trento Informer in WeLive Player ...... 32 Figure 34 - Trento Informer in WeLive Marketplace (Services) ...... 32 Figure 35 - General information ...... 33 Figure 36 - Map of rooms available...... 33 Figure 37 - Filters ...... 33 Figure 38 - Trento Room Booking in Google Play ...... 34 Figure 39 - Trento Room Booking in WeLive Player ...... 34 Figure 40 - Trento Room Booking in WeLive Marketplace (Services) ...... 34 Figure 41 – Population Process in Bilbao ...... 39 Figure 42 – Bilbao´s Open Data portal...... 44 Figure 43 – DCAT harvester...... 45 Figure 44 – Proposals filtering ...... 46 Figure 45 – List of Proposals ...... 46 Figure 46 – Detail of a Proposal, with their ratings and votes ...... 46 Figure 47 – Map of proposals by neighborhood ...... 46 Figure 48 – Comments in a proposal ...... 46 Figure 49 – Statistics of a proposal ...... 46 Figure 50 – Rating and commenting a proposal...... 46 Figure 51 – Introducing a new request ...... 46 Figure 52 – Main menu of the app ...... 46 Figure 53 – Bilbozkatu in Google Play screenshot ...... 47 Figure 54 – Bilbozkatu in WeLive Player ...... 47

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 6

Figure 55 – Bilbozkatu in WeLive Marketplace ...... 47 Figure 56 – List of Auzonet functionalities ...... 48 Figure 57 – Introduce needs or things to borrow ...... 48 Figure 58 – Auzonet search screen ...... 48 Figure 59 – Auzonet in Google Play screenshot ...... 48 Figure 60 – Auzonet in WeLive Player ...... 49 Figure 61 – Auzonet in WeLive Marketplace ...... 49 Figure 62 – Filtering POIs created by citizens ...... 50 Figure 63 – POI search by category ...... 50 Figure 64 – POI search by text ...... 50 Figure 65 – POIs located on a map ...... 50 Figure 66 – POIs located on a map ...... 50 Figure 67 – Details of a POI ...... 50 Figure 68 – Searching by location ...... 50 Figure 69 – Introducing a new POI ...... 50 Figure 70 – Login ...... 50 Figure 71 – Bilbon in Google Play screenshot ...... 51 Figure 72 – Bilbon in WeLive Player ...... 51 Figure 73 – Bilbon in WeLive Marketplace ...... 51 Figure 74– Events search by date or map ...... 52 Figure 75– App menu ...... 52 Figure 76– Bilbao Ekintza news ...... 52 Figure 77 - Filling in user profile ...... 52 Figure 78 – Big Klub in Google Play screenshot ...... 53 Figure 79 – Big Klub in WeLive Player ...... 53 Figure 80 – Big klub in WeLive Marketplace ...... 53 Figure 81 – List of Bilbao Events functionalities ...... 54 Figure 82 – List of Events filtered by Exhibitions ...... 54 Figure 83 – Event Information Card ...... 54 Figure 84 – Events Map ...... 54 Figure 85 – Form to create new event ...... 54 Figure 86 – User Events administrator ...... 54 Figure 87 – Bilbao Events in Google Play screenshot ...... 55 Figure 88 – Bilbao Events in WeLive Player ...... 55 Figure 89 – Bilbao Events in WeLive Marketplace ...... 55 Figure 90 – Publication of the Nearest Point Finder BB in the WeLive Marketplace...... 56 Figure 91 – Publication of the Image Uploader BB in the WeLive Marketplace...... 57 Figure 92 – Publication of the Geonames BB in the WeLive Marketplace...... 57 Figure 93 – Publication of the Geoutilties BB in the WeLive Marketplace...... 58 Figure 94 – Publication of the Geoutilties BB in the WeLive Marketplace...... 58 Figure 95 – Administration interface for the Bilbao Ekintza Events BB...... 59 Figure 96 – Publication of the In-app BB in the WeLive Marketplace...... 59 Figure 97 – Publication of the Survey BB in the WeLive Marketplace...... 60 Figure 98 – Administration interface for the Survey BB...... 60 Figure 99 – Publication of the Survey BB in the WeLive Marketplace...... 60 Figure 100 – Publication of the directions (eus-routes) BB in the WeLive Marketplace...... 61 Figure 101 – Citizens´ and stakeholders’ interests in different public sectors in Helsinki-Uusimaa region ...... 64 Figure 102 – Example: result of the design game ...... 65 Figure 103 - Three step co-creation process...... 66 Figure 104 - Collaborative innovation process [21]...... 66 Figure 105 - The concept creation collaboration structure in Vantaa City’s point of view ...... 67 Figure 106 - The challenge themes presented by the City of Vantaa in spring 2017 ...... 68 Figure 107 - Total number of 152 identified needs in thematic categorization ...... 68 Figure 108 - Master’s Courses’ engaged citizens’ demographics - Age ...... 70 Figure 109 - Master’s Courses’ engaged citizens' demographics – Stakeholder type and ICT skills ...... 70 Figure 110 - Digital service concepts created in the master’s coursers in thematic categorization ...... 70

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 7

Figure 111 - Movester and Tendo applications ...... 71 Figure 112 - “Double Diamond” process model [22] ...... 71 Figure 113 - Design game session...... 72 Figure 114 - Design Game sessions’ engaged citizens’ demographics - Age ...... 72 Figure 115 - Design Game sessions’ engaged citizens’ demographics – Stakeholder type and ICT skills ...... 73 Figure 116 - WeLive Design Game 2.0 renewed cards: persona, user need and datasets ...... 73 Figure 117 - WeLive Seminar 4...... 74 Figure 118 - WeLive Seminar attendees’ demographics – Stakeholder type ...... 74 Figure 119 - Thematic datasets included in WeLive Design Game 2.0 and WeLive-Platform (155 datasets) ...... 77 Figure 120 – Finnish pilot services ...... 78 Figure 121 – Architecture overview for Finnish pilot services hosted in the CNS environment ...... 79 Figure 122 – My Polls menu ...... 80 Figure 123 – My Polls: Create one or more location based polls to reveal the public opinion ...... 81 Figure 124 – My Polls: Summary of poll answers can be viewed as pie charts ...... 81 Figure 125 – My Polls: Poll heatmap shows averages of poll location answers with colors ...... 82 Figure 126 – My Opinion menu ...... 83 Figure 127 – My Opinion: Poll map view allows search and adding poll locations ...... 83 Figure 128 – My Opinion: Answer poll questions and view statistics on answers by others ...... 84 Figure 129 – My Opinion: Poll density heatmap helps finding areas with active polls ...... 84 Figure 130 – My Neighbourhood menu ...... 85 Figure 131 – My Neighbourhood: Add one or more personal preferences to define what is important to you ...... 86 Figure 132 – My Neighbourhood: Add one or more interesting locations to be analysed ...... 86 Figure 133 – My Neighbourhood: Match matrix summarizes how well each location matches your preferences ...... 86 Figure 134 – My Neighbourhood: Match heatmap helps finding areas that match your personal preferences ...... 87 Figure 135 – My Neighbourhood: Finding a safe neighbourhood with city rental houses ...... 87 Figure 136 – My Neighbourhood: Sub-requests triggered by a simple match heatmap request ...... 88 Figure 137 - Applications in the WeLive Marketplace ...... 89 Figure 138 - Sportit in APP Store and Google Play ...... 90 Figure 139 - Home Page (iOS) ...... 91 Figure 140 - The general map view, specific sport facility view and the rules and practice assistant view (iOS)...... 91 Figure 141 - Helsinki City Museums in Google Play ...... 92 Figure 142 - Detailed map view ...... 92 Figure 143 - Helsinki City Bikes in Google Play ...... 93 Figure 144 - The general map view ...... 94 Figure 145 - HELSINKI-UUSIMAA Items relations ...... 94 Figure 146 – Age structure of survey participants ...... 107 Figure 147 – Personal digital needs of examinees - the most common answers (in percentages) ...... 107 Figure 148 – Examinees' needs for public service sectors - the most common answers (in percentages) ...... 107 Figure 149 – Data sources in Novi Sad ...... 109 Figure 150 – The first window of Relocation Advisor application in both Web and Android service ...... 112 Figure 151 – Information regarding one of schools in Novi Sad ...... 112 Figure 152 – Route from requested address to one of the schools in Novi Sad ...... 112 Figure 153 – Bus stops on requested bus line ...... 112 Figure 154 – Parking places nearby requested address ...... 112 Figure 155 –The first window of Safe City Trip application in both web and android service ...... 114 Figure 156 – The route which the user has requested ...... 114 Figure 157 – Window showing the quality of water in Novi Sad...... 114 Figure 158 – Microphones shown on the map presenting the noise levels in Novi Sad ...... 114 Figure 159 – Noise level in the city of Novi Sad ...... 114 Figure 160 – Traffic buttons showing the amount of traffic in the city ...... 115 Figure 161 – Information regarding traffic in specific area in the city of Novi Sad ...... 115 Figure 162 – Public procurement transparency application logo and first page...... 117 Figure 163 – Options available in the application ...... 117 Figure 164 – Companies' public procurement options ...... 117 Figure 165 – Information about the company, which the user chose to get information about ...... 117 Figure 166 – Statistics ...... 117

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 8

Figure 167- Log in screen ...... 118 Figure 168- Log in with WeLive credentials ...... 118 Figure 169- Tooltip menu ...... 119 Figure 170- Local community map overview ...... 119 Figure 171- Community select list ...... 120 Figure 172- Topic picker ...... 120 Figure 173- Point of interest details ...... 121 Figure 174- Tooltip menu and survey page ...... 121 Figure 175 - Community post create form ...... 122 Figure 176 - Post table view ...... 123 Figure 177 - Topic create modal...... 123 Figure 178 - User registration ...... 124 Figure 179 - Post map view ...... 124 Figure 180 - Post pin details ...... 125 Figure 181 - Application Homepage ...... 125 Figure 182 - Reporting communal problem ...... 126 Figure 183 - Description of new communal problem ...... 126 Figure 184 - Problems category ...... 127 Figure 185 - Address assigning to the reported problem ...... 127 Figure 186 - Review of reported communal problems ...... 128 Figure 187 - Detailed review of the reported problems ...... 128 Figure 188 - Reporting situation problem ...... 129 Figure 189 - Reporting situation problem, topic choice ...... 129 Figure 190 - Selection of the category of situation problem ...... 130 Figure 191 - Assigning address to problem ...... 130 Figure 192 - Review of reported situation problems ...... 131 Figure 193 - Detailed review of reported situation problems ...... 131 Figure 194- Terms of use ...... 132 Figure 195- Main screen ...... 133 Figure 196- Cultural events screen...... 133 Figure 197- Museums and galleries screen ...... 134 Figure 198- Theatres screen ...... 134 Figure 199- Questionnaire screen ...... 135

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 9

TABLES

Table 1 – Most requested services in Trento by area ...... 18 Table 2 – Number of broken links for Trento pilot...... 36 Table 3 – Broken links for Trento pilot...... 38 Table 4 – Summary of starts earned by datasets from Trento pilot...... 38 Table 5 – Number of broken links for Bilbao pilot...... 62 Table 6 – Broken links for Bilbao pilot...... 63 Table 7 – Summary of starts earned by datasets from Trento pilot...... 63 Table 8 - Concept evaluation criteria ...... 75 Table 9 - Engaged people until 5.10.2017 ...... 76 Table 10 – Number of broken links for Helsinki-Uusimaa pilot...... 103 Table 11 – Datasets with an invalid SSL certificate from Helsinki-Uusimaa pilot...... 105 Table 12 – Unreachable resources from Helsinki-Uusimaa pilot...... 105 Table 13 – Summary of starts earned by datasets from Helsinki-Uusimaa pilot...... 106 Table 14 – Summary of starts earned by datasets from Novi Sad pilot...... 137 Table 15 – Quantitative outcome of population activities ...... 138

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 10

1. EXECUTIVE SUMMARY This document reports the outcomes of Tasks from T3.3 to T3.6, that is to say the setup and population of the WeLive environment for the four project pilots, namely Trento, Bilbao, Novi Sad and the Finnish region of Uusimaa-Helsinki. By “WeLive environment” we mean the juxtaposition of the WeLive framework and of the artefacts (services, building blocks, datasets, needs, ideas, challenges and more) published onto it, with which the stakeholders in the different cities/region interact during the pilot execution. The WeLive framework was described in the update versions of WP2 deliverables [28], [29], [30], [31], [32], [33], [34], and [35] for what concerns its components, and in the deliverable [36] for what concerns its integration. The guidelines followed for the integration and population activities were set in the deliverable [37]. In this document, we focus on the actual population activities carried out in the different pilot cities and one region and on the actual artefacts used for preparing the pilot environments. This document will briefly recall the portion of the WeLive environment that is commonly shared by all pilots and will provide the details of those aspects that differentiates the environments prepared in the three cities and one region involved in the experimentation. In particular, for each of these four environments, they will be described: • The processes by which the population of the environments was obtained, in particular providing insights about the different techniques used to engage people in this population effort and the relationship between the populating artefacts and the involvement of citizens; • Any possible pre-existing infrastructure that have facilitated the setup and population of the environment; • The actual artefacts by which the environment was populated. This second issue of the deliverable provides an update of the contents provided in the first issue [38], both by completing and extending the information already provided – for instance, improving the details about the first pilot phase artefacts with more updated information about the usage, enhancements, etc. - and by adding brand new material which documents the population of the WeLive framework for the second pilot phase of the project. This deliverable also considers the recommendations received by the project reviewers in the previous iterations, and describes those actions that represent the consortium reply to such recommendations. In particular, good care was taken of describing how the points recalled in the document “Address of review recommendations in Periodic Report 2” [39] were tackled. Similarly to what has been done for the second iteration of the other deliverables, also within the current document, all the major updates will be highlighted using the blue color. As usual, the description will be enriched by a (updated) discussion of possible ethical issues involved in the activities described, and we will provide some final considerations about the work that was executed. Overall, at the end of this document the reader will achieve a full understanding of the how the environment in the different pilot cities/region were settled for the execution of the pilots in which the WeLive co-innovation and co-creation approach were tested.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 11

2. INTRODUCTION The 2010 edition of the EU eGovernment Benchmark Report states that currently public services are built following an administration-centric approach, driving to a low usage, rather than according to the citizens´ need (user-centric approach). Public administrations are facing key socioeconomic challenges such as demographic change, employment, mobility, security, environment and many others. Besides, citizens expectations, in terms of burden reduction, efficiency, and personalization, are growing and will make the take-up of traditional public e-services steadily harder in the following years. Citizens want to transit from being mere consumers of public services to providers of those services, i.e. prosumers of the open government ecosystem. Public-private parnership and active contribution of citizens are two key instruments to transform the way currently cities and territories are being governed. To turn cities and territories into hubs of welfare, innovation and economic growth (i.e. to give place to Smarter Cities or Territories) not only they have to make a more efficient management of resources but they also have to be aware and reactive to the socio-economic needs and wants of their stakeholders, i.e. their citizens, local businesses and companies. ICT-enabled Open and Collaborative Government is the recipe to deliver "more from less". Indeed, governments cannot be any longer the single providers of public services. Enpowerment of stakeholders is necessary by incentivizing them to take a more active role. Public-private partenerships have to be catalysed to give place to a more sustainable model of government which also behaves as a economy promotion dynamizer. The WeLive project was born as a means to address the above challenges. WeLive aims at transforming the current e-government approach followed by most public administrations into we-government where all the stakeholders of public administration, namely citizens, local businesses and companies, are treated as peers (collaborators) and prosumers (providers) instead of the usual customer role associated to them. WeLive will enable also the so-called “t-Government” (Transformational Government) by providing stakeholders with the technology tools that enable them to create public value. In addition, WeLive is also thought to embrace l- Government (Lean Government), which aims to do more with less by involving other players, leaving the Government as an orchestrator around enabled platforms. Finally, WeLive fully adopts m-Government, i.e. an extension or evolution of e-government through utilization of mobile technologies for public service delivery. Consequently, WeLive proposes a new concept of e-Government, which provides the means, i.e. an environment or platform, analogously to the Web, and leaves others, all the stakeholders in a city or territory, to lead the innovation process and so turn public resource assets into artifacts to nurture economic growth and job creation. One of the goals of the WeLive project is to test its approach by running four pilots in four European cities, namely Trento (Italy), Novi Sad (Serbia), Bilbao (Spain), and Helsinki-Uusimaa Region (Finland). These cities and one region are good examples of economic dynamism and social welfare in their respective countries; they are different with respect to population size and each of them is endowed with distinguishing features, which overall make them very suitable to measure the impact of the Open and Collaborative Government solution proposed by WeLive. This deliverable describes the activities of Work Package 3 (WP3) “Integration, set-up and population of the WeLive framework” [13] that are required for the setup of the WeLive framework in the four trial sites. The deliverable is strictly related to the deliverable “D3.2 – Methodologies and validation of the integration of the WeLive environment v2” [36] that describes the integration of the WeLive components into a unique framework and the deliverable “D3.4 – Guidelines for the integration and population of the WeLive environment v2” [37] that provides the guidelines for the integration and setup of the framework required for launching the pilot activities. This document is an update of deliverable “D3.5 – Trento, Bilbao, Finnish Region, and Novi Sad Environment v1” [38] and describes the environments in which the second pilot phase of the WeLive project has taken place. By “environment”, we mean the assembly of the unique instance of the WeLive framework

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 12

that has been integrated and setup, with other infrastructural elements adopted in the different cities/region, and with a set of artefacts (services, building blocks, datasets, challenges, needs, ideas and more) published onto the platform whose role is to trigger the WeLive co-innovation and co-creation processes. It has to be noted that despite the presence of a unique and shared instance of the WeLive framework that will serve the four pilots, we can reasonably talk of four different environments. As a matter of fact, if from a technical and physical point of view the running framework is just one, nevertheless, from a logical point of view, the presence of other technical elements or tool and the different artefacts loaded onto the framework give place to four separate environments, that will be separately used by the stakeholders of the different cities/region involved in the experimentation. The ultimate goal of this deliverable is to describe these virtual environments and how they are characterized by peculiar aspects and by different elements. Each pilot city/region actually entered the project already having in its background its own smart city approach that the WeLive project contributed to enhance and extend. In some cases, such a local approach consists of pieces of infrastructure, services, datasets or other kinds of IT artefacts that have been integrated more or less tightly into the WeLive framework. In some other cases, the background of the local approach comprises tangible or intangible non-IT artefacts that are relevant for the execution of the WeLive innovation process. Besides, all the pilot cities share the existence of a number of WeLive artefacts that have been devised for initially populating the framework in order to trigger and exemplify the intended co-innovation approach. This deliverable explains how these platforms and artefacts, whatever their form and origin, have been integrated or have been integrated into the WeLive platform or are part of the environment for the pilot execution. Great attention will be paid in particular to describe the process by which these environments have been realized and to explicitly link the WeLive artifacts that have been devised both to such processes and, in particular, to the engagement activities performed in the pilot cities. In particular: In Section 3, we describe the part of the WeLive environment that is shared by all the pilots, In Section 4, the Trento task force introduces the peculiarities of its pilot environment; In Section 5, the Bilbao task force introduces the peculiarities of its pilot environment; In Section 6, the Uusimaa-Helsinki task force introduces the peculiarities of its pilot environment; In Section 7, the Novi Sad task force introduces the peculiarities of its pilot environment; Finally, in Section 8, we draw some conclusions about the setup and the population of the WeLive environments for the pilot execution.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 13

3. COMMON ENVIRONMENT FOR ALL WELIVE PILOTS The environment in which the users engaged in the pilot iterations of the WeLive project are expected to operate is composed by three elements. The first one is the centralized common instance of the integrated WeLive framework described in the deliverable “D3.2 – Methodologies and validation of the integration of the WeLive environment v2” [36]. The second one is any optional legacy infrastructure offered locally by each city to complement in some aspect the WeLive technological stack. The last one is the set of artefacts that each city publishes on the platform to enable the co-innovation and co-creation processes fostered by the WeLive approach. The second and the third one, being a prerogative of each pilot city, will be the subject matter of sections from 4 to 7. In the rest of this section, we focus on the first one. In the DoA of the project ([13]), when referring to the activities related to pilot execution, we repeatedly mentioned the existence of four different environments, one per city/region, in which stakeholder (citizens, businesses, public administrations) would be engaged to take part to the co-innovation and co-creation processes. While this is actually what has happened in the first pilot iteration and is happening the second pilot execution, at the same time, a portion part of these four environments is actually shared amongst the four different trials. This part of the environment is the unique instance of the WeLive framework that has been deployed. A thorough description of such environment is contained in deliverable “D3.2 – Methodologies and validation of the integration of the WeLive environment v2” [36], while a complete description of the components integrated in such environment can be found in the updated version of WP2 deliverable, that is to say [28], [29], [30], [31], [32], [33], [34], and [35] . Substantially, it corresponds to the set of tools with which the users of the WeLive framework can interact to perform their activities in terms of co-innovation and co- creation. Such tools correspond to the Ideation Board component (formerly known as Open Innovation Area), the Citizen Data Vault, the Datasets component (formerly known as Open Data Stack), the Charts component (formerly known as Analytics Dashboard), the Services component (formerly known as Marketplace), and all the other visible or invisible tools that support the execution of the former ones, e.g. in terms of authentication, logging. Such an environment encompasses also the cloud hosting facilities represented by the CNS marketplace and the Cloudfoundry PaaS. The reasons behind the choice for having just one deployed instance for these elements instead of replicating them for the four trials, can be summarized as follows. First, the Consortium considered more effective to clearly separate the integration task from its replication in different settings. The integration of the WeLive legacy components, opportunely tailored to the requirements of the project, demonstrated to be a challenge difficult enough for the first iteration of these project activities. Mixing such problems with a concurrent replication of the deployment on different infrastructures would have delayed furtherly the completion of the activities themselves. In fact, this choice has allowed the Consortium to gain more insight about the matters of replication, configuration and adaptation of the WeLive framework to different situations. Besides, already since the start of the first activities related to the tailoring of the components, to the integration of the framework and to the planning of the pilot execution that have occurred in parallel, it has been clear that the replication of this environment would have not granted any concrete advantage to the execution of the pilots and to the project. About any possible language issue, the opportune management of localization within the unique instance of the framework has prevented the raise of such kind of problems. Furthermore, the centralization of the execution environment of the WeLive framework has guaranteed a neat advantage in terms of management of the framework and of presentation of the results. Finally, yet importantly, the arrangement of a unique deployment of the WeLive framework has carried along a containment of the global costs sustained by the project for the hardware infrastructure and for the virtualization of the systems.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 14

The choice of using a common instance of the WeLive framework in the three pilot cities and one pilot region has been validated and confirmed also for the second round of engagement activities. Considering the building blocks developed, a number of them is shared amongst the pilots. Some of them are considered core BB, in that they provide functionality that not only are common but are also paramount. Some of them are simply generic and can be or have been used as they are by different pilots without the need of being adapted. Here it follows the list and a brief description of such core and common building blocks: Core Building Blocks: “Authentication and Authorization Component (AAC) BB”: relies on the OAuth2.0 protocol to handle resource access authorization and on external identity providers to manage user authentication. Specifically, AAC supports integration with the identify providers made available through standard authentication protocols, such as Shibboleth, Open ID, OAuth, or CAS. “Logging BB”: offers a set of instruments for validating, storing and analyzing the relevant events and activities both from within the WeLive platform components and from the 3rd part building blocks. These instruments come in the form of REST APIs and therefore programmatically available to the applications and components developed with different technologies and languages. Common Building Blocks: “CDV”: an ad hoc version of the homonymous WeLive core building block optimized to be used within the Visual Composer; it offers a set of instruments for validating, storing and analyzing the relevant events and activities both from within the WeLive platform components and from the 3rd part building blocks; these instruments come in the form of REST APIs and therefore programmatically available to the applications and components developed with different technologies and languages. “Query Mapper”: facilitates query of datasets through SQL statements. “Registry”: exposes the WeLive Marketplace searching APIs in order to get the other tools able to search and reuse the artefacts published into the platform. “Scraper API”: extracts data from HTML web pages. Web scraper allows registration of a desired URL (that should be parsed), a script including scraping logic, and JSON file containing the extracted data. The user has to provide a script for parsing the webpage, since different script has to be developed for each webpage to be parsed and script should include the type of output expected (regular expressions that applied to process contents). The results of the Web scraper are integrated into the ODS, i.e. a new dataset in the ODS will be created with the extracted data. “Twitter API”: extracts data from Twitter. Twitter provides unstructured info and based on social network wrapper it will be possible to create a new or extending datasets (compiling the selected tweets in successive dates) that talk about certain topics in a given period within a given area. For the datasets produced and used it has been possible a report of the quality of the datasets is provided. This report analyses the quality of the datasets provided by different city/region pilots to the WeLive project in terms of broken links and openness. The first report, generated with the CKAN report extension [23], checks the number of datasets containing broken links. The second one, generated with the previously mentioned CKAN report extension and the CKAN Quality Assurance extension [24], computes the score earned by each dataset

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 15

in the Linked Open Data 5-star scale. As conclusion of the results from this report, a set of best practices to fix detected issues are described. In the following sections, each task force explains how this common environment has been integrated and completed for each pilot city and the region, with all those elements needed to trigger and to support the co- innovation and co-creation approaches.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 16

4. TRENTO ENVIRONMENT 4.1. PROCESS FOLLOWED IN TRENTO FOR PLATFORM POPULATION The population of the WeLive platform for Trento environment is the final stage of a process launched at the beginning of the project and which involved the participation of several stakeholders in different online and offline activities. This process refers both to pilot phase I and pilot phase II of the project although they exhibit different characteristics. The process followed in Trento mainly comprised two stages as shown in Figure 1: • A first stage named “ Stakeholders Consultation Process ” aiming at collecting needs and ideas from stakeholders in order to identify requirements. • A second stage named “ Expectations and insights extraction ” for transforming such requirements, needs and ideas into a set of services, building blocks and datasets that address the stakeholders´ needs. This phase was accomplished involving WeLive consortium members.

Figure 1 - Population Process in Trento

4.1.1. First Pilot Phase 4.1.1.1. Stakeholder Consultation Process As described in D1.3 “WeLive scenarios, services and building blocks” ([2]) the municipality of Trento decided to organize the stakeholders’ consultation process for the first pilot phase in three steps: • Surveys • Workshop • Design games

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 17

Surveys At the end of June 2015, a survey was disseminated to citizens, public administrations, companies and professionals. The survey was made available both online and on paper for two weeks. A large communication campaign allowed reaching most of citizens by using the Web site, where a main story was edited, by sending ad hoc newsletters to opportune mailing lists, by spreading the news on social networks such as Facebook and Twitter. Paper version was also distributed by the Public Relation Office and made available in all the information points of the twelve city's districts. The results confirmed positively the initial expectations. Despite the summer period, we could witness a high participation: 555 people took the survey and 352 forms were completed. The average time to complete the form was 11 minutes and 32 seconds. The survey gave feedback about the areas where a stronger investment by the city was considered more valuable, at least from the point of view of the stakeholders: Online services Sustainable Mobility Environment Energy efficiency and building Contribution with ideas and suggestions for new services was very high, with 92 proposals. Some of them delivered more ideas up to a total of 244. In Table 1, it is available a summary of the main proposals, grouped according to their relevant area:

Area Most wanted services

Government / Online Digital helpdesk where submit all kind of dossier. Booking on –line of public services facilities (sport, conference hall, etc.). Online payment related pending dossier by the Administration.

Sustainable mobility Improving of sustainabl e mobility: bike sharing, car sharing/ca r pooling, info about bike-lane. Strengthen information about public transport: parking, fastest solution in order to reach the destination.

Environment; Waste Service or app with more info abo ut waste recycling . Reporting about management / decorum abandoned waste or deteriorated areas

Participation Participation to the management of public goods . Simplified reporting methods

Wi -Fi Expanding area where Wi -Fi is free

Table 1 – Most requested services in Trento by area

Workshops According to the results of the survey and the relevant number of stakeholder available to be involved, three workshops were organized, with the presentation of the above summarized results and discussion about new proposals.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 18

Design Games After the survey and the workshops, the third step was to organize some design games focused on “ government and online services ” and “ sustainable mobility ”, considering that the survey results highlighted both these issues as the most promising. 4.1.1.2. Expectations and insights extraction The result of this process was to determine in detail the demands and needs of stakeholders of Trento. Some of these requirements were already well known by the Municipality of Trento as well as priorities to satisfy. For this reason the municipality had already initiated specific projects: The introduction of a “one-stop shop” for all the interactive online services connected with another specific European H2020 Project, named “Simpatico” (regarding "Government / online services" Area) The introduction of “FuturaTrento” project and platform to permit the participation and the management of public goods (regarding Participation area) The development of a specific app “100% Riciclo” and the connected services (regarding "Environment" Area and “Waste management/decorum” in particular) For the remaining requirements, especially in “Sustainable Mobility”, Trento task force studied the viability of the scenarios and the ideas presented by defining which building blocks, datasets and infrastructures were necessary to transform each of these scenarios and ideas into real assets and prototypes that could be further populated into the WeLive framework. This phase involved the design and implementation of a set of assets by WeLive partner and required the participation if stakeholders during the testing phase to identify potential deficiencies and problems to be solved before the pilot phase II. Finally the services carried out according to user requests have been objects of a specific hackathon for improvement, as well as additional requests for improvement through specific challenges included in the “Open innovation Area” (Ideation Board) of WeLive platform. 4.1.2. Second Pilot Phase 4.1.2.1. Stakeholders Consultation Process The consultation process of the second pilot phase began with an ideas competition aimed at co-creating new services as well as improving existing ones (namely, those developed during the first pilot phase). The competition exploited the WeLive project tools; upon registration on the WeLive platform, citizens could signal their needs and respond to challenges launched by the Municipality by proposing their own ideas in the Ideation Board. Between the 20 th of December 2016 and the 20 th of January 2017, following a strategic, multimedia communication campaign, 50 new users registered to the platform and 37 new ideas were proposed in response to 7 challenges concerning, inter alia , Transportation and Mobility, Quality of Life and Residence - Housing & Development. According to the criteria defined by the organizer and reported both on the WeLive platform and on the municipality’s official website, nine ideas were selected as winning ideas. Six of these were ideas for new digital services: PA Guide Room Booking Trento Informer ProntOrto BiblioApp

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 19

Family Friendly App Three of them were aimed at improving the apps developed during the first pilot phase: Trento Bike Sharing Trento Transport Timetables Trento Street Cleaning 4.1.2.2. Expectations and insights extraction The aim of this participatory, bottom-up process was to assess further needs and demands of stakeholders in Trento and to co-create new services to address them. The competition proved successful in bringing up new ideas which were unknown or had not been previously considered by the PA. The municipality took up the challenge of assessing the availability of the infrastructure, datasets and building blocks required to transform these insights into valuable assets that have been eventually included into the WeLive framework. This objective was reached following a precise process. Firstly, the “Citizens’ and stakeholders’ engagement and cooperation plan” ([40]) set the strategy for engaging winners of the ideas competition in the refinement of their ideas. In May 2017 the municipality organized a dedicated workshop to assess availability and define the subsequent steps. Then, communication between the municipality and the citizens was mainly carried out offline. Secondly, a co-creation lab took place in summer 2017 to implement some of the winning ideas. A group of high school students and employees of the municipality worked in teams to transform ideas into assets: specifically, two new apps were developed: Trento Informer Trento Room Booking These groups have eventually been engaged into the testing phase of these new services in order to identify possible deficiencies. 4.2. INTEGRATION WITH LOCAL INFRASTRUCTURE In order to support the definition and publication of the open artefacts, the environment adopted in Trento relies on two software systems, namely open data portal and open service portal. The open datasets provided by the Municipality of Trento as well as by other local stakeholders are published in the CKAN-based open data portal of the Trentino province [1]. The use of the de-facto standard technology facilitates the integration of this tool with the WeLive framework. Indeed, currently the integration is achieved through the continuous harvesting of the relevant datasets from this portal. The extracted metadata is then automatically published to the WeLive platform, in particular, in the Open Data Stack (Datasets) and in the Marketplace (Services). Currently, the open data portal of the Trentino province hosts as much as 5124 open datasets that belong to 212 organizations within the Trentino province. The harvesting procedure for populating the ODS component of the WeLive framework considers the subset of datasets (200 in total, there were 16 during the first pilot phase) that belong to the Municipality of Trento organization. For more documentation about the ODS please check the WeLive online documentation ([14]).

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 20

Figure 2 – Trentino Open Data Portal

In order to publish and manage the building blocks, the Trento environment adopts the Open Service portal that is being developed and maintained by FBK. This portal allows for publication of Web services and APIs, allowing the users to explore their metadata (i.e., the formats and protocols, authors, licenses) and documentation, as well as to perform tests and see the results of the service invocations.

Figure 3 – Open Services Portal

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 21

The Open Service portal is also integrated with the WeLive framework to guarantee that the building blocks published within the portal appear on the WeLive Marketplace (Services). To accomplish this, the portal relies on the APIs provided by the marketplace for the artefact creation. Specifically, when a new open service is published, the corresponding WeLive-compatible specifications are generated, namely linked USDL and WADL / WSDL documents. Together with other metadata, the references to these specifications are passed to the marketplace API. 4.3. SERVICES, BUILDING BLOCKS, DATASETS 4.3.1. First pilot phase The users of the WeLive framework involved in the activities of the second iteration of the Trento pilot will have the opportunity to interact with a set of WeLive-compliant artefacts that have been devised for the first iteration of the Trento pilot. Such artifacts are published in the WeLive Marketplace (Services) and are of three kinds: services, building blocks and datasets. The following sub-sections provide the details about them. 4.3.1.1. Services The Trento task force has implemented three public service applications, namely: Trento Street Cleaning Trento Bike Sharing Trento Transport Timetables Such applications are presented to WeLive users through the WeLive Marketplace (Services) and through the WeLive Player app. They are actually Android apps and, thus, are available for download from the Google Play app store. The services offered within the three applications have been identified with the help of citizen during the engagement activities executed by the Trento task force during the first year of the project, which are described in [2]. The following subsections provide a description of the envisaged applications. Trento Street Cleaning The app “Trento Street Cleaning” stems from the need, expressed by Trento citizens, to avoid being fined or, even worse, to have their car removed due to the cleaning of the street cleaning that takes place during certain periods of the year. The cleaning of the streets is communicated to Trento citizens using standard channels that is to say, websites, bulletins, etc.), and temporary road signs that are exposed 48 hours before the cleaning itself. Overall, for the citizens it is not always easy to get informed timely about such occurrences. For this reason, it is useful for them to know in advance when streets, where they usually park their car, are going to be cleaned. The app presents, on a day-by-day basis, the schedule of the street cleaning. Such information is displayed both in the shape of a list of occurrences (Figure 4) and with markers located in the relevant streets within the city map (Figure 5). Users can also perform a text search for a street they are interested in (Figure 6). Whatever the way in which a street is selected, the user gets the complete schedule of upcoming cleanings planned (and also of the ones that have been already carried out) for that street (Figure 7) and the details of a single cleaning occurrence (Figure 8). If a user is interested in receiving push notifications the day before the cleaning is performed for a given street they can set such street as favorite. User can also manage such list of favorite streets (Figure 9).

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 22

Figure 4 – List of street cleaning Figure 5 – Map of street cleaning Figure 6 – Search for street cleaning occurrences occurrences occurrences

Figure 7 – Schedule of cleaning for a Figure 8 – Details of a street Figure 9 – Favorite streets street cleaning occurrence

The service is present in Google Play, WeLive Marketplace (Services) and WeLive Player.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 23

Figure 10 - Trento Street Cleaning in Google Play Figure 11 - Trento Street Cleaning in WeLive Player

Figure 12 - Trento Street Cleaning in WeLive Marketplace (Services)

Trento Bike Sharing The app “Trento Bike Sharing” is the result of Trento citizens’ interest towards the usage of bike sharing. In Trento it has been active since some years a service of electric bike sharing. The stations hosting the bikes are spread throughout the city and are endowed with sensors that provide the number of bikes and free slots available in the station itself. The application allows the user to perform a real-time check over the number of bicycles that are available and the number of empty slots for returning the bicycle (Figure 13). The stations can either be viewed as a list (Figure 14) or browsed on a map (Figure 15). In this way the user can, for example, see which the nearest stations are.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 24

It is possible to set some stations as favorites to have them always at one’s fingertips (Figure 16). The app is built over one of the building blocks available within the WeLive Marketplace (Services). Namely, it is the “Bike Sharing” building block which provides the real time availability of bikes within bike stations.

Figure 13 – Bikes availability within Figure 14 – List of shared bike Figure 15 – Shared bike station on a shared bike station station the city map

Figure 16 – Favorite shared bike stations management

The service is present in Google Play, WeLive Marketplace (Services) and WeLive Player.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 25

Figure 17 - Trento Bike Sharing in Google Play Figure 18 - Trento Bike Sharing in WeLive Player

Figure 19 - Trento Bike Sharing in WeLive Marketplace (Services)

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 26

Trento Transport Timetables The interests expressed by Trento citizens during the engagement activities performed within the WeLive project about sustainable mobility motivated the design and the implementation of the app “Trento Transport Timetables”. The app displays in a simple and immediate manner the timetables of buses that circulate in Trento and of trains passing by Trento (Figure 20, Figure 21, and Figure 22). The timetables in some cases also report real-time information about delays. Users can save their favorite tables for having them at hand in the main page. The timetables can be selected by choosing them from a list or by browsing a map (Figure 23) and checking what are the next runs for a particular bus stop or train station (Figure 24), as for instance the closest one. In addition this app enables a personalization of the service which is achieved by allowing the users to store and manage a list of favorite bus lines, bus stops or train stations (Figure 25).

Figure 20 – Bus line selector Figure 21 – Train line selector Figure 22 – Sample bus line timetable

Figure 23 – Bus stops on the city Figure 24 – Next runs at a given bus Figure 25 – Favorite lines, stops and map stop stations

The service is present in Google Play, WeLive Marketplace and WeLive Player.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 27

Figure 26 - Trento Transport Timetables in Google Play Figure 27 - Trento Transport Timetables in WeLive Player

Figure 28 - Trento Transport Timetables in WeLive Marketplace (Services)

4.3.1.2. Building blocks The environment of the Trento pilot can count on a number of building blocks that are hosted on the Trento open services platform, as explained in Section 4.2, and that are published as WeLive compliant artifact onto the WeLive Marketplace (Services). Such building blocks provide basic functionalities of different kinds, which are related to different service domains. Here below they are fully listed and catalogued: Mobility domain:

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 28

“Public Transport” : a service that provides access to the local transport network information, including the static and real-time information about the public transport schedules and their deviations, information about parking structures and their real-time filling, information about road works and blocks, etc. “Route Planner” : a service that provides the functionality of multimodal route planner, enabling planning for public transport and a car, bicycle routes, considering also the bike sharing stations and parkings nearby, etc. Besides, the service allows the user to store the planned routes and perform their monitoring, signaling possible problems (e.g., delays, strikes, accidents, etc). “Street Cleaning” : a service that provides information about the street cleaning schedules in the city of Trento. Specifically, the service allows for accessing the information about which streets are subject to cleaning on a specific day, to search for the street schedule by the street name, etc. “Bike Sharing” : a service that represents the real-time information about electric bike sharing stations in Trentino. The information represents the availability of the bike and bike slots at real time. “Mobility Crowdsourcing” : a service allows the user to signal different problems and situations regarding the mobility information. Typical scenarios include the information about bus or train delays, accidents, bike sharing station problems, transport network strikes, etc. Information and Tourism domain: “Trento in Your Pocket” : a service that provides an access to the cultural and touristic information about Trento and its suburbs. This includes events, places of interests, itineraries, hotels, restaurants, etc. Environment domain: “Waste Disposal” : a service that provides information about the waste disposal in the city, including the way the waste is separated, points of disposal, their opening times, etc. General purpose services: “City Report” : a service that exposes the functionality for the citizen to report a problem or a recommendation to the public administration regarding the provided services and infrastructure. The API exposes the methods for reading and publishing the problems across different tenants (municipalities or departments) and different services (e.g., road infrastructures, waste management, etc.). “Geocoder” : a service permits to convert an address in its coordinates, and vice versa converts coordinates in a readable address. The service uses Open Street Map data source to resolve addresses. “CDV Citizen Data Vault Trento”: the Citizen Data Vault (CDV) is the WeLive component that allows the citizens to manage their own data in a vault. The CDV collects the citizens profile data during the interaction with the WeLive tools tools. Furthermore the CDV provides a set of API to get the user profile data and to store and manage data generated using the third party application (User Data). All these operations require WeLive Authorization. 4.3.1.3. Datasets The Trento environment is completed by a list of datasets that are stored in the open data portal of the Trentino province, under the Municipality of Trento organization, as explained in Section 4.2, that have been imported

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 29

into the Open Data Stack (Datasets) tool of the WeLive framework and that are exposed on the WeLive Marketplace (Services). Such datasets are of different kinds. Here it follows the complete list: “Railways in Trentino” : data about the rail transport flowing in Trentino (excluding Trento-Malè line), in GTFS format. The data are updated each time change. Main available information: lists of stops (georeferenced), list of lines, list of racing times. Data from the Trento-Malè line are available, along with the other of the Trentino public transport data, on the portal of the Trentino open data (dati.trentino.it). “Waste differentiation in 2013” : CSV data related to municipal waste produced on a monthly basis (in tons) in the town of Trento. “Civic numbers”: set of all points of house numbers. They are divided into two categories. HOME: for every number there exists always and only one, is the main entrance to the building. SECONDARY: for every number there can be different, represent any secondary entrances to the building. The data are available in the GML, SHP, KML, DXF formats. “Street list”: set of all linear elements that represent the road graph of the Municipality of Trento. The data are available in the GML, SHP, KML, DXF formats. “Shops localization”: list of shops localized by the corresponding civic number. The data are available in the GML, SHP, KML, DXF formats. “Council financial report”: tables are related to revenue, subdivided by title and category, and expenditure, subdivided by title and function, noted during the reporting. The data are available, in CSV format, from 2003 until 2011, in 9 different datasets. 4.3.2. Second Pilot Phase The environment for the second pilot phase has been populated with a set of WeLive-compliant artefacts (services, building blocks and datasets) which are published in the WeLive Services section. The following section provides further details for each artefact. 4.3.2.1. Services The Trento task force has implemented two public service applications based on the winning ideas of the ideas contest, namely: Trento Informer Trento Room Booking Such applications can be found in the WeLive Services section and in the WeLive Player app. As they are Android apps, they are available for download from the Google Play app store. These applications stem from a co-creation strategy set up during the second pilot phase of the project which is described in section 4.1.2.1: their content and functionalities reflect the ideas proposed by citizens in the context of the ideas competition. The following subsections provide a description of both applications. Trento Informer Given the plethora of sources available, the app Trento Informer aims at gathering useful information concerning events in the city of Trento all in one place. Citizens can now access all information coming from the municipality’s official website concerning, inter alia , events, alerts, lost and found. Users can visualize information on a list ( Figure 29 ), can filter by themes ( Figure 30 ) and sources and can add notifications, sources or themes to favorites ( Figure 31 ). This app clearly addresses the need expressed by citizens to have a unique access point to all relevant information instead of referring to different and often confusing websites.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 30

Figure 29 - List of information Figure 30 - Filter by themes Figure 31 - Favorites

The service is present in Google Play, WeLive Marketplace and WeLive Player.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 31

Figure 32 - Trento Informer in Google Play Figure 33 - Trento Informer in WeLive Player

Figure 34 - Trento Informer in WeLive Marketplace (Services)

Trento Room Booking One of the interests expressed by citizens during the engagement activities performed in the second pilot phase concerns the possibility to book a public venue for different purposes. This service is already provided by the municipality of Trento; however, it is quite primitive as it consists of browsing a list of rooms and engaging directly with the responsible people over the phone. On the contrary, the app Trento Room Booking allows

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 32

users to access all essential information concerning a specific room - such as location, number of seats, intended use, technical equipment and contacts ( Figure 35 ) and to book the room directly from the app. Users can search for a specific room from a list or can visualize rooms on a map ( Figure 36 ). Alternatively, they can filter by availability, number of seats, distance, district, intended usage and costs ( Figure 37 ). Once a request for booking is accepted by the competent people, this information will be displayed in the section “My bookings” where users can also make changes.

Figure 35 - General information Figure 36 - Map of rooms available Figure 37 - Filters

The service is present in Google Play, WeLive Marketplace and WeLive Player.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 33

Figure 38 - Trento Room Booking in Google Play Figure 39 - Trento Room Booking in WeLive Player

Figure 40 - Trento Room Booking in WeLive Marketplace (Services)

4.3.2.2. Building Block A few more building blocks were published onto the WeLive platform during the population activities of the second pilot phase. Some of them constitute the bricks on which new public services have been developed or improvements of existing building blocks. Some other were implemented as a derivative of existing building blocks to improve their compatibility with the Visual Composer and thus be used within this tool to develop a

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 34

mockup/mashup application. Lastly, we are also going to describe an example of a building block exchanged with another pilot city. These building blocks are all hosted on the Trento open services platform, as explained in Section 4.2, or on the WeLive Cloudfoundry hosting environment and are published as WeLive compliant artifact onto the WeLive Marketplace (Services). New BBs for second pilot phase: “Trento Informer”: a 4-star building block that delivers information (events, notifications) related to the city of Trento and allows users to personalize their choice in receiving alerts about topics of their interest; this BB is used within the homonymous mobile app developed for pilot phase II. “Trento Room Booking”: a service that provides a functionality to search public rooms, filter the results as per use preferences; it also allows to check room availabilities in requested periods and to perform booking operation associated to logged in user account; this BB is used within the homonymous mobile app developed for pilot phase II. “Public Transport GTFS”: a building block derived from the Public Transport BB which provides the public transport information in the standard GTFS format; the service provides the information separately for different transport agencies. Visual Composer related BBs: “Logging BB for VC”: an ad hoc version of the homonymous WeLive core building block optimized to be used within the Visual Composer; it offers a set of instruments for validating, storing and analyzing the relevant events and activities both from within the WeLive platform components and from the 3rd part building blocks; these instruments come in the form of REST APIs and therefore programmatically available to the applications and components developed with different technologies and languages. “Route Planner for VC”: an ad hoc version of the homonymous Trento building block optimized to be used within the Visual Composer; it provides the functionality of multimodal route planner, enabling planning for public transport and a car, bicycle routes, considering also the bike sharing stations and parking lots nearby, etc. Besides, the service allows the user to store the planned routes and perform their monitoring, signaling possible problems (e.g., delays, strikes, accidents, etc.); currently, the service operates in the Trentino area. Exchanged BB: “Geolocator”: a very little service, ported from the Bilbao pilot, which provides inverse and forward geocoding; geocoding is the computational process of transforming a postal address description to a location on the Earth's surface (spatial representation in numerical coordinates); reverse geocoding, on the other hand, converts geographic coordinates to a description of a location, usually the name of a place or an addressable location. 4.3.2.3. Datasets As explained in Section 4.2, a list of datasets that are stored in the open data portal of the Trentino province completes the Trento environment. The data owned by the municipality have been imported into the Datasets tool of the WeLive framework and can be accessed from the Services section of the WeLive platform. While only 16 datasets were imported during pilot phase I, a number of 200 datasets are currently available in this section [41]. Among these, some new datasets have been used to improve existing apps, namely Trento Street

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 35

Cleaning has been considerably improved using a dataset related to road graphs [42] and dataset concerning street cleaning and no parking areas [43]. Dataset quality report As stated in section 3, the dataset quality report is divided in the broken link report and openness report. In Table 2, the summary of the broken link report for Trento city pilot can be seen.

Datasets with broken links Broken links % of broken links

10 25 9%

Table 2 – Number of broken links for Trento pilot.

Trento has 25 broken links distributed along 10 datasets. These links, shown in Table 3, are related to geolocation data and to “Rendiconto” series.

Dataset Resource Link

https://dev. WeLive .eu/ods/data GML http://webapps.comune.trento.it/cartografia/catalogo? set/comune-di-trento- db=base&sc=commercio&ly=civici_pubblici_esercizi&fr= localizzazione-pubblici-esercizi gml

https://dev. WeLive .eu/ods/data SHP http://webapps.comune.trento.it/cartografia/catalogo? set/comune-di-trento- db=base&sc=commercio&ly=civici_pubblici_esercizi&fr= localizzazione-pubblici-esercizi shp

https://dev. WeLive .eu/ods/data KML http://webapps.comune.trento.it/ca rtografia/catalogo? set/comune-di-trento- db=base&sc=commercio&ly=civici_pubblici_esercizi&fr= localizzazione-pubblici-esercizi kml

https://dev. WeLive .eu/ods/data DXF http://webapps.comune.trento.it/cartografia/catalogo? set/comune-di-trento- db=base&sc=commercio&ly=civici_pubblici_esercizi&fr= localizzazione-pubblici-esercizi dxf

https://dev. WeLive .eu/ods/data Entrate per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T110115/Entrate-per-categoria-2004.csv rendiconto-del-2004 2004

https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T110334/Spese-per-funzione-2004.csv rendiconto-del-2004 2004

https://dev. WeLive .eu/ods/data 2013 -03 - http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- 15T110334 15T110334/Spese-per-funzione-2004.csv rendiconto-del-2004 /Spese-per- funzione- 2004.csv

https://dev. WeLi ve .eu/ods/data Entrate per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T111231/Entrate-per-categoria-2005.csv rendiconto-del-2005 2005

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 36

https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T111343/Spese-per-funzione-2005.csv rendiconto-del-2005 2005 https://dev. WeLive .eu/ods/data Entrate per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T112119/Entrate-per-categoria-2006.csv rendiconto-del-2006 2006 https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T112223/Spese-per-funzione-2006.csv rendiconto-del-2006 2006 https://dev. WeLive .eu/ods/data Entrate per http://dati.tre ntino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T112411/Entrate-per-categoria-2007.csv rendiconto-del-2007 2007 https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T112534/Spese-per-funzione-2007.csv rendiconto-del-2007 2007 https://dev. WeLive .eu/ods/data Entrate per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T112653/Entrate-per-categoria-2008.csv rendiconto-del-2008 2008 https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T112738/Spese-per-funzione-2008.csv rendiconto-del-2008 2008 https://dev. WeLive .eu/ods/data Entrate per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T112918/Entrate-per-categoria-2009.csv rendiconto-del-2009 2009 https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T113057/Spese-per-funzione-2009.csv rendiconto-del-2009 2009 https://dev. WeLive .eu/ods/data Entrate per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T113618/Entrate-per-categoria-2010.csv rendiconto-del-2010 2010 https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T113709/Spese-per-funzione-2010.csv rendiconto-del-2010 2010 https://dev. WeLive .eu/ods/data Entrate per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- categoria 15T114506/Entrate-per-categoria-2011.csv rendiconto-del-2011 2011 https://dev. WeLive .eu/ods/data Spese per http://dati.trentino.it/storage/f/2013 -03 - set/comune-di-trento- funzione 15T114606/Spese-per-funzione-2011.csv rendiconto-del-2011 2011

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 37

https://dev. WeLive .eu/ods/data GML http://webapps.comune.trento.it/catalogo?db=base&sc set/comune-di-trento-stradario =toponomastica&ly=grafo_web&fr=gml

https://dev. WeLive .eu/ods/data SHP http:/ /webapps.comune.trento.it/catalogo?db=base&sc set/comune-di-trento-stradario =toponomastica&ly=grafo_web&fr=shp

https://dev. WeLive .eu/ods/data KML http://webapps.comune.trento.it/catalogo?db=base&sc set/comune-di-trento-stradario =toponomastica&ly=grafo_web&fr=kml

https://dev. WeLive .eu/ods/data DXF http://webapps.comune.trento.it/catalogo?db=base&sc set/comune-di-trento-stradario =toponomastica&ly=grafo_web&fr=dxf

Table 3 – Broken links for Trento pilot.

Regarding to the openness report, Table 4 shows the summary of the number of stars earned by datasets provided by Trento city pilot in the Linked Data 5-star scale. The most of them are located in the 3-star level of the scale, that is, they are published in an interoperable open format like CSV or JSON.

0 stars 1 star 2 stars 3 stars 4 stars 5 stars Average stars

3 1 0 82 0 0 2.9

Table 4 – Summary of starts earned by datasets from Trento pilot.

Recommendations The overall quality of datasets from Trento city pilot can be considered good, as they have few broken links and average rating in the 5-star scale for this pilot is 2.9, which is acceptable as most of the datasets are in the 3- star level. For increasing the quality of its datasets, Trento must fix the broken links or redirect old links to new ones if resources have been moved. For increasing the rating of the datasets, it must publish them as RDF, though this might be a complex task.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 38

5. BILBAO ENVIRONMENT 5.1. PROCESS FOLLOWED IN BILBAO FOR PLATFORM POPULATION The population of the WeLive platform for Bilbao environment is the final stage of a process launched at the beginning of the project and which involved the participation of several stakeholders in different online and physical activities. The process followed in Bilbao mainly comprised two stages as can be seen in Figure 41: A first phase named “Stakeholders Consultation Process” with the aim of collecting needs and ideas from stakeholders in order to identify requirements. This phase consisted of organizing and executing several activities involving external people representing several interest groups (citizens, representatives from companies and businesses from Bilbao and representatives from Bilbao public administration). Prior to this consultation process, several dissemination materials and communications assets were designed with the main purpose of ensuring the high engagement of representatives from each stakeholders group. The second phase was accomplished internally by involving WeLive consortium members and consisted of transforming these requirements, needs and ideas into a set of services, building blocks and datasets that address the stakeholders´ needs.

Figure 41 – Population Process in Bilbao

5.1.1. Phase 1 - Stakeholders Consultation Process As described in the deliverable D1.3 “WeLive scenarios, services and building blocks” [2], Bilbao task force decided to organize the stakeholders’ consultation process in four steps: Surveys Workshop Idea Contest Design games

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 39

5.1.1.1. Surveys The stakeholders´ consultation process in Bilbao was launched by distributing an online questionnaire by mail in order to identify which topics were most interesting for Bilbao stakeholders. From this activity, Bilbao task force obtained 303 questionnaires (270 questionnaires from citizens, 43 from companies’ representatives and 10 from public administration representatives). After the analysis of these questionnaires, it was concluded that most interesting areas of improvement for Bilbao stakeholders are Traffic, Culture and Health as well as the most demanded services were cultural agenda , real-time traffic/parking information , activities for children and information about pharmacies . 5.1.1.2. Workshops Based on the results from surveys in previous step (and discovered the most interesting areas of improvement in the city), three workshops were organized : one for each stakeholder group. In this activity for each area of interest, a table was developed describing discovered facts and ideas. The facts referred to the problems that Bilbao stakeholders have in their daily life. On the other hand, the ideas represented the solutions suggested by workshops participants for addressing each need. The demographic information of the people attending the three workshops were the following: Workshop with Citizens ‰ Workshop attendees were 14. 12 male and 2 female. 11 employed by a third party and 3 entrepreneurs/self-employed Workshop with companies representatives ‰ Workshop attendees were 10 All male 4 entrepreneurs/self-employed and 6 employed by a third party Workshop with public administration representatives ‰ Workshop attendees were 5 4 female and 1 male 5 civil servant 5.1.1.3. Idea Contest After meetings with the Bilbao Ekintza Municipal Society and the Youth Area, as the most involved areas with the project and with greater capacity of relationship with the target groups: Entrepreneurs, young people, ... two Ideas Contests were promoted: Bilbao Ekintza Idea Contest: Bilbao Ekintza is the department responsible for development economic and relationship with Entrepreneurs. It was held at the end of November 2016 in the Euskalduna Conference Hall (Bilbao). The summary for this idea contest is the following: Challenge Relevant Ideas Attendanc e Collect ideas for the development 9 Ideas were presented, focusing 20 people between 35 and 60 of potential mobile applications the most valued in Community of years of age with gender data and technological solutions that Entrepreneurs and SMEs, (80% men - 20% women). encourage interaction and Relationship between companies partnership among the different and Economic Development Area agents of the entrepreneurial of Bilbao environment in the City Council, Information on Co- city with the ultimate goal of working Centers. promoting Entrepreneurship and Economic Development in Bilbao.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 40

Youth Area Idea Contest: It was held at the mid-January 2017 at the Youth Multi-Activity center Bilbo Rock (Bilbao). The summary for this idea contest is the following: Challenge Relevant Ideas Attendance Define ideas that allow - through 16 Ideas were presented focusing 22 people, between 20 an app, web ... – disclose and the most valued by the Jury in and 40 years with consolidated share initiatives that are carried Communication of Events of the data on gender (40% men - 60% out in the city by groups, agents city to young people, Social women). and / or young people (in the areas network or Youth Community of of culture, creation, leisure and the city, Creation and centralized sports) in order to project a more dissemination of Events, etc. innovative, creative and cutting- edge Bilbao city.

5.1.1.4. Game Design Session This game design session goal was to come up with new public services ideas (three, one per each group defined in the session). The playful aim of the game was to win a contest for your team in which new digital services of the year 2020 were invented and their users and ways of use were described. The services were built in a creative way together in teams based on the material and user needs presented in the game. At the end of the game the service scenarios were presented and put to a vote. Each participant has 1 vote. Extra points were given for the best presentation (3 extra points). The game director guided the participants safely through the amazing stages. This session was held at mid-May 2017 in the Ingenio Room at University of Deusto. The summary for this idea contest is the following: Challenge Relevant Ideas Attendance There were two different Three ideas appeared as result of These participants were a mi xture challenges for this activity: this activity: of people with medium ICT skills Promotion of economic Creation of a Social and with low ICT skills. And male activity in different Network (or later called and female participation was neighborhoods of Bilbao "Community" after the balanced (total of 25 attendees). Generation of activity comment period) for around the Estuary of publication / reception of Bilbao. Promotion of activities, mainly sports. activities and uses of the Tourist guides service of Estuary of Bilbao and its the estuary of Bilbao surroundings. formed by seniors, retired ... who can tell the story of the estuary along with their own experience. Interactive platform, fed by the citizens that relate data and information of

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 41

the city, relative to the events and all the activity related to the river.

As result of this phase 1 for the platform population process, where main purpose was to know in detail the demands of Bilbao stakeholders, a set of scenarios and services were defined . 5.1.2. Phase 2 - Expectations and insights extraction Starting from the information about defined scenarios result from previous phase, a second step was launched. In this second step, Bilbao task force studied the viability of these scenarios and ideas by defining which building blocks, datasets and infrastructures were necessary to transform each of them into real assets and prototypes that could be further populated into the WeLive framework. This second phase involved the design and implementation of a set of assets by WeLive partners and required the participation if stakeholders during the testing phase to identify potential deficiencies and problems to be solved before the pilot phase II. In this Phase 2 of the process for platform population in Bilbao, we would like to emphasize on the relationship between the produced artefacts and the co-creation process by which they were devised. To do so, a table correlating the co-creation process activities and the resulting artifacts has been created.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 42 Co -Creation Idea / Issue of Interest Public Service generated Building Blocks generated Open Datasets used Activity Workshops with Most demanded services were Auzonet, Bilbon and BB Citizens voting, BB Users Restaurants, cider halls and cellars from stakeholders cultural agenda , real-time Bilbozkatu feedback, BB Users Ranking, Basque Country traffic/parking information , activities Nearest Point and Image Tourism offices from Basque Country for children and information about Uploader and In-app Tourist accommodations in Basque Country pharmacies questionnaires Inhabitants classified by neighborhood and sex (totals) Bilbao Ekintza Idea Social Network for entrepreneurs and Big Klub Geonames, Geoutilities, None Contest companies from Bilbao that allows Bilbao Ekintza Events and those users to register for Survey BB entrepreneurship related events and to get in touch with other users and event attendants. Youth Area Idea Provide a tool where yo ung people Bilbao Events Bilbao Agenda and Directions Bilbao’s local agenda Contest can promote events they are (eus-routes) organizing and also know the events agenda for the city of Bilbao. Game Design Community Social Network for None None None Session publication / reception of activities, mainly sports Tourist guides service of the estuary of Bilbao formed by seniors, retired ... who can tell the story of the estuary along with their own experience Interactive platform, fed by the citizens that relate data and information of the city, relative to the events and all the activity related to the river Apart from the already developed artifacts (ideas coming from the co-creation process), a hackathon is running in Bilbao. It was organized in three different sessions: End of September: contest presentation. WeLive Project objectives presentation together with previous co-creation activities held in the framework of the Project. WeLive platform presentation to support co-creation process, in particular, the following components were explained deeply: OIA, Marketplace and Visual Composer. End of October: development session. Here the participants could receive advice, both regarding the idea and the platform use. End of November: hackathon resolution. New ideas and services completely developed from SMEs and developers, using the Visual Composer. 5.2. INTEGRATION WITH LOCAL INFRASTRUCTURES Regarding to the integration with already existing local infrastructures, WeLive platform is integrated with Bilbao’s Open Data portal 141 [26] (Figure 42) through the Open Data Stack. The harvesting extension of the ODS allows harvesting metadata about datasets published in external platforms. In the case of Bilbao, the entire catalogue 1 of datasets is described using the W3C standard Data Catalog Vocabulary (DCAT) [44]. This DCAT catalogue shows metadata like the title, description and license of each dataset, resources associated to a dataset, format of these resources, etc.

Figure 42 – Bilbao´s Open Data portal.

The harvesting extension of the ODS allows harvesting metadata from datasets hosted in other platforms like CKAN or platforms describing their datasets using DCAT. The ODS extracts the metadata from this sources and replicates the datasets in WeLive platform. However, the original resource (the CSV, JSON, XLS, etc. file) is linked to the original source. In section 5.3.3, datasets harvested from Bilbao Open Data portal are described. For more documentation about the ODS please check the WeLive online documentation ([14]).

1 http://www.bilbao.net/opendata/es/catalogo/rdf

Figure 43 – DCAT harvester.

5.3. SERVICES, BUILDING BLOCKS AND DATASETS Bilbao’s task force has developed five services so far. All these services have been published into WeLive framework (WeLive Marketplace) as mobile applications. Bilbozkatu: app for allowing citizens of Bilbao vote and rate different proposals or ideas published by other citizens and/or the town hall. BilbOn: This service provides information about different public utilities and points of interest. This service uses a public dataset from Bilbao, and allows users to contribute with their own POIs. Auzonet: This app implements a social network that allows neighbors offer different solutions, based on geographical proximity and trust. Big Klub: App for keeping up to day with entrepreneurship events that take place in Bilbao and getting in touch with other entrepreneurs and companies. This Social Network also offers entrepreneurship- related news from Bilbao Ekintza. Bilbao Events: it is a tool where young people can promote the events they are organizing, and at the same time, know events created by the rest of users. Furthermore, it includes the different agendas from public entities, classified by type of event. 5.3.1. Services 5.3.1.1. Bilbozkatu This mobile application allows citizens of Bilbao voting and rating proposals and/or ideas launched by other citizens and/or the city council about different city concerns (i.e., best place for locating a new kids’ playing area, local projects’ definition, etc.). Through their contributions and votes, citizens have the opportunity to participate, collaborate and co-decide how they like their neighborhood to become. From the stakeholder consultation process where different stakeholders were involved in several workshops, it was identified a common need for all of them. The stakeholders wanted to be involved in the decision making process of Bilbao and to participate in the design of the city of the future. This was the main reason for creating an application like Bilbozkatu which is an app for digital democracy and citizen participation. Thanks to this app, the Bilbao city council is able to know which the most important concerns for the citizens are, and this information could be used for easing the decision-making processes.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 45

Figure 44 – Proposals filtering Figure 45 – List of Proposals Figure 46 – Detail of a Proposal, with their ratings and votes

Figure 47 – Map of proposals by Figure 48 – Comments in a proposal Figure 49 – Statistics of a proposal neighborhood

Figure 50 – Rating and commenting Figure 51 – Introducing a new Figure 52 – Main menu of the app a proposal request

Among its main functionalities, Bilbozkatu offers: Voting campaign publication. Campaign selection.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 46

Campaign voting by the citizens. Publication of the results of the voting. Information to neighbors. From the building blocks described in sections below, Bilbozkatu uses: “Users feedback” “Citizen voting” and “In-app questionnaire” Building Blocks. It has been developed under Ionic Framework, so as it is a multiplatform application. The new service is present in Google Play, WeLive Marketplace and WeLive Player.

Figure 53 – Bilbozkatu in Google Play screenshot

Figure 55 – Bilbozkatu in WeLive Marketplace Figure 54 – Bilbozkatu in WeLive Player

5.3.1.2. Auzonet Auzonet is a Social network for neighborhoods in Bilbao for providing solutions to the inhabitants of those neighborhoods, based on the proximity and confidence. The main purpose of this social application is to enable citizens to borrow the things they need from neighbors in less than 30 minutes. A citizen has the chance to show his/her needs with other neighborhoods as well as share the things he/she can offer to other people too. Bilbao citizens will be able to search in others offers or find something to lend to a neighborhood that has published his/her need. This mobile application contributes to create “community” which was one of the common needs proposed by several stakeholders during the stakeholders’ consultation process events.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 47

Auzonet key functionalities (Figure 56) are: Social network based on proximity and confidence Citizen/user registers into the service Introduce needs or things to borrow (Figure 57) Registered users will receive a push notification based on proximity and confidence User who borrows has the possibility to rate the service.

Figure 56 – List of Auzonet Figure 57 – Introduce needs or Figure 58 – Auzonet search screen functionalities things to borrow

Users post something they want to borrow, neighbours willing to lend things get a push notification to which they can respond in a single touch, and thus the borrowing process enabled. NEW FEATURES IN THE APP: included a new type of item to borrow (TIME). This new type of item allows to exchange time/favours, in addition to physical objects. This enhancement is based on the interviews to citizens previous to gamified session for Miribilla Neighbour Association (Inform Me event). From the building blocks described in sections below, Auzonet uses: Common Building Blocks: Map interface, Users feedback, Users ranking Core Building Blocks: logging, authentication, registry and query mapper Specific Building Block: Image Uploader It has been developed under Ionic Framework, so as it is a multiplatform application. The new service is present in Google Play, WeLive Marketplace and WeLive Player.

Figure 59 – Auzonet in Google Play screenshot

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 48

Figure 60 – Auzonet in WeLive Player Figure 61 – Auzonet in WeLive Marketplace

5.3.1.3. BilbOn This service provides information about public utilities of the city (i.e.: public toilettes, mailboxes, public bikes, stations, pharmacies etc.). It offers a catalogue of urban POIs, geolocated news and warnings, etc. The main purpose of this app is that citizens and visitors have more information to know better the city. Moreover, every POI can be enriched with information and contents provided by users. From the building blocks described in sections below, BilbOn uses: “Nearest Point” building block to find the nearest POI from user’s actual location. BilBon’s key functionalities are: Urban POIs geolocation. Search of interesting points based on user’s needs. POIs publication, enriching the context.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 49

Figure 62 – Filtering POIs created by citizens Figure 63 – POI search by category Figure 64 – POI search by text

Figure 65 – POIs located on a map Figure 66 – POIs located on a map Figure 67 – Details of a POI

Figure 68 – Searching by location Figure 69 – Introducing a new POI Figure 70 – Login

The new service is present in Google Play, WeLive Marketplace and WeLive Player.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 50

Figure 71 – Bilbon in Google Play screenshot

Figure 73 – Bilbon in WeLive Marketplace Figure 72 – Bilbon in WeLive Player

5.3.1.4. Big Klub This mobile application is a Social Network for entrepreneurs and companies from Bilbao that allows those users to register for entrepreneurship related events and to get in touch with other users and event attendants. Also, the app allows attendants to rate and give feedback about these events. Big Klub key functionalities are:

• Listing news from Bilbao Ekintza. Navigation through offered events. Registration to events. Filling in satisfaction questionnaires of events. • Filling in a satisfaction questionnaire of the app. • Searching for and contacting other users. From the building blocks described in sections below, Big Klub uses:

• Common Building Blocks: “Bilbao Ekintza Events”, “Survey BB” and “In-app questionnaires”. • Core Building Blocks: “Logging”, “AAC”, “WeLive Citizen Data Vault” (CDV), and “WeLive Liferay User Manager”. • Specific Building Block: “Big Klub BB”. It has been developed under Ionic Framework, so it represents is a multiplatform application.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 51

Figure 74– Events search by date or map Figure 75– App menu Figure 76– Bilbao Ekintza news

Figure 77 - Filling in user profile

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 52

The new service is present in Google Play, WeLive Marketplace and WeLive Player.

Figure 78 – Big Klub in Google Play screenshot

Figure 79 – Big Klub in WeLive Player

Figure 80 – Big klub in WeLive Marketplace

5.3.1.5. Bilbao Events The developed mobile application aims to solve existing problems in the communication of events organized by young people. The basic idea of the application is that they work as a tool where users can promote the events they are organizing, as well as, know the events created by the other users. In order to have a greater volume of activities, the agendas of the different public entities are incorporated. The objective of the Bilbao Events APP is the number of people who use this application to manage information related to events. This information can be of the following types: General information of the event: place, date, temperature, location, etc. There will be the possibility of searching through different categories. Specific information about the event: provided through the group chat by the people interested in the event or by the assistants themselves. This information may include: before the event; during the event and after the event. The idea is to create, promote and retain a Leisure Community for young people around the APP. Bilbao Events key functionalities are: Listing of events of the "Municipal Agenda of Bilbao", as well as the events created by the users of the App Browse events offered, the user could filter events, to help obtain the information you need. Filtering can be done by: Typology (Cinema, Courses, Scholarships, Workshops, Sports, Exhibitions, Conference, Congress, Music, Awards and Contests, Professional, Theater and Dance, Others) Dates Location

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 53

Group chat for each event, where users of the App can participate and express their opinion about the event The user has an interactive map where s/he can view the location of the events that are of interest, filtered by types, they can also find out what is the "fastest" way to get to the location of that event from the point where is found, choosing the mode of movement (car, bicycle or walking). Share an event on social networks. The user can share the information of the event, as well as the APP (for possible download), on their social networks or at least the applications they have installed on their mobile (WhatsApp, Facebook, Twitter, Instagram ...) Users can register their own events Administrator profile, which must approve the event that users upload (providing a delay of 24 hours). These admin users either validate the event and at that moment it will be published or rejected and a text will be written indicating the reason why its publication was rejected for the user who tried to register that event to see it. For this there will be a list of pending events to be published, that only administrators will see, once the event has been approved or rejected (by an administrator user), it will disappear from that list

Figure 81 – List of Bilbao Events Figure 82 – List of Events filtered by Figure 83 – Event Information Card functionalities Exhibitions

Figure 85 – Form to create new Figure 84 – Events Map Figure 86 – User Events administrator event

From the building blocks described in sections below, Bilbao Events uses: Common Building Blocks: “Map interface”, “Users feedback”, “Users ranking” Core Building Blocks: “logging”, “authentication”, “registry” and “query mapper”

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 54

Specific Building Block: “Bilbao Agenda” It has been developed under Ionic Framework, so as it is a multiplatform application. The new service is present in Google Play, WeLive Marketplace and WeLive Player.

Figure 87 – Bilbao Events in Google Play screenshot

Figure 88 – Bilbao Events in WeLive Player

Figure 89 – Bilbao Events in WeLive Marketplace

5.3.2. Building blocks The Bilbao city pilot provides some building blocks that are currently hosted on the project’s internal open services platform (a Cloudfoundry instance). These building blocks are published as WeLive compliant artifacts onto the WeLive Marketplace. The building blocks developed for the Bilbao pilot provide functionalities that are used by the different city services have been explained in section 5.2.1. The list of the building blocks currently provided inside the Bilbao city pilot is explained in the next subsections. 5.3.2.1. BB Citizens voting (Bilbozkatu) This building block allows users voting different proposals, ideas, etc. It is specific for Bilbozkatu app. These voting functionalities will be used in different applications and that is the reason why we have created a Building Block for it, so as it can be reused in various apps, optimizing and reducing the developing costs. This BB provides these methods: Get proposals (optionally, it is possible to determine how many registers to obtain from the database, and paginate them). Get proposals based on different criteria (area, category, text) Get the number of proposals grouped by area Get the details of the proposal Registered users can vote a proposal Registered users can publish a new proposal Users’ registration

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 55

5.3.2.2. BB Users feedback This BB provides functionalities for capturing users’ feedback (ratings, comments) for each proposal, idea, POI, etc. These feedback functionalities will be used in different applications, that is why we have created a Building Block for it, so as it can be reused in various apps, optimizing and reducing the developing costs. This BB is used in Bilbozkatu and provides these methods: Introducing feedback (for a specific proposal, comment and rating) Get feedbacks for a proposal Get the number of feedbacks after a given date and until a given date. Get the average rating of the feedbacks Offer a WADL of the service. 5.3.2.3. BB Users Ranking This BB allows generating a ranking of users for different services. These ranking functionalities will be used in different applications, which is the reason why we have created a Building Block for it, so as it can be reused in various apps, optimizing and reducing the developing costs. These are its main functionalities: Add users Rate a user See users’ ranking Get the users’ list Delete a users’ feedback Get the list of users of a service and object. 5.3.2.4. Nearest Point Finder This BB provides a basic functionality to those services requiring calculating the list points that are closer to a specific location. Its main functionality is to provide, from a list of possible map locations, the one that is the closest to the user specified location.

Figure 90 – Publication of the Nearest Point Finder BB in the WeLive Marketplace.

5.3.2.5. Image uploader

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 56

The BB provides functionality to simplify the management of user images inside services. The BB relies on Flick to store the user images and guarantees that only the owner of each image can access his/her corresponding images. The main functionalities of the building block are: Add image by user Retrieve image of by the user Tag image Retrieve images with specific tag

Figure 91 – Publication of the Image Uploader BB in the WeLive Marketplace.

5.3.2.6. Geonames This BB is aimed to provide an easy access to GeoNames data (https://geonames.org). The GeoNames geographical database covers all countries and contains over eleven million place names that are available for download free of charge. In particular, the BB provides methods to access the following functionality: roads, intersections, populations, time zones, weather, earthquakes info, etc.

Figure 92 – Publication of the Geonames BB in the WeLive Marketplace.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 57

5.3.2.1. Geoutilities It enables forward and reverse geocoding service. This can be done for a single element (only one address or coordinates) or for several elements. Not a current feature, but in a future, an update will be added with a service to calculate distance between 2 addresses or 2 coordinates.

Figure 93 – Publication of the Geoutilties BB in the WeLive Marketplace.

5.3.2.2. Bilbao Ekintza Events This building block is used to retrieve information about events organized in a city, filtering them by their location (distance) and by the dates and times supplied by a user. In addition, another filter associated to the price of the event could be supplied. The BB provides a standard API, which can be used by derivatives of this BB in other cities. A grounding of this BB should occur to foster its usage, i.e. the data sources will differ from city to city, in their format and way of accessing. This part will have to be customized when adapted to each city.

Figure 94 – Publication of the Geoutilties BB in the WeLive Marketplace.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 58

In addition, the BB provides an administrative interface that can be used by the municipality to manage the event data.

Figure 95 – Administration interface for the Bilbao Ekintza Events BB.

5.3.2.3. In-app questionnaires This BB provides functionality to create online questionnaires that can be shown inside mobile applications in order to retrieve information about the application usage. The functionality provided by the Building Block includes the creation of questionnaires with multiple questions and different response types (free text, closed range) and support for internationalization in multiple languages. The stored responses can be later retrieved in CSV format by the application owners. The main functionalities of the building block are: Create a questionnaire Add questions to a questionnaire Add a translation for a question Add allowed responses for a question Retrieve a questionnaire and its associated responses in a specific language Store responses for a questionnaire Retrieve all the responses in CSV format for a specific application or pilot.

Figure 96 – Publication of the In-app BB in the WeLive Marketplace.

5.3.2.4. Survey BB This BB is an extension of the functionality provided by the In-app questionnaires building block. In addition to the previous functionality, it includes a management web page that allows editing the questions. The new functionality has been added to a new BB in order to maintain the compatibility with the applications using the in-app questionnaires.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 59

Figure 97 – Publication of the Survey BB in the WeLive Marketplace.

Figure 98 – Administration interface for the Survey BB.

5.3.2.5. Bilbao Agenda BB This BB provides access to the Bilbao event agenda. It contains methods to query and update the data using the functionality provided by the ODS. In addition, the BB solves some issues detected (missing data) by scrapping some external sources and completing the data presented to the user through the BB.

Figure 99 – Publication of the Survey BB in the WeLive Marketplace.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 60

5.3.2.6. Directions (eus-routes) This is the building block which retrieves indications on how to go from one place to another. It contains methods to obtain the data in different formats depending on the needs of the user.

Figure 100 – Publication of the directions (eus-routes) BB in the WeLive Marketplace.

5.3.3. Datasets WeLive platform hosts 166 datasets for Bilbao pilot. These datasets can be classified as follows: 158 datasets harvested from Bilbao Open Data portal. 3 datasets harvested from Open Data Euskadi [25] portal (open data from Basque Government). 4 datasets generated by applications and building blocks from Bilbao pilot (BilbOn, Auzonet, Bilbao Events and Bilbao Ekintza Eventos). 1 dataset generated by the ODS from data gathered from Twitter. Among datasets harvested from Bilbao Open Data portal, we can find datasets related to different topics like demography, culture and leisure, economy, environment, public transportation or tourism. These datasets are published in the following formats: 104 CSV documents, 40 RSS, 39 JSON, 36 XML, 3 XLS , and 2 RDF. For its usage in Bilbon application, we have harvested some datasets from Open Data Euskadi. These datasets are related with hostelry and tourism resources in the Basque Country. Bilbon only uses data about points of interests from Bilbao, but the application could be easily extended to cover the entire Basque Country. Datasets harvested from Open Data Euskadi portal are the following ones: Restaurantes, sidrerías y bodegas de Euskadi (restaurants, cider halls and cellars from Basque Country): this dataset contains metadata and geolocation data about these hostelry locations. Oficinas de turismo de Euskadi (tourism offices from Basque Country): this dataset contains metadata and geolocation data about tourism offices in Basque Country. Alojamientos turísticos de Euskadi (tourist accommodations in Basque Country): this dataset describes metadata and geolocation data about tourist accommodations in Basque Country. These datasets contain their resources described in JSON, CSV and XLS formats.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 61

In addition to the harvesting of already existing datasets, three new datasets have been created for the WeLive project: two related to apps developed within the pilot and one with data scrapped from social networks. The datasets related to apps are the following ones: Bilbon User POIs: this dataset stores Points of Interest created by Bilbon app users. In addition to POIs published by datasets from Open Data Euskadi, users can create their custom POIs, sharing them with other users. Auzonet: this dataset contains two resources. The first one, “Locations” , describes different neighborhoods from Bilbao, including their geolocation. The other one, “Categories” , describes different categories used by the app. These two datasets contain their resources described in JSON format. On the other hand, we have created a new dataset using the Twitter Topic Harvester provided by the ODS. This dataset looks for tweets related to a set of words related to the categories of ideas from the Open Innovation Area. These tweets are analyzed in order to generate a set of topics that could be interesting for the citizens of Bilbao. Resultant topics are published in JSON format. In addition to these datasets, there are four datasets used by different applications and building blocks developed within the WeLive platform during the second pilot phase. The first one is “Bilbozkatu”, an app which uses the dataset named “ Habitantes por barrio y sexo (totales)” (Inhabitants classified by neighborhood and sex (totals)), describing different neighborhoods from Bilbao and some demographic data about them. The second one is “Bilbao Events”, an app which uses the dataset named “Agenda Municipal de Bilbao” (Bilbao’s local agenda). The later ones are “Bilbao Ekintza Events” and “Bilbao Ekintza Surveys ”, used by “Bilbao Ekintza Eventos” building block. 5.3.3.1. Dataset quality report In Table 5, the summary of the broken link report for Bilbao city pilot can be seen.

Datasets with broken links Broken links % of broken links

5 6 2%

Table 5 – Number of broken links for Bilbao pilot.

Bilbao pilot has six broken links distributed among five datasets. From these datasets, three of them were harvested from Open Data Euskadi [25], the open data portal from Basque Government. The remaining datasets, shown at Table 6, they were not offline at all, but the server lasts more than 30 seconds on serving them, which could produce problems when consuming them with an external client.

Dataset Resource Link

https://dev. WeLive .eu/ods/data RDF http://www.bilbao.net/cs/Satellite?c=OD_Dataset_FA& set/catalogo-de-datos- cid=1272994251637&language=es&pageid=127299417 publicados-en-el-portal-bilbao- 6309&pagename=Bilbaonet/OD_Catalogo_FA/OD_pinta open-data rDetalleCatalogo&site=Bilbaonet

https://dev. WeLive .eu/ods/data JSON http://www.bilbao.net/cs/Satellite?c=Page&language=e set/guia-de-asociaciones-de- s&pageid=3000066645&pagename=Bilbaonet/Page/OD bilbao _guiaAsociaciones&formato=JSON

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 62

https://dev. WeLive .eu/ods/data XML http://www.bilbao.net/cs/Satellite?c=Page&language=e set/guia-de-asociaciones-de- s&pageid=3000066645&pagename=Bilbaonet/Page/OD bilbao _guiaAsociaciones&formato=XML

Table 6 – Broken links for Bilbao pilot.

Regarding to the openness report, Table 7 shows the summary of the number of stars earned by datasets provided by Bilbao city pilot in the Linked Data 5-star scale. There are 160 datasets with 0 stars, 7 with 4 stars and 1 with 5 stars. The main reason to be too many datasets with 0 stars is that they have not a license specified in the DCAT catalogue from Bilbao Open Data [26] portal from which the ODS harvests the datasets, so they can’t be labelled as Open Data. For fixing this issue, the property http://purl.org/dc/terms/license must be added to each dataset description on the DCAT catalogue. The most of them are located in the 3-star level of the scale, that is, they are published in an interoperable open format like CSV or JSON.

0 stars 1 star 2 stars 3 stars 4 stars 5 stars Average stars

160 0 0 7 0 1 0.2

Table 7 – Summary of starts earned by datasets from Trento pilot.

5.3.3.2. Recommendations For fixing the resources that takes more than 30 seconds to be fectched, Bilbao City council should decrease the response time of the server on which they are hosted or, if these resources are generated dynamically for each request, a cache server should be deployed. Regarding to the openness report, datasets with 0 stars could be fixed easily adding the http://purl.org/dc/terms/license to the DCAT catalogue, increasing they rating at least to 2 or 3 stars. Other datasets are rated with 0 stars because they are published as RSS, a format which is not considered as interoperable. Regarding to datasets with a score of 3 stars, they must evolve from CSV or JSON to RDF to score at least 4 stars.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 63

6. HELSINKI-UUSIMAA ENVIRONMENT This section describes the services, building blocks and datasets prepared for the first phase of the Finnish pilot. 6.1. PROCESS FOLLOWED IN FINLAND FOR PLATFORM POPULATION In the first pilot phase, the stakeholders’ co-creation and engagement process in Helsinki-Uusimaa region included methods like 1) Survey and 2) Design game. 1) The web-based survey was published in the early phase of the project to collect initial information about users’ and stakeholders’ needs, hopes and wishes regarding to future digital services. The survey method enables involving through web based channels a high amount of citizens and stakeholders and thereby obtaining a large quantity of information. The first part of the survey contained questions about participants’ age, occupation, where they live/is company stablished/public administration belongs, usage of ICT technologies and digital services, their interests in different public sectors, open data published by public administrations and data assets freely offered by companies. The second part of the survey contained open-ended questions about digital services that participants would like to use or their relatives/friends would like to use, data to be opened by companies, open data wanted by companies, open data gathered by public administrations and its usefulness, in which projects related to open data is public administration participating and open data resources to be published by public administrations. Additionally, participants’ contact information was asked for later participation. The results from survey indicated that citizens and stakeholders in Helsinki-Uusimaa region were more interested in the areas of residence, health and sport (Figure 101). Totally 307 people from the Capital Region of Finland took part in the survey: 267 citizens, 16 company and 24 city representatives.

Type of interest Percentage Residence 64,60% Health 64,16% Sports 63,27% Maps 61,06% Traffic 59,73% Tourism 57,96% Culture 54,87% Education and training 50,00% Work 46,02% Family and social services 37,17% Environment 34,96% Finance and taxation 32,30% Safety 25,66% Communication 25,66% Zoning 21,24% Democracy 20,35% Management 20,35% Properties 19,03% Legal protection 19,03% Livelihood 18,58% Building 14,16% Other 3,98% Figure 101 – Citizens´ and stakeholders’ interests in different public sectors in Helsinki-Uusimaa region

2) A design game, based on the results from the survey, was created. The design game helped to facilitate a user-centered design process for cross-disciplinary design groups early in the design process. Moreover, the design game enabled framing collaborative design activities in a game format, arguably improves idea generation and communication between citizens, public administration and companies. The end result of the design game session was new service ideas, scenarios and needed data assets.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 64

Altogether, four design game sessions was arranged in May 2015. Each game session attended citizens and representatives from companies and public administration and the session took approx. three hours which during participants developed more concrete and detailed scenarios based on needs and ideas revealed in web based survey research. In the beginning of the game session the participants chose five different personas for whom they would like to design a new digital service. Then participants chose five interesting user needs to the personas. After that participants chose needed data assets in order to create wanted digital service. In the last phase participants descried the digital service in words and pictures. End of the game session participants presented the ideas to other teams and then they voted the best ideas. Total 10 initial digital service concepts (see Figure 102) were created in four game sessions. 34 persons in total took part in the game events: 32 participants in the design games were citizens, one company and one city representatives also participated.

Figure 102 – Example: result of the design game

In the second pilot phase, the stakeholders’ co-creation and engagement process in Helsinki-Uusimaa region is based on a three-step co-creation approach ( Figure 103 ), which is the basis of WeLive project. This model acts as a parent model of the co-creation in Finnish engagement process. The more specific model ( Figure 104 ) has formed during the pilots and aims to enhance collaborative innovation in the cities. This model is the defining element of the Helsinki-Uusimaa co-creation and engagement process. The main factor is that both, digital (WeLive platform) and physical (meetings and workshops) manner of approach are included in the service development and the engagement process, and that the co-creation is the linchpin of the building block and application development and production. All the created services should be based on real life needs of the citizens and the identified challenges of the cities and municipalities, therefore citizens and public administration representatives are part of the development process during the whole cycle, acting as prosumers. The stakeholders’ co-creation and engagement process includes methods like planning meetings and workshops, design games, concept creation and citizen engagement, WeLive seminars and application

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 65

development. The main aspects of the collaborative innovation process are Needs & Challenge identification, Idea generation, Idea selection, Development, Implementation, Exploitation & Dissemination and the iterative nature of the whole co-creation cycle.

Figure 103 - Three step co-creation process.

Figure 104 - Collaborative innovation process [21].

6.1.1. Need and challenge identification The basis of the digital service production and development is the need and challenge identification phase. Therefore the created applications are based on actual real life needs. Vantaa City has been active orchestrator and organizer of the events and engagement activities with the support of Laurea and during the project, the identification process has included several workshops between Laurea and Vantaa City, and also since the beginning of 2016, Vantaa’s internal workshops with its different departments. In addition, a conducted survey in 2015 defined the needs of the citizens of Vantaa and brought up that health and sports are the most important themes for the citizens. Laurea also created a challenge call, a contest to generate digital service

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 66

ideas. All these activities support Vantaa City’s strategic aim to increase its citizens’ motivation towards sports and welfare. In addition, more needs have been identified during the project in WeLive Design Game sessions and Laurea’s Master’s degree courses’ engagement processes and persona creation. In parallel, winner developer team of the first pilot phase’s idea contest continues developing their service concept with the help of city of Vantaa and Laurea. 6.1.1.1. Planning meetings and workshops The core of the outcomes, events, applications and generated service ideas in the second pilot phase has been the collaboration between Laurea and its partners, especially Vantaa city. The first step in spring 2017 was a planning meeting, in which the representatives of the City of Vantaa and Laurea University of Applied Sciences discussed about the insights and expectations regarding to the future service production in Vantaa. The main element of the discussions was the idea of having services centralized in a physical space which provides various public services for the Vantaa’s citizens. In addition, several meetings between the Vantaa City representatives and Laurea were held during the spring to elaborate the goals of the service design and production collaboration. The essential element of the collaboration between Laurea and Vantaa has been a cluster collaboration with the Six Cities Strategy (6Aika Strategy) [20], in which the six largest cities in Finland have joined forces to tackle urban challenges by producing urban services on three focus areas: Open innovation platforms, Open data and interfaces, and Open participation and customership . All development work strives towards communality, openness and accessibility. In the WeLive project, Laurea has been able to establish a collaboration with the City of Vantaa (Figure 105 ) within the Open data and interfaces focus area. In the Open data and interfaces focus area, the participant cities open up their data stores to be utilized by the entire city community by developing joint operating models, and publishing platforms and interfaces. The particular emphasis is placed on opening up data that benefits business, because activating businesses and developers to utilize the data is seen as the key to the successful implementation of the focus area.

Figure 105 - The concept creation collaboration structure in Vantaa City’s point of view

6.1.1.2. Needs During the spring 2017, Vantaa City organization presented their needs and challenges ( Figure 106 ) regarding to the service production to the Laurea’s Master’s degree classes, in which the students created digital service concepts to match the needs. The collaboration with Vantaa City has been a steering factor in concept creation

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 67

process and consequently the created concepts are based on the empirical and research data conducted by the city. In addition, a larger need basis was formed during the pilot phases one and two as more empirical data were collected. As an outcome of the user engagement, 152 service needs in 22 themes were identified ( Figure 107 ) and also added into the WeLive-platform. The needs are also present in the WeLive Design Game 2.0 to design new services based on realistic needs. Children’s sport facilities, sport facilities for beginners, camping site info and social media for sports are few examples among the identified needs in the popular sport theme.

Figure 106 - The challenge themes presented by the City of Vantaa in spring 2017

Figure 107 - Total number of 152 identified needs in thematic categorization

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 68

Another remarkable collaboration starts in the autumn 2017 as International Organization for Migration (IOM) will present challenges for the Laurea’s Master’s degree courses’ students. The challenges regards to the enhancement of the social services in terms of communication in a situation, in which there is no common language between a customer and healthcare staff. The subject matter is very topical due to the increased migration and immigration in the EU. 6.1.2. Idea generation Citizens and public administrations present needs and challenges which are collected via different engagement methods such as surveys, workshops and design game sessions. The presented needs are forwarded to both, physical innovation process and a digital platform, which refers to WeLive Platform. As an example, Vantaa City aims to motivate its citizens towards healthier life and they presented the challenge to Laurea. In parallel, citizens shared their needs to easily find sport and welfare locations and facilities. These have led to multiple approaches including design game sessions and master’s degree courses’ concept creation. 6.1.2.1. Concepts As a response to the results of the survey conducted in 2015 and the challenges and needs Vantaa city had identified in its research and workshops, dozens of digital service concept ideas were generated with multiple methods. In the concept creation process during the spring 2017 master’s degree courses, 74 citizens with various backgrounds ( Figure 108 , Figure 109 ) were engaged and as a result 25 digital service concepts ( Figure 110 ) were generated. The concept creation process is an obvious example showing the concrete correlation between the ongoing user engagement and the developed service concepts. The concepts are not based on just a marketing research or benchmarking, but on interviews and real problems, needs and insights of the users. SMEs were also involved in the idea generation process via the collaboration between Laurea and the Six Cities Strategy. The sport theme was identified as the most crucial one and many of the created concepts were based on sports or wellbeing. Good examples of the created concepts are “Movester” ( Figure 111 ), a sport application for busy citizens to fit their schedules and sport hobbies, and “Tendo” ( Figure 111 ), a digital platform including data of the city’s sport facilities. “Sportit”, further developed digital sport service showing city’s sport facilities and offering information about them, is a combination of the created concept ideas. In addition, as a result of the three Design Game sessions, 37 service concept ideas were generated. The concepts are not described as specifically as the ones created in the master’s degree courses, but act as a valuable resource in the research and service development process. In the design game sessions, also more needs were identified and forwarded to the WeLive Platform. During the autumn 2017, in the new Laurea’s master’s degree courses, more citizens will be engaged and therefore new concept ideas will be generated, based on gathered empirical material. There will be new digital service concepts as a response to the challenges presented by the City of Vantaa and International Organization for Migration. In addition, new Design Game sessions with WeLive Design Game 2.0, including the renewed needs, personas and datasets will generate more digital service concept ideas.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 69

Figure 108 - Master’s Courses’ engaged citizens’ demographics - Age

Figure 109 - Master’s Courses’ engaged citizens' demographics – Stakeholder type and ICT skills

Figure 110 - Digital service concepts created in the master’s coursers in thematic categorization

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 70

Figure 111 - Movester and Tendo applications

The whole concept creation process is based on the co-creation and iterative Service Design (Double Diamond) process (Figure 112), in which the users of the service are involved to participate into the development throughout the process. The double diamond model is particularly suitable for structuring a course with external collaboration and user involvement in the development of solutions. The model is inspired by the professional design process that entrails emphasis on problem analysis as the basis for creating a solution for an external client [19]. The key element of the model is the four main stages across two adjacent diamonds. The problematization and understanding of a problem are equally important. Each of the four stages is characterized by either convergent or divergent thinking [19]. The stages are [19]: Discover –identify, research and understand the initial problem Define – limit and define a clear problem to be solved Develop – focus on and develop a solution Deliver – test and evaluate, ready the concept for production and launch

Figure 112 - “Double Diamond” process model [22]

6.1.2.2. Design game session Along with the ongoing development work, WeLive Design Game sessions ( Figure 113 ) have been held to increase the number of the generated service concept ideas and to engage more people in the co-creation

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 71

process. During the spring 2017, 37 digital service concept ideas in 10 themes were generated in three Design Game sessions with the engagement of 64 people (Figure 114 , Figure 115 ). Rideshares, job applying services, services for disabled people and social culture services are few examples of the generated ideas. During the summer, Design Game was updated based on the empirical material, and the personas, need cards and datasets were renewed. The renewed needs were also added to the WeLive platform. The Design game 2.0 was released in early October and used in multiple sessions during the autumn. The game will be tested within the Master’s degree courses of Laurea.

Figure 113 - Design game session.

Figure 114 - Design Game sessions’ engaged citizens’ demographics - Age

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 72

Figure 115 - Design Game sessions’ engaged citizens’ demographics – Stakeholder type and ICT skills

6.1.2.3. WeLive Design Game 2.0 The aim of developing WeLive Design Game 2.0 was to improve its effectiveness in service design. The new game’s most distinctive feature compared to the previous version is the renewed cards. The majority of the renewed dataset cards ( Figure 116 ) are based on the real datasets available in Helsinki Region Infoshare. The renewed user need cards’ ( Figure 116 ) content is based on more inclusive research data and the renewed persona cards ( Figure 116 ) are designed to be more realistic and therefore more approachable for the players. There is more diversity among the personas in terms of socio-economic status. In addition, all the renewed cards have new visual design. Design Game 2.0 was ready to be played in October 2017 and there will be 11 game sessions held after the release. Five sessions will be executed either in Tikkurila Library or Koivukylä’s Service Space at Vantaa. Koivukylä’s Service Space case is a distinctive link to the spring 2017 discussions between the Vantaa City’s and Laurea representatives, in which the centralized service space idea was a very essential element. The Koivukylä’s service space is based on a participatory innovation co-creation service design and the WeLive Design game sessions are significant part of the entirety and the service production methodology screening process. The service space is an effective platform to engage citizens with real needs and with different backgrounds.

Figure 116 - WeLive Design Game 2.0 renewed cards: persona, user need and datasets

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 73

6.1.3. Idea selection 6.1.3.1. WeLive seminars The pilot phase 2 includes two WeLive Seminars. WeLive Seminar is a networking event related to open data usage, co-creation and innovation, also promoting the WeLive -project and platform. The fourth seminar ( Figure 117 ) was arranged at May 10, 2017 in cooperation with the City of Vantaa. The seminar addressed such themes as innovation, open data, crowdsourcing and co-creation. The event engaged students, company representatives, and Vantaa and Espoo city organization representatives ( Figure 118 ). After the speakers’ presentations on each theme, the master’s degree students presented their created concept ideas to the attendees gaining their interest in the works. Vantaa city representatives estimated the concepts’ value based on the criteria ( Table 8) and especially the sport and welfare concepts gained interest. As a result of combining the best elements of multiple concepts, Sportit application was created and taken into a further development. The ongoing liaison between Laurea and the Vantaa City’s responsible representative was fruitful and considerably helped to plan and execute the fourth WeLive seminar. The fifth WeLive seminar has been arranged in the autumn 2017. The event aimed to increase the visibility of the service production collaboration cases between Laurea and its stakeholders Vantaa City and International Organization for Migration. In addition, new digital service concept ideas were presented to the participants to gain interest and get the ideas into the further development.

Figure 117 - WeLive Seminar 4

Figure 118 - WeLive Seminar attendees’ demographics – Stakeholder type

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 74

City’s Point of view Citizen’s point of view

1. Matches for the WeLive theme Matches for the WeLive theme

2. Can be utilized in the public sector and can have Promising in terms of usefulness and impact an impact on the society

3. Illustrative and high-level description and Illustrative and high-level description and presentation presentation

4. Novel innovative digital service Novel innovative digital service

Table 8 - Concept evaluation criteria

6.1.4. Development The development phase is an iterative process of multiple phases including the first development until the release of the initial versions of the services, and to following development phases to improve the applications’ usability and user experience by using the feedback provided by the users and alpha testers. 6.1.4.1. Application development The minimum viable versions of the second pilot phase applications were released in the summer 2017. Sportit application was developed, preliminarily evaluated and noticed to have potential so the development and tests continued during the autumn in several development workshops participated by a dedicated developer groups including 23 developers to focus on the further development of the application’s features and usability. The key point is to increase application’s motivational features. Why should the users use the application regularly? During the autumn, three alpha tests were arranged and they pointed out several issues regarding mostly to usability and user experience. Look & feel was not as smooth as should be and not all of the features functioned properly. These issues were taken into examination and used to improve and develop applications further. A specified competition will be arranged in November to motivate developers to develop Sportit application further and improve its features, user experience and usability. 6.1.4.2. Citizen engagement The user engagement activities have been a crucial element in service production and service design during the second pilot phase. The service needs basis has been created from the empirical findings based on real life problems. The service development is based on an ongoing user engagement and an iterative prosumer based manner of approach. Citizens with different socio-economic backgrounds ( Table 9), including vulnerable groups like unemployed and elderly, have participated in various events and shared their views on their needs for digital services. The insights about the interest towards sports and culture were gained from the survey answered by citizens, which helped to define the themes for the Master’s degree digital service concepts. Especially the sport theme gained a lot of interest both in the survey and in the concept creation. This verifies the concrete correlation between the interests regarding the services, and the created concept ideas. Sportit, Helsinki City Museums and Helsinki City Bikes applications were developed, preliminarily evaluated, tested and released. The development will continue in a user-centered manner and Sportit application got a focused developer groups developing its features further during the autumn. The service development and co-creation activity aim to strengthen the innovative, platform-based service production and design. More prosumer way of engagement in service design occurred during autumn 2017.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 75

The essential element of the application development is the iterative nature aiming to improve the services in each development cycle.

EVENTS PARTICIPANTS FIRST PILOT PHASE 759 3 WELIVE DESIGN GAME SESSIONS 103 EVALUATIONS AND TESTS 34 SEMINARS 146 EXHIBITIONS 80 WORKSHOPS 94 WEB SURVEY 302 SECOND PILOT PHASE 267 4 WELIVE DESIGN GAME SESSIONS 85 ENGAGED PEOPLE IN MASTER’S CLASSES 78 SERVICE PLATFORM PLANNING WORKSHOP 20 WELIVE 4 -SEMINAR 84 OVERALL 1026 Table 9 - Engaged people until 5.10.2017

6.1.5. Implementation The implementation phase of the created services is based on an iterative approach. The first released versions are not the final ones and they enter into another cycle of development. For example, during the second pilot phase, Sportit application was developed and released in summer 2017 and after that it entered into a second iteration phase, which included alpha tests and dedicated groups of developers aimed at increasing the application’s usability and user experience. After the second development phase, there will be an upgraded application to be tested and to enter next iteration phase, and to be exploited and disseminated. The implementation phase is executed in co-implementation manner. The aim is to create a website for the application development for all the interested developers to use the development possibilities of the application for their own purposes. This will also include exploitation and dissemination possibilities of the application features and components. 6.1.6. Exploitation/Dissemination Based on the conducted research of the needs, challenges and service ideas, suitable datasets and building blocks have been added into WeLive-platform for the developers to exploit. These are significant components of the service development. 6.1.6.1. Datasets The majority of the presented datasets ( Figure 119 ) are collected from the Helsinki Region Infoshare (HRI), which acts as a data repository in the Helsinki Region. WeLive-platform contains examples of the datasets. The added datasets support the concepts and the user’s needs gathered in the research and concept creation process. The platform includes datasets like Helsinki Area Service Map, Buildings of Espoo and Population projection in the Metropolitan Area in 2015-2024. The Helsinki Region Infoshare service [18] aims to make regional information quickly and easily accessible to all. Helsinki, Espoo, Vantaa and Kauniainen open their data via HRI and the data can be used in research and development activities, decision-making, visualization, data journalism and in the development of applications. The published data is mainly statistical, giving a comprehensive and diverse view on different urban phenomena, such as living conditions, traffic, economics, environment, employment and well-being. A great

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 76

quantity of the data is GIS based. Using the data is free and citizens, businesses, universities, research facilities, municipal administration or anyone interested in open data, can participate. The data is ready to be used and there are no limitations on users.

Figure 119 - Thematic datasets included in WeLive Design Game 2.0 and WeLive-Platform (155 datasets)

6.1.7. Stakeholders 6.1.7.1. Citizens and developers Citizens and developers are the foundation of the digital service production and platform population. The services are based on the needs of citizens and they are developed by the developers, and as a response to the feedback of the citizens. 6.1.7.2. Public administrations Vantaa city has been a major orchestrator of the need identification process and the development and idea selection phases. Vantaa also made possible to engage a great number of attendees in the WeLive Seminars, by using its networks. 6.1.7.3. Laurea Laurea has been facilitating and supporting the whole collaborative innovation cycle. By arranging WeLive Design Game sessions, concept creation in the master’s degree courses and different events, Laurea has gathered different actors to co-create and co-develop new digital service ideas. 6.2. DESIGN PRINCIPLES The design game sessions described in the previous Section created many great ideas – some more realistic to implement than the others. The Finnish Task Force members (LAUREA and CNS) made the final decision on which ideas to implement for the first WeLive pilot phase by taking into account the technical feasibility of the

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 77

ideas and available resources to implement them. An important criterion behind the decision was that services should support each other and base (at least partially) on a common set of building blocks. The selected Finnish pilot services base on a common theme and exchange information through a shared database of geographic data called the “GeoDB”. The GeoDB comprises data derived from various open datasets and is extended with data submitted by application users. The ambitious goal behind the services has been to create a framework to handle, collect, combine, utilize and visualize all location-based data by common means and tools (the building blocks) – despite of the origin and original format of the data. Figure 120 shows the relationships and roles of the applications and their potential target audience.

Figure 120 – Finnish pilot services

Another common theme has been to study and enable business models for the services and building blocks. Therefore, all Finnish first pilot services, building blocks and the GeoDB are hosted in the CNS Hosting Environment, which keeps track on building block usage and provides means to fully control access to services. During the first and the second pilot phases, all services are available free of charge to all registered WeLive users so real business models or payments are not yet applied in practice. However, detailed transaction based statistics collected by the CNS environment allows analyzing the business potential and hosting costs of the artefacts which helps in selecting the appropriate business models for WeLive artefacts. The CNS Hosting Environment takes care of creating HTTP call interfaces and API specifications required for WeLive-compatible building blocks. Inside the CNS environment, actual data processing steps are first implemented and deployed as “Data Refining Solutions” and then mapped to building block features. Finally, the building block is published to generate a REST API that can be called by applications. Figure 121 shows the overall architecture of the Finnish pilot services.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 78

Figure 121 – Architecture overview for Finnish pilot services hosted in the CNS environment

6.3. SERVICES 6.3.1. Pilot phase 1 services Three new applications have been created for the first phase of the Finnish Pilot: My Polls, My Opinion and My Neighbourhood. These applications are closely related to each other as explained in Section 6.2. The following subsections briefly describe the applications and their main features. Several technical improvements and updates have been made to the applications for the second pilot phase. They have been converted to use the new Vaadin web application framework version 8, which is significantly different from the previous version 7. In addition, other applied Java libraries have been updated to the latest versions. However, the biggest technical improvement was to start using automatically generated client libraries when calling the building blocks, instead of using manually programmed client-side code as in the first versions. The client libraries are generated in the CNS Marketplace by combining REST APIs of all BB dependencies into unified application-specific API. The use of client code generators guarantees that applications are always calling the building blocks and parsing the responses correctly. Any change to building block call interfaces, such as added or modified parameters, will cause updates to the client code library as well that are easy to notice from version control logs. Significant changes will cause compile time errors in the application source code and force updating the applications accordingly – which is only a good thing. Earlier, it was very hard to keep track of API changes and any missed update could have caused application malfunctions.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 79

6.3.1.1. My Polls The My Polls application allows creating and managing location based polls (“geo-polls”) and viewing statistics and trends for existing geo-polls. Each geo-poll includes a simple question to be asked from citizens (e.g. “How safe is traffic at this location?”) and can be associated to one or more locations for which the question is relevant. Each geo-poll must be associated to an observable attribute (e.g. “safety”, “proximity” or “cleanness”) and a tag (e.g. “traffic”, “public services” or “park”) which together define the perspective and value range for the poll. Use of common well-defined attributes and tags for all geo-polls makes the results comparable and allows combining them with information extracted from open data sets that are mapped to the same attributes and tags. My Polls is the most convenient to use as a web application but is also available as an Android application. The application includes multiple views for different functionality. Users can switch between application views from left side of the top menu bar shown in Figure 122. In the web browser version, there is a separate button for each view. In the mobile version, there is drop-down menu including a list of views.

Figure 122 – My Polls menu

The main features of the application are easy to access via the application menu: The 'My Polls' view shows user’s current polls and allows adding and editing polls (Figure 123). The 'Charts' view shows statistics on answers submitted to user’s polls as pie charts (Figure 124). The 'Heatmap' view shows a heatmap visualization summarizing user’s poll results. Colors of the heatmap represent the average of given answers on that area (Figure 125). The 'Info' view shows information about the application and a quick guide. The 'Terms of Use' view shows application usage terms that must be accepted when using the application for the first time. The 'Feedback' view allows filling and submitting a questionnaire that gives valuable feedback for application developers and the WeLive project. The 'User Profile' window shows information about the user account used to log in. The application can be used in Finnish and English. The language can be changed any time from the flag show in the upper right corner. Clicking the 'Logout' button closes the application session and logs out the user.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 80

Figure 123 – My Polls: Create one or more location based polls to reveal the public opinion

Figure 124 – My Polls: Summary of poll answers can be viewed as pie charts

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 81

Figure 125 – My Polls: Poll heatmap shows averages of poll location answers with colors

My Polls uses the following building blocks described in Section 6.4 GeoPoll Statistics GeoPoll Locations GeoPoll Polls GeoPoll Perspectives Geo Locations GeoPoll Tags GeoPoll Attributes GeoPoll My GeoPoll Heatmaps In addition, some of the directly called building blocks make sub-requests to other building blocks and solutions. See the discussion about sub-requests in Section 6.3.1.3 for more information. 6.3.1.2. My Opinion The My Opinion application allows finding open geo-polls near to a specified location (e.g. user’s current location) and answering them. Nearby geo-polls are shown as markers on a map wherein marker icons indicate the topic of the geo-poll based on the associated tag. Clicking the marker shows the geo-poll details and allows users to answer to it. After submitting the answers, the user can view statistics of answers submitted by other users for the same geo-poll location. This motivates people to actively answer the polls in case they are interested to see the public opinion. My Opinion is available both as an Android application and as a web application. The application includes multiple views for different functionality. Users can switch between application views from left side of the top menu bar shown in Figure 126. In the web browser version, there is a separate button for each view. In the mobile version, there is drop-down menu including a list of views.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 82

Figure 126 – My Opinion menu

The main features of the application are easy to access via the application menu: The 'Poll Map' view allows searching and adding poll locations (Figure 127), submitting answers to polls and viewing statistics on poll answers (Figure 128). The 'Heatmap' view visualizes poll location density as a heatmap (Figure 129). Areas colored with orange or red have the highest density of poll locations. The heatmap can be used to find new areas with polls to answer. The 'Info' view shows information about the application and a quick guide. The 'Terms of Use' view shows application usage terms that must be accepted when using the application for the first time. The 'Feedback' view allows filling and submitting a questionnaire that gives valuable feedback for application developers and the WeLive project. The 'User Profile' window shows information about the user account used to log in. The application can be used in Finnish and English. The language can be changed any time from the flag show in the upper right corner. Clicking the 'Logout' button closes the application session and logs the user out.

Figure 127 – My Opinion: Poll map view allows search and adding poll locations

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 83

Figure 128 – My Opinion: Answer poll questions and view statistics on answers by others

Figure 129 – My Opinion: Poll density heatmap helps finding areas with active polls

My Opinion uses the following building blocks described in Section 6.4. GeoPoll Answers GeoPoll Statistics

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 84

GeoPoll Locations GeoPoll Polls Geo Locations GeoPoll My GeoPoll Density Heatmap In addition, some of the directly called building blocks make sub-requests to other building blocks and solutions. See the discussion about sub-requests in Section 6.3.1.3 for more information. 6.3.1.3. My Neighbourhood The My Neighbourhood application allows users to define a set of personal preferences for a dream neighborhood, i.e. personally important location related matters that affect their quality of life. Each personal preference should be associated to one of the existing attributes and tags (that were used for defining geo-polls as well) and given the level of importance on scale 1-100. Optionally, users can also add notes describing the reasons why this matter is so important if they wish to give city managers some valuable insights for improving the neighbourhood. The service automatically analyzes the quality of life in user’s current neighbourhood based on the given preferences and GeoDB data including geo-poll answers and information from open data sets. Users can also add other interesting addresses to be analysed, e.g. their work location or potential regions they consider to moving to. My Neighbourhood is best when used as a web application but is also available as an Android application. The application includes multiple views for different functionality. Users can switch between application views from left side of the top menu bar shown in Figure 130. In the web browser version, there is a separate button for each view. In the mobile version, there is drop-down menu including a list of views.

Figure 130 – My Neighbourhood menu

The main features of the application are easy to access via the application menu: The 'Preferences' view shows user’s current personal preferences and allows adding, editing or deleting them (Figure 131). The 'Locations' view shows user’s current set of locations and allows adding, editing or deleting them (Figure 132). The 'Scores' view shows a match matrix indicating how well the added locations match to user’s personal preferences (Figure 133). The 'Heatmap' view shows a heatmap visualization summarizing the match scores on the map. Areas colored orange or red match user’s personal preferences very well while blue color indicates areas that do not fit for the user (Figure 134). Application settings can be modified in the 'Settings' view. The 'Info' view shows this information page

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 85

The 'Terms of Use' view shows application usage terms that must be accepted when using the application for the first time. The 'Feedback' view allows filling and submitting a questionnaire that gives valuable feedback for application developers and the WeLive project. The 'User Profile' window shows information about the user account you have used to log in. The application can be used in Finnish and English. The language can be changed any time from the flag show in the upper right corner. Clicking the 'Logout' button closes the application session and logs the user out.

Figure 131 – My Neighbourhood: Add one or more personal preferences to define what is important to you

Figure 132 – My Neighbourhood: Add one or more interesting locations to be analysed

Figure 133 – My Neighbourhood: Match matrix summarizes how well each location matches your preferences

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 86

Figure 134 – My Neighbourhood: Match heatmap helps finding areas that match your personal preferences

In order to create match matrices and match heatmaps, My Neighbourhood calls building blocks that combine information from various open datasets and geo-polls. Figure 135 shows an example wherein the user wants to find a safe neighbourhood which has city rental houses. The data needed to answer to this query can be found from different open data sets, but all the required pieces of information may be hard to find and combine. However, GeoDB combines and normalizes the data and provides efficient geographic queries to make this kind of location based analysis possible!

Figure 135 – My Neighbourhood: Finding a safe neighbourhood with city rental houses

My Neighbourhood uses the following building blocks described in Section 6.4. GeoPoll Answers GeoPoll Locations

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 87

GeoPoll Perspectives GeoPoll Tags GeoPoll Attributes GeoPoll My GeoDB Match Matrix Geocoder GeoDB Match Heatmap In addition, many of the directly used building blocks have dependencies to other building blocks or data refining solutions. For example, when My Neighbourhood makes one request to GeoDB Match Heatmap, it triggers several sub-requests to other solutions that trigger further sub-requests and so forth. Figure 136 shows a sequence diagram for performing a simple match heatmap request involving only one user location and preference. In case a user has added multiple locations and preferences, the overall processing involves significantly larger number of transactions executed concurrently inside the CNS hosting environment. The CNS environment controls and monitors all individual transactions and supports transaction based billing in case the called solution involves usage costs. In order to demonstrate exchanging building blocks between pilot cities, the My Neighbourhood application can be configured to use the Geoutilities building block by the Bilbao Task force instead of the original Geocoder building block. Both building blocks can geocode the given street address into geolocation coordinates, but have have a slightly different call interface.

Figure 136 – My Neighbourhood: Sub-requests triggered by a simple match heatmap request

6.3.2. Pilot phase 2 services Three new applications have been created for the second phase of the Finnish Pilot: Sportit, Helsinki City Museums and Helsinki City Bikes. The following subsections briefly describe both pilot phases’ applications and their main features. The first pilot phase includes My Polls, My Opinion and My Neighborhood applications. The second pilot phase applications include Sportit, Helsinki City Museums and Helsinki City Bikes ( Figure 137 ).

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 88

Figure 137 - Applications in the WeLive Marketplace

6.3.2.1. Sportit Sportit is a mobile application that is available for iOS and Android ( Figure 138 ). It provides information about Sport Locations all around Finland. Data for the application is provided by national sport location database Lipas. Application has two main features, a list view and a map view of nearby sports locations. Both of these views application automatically locates the user and shows different sports location near the application user. The list view provides an easy way to scroll through different locations that are nearby. Users are also able to filter the list based on the category of the location. Each item on the list can be clicked and the application will provide detailed view of the location. In detailed page user can see the specific map view and also additional information about the location for example website. The second main feature is the map view of the sport locations. The map view has similar features with the list view. In the map view user can easily see in one view where different sports locations are based. User can also filter the sports locations in the map view. Each of the map markers is also interactive and when the user clicks the map marker it opens a pop-up window which shows additional information for the user and also provides a link to the detailed view of the location. The application also includes an assistant feature, which helps the user to get to know the different rules and exercise techniques. The service idea originated from the Vantaa City’s aim to increase its citizens’ motivation to participate in sports and welfare. In the forthcoming development during the autumn, a group of 23 developers will focus on the development of the application’s features and usability. Key features: Locating the user Providing data about nearby sport facilities Allow commenting different sport facilities Required datasets: New commenting building block will be created, to enable the commenting for each location. Services will be mainly based on finding relevant data geographical coordinates and unique location IDs (provided by Lipas-database).

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 89

List of Building Blocks: BB-HELSINKI-UUSIMAA-13, BB-HELSINKI-UUSIMAA-14

Social Simple User Real -time Long Tail UGC Ubiquity Interaction Interaction data

✓ ✓ ✓ ✓ ✓ ✓ Common Drivers Geo -located Technical Multi - Open Data Long-term sustainability service feasibility focused ✓ ✓ ✓ ✓ ✓

Figure 138 - Sportit in APP Store and Google Play

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 90

SEARCH

LEARN

SHARE

Figure 139 - Home Page (iOS)

Figure 140 - The general map view, specific sport facility view and the rules and practice assistant view (iOS)

6.3.2.2. Helsinki City Museums Helsinki City Museums is a map-based mobile application for Android ( Figure 141 ) providing the locations of the museums of Helsinki City. Key features:

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 91

Locating the user Providing location of nearby museums in Helsinki. Required datasets: Helsinki Service Map Backend API will provide finding relevant geographical coordinates and unique location IDs. Open Weather Data can be also be implemented. List of Building Blocks: BB-HELSINKI-UUSIMAA-12: Helsinki Service Map Backend API

Figure 141 - Helsinki City Museums in Google Play

Figure 142 - Detailed map view

6.3.2.3. Helsinki City Bikes Helsinki City Bikes is a mobile application that is available for Android ( Figure 143 ). It provides an easy access to get information about City Bikes in Helsinki. City Bikes are free bikes that provided by the city for it citizens.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 92

Application’s main feature is the interactive real-time map which shows the current status of different City Bike stations that are located near the user.

When user starts the application, it automatically locates the user’s current location and centers the map to it. This way the user can easily see near City Bike stations. Each City Bike station is shown as a speech bubble inside the map. Each bubble also shows the current bike availability for each station. Each station marker is also interactive. User can click the desired station and is able to see the name and the last updated date of the station. Application also provides a feedback form for the user which provides feedback for the developers and WeLive-project. Key features: Locating the user Providing location of nearby bike stations. Providing current status of each bike station. Required datasets: Services will be mainly based on finding relevant data geographical coordinates and unique network IDs (provided by citybik.es). Open Weather Data can be also be implemented. List of Building Blocks: BB-HELSINKI-UUSIMAA-11: City Bikes

Social Simple User Real -time Long Tail UGC Ubiquity Interaction Interaction data

✓ ✓ ✓ ✓ ✓ ✓ Common Drivers Geo - Technical Multi- located Open Data Long-term sustainab. feasibility focused service ✓ ✓ ✓ ✓ ✓

Figure 143 - Helsinki City Bikes in Google Play

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 93

Figure 144 - The general map view

Figure 145 - HELSINKI-UUSIMAA Items relations

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 94

6.4. BUILDING BLOCKS This Section describes the building blocks created for the first phase of the Finnish pilot. The “SOLUTION:” field given for each building block feature (POST/GET ) identifies the data refining solution currently implementing the related functionality. Building blocks have been updated for the second pilot phase by fixing some bugs and redesigning REST API operations so that all building blocks follow the same naming principles and can be grouped more logically in the API documentation (Swagger UI). Likewise, few new operations have been added and some legacy operations have been removed. Technically, building blocks have been rebuilt to use the latest data refinery toolkit libraries by CNS. 6.4.1. GeoPoll Answers This is the building block which provides GeoDB poll answer functionality. It allows adding new answers and querying the existing answers with different filters. Coordinates are in WSG-84 (EPSG:4326). POST /answers/add Insert an observation with location information into the database. This can be used to insert poll answers as well as other data. Perspective_id and location_id are required, poll_id is optional. SOLUTION: GeoDB insert_observation 3.0 POST /answers/find Get and filter observations from GeoDB. The observations can be filtered by (longitude, latitude and distance), attribute_id, perspective_id, tags, (timestamp and time_unit), location_ids, grid_id, layer_id, dataset_id, poll_ids and normalization or any combination thereof. Filters in parenthesis must be provided together. SOLUTION: GeoDB get_observations_filtered 3.0 6.4.2. GeoPoll Statistics Tools for viewing GeoDB observation statistics. Currently very limited, only provides a function for getting binned count summary for observations. POST /statistics/get_totals Get binned total answer counts for a list of polls. SOLUTION: GeoDB get_totals_for_polls 3.0.0 6.4.3. GeoPoll Locations This building block allows adding new poll - location associations as well as listing locations already associated with polls. Coordinates are in WSG-84 (EPSG:4326), distances in meters. POST /poll_locations/find Get locations associated with a poll within given radius of a point. Longitude and latitude parameters should be in WSG-84 (EPSG:4326) coordinate system, distance in meters. SOLUTION: GeoDB get_poll_locations 3.0.0 POST /poll_locations/add Insert locations to a poll. This is restricted to polls where users are allowed to add new points and those in which you are the owner or in the administration group.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 95

SOLUTION: GeoDB insert_own_poll_locations 3.0.0 6.4.4. GeoPoll Polls Building block for creating, editing and viewing GeoDB poll information. GeoDB polls allow you to easily collect geospatially associated opinion data, which is automatically stored for easy retrieval, aggregation and analysis. POST /polls/find Get a filtered list of the polls available in the database. The possible filters include poll names, attribute_ids, tags, owners and poll status. SOLUTION: GeoDB get_polls 3.0.0 POST /polls/update Update poll information. Following information can be changed: poll name, description, license, dataset, start time, end time, user expandability, visibility and modifiability (owner only or group). Changes will not affect existing observation data. SOLUTION: GeoDB update_poll 3.0.0 POST /polls/add Creates a new poll for collecting location specific data. Name and description are required, as well as IDs of the perspective and dataset to which the poll will be associated. Perspective contains information about the values being collected, while datasets make it possible to easily keep track of different but related data. The poll location set can also be either user expandable or limited to a set of points provided by the poll administrator. SOLUTION: GeoDB insert_own_poll 3.0.0 6.4.5. GeoPoll Perspectives Tools for viewing and adding GeoDB perspectives. Perspectives are used to describe the meaning and attribute type of the associated observation data. Well defined perspectives also allow easy data aggregation even if data is collected from different polls or stored in different datasets. POST /perspectives/find Retrieve a list of existing perspectives and their information. This list can optionally be filtered with attribute IDs, poll IDs, perspective tags and attribute name. SOLUTION: GeoDB get_perspectives 3.0.0 POST /perspectives/add Insert a new perspective into the database. An existing attribute ID must be provided, while name, description and tags are optional but highly recommended. SOLUTION: GeoDB insert_perspective 3.0 GET /perspectives/{perspective_id} Returns the perspective matching the given unique identifier perspective_id, if such exists. SOLUTION: GeoDB get_perspective_by_id 1.0

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 96

6.4.6. Geo Locations Building block for adding and querying GeoDB locations. Each observation in the data must be associated with a location, but it is possible to add a new location automatically when entering a new observation. Location data allows querying the observations with geospatial queries. Coordinates are in WSG-84 (EPSG:4326), distances in metres. POST /locations/find Return all stored locations within the given distance of the given point. SOLUTION: GeoDB get_locations 3.0 POST /locations/add Insert a new location at given coordinates if no existing location is found within specified distance. Return either the inserted location or nearest found location. Minimum distance can be used if all observations or poll answers within a radius need to be associated with a single point. SOLUTION: GeoDB insert_or_get_location 3.0.0 6.4.7. GeoPoll Tags Tools for viewing, adding, updating and deleting tags associated with GeoDB perspectives. Having correct tags associated to a perspective allows easy searching for related polls and observation data. POST /tags/delete Delete perspective tags from the database. SOLUTION: GeoDB delete_tags 3.0 POST /tags/find Get a list of perspective tags, optionally filtered with a perspective ID. SOLUTION: GeoDB get tags 3.0 POST /tags/add Inserts a tag and/or associate a tag with a perspective. SOLUTION: GeoDB insert_or_assign_tag 3.0 6.4.8. GeoPoll Attributes Building block that allows adding and querying GeoDB attributes. Attributes define a numerical range and type for associated perspective (and thus observations) as well as their more abstract concept. POST /attributes/find Get a list of attributes in the database. Attributes can be filtered by perspective IDs, attribute IDs, attribute names and value types. Information listed for each attribute are its name, description, type, minimum and maximum values. SOLUTION: GeoDB get_attributes 3.0 POST /attributes/add Insert a named numeric attribute into the database. The only required field is value type, but providing name, description and minimum/maximum values (if applicable) is recommended to make the attribute more useful.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 97

SOLUTION: GeoDB insert_attribute 3.0 6.4.9. GeoPoll Users Tools for adding, modifying and deleting GeoDB users as well as viewing and updating their preferences and personal locations. For administrative use only. POST /user/permissions Modify geodb user permissions SOLUTION: GeoDB manage_user_permissions 3.0.0 POST /users/add Insert user entry into geodb SOLUTION: GeoDB insert_user 3.0.0 POST /users/delete Delete user from a GeoDB SOLUTION: GeoDB delete_user 3.0.0 POST /users/find Get user information for one or more GeoDB users SOLUTION: GeoDB get_users 3.0.0 6.4.10. GeoPoll My Solutions for changing the user's personal information and preferences. This building block also contains methods for viewing the content added by the user. These solutions require no special permissions and can be made available to all registered users. GET /my/polls Get a list of your own polls and polls for which you are marked as an administrator. Returns comprehensive information for each listed poll, including information on associated perspective and locations. SOLUTION: GeoDB get_own_polls 3.0 POST /my/observations/find Get user's own observations, for example poll answers. These can be filtered by area given as center coordinates and distance. Coordinates are in WSG-84 (EPSG:4326), distances in metres. SOLUTION: GeoDB get_own_observations 3.0 POST /my/poll_locations/find Get a list of poll locations viewable by this user without additional permissions. SOLUTION: GeoDB get_own_poll_locations 3.0 POST /my/username Update your own username. SOLUTION: GeoDB update_own_username 3.0

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 98

POST /my/locations/delete Delete your own user locations with this awesome tool. Useful for managing the list of locations you are interested in. SOLUTION: GeoDB delete_own_user_locations 3.0 POST /my/preferences/delete Delete your perspective associated preferences. SOLUTION: GeoDB delete_own_user_preferences 3.0 GET /my/preferences Get a list of the perspective preferences you have set. SOLUTION: GeoDB get_own_preferences 3.0 POST /my/preferences/upsert Insert or update your perspective preferences. These can be used to indicate what things you prefer and what you wish to avoid, for example you wish to maximize proximity of services but want to avoid areas with hazardous traffic. Used to generate recommendations in My Neighbourhood app. SOLUTION: GeoDB upsert_own_user_preference 3.0 POST /my/locations/upsert Update or insert locations to the list of locations you find interesting. SOLUTION: GeoDB upsert_own_user_locations 3.0 POST /my/locations/find Get a list of locations you have marked as interesting. SOLUTION: GeoDB get_own_locations 3.0 GET /my/licenses Get a list of licenses you are using. SOLUTION: GeoDB get_own_licenses 3.0 6.4.11. GeoHeatmap This is the building block for creating heatmaps from geodata. POST /heatmaps/google/average Visualizes the average of values associated to geolocations as a heatmap on Google Maps. The heatmap is returned as a stand-alone HTML page which can be e.g. saved to a local computer and viewed later without connection to the Cloud'N'Sci.fi marketplace. The colors of the heatmap at a specific map location represent the average of input data values nearby the location. SOLUTION: Google Maps Average Heatmaps 1.6 POST /heatmaps/google/density Visualizes the density of given geolocations as a heatmap on Google Maps. The heatmap is returned as a stand- alone HTML page which can be e.g. saved to a local computer and viewed later without connection to the

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 99

Cloud'N'Sci.fi marketplace. The colors of the heatmap at a specific map location represent the density of nearby input locations. SOLUTION: Google Maps Density Heatmaps 1.3 6.4.12. GeoDB Match Matrix Computes a match matrix based on the given user preferences and locations. The match matrix includes a score for each preference-location pair indicating how well does that location match to the preference. A total match score is also returned for each location. POST /match/matrix Evaluates how well the given locations match to the given user preferences by computing a match matrix. SOLUTION: Match Matrix HEL 0.6 6.4.13. Geocoder Geocoding service which converts the given street address to (latitude, longitude) coordinates. POST /geocode/address Converts the given street address to the corresponding geolocation coordinates. SOLUTION: Geocoder 9.5 6.4.14. Personal Data Personal Data Building Block is a service to store and manage personal data in a highly secure and structured way POST /data/action Manages your personal data by using Citizen Data Vault. Add, Get, Update, Find or Delete personal data using tags or ID, returns the data or ID. SOLUTION: Personal Data 1.1.3 6.4.15. GeoDB Match Heatmap Generates a match score heatmap for the given personal preferences and favorite locations based on all relevant data in the GeoDB. POST /match/heatmap Creates a match score heatmap based on GeoDB data and personal preferences. SOLUTION: Match Heatmap HEL 0.5 6.4.16. GeoPoll Heatmaps This building block creates heatmap visualizations showing average of poll answers. GET /heatmaps/poll Creates a heatmap visualization for the given poll. SOLUTION: GeoPoll Answer Heatmap 3.0.0 6.4.17. GeoPoll Density Heatmap

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 100

Returns heatmap visualization which shows the density of poll locations on Google Maps. GET /heatmaps/density Creates a heatmap visualization showing the density of existing poll locations SOLUTION: GeoPoll Density Heatmap 3.1.0 6.4.18. Geo Areas GeoDB area related tools. POST /areas/add Insert areas from a tab separated CSV file and an associated JSON metadata file. The tab separated fields are: polygon as WKT, name, identifier, description. All fields must be present, although others than polygon may contain an empty string. JSON fields are name (string), description (string), data_source (string) and layer_id (integer). If layer_id is supplied, the script will try to use an existing layer info and fail if layer with given id is not found. Otherwise a new layer is created using the supplied name, description and data_source. SOLUTION: GeoDB insert_areas_csv 3.0.0 GET /areas/layers Get a list of area layers in the database. SOLUTION: GeoDB get_area_layers 1.0.0 POST /areas/layer/add Insert area layer information into the database. Each inserted area must be associated to an area layer, which indicate what the areas define, e.g. Helsinki districts or Helsinki Subdistricts. SOLUTION: GeoDB insert_area_layer 1.0.0 6.4.19. Area datasets Manage area datasets used in other GeoDB Building Blocks POST /datasets/area/add Insert a set of area observation data from a CSV file and an associated JSON metadata file. SOLUTION: GeoDB insert_area_observations 3.0.0 6.4.20. Citizen Data Vault API The Citizen Data Vault (CDV) is the WeLive component that allows the citizens to manage their own data in a vault. The CDV collects the citizens profile data during the interaction with the WeLive tools tools. Furthermore the CDV provides a set of API to get the user profile data and to store and manage data generated using the third party application (User Data). All these operations require WeLive Authorization. 6.5. DATASETS The following list includes the names, descriptions and formats of Finnish open data sets that available in the WeLive Platform at the moment of writing this document. Helsinki Area Service Map – Organizations: List of organizations in Helsinki area service map data. Most of the textual data is also included in English and Swedish. JSON,XML

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 101

Helsinki-Uusimaa's twitter topics: Twitter topics posted by Helsinki-Uusimaa during the WeLive project. JSON Buildings of Vantaa: This dataset provides the buildings of Vantaa in polygons. The data is in GeoJSON -format. The coordinate system used is ETRS-GK25. JSON Parking violations in Helsinki: This dataset provides all parking violations issued in Helsinki starting from January 2014. CSV Pääkaupunkiseudun Palvelukartan REST-rajapinta: The REST API offers your own web-applications easy access to the data content of the City of Helsinki Service Map. The REST API is implemented using principles of REST architecture. Data can be queried in JSON or XML formats. JSON, XML Pääkaupunkiseudun ilmanlaatuindeksit 2015: Air quality data for the Helsinki city area 2015. XML City of Helsinki Budget Information 2012-2014: This dataset provides the City of Helsinki's budget information for the years 2012, 2013 and 2014. CSV Helsingin kaupungin palauterajapinta: The issue reporting API is used by applications for sending service requests to the City of Helsinki. JSON HSL:n liityntäpysäköintipaikat: Information about public parking places in Helsinki city area. JSON Espoon kaupungin liikennetiedotepalvelun rajapinta: API to get traffic information for city of Espoo. XML Buildings of Espoo: This dataset provides information on buildings in Espoo. JSON District Map of the City of Helsinki: District Map of the City of Helsinki. Coordinates in WGS 84 (WGS 1984, EPSG:4326). KML HSL:n asiakastyytyväisyystutkimus: Asty Web is Helsinki Region Transport's internet database, which provides research information on passenger satisfaction in public transportation. It is possible to make custom tables, reports and graphs from your own data selection. The data can be broken down by municipality, mode of transport or by the respondent's gender. The Asty Web database contains Helsinki Region Transport's year-round survey material. Every year over 50 000 passengers participate in the survey, evaluating the quality of public transport on a scale of one to five (1 = very bad, 5 = very good). The research is conducted on public transport on weekdays between 6:00 and 18:00. Questionnaires are distributed to randomly selected passengers. Asty Web provides survey results starting from 2011. The customer satisfaction data is available via REST-API. The data is returned in CSV- format and it is accessible with the HTTP GET-method. JSON Helsingin kaupunginmuseon aineistot: Photographs, art and objects from the collections of Helsinki City Museum. JSON … Helsinki Area Service Map - Services by Category: Helsinki area service map service category list and the IDs of service points associated with each category. Main language is Finnish, but category names are also available in English and Swedish. JSON,XML Helsinki: Pohjoismaiset suurkaupungit: The Statistical Yearbook provides a varied, statistics-based description of Helsinki and its residents. Many of the tables also present comparative data from the rest of the Helsinki Metropolitan Area, the Helsinki Region and Finland as a whole. Moreover, the yearbook contains a chapter on major cities in the rest of Scandinavia and one on the capitals of Lithuania, Latvia and Estonia, and on the City of S:t Petersburg. The book contains 257 tables in all. The publication is bilingual and the statistical tables have headings in English. The statistical yearbook is provided in the form of an archived Excel-file. XLSX Vantaan avoimet työpaikat –rajapinta: API to find open jobs in city of Vantaa. JSON Ilmansaastepitoisuudet 2014: This dataset provides Helsinki Region Environmental Services (HSY) air pollutant information from 2014. XML

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 102

Helsinki Area Postal Code Areas: The Helsinki metropolitan postal code areas have been produced together in a joint effort with the cities of Helsinki, Espoo and Vantaa. The data contains precise territorial borders and information on the postal code and place of business. The postal code territorial borders have been produced based on the municipalities' own borders and therefore they are compatible with the municipalities' own postal code territorial borders. The accuracy of this combined dataset differs by municipality. This is caused by the initial data and administration procedures. This dataset was produced 1/2015. KML Helsinki Area Service Map – Departments: Department data from Helsinki area service map. Main language is Finnish, but English and Swedish translations are available for most of the data. JSON,XML Traffic Accidents in Helsinki: This dataset provides statistics on traffic Accidents in Helsinki. CSV Eduskuntavaalit Helsingissä 2015: This dataset provides statistics on the Parliamentary elections in Helsinki 2015. XML School service areas of the City of Helsinki: This dataset provides public school districts in the City of Helsinki for the school year 2015-16 in vector or MapInfo-tab format. The geographic coordinate system is ETRS-GK25. KML Helsingin seudun sairastavuusindeksi: This dataset provides the Helsinki region morbidity index. XML Helsinki Area Service Map - Service Points: Service points listed in Helsinki area service map. Most of the descriptions in the data are also available in English and Swedish. JSON,XML,CSV Pääkaupunkiseudun energiankulutus: This dataset provides energy consumption data on the metropolitan area's and metropolitan cities' (Helsinki, Espoo, Vantaa, Kauniainen) by sector (district heating, oil heating, electric heating, electricity for consumption, cars, other road traffic, trains, ships, other fuel) in 1990 and 2000-2013. XML Helsinki Area Address Catalogue: This dataset provides the regional address book of the Helsinki metropolitan area in a CSV file. The coordinates are provided as WGS-84 latitude and longitude as well as geom points in ETRS-GK25 (EPSG:3879) system. CSV Kuuden suurimman kaupungin lastensuojelun vertailu: This dataset provides a comparison of child welfare between the six largest cities. CSV Helsinki: Turvattomuutta kokevien osuudet peruspiireittäin 2003, 2006 ja 2009: This dataset provides the results of the Helsinki: Safety survey by area in 2003, 2006 and 2009. XLS Population projection in the Metropolitan Area in 2015-2024: Population by age in Helsinki Metropolitan Area by District on 1 Jan. 1992-2014 and population projection 2015-2024. CSV Buildings of Helsinki: This dataset provides the buildings of Helsinki in polygons. The coordinate system used is ETRS-GK25. CSV 6.5.1.1. Dataset quality report Table 10 shows a summary of broken links for Helsinki-Uusimaa.

Datasets with broken links Broken links % of broken links

14 18 26%

Table 10 – Number of broken links for Helsinki-Uusimaa pilot.

Helsinki-Uusimaa pilot has 18 links with issues, distributed among 14 datasets. There are 16 links that are not really broken, but the URL redirect to a domain whose SSL certificate is not correctly signed. Despite of this, it is not an inconvenience when browsing and downloading these datasets, they could produce issues when exploring them with external clients, like the ones built with Java programming language. Table 11 shows these datasets. In Table 12 two datasets that there are really unreachable are shown, the first one

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 103

(https://dev.WeLive.eu/ods/dataset/espoon-kaupungin-liikennetiedotepalvelun-rajapinta), because it asks for authentication.

Dataset Resource Link

https://dev. WeLive .eu/ods/data Excel - http://www.hel.fi/hel2/tietokeskus/data/helsinki/Oiva_Akat set/helsingin-kaupungin- tiedosto emia/Oivan_koulutukset.xls henkiloston-koulutukset

https://dev. WeLive .eu/ods/data CSV - http://www.hel.fi/hel2/tietokeskus/data/helsinki/Oiva_Akat set/helsingin-kaupungin- tiedosto emia/Oivan_koulutukset.csv henkiloston-koulutukset

https://dev. WeLive .eu/ods/data Helsingin http://www.hel.fi/hel2/tietokeskus/data/helsinki/kulttuuri/ set/helsingin-taidemuseon- taidemuseo Helsingin_taidemuseon_n%C3%A4yttelyt.xlsx nayttelyt n näyttelyt Excel- tiedostona

https://de v. WeLive .eu/ods/data Helsingin http://www.hel.fi/hel2/tietokeskus/da ta/helsinki/kulttuuri/ set/helsingin-taidemuseon- taidemuseo Helsingin_taidemuseon_n%C3%A4yttelyt.csv nayttelyt n näyttelyt CSV- tiedostona

https://dev. WeLive .eu/ods/data Taidemuse http://www.hel.fi/hel2/tietokeskus/data/helsinki/kulttuuri/ set/helsingin-taidemuseon- on Helsingin_taidemuseon_prosenttirahahankkeet.xls prosenttirahahankkeet prosenttira hahankkeet Excel- tiedostona

https://dev. WeLive .eu/ods/data Taidemuse http://www.hel.fi/hel2/tietokeskus/data/helsinki/kulttuuri/ set/helsingin-taidemuseon- on Helsingin_taidemuseon_prosenttirahahankkeet.csv prosenttirahahankkeet prosenttira hahankkeet CSV- tiedostona

https://dev. WeLive .eu/ods/data Pakattu http://www.hel2.fi/tietokeskus/data/helsinki/helsingin_kau set/helsingin-tilastollinen- Excel- pungin_tilastollinen_vuosikirja_2011/Helsingin_tilastollinen vuosikirja-2011 tiedosto _vuosikirja_2011.zip

https://dev. WeLive .eu/ods/data Pakattu http://www.hel2.fi/tietokeskus/data/helsinki/helsingin_kau set/helsingin-tilastollinen- Excel- pungin_tilastollinen_vuosikirja_2012/Helsingin_tilastollinen vuosikirja-2012 tiedosto _vuosikirja_2012.zip

https://dev. WeLive .eu/ods/data Pakattu http://www.hel.fi/hel2/tietokeskus/data/helsinki/helsingin_ set/helsingin-tilastollinen- Excel- kaupungin_tilastollinen_vuosikirja_2013/Helsingin_tilastollin vuosikirja-2013 tiedosto en_vuosikirja_2013.zip

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 104

https://dev. WeLive .eu/ ods/data Pakattu http://www.hel.fi/hel2 /tietokeskus/data/helsinki/helsingin_ set/helsingin-tilastollinen- Excel- kaupungin_tilastollinen_vuosikirja_2014/Helsingin_tilastollin vuosikirja-2014 tiedosto en_vuosikirja_2014.zip

https://dev. WeLive .eu/ods/data Helsingin http://www.hel.fi/hel2/tiet okeskus/data/helsinki/helsingin_ set/helsingin-tilastollinen- tilastollinen kaupungin_tilastollinen_vuosikirja_2014/Helsingin_tilastollin vuosikirja-2015 vuosikirja en_vuosikirja_2014.zip 2015

https://dev. WeLive .eu/ods/data Helsingin http://www.hel.fi/hel2/tie tokeskus/data/helsinki/tieke/helsi set/helsingin-tilastollinen- tilastollinen ngin_kaupungin_tilastollinen_vuosikirja_2016/Helsingin_tila vuosikirja-2016 vuosikirja stollinen_vuosikirja_2016.zip 2016

https://dev. WeLive .eu/ods/data Helsinki: http://www.h el.fi/hel2/tietokeskus/data/helsinki/tieke/helsi set/helsinki-pohjoismaiset- Pohjoismai ngin_kaupungin_tilastollinen_vuosikirja_2015/Pohjoismaiset suurkaupungit set _suurkaupungit.xls suurkaupu ngit

https://dev. WeLive .eu/ods/data Helsinki: http://www.hel.fi/hel2/tietokeskus/data/helsinki/tieke/helsi set/helsinki-pohjoismaiset- Pohjoismai ngin_kaupungin_tilastollinen_vuosikirja_2015/Pohjoismaiset suurkaupungit set _suurkaupungit.xls suurkaupu ngit

https://dev. WeLive .eu/ods/data Ex cel - http://www.hel.fi/hel2/tietokeskus/data/helsinki/tieke/helsi set/helsinki-vaalit tiedosto ngin_kaupungin_tilastollinen_vuosikirja_2016/Vaalit.xls

Table 11 – Datasets with an invalid SSL certificate from Helsinki-Uusimaa pilot.

Dataset Resource Link

https://dev. WeLive .eu/ods/data Espoon http://espoo.datex2.fi:8180/axis2/services/espooDatex2Pull set/espoon-kaupungin- kaupungin Service liikennetiedotepalvelun- liikennetied rajapinta otepalvelu n

https://dev. WeLive .eu/ods/data HSL:n http://d ata.hslhrt.opendata.arcgis.com/datasets/8baa56336 set/hsl-n-myyntipisteet myyntipiste dc74a279c0f0a32998577d4_0.csv et

Table 12 – Unreachable resources from Helsinki-Uusimaa pilot.

Regarding to the openness report, it shows the summary of the number of stars earned by datasets provided by Helsinki-Uusimaa pilot in the Linked Data 5-star scale. There are 9 datasets with 0 stars, mainly because there are not reachable due the SSL issue commented above. Datasets ranked with 2 stars could improve its score if they are published using open formats like CSV, instead XLS. Regarding datasets have earned a score of 3 stars.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 105

0 stars 1 star 2 stars 3 stars 4 stars 5 stars Average stars

9 0 13 27 0 0 2.2

Table 13 – Summary of starts earned by datasets from Helsinki-Uusimaa pilot.

6.5.1.1.1. Recommendations Helsinki-Uusimaa pilot could improve the quality of its datasets following a few simple steps. For example, they could fix most of the “broken” links fixing the SSL certificate of the server and removing the authentication from one of them. Regarding to the openness, datasets with a score of 2 stars could evolve to 3 stars publishing them using open formats like CSV or JSON.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 106

7. NOVI SAD ENVIRONMENT 7.1. PROCESS FOLLOWED IN NOVI SAD FOR PLATFORM POPULATION In the city of Novi Sad, for citizens’ and stakeholders’ engagement and cooperation, the following activities were organised: surveys and workshops. 7.1.1. Surveys The survey was conducted in the early phase of the project i.e. distributed questionnaires to different stakeholders (citizens, companies and public administrations) by e-mail. Novi Sad launched a survey among different stakeholders in order to know their needs and expectations about the city. It was distributed to 116 citizens, 21 companies and 9 public administrations. In the figure below the age structure of the survey participants is presented.

3,45% 9,48% 19,83% Age 18-25 12,93% Age 26-33 Age 34-41 54,31% Age 42-49 Age 50-57

Figure 146 – Age structure of survey participants

As for the results from survey, the main outcomes are presented below:

7 Real estate 4,84 12 Existence 16 6,45 21 Employment 6,45 28 Finance and Taxing 29 6,45 29 33 Taxes 11,29 Security 34 34 16,13 41 Habitation 42 Education 25,81 44 54 29,03 Tourism 57 59 Transportation… 32,26 60 Culture 63 35,48 67 67 Health services and… 38,71 Maps 70 0 20 40 60 0 20 40 60 80

Figure 147 – Personal digital needs of examinees - the Figure 148 – Examinees' needs for public service sectors - the most most common answers (in percentages) common answers (in percentages)

The results in the Figures are presented as the percentage of examinees’ answers towards specific topics. The survey’s results are analysed and based on that it was concluded that the stakeholders are mostly interested in: Health services and information Transportation and traffic Administration /Public services (Legal protection, family and social services, finance, taxation, real estate) Education and culture

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 107

Maps Employment Environment 7.1.2. Workshops After deep analysis of survey results, several workshops with smaller groups of people were organised. During these workshops, different planned services were presented and discussed to obtain feedback, which was used to improve the functionality. Based on the survey results people were separated in smaller groups depending on the group of stakeholder (citizen, companies and public administration) and each workshop focused on specific services. Taking advantage of the fact that City of Novi Sad is participating in several international scientific and research projects, funded by the European Union, and all of them aimed at improving the public services system in Novi Sad by introducing innovation through the use of modern technology, the City has organized a promotional campaign entitled "Novi Sad - Smart City”. This promotional campaign "Novi Sad - Smart City" includes the following activities and all of them were launched in the scope of WeLive project: Series of workshops in local communities in Novi Sad on the theme "Novi Sad - Smart City" that bring together representatives of the tenants' councils and interested citizens, providing a platform for their ideas, comments and suggestions to influence the development of the City, and thus the places of their immediate residence. Workshops for local self-government for 70 LS representatives in total from 24 th to 26 th August 2015 four workshops were organized for those representatives who are currently not involved in projects, but are working on the improvement of these fields, or will get involved in the provision of services through the new platforms, since the development of the Novi Sad Sustainable Development Strategy is valid through 2020 is in progress and it covers topics such as good government and smart Cities. General public events were organized depending on the possibilities and promoted several city and project partner websites (five being targeted minimum). Moreover, the city representative promoted the project: Marijana Dukić Mijatović, Head of the Local Economic Development Office of the City of Novi Sad made the statement for local TV, explaining the main aim of project is to improve domestic administration using technologies. Moreover, the public event titled Novi Sad, a smart city – activities and opportunities held on 2 nd February 2015 at the City Assembly of Novi Sad premises was also hosted by Mrs Dukic Mijatovic.

The objective of all workshops was to provide information, exchange opinions and include the citizens in the projects. In addition, as several pilot projects were conducted at the mentioned promotions, the pool of future respondents and participants was expanded. On the workshops presented we summarized results from the survey and discussed about new ideas and proposals with participants. Based on these discussions we have collected more inputs and based on these conclusion, the scenarios and services have been prepared. 7.2. INTEGRATION WITH LOCAL INFRASTRUCTURE On the territory of Serbia, the City of Novi Sad has been among the first to try to collect open data for a local self-government unit. Open data provided by the City of Novi Sad are located in multiple sources. One source of open data is CKAN node used in the CLIPS project. In addition, web services that are in the data center of the PUC “Informatika” are utilized. Other data are collected as part of the WeLive project housed in ODS. For easier data management, all data are in CVS or JSON formats. The Figure 149 shows how the data is stored in the municipality of Novi Sad. Linking data from WeLive project is carried out through the ODS and building blocks.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 108

Figure 149 – Data sources in Novi Sad

7.3. SERVICES, BUILDING BLOCKS, DATASETS The users of the WeLive framework involved in the activities of the first and second iteration of the Novi Sad pilot will interact with an environment that has been populated with a set of WeLive-compliant artefacts. Such artifacts are published in the WeLive marketplace and are of three kinds: services, building blocks and datasets. The following sub-sections provide the details about them. In order to improve a number of downloads than was lower than expected, comprehensive set of activities is conducted, i.e. intensive campaign via social channels (YouTube, Tweeter, and Facebook), website, emails, media articles and word of mouth. Also, based on the feedback from users received via all communication channels, the version of applications from Pilot Phase 1 have been improved with new releases that resolve some bugs and introduce some new features. 7.3.1. Services For the WeLive Pilot Phase 1, the Novi Sad task force has implemented three public service applications, and for Pilot Phase 2, two more applications are developed , namely: Safe City Trip Relocation Advisor Public Procurement Transparency My Local Community Culture Key Applications are available to WeLive users through the WeLive Marketplace and through the WeLive Player app. They are actually Android apps and, thus, are available for download from the Google Play app store. For the applications Safe City Trip and Relocation Advisor, there are also web versions of applications. The services offered within the three applications have been identified with the help of citizens during the engagement activities executed by the Novi Sad task force during the first year of the project, which are described in [2]. Other two applications were developed based on the results of the Idea contest held in Novi Sad, and are described in [27] (both Ideas Evaluation and Selection Process and applications are described in this deliverable). During the October 2017 alpha testing was successfully completed, and applications have been improved based on suggested recommendations.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 109

System Requirements for Safe City Trip and Relocation Advisor web applications are: Windows XP, Windows Server 2003 and Windows Vista, Windows 7, Windows 8, Windows 8.1, and Windows 10. Systems Requirements for Safe City Trip, Relocation Advisor, Public Procurement Transparency, My Local Community, and Culture Key support on android smart phones support: Android 3.0., Android 4.0., Android 4.1., and Android 4.4. The applications are described in details in the following sections. 7.3.1.1. Relocation Advisor

Relocation Advisor is both web and android service which allows citizens and business people to find an appropriate apartment based on open data-information on public utility infrastructure in relation to their residential purposes, citizens are able to get data about vicinity of parks, playgrounds, kindergartens, schools, as well as traffic congestion, noise, and other information related to environment and neighborhood of their place of interest. This information will give better insight about considered city area for living purposes.

For the web access to the service, follow the link [16]. If a user wants to download the application on smart phone, it should look for Relocation Advisor application on Google Play under WeLive project.

Figure 150 shows the window with several boxes and map of Novi Sad.

In the upper part of the screen, there are three boxes which users should fill. The first one is the street which they would like to check. Once they found the street, the second box is asking them to be more precise of the exact block where their building is placed. Finally, the last box is the purpose of their relocation to the mentioned address ( living, business, or other purposes; options A, B, and C respectively ). Below the map of Novi Sad with requested address, there is a scale measuring the quality of the air in that area. The button search is marked with the blue color. Once the button search is pressed, several options and types of information are shown in the boxes below the map. Relocation Advisor application users get information regarding the quality of the air in the typed address as the first option shown. Facilities nearby the address such as pharmacies, ambulances, schools, cinemas, banks, etc. are under the second option. There are also information about sewerage system, infrastructure of the roads, pedestrian roads, hot water networks, electricity networks, and other information relevant for users who want to move to specific neighbourhood. All information is available in one window and under the same umbrella of data. The third option shows all the schools in the city of Novi Sad. To see particular school nearby the address a user is looking for, it is enough to zoom the map and see only schools close to the requested address. By clicking on any school shown on the map, the information about the school appears in new window (school address, phone number, and the web site). The example of one school in Novi Sad and its information is shown in Figure 151. For each school in Novi Sad, it is possible to see the route from the requested address in the application to any school. To request this option, users only need to click the button “show the route” which is in the window below the map on the right from the school name and the distance shown next to the school name (blue button, “Prikaži Putanju”). After requesting the route from user's street to the specific school, the map shows the route marked with the blue color as showed in Figure 152. The fourth option is showing the bus lines in Novi Sad. Particularly, when specific address is typed, the application shows all the bus lines passing by around the mentioned street. They are all mentioned below the

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 110

map, as well as their routes, and the possibility to show the whole route with all bus stops. This option is valid once the blue button next to the bus line description is pressed (“Prikaži Stanice”). As it can be seen in the Figure 153, blue buttons in the right bottom of the window are different bus lines and their stops on the whole route through the city. By clicking on each stop and zooming the map, it is possible to see exact point where the bus stop is. To zoom the map, users can use two buttons in the right bottom corner of the map marked as + and -. The button + is to zoom map in and make it bigger, while the button - is to zoom map out and make it smaller. Finally, the last option is to check parking spots in nearby the requested address. This option gives input to users in parking nearby, exact position, as well as if it is free of charge or not and if it has spots for people with special needs. On the right side of the window under the map, as shown on the Figure 154, people can request to see where is the parking they want to use. The little icon of parking shows up on the map after the request. To leave the application, it is enough to press the black buttom in the upper right corner in both android and web applications.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 111

Figure 151 – Information regarding Figure 150 – The first window of Relocation Advisor application in both Web and Android one of schools in Novi Sad service

Figure 152 – Route from requested address to Figure 153 – Bus stops on requested bus line one of the schools in Novi Sad

Figure 154 – Parking places nearby requested address

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 112

7.3.1.2. Safe City

Safe city trip is both web and android service that allows citizens to make optimal city trip planning based on their specific needs. Based on the information about pollen (to be implemented), traffic congestion and quality of surface water, they will get the optimal route to safely go by bicycle and enjoy in swimming and outdoor activities. Furthermore, the users are enabled to avoid unexpected roadwork and congested streets.

For the web access to the service, follow this link [17]. If a user wants to download the application on a smart phone, he/she should look for Safe City Trip application on Google Play under WeLive project.

The first window appearing in both smart phones and web browser should be the starting point for using the application. It consists of options available for users: starting and final point of the user's route, water quality, noise, traffic, and the button requesting the mentioned route. Figure 155 shows the window with several boxes and map of Novi Sad. As shown in Figure 155, several options are available for users. The green arrow shows where the user should type starting point of his/her trip . The red arrow is the final point of the trip and the user should type his final destination in the box marked with the red arrow. In order to find the best route for his/her trip, the user should press the blue button Nađite Putanju placed below all boxes in the window on the left. It is marked with the black arrow in Figure 155. Once the user decides to find its route from one place to another, the application will allow him/her to choose between reaching the final destination by car or bicycle or on foot. After pressing the blue button Nađite Putanju , the route is shown on the map with the blue line which is the route that the user requested. It is shown below in Figure 156.

Other options in this application mentioned before are the water quality, noise in the city, and the traffic . Each of them can be marked by the user on their gray buttons Kvalitet Vode, Buka, and Saobraćaj respectively. Once the button and option is marked, the gray buttons turn to blue colour which is the sign that the user requested some action.

If the user wants to know the quality of the water in the city, he/she needs to press Kvalitet Vode button and the new window will show the information regarding quality of water in Novi Sad. Its appearance is shown below in Figure 157.

The window of the quality of water in Novi Sad is giving information such as temperature, color, smell, Ph value, level of O2, etc. The window can be left easily with the button Zatvori in the right bottom corner of the window. After that, the application will return the user to the main window where his/her route will be still available.

The second option that could be checked in Safe City Trip is noise level in Novi Sad. Noise levels are shown on the map of Novi Sad with or without requested route from the user, as long as the button for noise is marked. When the action is requested, the blue microphones are exposed on the map of Novi Sad as shown in Figure 158.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 113

Figure 156 – The route which the Figure 155 –The first window of Safe City Trip application in both web and android service user has requested

Figure 157 – Window showing the quality of Figure 158 – Microphones shown on the Figure 159 – Noise level in the city water in Novi Sad map presenting the noise levels in Novi of Novi Sad Sad

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 114

Figure 160 – Traffic buttons showing the Figure 161 – Information regarding amount of traffic in the city traffic in specific area in the city of Novi Sad

Once the microphones appear on the map as it pointed with the black arrow on the Figure 158, in order to see the noise level in different parts of the city, users should click on the microphone close to the place they would like to go or live or where they just plan to see the noise level, and the new window with the noise level information will appear. It shows the noise in decibels (dB) and for the period of the last six months or the last year. Once users have checked the noise level, they can easily close the window by clicking the button in the right bottom Zatvorite , or they can just use close button on the right top. Once the window is closed, the application is back to the map of Novi Sad and requested address or route. Figure 159 shows how the window and information regarding noise in different parts of Novi Sad look like.

Finally, the last option for users available in Safe City Trip application is to check traffic in the city and on the routes they would like to take. The action for finding the traffic in the city is taken by pressing the button for traffic in the box on the left side of the map. Once the button Saobraćaj (Traffic) is pressed, the screen in Figure 160 appears.

As shown in Figure 160, there are many green and orange circles showing the level of traffic in different parts of the city. There is one more possible circle to appear (red one) and each of them is representing the density of the traffic and cars in the city. The red circle is showing the high density in the traffic, orange is presenting medium density, while the green one means low density of the traffic in Novi Sad of a particular area. Users can get an insight without pressing any of the circles to see the traffic around particular areas and neighbourhoods. In addition, there is an option for users to see exactly how crowded is the city by clicking on any circle they are interested in. If users want to know more, to get the information on how many cars are passing by and in which streets, as well as on the flow of the traffic in general, the relevant information is updated every five minutes, they can obtain this type of information by clicking on specific circle on the map. Once they do so, a window with all mentioned information appears as in Figure 161.

The first column is showing the streets covered by the circle, the second one is giving the insight about the way the traffic is running. The third one is showing the date and the last one is showing the time which is, as mentioned before, updated every 5 minutes. For closing the window with information about the traffic, the

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 115

users can easily close it by clicking the button in the right bottom Zatvorite , or they can just use close button on the right top. Once the window is closed, the application is back to the map of Novi Sad and address or route is requested.

To leave the application, it is enough to press the black button in the upper right corner in both android and web applications. 7.3.1.3. Public Procurement Transparency

Public procurement transparency & Public procurement follower is the service that allows public administration and citizens to follow Public procurement process. This service allows citizens and companies to receive clear information about new competitions that they could apply to, accompanied with the possibility to obtain information on companies from the same activity, the concluded agreements and similar. For public administration persons, it will allow perceiving weaknesses and advantages of applying the Law in practice, giving the possibility of simplifying the procedures and steps and having the initiative to amend the Law on Public Procurement. In addition, based on self-government public procurement, open data can be used for making various studies and analysis of importance for the City.

This service is provided through the smart phone application called Public procurement transparency under the project WeLive. If a user wants to download the application on smart phone, she should look for Public procurement transparency application on Google Play. The picture in Figure 162 shows the application's logo.

After choosing to start checking on public procurement, the user can choose between three options Public procurement ( Nabavke ), Statistics ( Statistika ), or Information about the application ( O aplikaciji ). Options are shown in Figure 163.

Since majority of users using this application are interested in looking for public procurement, the first option to choose is public procurement ( Nabavke ). When choosing the option public procurement, a number of different public procurements from various companies appear. The user should choose the one he/she is interested in. The new window should look like in Figure 164.

Various companies are presented and by clicking on one of them, more information regarding the public procurement of the company appears in the new window. Any of these companies and their public procurement can be easily checked through this application.

Once the company has been chosen by the user, the information about public procurement of the company shows in the new window. The following information regarding company's public procurement are shown respectively: number of procurement, who ordered it, the date, document's name, phone number, contact person, and place of the company, as it is shown in Figure 165.

For leaving the chosen company, the user can click on the arrow in the left top corner as shown in the figure. The application will return the user to the page with all other companies and possibilities to choose some other tab such as statistics or about the application. The blue arrow is presenting the button which should be pressed in order to go back where the list of all companies are.

As mentioned before, other tabs and options are available in the application. One of them is statistics application, which shows the user the number of public procurement in different cities in Serbia, but also in

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 116

particular parts of Serbian capital Belgrade (as it is huge area with a lot of companies and public procurements). The window of Statistics tab should be like in Figure 166.

To leave the application, it is enough to press the black button in the upper right corner or just to press the button for accessing the main many on the user's smart phone.

Figure 162 – Public procurement Figure 163 – Options available in the Figure 164 – Companies' public transparency application logo and application procurement options first page

Figure 165 – Information about the Figure 166 – Statistics company, which the user chose to get information about

7.3.1.4. My Local Community User part (Local Community)

My local community is an extension of the “Moj grad” Android app that helps users keep up to date with the latest news from the local communities of the city of Novi Sad.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 117

Once the app is installed and started the following screen appears. In the login page, users have a few options for logging in: Google, Microsoft account, Facebook and WeLive as can be seen in Figure 167 . A user may use any of the given providers to log in.

Figure 167- Log in screen

After selecting logging account (example is shown for WeLive account Login), the user is prompted to enter their credentials as can be seen in Figure 168 .

Figure 168- Log in with WeLive credentials

In the case that the user still doesn’t have the WeLive account, he/she should go to tab REGISTER and perform REGISTRATION. Once the user has successfully logged in, in order to use application the term of use should be accepted by a user first time when he/she launch the application ( Figure 169 ).

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 118

Figure 169- Tooltip menu

After that the user should navigate to the “Local Community” tab as can be seen in Figure 170 .

Figure 170- Local community map overview

Here we can see that all events for all topics are shown on the map. These pins, when clicked, show the information related to the location of the pin. The user has two filtering options at this point. The first is to filter the events by selecting a specific local community, which can be done by clicking the “Select Community” tab as can be seen in Figure 171 .

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 119

Figure 171- Community select list

By selecting a community by clicking it in the list, you will see only the events posted by this specific community. There is also the option of selecting a topic. This is done by clicking the “Select Topic” picker as can be seen in Figure 172 .

Figure 172- Topic picker

By selecting a topic, the user will see on the map all the events, regardless of the local community that has posted it, that share this topic. As previously stated, clicking on a pin will show details of the event it represents as can be seen in Figure 173 .

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 120

Figure 173- Point of interest details

Finally, last but not least, there is the survey which users can take after using the application. Survey can be accessed from in the tooltip menu on the top right corner and it has several questions useful for application developers. The survey is the same for all applications, and the idea is to make it user friendly and easy to give a feedback. Users can rank their answer from one to five stars depending on the satisfaction level.

To leave the application, it is enough to press the Logout button that is located in the tooltip menu on the top right corner as can be seen in Figure 174 .

Figure 174- Tooltip menu and survey page

Administration part (Local Community Portal)

The WeLive Local Community Portal is a simple web application used to insert information about local communities into the database, which is used for the services used by the MojGrad android application.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 121

At this moment in time this application has a single user (a kind of super admin) who inserts the data for each local community (if in time the need arises that each local community should have its own user the application will be modified to support this feature). This application is located on the following URL: http://azuredev.dunavnet.eu/portalWeLiveLocalCommunity This application allows the user to create and insert the following information into the database: Create, Read, Update and Delete a local community post Create a topic for the local community post Adding a user ( this is here to allow for simple extension of user management later on ) Viewing the posts as pins on the map ( this is how the data is displayed in the mobile app as well) Create, Read, Update and Delete a local community post

The local community post is displayed as a point of interest on a map, or rather as a pin. The Post contains fields for the post title a select for topic options a select for the local community that is posting the information, an address field and a description field as can be seen in Figure 175 .

Figure 175 - Community post create form

All created posts are displayed in a table. Each row has two buttons at the end of the row for editing and deleting a specific post, the “+” button on the top left corner of the table is the create button which leads to the post create form. There is also a search bar that lets the user search for a specific post by the topic of the post as can be seen in Figure 176 .

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 122

Figure 176 - Post table view

Create a topic for the local community post

In the navigation bar of the application there is a “create a topic” link that when clicked opens up a modal that has a name field. Filling in the topic name and clicking “save” will create a topic. This modal can be seen in Figure 177 .

Figure 177 - Topic create modal

Adding a user

At the moment, this feature is here to make it easy to extend the application and add user management. Currently the add user form is a basic registration form witch will add a user to the database, it has a username, password and confirm password field as can be seen in Figure 178 .

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 123

Figure 178 - User registration

In the case in which each local community has its own user, this form should be extended with the selection of the local community which should be visible to the super admin only. Viewing the posts as pins on the map

The main page of the application is a map view that displays all the posts on a map as clickable pins as can be seen in Figure 179 .

Figure 179 - Post map view

On the right side of the map there is a filter portion that allows for filtering the posts by topics and local community or displaying all posts. Clicking on a pin will show the details of the post as can be seen in Figure 180 .

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 124

Figure 180 - Post pin details

Moj Grad

After registration, on the application homepage the user can see the list of reported problems and option for problem illustration on the map. In the right-hand corner of the screen, there is a menu where details about application are written, and the option for logout.

Figure 181 - Application Homepage

Report Communal Problem

New communal problem can be reported by selecting option „+“, which is located on the bottom of the screen in the right-hand corner of the user’s mobile phone.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 125

Figure 182 - Reporting communal problem

By clicking on „+“, new screen will be opened, where first the user should select the main topic of the problem: Communal problem or Situation centre.

Figure 183 - Description of new communal problem

By choosing topic Community problem reporting (Prijavljivanje komunalnih problema) , firstly from the drop- down menu the user should select problem category (kategoriju problema) , by click on the corresponding category.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 126

Figure 184 - Problems category

Then it is necessary to insert the Adress where the problem is noticed. By click on the button Take over address (Preuzmi adresu) , corresponding address will be asigned to the reported problem.

Figure 185 - Address assigning to the reported problem

In the next step it is necessary to insert Problem description (Opis problema) , and possibly a photo (fotografiju) that ilustrates problem. By click on the button Send (Pošalji) , your announcement will be completed. Review of the announced communal problems

Announce communal problems can be seen on the application „homepage“ in the form of list, with listed time when the problem was reported, address and current status. By choosing option Display the problem on the map (Prikaz problema na mapi) , city map will be opened, with marked addresses where the problems are reported.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 127

Figure 186 - Review of reported communal problems

Detailed review of the reported problems

For detailed review of the problems, the user should click on the desired problem from the list, i.e. from the map if the user chooses the option Display problem on the map (Prikaz problema sa mape) and all information will be shown: problem category, address where it is reported, display on the map, problem description and its status Unread, In the progress, Solved (Nepročitan, U obradi, Rešen ).

Figure 187 - Detailed review of the reported problems

Situation center

In the case that you have to report disaster like fire, earthquake, flood, etc. these problems could be also reported by using Moj Grad application. Announcements of situation problems

New situation problem is reported by choosing the option „+“, which is located on the bottom of the screen in the right-hand corner of your mobile phone.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 128

Figure 188 - Reporting situation problem

Then, the user chooses the topic Situation centre.

Figure 189 - Reporting situation problem, topic choice

From the drop-down menu, the user chooses the category for the situation problem he/she would like to report. Possible options are: fire, earthquake, flood, technological dangerous, terrorism, weather disaster, etc.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 129

Figure 190 - Selection of the category of situation problem

Then, the user should insert the address where the problem is located and click on Take over address (Preuzmi adresu) .

Figure 191 - Assigning address to problem

Finally, the user should describe the situation, and if he/she has a photo then he/she should insert it, and click on the button Send (Pošalji). The user’s report will be added on the list of reported problems.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 130

Review of the reported situation problems

Identically, as in the case of communal problem reporting, reported situation problem could be seen from the application „homepage “ in the form of list, with listed time when the problem was reported, address and current status. By choosing the option Display the problem on the map (Prikaz problema na mapi) , the city map will be opened, with marked addresses where the problems are reported.

Figure 192 - Review of reported situation problems

Detailed review of the reported situation problems

For detailed review of the problems, the user should click on the desired problem from the list, i.e. from the map; if he/she chooses the option Display problem on the map (Prikaz problema sa mape), all the information will be shown: problem category, address where it is reported, display on the map, problem description and it status Unread, In the progress, Solved (Nepročitan, U obradi, Rešen ).

Figure 193 - Detailed review of reported situation problems

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 131

7.3.1.4 Culture Key Culture key is an application that helps users to follow cultural events in Novi Sad. In addition to cultural events, the application provides information about basic information about museums and theatres in the city. After installation of the application the user must confirm the terms of use. If the user declines to confirm the terms, the application will be closed. After confirming the terms of use, the user will be redirected to the menu screen.

Figure 194- Terms of use

In the menu screen, the user can see available options: Cultural events / Događaji Museums and galleries / Muzeji Theatres / Pozorišta Questionnaire (red button in the right-hand corner)

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 132

Figure 195- Main screen

Cultural events In this screen, the user can find the list of all cultural events. In the list, cultural events are from the current month. After choosing one of the events, the user can see details that cultural event.

Figure 196- Cultural events screen

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 133

Museums and galleries In this screen, the user can find the list of all museums and galleries. After choosing one of the items, the user can see the details of that museum or gallery. The application is the open default web application with a link for more info.

Figure 197- Museums and galleries screen

Theatres In this screen, the user can find the list of all theatres. After choosing one of the items, the user can see details of that theatre. The application is the open default web application with a link for more info.

Figure 198- Theatres screen

Questionnaire (red button in the right-hand corner) In this screen, the user can get survey.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 134

Figure 199- Questionnaire screen

7.3.2 Building blocks The building blocks developed for the Novi Sad pilot provide functionalities that are used by the different city services explained in the previous section 7.3.1. The list of the building blocks currently provided inside the Novi Sad city pilot are explained in more details below. These services are developed as REST API using NodeJS Express Framework. Currently they are deployed locally. 7.3.2.4 Water and air quality This service provides a report about water quality of river Danube in Novi Sad. Data about water quality are obtained from this site ([15]). Information about air quality is obtained from the Environmental Protection Agency site. For WeLive Project, we developed services to get data from Environmental Protection Agency site. The building block encompasses 3 methods: Air quality for today - http://WeLive.nsinfo.co.rs/sepaToDay Air quality for week - http://WeLive.nsinfo.co.rs/sepaWeek Air quality for month - http://WeLive.nsinfo.co.rs/sepaMonth

This building block is used by Safe City Trip application. 7.3.2.5 Traffic analyzer This building block returns information about traffic fetched from service available at this URL: http://94.247.200.39/traffic This building block is used by Safe City Trip application.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 135

7.3.2.6 Citizen Data Vault API The Citizen Data Vault (CDV) is the WeLive component that allows the citizens to manage their own data in a vault. The CDV collects the citizens profile data during the interaction with the WeLive tools.. Furthermore, the CDV provides a set of API to get the user profile data and to store and manage data generated using the third party application (User Data). All these operations require WeLive Authorization. This building block is used by all application. 7.3.2.7 My Local Community API This API https://dev.WeLive.eu/marketplace/-/marketplace/view/20229 , returns data about the local communities of the city of Novi Sad and also the news feed that the each local community posts, as well as the certain topics that each community defines. There are 4 services: http://azuredev.dunavnet.eu/portalWeLiveLocalCommunity/Home/GetPosts?Id={Id} Returns the posts of a local community in relation to a topic Id. If the Id has not passed, it will return all posts, regardless of the topic http://azuredev.dunavnet.eu/portalWeLiveLocalCommunity/Home/GetLocalCommunityPosts?Id={Id} Gets the posts related to a specific local community Id http://azuredev.dunavnet.eu/portalWeLiveLocalCommunity/Home/GetTopics Gets all the topics. They are represented by objects containing an Id and a name. http://azuredev.dunavnet.eu/portalWeLiveLocalCommunity/Home/GetLocalCommunities Gets all the local community objects. These objects contain an Id, name, address, latitude and longitude This building block is used by My Local Community application. 7.3.2.8 Events in Novi Sad Returning all events in Novi Sad. Service returns JSON array with short events information. http://WeLive.nsinfo.co.rs/tons/{MM} This building block is used by Culture Key application. 7.3.2.9 Museums in Novi Sad Returning list of museums in Novi Sad. Service returns JSON array of museums in Novi Sad. http://WeLive.nsinfo.co.rs/museums This building block is used by Culture Key application. 7.3.2.10 Theaters in Novi Sad Returning list of theaters in Novi Sad. Service returns JSON array of theatres in Novi Sad. http://WeLive.nsinfo.co.rs/theaters This building block is used by Culture Key application.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 136

7.3.3 Datasets Novi Sad pilots will use only external datasets that are already publicly available and do not include any personal data (at least not during the first pilot): “Parking places ”: data about Parking places in Novi Sad, provide by PUC Parking servis Novi Sad “Schools”: all schools in Novi Sad provide by Serbian government “Bus lines”: all bus lines and bus stations in Novi Sad, provide by PU gradsko saobracajno Novi Sad “Noise”: noise report form 2014 – 2016 provide by City Administration for Environmental Protection “Taksi stajalista”: taxi station in Novi Sad, provided by tourist organization of Novi Sad “Bankomati”: ATMs , provided by tourist organization of Novi Sad ”PARKING ZA TURISITČKE AUTOBUSE”: parking for tourist buses, provided by tourist organization of Novi Sad “Fakulteti” : Registry of faculties in Novi Sad, provided by tourist organization of Novi Sad “Pozorista”: registry of theatre in Novi Sad, provided by tourist organization of Novi Sad “Parkinzi za bicikle”: registry of bike parking, provided by tourist organization of Novi Sad “Policija”: polices stations in Novi Sad, provided by tourist organization of Novi Sad “Sudovi”: courts in Novi Sad, provided by tourist organization of Novi Sad “Poste”: post offices in Novi Sad, provided by tourist organization of Novi Sad “Bolnice”: hospitals in Novi Sad, provided by tourist organization of Novi Sad “Sportski centri I nautika” : sport centers in Novi Sad, provided by tourist organization of Novi Sad “kulturni centri”: Cultural centers in Novi Sad, provided by tourist organization of Novi Sad “Galerije”: gallerys in Novi Sad, provided by tourist organization of Novi Sad “Parking zone TONS”: parking zones in Novi Sad, provided by tourist organization of Novi Sad “Apotekarska ustanova Novi Sad”: registry of pharmacies “Broj stanovnika po naselju” : population by settlements in Novi Sad “Starosna struktura po mestima”: age structure of the population by places “Muzeji”: Museums in Novi Sad “Turisticka organizacija”: Tourist offices in Novi Sad 7.3.1.5. Dataset quality report Novi Sad pilot has no broken links. Table X shows the number of stars earned by datasets provided by Novi Sad city pilot in the Linked Data 5-star scale.

0 stars 1 star 2 stars 3 stars 4 stars 5 stars Average stars

2 0 0 23 0 0 2.8

Table 14 – Summary of starts earned by datasets from Novi Sad pilot.

7.3.1.6. Recommendations Novi Sad pilot has not too much datasets, so its main concern could be to increase the number of open datasets.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 137

8. CONCLUSIONS In this deliverable we reported about the environments created in 3 three cities and 1 region where the WeLive project is running the second round of its pilot experimentation. Such environments were described under all points of view. We started with recalling the common infrastructural component consisting of the centralized instance of the WeLive framework. Then, for each of the pilot cities and the region, we described the peculiarities of the relevant environments both from the point of view of possible other pieces of local pieces of infrastructures integrated into the common framework and from the point of view of the artefacts made available onto the framework itself. Instances of such local infrastructures are the pre-existing open data and open service catalogues available in some pilot cities/region. About artefacts, all pilot task forces described the services, the building blocks and the actual datasets they have made available onto the framework to enable the activation of the urban service co-creation process. We also focused on the activities that led to the creation of such environments, by briefly recalling the engagement processes that took place in each pilot city/region, thus establishing a link between the aforementioned artefacts and the activities that generated them. The description of such environments encompasses also the update of the information provided about the population of the WeLive framework for the first pilot phase. The quantitative outcome stemming from the population activities is summed up in the Table 15 (in parenthesis the values related to the first pilot phase population):

Pilot city/region Datasets Building blocks Mobile apps

Trento 200 (16) 15 (10) 5 (3)

Bilbao 166 (164) 14 (6) 5 (3)

Helsinki-Uusimaa 31 (31) 21 (20) 5 (3)

Novi Sad 23 (23) 10 (3) 5 (3)

TOTAL 420 (237) 60 (39) 20 (12)

Table 15 – Quantitative outcome of population activities

This deliverable provided an update of the contents of the first version of the same document [38], both by completing and extending the information already provided – for instance, improving the details about the first pilot phase artefacts with more updated information about usage, enhancements, etc. - and by adding brand new material which documents the population of the WeLive framework for the second pilot phase of the project. This deliverables also addressed some of the recommendations received by the project reviewers in the previous iterations, and describes those actions that represent the consortium reply to such recommendations. In particular, good care was taken of describing how some of the points recalled in the document “Address of review recommendations in Periodic Report 2” [39] were tackled: Provide evidence that mobile apps are present on Google Play, WeLive Marketplace, WeLive Player Clarify process to devise app Explicitly state the link between the apps and the process/ideas/needs; Explain concretely how the user engagement helped in delivering better services Highlight possible demographic info about people proposing the implemented services

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 138

Describe the link between apps and other artefacts (building blocks, datasets) Finally, the activities related to the population of the framework took advantage of the results obtained during the first population of the framework. We are not only referring to the concrete results in terms of artefacts realized but also to less tangible achievements. In particular, the collaboration amongst the municipalities and one region involved in the pilots brought them to compare the relevant experiences made during the population and produced some consideration that were very useful for the second population round and that constitute the basis for the future adoption of such results. The first of such heritage is the actuation of building block reuse that was applied by some pilots to develop or improve the applications. Then, the same concept of reuse has been applied to the developed apps themselves. The adaptation of developed apps or parts of them in order to be deployed by other cities has been enacted. Finally, at the level of the datasets, the opportunity of reusing data has been assessed turning in the release of datasets that are similar to the ones available in other pilot cities.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 139

9. ABBREVIATIONS

API Application Programming Interface

BB Building Block

CKAN Comprehensive Knowledge Archive Network

CNS Cloud ‘N’Sci

CSV Comma Separated Value

DCAT Data Catalog Vocabulary

DoA Description of Action

DXF Drawing eXchange Format

EU European Union

GML Geography Markup Language

GTFS Google Transit Feed Specification

HTTP Hypertext Transfer Protocol

ICT Information and Communication Technologies

JSON JavaScript Object Notation

KML Keyhole Markup Language

KML Keyhole Markup Language

ODS Open Data Stack

PaaS Platform as a Service

POI Point Of Interest

REST Representational State Transfer

SHP Extension of the shape files

USDL Unified Service Description Language

WADL Web Application Description Language

WP Work Package

WSDL Web Service Description Language

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 140

10. REFERENCES

[1] Trentino open data portal, http://dati.trentino.it/ H2020 -INSO -2014, WeLive project deliverable, “D1.3 - WeLive scenarios, services and building [2] blocks v1 “, final version, WeLive consortium, September 2015 H2020 -INSO -2014, WeLive project deliverable, “D3.1 – Methodologies and validation of the [3] integration of the WeLive environment v1“, final version, WeLive consortium, September 2016 H2020 -INSO -2014, WeLive project deliverable, “D2.1 - Report on the WeLive Open Innovation [4] and crowdsourcing tools v1“, final version, WeLive consortium, December 2015 H2020 -INSO -2014, WeLive project deliverable, “D2.3 - WeLive Open Innovation and [5] crowdsourcing tools v1 “, final version, WeLive consortium, December 2015 H2020 -INSO -2014, WeLive project deliverable, “D2.5 - Report on the Open Data and User [6] generated Data Layer v1 “, final version, WeLive consortium, March 2016 H2020 -INSO -2014, WeLive project deliverable, “D2.7 - Open Data and User generated Data [7] Layer v1“, final version, WeLive consortium, March 2016 H2020 -INSO -2014, WeLive project deliverable, “D2.9 - Report on the WeLive Open Service [8] Layer v1“, final version, WeLive consortium, March 2016 H2020 -INSO -2014, WeLive project deliverable, “D2.11 - Open Service Layer v1“, final version, [9] WeLive consortium, March 2016 H2020 -INSO -2014, WeLive project deliverable, “D2.13 - Report on the Tools and components [10] for personalization and transparency v1 “, final version, WeLive consortium, March 2016 H2020 -INSO -2014, WeLive project deliverable, “D2.15 - Tools and components for [11] personalization and transparency v1 “, final version, WeLive consortium, March 2016 H2020 -INSO -2014, WeLive project deliverable, “D3.3 – Guidelines for the integration and [12] population of the WeLive environment v1“, final version, WeLive consortium, September 2016 H2020 -INSO -2014, WeLive Annex I to the GA “Description of Action” (645845). WeLive – A [13] neW concept of pubLic administration based on citizen co-created mobile urban services, February 2015. Online documentation of the WeLive Open Data Stack component, [14] https://dev.WeLive.eu/documentation/user-guide/ods/index.html

[15] Novi Sad Environmental Protection Agency site, http://80.93.233.118:8080/apex/f?p=406:2:0

[16] Relocation advisor app Web link, http://relocation-advisor.dev.WeLive.eu/account/login

[17] Safe City app Web link, http://safe-trip.dev.WeLive.eu/safe-trip/account/login

[18] Helsinki Region Infoshare Web link, http://www.hri.fi/fi/

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 141

Innovation and entrepreneurship in education Web link, [19] https://innovationenglish.sites.ku.dk/model/double-diamond-2/

[20] The Six Cities Strategy Web link, https://6aika.fi/

[21] Kauppinen, S., Luojus, S. & Tähtinen, L. (Forthcoming) Open innovation in public sector.

[22] Double Design Process model, Design Council web linkhttp://www.designcouncil.org.uk/

[23] CKAN report extension, https://github.com/datagovuk/ckanext-report

[24] CKAN Quality Assurance extension, https://github.com/ckan/ckanext-qa

[25] Open Data Euskadi Portal, http://opendata.euskadi.eus

[26] Bilbao Open Data Portal, http://www.bilbao.eus/opendata

H2020-INSO-2014, WeLive project deliverable, “D1.4 - WeLive scenarios, services and building [27] blocks v2 “, final version, WeLive consortium, April 2017

H2020-INSO-2014, WeLive project deliverable, “D2.2 - Report on the WeLive Open Innovation [28] and crowdsourcing tools v2“, final version, WeLive consortium, April 2017

H2020-INSO-2014, WeLive project deliverable, “D2.4 - WeLive Open Innovation and [29] crowdsourcing tools v2 “, final version, WeLive consortium, March 2017

H2020-INSO-2014, WeLive project deliverable, “D2.6 - Report on the Open Data and User [30] generated Data Layer v2 “, final version, WeLive consortium, March 2017

H2020-INSO-2014, WeLive project deliverable, “D2.8 - Open Data and User generated Data [31] Layer v2“, final version, WeLive consortium, March 2017

H2020-INSO-2014, WeLive project deliverable, “D2.10 - Report on the WeLive Open Service [32] Layer v2“, final version, WeLive consortium, April 2017

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 142

H2020-INSO-2014, WeLive project deliverable, “D2.12 - Open Service Layer v2“, final version, [33] WeLive consortium, March 2017

H2020-INSO-2014, WeLive project deliverable, “D2.14 - Report on the Tools and components [34] for personalization and transparency v2 “, final version, WeLive consortium, April 2017

H2020-INSO-2014, WeLive project deliverable, “D2.16 - Tools and components for [35] personalization and transparency v2 “, final version, WeLive consortium, March 2017

H2020-INSO-2014, WeLive project deliverable, “D3.2 – Methodologies and validation of the [36] integration of the WeLive environment v2“, final version, WeLive consortium, April 2017

H2020-INSO-2014, WeLive project deliverable, “D3.4 – Guidelines for the integration and [37] population of the WeLive environment v2“, final version, WeLive consortium, April 2017

H2020-INSO-2014, WeLive project deliverable, “D3.5 – Trento, Bilbao, Finnish Region, and Novi [38] Sad Environment v1“, final version, WeLive consortium, December 2016

H2020-INSO-2014, WeLive project deliverable, “Address of review recommendations in [39] Periodic Report 2 “, final version, WeLive consortium, July 2017

H2020-INSO-2014, WeLive project deliverable, “D4.4 – Citizens’ & Stakeholders’ engagement [40] & cooperation plan v2” final version, WeLive consortium, May 2017

[41] WeLive platform Datasets component, https://dev.WeLive.eu/ods/en/organization/trento

Trento road graph dataset, http://dati.trentino.it/dataset/grafo-stradale-vie-soggette-a- [42] pulizia-strade

Trento street cleaning and no parking areas dataset, http://dati.trentino.it/dataset/pulizia- [43] strade-e-relativi-divieti-di-sosta-autunno-2017

[44] W3C Data Catalog Vocabulary (DCAT), https://www.w3.org/TR/vocab-dcat/

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 143

11. COMMENTS FROM EXTERNAL REVIEWERS 11.1. NOVI SAD 15/12/2017

Score Issue Yes No Comments (1=low to 5=high) Is the architecture of the document Yes 5 correct? Does the architecture of the document Yes 5 meet the objectives of the work done? Does the index of the document collect Yes 5 precisely the tasks and issues that need to be reported? Is the content of the document clear Yes 5 and well described? Does the content of each section Yes 5 describe the advance done during the task development? Does the content have sufficient Yes 5 technical description to make clear the research and development performed? Are all the figures and tables Yes 4 Some are missing numbers, numerated and described? some images, and some explanation to what they refer to Are the indexes correct? Yes 5 Is the written English correct? Yes 4 Overall it is very good Main technical terms are correctly Yes 4 Some partners need to amend referenced? their data still Glossary present in the document? Yes 5

Jelena Jakovljev [email protected] Municipality of Novi Sad

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 144

11.1. LAUREA 12/12/2017

Score Issue Yes No Comments (1=low to 5=high) Is the architecture of the document x 5 correct? Does the architecture of the x 5 document meet the objectives of the work done? Does the index of the document x 5 collect precisely the tasks and issues that need to be reported? Is the content of the document clear x 4 and well described? Does the content of each section x 5 describe the advance done during the task development? Does the content have sufficient x 5 technical description to make clear the research and development performed? Are all the figures and tables x 2 The numbers are wrong. There numerated and described? are two Figure 1 descriptions, which distorts the entirety of the numbering. In addition, many of the figures don’t have references in the text. Are the indexes correct? x 5 Is the written English correct? x 5 Main technical terms are correctly x 5 referenced? Glossary present in the document? x 5

Lassi Tähtinen [email protected] Laurea University of Applied Sciences

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 145

12. ANNEX I – ETHICAL COMPLIANCE CHECK

1) How should we take into All the activities related to the setup of the WeLive environments account the WeLive Code of has been conducted taking into account the principles of the Conduct? Does our work support WeLive code of conduct. In particular, the processes for the the WeLive Innovation model? selection of the artefacts to be loaded onto the framework adheres Should the WeLive Code of strictly to point 1 and 2 of the WeLive Code of Conduct. Point 4 is Conduct and/or Innovation model addressed explicitly, by describing this selection process as part of be developed based on our work? the deliverable. Users’ data within the services provided for the (> see the WeLive Code of population of the framework are managed fulfilling the dignity, Conduct) privacy and protection requirements stated in point 7. About the support provided by the work described in this deliverable to the WeLive Innovation model, it has been recalled in the appropriate places in this document how the population of the framework represents itself a means by which the WeLive Innovation Model is supported and the WeLive Innovation Process is triggered. 2) What requirements does the The population of the WeLive framework described in this new Data Protection Act sets for document took place in 2016 and 2017 and, therefore, it is not our work? Consent forms? Access subject to the prescription of the new Data Protection Act. Of to data and right to be forgotten? course, when the new Data Protection Act will come into play all Transfer to third countries? the artefacts (services, building blocks and datasets) will be revised Privacy by Design? The use of data to assess their compatibility with the new regulations. for public purposes? The governance model and responsibilities? Hackering issues? (> see WeLive Data protection document, the New Data Protection Act and D8.6) 3) How should we take into All the services developed for the population of the framework account WeLive Terms of Use in force users to read and accept the WeLive Terms and Conditions our development work? Should before entering the service itself. Such terms have been updated they be developed based on what during the development work as required and accordingly to the we will do? (> see WeLive Terms suggestions received. of Use and D8.6) 4) How should we take into These questions do not apply since the work described in this account Consent Forms, data document does not focus on that kind of citizens’ engagement that protection and authorizations in involve consent forms, collection of data and authorizations. our research? Is it necessary to collect personal information? How is our data management? (> see the D5.3, current templates for the Consent forms, D8.1 and D8.6)

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 146

5) Is accuracy and precision of This question does not apply since the work described in this WeLive personal/other data an document does not focus on that kind of citizens’ engagement that issue to be taken into our involve consent forms, collection of data and authorizations. development work? (> see the D5.3) 6) How should we make it possible These questions do not apply since the work described in this for vulnerable people to also take document does not focus on that kind of citizens’ engagement that part into development work? How involve consent forms, collection of data and authorizations. are the Consent forms? Are the participating methods suitable? How about marketing material? (> see the D5.3) 7) Does the local data protection Local data protection regulations impose constraints that must be set requirements for our work? fulfilled when exposing datasets onto the WeLive framework. The Does our work deal with data population activities presented relatively to datasets will cause un transfer to third countries? Do we update of the data management plan. When populating the need authorizations for the use of platform we took care of providing the right acknowledgement and external data? (> see local data attribution to the owner or distributor of the data. protection act (and after 2018 the new Data Protection Act), D8.42 and D8.4) 8) Is there any other issues, which No other issue. are relevant from the viewpoint of our work? If yes, discuss the situation with the Ethics Board before starting the work.

D3.6 – Trento, Bilbao, Finnish Region and Novi Sad Environment v2 page 147