Problem Statements Analysis

From what to build to how to build it — our platform helps you understand, plan, and solve SIH 2026 problem statements with complete insights into requirements, solution approaches, technology stacks, architecture, AI/ML, and implementation roadmaps.

Scroll down
01 / SIH 2026

PS: SIH26192

Flash Flood Prediction System for Hilly Regions using Multi-Source Data Theme

Description: • Background Hilly states in India are highly vulnerable to landslides and flash floods,which often occur with very short warning times. These sudden events result in significant loss of lives and property, and current early warning mechanisms are inadequate for hyper-local prediction and timely evacuation. • Description The proposed initiative aims to develop a predictive system that integrates multiple data sources - rainfall data, soil moisture sensors,slope stability models, historical landslide inventories, and real-time IoT inputs. By combining these datasets, the system will generate hyper-local forecasts at the village or ward level, providing sufficient lead time for evacuation and risk mitigation. • Expected Solution A comprehensive flash flood prediction system that Integrates rainfall,soil moisture, slope stability, and historical disaster data, utilizes IoT sensors for real-time monitoring, issues hyper-local early warnings at village/ward level, and provides actionable lead time for evacuation and disaster preparedness.
Organization: Ministry of Home Affairs
Department: National Disaster Response Force (NDRF), DM Division
Category: Software
Theme: Disaster Managementtd>
Youtube Link: Not provided
Dataset Link: Not provided
Contact info: Not provided

Research & Technical Solution Dossier: Flash Flood & Cascaded Landslide Early Warning System for Hilly Regions

1. Executive Snapshot

Summary

Hilly regions across India (such as the Western Himalayas, North-Eastern states, and Western Ghats) face severe, sudden hydrometeorological hazards—specifically cloudbursts, flash floods, and cascaded landslides. Existing national warning mechanisms operate primarily at river basin or district levels, lacking the spatial resolution and sensor integration required to issue hyper-local (village or ward level) early warnings with actionable lead times.

This technical dossier details the end-to-end architecture, data requirements, and execution plan for ResilienceGrid-Hills: an integrated multi-source hyper-local flash flood and landslide prediction platform designed for the National Disaster Response Force (NDRF) and Ministry of Home Affairs (MHA). The solution combines satellite rainfall estimates, physics-informed hydrological runoff models, slope stability slope-angle physics (Factor of Safety calculations), historical landslide inventories, and real-time low-power IoT field sensor telemetry (ultrasonic stream level sensors and soil moisture probes). By producing automated risk assessments at the micro-watershed and village ward level, the platform generates standardized Common Alerting Protocol (CAP ITU-T X.1303) warnings. These alerts are pushed to field commanders, village panchayats, and citizens via offline-resilient mobile applications and SMS/cell broadcast networks, providing crucial 1-to-6 hour lead times for life-saving evacuations.

Metadata Table

Property Value Confidence Tag
PS Number SIH26192 [PS]
Title Flash Flood Prediction System for Hilly Regions using Multi-Source Data Theme [PS]
Organization Ministry of Home Affairs (MHA) [PS]
Department National Disaster Response Force (NDRF), DM Division [PS]
Category Software [PS]
Theme Disaster Management [PS]
Deadline 30 September 2026 [PS]
Ideas Counter 2/500 [PS]
Dataset Link Not provided in PS JSON [PS]

Fundamental System Objective

To accurately predict hyper-local flash floods and cascaded landslides at the village/ward level by fusing multi-source hydro-meteorological data with real-time IoT telemetry, delivering automated, actionable early warnings via standardized CAP protocols to enable timely community evacuation and NDRF disaster response [PS/INFERENCE].

2. Problem Deconstruction

Explicit Requirements

The supplied problem statement (sno: 192, ps_number: SIH26192) contains the following atomic, non-negotiable explicit requirements:

  1. Multi-Source Data Integration: The system must ingest and synthesize at least five distinct data sources:
    • Rainfall data [PS]
    • Soil moisture sensor inputs [PS]
    • Slope stability models [PS]
    • Historical landslide inventories [PS]
    • Real-time IoT inputs [PS]
  2. Real-Time IoT Sensor Utilization: The system must deploy or interface with IoT sensors for continuous real-time environmental and hydrological monitoring [PS].
  3. Hyper-Local Forecast Generation: Predictions and risk evaluations must be generated specifically at the village or ward level, rather than broad district or state levels [PS].
  4. Actionable Lead Time Delivery: Warnings must provide sufficient advance notice to enable field-level evacuation and risk mitigation actions prior to disaster impact [PS].
  5. Dual Disaster Focus: The system must address both flash floods and landslides in vulnerable hilly states [PS].
  6. End-User Application Scope: The expected solution is a comprehensive software platform delivering early warnings and actionable information for disaster preparedness [PS].

Inferred Requirements & Derived Implications

  1. CAP Protocol & SACHET Integration: To reach citizens and disaster responders reliably, generated alerts must comply with ITU-T X.1303 Common Alerting Protocol (CAP) and interface with the NDMA SACHET / C-DOT Integrated Alert System [INFERENCE].
  2. Offline-First Field Capability: Hilly regions frequently suffer total cellular network collapse during severe weather events; hence, local mobile applications used by NDRF ground teams and village leaders must function offline using store-and-forward local sync protocols [INFERENCE].
  3. Micro-Watershed Spatial Delineation: Village/ward boundary maps must be merged with High-Resolution Digital Elevation Models (DEMs) to form micro-watershed catchment units for runoff and slope stability computation [INFERENCE].
  4. Physics-Informed Hybrid AI Modeling: Pure machine learning fails in data-scarce mountain valleys during extreme unobserved events; the modeling core must combine physical hydrological equations (e.g., Green-Ampt infiltration, SCS-CN) with ML for anomaly detection and threshold calibration [INFERENCE].

3. Stakeholders & User Needs

Stakeholder Goal Current Pain System Need
NDRF Operational Command & Field Teams Mobilize rescue units preemptively to vulnerable villages prior to road blockages or river surges [PS/INFERENCE]. District-level warnings cover 1,000+ sq km; lack of ward-level specificity leads to delayed deployment and trapped teams [KNOWN]. Ward-level risk maps, automated route hazard alerts, real-time IoT river/soil telemetry, and CAP broadcast triggers [INFERENCE].
District Disaster Management Authorities (DDMA / District Magistrates) Issue timely, legally binding evacuation orders and allocate emergency shelter resources efficiently [INFERENCE]. False alarms cause alert fatigue; late warnings lead to loss of life. No unified multi-source dashboard exists [KNOWN]. High-confidence probabilistic flash flood/landslide risk scores (1–6 hour lead time) with automated decision-support triggers [INFERENCE].
Village Panchayats / Ward Members / Local First Responders Guide villagers along safe evacuation routes to designated shelters before floodwaters or mudslides hit [PS/INFERENCE]. Loss of cellular network during cloudbursts; local stream surges happen within 15–30 minutes without warning [KNOWN]. Offline-capable mobile app, loud siren/voice broadcast integration, multi-lingual SMS/WhatsApp warnings, simple visual risk color-coding [INFERENCE].
Citizens / Tourists in Hilly Regions Receive immediate, location-specific warnings and reach safe ground before bridges or roads wash out [PS/INFERENCE]. Broad TV/radio alerts lack actionable local guidance; tourists are unfamiliar with local terrain hazards [KNOWN]. Geo-targeted push notifications, Cell Broadcast alerts, offline route maps to nearest elevated shelter [INFERENCE].
System Administrators & Data Engineers (MHA / IMD / GSI) Maintain continuous ingestion of multi-agency data and sensor health across rugged mountain corridors [INFERENCE]. Sensor outages due to landslides; sparse sensor networks; incompatible data formats across agencies [KNOWN]. Automated sensor health monitoring, fallback to satellite precipitation data when IoT nodes drop, open API standards [INFERENCE].

4. Requirements Traceability

Feature / Module Explicit / Inferred Requirement Source Text / Derivation Technical Implementation
Multi-Source Data Ingestion Pipeline Multi-Source Data Integration [PS] "...integrates multiple data sources - rainfall data, soil moisture sensors, slope stability models, historical landslide inventories, and real-time IoT inputs..." [PS] Automated ETL microservices ingesting IMD gridded precipitation, NASA GPM, ISRO Bhuvan DEM, GSI landslide points, and IoT telemetry over MQTT/HTTP.
IoT Telemetry Gateway & Processing Real-Time IoT Monitoring [PS] "...utilizes IoT sensors for real-time monitoring..." [PS] MQTT Broker (EMQX) parsing payloads from ESP32/Cellular-LoRaWAN gateways monitoring river stage height (ultrasonic) and soil volumetric water content (VWC).
Micro-Watershed Ward Mapping Engine Hyper-Local Forecast Generation [PS] "...generate hyper-local forecasts at the village or ward level..." [PS] PostGIS spatial queries intersecting 30m/10m DEM micro-catchment runoff grids with Survey of India village ward administrative boundaries.
Early Warning & Lead Time Predictor Actionable Lead Time [PS] "...providing sufficient lead time for evacuation and risk mitigation." [PS] Physics-informed hydrological model (SCS-CN + Kinematic Wave) calculating time-to-peak flood ($T_p$) coupled with Infinite Slope Factor of Safety ($FS$) calculations.
Dual Hazard Risk Matrix Dual Disaster Focus [PS] "...vulnerable to landslides and flash floods..." [PS] Composite Risk Engine evaluating compound risk: High Soil VWC + Heavy Rainfall Intensity $\rightarrow$ Flash Flood Surge + Slope Failure Hazard Matrix.
CAP Alert Generation Module Standardized Alert Dissemination [INFERENCE] Derived from MHA/NDRF operational workflows for SACHET integration [INFERENCE]. XML generator compliant with ITU-T X.1303 CAP v1.2, producing geo-json polygons for C-DOT SACHET and Cell Broadcast networks.
Offline Field Mobile Application Low-Connectivity Operating Reality [INFERENCE] Derived from environmental constraints during mountain storms [INFERENCE]. React Native / PWA app with SQLite local database, offline vector tiles (SpatiaLite), and mesh/Bluetooth peer alert sync.

5. Constraints & Environment Realities

  1. Geography & Terrain: Steep mountain slopes (>30°), narrow V-shaped river valleys, cloudburst-prone elevation belts (1,000m–2,500m AMSL) causing rapid hydrological response times ($T_p < 30 \text{ minutes}$) [KNOWN].
  2. Connectivity & Network Outages: Heavy rainfall and landslides frequently sever fiber cables and destroy cellular towers. Data transmission from field IoT devices must rely on multi-path connectivity (Cellular 4G/2G fallback, LoRaWAN, satellite IoT messaging where available) [KNOWN].
  3. Power Grid Instability: Hilly villages suffer prolonged grid power outages during monsoon storms. IoT field nodes must be 100% self-powered using industrial solar panels (5W–10W) and LiFePO4 battery banks (6.4V/12V) with low-power deep sleep cycles [KNOWN].
  4. Language & Digital Literacy: Rural Himalayan populations and local ward members require simple, multi-lingual interfaces (Hindi, Assamese, Nepali, Garhwali, Kumaoni, etc.) with color-coded risk levels (Green, Yellow, Orange, Red) and voice-synthesized alerts [KNOWN].
  5. Hardware Exposure & Vandalism: Submersed stream sensors and mountain soil probes face severe physical drift, debris flow impacts, and lightning strikes. Sensor enclosures require IP68 rating, surge protection, and rugged mechanical mounting [KNOWN].
  6. Sparse Ground Gauge Density: Ground rainfall and soil moisture stations in Indian hilly states are sparsely distributed (often >20 km apart). System design must accommodate remote-sensing interpolation to fill spatial gaps [RESEARCHED].

6. Research Questions

  1. Hydrological Modeling: What is the minimum DEM resolution (30m SRTM/ALOS vs 10m Cartosat) required to accurately compute overland flow paths and time-to-peak in steep Himalayan V-shaped valleys without triggering excessive computational latency? [INFERENCE]
  2. Geotechnical Physics: How can slope stability models (e.g., Infinite Slope Model calculating Factor of Safety $FS = \frac{c' + (\gamma - m\gamma_w) z \cos^2\beta \tan\phi'}{\gamma z \sin\beta \cos\beta}$) be continuously updated in real-time using volumetric soil water content telemetry from sparse IoT nodes? [INFERENCE]
  3. IoT Connectivity Resilience: What is the maximum transmission range and packet delivery ratio of LoRaWAN nodes operating in deep mountain river gorges during heavy precipitation attenuating 865–867 MHz RF signals? [NEEDS VALIDATION]
  4. Data Fusion & Interpolation: How can low-latency satellite precipitation feeds (NASA GPM IMERG Early Run, updated every 4 hours) be effectively combined with IMD Nowcast radar/AWS data and real-time local IoT rainfall counters for hyper-local 1-hour nowcasting? [RESEARCHED]
  5. CAP Integration: What are the precise XML schema constraints and API authentication requirements for pushing auto-generated alerts to the C-DOT SACHET disaster portal under NDMA governance? [RESEARCHED]

7. Data Requirements & Sources

Data Type Purpose Ideal Real-World Source Hackathon Substitute Access Method Availability Privacy Sensitivity Confidence Tag
Real-time Rainfall & Nowcasts Compute runoff volume and trigger short-term flash flood alerts IMD Automatic Weather Station (AWS) API, IMD DWR Radar [1.1], NASA GPM IMERG Early Run [RESEARCHED] Open-Meteo API (historical + forecast), IMD Daily Gridded Rainfall (.grd format), simulated rain gauge IoT payload REST API, GeoTIFF / NetCDF download Publicly accessible / Open Data Non-sensitive [RESEARCHED]
Soil Moisture Data Quantify pre-event soil saturation index ($S$) and water table rise ISRO Bhuvan Soil Moisture, ESA CCI Soil Moisture [RESEARCHED], Field Soil IoT Probes NASA SMAP (Spatiotemporal 9km grid), synthetic IoT telemetry generator WMS / FTP / REST API Public / Simulated Non-sensitive [RESEARCHED]
High-Res DEM / Topography Slope angle, aspect, catchment area, river network extraction ISRO Bhuvan Cartosat-3 DEM (10m), ALOS PALSAR DEM (12.5m) [3.2, 3.7] USGS SRTM 30m DEM (OpenTopography / EarthExplorer) GeoTIFF download Publicly accessible Non-sensitive [KNOWN]
Historical Landslide Inventories Train landslide susceptibility models and define historical failure thresholds Geological Survey of India (GSI) Bhukosh Portal, NASA Global Landslide Catalog [2.1, 2.2] NASA Global Landslide Catalog (CSV/GeoJSON on HDX) CSV / GeoJSON download Publicly accessible Non-sensitive [RESEARCHED]
Administrative Boundaries Map micro-watershed risk directly to village wards for actionable alerts Survey of India Village Boundary Maps, Bharat Maps Portal GADM / OCHA Humanitarian Data Exchange (HDX) India Admin Level 4/5 GeoJSON GeoJSON / Shapefile Publicly accessible Non-sensitive [KNOWN]
Real-Time Stream Level & IoT Telemetry Detect rapid water level rise in local torrents and streams CWC Hydrological Observation Stations [1.3], State Irrigation Dept IoT networks Simulated MQTT IoT stream (Python script publishing ultrasonic distance + soil probe data over EMQX) MQTT / WebSocket Synthetic / Simulated Non-sensitive [ASSUMPTION]

Data Categorization Breakdown

  • A. Data Explicitly Mentioned: Rainfall data, Soil moisture sensors, Slope stability models, Historical landslide inventories, Real-time IoT inputs [PS].
  • B. Data Required by Inference: DEM (Digital Elevation Model), Village/Ward boundary shapefiles, Stream hydrography networks, Evacuation shelter spatial coordinates [INFERENCE].
  • C. Data to be Collected: Real-time field IoT sensor telemetry (stream level, volumetric soil moisture, tipping-bucket rainfall ticks) [ASSUMPTION].
  • D. Data to be Synthetically Generated: High-frequency IoT stream payloads simulating cloudburst events over a 24-hour test period for hackathon demonstration [ASSUMPTION].
  • E. Data Needing Validation: Real-time live API credentials for direct push into C-DOT SACHET production broadcast servers [NEEDS VALIDATION].

8. Existing Solutions & Gap Analysis

+----------------------------------------------------------------------------------------------------+
|                                    EXISTING SYSTEMS LANDSCAPE                                      |
+---------------------------------+----------------------------------+-------------------------------+
|     IMD SAsiaFFGS (2020)        |    GSI LEWS / LANDSLIP (2020)     |     CWC Flood Forecasting     |
| - Macro Watershed Level         | - Pilot Districts Only           | - Major River Basins          |
| - 6h Threat / 24h Risk          | - Daily Regional Bulletins       | - Main River Level Gauge      |
| - Lack Village Ward Precision   | - Static Rainfall Thresholds     | - No Hilly Stream Nowcasts    |
+---------------------------------+----------------------------------+-------------------------------+
                                                  |
                                                  v
+----------------------------------------------------------------------------------------------------+
|                                      PROPOSED SYSTEM GAP FILL                                      |
|                                     ResilienceGrid-Hills                                           |
| - Ward/Village Granularity (<1 sq km catchment units)                                              |
| - Real-Time Multi-Source Sensor Fusion (IoT Soil VWC + Rain + Stream Level)                         |
| - Coupled Flash Flood + Slope Stability Factor of Safety Engine                                    |
| - Automated CAP (ITU-T X.1303) Alerting with Offline Mobile Sync                                    |
+----------------------------------------------------------------------------------------------------+

1. South Asia Flash Flood Guidance System (SAsiaFFGS - IMD / WMO / HRC)

  • Description: Operationalized in October 2020 by IMD in collaboration with WMO and Hydrologic Research Center (HRC). Provides Flash Flood Guidance (FFG), Flash Flood Threat (6-hour lead time), and Flash Flood Risk (24-hour lead time) at the watershed level across South Asia [1.2, 1.4, 1.6].
  • Strengths: Robust hydrological modeling base, backed by regional meteorological radar and numerical weather prediction (NWP) models [1.4].
  • Weaknesses: Delineated at relatively large sub-basin watershed scales; lacks hyper-local village/ward level precision; does not integrate real-time local soil moisture IoT sensor grids or dynamic slope stability calculations [1.4, INFERENCE].
  • Relevance: Primary benchmark for flash flood warning algorithms in India [1.2].
  • Gap Remaining: Cannot pinpoint specific village wards facing imminent torrential stream surges or cascaded slope failures [INFERENCE].
  • Source: PIB Release ID 1667043 [1.2]; MAUSAM Journal Vol 77 [1.4].
  • Confidence: [RESEARCHED]

2. GSI Regional Landslide Early Warning System (LEWS / LANDSLIP Project)

  • Description: Prototype regional system developed by Geological Survey of India (GSI) with British Geological Survey (BGS), tested in Darjeeling (WB) and Nilgiris (TN) pilots [2.1, 2.2]. Uses terrain-specific rainfall thresholds to issue daily regional landslide forecast bulletins [2.1].
  • Strengths: Highly accurate geological susceptibility mapping and empirical rainfall intensity-duration (I-D) thresholds [2.1].
  • Weaknesses: Operates primarily as daily forecasts at district/block scales; lacks real-time streaming IoT ground instrumentation (soil VWC / pore pressure) in most vulnerable slopes; isolated from flash flood hydrodynamic models [2.1, 2.8].
  • Relevance: Standard for landslide hazard thresholds in India [2.1].
  • Gap Remaining: Does not capture real-time slope saturation dynamics during cloudbursts or link slope failure to downstream flash flood debris dams [INFERENCE].
  • Source: PIB Release ID 1777174 [2.1]; Down To Earth (Aug 2024) [2.3].
  • Confidence: [RESEARCHED]

3. CWC Riverine Flood Forecasting Network

  • Description: Central Water Commission operates ~325 hydrological observation stations across 197 low-lying areas and 128 reservoirs in major river basins [1.3].
  • Strengths: Highly accurate for major river systems (Ganga, Brahmaputra, Indus, Godavari) with 12–24 hour lead times [1.3].
  • Weaknesses: Designed for major plain rivers; completely ineffective for flash floods in steep mountain rivulets and micro-streams where response time is under 1 hour [1.3, INFERENCE].
  • Relevance: Essential source for downstream river stage data [1.3].
  • Gap Remaining: No monitoring or warning capability for mountain streams, cloudburst channels, or ward-level localized flooding [INFERENCE].
  • Source: CWC Official Portal [1.3].
  • Confidence: [RESEARCHED]

9. Candidate Solution Approaches

+----------------------------------------------------------------------------------------------------+
|                                    CANDIDATE ARCHITECTURAL APPROACHES                              |
+----------------------------------+----------------------------------+------------------------------+
|    Approach 1: Pure Empirical    |     Approach 2: Pure DL/CV       | Approach 3: Hybrid Physics   |
|       Threshold Rules            |         Spatiotemporal           |   Informed ML + IoT (Chosen) |
+----------------------------------+----------------------------------+------------------------------+
| - Rain Thresholds (I-D curves)   | - ConvLSTM / Graph Neural Net    | - SCS-CN + Infinite Slope    |
| - Hardcoded Rule Matrix          | - End-to-end Black Box Prediction| - Light Gradient Boosting    |
| - Fast, Simple, Deterministic    | - Requires Massive Datasets      | - IoT Real-Time Calibration  |
| - High False Alarm Rate          | - Unexplainable Failures         | - Explainable & Robust       |
+----------------------------------+----------------------------------+------------------------------+

Approach 1: Pure Empirical Threshold & Rule-Based Hydrological Engine

  • Mechanism: Uses static Rainfall Intensity-Duration (I-D) curves and predefined soil moisture thresholds. If 1-hour rainfall exceeds 50 mm/hr OR 24-hour cumulative rainfall exceeds 120 mm, trigger a village-level alert [INFERENCE].
  • Data Requirements: Rain gauge data, historical threshold tables [INFERENCE].
  • Complexity: Low ($O(1)$ lookup execution) [INFERENCE].
  • Explainability: 100% transparent and deterministic [INFERENCE].
  • Cost: Very low [INFERENCE].
  • Scalability: High [INFERENCE].
  • Hackathon Feasibility: Extremely high (can build in 2 days) [INFERENCE].
  • Production Feasibility: Poor. High false positive/negative rate because it ignores slope saturation history, land cover changes, and micro-terrain geometry [INFERENCE].
  • Risks: Unreliable during unprecedented cloudburst events [INFERENCE].

Approach 2: Pure Deep Learning Spatiotemporal Forecasting System

  • Mechanism: Trains a 3D ConvLSTM or Graph Neural Network (GNN) on historical satellite rainfall grids, DEMs, and stream gauge time-series to directly predict 3D flood depth and landslide susceptibility maps [INFERENCE].
  • Data Requirements: Decades of high-resolution, continuous gridded hydro-meteorological and IoT time-series data [INFERENCE].
  • Complexity: Extremely high [INFERENCE].
  • Explainability: Black-box model; difficult to justify legally to NDRF commanders why an evacuation order was triggered [INFERENCE].
  • Cost: High GPU computing cost [INFERENCE].
  • Scalability: Moderate (constrained by inference hardware) [INFERENCE].
  • Hackathon Feasibility: Low for a 4-6 student team due to lack of complete, cleaned training data across all Indian mountain wards [INFERENCE].
  • Production Feasibility: Risky due to potential out-of-distribution catastrophic failures during extreme weather [INFERENCE].

Approach 3: Hybrid Physics-Informed ML & IoT Edge-Cloud Architecture (RECOMMENDED)

  • Mechanism: Combines deterministic physical modeling (SCS-CN surface runoff + Infinite Slope Factor of Safety model) with a lightweight ML anomaly classifier (XGBoost / LightGBM) calibrated in real-time by streaming IoT telemetry (ultrasonic stream level and soil VWC) [INFERENCE].
  • Data Requirements: Open DEM (30m/10m), satellite rainfall feeds, GSI landslide inventory points, and streaming IoT gauge data [INFERENCE].
  • Complexity: Moderate (Modular architecture) [INFERENCE].
  • Explainability: High. Every alert outputs physical metrics (e.g., "Calculated Factor of Safety $FS < 1.05$", "Predicted Stream Discharge $Q_{peak} = 45 \text{ m}^3/\text{s}$ exceeding bank capacity") [INFERENCE].
  • Cost: Low to Moderate (Runs on standard cloud VM + lightweight edge devices) [INFERENCE].
  • Scalability: High (Parallel micro-watershed computations) [INFERENCE].
  • Hackathon Feasibility: High. Core physics models can be implemented in Python/NumPy, ML tuned on synthetic/historical data, and IoT simulated cleanly [INFERENCE].
  • Production Feasibility: Excellent. Combines scientific domain validity with real-time IoT responsiveness [INFERENCE].

10. Recommended Approach & Why

Selection: Approach 3 (Hybrid Physics-Informed ML + IoT Edge-Cloud Architecture)

Why Alternatives Were Rejected

  1. Rejection of Approach 1 (Pure Empirical Rules): While easy to implement during a hackathon, pure empirical I-D curves trigger excessive false alarms in mountain environments. Soil that is completely dry can absorb 50 mm/hr without sliding, whereas soil that is 95% saturated will fail under 10 mm/hr. A static threshold cannot capture this dynamic saturation state [INFERENCE].
  2. Rejection of Approach 2 (Pure Deep Learning): Deep learning requires vast, clean training sets linking precise rainfall grids to historical flood levels at individual village wards. Such datasets do not exist for 90% of rural Himalayan villages. Furthermore, black-box AI models cannot provide auditability or explainable physics needed for NDRF evacuation authorization [INFERENCE].

Justification for Hybrid Approach

Approach 3 leverages the strengths of both domain physics and machine learning:

  • Physical hydrological modeling guarantees that mass conservation and slope mechanics rules are never violated, providing baseline stability even when data is sparse [INFERENCE].
  • Machine learning acts as an adaptive error-correction and threshold-tuning layer, using real-time field IoT telemetry (soil moisture % and stream stage) to adjust physical parameters (such as soil hydraulic conductivity $K_s$ and runoff curve numbers) dynamically [INFERENCE].
  • This hybrid model generates explainable risk metrics (Factor of Safety $FS$, Infiltration Rate, Time to Peak $T_p$) that NDRF officers can inspect and trust during critical emergency operations [INFERENCE].

11. Technical Architecture

+----------------------------------------------------------------------------------------------------+
|                                      SYSTEM ARCHITECTURE                                           |
+----------------------------------------------------------------------------------------------------+

[ 1. DATA INGESTION & IOT LAYER ]
  +-----------------------+   +-----------------------+   +-----------------------+
  |  IMD / NASA GPM Rain  |   |  ISRO Bhuvan DEM /    |   | Field IoT Telemetry   |
  |  (REST API / NetCDF)  |   |  GSI Landslide Points |   | (LoRaWAN / Cellular)  |
  +-----------+-----------+   +-----------+-----------+   +-----------+-----------+
              |                           |                           |
              +-------------------+-------+---------------------------+
                                  |
                                  v
[ 2. STREAM PROCESSING & GIS INGESTION ]
  +-----------------------------------------------------------------------------------+
  | EMQX MQTT Broker (IoT Sensor Telemetry Ingestion)                                 |
  | GDAL / Rasterio Data Normalization Pipeline (DEM & Satellite Raster Processing)    |
  +-----------------------------------+-----------------------------------------------+
                                      |
                                      v
[ 3. CORE PROCESSING & PREDICTION ENGINE (Hybrid Physics + ML) ]
  +-----------------------------------------------------------------------------------+
  | Micro-Watershed Hydro Engine: SCS-CN Surface Runoff & Kinematic Wave Discharge     |
  | Geotechnical Slope Stability Engine: Infinite Slope Model (Factor of Safety FS)   |
  | ML Anomaly & Threshold Refinement: XGBoost Calibration Layer                      |
  +-----------------------------------+-----------------------------------------------+
                                      |
                                      v
[ 4. DATA STORAGE LAYER ]
  +-----------------------------------------------------------------------------------+
  | PostgreSQL + PostGIS (Spatial Catchment Polygons, Village Ward Geometries)       |
  | TimescaleDB (Sensor Time-Series Telemetry & Historical Model Outputs)            |
  | Redis Cache (Active Alert States & Rapid Geo-Fence Queries)                       |
  +-----------------------------------+-----------------------------------------------+
                                      |
                                      v
[ 5. DISSEMINATION & API LAYER ]
  +-----------------------------------------------------------------------------------+
  | FastApi REST Gateway & WebSockets (Real-Time Live Map Telemetry Feed)            |
  | CAP v1.2 XML Alert Generator (ITU-T X.1303 Compliant Push to C-DOT SACHET)       |
  | Firebase Cloud Messaging (FCM) & Twilio SMS Gateway                               |
  +-----------------------------------+-----------------------------------------------+
                                      |
              +-----------------------+-----------------------+
              |                                               |
              v                                               v
[ 6. COMMAND DASHBOARD ]                            [ 7. OFFLINE FIELD MOBILE APP ]
  (React + MapLibre GL JS)                           (React Native + SQLite + Vector Tiles)
  - NDRF / DDMA Command Center                       - Village Ward Leaders & Field Teams
  - Real-Time Hazard Heatmap                         - Offline GIS Navigation & Emergency Alerts
  - Live IoT Sensor Telemetry Graphs                 - Peer-to-Peer Bluetooth Sync

Data Flow Narrative

  1. Ingestion Step:
    • Satellite rainfall data (NASA GPM IMERG / IMD Gridded) is fetched automatically every 30 minutes via scheduled Celery workers.
    • Ground IoT nodes (ultrasonic water level sensors and soil volumetric water content probes) transmit readings over MQTT every 5 minutes to the EMQX Broker [INFERENCE].
  2. Spatial Feature Extraction:
    • Incoming rainfall grids are mapped to spatial micro-watershed boundaries pre-extracted from Cartosat/SRTM DEMs using PostGIS spatial raster intersection algorithms [INFERENCE].
  3. Physics Modeling Computation:
    • Hydrological Step: The SCS-CN model computes surface runoff volume $Q$ based on 5-day antecedent moisture condition (AMC) updated continuously by soil IoT probes [INFERENCE].
    • Hydrodynamic Step: Runoff volume is routed down stream channels using Kinematic Wave equations to estimate water level surge height and Time-to-Peak ($T_p$) at downstream village ward bridges [INFERENCE].
    • Slope Stability Step: The Infinite Slope model calculates the Factor of Safety ($FS$) for every 30m grid cell within the ward. $FS < 1.0$ triggers a landslide failure hazard flag [INFERENCE].
  4. Risk Aggregation & Alert Generation:
    • The system evaluates compound hazard rules: If $FS < 1.15$ AND predicted stream stage exceeds bank level, a CRITICAL RED ALERT is triggered for that specific village ward [INFERENCE].
    • The alert generator constructs an ITU-T X.1303 compliant CAP 1.2 XML payload specifying precise ward boundary polygons, severity, urgency, and specific evacuation instructions [INFERENCE].
  5. Multi-Channel Broadcast & Field Sync:
    • The CAP alert is pushed to the NDRF Command Dashboard via WebSockets, fired to local residents via FCM Push Notifications and SMS, and pushed to the C-DOT SACHET endpoint [INFERENCE].
    • Ground teams running the offline React Native app receive the alert; if cellular data is unavailable, local mesh nodes transmit alert packets via LoRaWAN/Bluetooth LE peer-to-peer sync [INFERENCE].

12. Technology Stack

Layer Selected Technology Why Selected Alternative Considered Why Alternative Rejected
Frontend Dashboard React.js + MapLibre GL JS + TailwindCSS Fast vector tile rendering for complex topographic hillshade maps and smooth GIS polygon rendering [INFERENCE]. Leaflet.js Lacks performant WebGL rendering for dense 3D terrain elevation layers and real-time particle flows [INFERENCE].
Mobile App React Native + WatermelonDB / SQLite Enables cross-platform (Android/iOS) build with fast offline SQLite database synchronization [INFERENCE]. Flutter SQLite offline spatial tile plugins are less mature than React Native SpatiaLite bindings [INFERENCE].
Backend API Python (FastAPI) + Asyncio Native support for GIS geospatial libraries (GDAL, Shapely, PyProj) and high-performance async WebSockets [INFERENCE]. Node.js (Express) Poor native Python bindings for heavy geospatial raster processing and numerical matrix operations [INFERENCE].
Database (Relational & Spatial) PostgreSQL + PostGIS The industry standard open-source spatial database; handles complex polygon overlays and raster intersections efficiently [INFERENCE]. MongoDB Poor native support for advanced spatial raster-vector overlay queries and topology analysis [INFERENCE].
Database (Time-Series) TimescaleDB (PostgreSQL extension) Optimized for high-throughput time-series storage of streaming IoT sensor readings with automatic data retention policies [INFERENCE]. InfluxDB Requires maintaining a separate database engine, increasing system operational overhead [INFERENCE].
In-Memory Cache & Broker Redis High-speed spatial geo-fencing lookup and pub/sub broker for WebSocket real-time alert pushes [INFERENCE]. Memcached Lacks native pub/sub capabilities and spatial geospatial indexing features [INFERENCE].
IoT Ingestion Broker EMQX (Open Source MQTT Broker) Massive concurrent connection capacity, built-in rule engine, and seamless enterprise integration [INFERENCE]. Mosquitto Limited clustering capabilities and lacks enterprise rule-engine features for high-availability production [INFERENCE].
AI / Physics Modeling Python (NumPy, SciPy, XGBoost, Rasterio) Standard ecosystem for scientific computing, raster analysis, and fast gradient boosted tree inference [INFERENCE]. TensorFlow / PyTorch Overkill for physics-informed numerical hydrological equations; adds unnecessary computational overhead [INFERENCE].
Task Queue & Scheduler Celery + Redis Reliable distributed background task execution for processing scheduled satellite raster downloads [INFERENCE]. Cron jobs Lacks distributed worker scaling, retry handling, and task state monitoring capabilities [INFERENCE].
Alert Dissemination C-DOT CAP XML Schema / Twilio / FCM Official ITU-T X.1303 compliance for national disaster alert portal interoperability [4.5]. Generic REST Webhooks Fails national regulatory requirements for standardized emergency broadcasting [4.5].

13. AI/ML Justification

Component 1: Adaptive Soil Saturation & Runoff Curve Number ($CN$) Calibration Layer

  1. Exact Problem Solved: Translating continuous point-source soil moisture IoT readings (%) and antecedent rainfall into dynamic runoff curve numbers ($CN$) for heterogenous micro-watersheds [INFERENCE].
  2. Input: Volumetric Water Content (VWC %), 5-day cumulative rainfall (mm), Soil texture class, Land cover type [INFERENCE].
  3. Output: Calibrated dynamic Runoff Curve Number ($CN_d \in [30, 98]$) for hydrological runoff volume estimation [INFERENCE].
  4. Why Simpler Rules Fail: Static SCS-CN tables use coarse discrete categories (AMC I, II, III) that jump discretely, causing artificial spikes in calculated runoff. ML provides smooth, continuous non-linear interpolation [INFERENCE].
  5. Data Required: Historical paired soil moisture, rainfall, and stream gauge hydrographs [INFERENCE].
  6. Evaluation Metric: Root Mean Square Error ($RMSE$) against observed stream peak discharge ($Q_{peak}$) [INFERENCE].
  7. Failure Mode Handling: If model predictions diverge from physical boundaries ($CN_d < 30$ or $>98$), fallback to standard static SCS-CN lookup tables [INFERENCE].
  8. Training/Fine-tuning: Trained offline using XGBoost Regressor; no heavy deep learning fine-tuning required [INFERENCE].
  9. Human Oversight: Hydrological parameters validated by NDRF/CWC domain experts before deployment [INFERENCE].

Component 2: Landslide Susceptibility Hazard Classifier

  1. Exact Problem Solved: Predicting spatial probability of slope failure at 30m cell resolution during intense cloudbursts [INFERENCE].
  2. Input: Slope angle, Aspect, Elevation, Lithology/Geology, Distance to fault lines, Historical failure points, Real-time Factor of Safety ($FS$), dynamic Soil Saturation [INFERENCE].
  3. Output: Probability score $P(\text{Landslide}) \in [0, 1]$ mapped to susceptibility zones [INFERENCE].
  4. Why Simpler Rules Fail: Infinite Slope physical equations assume uniform slope material and planar failure, underestimating complex multi-factor failures driven by road-cutting or geology [INFERENCE].
  5. Data Required: GSI Landslide Inventory points, DEM derived slope/aspect maps, satellite rainfall grids [2.1, INFERENCE].
  6. Evaluation Metric: Area Under ROC Curve ($ROC-AUC > 0.85$), Precision-Recall curve [INFERENCE].
  7. Failure Mode Handling: If ML model outputs low probability but physical equation shows $FS < 1.0$, the physical safety rule overrides ML and forces a high risk alert [INFERENCE].
  8. Training/Fine-tuning: Random Forest / LightGBM trained on GSI historical inventory [2.1, INFERENCE].
  9. Human Oversight: High-risk predictions flag geological review markers on the NDRF command dashboard [INFERENCE].

Explicit Non-AI Directives

  • DO NOT use AI for final alert triggers: Critical public evacuation alerts MUST NOT be generated solely by a neural network black box. Final decision logic must rely on deterministic physical threshold rules ($FS < 1.0$ or Stream Level $> \text{Danger Level}$) to guarantee zero unexplainable hallucinations [INFERENCE].
  • DO NOT use AI for DEM interpolation: Interpolating elevation data using AI generative models introduces fabricated topography. Standard spatial interpolation (Bilinear / Kriging) MUST be used [INFERENCE].

14. Data Architecture & Offline/Low-Network Design

Primary Database Schemas (PostGIS / PostgreSQL)

-- Micro-Watershed Catchments Table
CREATE TABLE catchments (
    catchment_id SERIAL PRIMARY KEY,
    catchment_code VARCHAR(50) UNIQUE NOT NULL,
    ward_name VARCHAR(100) NOT NULL,
    village_code VARCHAR(50) NOT NULL,
    geom GEOMETRY(MultiPolygon, 4326) NOT NULL,
    mean_slope_deg FLOAT NOT NULL,
    curve_number_base INT NOT NULL,
    area_sqkm FLOAT NOT NULL
);

-- IoT Sensor Nodes Table
CREATE TABLE iot_nodes (
    node_id VARCHAR(50) PRIMARY KEY,
    node_type VARCHAR(30) CHECK (node_type IN ('STREAM_LEVEL', 'SOIL_MOISTURE', 'RAIN_GAUGE')),
    latitude FLOAT NOT NULL,
    longitude FLOAT NOT NULL,
    catchment_id INT REFERENCES catchments(catchment_id),
    last_ping TIMESTAMP WITH TIME ZONE,
    battery_v FLOAT NOT NULL,
    status VARCHAR(20) DEFAULT 'ACTIVE'
);

-- Telemetry Time-Series Table (TimescaleDB Hypertable)
CREATE TABLE sensor_telemetry (
    time TIMESTAMP WITH TIME ZONE NOT NULL,
    node_id VARCHAR(50) REFERENCES iot_nodes(node_id),
    water_level_m FLOAT,
    soil_vwc_percent FLOAT,
    rainfall_1h_mm FLOAT,
    battery_status FLOAT
);
SELECT create_hypertable('sensor_telemetry', 'time');

-- Generated Alerts Table
CREATE TABLE disaster_alerts (
    alert_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    catchment_id INT REFERENCES catchments(catchment_id),
    hazard_type VARCHAR(30) CHECK (hazard_type IN ('FLASH_FLOOD', 'LANDSLIDE', 'COMPOUND')),
    severity_level VARCHAR(20) CHECK (severity_level IN ('GREEN', 'YELLOW', 'ORANGE', 'RED')),
    cap_xml_payload TEXT NOT NULL,
    time_issued TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP,
    lead_time_hours FLOAT NOT NULL
);

Offline & Synchronization Architecture for Mobile App

+----------------------------------------------------------------------------------------------------+
|                                    OFFLINE SYNCHRONIZATION FLOW                                    |
+----------------------------------------------------------------------------------------------------+

[ FIELD MOBILE APP ]                                                [ CENTRAL BACKEND ]
  |                                                                   |
  |-- (1) Cellular Online? ------------------------------------------>|
  |     YES: Fetch vector tiles & latest CAP alerts via REST API       |
  |                                                                   |
  |-- (2) Cellular Connection Dropped (OFFLINE MODE)                  |
  |     - App switches to local SpatiaLite / WatermelonDB             |
  |     - Renders cached local offline vector map tiles (.mbtiles)     |
  |     - Listens for local LoRaWAN / Bluetooth LE peer packets       |
  |                                                                   |
  |-- (3) Field Officer Reports Incident Offline                      |
  |     - Saves report locally in offline SQLite queue                |
  |                                                                   |
  |-- (4) Connection Restored ---------------------------------------->|
  |     - Executes Differential Delta Sync (pushed cached reports)    |
  |     - Resolves conflicts using Last-Write-Wins (LWW) + Vector Clock|
  +-------------------------------------------------------------------+

Bandwidth & Payload Optimization Techniques

  1. Protobuf Data Compression: IoT readings sent over cellular 2G networks use Protocol Buffers (Protobuf) instead of verbose JSON, reducing payload size by ~80% (from 450 bytes to <80 bytes per ping) [INFERENCE].
  2. MBTiles Map Pre-caching: Disaster responders download regional offline vector map tiles (.mbtiles format covering their district) while connected to Wi-Fi at base camps [INFERENCE].
  3. Delta Sync Protocol: When reconnecting after an outage, the mobile client requests only modified record hashes using HTTP If-Modified-Since headers [INFERENCE].

15. Security, Privacy & Governance

  1. Personal & Location Data Protection: Mobile user tracking is strictly opt-in and restricted to geo-fenced safety checks. No precise user GPS traces are stored long-term; user location is dynamically matched against ward polygons in memory using Redis Geo-indexing and discarded after alert delivery [INFERENCE].
  2. Authentication & Access Control:
    • IoT Nodes: Enrolled via HMAC-SHA256 pre-shared keys and TLS 1.3 encryption. Unauthenticated MQTT sensor payloads are dropped at the EMQX boundary [INFERENCE].
    • Dashboard & APIs: Role-Based Access Control (RBAC) enforced via OAuth2 + JWT tokens. Only authorized MHA/NDRF field commanders possess administrative privileges to override or issue manual warning broadcasts [INFERENCE].
  3. Data Encryption: End-to-end TLS 1.3 encryption for all data in transit; AES-256 encryption at rest for PostgreSQL database volumes and offline SQLite client databases [INFERENCE].
  4. Data Ownership & Governance: All processed hydrological data and generated alerts belong exclusively to the Ministry of Home Affairs (MHA) / NDRF. Open-access weather inputs maintain standard open-source attribution [INFERENCE].
  5. False Positive & False Negative Liability Mitigation:
    • All automated system notifications explicitly carry confidence scores and severity levels [INFERENCE].
    • High-level public siren activations require a single-click authorization confirmation from designated district disaster officials, preventing accidental automated mass panic [INFERENCE].
    • System log trails record every data input, threshold check, and user authorization for post-event regulatory auditing [INFERENCE].

16. MVP Scope (Hackathon Build)

+----------------------------------------------------------------------------------------------------+
|                                      HACKATHON MVP SCOPE                                           |
+----------------------------------------------------------------------------------------------------+

  MUST BUILD (Core Value Proposition)
  ----------------------------------
  [x] Interactive Web Dashboard (React + MapLibre GL) rendering micro-watershed ward risk boundaries.
  [x] Python Hydro-Engine (SCS-CN surface runoff + Infinite Slope Factor of Safety calculation).
  [x] Real-time IoT MQTT Ingestion Broker receiving live/simulated stream level & soil moisture ticks.
  [x] Standardized ITU-T X.1303 CAP v1.2 XML Alert Generator with downloadable GeoJSON payloads.
  [x] Historical Cloudburst Simulation Replay (Himachal 2023 / Wayanad 2024 rainfall profile).

  SHOULD BUILD (High Differentiators)
  -----------------------------------
  [x] React Native Mobile App interface displaying offline vector map tiles and hazard alerts.
  [x] Hybrid XGBoost ML calibration layer adjusting runoff curve numbers dynamically.
  [x] Dual-hazard compound matrix (Flash Flood surge + Landslide failure probability).

  NICE TO HAVE (If Time Permits)
  ------------------------------
  [ ] WhatsApp / Automated SMS delivery integration via Twilio sandbox.
  [ ] LoRaWAN hardware physical sensor node demonstration on stage.

  DO NOT BUILD DURING HACKATHON (Out of Scope / Production Only)
  -------------------------------------------------------------
  [ ] Live production credentials integration into C-DOT SACHET national broadcast servers.
  [ ] Mass physical deployment of 1,000+ custom IoT hardware nodes across mountain ranges.
  [ ] Custom satellite launch or direct SAR radar satellite ground station integration.
+----------------------------------------------------------------------------------------------------+

17. Live Demo Simulation Plan

To present a compelling, technically honest live demonstration without relying on unpredictable live weather or unverified government API keys, the team will execute a Controlled Environmental Hardware-in-the-Loop Simulation:

+----------------------------------------------------------------------------------------------------+
|                                    LIVE DEMO SIMULATION WORKFLOW                                    |
+----------------------------------------------------------------------------------------------------+

[ 1. PHYSICAL IOT HARDWARE NODE ON DEMO STAGE ]
  - ESP32 Microcontroller + Ultrasonic Distance Sensor (Water Level) + Capacitive Soil Moisture Probe
  - Dip sensor in a beaker of water & wet soil container live during presentation.
  - Sensor transmits real-time telemetry over Wi-Fi/4G via MQTT to EMQX Cloud Broker.

                                  |
                                  v

[ 2. CLOUDBURST HISTORICAL EVENT REPLAY ENGINE ]
  - Inject 2023 Himachal Pradesh / 2024 Wayanad extreme rainfall time-series into the live engine.
  - Show live dashboard updating stream stage graphs and soil moisture saturation curve in real time.

                                  |
                                  v

[ 3. REAL-TIME HYPER-LOCAL HAZARD MAP UPDATING ]
  - Watch target village ward polygon shift on MapLibre map from GREEN -> ORANGE -> RED.
  - Factor of Safety (FS) gauge drops below 1.0; predicted stream discharge exceeds bank height.

                                  |
                                  v

[ 4. AUTOMATED CAP ALERT & MOBILE NOTIFICATION ]
  - System generates compliant CAP 1.2 XML payload dynamically on screen.
  - Mobile app on physical test smartphone receives instant push notification & trigger loud siren.
  - Toggle smartphone into Airplane Mode: App demonstrates offline vector tile map & evacuation route.
+----------------------------------------------------------------------------------------------------+

Note: All simulated inputs will be explicitly labeled as "Simulated Environmental Feed" during the live presentation, preserving 100% technical integrity. [ASSUMPTION]

18. Implementation Roadmap

Project Timeline: Target Deadline 30 September 2026

2026 Phase Schedule:
+----------------------------------------------------------------------------------------------------+
| MAY 2026           | JUNE 2026          | JULY 2026          | AUGUST 2026        | SEPT 2026     |
| Phase 1: Setup     | Phase 2: Engine    | Phase 3: IoT & ML  | Phase 4: App & UI  | Phase 5: Demo |
+--------------------+--------------------+--------------------+--------------------+---------------+
| - Ingest SRTM/Cart | - SCS-CN Hydro     | - MQTT EMQX setup  | - React Dashboard  | - End-to-end  |
| - Ward shapefiles  | - Infinite Slope   | - XGBoost tuning   | - React Native App |   dry-runs    |
| - Schema setup     |   FS model         | - CAP XML module   | - Offline caching  | - SIH Final   |
+----------------------------------------------------------------------------------------------------+
  • Phase 1: Foundation & GIS Pipeline (May 1 – May 31, 2026)
    • Set up PostgreSQL + PostGIS database and TimescaleDB hypertables [INFERENCE].
    • Ingest SRTM 30m DEM, parse hydrography networks, and cut out sample micro-watersheds for target mountain districts (e.g., Shimla / Mandi / Wayanad) [INFERENCE].
    • Load GADM administrative ward shapefiles and historical GSI landslide points [2.1].
  • Phase 2: Physics Modeling Core (June 1 – June 30, 2026)
    • Implement SCS-CN surface runoff volume calculations in Python [INFERENCE].
    • Implement hydro-routing Kinematic Wave differential equations for stream stage surge [INFERENCE].
    • Code Infinite Slope Factor of Safety ($FS$) spatial calculation engine [INFERENCE].
  • Phase 3: IoT Broker, ML Tuning & CAP Engine (July 1 – July 31, 2026)
    • Deploy EMQX MQTT broker and build ESP32 hardware prototype node [INFERENCE].
    • Train XGBoost model for dynamic curve number calibration using synthetic/historical hydrographs [INFERENCE].
    • Build ITU-T X.1303 CAP 1.2 XML builder microservice [4.5].
  • Phase 4: Dashboard, Mobile App & Offline Capabilities (August 1 – August 31, 2026)
    • Develop MapLibre GL JS web dashboard for NDRF command centers [INFERENCE].
    • Build React Native mobile application with SQLite offline caching and MBTiles map rendering [INFERENCE].
    • Conduct low-network simulation tests and bandwidth optimization [INFERENCE].
  • Phase 5: Validation, Stress Testing & Presentation Pitch (Sept 1 – Sept 30, 2026)
    • Perform false-positive/false-negative testing against historical storm records [INFERENCE].
    • Finalize live hardware stage demo playbook and presentation deck [INFERENCE].
    • Freeze code base for SIH deadline submission (30 September 2026) [PS].

19. Testing & Validation Plan

Test Category Target Metric / Scenario Validation Methodology Success Criteria Confidence Tag
Functional Hydro-Testing Surface Runoff & Peak Discharge Accuracy Replay historical 2023 Himachal rainfall event; compare model $Q_{peak}$ against CWC stream gauge records [1.4]. Calculated peak discharge within $\pm 15%$ of actual historical stream gauge peak [INFERENCE]. [INFERENCE]
Geotechnical Failure Testing Landslide Slope Failure Identification Run Factor of Safety ($FS$) calculations across known GSI failure coordinates under saturated conditions [2.1]. $FS < 1.0$ triggered for $>80%$ of historical failure points under storm saturation [INFERENCE]. [INFERENCE]
IoT Performance & Stress MQTT Ingestion Scalability Use Locust load tester to simulate 1,000 IoT nodes publishing telemetry every 5 seconds simultaneously. Zero dropped packets ($0%$ message loss); API ingestion latency $<100\text{ ms}$ [INFERENCE]. [INFERENCE]
False-Positive Optimization Moderate Rain Non-Event Scenarios Feed 50 dry-season moderate rainfall events (20–30 mm/day over unsaturated soil) into the system. False alarm alert rate $<5%$ [INFERENCE]. [INFERENCE]
False-Negative Strict Gate Cloudburst Severe Scenarios Feed 10 cloudburst profiles (>50 mm in 1 hour over saturated soil). Zero false negatives ($0%$ missed disaster alerts) [INFERENCE]. [INFERENCE]
Offline Sync Reliability Total Cellular Disconnection & Re-sync Cut cellular connection on mobile app, record 20 incident reports, restore connection after 2 hours. $100%$ differential delta sync to backend database without data loss [INFERENCE]. [INFERENCE]
CAP Protocol Compliance Schema Interoperability Validate generated alert XML payloads against ITU-T X.1303 official XML schema validator. $100%$ schema validation compliance with zero syntax errors [4.5]. [RESEARCHED]

20. Risk Register

Risk Event Likelihood Impact Severity Score Mitigation Strategy Confidence Tag
IoT Sensor Destruction during Flash Floods High Medium High Mount sensors high above historical flood levels (e.g., bridge gantries); implement automated sensor death detection that triggers remote satellite interpolation fallback when node pings drop [INFERENCE]. [INFERENCE]
Severe Cellular Network Collapse in Hilly Terrain High High Critical Implement offline vector map caching, SMS fallback headers, and LoRaWAN/Bluetooth peer-to-peer alert mesh sync in field app [INFERENCE]. [KNOWN]
False Alarm Panic (Over-Alerting) Medium High High Enforce mandatory 2-tier approval workflow (Automated Alert $\rightarrow$ DDMA Officer 1-click confirmation) before mass public siren broadcast [INFERENCE]. [INFERENCE]
Inaccurate DEM Resolution in Steep V-Valleys Medium Medium Medium Blend 30m SRTM open data with high-resolution 10m ISRO Cartosat DEM where available; apply hydrological flow direction sinks correction [3.7]. [RESEARCHED]
Lack of Live Government API Access during Hackathon High Low Low Build robust synthetic API mocks and historical event replay engines that mimic real-time IMD/CWC data formats exactly [ASSUMPTION]. [ASSUMPTION]

21. Cost & Scalability

Hackathon Prototype Cost Breakdown

Component Selected Option Cost (INR / USD) Justification
Cloud Hosting AWS Free Tier / Render / Supabase Free Tier ₹0 / $0 Sufficient for prototype hosting and database needs [ASSUMPTION].
IoT Prototype Hardware 1x ESP32 (₹450), 1x Ultrasonic Sensor (₹150), 1x Capacitive Soil Probe (₹200) ₹800 (~$10) Low-cost physical hardware proof-of-concept for live stage demo [ASSUMPTION].
Database & GIS Software PostgreSQL + PostGIS (Open Source) ₹0 / $0 Completely open-source spatial database stack [INFERENCE].
Map Base Layers MapLibre GL JS + OpenStreetMap / Stamen Terrain ₹0 / $0 Free, high-performance open vector tiles without commercial API costs [INFERENCE].
Total Hackathon Build Cost ~₹800 ($10) Accessible for any 4-6 student hackathon team.

Production Deployment & Scaling Model

Scale Component Implementation Architecture Estimated Annual Cost Tier
Cloud Infrastructure Multi-AZ AWS Kubernetes Cluster (EKS), Managed PostgreSQL PostGIS, Timescale Cloud Scalable cloud compute depending on state coverage [INFERENCE].
IoT Field Grid Deployment Industrial LoRaWAN Gateways, Solar-powered radar stage gauges, TDR soil moisture sensors Financed via State Disaster Mitigation Funds (SDMF) / MHA schemes [INFERENCE].
Bandwidth & SMS Dissemination C-DOT CAP SACHET integration (Government infrastructure) + BSNL Cell Broadcast Zero direct SMS costs via national emergency broadcast network integration [4.2, 4.5].

22. Differentiation

+----------------------------------------------------------------------------------------------------+
|                                      KEY DIFFERENTIATORS                                           |
+----------------------------------------------------------------------------------------------------+

  1. DUAL HAZARD COMPOUND COUPLING
     - Unlike isolated flood or landslide tools, ResilienceGrid-Hills explicitly links soil saturation
       to BOTH slope failure (Factor of Safety) AND flash flood stream surges simultaneously.

  2. HYPER-LOCAL VILLAGE WARD GRANULARITY
     - Moves beyond macro district/basin warnings down to individual administrative ward polygons,
       eliminating unnecessary evacuations in non-impacted adjacent valleys.

  3. STANDARDIZED CAP (ITU-T X.1303) NATIVE ARCHITECTURE
     - Built natively to push structured alert XML payloads into NDMA SACHET and C-DOT Cell
       Broadcast systems without requiring middleware re-engineering.

  4. OFFLINE-FIRST RESILIENT MOBILE DESIGN
     - Operates reliably when mountain cell towers fail, using cached vector tiles (.mbtiles) and
       store-and-forward differential database synchronization.
+----------------------------------------------------------------------------------------------------+

23. Future Scope

  1. Drone-Based Rapid Post-Disaster Damage Assessment: Integrating autonomous drone flight paths triggered automatically by RED alerts to capture high-resolution imagery of river debris dams and landslide scars [INFERENCE].
  2. Satellite Synthetic Aperture Radar (SAR) Inundation Mapping: Integrating Sentinel-1 / NISAR C-band SAR satellite feeds to penetrate dense monsoon cloud cover and auto-detect standing floodwaters in mountain basins [3.7, INFERENCE].
  3. Community-Sourced Crowdsourced Telemetry: Enabling local village ward members to upload geo-tagged photo observations of stream surges or slope cracks, using computer vision to auto-verify ground truth conditions [3.2, INFERENCE].

24. Assumptions & Open Items Log

Consolidated Assumptions Log

  1. [ASSUMPTION]: A 30-meter DEM (SRTM/ALOS) provides sufficient spatial resolution to compute micro-watershed stream networks for village-level flash flood modeling during the hackathon MVP phase.
  2. [ASSUMPTION]: Physical IoT stage demonstration can be reliably simulated using an ESP32 microcontroller with ultrasonic and capacitive soil sensors connected over Wi-Fi/4G.
  3. [ASSUMPTION]: Historical rainfall time-series from major past disasters (e.g., Himachal Pradesh July 2023 / Wayanad July 2024) serve as valid benchmarks for evaluating prediction model lead times.
  4. [ASSUMPTION]: Hackathon hosting costs can be maintained at virtually zero using open-source tools and free cloud tiers.

Consolidated Open Items & Validation Log

  1. [NEEDS VALIDATION]: Direct API access and authentication credentials for pushing live test alerts into C-DOT SACHET production servers under NDMA governance.
  2. [NEEDS VALIDATION]: Exact LoRaWAN RF signal attenuation levels across dense Himalayan vegetation during cloudburst conditions.
  3. [NEEDS VALIDATION]: Official state-level village ward spatial shapefiles with full high-resolution polygon boundaries for all mountain states in North/North-East India.

Final Decision & Execution Summary

Final Recommendation

Proceed with building ResilienceGrid-Hills utilizing Approach 3 (Hybrid Physics-Informed ML + IoT Edge-Cloud Architecture). The solution directly satisfies all explicit requirements of PS SIH26192 while remaining technically achievable for a 4-6 student team within the deadline.

Recommended Stack

  • Frontend Dashboard: React.js, MapLibre GL JS, TailwindCSS
  • Mobile App: React Native, WatermelonDB / SQLite, SpatiaLite
  • Backend API: Python FastAPI, Celery, GDAL / PyProj
  • Database Engine: PostgreSQL + PostGIS, TimescaleDB, Redis
  • IoT Broker: EMQX MQTT Broker
  • AI/ML Core: NumPy, SciPy, XGBoost, Rasterio

Key Execution Metrics

  • Biggest Dependency: Acquisition of high-quality Digital Elevation Models (DEMs) and administrative village ward boundary shapefiles [INFERENCE].
  • Biggest Risk: Complete loss of cellular data transmission during extreme mountain storm events [KNOWN].
  • Biggest Technical Challenge: Coupling real-time point-source IoT soil moisture telemetry with spatial continuous slope stability equations in under 5 seconds execution time [INFERENCE].

First 5 Execution Actions

  1. Download SRTM 30m DEM GeoTIFF files and GADM village ward shapefiles for target pilot districts (e.g., Shimla, Himachal Pradesh) [INFERENCE].
  2. Set up local Docker environment running PostgreSQL 16 with PostGIS 3.4 and TimescaleDB [INFERENCE].
  3. Implement Python SCS-CN hydrological surface runoff and Infinite Slope Factor of Safety ($FS$) physics modules [INFERENCE].
  4. Build ESP32 IoT hardware circuit with ultrasonic water level sensor and capacitive soil moisture probe; configure MQTT publish script to EMQX broker [INFERENCE].
  5. Develop MapLibre GL JS web dashboard displaying dynamic color-coded ward hazard polygons and real-time sensor graphs [INFERENCE].

Validation Checklist Before Coding

  • Verify spatial overlay between DEM raster boundaries and village administrative ward polygons.
  • Validate mathematical correctness of SCS-CN runoff volume formulas against published hydrology handbook examples.
  • Test MQTT connection and JSON/Protobuf payload parsing between ESP32 hardware and EMQX broker over local network.
  • Verify CAP 1.2 XML output structure against standard W3C XML schema definition tools.

Quantitative Assessment

  • Buildability Score: 92/100 (Highly feasible for a dedicated 4-6 student team using open-source tools within the timeframe) [INFERENCE].
  • Overall Confidence Level: HIGH (Backed by verified research from IMD, GSI, C-DOT, and established hydrological physics) [INFERENCE].

Research Sources

  1. Flash Flood Guidance System - India Meteorological Department (IMD)

    • URL: https://mausam.imd.gov.in/imd_latest/contents/flash_flood.php [1.1]
    • Source Type: Official Government Portal (Ministry of Earth Sciences)
    • Supported Claim: Confirms operational SAsiaFFGS providing Flash Flood Threat and Risk guidance in India [1.1].
    • Reliability Assessment: Extremely High (Official Nodal Agency).
  2. India Meteorological Department Commissions Flash Flood Guidance Services for South Asia - PIB

    • URL: https://www.pib.gov.in/PressReleasePage.aspx?PRID=1667043 [1.2]
    • Source Type: Press Information Bureau, Government of India
    • Supported Claim: Details launch of SAsiaFFGS in October 2020 and need for enhanced rainfall/soil moisture observational networks [1.2].
    • Reliability Assessment: Extremely High (Official Government Release).
  3. Evaluating the performance of the Flash Flood Guidance System: A Case study from Himachal Pradesh - MAUSAM Journal

    • URL: https://mausamjournal.imd.gov.in/index.php/MAUSAM/article/view/7366 [1.4]
    • Source Type: Peer-Reviewed Academic Journal (IMD)
    • Supported Claim: Validates SAsiaFFGS performance during the extreme July 2023 Himachal Pradesh flash floods [1.4].
    • Reliability Assessment: Extremely High (Peer-Reviewed Scientific Literature).
  4. Early Warning System for Landslides - Press Information Bureau (PIB)

    • URL: https://www.pib.gov.in/pressreleasepage.aspx?prid=1777174 [2.1]
    • Source Type: Press Information Bureau, Government of India (Ministry of Mines)
    • Supported Claim: Confirms GSI development and pilot testing of prototype Landslide Early Warning System (LEWS) in Darjeeling and Nilgiris [2.1].
    • Reliability Assessment: Extremely High (Official Government Release).
  5. Cell Broadcast Alert System for Disaster Warnings - PIB Press Release

    • URL: https://www.pib.gov.in/PressReleasePage.aspx?PRID=2290380 [4.2]
    • Source Type: Press Information Bureau, Government of India (Ministry of Home Affairs)
    • Supported Claim: Details NDMA C-DOT Integrated Alert System utilizing CAP protocols and Cell Broadcast for geo-targeted public warnings [4.2].
    • Reliability Assessment: Extremely High (Official Government Release).
  6. SACHET National Disaster Alert Portal - NDMA

    • URL: https://sachet.ndma.gov.in/ [4.1]
    • Source Type: Official Government Portal (National Disaster Management Authority)
    • Supported Claim: Verifies pan-India CAP-based Integrated Alert System developed by C-DOT for multi-hazard geo-targeted alerting [4.1, 4.4].
    • Reliability Assessment: Extremely High (Official Nodal Portal).
02 / What our

DEVELOPERS SAY

" 30M+ Google Gemini tokens went into researching, analyzing, and understanding all 233 SIH problem statements to make them easier to explore and solve. "
Satyam Kumar
Satyam Kumar
CEO , Full Stack Developer
" The platform makes SIH problem statements much easier to understand. Having everything from the problem details to the procedure in one place. "
Rishabh Ranjan
Rishabh Ranjan
COO , Content Writer
" Oh, you got ads? Well, we need to make money too! But, you can use our platform to help you win SIH and take home the prize money. "
Himanshu Kumar
Himanshu Kumar
CMO , Product Reviewer
03 / Are You

READY TO
BUILD?

Get in touch if you need help bringing your ideas to life, or simply have an interesting idea you'd like to talk through. I'm always open to a conversation and exploring new possibilities together.