Developing Open Data in Tampere

Joonas Dukpa, Project Manager, Data & APIs, IT Management

1 When data is open data? 1 LEGALLY OPEN The work must be in the public domain or provided under an open license.

2 TECHNICALLY OPEN xml, json, csv, kml, The work must be provided in a form readily processable by a computer and where the individual elements of the work can be easily geotiff... accessed and modified. 3 FREE OF CHARGE The work must be provided as a whole and at no more than a reasonable one-time reproduction cost, and should be downloadable via the Internet without charge.

2 Why open data?

"City of Tampere sees open data as an accelerator for creating new, customer oriented services and applications agilely.”

- Jarkko Oksala, CIO, City of Tampere

3 How?

• Started fast with ”low hanging fruits” o Datasets that are technically available o Datasets that have clear ownership o Datasets that aren’t restricted by privacy or other legislative issues o Actual demand for a dataset not mandatory

4 What?

• Static data: • Top 10 now: o Financial data o Unity 3D model o Statistical data o Buildings in Tampere o 3D models o Procurements o GIS Data o Combined detailed plan map • Real-time data: o Traffic lights API Base map of Tampere o Public transport o Public Transport API o Parking data o Aerial Photograph of Tampere o Roadworks and incidents o 1946 o Streetlights and maintenance o Income and Expenditure o Events data o Noise pollution analysis

5 Case: Sun Energia

http://kartat.tampere.fi/ http://www.sunenergia.com/

6 Open Data Portal

• Open Source project with six largest cities in Finland (Tampere, Helsinki, Espoo, Vantaa, Turku, Oulu) • Multilingual: Finnish, Swedish, English • Shared codebase: https://github.com/6aika/sixodp • Four separate instances for each region o data.tampere.fi, hri.fi, data.ouka.fi and data.lounaistieto.fi • Combines CKAN with Wordpress • Running on Amazon Webservices

7 Development model

• Co-operative development model • Costs split between cities • Separate instances enable flexibility in development • One city can procure new features individually if necessary • So far all development done together • Open development tools: Github, Taiga, Slack

8 Future of open data

Together, deciding what APIs to implement and Common APIs what standards and technologies to use. Collaboration on implementation of APIs.

Together, finding the best data standards and Common data models. Harmonizing datasets. Publishing guides models and recommendations.

Together, building a CKAN based, open source Open data data portal to ease opening, managing and using platform data.

Together, activating businesses to utilize open data and APIs. Constant dialogue between the More business data producers and users. Sparring and trainings for companies. Visibility on different channels.

9 Joonas Dukpa [email protected]

10