← All cases · Time back · in operation · since September 2026
Trips that grow on the map
24 stops without gaps from 11 Aug to 12 Sep 2026 in the data core — the map draws itself.
Figure: 24 Stationen lückenlos im Datenkern der Reise (11.08.–12.09.2026) · measured 7 September 2026
Request: „Add Cape Town as a stop with three nights.“
- Keep every stop as a row in a data core (CSV): place, nights, lodging, booking status.
- Recalculate drive times between stops whenever something changes.
- Generate an interactive map on the private network, readable on the road.
- Bookings flow back into the plan and the calendar together with their cancellation deadlines.
Trip planning in spreadsheets, e-mails and heads — and nobody knew whether the drive times still held.
Where, how long, and every booking.
A data core from which map, calendar and deadlines are generated replaces three spreadsheets that contradict each other — the pattern is “one source, many views”.
“Add Cape Town as a stop with three nights” — that is all the travel plan needs. Every stop is a row in a data core; from it the AI recalculates drive times and draws an interactive map I can see on my phone on the road. Bookings flow back into the plan and the calendar with their cancellation deadlines. For the South Africa trip, 24 stops sat in the data core without a gap. The tool is the one table behind it; the map is just one view of it.
Evidence in my own archive · as of 24 October 2026.