[Purple10101]

What

The Tracker page gains a second display. A Display control in the page header switches the panel between Delay / Doppler and a wedge view: a map of where the node is proven to see, built only from ADS-B-verified detections, with its tracks drawn on it. Labelled tracks are trails of their verified positions; unlabelled tracks are their delay arcs, solid inside the wedge and faint outside. Clicking a track in the rail replays its travel through the wedge over ten seconds.

Why

Delay and Doppler say nothing about which way the antenna looks or how far it reaches, and a declared beam is configuration, not measurement. The wedge is evidence: a slice appears only once two different aircraft have been detected in it, and it holds for a sliding 24 hours.

The wedge view

• Layers: the proven lobes; close-in slices drawn lighter with a dashed edge (mostly aircraft overhead, not the antenna's pattern); the processed range limit as a grey dashed ellipse, since a slice reaching it is capped by the node's delay setting; receiver, transmitter and baseline; trails and arcs.
• Footer: the legend and the evidence, for example "Last 24 h · 273 aircraft · 54 of 72 slices proven · 36 close-in · 7 at the processed range limit".
• Notices over the map explain an empty or missing wedge: not proven yet, just reset, receiver or transmitter moved, no location set, a tracker without the wedge (404/503), or unreachable (502).
• Replay: clicking a row also replays it in the wedge view; clicking again stops or replays. A labelled aircraft moves along its trail with its measured arc; an unlabelled arc sweeps with a fading afterglow. Other tracks dim.
• Reset wedge clears the wedge on the node behind a confirm dialog, separate from Clear buffer because it must not touch tracking.
• The map reuses the setup wizard's Leaflet and CARTO basemap and key handling, fits the lobes, then keeps the viewer's pan and zoom.
• The scope is not redrawn while hidden. Delay / Doppler gets no replay cursor, since Plotly would redraw the whole scene every frame.

How it is built

retina-tracker owns every shape (lobes, arcs, the range limit); the page only draws. Four routes proxy the sidecar's coverage endpoints and relay its status. Track ids are checked before they reach the upstream path. Track columns on the stream gain lat/lon, which only the wedge view reads; the scope ignores them. The new script is static/tracker-wedge.js.

Testing

• Full suite: 1059 passed; ruff clean; the dead-code gate is clean.
• Headless Chromium against a local tracker fed synthetic traffic: wedge, both replays, reset, reload into the wedge view, and phone width.
• Live on a test node for two days with real map tiles.
• Not verified: browsers other than Chromium, or a real phone.

Docs

docs/features/tracker.md gains a Wedge view section (with Replaying a track and Resetting the wedge) and the stream's lat/lon columns; docs/README.md maps static/tracker-wedge.js.

After this

• Needs the retina-tracker coverage wedge PR (Coverage wedge: where the node is proven to see, from ADS-B-verified detections retina-tracker#38) and a retina-node bump of its retina-tracker pin. Until a node runs that tracker, the wedge view says so and Delay / Doppler is unchanged.

🤖 Generated with Claude Code