Skip to content

Forecast confidence tiering, time normalization, dep updates - #4

Merged
chriselsen merged 2 commits into
mainfrom
feat/forecast-confidence-and-deps
Aug 2, 2026
Merged

chriselsen merged 2 commits into
mainfrom
feat/forecast-confidence-and-deps

Conversation

@chriselsen

Copy link
Copy Markdown
Contributor

Summary

Reduces false-urgency ("crying wolf") risk in flood alerting and normalizes
timestamp display, plus routine dependency maintenance.

Forecast confidence tiering

  • Add lead-time tiers (Warning: 0-2d, Watch: 3-5d, Outlook: 6+d) reflecting
    Google's documented decrease in forecast skill at longer horizons
  • Confirm elevated severity by checking agreement across multiple daily
    forecast issuances (Google reissues forecasts daily) rather than persisting
    our own severity history — avoids relying on ETL ephemeral state, which
    isn't designed for growing time-series data
  • Mark unconfirmed/preliminary severity distinctly in callsign, remarks, and
    polygon fill opacity, so a single volatile long-lead-time spike doesn't read
    as equally certain as a confirmed same-day forecast
  • Render lower-confidence (non-qualityVerified) gauges with reduced
    marker-opacity to visually distinguish them on the map
  • Cross-reference gauges already covered by a Significant Flood Event in
    remarks/callsign, per Google's own event-based alerting guidance
  • Surface forecastChange.valueChange (predicted change bounds) in remarks
    when available, showing a range instead of a single point value

Date/time normalization

  • Standardize all surfaced timestamps per the TAK.NZ convention: metadata
    now exposes separate *UTC (raw ISO 8601, unmodified) and *Local
    (DD/MM/YYYY, HH:mm NZST/NZDT (<relative>)) fields
  • NZ local time computed via Intl.DateTimeFormat with
    timeZone: 'Pacific/Auckland' so NZST/NZDT transitions are handled
    automatically
  • Relative time uses floor-based tiering (minutes/hours/days) with correct
    singular/plural

Dependency updates

  • @sinclair/typebox 0.34.49 → 0.34.52
  • @tak-ps/etl 10.8.0 → 10.9.0
  • eslint 10.6.0 → 10.8.0
  • typescript-eslint 8.62.1 → 8.65.0
  • Resolved a high-severity transitive brace-expansion DoS advisory via
    npm audit fix
  • typescript stays pinned at 6.0.3 (latest 6.x): typescript-eslint's peer
    range still caps at <6.1.0, so TypeScript 7.x isn't yet installable
    alongside it without breaking lint/type-checking

Testing

  • npx tsc --noEmit — passes
  • npm run lint — passes
  • npm run build — passes
  • npm audit — 0 vulnerabilities
  • Manually verified date/time formatting output (UTC/NZ/relative-time
    boundaries) against the standard via a standalone script

Not verified: end-to-end run against the live Google Flood Forecasting API
(requires API_KEY/ETL_* credentials), so forecast-confirmation logic and
CoT payload output haven't been validated against real API responses.

Blocked / follow-ups

  • None blocking. Revisit pinning typescript to 7.x once typescript-eslint
    adds support.

- Add lead-time tiers (Warning/Watch/Outlook) reflecting decreasing
  forecast skill at longer horizons
- Confirm elevated severity via agreement across multiple daily
  forecast issuances (Google reissues forecasts daily) instead of
  persisting our own history in ephemeral state
- Mark unconfirmed/preliminary severity distinctly in callsign,
  remarks, and polygon fill opacity
- Render lower-confidence (non-qualityVerified) gauges with reduced
  marker-opacity to visually distinguish them on the map
- Cross-reference gauges covered by a Significant Flood Event in
  remarks/callsign, per Google's event-based alerting guidance
- Surface forecastChange.valueChange (predicted change bounds) in
  remarks when available
- Normalize all surfaced timestamps to the TAK.NZ date/time standard:
  metadata now exposes separate *UTC (raw ISO 8601) and *Local
  (DD/MM/YYYY, HH:mm NZST/NZDT + relative time) fields, computed via
  Intl.DateTimeFormat with Pacific/Auckland to handle DST correctly
- @sinclair/typebox 0.34.49 -> 0.34.52
- @tak-ps/etl 10.8.0 -> 10.9.0
- eslint 10.6.0 -> 10.8.0
- typescript-eslint 8.62.1 -> 8.65.0
- resolve transitive brace-expansion high-severity advisory via
  npm audit fix

typescript stays pinned at 6.0.3 (latest 6.x): typescript-eslint's
peer dependency still caps at <6.1.0, so TypeScript 7.x is not yet
installable alongside it without breaking lint/type-checking.

Verified: npm run build, npm run lint, tsc --noEmit, npm audit (0
vulnerabilities) all pass.
@chriselsen
chriselsen merged commit 118fd94 into main Aug 2, 2026
1 check passed
@chriselsen
chriselsen deleted the feat/forecast-confidence-and-deps branch August 2, 2026 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant