feat(fullstack): v1.2.1 geo-zoning, per-zone seismograph and GNSS readiness - #367
Merged
Conversation
- geohash Redis zone index (geo.py) with PostGIS source of truth
- Redis Streams ingestion substrate (ingest.py) + TimescaleDB migration (timescale.py)
- GNSS-ready data model: Sensor.last_fix_at, Reading.lat/lon
- per-area cooldown fragmentation in worker
- DELETE /zones/{id}/readings and GET /zones/{id}/alerts endpoints
- zone/geo/timescale integration and unit tests
- live per-zone seismograph feed (useZoneReadings) with horizontal zone strip - sliding window chart anchored to wall clock + linear MAG scale - GPS zone detection (expo-location -> /zones/locate) - MIC/RESEARCH theme toggle + civil-defense siren on critical alerts - Settings Explore section + v1.2.1 footer
- optional GnssModule with UART fix + NVS last-known location (GNSS_ENABLED) - provisioning sends real fix when available, else last-known / omits - updated config example and platformio deps
- run test_geo_integration.py against real PostGIS + Redis - run test_timescale_integration.py against real hypertable - run test_zone_readings.py against fresh PostGIS (new per-zone job)
- CITATION.cff to v1.2.1, date 2026-08-14 - CHANGELOG v1.2.1 (geo-zoning, zone endpoints, live chart overhaul) - README roadmap: v1.2.1 current - backend README: locate + zone readings/alerts endpoints - ROADMAP: v2.0.0 KiCad/PCB design done, fabrication pending
- use cryptographically strong SystemRandom in zone simulator (S2245) - wrap JSX text separator in braces to avoid comment parsing (S6438)
- only swallow the expected BUSYGROUP redis error in ingest group creation - declare explicit non-root USER in the timescale postgres image (S6471)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v1.2.1 — Geo-Zoning & Cooldown Fragmentation (GNSS-ready)
Backend
geo.py) with PostGIS as source of truth; pure-Python geohash encoder matchingST_GeoHashingest.py) + idempotent TimescaleDB migration (timescale.py)Sensor.last_fix_at,Reading.lat/lonDELETE /zones/{zone_id}/readingsandGET /zones/{zone_id}/alertsendpointsFrontend
/zones/locate)Firmware
GNSS_ENABLEDcompile flagCI / Docs
Closes the v1.2.1 release.