Map: aircraft context — squawk and emitter category, rotorcraft icon, orbit detection, FAA TFRs #244

New Issue

2026-10-05T02:08:38-04:00

logan commented

2026-10-05 02:08:38 -04:00

Problem

telemetry.py:29 AircraftReport carries only icao/callsign/position/altitude/speed/track; no squawk or emitter category, so every aircraft draws the same and a low, slow, circling helicopter (the oldest 'something is happening' tell) is not distinguishable.

Who asked

TOC, RCC, GSOC, NEWS, HOBBY (5 of 8).

Proposal

node-26: send squawk + emitter category (readsb already decodes both); c2-core: accept/store them.
Rotorcraft icon; alert chip on squawk 7500/7600/7700.
Orbit detector over the existing 24 h trail: sustained heading sweep >= 360 deg within a small radius below ~3,000 ft → low-confidence signal linked to any incident within a few km.
FAA TFR polygons with effective times.

Data source and terms

Own-node ADS-B. FAA TFR list at tfr.faa.gov (public). FAA Releasable Aircraft Database (public domain) for type only.

Effort

M (cross-repo)

Acceptance criteria

A test trail circling at low altitude raises the orbit signal; a straight transit does not.
No registrant/owner names are displayed.

Notes

Standing-rule constraints: the FAA registry lists individual owners — never display registrant names (names policy). Do not label law-enforcement tails by agency. Avoid ADS-B Exchange / FlightAware APIs (commercial terms).

Reviewed against Server origin/main c4e1f9a (2026-10-05), from code only. Source: map persona panel 2026-10-05 (tracking issue lists all items).
Persona key: TOC = county PD real-time crime center supervisor; NOC = Con Ed electric ops NOC; RCC = MTA rail/bus control desk; GSOC = corporate security operations analyst; OEM = county emergency management duty officer; NEWS = TV newsroom assignment editor; FD = volunteer fire chief / county fire dispatcher; HOBBY = scanner power user / local journalist.

## Problem `telemetry.py:29` `AircraftReport` carries only icao/callsign/position/altitude/speed/track; no squawk or emitter category, so every aircraft draws the same and a low, slow, circling helicopter (the oldest 'something is happening' tell) is not distinguishable. ## Who asked TOC, RCC, GSOC, NEWS, HOBBY (5 of 8). ## Proposal - node-26: send squawk + emitter category (readsb already decodes both); c2-core: accept/store them. - Rotorcraft icon; alert chip on squawk 7500/7600/7700. - Orbit detector over the existing 24 h trail: sustained heading sweep >= 360 deg within a small radius below ~3,000 ft → low-confidence signal linked to any incident within a few km. - FAA TFR polygons with effective times. ## Data source and terms Own-node ADS-B. FAA TFR list at tfr.faa.gov (public). FAA Releasable Aircraft Database (public domain) for type only. ## Effort M (cross-repo) ## Acceptance criteria - A test trail circling at low altitude raises the orbit signal; a straight transit does not. - No registrant/owner names are displayed. ## Notes Standing-rule constraints: the FAA registry lists individual owners — never display registrant names (names policy). Do not label law-enforcement tails by agency. Avoid ADS-B Exchange / FlightAware APIs (commercial terms). --- Reviewed against Server origin/main c4e1f9a (2026-10-05), from code only. Source: map persona panel 2026-10-05 (tracking issue lists all items). Persona key: TOC = county PD real-time crime center supervisor; NOC = Con Ed electric ops NOC; RCC = MTA rail/bus control desk; GSOC = corporate security operations analyst; OEM = county emergency management duty officer; NEWS = TV newsroom assignment editor; FD = volunteer fire chief / county fire dispatcher; HOBBY = scanner power user / local journalist.

logan added the

labels 2026-10-05 02:08:38 -04:00

logan referenced this issue

2026-10-05 02:09:11 -04:00

Map roadmap — persona panel 2026-10-05 #247

logan referenced this issue

2026-10-05 02:22:58 -04:00