fix(alpr): require explicit SharpV G3 before showing G3 specs

Address gekh's P2 review of ch-bas's ALPR datasheet feature. Keep the
vendored records verbatim, reject generation-ambiguous SharpV model tags,
and cover G1/G2/G3 matching and the rendered card with node:test.

Update the documented matched-camera count and changelog, preserving
original author ch-bas and existing attribution.
This commit is contained in:
Kevin Rajan authored and bassem chagra committed 2026-11-14 12:38:32 +01:00
1 parent 71d853dff0
commit 5371f3ee70
4 files changed
+43 -9

No files matched your search

+4 -3
View File
@@ -971,12 +971,13 @@ screen. Cyan camera badges use Manjunath's camera artwork; selection switches to
larger coral badge with corner brackets and an animated tactical card. Numeric
mapped bearings draw illustrative 90 m direction wedges (not measured coverage).
A camera whose OSM `model` tag names known hardware (Motorola Solutions Vigilant,
Genetec AutoVu SharpV, Axis, Verkada, Bosch MIC; 459 of the 1,567 tagged cameras
Genetec AutoVu, Axis, Verkada, Bosch MIC; 408 of the 1,567 tagged cameras
in October 2026) gets a `SPEC` line on its card from vendored datasheet records
(`src/layers/alpr/modelSpecs.js`, matched with the CCTV layer's
`createModelSpecLookup`). A `manufacturer` naming another maker rejects the
match, and the raw tag text is never shown. The hourly extract has no `model`
field yet, so only an Overpass-backed source fills it.
match, and the raw tag text is never shown. Unversioned `AutoVu SharpV` tags
cannot choose between G1/G2/G3 datasheets and show no specs. The hourly extract
has no `model` field yet, so only an Overpass-backed source fills it.
The shared overlay paints gradients for at most 64 nearby cameras, promoting the
selected camera; farther cameras keep native Cesium badges without wedges.
Native ground-clamped wedges (a ground polyline plus a classification polygon per