Maurice
7da0080557
* docs(wiki): correct the install and operations pages for 4.0.0 Quick Start passed docker an empty ENCRYPTION_KEY: an assignment prefix is not expanded on the same command line, so the server silently generated its own key instead of taking the one the page told you to set. The tag examples pinned to the 3.x line, the documented tmpfs size did not match the shipped compose file, and several .env values were described as reaching the container when compose never interpolates them. * docs(wiki): match the MCP reference to the registered surface The scope table was missing the whole Collections group and the totals said 27 scopes across 13 groups where the code registers 29 across 14. The Cloudflare link on the setup page pointed at an anchor on its own page instead of the heading on Troubleshooting. * docs(wiki): correct the plugin and admin pages Three links to Plugin-Development carried a .md suffix, which does not resolve on the wiki. The admin pages described tabs, permissions and storage behaviour that had moved on. * docs(wiki): bring the feature pages back in line with the app Costs still documented the old panel, where categories could be added, renamed, reordered and deleted; they are fixed now and the panel is a day-grouped ledger with settlements. Trip sharing, journeys, maps, packing, reservations and the account pages had all drifted in the same way. * docs(wiki): cover the pages the first pass did not reach The MCP catalog listed 168 of the 201 registered tools; the settlement tools and rate_place were missing here and the Collections family from the addon page. Several resource rows claimed a trips:* scope where the handler asks for trips:read. * docs(wiki): tighten the corrections a review picked apart The audit-log resource is the row id, not the credential id; an admin password reset does not bump password_version the way the page implied; and a few of the new paragraphs described behaviour more confidently than the code supports. * docs(wiki): fix what a last read-through caught Costs shows every figure in your display currency, not the trip's, and an expense with no payer still counts against the members it is split between. Studio's cutoff is a 1024px viewport rather than phones alone, and the Integrations tab is gated on the providers an admin has configured. * docs(wiki): the last few the review caught A passkey satisfies the MFA policy everywhere except the WebSocket handshake, which still asks for TOTP, so a passkey-only account under that policy gets no live updates. Mobile optimizes a day from two places, not three. The ctx.db row carried an unescaped pipe that split the table, and the Backups table linked with a wiki link whose pipe did the same.
7.1 KiB
Transport: Flights, Trains & Cars
Log flights, trains, car rentals, and cruises with departure and arrival endpoints, times, and transit-specific details.
Where to create
Open the Transports tab in the trip planner and click Add, or open the planner from a day view and use the transport shortcut. Transport records appear in the Reservations panel alongside other bookings.
Public transit search
The Add transport dialog has two modes: Manual transport (the classic form) and Automated transport — a public-transit route search powered by Transitous, free open data with no API key or paid provider. The transit button (tram icon) on each day header opens the dialog straight in the Automated mode. (The rename pencil this button replaced moved next to the day name in the day detail panel.)
You can also start the search from a single leg: click the travel-time connector between two stops in the day plan and pick Public transit from the menu. The search opens with that leg's start and end already filled in and the departure time taken from the stop you are leaving.
The mode switch only appears when the trip has a start date and an end date — a transit search needs real dates to depart against. On a trip without dates the dialog opens directly on the manual form; add dates in the trip settings to get the Automated mode back.
- Pick from and to (stop/station search; the day's own places and hotels appear as quick picks), a depart/arrive time, and filter by mode: train, subway, tram, bus, ferry, cable car.
- Rank the results by best route, fewer transfers, or less walking.
- Each result shows local departure/arrival times, duration, transfers, walking time and the line badges in their official colors; expand it for the stop-by-stop breakdown.
- Add to day saves the chosen connection as a first-class transit entry. It slots into the day timeline at its departure time and shows its line badges, transfers and walking time right in the plan. Clicking it opens the journey view: the full stop-by-stop itinerary together with the editable booking fields (title, status, confirmation code, notes), a Change route action that re-runs the search and replaces the itinerary, and delete. In the Transports tab these journeys appear in their own Automated public transit section.
Self-hosters can point the TRANSIT_API_URL environment variable at their own MOTIS instance.
Transport types
Nine types are available: Flight, Train, Bus, Car, Taxi, Bicycle, Cruise, Ferry, and Other.
Common fields
All transport types share these fields:
| Field | Notes |
|---|---|
| Title | Required |
| Departure day | Linked to a trip day |
| Departure time | Optional |
| Arrival day | Linked to a trip day (can differ from departure day) |
| Arrival time | Optional |
| Booking / confirmation code | Optional |
| Status | Pending or Confirmed |
| Notes | Optional free text |
Endpoints
Flights
The departure and arrival fields use the Airport picker — type a city name or IATA code (minimum two characters) to search. Results show the IATA code, airport name, city, and country.
Once you select an airport, the timezone for that airport appears next to the time field. This lets you enter local departure and arrival times without confusion across time zones.
Trains, cars, and cruises
Departure and arrival fields use the generic location picker — search by place name or enter a free-text location. Results come from the maps search service.
For the Car type the date fields are relabelled to match a rental: the departure side reads Pickup and Pickup time, the arrival side Return and Return time. There is no separate car-rental type — a rental and your own car are both logged as Car.
Flight-specific fields
When the type is set to Flight, two additional fields appear:
- Airline — carrier name (e.g. Lufthansa)
- Flight number — (e.g. LH 123)
Train-specific fields (multi-leg route)
A long-distance rail trip is often several trains on one ticket, so trains use a multi-leg route editor (the same one flights use), not a single flat field block. You build an ordered chain of stations:
- Search each station with the location picker; use Add stop to insert intermediate stations between the start and end.
- Each leg (the segment between two consecutive stations) has its own train number, platform, seat, and its own departure/arrival day and time.
- N stations make N − 1 legs. A simple two-station train is just one leg — enter its train number/platform/seat there.
Trains created before this feature keep working: their existing train number/platform/seat are read as a single leg.
On the map
Transport records with both endpoints set appear as lines on the trip map:
- Flights, cruises and ferries render as geodesic great-circle curves that follow the curvature of the Earth.
- Cars, buses, taxis and bicycles follow real roads, routed on demand via a public OSRM router (driving for car/bus/taxi, cycling for bicycle). A straight line shows while the route loads, and is kept if routing fails or the trip is over ~2000 km.
- Trains render as a straight polyline; a multi-leg train draws its full station chain (from → stop → to).
Confirmed bookings are drawn as solid lines; pending bookings use a dashed line. Each endpoint gets a pill-shaped marker with the transport icon. Turn on Booking route labels (Settings → General → Travel & map) to print the airport code or station name in the pill as well; the label appears once the two endpoints are far enough apart on screen.
See Map-Features for details on how these overlays work.
In the day plan
When a transport is assigned to a day, it appears inline in the day timeline between places. Multi-day transports show phase labels depending on the type:
| Type | Start day | Middle days | End day |
|---|---|---|---|
| Flight | Departure | In transit | Arrival |
| Car / Car rental | Pickup | Active | Return |
| Train / Cruise | Start | Ongoing | End |
A multi-leg train (and a multi-leg flight) instead shows one row per leg, each slotting into its own day at its own time and independently reorderable, rather than a single spanning row.
See Day-Plans-and-Notes for details.
Faster: import the confirmation — If you have a booking confirmation email or PDF, you can skip the form entirely. See Import from booking confirmation in the Reservations guide.
See also: Reservations-and-Bookings · Accommodations · Map-Features · Day-Plans-and-Notes