PLATFORM · FEATURES · METHODOLOGY
Terraguard combines near-real-time earthquake and wildfire monitoring, map-based exposure checks, evidence-grounded event intelligence, historical analysis, and controlled Telegram notification in one bilingual platform.
01 · What the platform includes
Each capability is connected to the same signed event record, so the map, intelligence, history, and notification workflow remain traceable to public sources.
Displays current USGS earthquakes and NASA FIRMS wildfire clusters with source health, priority incidents, severity, danger radius, coordinates, occurrence time, magnitude or fire radiative power, and hotspot counts.
USGS + NASA FIRMS
Checks VIIRS NOAA-21, NOAA-20, and Suomi-NPP near-real-time products, selects the freshest valid acquisition set, refreshes every five minutes, and preserves the last good markers during upstream disruption.
Multi-satellite · auto refresh
Uses strict-English vector labels, selectable 2D or persistent terrain-enabled 3D, hillshade, building extrusion, hazard markers, and visible source attribution.
MapLibre · terrain · buildings
Uses high-accuracy device location, a network-assisted recovery path, or manual map placement. Turf calculates distance against each event zone and can trigger an in-browser alert with vibration and safety steps.
GPS · assisted · map placement
Explains a selected incident using fresh, bounded USGS and FIRMS evidence. The chat supports event-specific prompts, citations, progress feedback, stop, retry, copy, and clear controls.
Claude Sonnet 4.6 · cited evidence
Combines a selected full USGS earthquake year with a separately dated worldwide FIRMS window of up to five days, plus source filters, KPIs, charts, sorting, pagination, desktop tables, and mobile cards.
Earthquake year · FIRMS window
An administrator selects a current signed event, reviews the exact message, authorizes the session, and confirms one manual post. The browser cannot provide or override the destination.
Terraguard server → Telegram bot → configured channel
The full interface supports English and Arabic with RTL layout, mobile navigation, touch-sized controls, loading and degraded states, while geographic map labels intentionally remain in English.
English · العربية · RTL
02 · Platform options
Terraguard exposes only purposeful operational choices. Provider credentials and destinations remain server-controlled.
Switches between the flat operational map and terrain/building perspective; the preference persists.
Chooses how the browser establishes exposure coordinates after explicit consent.
Moves between factual source fields and evidence-grounded conversational analysis.
Applies source-aware filters, year/date controls, charting, sorting, and pagination.
Translates the interface and mirrors layout for Arabic; basemap labels remain English.
Posts the exact selected-event alert through the bot to the fixed server-side channel.
03 · How Terraguard works
The platform keeps collection, interpretation, exposure, investigation, and outbound communication as explicit stages.
Server routes request current USGS GeoJSON and three NASA FIRMS VIIRS NRT products with bounded timeouts.
Both feeds become one strict event contract; nearby fire pixels are clustered and every current event is signed server-side.
Magnitude, depth, clustered FRP, and hotspot density produce an explainable severity and heuristic danger radius.
The map refreshes while active and after focus, visibility, or network recovery; source health and stale snapshots remain visible.
Incident details, history, and Claude use bounded, attributable USGS/FIRMS evidence without receiving the user's location.
A short-lived administrator session and explicit payload confirmation authorize one manual Telegram bot-to-channel post.
04 · Trust, privacy, and resilience
Coordinates remain in browser memory, are not written to a database, and are never sent to Claude.
Incidents link to USGS or NASA FIRMS; map and AI sources remain visible to the operator.
Healthy data stays available when a feed degrades. Terraguard marks connected, degraded, stale, and offline states instead of fabricating certainty.
Telegram secrets and destination remain server-only. Signed events, same-origin checks, admin sessions, cooldowns, and rate limits protect posting.
05 · Data and service partners
06 · Technical foundation
Next.js 15 App Router · React 19 · strict TypeScript · Tailwind CSS · MapLibre GL · OpenFreeMap vectors · Mapterhorn terrain · Turf geospatial calculations · Claude Sonnet 4.6 · Telegram Bot API · Papa Parse · server-only credentials · no persistent application database.
The product uses browser memory and localStorage for some client state, while Telegram cooldown and rate-limit state is process-local. A public-authority deployment would require validated risk models, durable delivery and idempotency storage, official alerting authorization, observability, load testing, and independent security and accessibility review.