Travel knowledge graphs

Connect your places, routes and partner knowledge.

A venue appears on a destination page, in a festival programme and along a cultural route. Your team needs to keep its shared information consistent while preserving the different conditions of each activity.

A travel knowledge graph gives places, events, routes, partners and sources connected records. It makes their relationships explicit, so the information can support different pages, languages and working processes.

Tamaga designs and builds these models in Drupal, starting with the information your organization already maintains.

Decide what belongs together and what needs its own context

A venue’s address can serve several activities. A workshop’s joining conditions belong to that particular session. A partner may organize one activity and contribute photographs to another.

The model needs to preserve those distinctions.

We identify the places, activities, organizations and sources involved, then define the relationships your work needs. Each relationship should have a clear meaning: an event takes place at a venue, a partner runs a session, or a source supports a particular statement.

For a destination, the Destination graph definition introduces the main kinds of information involved.

One festival, several connected records

Consider a fictional regional tourism organization publishing a guide to an annual craft festival. This year’s programme includes workshops at two venues, run by local partners.

Five connected festival records

Five connected festival records
Record Information it maintains
This year’s festival edition Its dates, programme and publishing responsibility.
Each workshop session Its time, joining conditions, venue and organizing partner.
Each venue Its location and supported access information.
Each partner Its identity, contribution and relevant public contact information.
Supporting sources Where particular information came from, when it was checked and what it establishes.

If a workshop time changes, the editor updates the session record and reviews the programme, activity page and translations that use it. The venue’s address remains a separate fact.

The model helps identify those connections. Corrections to a sent newsletter or a partner’s website still need their own follow-through.

For visitors, the relationships should support useful questions: which workshop takes place where, what applies to that session, and where to find the relevant visiting information.

Give each use the information it needs

The same underlying records can support a destination guide, an event programme and an itinerary. Each presentation needs an appropriate selection of information.

A festival overview helps someone choose an activity. A workshop page explains its arrangements. The venue page provides the access information needed before visiting.

Languages can describe the same place while retaining their own wording and editorial review. Private partner notes need appropriate access rather than automatic inclusion in public pages.

Where structured data is useful, the Schema.org work maps suitable public information to appropriate types and relationships, checked against the visible content and intended consumer.

What an implementation can include

An agreed scope can produce:

  • A documented content model: the records, relationships and distinctions your organization needs.
  • Representative working records: examples built from existing material, with sources and unresolved questions retained.
  • Editing and maintenance rules: who can change information, who reviews it and what should trigger another check.
  • Publishing examples: pages, language versions and appropriate structured representations using the model.
  • Migration and connection priorities: what can be retained, what needs reconciliation and where existing systems remain responsible.

Start with a representative set of material. Test whether an editor can distinguish shared facts from activity-specific conditions, follow a source and understand the consequences of a change.

Tamaga Hospitality

Another application: accommodation

A room type can describe a shared layout while individual physical rooms retain their own outlooks. Keeping those records distinct gives each fact an appropriate home.

A shared room-type outline above two rooms with matching layouts: one overlooks a lake, the other a leafy courtyard.
Illustrative example: one room type, two physical rooms with the same layout and different outlooks.
AI-generated illustration · Tamaga

Choose the next step for your situation

If you first need to decide which pages should answer which audience questions, Topical Mesh explains that editorial work.

When connected information also needs to support staff preparation, documents and handovers, Travel operations backends explains the wider operational scope.

Once public explanations are in place, AI Visibility Testing offers a way to observe how external AI answers represent them.

Start with the information you already use

Bring a guide, programme, itinerary or partner record that your team maintains in several places.

We can use it to identify the underlying records, their relationships, the sources supporting them and the people responsible for changes. That provides a practical basis for agreeing an implementation scope.