AlpineBits DestinationData

This standard concerns the exchange of data of interest for tourist destinations such as events and ski areas. The standard is released under the CC-BY-SA licence.

Since 2018, the Alliance has developed 3 releases of the DestinationData standard, the latest of which is called “AlpineBits DestinationData 2022-04“.

In the current version of the standard, the scope includes the exchange of data on events, series of events, event locations, mountain areas, ski lifts, trails, snow parks.

AlpineBits DestinationData specifies a REST API for exchanging destination data based on the AlpineBits DestinationData ontology. The API is built on JSON: API v1.0 designed to support the client-server communication model, with particular attention to system-to-system communication.

AlpineBits DestinationData is built on:

  • an OntoUML ontology that describes the conceptualisation and purpose of the standard;
  • RESTful architectural style;
  • the JSON specification: API v1.0 for REST APIs which exchange JSON data through HTTP messages;
  • HTTPS and basic authentication protocols for secure communication;
  • JSON Schema standard – draft 7 for the validation of messages in the AlpineBits DestinationData standard;
  • GeoJSON standard for modelling geospatial data;
  • structured data scheme.


A readily accessible open source Reference Implementation of this standard is also available, seamlessly linked to the Open Data Hub – the open data platform established at NOI Techpark in Bolzano.

Alpinebits DestinationData latest release

AlpineBits DestinationData 2022-04 is the current release of the standard. Download the source files for the AlpineBits DestinationData Standard.

It contains a zip file with the AlpineBits documentation, XML sample files, relax-ng schema files and XSD
schema files.

Older versions of the standard are also available
Additional Resources

For every route type defined in the standard, there is a JSON Schema that describes the structure of the messages it should return. Schemas can be used to programmatically validate messages against.

→ If you are implementing a DestinationData server, you can use these schemas to check if your implementation is compliant with the standard. You can also use them at run-time to check if your server is sending correctly structured messages.

→ If you are consuming data from a DestinationData server, you can use these schemas to validate the data you receive, which adds a layer of protection to your application.

Get involved

Explore our Git repositories, which house code and tools related to AlpineBits’ open specification. Follow the progress of the latest standard releases on our Git repository, with open discussions available for public review. However, only members of the AlpineBits Alliance are allowed to participate in the discussion.