Victoria's Code STA / 01
GCS — build log

One Map, Eleven Radars: A Whole-Fleet Glance

A map answers where everything is. It's bad at telling you which asset is about to have a problem. So I built the what-view: eleven assets, every critical number, one screen — a grid of identical status cards where trouble literally glows.

Up to now my console had a map with markers on it. Useful, but a map is a where tool. An operator flying eleven assets across four domains also needs a what tool — altitude, heading, battery, link health, mode — for everything at once, without clicking through eleven panels. I kept catching myself opening panels one by one to answer a question the screen should have already answered.

Iisang tingin, buong fleet (one glance, the whole fleet).

The problem with a map-only view

A map answers "where is everything." It's bad at "which asset is about to have a problem." Battery, link quality, and mode aren't spatial — cramming them onto map pins makes the map noisy and still buries the one number that matters. An operator scanning for trouble shouldn't have to read eleven popups. I tried it. It's exhausting.

Small multiples beat one busy dashboard

What I landed on is a grid of compact status cards — one per asset — each showing the same handful of vital signs in the same layout. Because every card is identical in structure, your eye learns the shape once and then scans for the outlier: the red battery, the dropped link, the asset in a mode it shouldn't be in.

Consistency is what makes a fleet legible. Eleven identical cards let you spot the one that's wrong in about a second. Eleven bespoke panels would take a minute — and I know, because that's what I had.

Color is a status, not decoration

Each vital sign has thresholds, and the color follows the value: nominal is quiet, caution is amber, critical is red. The operator isn't really reading numbers, they're scanning for warmth. A healthy fleet is a calm grid. Trouble glows.

The cards render from each asset's declared capabilities, same principle as the command palette. A subsurface vehicle shows depth; an air asset shows altitude. Same card component, different vital signs, no per-domain branching. That decision keeps paying me back every time I add a vehicle type.

The map didn't go away

This is a second lens, not a replacement. Where-view and what-view answer different questions, and the operator flips between them. Selecting an asset in one highlights it in the other, so the two stay in sync. The map for spatial reasoning, the grid for triage.

A lesson I keep re-learning on this project: the value isn't the data, it's making the data legible. Same telemetry either way — but a grid of small multiples turns eleven data firehoses into one scannable picture.
Build log entry. Apache-2.0. Part of the multi-domain GCS build log.
Comments

Thoughts?

Comments are threads on GitHub, so a GitHub account is needed to post. No account? Email me instead — I read everything.