Timeline (when things happened)
Chart
Each row drawn as a bar from its start to its end, one lane per row — a Gantt chart.
When to use
Section titled “When to use”Seeing when things happened and how they overlap — bookings, shifts, a vehicle’s stops in a day.
When not to use
Section titled “When not to use”You want a count or a total; this shows each row, not an aggregate.
What the table needs
Section titled “What the table needs”Two date/time columns, a start and an end, and a column that names each row.
Asking the AI
Section titled “Asking the AI”Describe it in a sentence — for example “when each truck was at the yard this week”.
From another AI
Section titled “From another AI”An assistant connected to Routario over MCP (Claude, ChatGPT) makes it with chart_create, then puts it on a board with dashboard_tile_add.
Settings
Section titled “Settings”- Subtitle — One line under the title. What the reader should take from it.
- Along the bottom — The column whose values become the slots along the bottom — a date for a trend, a category for a comparison.
- Series — Each series is one measure, optionally narrowed to the rows that match a condition.
- Measure — What each series computes over the rows in a slot.
- Unit — For ‘time between two dates’: the unit the gap is measured in.
- Aggregate — For ‘time between two dates’: how several rows’ gaps become one number.
- Where — Narrows one series to the rows matching a condition — how several series share one axis.
- Colour — A plain colour picks a pigment and says nothing about the data. A named meaning — went well, needs attention, went wrong — tells the reader something they will believe.
- Show numbers as — How the value axis, the tooltips and the printed values spell a number.
- Legend — Where the series names sit, if anywhere.
Auto-generated from the tile registry (core/custom_tables/tile_registry.py) — the same text the chart editor and the AI drafter read. Do not edit by hand.