Tourism.one Data: your travel data in one place

Benefits

• One source of truth

  Infopoints, websites and AI assistants use the same reconciled dataset instead of many separate synchronisations.

• Existing systems and open data in one place

  Partner systems such as Feratel, Outdooractive or Contwise can be connected through connectors; open sources such as OpenStreetMap, Wikidata or the Open Data Hub can be used directly.

• Origin and licence for every field

  For every field you can see which source it comes from and under which licence it is published.

• Clear separation of data

  Every source is classed as “read-only”, “read and write” or “own data”. Third-party data is never changed.

• Maintain your own data directly

  You create and edit a region’s events and infrastructure yourself. Corrections to third-party data are kept as a separate record with priority; the source stays unchanged.

• Multilingual

  The website and the data model are multilingual from the start: German, Polish and English.

• Open core

  The core is licensed under Apache-2.0 (open-source publication in preparation) and builds its data model on Schema.org.

• Multi-tenant, one area per region

  Every region or customer gets its own area with its own sources, its own data and its own access.

• AI assistants via MCP

  AI assistants access the data through the Model Context Protocol (mcp.tourism.one). Without a key: read-only and open data only.

• Hosted in the EU, no tracking

  The service runs on Microsoft Azure in the West Europe region. There are no tracking services and no cookies other than technically necessary ones.

Three data classes

Every source belongs to exactly one class. The class decides what the hub may do with the data.

• Read-only

  read-only

  Third-party source. The hub reads and caches the data where the licence permits and never writes back.

  Examples: OpenStreetMap, Wikidata, Open Data Hub, Outdooractive, Contwise, Guidle

• Read and write

  read-write

  The source allows write-back through its own interface. Writing happens only through the connector and only after approval for each tenant; it is switched off today.

  Examples: Feratel, later a customer’s CMS

• Own data

  own

  Data held in the hub itself (Schema.org model). The tenant creates, changes and deletes it and chooses the licence.

  Examples: Events, infrastructure, corrections made by a region

Open and fair

The core is licensed under Apache-2.0; its publication as open source is in preparation. Origin and licence are visible for every item of information. Third-party sources are stored and passed on only within their licence; the public interface returns only data from openly licensed sources.

Licence and usage notes