Decide and finish SPC fire-weather Day 2 — geometry never fetched, text plumbing dead #63
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#63
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Only the Day 1 fire layer URL exists (app/services/spc.py:28) and
_parse_fire_featurehardcodes day=1 (:209-225), so no fire outlook can evermatch day 2 — yet
fetch_spc_fire_outlook_text(2)is called every poll(spc_processor.py:109-113, 722-729) into a dict that day-2 can never index.
Either add the Day 2 fire layer (+parse day=2, tests), or remove the Day 2
text fetches and document Day-1-only scope in README. Recommend adding it —
same rationale as the Day 1/2/3 convective fix.
Acceptance criteria:
Filed from the 2026-07-17 codebase audit (
docs/.internal/report-2026-07-17.md), finding F-24.Decision (SPC fire-weather Day 2)
Decision: ADD Day 2 rather than remove the dead text plumbing. Rationale matches the audit recommendation and the earlier Day 1/2/3 convective fix — the
fetch_spc_fire_outlook_text(2)call is already made every poll, so the intent was always Day-2 coverage; the gap is only the missing geometry layer + a hardcodedday=1in_parse_fire_feature. Adding the Day 2 fire layer URL, parsingday=2, and tests makes the existing per-poll fetch meaningful instead of dead. Implemented in v1.4.0 Phase 2.Picking this milestone up now (v1.4.0 — codebase health).
Done in #108 (merged). Added SPC fire-weather Day 2:
SPC_FIRE_LAYER_URLSnow maps day 1→MapServer layer 1 and day 2→layer 4 (verified against the SPC firewx service metadata),_parse_fire_feature(day, feature)takes the day (was hardcoded 1) withD{day}_FIRE_...product ids, andfetch_fire_outlooks()loops both layers with per-day freshness recording. Nospc_processor.pychange needed — it already threadsoutlook.dayand had both{1,2}fire-text slots, so the previously-dead Day-2 text fetch is now live. README updated to Day 1-2 fire coverage. Full suite 661 passed on the dev server. (Transition: the Day-1 fire dedup id changesFIRE_→D1_FIRE_, so a rare active CRIT/EXTR Day-1 fire outlook could re-notify once at deploy.)