> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/artists/transport.md).

# Transport

Every movement of people this edition drives, books or tracks: one ride per movement.

**Type**: *transfer (own driver)*, *taxi*, *shuttle*, *flight*, *train*, *own vehicle*, *boat* or *helicopter*. The type is chosen first and fixed; a miskeyed ride is deleted and recreated.

**Time**: a flight or train is asked for its **departure** (it runs on a timetable); every other type, boats and helicopters included, is asked for a pickup time on an event day.

**Status**: each type walks its own ladder. Road types go from *to book* through *en route*, *picked up* and *delivered*; flights, trains, boats and helicopters use the booked/confirmed/arrived ladder; an own-vehicle ride starts *planned* (nobody books an artist who drives themselves).

**Passenger and route**: a performance of this edition or a typed name; each end of the route is the venue, an accommodation, an entry from the **address book**, or free text.

**Drivers and vehicles**: your own fleet, assignable on the types your team drives. A taxi names the supplier it was booked with instead.

The rides list opens on **today** during the event, there is a calendar view, and each ride has a PDF. Flights can be flagged per artist with *needs flight* from the artist type.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eventication.com/event/artists/transport.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
