fix(local-adsb): hold an altitude no aircraft could have reached

A corrupt frame can still pass CRC, and one reached the globe as a DC-9 at
108,800 ft (#714). The browser decoder cannot produce that value: it decodes
only 25 ft (Q=1) altitudes, which stop at 50,175 ft. It came from a 1090
decoder feed, so the check sits in the layer's per-aircraft ingest, where the
browser SDR and the feeds already meet.

Each altitude must be reachable from the last accepted one at 1.5 x the
larger reported vertical rate + 2,000 ft/min (12,500 ft/min with none) over
the elapsed time + 1 s, plus 300 ft, which is the position speed check's
shape. A refused report holds the last accepted altitude on the record
itself, so the marker height, the card, the model ceiling and route
plausibility read the same value. Only a newer message is judged, because the
layer re-reads one record several times a second and a re-read must not count
toward the three-refusal re-anchor or let the refused value through. Surface
reports pass unjudged, since a feed's "ground" is 0 and not a barometric
reading. Refusals are counted as rejectedAltitudes in the layer stats.
This commit is contained in:
Pedro Lobato committed 2026-09-28 10:56:54 -05:00
1 parent 81eb44340d
commit 96d8000620
6 files changed
+314 -5

No files matched your search

+9
View File
@@ -1,5 +1,14 @@
# Changelog
- Local ADS-B no longer draws an aircraft at an altitude it cannot have
reached. A corrupt frame can still pass CRC, and one reached the globe as a
DC-9 at 108,800 ft. Each altitude report must now be reachable from the last
accepted one at a plausible vertical rate, whether it came from the browser
SDR or a decoder feed. A refused report keeps the previous altitude for the
marker, the card and the 3D model alike. Three refusals in a row start over
from the new value, and a surface report is never compared with the last
airborne altitude. The layer stats count refusals as `rejectedAltitudes` (Pedro Lobato, #714).
- CCTV cameras whose bearing is a guess now say so. Packs mark bearings derived
from a hash of the camera id as `headingConfidence: 'low'`, but nothing read the
flag, so roughly 70% of a default catalog rendered like surveyed facings. The HUD