Datasets

The goal of the Open Data Hub project is to make available datasets containing data about the South Tyrolean ecosystem, to allow third parties to develop novel applications on top of them, consuming the exposed data. These applications may range from a simple processing of datasets to extract statistical data and to display the result in different graphic formats like pie-charts, to far more complex applications that combine data from different datasets and correlate them in some useful way.

As seen in Figure 1, data originate from different domains (Mobility, Tourism, and so on); they are gathered from sensors and packed together by Data Providers. Sensors can be for example GPS devices installed on buses that send their real-time geographic position or a small electronic device on a plug of an e-charging station that checks the if the plug is being used or not, to let people know that the charging outlet is available.

Datasets are accessible through a REST API, the URL of each endpoint is given along with other information in the description of each dataset, see the lists of datasets in the remainder of this section.

Data Providers

A Data Provider is any entity that shares their Open Data with the Open Data Hub project, allowing their free reuse (ideally under a free licence like CC0 license (public domain) or CC BY-SA license) from any third-party that relies on the Open Data Hub to build their application. These entities can be private companies or enterprises, public bodies, and even private citizen, if they have interesting data about South Tyrol to share.

The Open Data exposed by the Open Data Hub originate from data and datasets owned by different actors (called Data Providers) which are at this time mostly local public bodies. Since there is no direct 1-to-1 correspondence between Data Providers and datasets, we currently offer a list of data providers whose data can be pulled from Open Data Hub. Indeed, an Open Data Hub dataset can be composed of data deriving from different providers, while a provider can submit to Open Data Hub multiple types of data that will belong to more than one dataset.

The Open Data Hub’s Data Providers are:

  • IDM Südtirol/Alto Adige

  • SIAG, Südtirol Informatica AG - Informatica Alto Adige

  • SASA, public transport operator

  • Alperia/Neogy, energy provider for South Tyrol

  • Municipality of Bolzano

  • Municipality of Merano

  • Municipality of Trento

  • Municipality of Rovereto

  • APPA, Trentino Agency of the environment

  • CISMA, Bluetooth sensors

  • Carsharing Alto Adige, via its technological partner DB Rent

  • LTS, South Tyrol Association of Tourism Organisations.

  • APPA, South Tyrolean agency for the environment.

  • InnoVie.

  • Südtirol Wein.

  • Route220, Nevicam and Driwe e-charging stations provider

A note about datasets.

The Open Data Hub contains many datasets: a few have been provided for testing purposes, other are meant for internal use only, and other contain only a part of their data that is available as Open Data.

While the goal of the Open Data Hub project is to expose only Open Data and the Open Data Hub team members always suggest to use CC0 license (public domain) to third-parties releasing datasets, it is not yet possible for the Open Data Hub team to guarantee the availability as open data of all the data in the datasets, because the data licensing and its distribution rights are decided by the copyright holder of each dataset.

Since some of the datasets may contain data that can not be distributed by the Open Data Hub team under an open licence like, e.g., CC0 license (public domain) or CC BY-SA license, a user will be able to retrieve from each dataset only those data that are distributed as Open Data.

At the date of writing, datasets in the Mobility and Tourism domains are available.

Accessing data in the Open Data Hub

There are different modalities to access data that are provided by the Open Data Hub, that are listed here. Currently, data from the Mobility and Tourism domains can be accessed, both from the command line and using a browser. Non-interactive access using APIs is also available. Various dedicated tutorials are available in the List of HOWTOs section; while in section Getting Involved you can find additional ways to interact with the data and the Open Data Hub team. The remainder of this section describes all the possibilities to access the Open Data Hub’s datasets and their content.

API

Programmatic and non-interactive access to the Open Data Hub’s dataset is possible using the APIs made available by the Open Data Hub Team.

The APIs are composed of a few generic methods, that can be combined with many parameters to retrieve only the relevant data and then post-processed in the preferred way.

The following table summarises how the two versions of the API can be used within the Open Data Hub’s domains.

API

Tourism

Mobility

v1

Recommended

Deprecated

v2

Recommended

There are currently two versions of the API, v1 and v2, with the former now deprecated for the Mobility domain and marked as such API v1 are now deprecated throughout the Open Data Hub documentation. New users are recommended to use the new API v2, while users of the API v1 are encouraged to plan a migration to the new API.

The new API v2 has a different approach compared to the previous version, and therefore is not compatible with the API v1, the main difference being that all data stored in the Open Data Hub can now be retrieved from a single endpoint, while with API v1 there was an endpoint for each dataset.

This change in approach requires also a breaking change for the users of API v1. The initial step, indeed, will not be to open the URL of the dataset and start exploring, but to retrieve the stationTypes and then retrieve additional data about each station. A stationType is the main object of a datasets, about which all the information in a dataset relate to; a dataset includes at least one stationType. A new, dedicated howto describing in detail the new API v2 and a few basic examples is already available in the dedicated section of this documentation.

Note

It is important to remark that the API v2 is only available for datasets in the Mobility Domain.

Browser access

Accessing data in the Open Data Hub by using a browser is useful on different levels: for the casual user, who can have a look at the type and quality of data provided; for a developer, that can use the REST API implemented by the Open Data Hub or even check if the results of his app are coherent with those retrieved with the API; for everyone in order to get acquainted with the various methods to retrieve data.

More in detail, these are the possibilities to interact with Open Data Hub’s data by using a browser:

  1. Go to the Apps built from Open Data Hub datasets section of the documentation, particularly sub-sections Production Stage Apps and Beta Stage Apps, and choose one of the web sites and portals that are listed there. Each of them uses the data gathered from one or more OPEN DATA HUB’s datasets to display a number of useful information. You can then see how data are exposed and browse them.

  2. In the same Apps built from Open Data Hub datasets section, you can also check the list of the Alpha Stage Apps and choose one of them that you think you can expand, then get in touch with the authors to suggest additional features or collaborate with them to discuss its further development to improve it.

  3. Access the ODH Tourism data browser and search for the Open Data available in the Tourism domain. You can simply use those data for your convenience, or you might even find a novel way to exploit those data and use them in an app or portal you are going to develop. A detailed howto is available: How to use the Open Data Hub’s Tourism Data Browser? to help you getting acquainted with the browser.

  4. Go to the Swagger interface of the datasets in the Tourism domain, located at http://tourism.opendatahub.bz.it/swagger/ui/index, to learn how the REST APIs are built and how you can script them to fetch data for your application. To get started, there is a dedicated howto: How to access Tourism Data? that will guide you in the first steps.

  5. Access the Swagger interface of the datasets in the Mobility domain, located at https://mobility.api.opendatahub.bz.it/v2/swagger-ui.html. Like in the case of the tourism’ Swagger interface, you can learn REST API call for that domain and fetch data for your application. There is a dedicated howto to learn more how to interact with this interface: ref:get-started-mobility

  6. Open the Analytics for Mobility web page, at https://analytics.mobility.bz.it/. This portal uses data in the mobility domain to display various information about the sensors, including their locations, what they measure, and actual data in near-real time. You can retrieve data gathered by the sensors directly from the dataset, in almost real-time.

CLI access

Unlike browser access, that provides an interactive access to data, with the option to incrementally refine a query, command line access proves useful for non-interactive, one-directional, and quick data retrieval in a number of scenarios, including:

  • Scripting, data manipulation and interpolation, to be used in statistical analysis.

  • Applications that gather data and present them to the end users.

  • Automatic updates to third-parties websites or kiosk-systems like e.g., in the hall of hotels.

Command line access to the data is usually carried out with the curl Linux utility, which is used to retrieve information in a non-interactive way from a remote site and can be used with a variety of options and can save the contents it downloads, which can them be send to other applications and manipulated.

The number of options required by curl to retrieve data from Open Data Hub’s dataset is limited, usually they are not more than 3 or 4, but their syntax and content might become long and not easily readable by a human, due to the number of filters available. For example, to retrieve the list of all points of interests in South Tyrol, the following command should be used:

curl -X GET "http://tourism.opendatahub.bz.it/api/ODHActivityPoi?pagenumber=1&pagesize=10&type=63&subtype=null&poitype=null&idlist=null&locfilter=null&langfilter=null&areafilter=null&highlight=null&source=null&odhtagfilter=null&odhactive=null&active=null&seed=null&latitude=null&longitude=null&radius=null" -H "accept: application/json"

Your best opportunity to learn about the correct syntax and parameters to use is to go to the swagger interface of the tourism or mobility domains and execute a query: with the output, also the corresponding curl command used to retrieve the data will be shown.

Authentication

The authentication layer is currently intended for internal use only. All data in the dataset that you can receive from the Open Data Hub are free to use and do not require any type of authentication.

The authentication layer can be of interest for developers who want to collaborate in the development of Open Data Hub; Details on the implementation are available in section Authentication in the Open Data Hub.

Datasets in the Mobility Domain

This section contains information about the datasets and how to access them using the API that the Open Data Hub team developed and made available.

The description of each dataset includes the following information:

  • The output format of the API call

  • An e-mail contact for the dataset

  • The versions of the API that can be used to access the dataset

  • The (new!) swagger URL of the APIs

  • The stationType that belong to each dataset

The datasets in the Mobility domain are grouped in Traffic and Mobility as follows:

Traffic

it.bz.opendatahub.bikesharing

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

Bicycle, BikesharingStation

it.bz.opendatahub.bluetooth

The data for this datasets are collected by experimental Bluetooth-based sensors and detectors currently located on various points of the streets of Bolzano and soon in other location of South Tyrol. Gathered data are then processed to obtain useful information about the traffic; therefore, data in this dataset are:

  • The total number of vehicles detected

  • An estimation of heavy and light vehicles

Collected data are also split within intervals (of e.g.,15, 30 minutes), for statistical and historical offline analysis. Moreover, the data gathered by the Bluetooth devices are used in the it.bz.opendatahub.linkstation.

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

BluetoothStation

it.bz.opendatahub.environment

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

EnvironmentStation

it.bz.opendatahub.linkstation

The data for this dataset are collected by the same Bluetooth-based sensors that are used to produce the Bluetooth dataset. Indeed, the data gathered by the sensors will be used to produce statistics about a LinkStation, which is defined as the path between an ordered pair of bluetooth stations.

  • the valid matches between pairs of Bluetooth sensors (also called Bluetooth stations).

  • The number of matches per predefined time interval (e.g., 30 or 60 minutes), like in the Bluetooth dataset

  • The estimated travel time and speed of the vehicle, computed for every 15 minutes interval only.

The definitions and algorithm used in the computations are extensively described in Section Data analysis complexity of this pdf article.

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

LinkStation

it.bz.opendatahub.parking

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

ParkingStation

it.bz.opendatahub.rwisstation

The Road Weather stations are sensors that measure both the road surface and the weather conditions.

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

RWISstation

it.bz.opendatahub.streetelements

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

Streetstation

it.bz.opendatahub.trafficstation

This datasets contains two types of data, both collected by sensors along the Italian A22 motorway.

  1. Aggregated data recorded by sensors drowned in asphalt, but separated for each lane of a street. For people in Italy, these sensors are those large rectangle boxes engraved in asphalt that you can seen also on streets in the cities.

  2. The VMS (Variable Message Sign) sensors collect data about the electronic road signs on the Motorway.

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

traffic, TrafficSensor, Trafficstation, TrafficStreetFactor, VMS

it.bz.opendatahub.weather

This dataset contains meteorological data provided by the hydrographical Department of South Tyrol.

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

MeteoStation

Mobility

it.bz.opendatahub.carpoolinghub

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

CarpoolingHub, CarpoolingService, CarpoolingUser

it.bz.opendatahub.carsharing

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

CarsharingStation

it.bz.opendatahub.echargingstation

This datasets exposes data about the existing e-charging stations in South Tyrol and their status, including historical data and usage.

Output

JSON, mime-type application/json

E-mail contact

API version

v1 API v1 are now deprecated, v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

EChargingPlug,EChargingStation

Public Transportation

This datasets shows the real time position of buses operated by SASA in South Tyrol and, through a few subsets, additional information about lines, station boards, and news.

Output

geoJSON

E-mail contact

info@sasabus.org

API version

v1

Swagger URL

http://sasabus.org/opendata

The additional subsets expose data in different formats:

  • info.opensasa.plandata (VDV 451 - VDV 452)

  • info.opensasa.stationboard (JSON)

  • info.opensasa.news (JSON)

  • info.opensasa.rssDE (XML)

  • info.opensasa.rssIT (XML)

Creative Industries

This dataset originates from data collected in the DAVINCI project, whose aims is to increase local businesses by improving innovation and digitalisation of services.

The data consists of a list of actors that operated in the creativity sector in South Tyrol and is used as data source to generate a map for a dedicated Web Component, available in Open Data Hub’s Web Component Store.

Output

JSON, mime-type application/json

E-mail contact

API version

v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

CreativeIndustry

NOI-Place

This dataset contains all places, offices, meeting rooms, and in general all points of interest located in the various buildings that compose the NOI Techpark in Bolzano-Bozen, Italy.

This dataset is used to create the interactive map of the NOI Techpark.

Output

JSON, mime-type application/json

E-mail contact

API version

v2

Swagger URL

https://mobility.api.opendatahub.bz.it/

StationType

NOI-Place

Datasets in the Tourism Domain

The following information is provided for each of the above-listed dataset:

  • The output format of the API call.

  • An e-mail contact for the dataset.

  • The versions of the API that can be used to access the dataset.

  • The swagger URL of the APIs.

Note

There is one StationType, namely MobileStation which is a mobile probe no longer active. It will always return an empty set of values, because historical data are not available in the Open Data Hub.

it.lts.accommodation

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Accommodation

it.lts.activity

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Activity

it.lts.activity_poi

This dataset contains a collection of activities and points of interest (PoI) in the South Tyrol region. The available data have been extracted from different sources, but at the moment only the data about the South Tyrolean museums and wines are freely available without authentication. These data can be obtained by using the keywords MuseumData and SuedtirolWein in the source filter of the dataset.

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/ODHactivityPoi

it.lts.event

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Event

it.lts.gastronomy

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Gastronomy

it.bz.opendatahub.location

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Common

it.hgv.package

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://service.suedtirol.info/swagger/ui/index#/Package

it.lts.poi

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Poi

it.bz.opendatahub.ski

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#!/Common/Common_GetSkiAreas

it.bz.opendatahub.snowreport

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#!/Weather/Weather_GetSnowReportBase

it.bz.opendatahub.weather-siag

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Weather

it.bz.opendatahub.webcam

Output

JSON, mime-type application/json

E-mail contact

API version

v1

Swagger URL

http://tourism.opendatahub.bz.it/swagger/ui/index#/Webcam

it.bz.siag.museum

This datasets contains information about the museums in the South Tyrol region and is retrieved directly from the Open Data portal of the Autonomous Province of Bolzano.

More information about this dataset, including metadata, is available in either Italian or German at the following URLs, respectively:

Output

JSON, CSV, XML#

E-mail contact

museen@provinz.bz.it

API version

Swagger URL

#The dataset can be dowloaded as XML using this URL:

https://cert.provinz.bz.it/musport/services/MuseumsService.MuseumsServiceHttpSoap11Endpoint/getMuseums

it.bz.siag.weather

Output

XML#

E-mail contact

meteo@provinz.bz.it

API version

Swagger URL

#The dataset in German can be dowloaded as XML using this URL: https://wetter.ws.siag.it/Weather_V1.svc/web/getLastProvBulletin