Datasets

New in version 2020.09: New domain category Other, which includes dataset that do not belong to existing domains

New in version 2020.09: New description of domains, new diagrams that show the datasets encompassed in each domain

New in version 2020.10: Information about licensing of data contained in the Open Data Hub responses

New in version 2020.10: Links from the dataset lists to the howto section

New in version 2021:01: access to data using R

Changed in version 2021.01: Reorganised presentation of the Accessing data in the Open Data Hub section

New in version 2021.01: access to data with SPARQL

New in version 2021.02: Open Data Hub Virtual Knowledge Graph and description of underlying Knowledge Model

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

Changed in version 2020.09: Updated the list of 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:

  • Autostrada del Brennero/Brennerautobahn management of the A22 motorway infrastructure

  • Alperia/Neogy energy provider for South Tyrol

  • APPA Bolzano South Tyrolean agency for the environment

  • APPA Trento Trentino Agency of the environment

  • Bezirksgemeinschaft Burggrafenamt Comunità Comprensoriale Burgraviato

  • Carsharing Alto Adige via its technological partner DB Rent

  • CISMA bluetooth sensors

  • IDM Südtirol/Alto Adige trailblazer for economic development in South Tyrol

  • H2 Südtirol Alto Adige energy company

  • HGV Hoteliers- und Gastwirteverband

  • Inno.vìe mobility solutions

  • LTS South Tyrol Association of Tourism Organisations

  • Municipality of Bolzano

  • Municipality of Merano

  • Municipality of Rovereto

  • Municipality of Trento

  • NOI Techpark technology and science park of South Tyrol

  • Route220, Nevicam and Driwe e-charging stations provider

  • SASA public transport operator

  • SIAG Südtirol Informatica AG - Informatica Alto Adige

  • Südtirol Wein - Vini Alto Adige consortium of South Tyrol Wines

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.

License of the JSON Responses

Whenever you query the data in the Open Data Hub, the snippet that you retrieve always includes a block of information called LicenseInfo, similar to the following one:

1
2
3
4
5
6
7
8
{
   "LicenseInfo": {
     "Author": "",
     "License": "CC0",
     "ClosedData": false,
     "LicenseHolder": "https://www.lts.it"
   }
}

The highlighted line shows a licence, which in this case is CC0, i.e., public domain and therefore freely reusable.

This block is always included as a child node within a JSON record that starts with an ID and a number of additional information, which may include also hyperlinks to resources that are external to the Open Data Hub, like for example this example which refers to a webcam and contains a link to an external provider where to find actual images from that webcam (snippet code shortened for the sake of simplicity):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
{
  "Id": "D3659E1F111C4CDB2EC19F8FC95118B7",
  "Active": true,
  "Streamurl": null,
  "Webcamurl": "https://webtv.feratel.com/webtv/?&pg=5EB12424-7C2D-428A-BEFF-0C9140CD772F&design=v3&cam=6323&c1=0",
  "LicenseInfo": {
    "Author": "",
    "License": "CC0",
    "ClosedData": false,
    "LicenseHolder": "https://www.lts.it"
  }
}

Whenever hyperlinks like the one shown in line 5 above appear, it must not be implied that the license mentioned in the LicenseInfo block (again, CC0) is applied to them: everything contained in that link may be covered by a different licence.

Indeed, the Licence mentioned in LicenseInfo nodes refer only to content of the parent node–i.e., the one that starts with “Id”, not to the content of any of the other children nodes, including Streamurl and Webcamurl.

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

Changed in version 2020.06: Direct link to the browsable version of the datasets.

Changed in version 2020.09: Improved description of datasets in the mobility domain, including external links, use cases, and Data Providers.

Changed in version 2020.09: added dropdowns to the list of datasets to improve usability

_images/Mobility-domain.png

Figure 3 The dataset in the Mobility Domain at a glance.

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

Note

Recall that the API v1 for the Mobility Domain is now deprecated.

The description of each dataset includes the following information:

Output

The output format of the API call

E-mail contact

An e-mail contact for the dataset

API version

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

StationType

The direct link to each stationType included in the dataset

Use cases and info

Link to web sites that use the dataset and to use cases based on the dataset

Web component

Link to Web Components developed on top of the dataset (optional)

Sources

The list of Data Providers whose data compose the dataset

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.

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

See also

The following howto will help you access data in the Mobility domain:

How to Access Mobility Data With API v2 Access and technical details about the available data

Other howtos are available in the dedicated section.

Traffic

The Mobility/Traffic sub-domain contains data about traffic (like e.g., real time traffic load of a street, environmental measurement) that are useful to plan a trip with an own means of transport, for example a car, or a bike.

Mobility

The Mobility/Mobility sub-domain contains data about public transportation, sharing of transport means, and recharging stations for e-cars.

Changed in version 2020.09: Improved description of datasets in the mobility/mobility domain, including new information

Deprecated since version 2020.10: Public Transportation dataset

Datasets in the Tourism Domain

_images/Tourism-domain.png

Figure 4 The dataset in the Tourism Domain at a glance.

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

Datasets presented here are related to all kind of touristic activities in South Tyrol. By exploring this domain, it is possible to find information about winter and summer offers from local touristic boards, information about weather, hotels and accommodation, Points of Interests, and a lot more.

Changed in version 2020.09: Removed datasets not offered directly from Open Data Hub (siag.museum and siag.weather)

Changed in version 2020.09: Renamed weather-siag dataset to weather-forecast

Changed in version 2020.09: Ordered datasets in alphabetical order

New in version 2020.09: Added article, common, venue and eventshort datasets

Changed in version 2020.10: Changed identifier of datasets activity, event, gastronomy, package, and POI

New in version 2020.10: API URL for all Tourism datasets.

The following information is provided for each dataset in the Tourism domain:

Output

The output format of the API call

E-mail contact

An e-mail contact for the dataset

API version

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

Swagger URL

The URL of the swagger interface to the data

API URL

The URL of the browsable version of the dataset

Use cases and info

Link to web sites that use the dataset and to use cases based on the dataset

Android App

Link to app for mobile phones developed using the data in the dataset

Sources

The list of Data Providers whose data compose the dataset

SPARQL Endpoint

Dataset is accessible through the SPARQL Endpoint 1

1

This information is provided only if the dataset is accessible through SPARQL.

See also

The following howto will help you access data in the Tourism domain:

How to access Tourism Data? Access and technical details about the available data

How to use the Open Data Hub’s Tourism Data Browser? Browse Open Data offered by the Open Data Hub

Quick and (not-so) Dirty Tips for Tourism (AKA Mini-howtos) Quick tips and troubleshooting

Other howtos are available in the dedicated section.

Datasets in Other Domains

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

Output

JSON, mime-type application/json

E-mail contact

API version

v2

StationType

CreativeIndustry

Web Component

Creative Industries

Sources

IDM

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

StationType

NOI-Place

Use cases and info

https://maps.noi.bz.it/

Sources

NOI Techpark

https://alpinebits.opendatahub.bz.it/AlpineBits

This endpoint provides data from the AlpineBits Open Standard, whose purpose it to ease B2B data exchange among actors involved in the alpine tourism.

Documentation for developers, including sample code snippets and additional material can be found on AlpineBits dedicated page for developers https://www.alpinebits.org/developers/.

Various development and testing tools can be found on http://development.alpinebits.org/#/home.

Output

XML, multipart/form-data

E-mail contact

help@opendatahub.bz.it

AlpineBits versions

v2017-10, v2018-10 (coming soon 2020-10)

AlpineBits Endpoint

https://alpinebits.opendatahub.bz.it/AlpineBits

The Open Data Hub Virtual Knowledge Graph

New in version 2021.02: Description of the Knowledge Model underlying datasets Accommodation, Gastronomy, and Event datasets

Some datasets in the Open Data Hub, namely Accommodation, Gastronomy, and Event, are organised into a Virtual Knowledge Graph that can be accessed using SPARQL from the dedicated SPARQL endpoint. In order to define more precise queries, this section describes the Knowledge Models (KM) underlying these datasets; the description of each KM is accompanied by an UML diagram which shows the KM at a glance.

Besides standard W3C’s OWL and RDF vocabularies, the Open Data Hub VKG uses:

  • schema.org for most of the entities used

  • geosparql for geo-references and coordinates of objects

  • purl for linking to related resources

Common Notation

Diagrams use UML class diagram formalism widely adopted in Knowledge Representation and in particular in the W3C’s Recommendation documents for the Semantic Web. The following additional notation applies:

Prefix

The default prefix used for classes and properties is http://schema.org/. This means that, unless differently stated, the definition of classes and properties, including their attributes, rely on a common standard as defined in schema.org’s vocabulary. As examples, see the LodgingBusiness class and the containedInPlace property.

Hint

Other prefixes are explicitly pre-pended to the Class or Property name, like e.g., noi:numberOfUnits.

Arrows

Arrows with a white tip denote a sub-class relationship, while black tips denote object properties.

Cardinality

Cardinality of 1 is usually not shown, but implied; the look across notation is used. For example, the image on the right-hand side–excerpt from the event dataset VKG–can be read as 0 to N MeetingRooms are ContainedInPlace Place.

_images/cardinality.png

See also

The SPARQL howto, which guides you in interacting with the SPARQL endpoint.

W3C Recommendation for OWL2 and RDF.

Official Specification of UML Infrastructure are available from Object management group