Tours (beta)

A trip used to be something you flew. Tours let it be walked, driven and cycled: a trip carries route sections of its own — road, hike, bike and ferry — each a named, ordered chain of stops with the legs between them, the road-trip counterpart to a cruise itinerary. Tours are not a fifth domain; they are a property of a trip.

The model

A section has a name, a mode, and an ordered list of stops — a place, a hotel, a port, a point picked on the map. Between two consecutive stops lies a leg, and each leg has a source for its line: routed by the configured routing provider, drawn by hand, or adopted from a recorded track. A leg may override the section’s mode (the ferry crossing in the middle of a road trip). A trip’s route count travels with the trip list, so a row can read “6 entries · 3 sections” without one request per trip.

The section list

On the trip page the Tours tab lists the trip’s sections, their mode, their stops and their length. Sections are ordered; a trip that drives out, hikes, and drives back is three sections. Stops are assigned from what the trip already holds — its hotels, its places, its ports — or picked fresh on the map.

The editor

Each section opens in an editor at /trips/:id/route/:routeId — the same address the tab hides behind the switch, since it would otherwise be reachable by URL with the tab gone. The editor is worked with the mouse:

Click a leg to switch to it. (An earlier candidate swallowed the click and quietly added a waypoint to the leg already open, so reaching for one leg edited another.)
Drag waypoints; insert new ones on the guide line; remove them on hover. Undo and redo cover the whole gesture chain.
Right-click offers what fits under the cursor — edit that leg, delete this waypoint, delete the whole selection, simplify, close.
Select turns the drag into a selection box, so several waypoints go at once; the stops themselves are never among them. One undo takes a box-delete back whole.
Per-leg overrides — mode and source — sit on the leg, not the section.
Back to automatic returns a hand-drawn leg to the router.

The route map beside the editor draws the section, its stops and the rest of the trip for context.

Routing providers

A routed leg asks a routing service for the line between two stops. Which service is an instance setting under Settings → Routing provider — a self-hosted OSRM on your own network is the intended case, which is also why the page’s Content-Security-Policy keeps its connect-src broad. Without a provider a leg is a straight chord you can draw over by hand.

Recorded tracks from Dawarich

If you keep a location history in a Dawarich instance, a section can adopt the track you actually drove or walked. TravStats pulls the points for the section’s time window, truncates a track that runs past what one leg can hold, and stores the adopted line with the leg. TravStats only ever reads from Dawarich; nothing is written back. The connection carries a switch of its own beside the tours switch, because a connection with nothing to connect to is worse than no card at all.

On the map

The dashboard’s Tours tab draws every section as its own line, coloured by mode, with the globe available like everywhere else; the trip map draws the trip’s sections beside its flights, cruise paths and hotel pins. See Maps.

Limits

Beta. The list and the editor are feature-complete; the feature as a whole is awaiting the owner’s release decision and may change shape. Data you record now is kept.
A tour proves no country by itself. A road crossing reaches the passport only through location history — the transited rung reads Dawarich country-days, not tour sections. See Countries & passport.
No turn-by-turn, no elevation profile, no GPX export. A section is a line on a map with named stops.
No statistics of their own yet. Kilometres driven do not appear in the statistics page; the section length is shown on the trip.
Cruise legs do not pull tracks yet. The Dawarich connection has its own switch so that when they do, the card is already there.