Same defect/fix as v0.14.3, applied to the sibling wfigs_perimeters adapter.
The dedup key was the bare attr_IrwinID, so a perimeter published once on first
observation and every later geometry refinement was silently deduped at the
supervisor's published_ids gate. Latent until perimeters actually refine.
Fix (one line, wfigs_perimeters.py:292):
id = f"{irwin_id}:{props.get('attr_ModifiedOnDateTime_dt')}". Each genuine
upstream refinement mints a new id and republishes; identical re-polls (same
modified time) still dedup. attr_ModifiedOnDateTime_dt is already read (it's
already mapped into event.data) -- no new field, no new event type, no subject
change, no migration. Note the prefixed field name (attr_*), unlike incidents.
Tests (extend tests/test_wfigs.py, new TestWFIGSPerimetersUpdatePropagation,
mirrors the v0.14.3 incidents matrix via a parallel _perimeter_response helper):
- unchanged perimeter dedups across polls (regression guard)
- modified perimeter republishes with a distinct id (the load-bearing proof)
- subject_for unchanged -> central.fire.perimeter.<state>.<county>
- None attr_ModifiedOnDateTime_dt -> deterministic ':None', no crash (no
monkeypatch needed: perimeters has no recency filter)
Updated the v0.14.3 scope-canary assertion (test_wfigs.py:688) for the new key
shape -- scope is perimeters this time.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Dedup key for wfigs_incidents was bare IrwinID, silencing every acreage/containment update after first publish. Fix: id = f"{irwin_id}:{ModifiedOnDateTime_dt}" so modifications republish; identical re-polls still dedup. No new field/event-type/subject/migration. wfigs_perimeters deferred (same pattern, v0.14.4 follow-up).
Mechanical lint fixes only — ruff 31 -> 0 across the two files.
- E402 module-import-not-at-top: 15 -> 0 (relocated module-level
`logger = logging.getLogger(...)` from mid-import to below the import
block in routes.py; imports now contiguous at top of file)
- F811 redefined-while-unused: 10 -> 0 (removed 10 redundant function-local
`from central.gui.csrf import reuse_or_generate_pre_auth_csrf` re-imports;
the module-level import at line 26 is now load-bearing)
- F401 unused-import: 4 -> 0 (routes.py: fastapi.Depends, and
central.gui.csrf.reuse_or_generate_pre_auth_csrf resolved by the F811 fix;
test_wfigs.py: sqlite3, central.config_models.RegionConfig)
- E702 multiple-statements-on-one-line-semicolon: 2 -> 0 (split the two
semicolon-joined statements in _fused_bbox, indentation preserved)
Deliberate function-local wizard imports (circular-import workaround) left
untouched. pytest: 890 passed / 1 skipped, unchanged across 3 runs.
no behavior change; ruff mechanical fixes only.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Plumb the upstream GeoJSON Polygon/MultiPolygon into Geo.geometry so the
archive renders the real fire-perimeter shape (ST_GeomFromGeoJSON) instead
of the bbox 4-corner fallback. Adapter-local change; the v0.9.3 Geo.geometry
framework already carries it end-to-end. Graceful null + dict-or-string
coercion via _as_geometry; fall-off removal events stay NULL.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
WFIGS returns ISO 3166-2 state codes (US-MT) and 2-letter incident
type codes (WF, RX). Normalize at parse boundary:
- normalize_state: strips US- prefix (US-MT -> MT)
- normalize_incident_type: maps codes to names (WF -> wildfire)
Fixes:
- category was fire.incident.wf, now fire.incident.wildfire
- region was US-US-MT-GLACIER, now US-MT-GLACIER
Both raw and normalized values stored in event.data.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Two new adapters for wildfire data from NIFC WFIGS:
- wfigs_incidents: Active fire incident locations
- wfigs_perimeters: Active fire perimeter polygons
Features:
- IRWIN GUID dedup via is_published/mark_published
- Fall-off detection with removal events when fires exit current
- Bbox post-filtering with shapely polygon intersection
- Severity mapping from DailyAcres (0-4 scale)
- Subject hierarchy: central.fire.<layer>.<state>.<county>
Ships disabled by default; operators enable via GUI.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
