mirror of
https://github.com/zvx-echo6/central.git
synced 2026-06-10 11:54:37 +02:00
malice
1d5548c24cFirst official-state-DOT-API pattern landing. Two adapters in one PR: - itd_511 (event-class): polls Events (60s) + Advisories (300s) from https://511.idaho.gov/api/v2/get/{event,alerts}. Decodes EncodedPolyline to LineString via the polyline lib (bookend LineString or Point fallback); ITD Severity string mapped None->1 / Minor->2 / Major->3 with IsFullClosure=true forcing 3 regardless; RecurrenceSchedules / Restrictions / DetourPolyline pass through unmodified. Advisories ship as structural pass-through under data.advisory since the upstream /alerts endpoint currently returns []; per-record try/except keeps a surprise shape from sinking the cycle when ITD posts its first one. - itd_511_cameras (telemetry-class): polls Cameras (600s). One event per camera per UTC day; image URL passes straight through to <img src>. Region uniform US-ID with data.source_jurisdiction preserving the raw upstream Source field for the ~1.2% cross-DOT border-region mirrors (UDOT / ODOT / WYDOT / WSDOT / NDot / MTD / DriveBC / Lemhi County). Subject convention (v0.9.20 forward): central.traffic.<event_type>.us.id and central.traffic_cameras.us.id.<camera_id>. Castle Rock state_511_atis keeps its bare-state subject; consumers stay on central.traffic.> wildcards during the A/B comparison window. Retry predicate tightened from the Castle Rock / TomTom precedent: 5xx + connection / timeout retry; 4xx other than 429 skip-with-warn (don't burn quota on permanent errors); 429 honors Retry-After once then retries. API key (alias 'idaho_511') travels in the ?key= query string, so every error log path runs through self._redact() to scrub the URL. Both adapters ship disabled; operator enables via GUI after registering the API key with 'python -m set_api_key idaho_511'. Reuses existing CENTRAL_TRAFFIC and CENTRAL_TRAFFIC_CAMERAS streams -- no archive restart needed. Scope-cap exception: this PR is ~1.5k lines vs. the standard 500-line cap, authorized as a one-time exception for the first official-state-DOT-API pattern landing. Two adapters + their tests + real-API fixtures naturally exceed the v0.9.x adapter-cap budget. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
28 lines
1,003 B
SQL
28 lines
1,003 B
SQL
-- Migration: 031_add_itd_511_adapters
|
|
-- Adds the itd_511 (event-class) and itd_511_cameras (telemetry-class) adapters
|
|
-- onto the EXISTING CENTRAL_TRAFFIC and CENTRAL_TRAFFIC_CAMERAS streams. NO
|
|
-- new streams -> no central-archive restart needed
|
|
-- (feedback_new_stream_needs_archive_restart). Both ship disabled; operator
|
|
-- enables via GUI after registering the 'idaho_511' API key
|
|
-- (python -m set_api_key, alias 'idaho_511').
|
|
-- itd_511 polls 60s (events) + 300s (advisories sub-poll); ~1.3 calls/min
|
|
-- combined, well under ITD's documented 10/60s budget.
|
|
-- Additive-only: idempotent via ON CONFLICT DO NOTHING.
|
|
|
|
INSERT INTO config.adapters (name, enabled, cadence_s, settings)
|
|
VALUES (
|
|
'itd_511',
|
|
false,
|
|
60,
|
|
'{"api_key_alias": "idaho_511"}'::jsonb
|
|
)
|
|
ON CONFLICT (name) DO NOTHING;
|
|
|
|
INSERT INTO config.adapters (name, enabled, cadence_s, settings)
|
|
VALUES (
|
|
'itd_511_cameras',
|
|
false,
|
|
600,
|
|
'{"api_key_alias": "idaho_511"}'::jsonb
|
|
)
|
|
ON CONFLICT (name) DO NOTHING;
|