Skip to content

Maps & visualisations

The dashboard’s main view is a map. The available modes are scoped to the tab you’re in — Flights, Cruises, Lodging and the combined All view each offer the modes that make sense for them. Switch modes from the Mode dropdown in the toolbar. The last mode is remembered per domain and encoded in the URL, so you can bookmark or share a view.

The map’s camera is remembered for the session: zoom into Berlin on the Flights tab and you are still over Berlin on the Cruises tab, and after every save. It is deliberately not persisted across a reload. The flat map and the globe keep separate cameras, since their zoom scales differ.

TabModesBest for
FlightsRoutes · Heatmap · Airport frequency · Trips · GlobeYour flight network, flat or on a sphere
CruisesSea routes · Itinerary · Port frequency · GlobeShip voyages, each in its own colour
LodgingPins · GlobeOne pin per house, sized and coloured by your choice
Places (beta)Dots · GlobeRecorded places, coloured by list
Tours (beta)Sections · GlobeRoad, hike, bike and ferry sections of a trip
AllOverview · Heatmap · Journey · GlobeEverything on one map, coloured by domain and status

Beside the map, every tab shows the same activity list. Picking an entry focuses it on the map rather than navigating away from the dashboard — a hotel used to throw you off the dashboard entirely. The next upcoming entry sits beside the tabs, follows the active tab, and names its trip.

Curved great-circle arcs between every flown airport pair, on a 2D MapLibre vector basemap. Pan, zoom, hover for tooltips, click an arc or airport to drill into the underlying flights. Arc colour is a colour mode you choose in the map settings — by frequency (a grey → amber → orange → red ramp so commuter routes stand out), by status, and others. A route is the pair, not the direction: FRA–MUC and MUC–FRA are one arc. Arcs start at the catalogue’s airport coordinates, so an arc never visibly misses its own airport dot.

Each airport becomes a soft blob of heat scaled by how many times you’ve been there — a quick read on where you cluster without the connecting lines.

One marker per airport, sized and coloured by visit count — the fastest answer to “what’s my home base?”.

The same flights drawn as moving paths along a timeline. A time slider lets you scrub through your travel history, each leg fading out after its trip time.

Every flight as a great-circle arc on a 3D globe — the MapLibre native globe projection with deck.gl arc layers, so the far side of the sphere is correctly hidden. Auto-rotation is opt-in and respects prefers-reduced-motion; drag to spin, scroll to zoom, click a marker or route for details.

  • Sea routes — each voyage drawn as a smoothed sea route through its ports, in its own distinct colour, with a direction arrow. A leg you have corrected by hand is drawn as you left it.
  • Itinerary — numbered port-of-call markers in visiting order.
  • Port frequency — markers sized by how often you’ve called at each port.
  • Globe — the same routes on the sphere.

The Lodging tab draws one pin per house. A stay is a place, not a route, so nothing connects the pins. Pins take a colour mode like flights and cruises, and a size slider in the map settings. A house without coordinates is listed beside the map, marked as unlocated, and its detail page offers to search a location right there. On the trip map the same pins carry the number of this trip’s nights.

On an instance with the beta switch on, recorded places are drawn as the same plain dot every other domain uses. The dot carries its list’s colour and tells a visited place from one on the wishlist by being filled rather than hollow. A list can wear a symbol instead of spelling its name on every pin; a switch on the map decides between “as each list says”, always names, and always symbols. Places have a size slider like every other domain, and their labels thin out with zoom. The ”+” menu on the map offers Add place, which opens the form and stays on the map after a save so you see the pin.

Tour sections — the driven, walked, cycled or ferried parts of a trip — get their own tab and their own line on the map, coloured by mode. The editor for a section is on the trip page; see Tours.

The All tab overlays every enabled domain on one map. Here colours come from the domain and the status, so past and upcoming read at a glance; place pins resolve their list’s colour and symbol through the same step the Places tab uses, so a pin cannot show one list’s colour and another’s symbol.

A key in the corner names every mark it draws — one row per domain (plural throughout), a circle for lodgings, and swatches of their own for airports and ports. It never covers the map attribution: CARTO and OpenStreetMap both require the credit to stay visible, so that is a licence matter rather than a tidiness one.

Airport dots, route arcs, ports, lodging pins and place dots all open something on click, and the pointer says so. A flight popup card stays on the tab it belongs to; switching domains closes it.

Every address input — lodgings, trip stops, custom ports, special-flight venues — opens one large map modal: search, click, or drag the pin, and the resolved address underneath is filled into the form on apply. Dropping a pin also answers “what is here?”: it lists the named places around the pin — the hotel, the snack bar, the station. Tapping one snaps the pin there and carries that place’s details into the form; confirming without picking keeps the plain reverse-geocoded address. Address and place lookups run in parallel, so one failing never takes the other down, and the addresses come back in Latin script.

A filter panel folds out from the left. The same filters apply to every mode: time period (year and/or month, multi-year), route frequency (routes flown ≥ N times), airlines, status (flown, scheduled, cancelled, historical). Filters are URL-shareable.

Flight and cruise colouring are explicit modes with their own setting; the legend resolves its swatches through the same setting, so a mode switch never changes what a colour means, and a view never decides the mode implicitly. On a beta instance a user may override the domain hues themselves.

  • Thousands of flights render smoothly on a modern laptop in any mode (deck.gl is GPU-accelerated).
  • Mobile WebGL handles Routes, Heatmap and the Globe; very dense data may stutter on low-end devices.
  • Only Trips (and the Journey mode) animate — the other modes show everything at once.
  • Airports are plotted individually; dense hubs can overlap visually at low zoom.
  • The camera is remembered for the session only. Whether it should survive a reload is a product decision not yet taken.