feat(timeline): multi-day historical fire progression timeline slider (Issue 17) #27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/issue-17-timeline-slider"
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?
Summary
Implements Issue 17: Multi-day historical fire progression timeline slider.
src/lib/services/sipongi-historical.ts: Parameterized query service for historical intervals (24h, 48h, 72h, 168h / 7 days) with in-memory caching and per-feature age decay computation (age_hours,age_tier).src/components/controls/timeline-slider.tsx: Interactive timeline scrubbing bar with preset buttons (24 Jam, 48 Jam, 72 Jam, 7 Hari), automated chronological playback with play/pause and 1x/2x speed controls, and live point count readouts.src/components/map/layers/hotspots-layer.tsx: Added GPU-accelerated age decay opacity interpolation (circle-opacityfading from 1.0 down to 0.35 over 72h) andsetHotspotsTimeFiltermethod for zero-re-download filtering.src/components/dashboard/dashboard-client.tsx: Wired timeline scrubbing and preset switching into MapView and HUD.sipongi-historical.test.ts: Vitest suite verifying age decay tiering and chronological filtering.Closes #17
Review for Issue 17
PR 27 implements the multi-day historical fire progression timeline slider.
Verdict is APPROVE.
The sipongi historical service caches intervals for 24h, 48h, 72h, and 7 days.
Age decay hours are computed per hotspot feature.
GPU accelerated age decay fades older fires from 1.0 down to 0.35 opacity.
The timeline slider controls include automated playback with play and pause.
Playback speed toggles between 1x and 2x.
Scrubbing updates the map layer filter client side with zero network requests.
The carto table and KPI ribbon dynamically update based on the temporal scrub limit.
All 42 unit tests pass across 6 test suites.
The vp check tool reports zero lint errors across 235 files.
Standalone production build succeeds.
All acceptance criteria are satisfied.
Merge decision is approved.