Data states

• Always write the state in words next to the dot. Legends list all five states, in this order, even when one has no vehicles.
• color.data-state.no-signal means a vehicle has gone silent. Use it for that alone.
• No signal is the one state cut by a slash: a diagonal gap, vehicle-dot.no-signal.cut-width wide, from the top left of the dot to the bottom right, which shows the surface beneath. Live and no signal are both solid dots, so without the cut they would differ by colour alone, and they would look the same in forced colours, where Windows' contrast themes replace every colour. The cut takes ink away rather than adding it, so the map grows no busier, and it reads down to the smallest dot.
• On the map, draw dots on a canvas, with a halo of color.data-state.halo and, for light line colours on the light map, a hairline of color.data-state.outline.
• Aircraft carry these states too, all but timetable only, in a glyph of their own rather than a dot, with the same fill strength, grey and cut: see Map.

No signal keeps moving

A vehicle with no signal keeps moving. From where it was last seen, it follows its path on the timetable plus its last known delay, drawn in the no signal glyph and labelled with the time of its last report: "No signal since 10:42". Left where it was last seen, it would mislead twice: an outage across a feed would look as if the city had stopped, and a dot frozen for twenty minutes would sit far from anywhere the vehicle can be. The glyph, not the position, carries the doubt: the cut dot and its words say the place is a guess, so the dot never needs to stand still to say so.

Thresholds

The age of a vehicle's latest report decides between live, ageing and no signal, and how old is too old depends on how often the feed reports. So the thresholds are the app's. vehicle-dot.live-threshold (60 s) and vehicle-dot.ageing-threshold (5 min) are defaults that suit a feed reporting every few seconds; each app sets its live threshold from its own feed's interval between reports, so that one late report doesn't fade a vehicle that is still reporting, and keeps it under the ageing threshold. An app such as Mylder, whose feed reports once a minute at best, sets its live threshold to 2.5 times the interval between reports, 150 s at 60 s and at most 4 min, and keeps the ageing threshold at 5 min.

The components draw the state they are given and never work one out from a timestamp; the app compares each report's age with its thresholds. Where a screen explains the states, it gives the app's own figures, never the defaults' as fixed facts.

Geometry

The vehicle-dot tokens give the geometry of each shape at any size: insets, stroke widths, the dash, the no-signal cut, and the default age thresholds between live, ageing and no signal, which each app sets for its own feed (Thresholds).

Delays

A delay is known only for live, ageing and estimated vehicles. Timetable only and no signal always show an unknown delay ("—"). Delay colours point at the status text colours; color.transit.delay.unknown is the one that misses 4.5:1, kept for the "—" next to stronger text.

Kinds of disruption

Each kind of disruption has its colour, always with its icon and its name. A service notice is the neutral kind, for a message whose fields don't say which of the other four it is: it is shown as received, never guessed into one of them.