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 or ) 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 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., or , 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.

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:

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.

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.

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.

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.

Access the Swagger interface of the datasets in the Mobility domain, located at https://mobility.api.opendatahub.bz.it/. Like in the case of the tourism’ Swagger interface, you can learn REST API call for that domain and fetch data for your application. More possibilities to interact with the Mobility domain datasets and the description of the new APIv2 are described in the dedicated howto.

Open the Analytics for Mobility web page, at https://analytics.opendatahub.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.

Open the Open Data Hub Knowledge Graph Portal where you can explore all the data that are already available as a virtual knowledge graph. Here you can check out some of the precooked query to see and modify them to suit your needs with the help of W3C’s SPARQL query language; SPARQL can be used also in the Playground to freely query the endpoint.

Programmatic access

Programmatic and non-interactive access to the Open Data Hub’s dataset is possible using any of the following methods made available by the Open Data Hub team.

API

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 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.

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.

AlpineBits client

TBD

Statistical Access with R

R is a free software for statistical analysis that creates also graphics from the gathered data.

The Open Data Hub Team has developed and made available bzar, an R package that can be used to access BZ Analytics data (see also How to Access Analytics Data in the Mobility Domain) and process them using all the R capabilities. Download and installation instructions, along with example usage can be found on the bzar repository.

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:

{
   "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):

{
  "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

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.

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 linkstation dataset.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	BluetoothStation
Use cases and info	https://analytics.opendatahub.bz.it/
Sources	CISMA

it.bz.opendatahub.environment

In this dataset can be found Pollution and Air Quality data (including, but not limited to, CO, NO2, PM 2.5, PM10). Some portion of the data have been manually elaborated, with the purpose to increase data quality.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	EnvironmentStation
Use cases and info	https://analytics.opendatahub.bz.it/, Project STODT
Sources	APPA Bolzano, APPA Trento, A22 Municipality of Bolzano

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 deprecated, v2
StationType	LinkStation
Use cases and info	https://analytics.opendatahub.bz.it/
Sources	A22

it.bz.opendatahub.parking

This dataset contains two types of data:

• Parking stations - off street parking data (currently for the cities of Bolzano, Merano, Trento, Rovereto), with slot availability and predictions

• Parking sensors - on street parking data (currently Bolzano, soon Merano). Single parking slots on streets, can be within a virtual area

Output	JSON, mime-type application/json
E-mail contact	contact
API version	v1 deprecated, v2
StationType	ParkingStation, ParkingSensor
Use cases and info	https://parking.bz.it, https://mobility.meran.eu, https://analytics.opendatahub.bz.it, https://mobility.bz.it
Sources	Municipalities of Bolzano, Merano, Trento and Rovereto

it.bz.opendatahub.rwisstation

The Road Weather stations are sensors that measure both the road surface and the weather conditions. Data represent a showcase from project CLEAN-ROADS, which offered open data until 2016.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	RWISstation
Use cases and info	https://analytics.opendatahub.bz.it/, https://map.clean-roads.eu/
Sources	A22

it.bz.opendatahub.streetelements

This datasets contains historical data about air quality processing along the roads.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	Streetstation
Use cases and info	–
Sources	CISMA

it.bz.opendatahub.trafficstation (1)

This datasets contains aggregated data collected by sensors drowned in asphalt, but separated for each lane of a street. For people that travel on Italian streets, these sensors are those large rectangle boxes engraved in asphalt that you can seen also on streets in the cities.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	traffic, TrafficSensor, Trafficstation, TrafficStreetFactor
Use cases and info	https://analytics.opendatahub.bz.it/
Sources	Municipality of Bolzano, A22

it.bz.opendatahub.trafficstation (2)

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

This dataset is formally part of the traffic station dataset, but since data are specific to VMS, we split them for clarity.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	VMS
Use cases and info	https://analytics.opendatahub.bz.it/
Sources	A22

it.bz.opendatahub.weather

This dataset contains meteorological data provided by the Weather and Avalanche Services of South Tyrol and Trentino, such as Precipitation and Air temperature

This dataset contains the measurements of the weather data, not the forecast.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	MeteoStation
Use cases and info	https://analytics.opendatahub.bz.it/
Sources	Weather and Avalanche Services of South Tyrol and Trentino

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

it.bz.opendatahub.bikesharing

This dataset contains data of the bike sharing service in Bolzano and Merano, such as stations (for station based service - Bolzano), areas (for free floating service - Merano), availability, battery state, and other useful information.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	Bicycle BikesharingStation Bicyclestationbay
Use cases and info	https://mobility.merano.eu/ https://analytics.opendatahub.bz.it/
Sources	Municipalities of Bolzano and Merano

it.bz.opendatahub.carpoolinghub

This dataset contains all data of the carpooling service of the Burggrafenamt/Burgraviato region in South Tyrol, including carpooling users, car availability, and locations with accessible destinations.

Note

Only users that have explicitly expressed their consent to privacy are included, no sensitive data is stored or exchanged.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	CarpoolingHub CarpoolingService CarpoolingUser
Use cases and info	https://carpooling.bz.it/ https://mobility.meran.eu/ https://analytics.opendatahub.bz.it/
Sources	Bezirksgemeinschaft Burggrafenamt/Comunità Comprensoriale Burgraviato, Inno.vìe

it.bz.opendatahub.carsharing

This dataset contains all data of the car sharing service in South Tyrol, including stations and availability.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	CarsharingStation
Use cases and info	https://mobility.meran.eu/ https://analytics.opendatahub.bz.it/ https://mobility.bz.it/
Sources	Car Sharing Südtirol Alto Adige

it.bz.opendatahub.echargingstation

This datasets exposes data about the existing e-charging stations and plugs in South Tyrol and their status, including historical data and usage. Data about station offering Hydrogen recharged are also included.

Note

For this datasets are available also a number of Web Components, see the use cases.

Output	JSON, mime-type application/json
E-mail contact
API version	v1 deprecated, v2
StationType	EChargingPlug EChargingStation
Use cases and info	https://mobility.meran.eu/ https://analytics.opendatahub.bz.it/ https://mobility.bz.it/
Web Components	Smart Mobility Mobility E-Charging Map Mobility E-Charging Dashboard
Sources	Alperia (Neogy), Route220, nevicam, Driwe, H2 Südtirol Alto Adige

Public Transportation deprecated

Warning

This dataset is not supported anymore and will be removed from the Open Data Hub in the next future.

This dataset 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.

There are additional subsets that 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)

Output	geoJSON
E-mail contact	info@sasabus.org
API version	–
URL	http://daten.buergernetz.bz.it/dataset/southtyrolean-public-transport http://sasabus.org/opendata
Use cases and info	https://suedtirolmobil.info/, https://mobility.meran.eu/, https://analytics.opendatahub.bz.it/, https://mobility.bz.it/
Web Component	Smart Mobility
Sources	STA, SASA

Datasets in the Tourism Domain

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.

it.bz.opendatahub.package

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://service.suedtirol.info/swagger/ui/index#/Package

it.bz.opendatahub.activity

This dataset contains data about activities from LTS, including local tours, hiking, running & fitness, cross-country skiing, alpine climbing, e-bike, downhill, nordic walking, and many more. This dataset offers LTS categorization and enhanced filtering.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/Activity
API URL	http://tourism.opendatahub.bz.it/api/Activity
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Sources	LTS ActivityData

it.bz.opendatahub.event

This dataset contains data about active events provided by LTS (TIC Web): meetings, fairs, markets, performances, courses, music, festivals, hikes, trips, guided tours, exhibitions, and so on. Data about past events is also included.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/Event
API URL	http://tourism.opendatahub.bz.it/api/Event
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Android App	Südtirol Guide/Alto Adige Guide
Sources	LTS
SPARQL Endpoint	https://sparql.opendatahub.bz.it

it.bz.opendatahub.gastronomy

This dataset contains data about gastronomy locations from LTS, including restaurants, bars, bistros, pubs, apres ski, pizzerias, fast food, cafeterias, vinotheques, beer gardens, mountain refuges, alpine huts, ski huts, etc. This dataset offers enhanced filtering (cuisine types, ceremony codes, dish codes etc.).

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/Gastronomy
API URL	http://tourism.opendatahub.bz.it/api/Gastyronomy
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Sources	LTS
SPARQL Endpoint	https://sparql.opendatahub.bz.it

it.bz.opendatahub.poi

This dataset contains data about PoIs from LTS, such as beauty and wellness centres, bikes, castles, climbing halls, cocktail bars, e-bike rentals, fashion shops, pharmacies, gas stations, car parks, shops, ski schools, and many more. This dataset offers LTS categorisation.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/Poi
API URL	http://tourism.opendatahub.bz.it/api/Poi
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Sources	LTS PoiData

it.bz.opendatahub.accommodation

This dataset contains various data about accomodation in South Tyrol, including information about the rooms.

Besided with Open Data Hub API, this dataset can be queried with the AlpineBits protocol.

Output	JSON, mime-type application/json
E-mail contact
API version	v1, AlpineBits HotelData 2017-10, 2018-10, and soon 2020-10
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/Accommodation
API URL	http://tourism.opendatahub.bz.it/api/Accommodation
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Android App	Südtirol Guide/Alto Adige Guide
Sources	LTS
SPARQL Endpoint	https://sparql.opendatahub.bz.it

it.bz.opendatahub.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 and also offer IDM categorisation. This is a kind of superdataset, which includes also poi dataset, activity dataset, and gastronomy dataset.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/ODHactivityPoi
API URL	http://tourism.opendatahub.bz.it/api/ODHActivityPoi
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Android App	Südtirol Guide/Alto Adige Guide
Sources	LTS ActivityData, LTS PoiData, LTS GastronomicData, SuedtirolWein, SIAG Museum data, IDM Content and other Sources

it.bz.opendatahub.common

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/Common

it.bz.opendatahub.eventshort

This dataset contains events provided by NOI Techpark, Eurac and St. Virtual.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/EventShort
API URL	http://tourism.opendatahub.bz.it/api/EventShort
Use cases and info	https://today.noi.bz.it/ https://noi.bz.it/event-calendar/ https://virtual.noi.bz.it/programma.html
Sources	LTS

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#/Location
API URL	http://tourism.opendatahub.bz.it/api/Location

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
API URL	http://tourism.opendatahub.bz.it/api/SkiArea

it.bz.opendatahub.snowreport

The Snow Report Data dataset contains detailed reports of all South Tyrolean Ski Areas, including an aggregation of different Datatypes. Status and conditions of Lifts, Slopes, Ski tracks, Sledges, Measuring points (like e.g., snow height and last snow day), and Ski Areas basic data are part of this dataset.

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
API URL	http://tourism.opendatahub.bz.it/api/Weather/SnowReportBase
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Sources	LTS, IDM

it.bz.opendatahub.venue

This dataset contains events location provided by LTS such as info about a location (e.g. number of seats, number of seats for disabled people, venue, etc.) or info to book an event location (e.g. prices, room configuration, etc.). Data are accessible in AlpineBits DestinationData format.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/Venue
API URL	http://tourism.opendatahub.bz.it/api/Venue
Use cases and info	https://databrowser.opendatahub.bz.it/
Sources	LTS

it.bz.opendatahub.weather-forecast

This dataset contains weather forecast for South Tyrol. Updated daily at 07:00 AM and 11:00 AM (Sundays only at 10 AM), the bulletin contains the following forecasts:

• current and next day weather, and five days evolution in the whole South Tyrol

• for current and next day in mountain

• current weather and next two days evolution for each South Tyrolean districts.

  All data is requested live through the Weather service of the Province of Bolzano-Bozen (South Tyrol). Data is available in English, German, and Italian language.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/weather
Use cases and info	https://databrowser.opendatahub.bz.it/
Android App	Südtirol Guide/Alto Adige Guide
Sources	SIAG

it.bz.opendatahub.webcam

This dataset contains Webcam Data. All data is synchronized daily from LTS (Webcam links). All data is transferred and is daily updated.

Output	JSON, mime-type application/json
E-mail contact
API version	v1
Swagger URL	http://tourism.opendatahub.bz.it/swagger/ui/index#/WebcamInfo
API URL	http://tourism.opendatahub.bz.it/api/WebcamInfo
Use cases and info	https://databrowser.opendatahub.bz.it/ https://suedtirol.info/
Sources	Webcam links from LTS and IDM

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.

Accommodation Dataset

Central class in this dataset is LodgingBusiness, to which belong multiple Accommodations.

A LodgingBusiness has as attributes geo:asWKT, email, name, telephone, and faxNumber and relations

• address to class PostalAddress, which consists of streetAddress, postalCode, and AddressLocality

• geo, i.e., a geographical location, to class GeoCoordinates, consisting of latitude, longitude, and elevation

There are (sub-)types of LodgingBusiness–called Campground, Hotel, Hostel, and BedAndBreakfast–sharing its attributes and relations.

An Accommodation is identified by a name and a noi:numberOfUnits and has relations

• containedInPlace to LodgingBusiness (multiple Accommodations can belong to it)

• occupancy to QuantitativeValue, which gives the maxValue and minValues of available units of accommodation and a unitCode.

noi:numberOfUnits is the number of available rooms, suites, apartments, etc. that are available in that Accommodation

geo:asWKT is a method used by opengis.net’s geosparql <http://www.geosparql.org/> to express geographic coordinates in a standard, textual form based on WKT.

Figure 5 The UML diagram of the Accommodation Dataset.

Gastronomy Dataset

The main class of this dataset is FoodEstablishment, described by geo:asWKT, description, name, telephone, and url.

A FoodEstablishment has

• a PostalAddress–consisting of streetAddress, postalCode, and AddressLocality–as address

• a GeoCoordinates–latitude, longitude, and elevation–as a geographical location geo

There are different (sub-)types of FoodEstablishment, all sharing the same attributes: Restaurant, FastFoodRestaurant, BarOrPub, Winery, and IceCreamShop.

geo:asWKT is a method used by opengis.net’s geosparql <http://www.geosparql.org/> to express geographic coordinates in a standard, textual form based on WKT.

Figure 6 The UML diagram of the Gastronomy Dataset.

Event Dataset

The main classe in this dataset is Event, described by a startDate, an endDate, and a description. Every Event has an organizer, either a Person or an Organization and a location.

A Person–identified by givenName, familyName, email, and telephone–worksFor an Organization, which has a name and an address, i.e., a PostalAddress consisting of streetAddress, postalCode, AddressLocality, and AddressCountry.

Finally, an Event has as location a MeetingRoom–identified by a name– which is containedInPlace a Place–which has also a name

Figure 7 The UML diagram of the Event Dataset.

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