fix(cctv): harden the WSDOT catalog fetch and describe its real direction codes

The catalog fetch now refuses redirects, cancels rejected bodies and reads
through the shared capped reader before the windows-1252 decode. The feed sends
cardinal codes plus B (both), O and null, not BW or diagonals; tests, comments
and docs now say so, with unchanged id-hash fallbacks. Documents the 8-1,200
per-pack range, drops the unverified low-volume compliance claim for facts and
a link to WSDOT's terms, and stops claiming the per-pack defaults fit under
the 4,000 cap: it is filled round-robin.
This commit is contained in:
Sameh Khamis committed 2026-10-15 15:17:59 -07:00
1 parent 24f14a77a3
commit 76bfd74a78
7 files changed
+148 -29

No files matched your search

+6 -5
View File
@@ -3,11 +3,12 @@
- Add WSDOT highway cameras (Washington State) as a keyless CCTV source pack:
WSDOT's official Travel Center camera layer, with frames registered only on
WSDOT's own image host (partner-hosted cameras such as Oregon DOT and City of
Seattle are skipped). Cameras with a single `CompassDirection`, cardinal or
diagonal, get a high-confidence heading; `BW` (Bothways) cameras use the
shared id-hash fallback at low confidence. By default the 250 cameras nearest
Seattle and Spokane load; `CCTV_WSDOT_MAX_SOURCES` sets the cap and
`CCTV_WSDOT_ENABLED=0` turns the pack off (bassem chagra, #644).
Seattle are skipped). Cameras with a single cardinal `CompassDirection` get
a high-confidence heading; `B` (both directions), `O`, and unset directions
use the shared id-hash fallback at low confidence. By default the 250
cameras nearest Seattle and Spokane load; `CCTV_WSDOT_MAX_SOURCES` sets the
cap (8–1,200) and `CCTV_WSDOT_ENABLED=0` turns the pack off (bassem chagra,
#644).
- Stop one retired bikeshare feed from reporting the whole layer as failed.
City feeds are fetched independently, but failure was recorded in a single