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: SIH26072

AIML based Nowcasting of thunderstorm and lightning using atmospheric observation including multiple radars, satellite, lightning and model data.

Description: AIML based Nowcasting of thunderstorm and lightning using atmospheric observation including multiple radars, satellite, lightning and model data.
Organization: Ministry of Earth Sciences (MoES)
Department: India Meteorological Department
Category: Software
Theme: Disaster Managementtd>
Youtube Link: Not provided
Dataset Link: Not provided
Contact info: Not provided

1. Executive Snapshot

Thunderstorms and lightning represent severe atmospheric hazards in India, causing over 2,000 casualties annually and causing extensive destruction to livestock, aviation, power grids, and agricultural infrastructure [KNOWN]. Traditional Numerical Weather Prediction (NWP) models require multi-hour computational cycles and fail to resolve the micro-scale convective initiation and rapid decay of localized thunderstorm cells within 0–3 hour lead times [RESEARCHED]. This dossier presents a production-grade, AI/ML-driven multimodal nowcasting architecture engineered specifically for the Ministry of Earth Sciences (MoES) - India Meteorological Department (IMD) under Problem Statement SIH26072 [PS]. The proposed solution fuses high-frequency Doppler Weather Radar (DWR) reflectivity grids, INSAT-3D/3DR/3DS geostationary satellite multispectral imagery, Indian Institute of Tropical Meteorology (IITM) Lightning Location Network (LLN) stroke events, and WRF atmospheric instability fields into a hybrid Deep Spatiotemporal Vision Transformer with Physics-Guided Advection [RESEARCHED]. The resulting platform delivers 1 km × 1 km hyper-local thunderstorm reflectivity (dBZ) and lightning stroke probability forecasts updated every 15 minutes, with an automated Common Alerting Protocol (CAP) alerting engine [INFERENCE].

Metadata Summary

Field Value Confidence
Problem Statement ID SIH26072 [PS]
Title AIML based Nowcasting of thunderstorm and lightning using atmospheric observation including multiple radars, satellite, lightning and model data. [PS]
Organization Ministry of Earth Sciences (MoES) [PS]
Department India Meteorological Department (IMD) [PS]
Category Software [PS]
Theme Disaster Management [PS]
Deadline 30 September 2026 [PS]
Ideas Counter 0/500 [PS]
Fundamental Objective Build a real-time, multi-modal AI/ML pipeline and interactive GIS decision support dashboard that ingest radar, satellite, lightning sensor, and NWP model data to predict thunderstorm cell tracking and lightning hazards 0–3 hours ahead at 1 km resolution with sub-minute inference latency. [INFERENCE]

2. Problem Deconstruction

The explicit problem statement provided by MoES/IMD requires an AI/ML-based nowcasting system utilizing four distinct atmospheric observation streams [PS]. Below is the complete atomic deconstruction of explicit requirements and derived technical implications.

Explicit Requirements

  • REQ-EX-01: AI/ML-Based Nowcasting System

    • Source Text: "AIML based Nowcasting of thunderstorm and lightning..." [PS]
    • Interpretation: The core forecasting engine must employ Artificial Intelligence / Machine Learning models rather than relying solely on linear optical flow extrapolation or classical rule-based heuristics [INFERENCE].
    • Implementation Implication: Development of a spatiotemporal deep learning model (e.g., ConvLSTM, U-Net, or Vision Transformer) trained on sequential atmospheric frames to output predictive raster maps up to 3 hours into the future [INFERENCE].
    • Confidence: [PS]
  • REQ-EX-02: Severe Weather Focus (Thunderstorm and Lightning)

    • Source Text: "...Nowcasting of thunderstorm and lightning..." [PS]
    • Interpretation: The model must predict both convective precipitation intensity (radar reflectivity / convective cloud initiation) and electric discharge events (cloud-to-ground and intra-cloud lightning strokes) [INFERENCE].
    • Implementation Implication: Dual-head or multi-task prediction outputs: 1) Radar Reflectivity ($Z \ge 35\text{ dBZ}$) forecast maps for storm tracking, and 2) Calibrated Lightning Stroke Density / Probability maps ($P(\text{Lightning}) \in [0,1]$) [INFERENCE].
    • Confidence: [PS]
  • REQ-EX-03: Multi-Radar Data Integration

    • Source Text: "...including multiple radars..." [PS]
    • Interpretation: The system must process and mosaic volumetric radar data from multiple Doppler Weather Radars (DWRs) operated by IMD across overlapping coverage zones [INFERENCE].
    • Implementation Implication: Ingestion and spatial alignment of polar coordinate DWR data (or gridded MAX reflectivity / Vertically Integrated Liquid (VIL) composites) from multiple regional radar stations into a unified Cartesian grid [INFERENCE].
    • Confidence: [PS]
  • REQ-EX-04: Satellite Data Integration

    • Source Text: "...satellite..." [PS]
    • Interpretation: Integration of geostationary earth observation satellite channels to detect cloud top growth, convective cloud initiation, and thermal infrared parameters [INFERENCE].
    • Implementation Implication: Ingestion of ISRO INSAT-3D / 3DR / 3DS satellite data via MOSDAC, specifically Thermal Infrared (TIR1: 10.8 µm), Water Vapor (WV: 6.8 µm), and derived Cloud Top Temperature (CTT) products [RESEARCHED].
    • Confidence: [PS]
  • REQ-EX-05: Ground Lightning Sensor Data Integration

    • Source Text: "...lightning..." [PS]
    • Interpretation: Ingestion of real-time ground-based lightning network observations to ground-truth electric activity and train prediction heads [INFERENCE].
    • Implementation Implication: Ingestion of time-stamped, geolocated lightning strike logs from the IITM Lightning Location Network (LLN) / Damini sensor grid [RESEARCHED]. Conversion of point stroke events into continuous spatial density rasters [INFERENCE].
    • Confidence: [PS]
  • REQ-EX-06: NWP Model Data Integration

    • Source Text: "...and model data." [PS]
    • Interpretation: Incorporation of background Numerical Weather Prediction (NWP) model outputs to provide large-scale thermodynamic and shear background context [INFERENCE].
    • Implementation Implication: Extraction of 3D atmospheric stability parameters (Convective Available Potential Energy - CAPE, Convective Inhibition - CIN, Vertical Wind Shear, Total Totals Index) from IMD Weather Research and Forecasting (WRF) or NCUM model runs [RESEARCHED].
    • Confidence: [PS]

Derived Requirements (Inferred)

  • REQ-IN-01: Real-Time Ingestion & Low-Latency Inference ([INFERENCE])

    • The nowcasting pipeline must complete data pre-processing, spatial alignment, AI inference, and alert generation within $< 3$ minutes of data arrival to provide operational utility within a 15–30 minute nowcast cycle [INFERENCE].
  • REQ-IN-02: Hyper-Local Spatial Resolution ([INFERENCE])

    • Output forecasts must be rendered on a geographic grid of $1\text{ km} \times 1\text{ km}$ resolution to provide actionable warnings at the block/tehsil/district level [INFERENCE].
  • REQ-IN-03: GIS Web & Mobile Decision Support Dashboard ([INFERENCE])

    • An interactive WebGIS dashboard with polygon warning overlays, station alerts, time-series player, and automated push notification logic is essential to demonstrate value to IMD meteorologists and disaster response authorities [INFERENCE].

3. Stakeholders & User Needs

Stakeholder Group Goal Current Pain Point System Need
IMD Operational Meteorologists Issue precise 0–3h nowcasts and district/station-level thunderstorm warnings. Manual inspection of disparate radar, satellite, and lightning windows; high cognitive load during rapid convective development [RESEARCHED]. Unified GIS interface fusing all observational feeds with AI-generated storm vectors and automated warning polygon suggestions [INFERENCE].
National / State Disaster Management Authorities (NDMA / SDMA) Evacuate open fields, halt outdoor operations, and deploy emergency teams before lightning strikes. Coarse district-wide alerts with multi-hour lag lead to warning fatigue and missed hyper-local severe strikes [KNOWN]. Automated CAP-compliant alerts triggered by 15-minute lead-time lightning probability thresholds at $1\text{ km}^2$ grid level [INFERENCE].
Farmers & Agricultural Workers Take shelter during open-field farming when a lightning storm approaches within 10–20 km. Lack of hyper-local, low-bandwidth real-time alerts in regional languages leading to high mortality rates [KNOWN]. Low-latency mobile notification / SMS alert with regional audio-visual warnings and 30-minute lead time [INFERENCE].
Aviation & Airport Authorities (AAI / ATC) Re-route flights and halt tarmac ground handling during severe convective activity and wind shear. Delayed radar-only updates fail to capture rapid cloud-top electrification and microburst initiation [KNOWN]. Automated runway cell velocity vectors and 0–2h reflectivity corridor extrapolation [INFERENCE].
Power Distribution Companies (DISCOMs) Isolate vulnerable transmission grids and dispatch repair crews for storm-damaged lines. Unpredictable lightning strikes trigger widespread grid trips without localized pre-warning [KNOWN]. Sub-station-level lightning risk heatmaps and strike count prediction [INFERENCE].

4. Requirements Traceability

Proposed System Feature Justifying Requirement Core Technical Implementation Confidence
Multi-Modal Feature Ingestion Engine REQ-EX-03, REQ-EX-04, REQ-EX-05, REQ-EX-06 Async Python pipeline using netCDF4, pyart, and rasterio to parse DWR NetCDF/BUFR, INSAT-3D HDF5, IITM LLN CSV, and WRF GRIB2 files [RESEARCHED]. [INFERENCE]
Spatio-Temporal Grid Resampling & Mosaicing REQ-EX-03, REQ-EX-04 Equal-area WGS84 EPSG:4326 grid interpolation engine normalizing multi-sensor resolutions to a standard $1\text{ km} \times 1\text{ km}$ spatial tensor [RESEARCHED]. [INFERENCE]
Cross-Attention Vision Transformer & U-Net Model REQ-EX-01, REQ-EX-02 Deep learning neural network ingesting past $T-4$ to $T_0$ multi-channel frames (Radar Z, INSAT CTT/WV, LLN Density, WRF CAPE) to forecast future $T_{+1}$ to $T_{+12}$ frames (0–3h) [RESEARCHED]. [INFERENCE]
Dual Prediction Heads (Reflectivity + Lightning) REQ-EX-02 Parallel output layers predicting 1) Max Reflectivity (dBZ) raster and 2) Calibrated Lightning Stroke Probability map $P(\text{Stroke} > 0) \in [0, 1]$ [INFERENCE]. [INFERENCE]
WebGIS Interactive Warning Dashboard REQ-IN-03 Mapbox GL JS / Leaflet frontend rendering time-series radar opacity overlays, satellite cloud motion, lightning stroke history, and CAP warning polygons [ASSUMPTION]. [INFERENCE]
Automated CAP Alerting & Push Gateway REQ-IN-01, REQ-IN-02 Rules engine triggering XML/JSON CAP alerts via WebSockets, Firebase Cloud Messaging (FCM), and SMS when cell reflectivity $> 40\text{ dBZ}$ and lightning probability $> 70%$ [RESEARCHED]. [INFERENCE]

5. Constraints & Environment Realities

Nowcasting systems in India operate under severe environmental, infrastructural, and observational constraints [KNOWN].

                        ┌─────────────────────────────────────────────────────────┐
                        │          INDIAN OPERATIONAL ENVIRONMENT REALITIES        │
                        └────────────────────────────┬────────────────────────────┘
                                                     │
         ┌───────────────────────┬───────────────────┴───────────────────┬───────────────────────┐
         │                       │                                       │                       │
┌────────┴────────┐     ┌────────┴────────┐                     ┌────────┴────────┐     ┌────────┴────────┐
│ RADAR COVERAGE  │     │ SATELLITE LATENCY│                     │ BANDWIDTH REALITY│     │ FIELD POWER     │
│ GAPS & TERRAIN  │     │ & RESOLUTION    │                     │ IN RURAL AREAS  │     │ & INFRASTRUCTURE│
└────────┬────────┘     └────────┬────────┘                     └────────┬────────┘     └────────┬────────┘
         │                       │                                       │                       │
 ┌───────┴────────┐      ┌───────┴────────┐                      ┌───────┴────────┐      ┌───────┴────────┐
 │• Non-uniform   │      │• 15-30 min scan│                      │• 2G/3G networks│      │• Frequent power│
 │  radar mesh    │      │  interval      │                      │  in farming    │      │  outages during│
 │• Terrain beam  │      │• 4 km spatial  │                      │  districts     │      │  thunderstorms │
 │  blockage in   │      │  resolution    │                      │• 100 KB max    │      │• Edgeware sync │
 │  Himalayas     │      │  (TIR channels)│                      │  payload limit │      │  resilience    │
 └────────────────┘      └────────────────┘                      └────────────────┘      └────────────────┘
  • Radar Mesh Coverage & Terrain Blockage: IMD operates $\sim 37$ DWR stations across India [RESEARCHED]. Coverage is dense along the east coast and major metros but sparse in parts of Central India, the Northeast, and mountainous Himalayan regions where radar beam blockage occurs [RESEARCHED]. The AI model must gracefully fallback to satellite and NWP inputs in radar-blind zones [INFERENCE].
  • Temporal & Spatial Disparities: Radar frames update every 10–15 minutes ($1\text{ km}$ resolution); INSAT-3D images update every 15–30 minutes ($4\text{ km}$ resolution for IR channels); IITM LLN updates continuously ($< 500\text{ m}$ stroke location accuracy); WRF model updates every 6 hours ($3\text{ km} - 9\text{ km}$ grid) [RESEARCHED]. Temporal alignment and spatial feature resampling are major processing bottlenecks [INFERENCE].
  • Field Connectivity & Low-Bandwidth Delivery: Rural disaster managers and agricultural workers frequently operate on congested 2G/3G mobile networks during extreme weather [KNOWN]. Heavy map tiles cannot be transmitted; the platform must deliver lightweight vector polygons ($< 50\text{ KB}$) or plain SMS alerts [INFERENCE].
  • Operational Latency Window: A nowcast for $T+30\text{ min}$ is useless if computation takes 20 minutes. Total end-to-end processing latency from data availability to prediction rendering must not exceed 180 seconds [INFERENCE].

6. Research Questions

To ensure technical rigor, the following critical research questions must be addressed during development:

  1. How to align multi-resolution spatial grids (1 km radar, 4 km satellite, 9 km WRF, continuous lightning points) without losing localized convective features?
    • Investigation Path: Evaluate bilinear, nearest-neighbor, and bicubic feature map interpolation versus learned spatial downsampling via strided 2D convolutional layers [RESEARCHED].
  2. What neural network loss function prevents temporal over-smoothing in multi-step reflectivity and lightning predictions?
    • Investigation Path: Compare MSE/MAE loss (which causes blurry, washed-out forecasts at $T+2\text{ hours}$) against Focal Loss combined with Structural Similarity (SSIM) and Perceptual Loss [RESEARCHED].
  3. How can the model effectively predict convective initiation (cell growth) in regions with zero initial radar reflectivity?
    • Investigation Path: Analyze the role of satellite Cloud Top Temperature (CTT) drop rates ($\Delta \text{CTT}/\Delta t$) and WRF Convective Available Potential Energy (CAPE) gradients as early indicators before precipitation particles grow large enough for radar detection [RESEARCHED].
  4. What is the operational availability and access protocol for real-time IMD DWR and IITM Damini data feeds for research/hackathon prototypes?
    • Investigation Path: Investigate MOSDAC FTP/HTTP endpoints, IMD Open Data Portal, and public AWS/NOAA radar datasets as realistic hackathon surrogates [RESEARCHED].

7. Data Requirements & Sources

Data Type Purpose Ideal Real-World Source Hackathon Substitute Access Method Availability Privacy Sensitivity Confidence
Doppler Weather Radar (DWR) Reflectivity Convective storm structure, intensity, and advection tracking. IMD Doppler Weather Radar Network (37+ stations, Max Z / VIL products) [RESEARCHED]. NOAA NEXRAD Level-II reflectivity grids or open radar datasets on AWS Open Data [RESEARCHED]. S3 / HTTP download / PyART NetCDF parsing [RESEARCHED]. Public archive available; Real-time API restricted [NEEDS VALIDATION]. Non-sensitive (Public weather) [RESEARCHED]
Geostationary Satellite Infrared / WV Cloud top cooling rates, convective cloud initiation outside radar coverage. ISRO/MOSDAC INSAT-3D / 3DR / 3DS Imager & Sounder (TIR1, TIR2, WV, CTT) [RESEARCHED]. GOES-16/17 Advanced Baseline Imager (ABI) or EUMETSAT MSG SEVIRI open netCDF archives [RESEARCHED]. MOSDAC API / FTP or AWS Open Data Cloud Storage [RESEARCHED]. Public archival access via MOSDAC registration [RESEARCHED]. Non-sensitive [RESEARCHED]
Ground Lightning Stroke Events Ground truth targets for lightning stroke density and flash probability heads. IITM Pune Lightning Location Network (83+ sensors) / Damini App backend [RESEARCHED]. ENGLN (Earth Networks) public samples, WWLLN (World Wide Lightning Location Network) or GOES Geostationary Lightning Mapper (GLM) [RESEARCHED]. CSV / GeoJSON point streams or gridded netCDF [RESEARCHED]. Sample datasets public; Live feed requires MoES MOU [NEEDS VALIDATION]. Non-sensitive [RESEARCHED]
NWP Atmospheric Thermodynamics Large-scale background instability (CAPE, CIN, Shear, Lifted Index). IMD Operational WRF (3 km) / NCUM model outputs [RESEARCHED]. NOAA Global Forecast System (GFS) 0.25° or ERA5 Reanalysis atmospheric variables [RESEARCHED]. NOMADS GRIB2 feed or Copernicus CDS API [RESEARCHED]. Publicly available free global access [KNOWN]. Non-sensitive [KNOWN]
Digital Elevation Model (DEM) Terrain slope/elevation impact on orographic convective uplift. SRTM 90m / ISRO CartoDEM [RESEARCHED]. AWS Terrain Tiles / USGS SRTM 30m / 90m [RESEARCHED]. Cloud-Optimized GeoTIFF (COG) via HTTP [KNOWN]. Publicly available free global access [KNOWN]. Non-sensitive [KNOWN]

8. Existing Solutions & Gap Analysis

                              EXISTING APPROACHES vs PROPOSED SOLUTION
┌───────────────────────────────┐ ┌───────────────────────────────┐ ┌───────────────────────────────┐
│     Extrapolation Models      │ │      Standard Physics NWP     │ │     PROPOSED HYBRID AI/ML     │
│     (Optical Flow / TITAN)    │ │        (WRF / NCUM)          │ │       MULTIMODAL FUSION       │
├───────────────────────────────┤ ├───────────────────────────────┤ ├───────────────────────────────┤
│ • Purely advective motion     │ │ • High physical accuracy      │ │ • Fuses Radar, INSAT, LLN &   │
│ • Zero cell growth/decay skill│ │ • 2-4 hour compute delay      │ │   WRF parameters              │
│ • Blurs quickly beyond 45 mins│ │ • Poor micro-scale resolution │ │ • 15-second GPU inference     │
│ • Blind to initial convection │ │ • High false alarm rate 0-1h  │ │ • Models growth & decay       │
└───────────────────────────────┘ └───────────────────────────────┘ └───────────────────────────────┘

1. Optical Flow & TITAN (Thunderstorm Identification, Tracking, Analysis, and Nowcasting)

  • Description: Classical radar extrapolation algorithms calculating optical flow velocity vectors from past reflectivity frames to advect storm cells forward in time [RESEARCHED].
  • Strengths: Computationally lightweight, low latency ($< 5\text{ seconds}$ execution), high accuracy for short lead times ($0-30\text{ minutes}$) [RESEARCHED].
  • Weaknesses: Assumes constant velocity and intensity; fails completely to model convective initiation (new storm formation), cell growth, or decay [RESEARCHED].
  • Relevance & Gap: Fails during rapid severe convective developments; cannot predict lightning initiation prior to radar echo formation [INFERENCE].
  1. High-Resolution WRF Numerical Weather Prediction (MoES/IMD)
  • Description: Physics-based hydrodynamical modeling simulating atmospheric dynamics at $3\text{ km} - 9\text{ km}$ resolution on supercomputing clusters (ARCA / ARUNICA) [RESEARCHED].
  • Strengths: Excellent multi-day atmospheric representation grounded in thermodynamic equations [KNOWN].
  • Weaknesses: High computational latency (2–4 hours per run cycle); spin-up errors impair short-term ($0-2\text{ hour}$) nowcasting accuracy [RESEARCHED].
  • Relevance & Gap: Too slow for real-time localized lightning early warnings; cannot process incoming 15-minute radar/satellite observations dynamically [INFERENCE].
  1. IITM Damini Mobile Application Architecture
  • Description: Mobile alerting system driven by IITM Pune's 83-sensor Lightning Location Network, issuing GPS radius-based warnings (20 km / 40 km) [RESEARCHED].
  • Strengths: Accurate real-time detection ($< 500\text{ m}$) of actual occurred lightning strikes across India [RESEARCHED].
  • Weaknesses: Primarily reactive (alerts after lightning strikes have begun occurring); limited predictive lead time ($< 15-20\text{ minutes}$ extrapolation); lacks radar/NWP multi-modal predictive fusion [RESEARCHED].
  • Relevance & Gap: Existing system alerts on current lightning; the proposed system builds a predictive 0–3h nowcasting layer ahead of cell electrification [INFERENCE].
  1. Google MetNet / MetNet-2 / Global MetNet
  • Description: Deep learning nowcasting neural networks developed by Google Research predicting precipitation up to 12 hours ahead using satellite and radar data [RESEARCHED].
  • Strengths: High skill score (CSI) across multi-hour horizons; uses axial self-attention to process large spatial contexts without over-smoothing [RESEARCHED].
  • Weaknesses: Designed for precipitation rate nowcasting; not fine-tuned for tropical extreme lightning electrification, regional Indian monsoon dynamics, or IITM ground sensor fusion [INFERENCE].
  • Relevance & Gap: Serves as architectural inspiration, but must be adapted for multi-modal Indian observations (INSAT-3D + DWR + IITM LLN) [INFERENCE].

9. Candidate Solution Approaches

                             SOLUTION APPROACH COMPARISON
┌─────────────────────────────────┬─────────────────────────────────┬─────────────────────────────────┐
│     APPROACH 1: CLASSICAL       │     APPROACH 2: SPATIOTEMPORAL   │    APPROACH 3: MULTIMODAL VIZ   │
│     FEATURE + XGBOOST           │     2D ConvLSTM / U-NET         │    TRANSFORMER + OPTICAL FLOW   │
├─────────────────────────────────┼─────────────────────────────────┼─────────────────────────────────┤
│ • Tabular grid features         │ • Image-to-image sequence model │ • Dual-branch hybrid arch       │
│ • Fast, interpretable           │ • Learns motion implicitly      │ • Optical flow advection core   │
│ • Ignores spatial context       │ • Blurs at longer lead times    │ • Cross-attention for physics   │
│ • Low hackathon complexity      │ • Moderate GPU overhead         │ • Sharp, physically grounded    │
└─────────────────────────────────┴─────────────────────────────────┴─────────────────────────────────┘

Approach 1: Classical Feature Engineering + XGBoost/LightGBM Grid Classifier

  • Mechanism: Discretize the geographic domain into a $0.01^\circ \times 0.01^\circ$ grid. For each grid cell, extract domain-engineered features from historical radar ($Z$, VIL), INSAT (CTT, $\Delta \text{CTT}/\Delta t$), LLN (flash counts in 10 km radius), and WRF (CAPE, CIN, Wind Shear). Train an XGBoost gradient boosted tree to classify whether $Z \ge 40\text{ dBZ}$ or Lightning $\ge 1\text{ stroke}$ occurs in the next 30/60/120 minutes [INFERENCE].
  • Problem Fit: Low-to-moderate; handles tabular non-linear interactions well but completely ignores multi-scale spatial cell shapes, advection velocity vectors, and neighborhood storm propagation [INFERENCE].
  • Complexity & Cost: Very low complexity; fast CPU training and sub-second inference [INFERENCE].
  • Hackathon vs Production Feasibility: High hackathon feasibility; moderate production skill score ceiling [INFERENCE].

Approach 2: End-to-End Spatiotemporal Deep Learning (ConvLSTM / 3D U-Net)

  • Mechanism: Stack continuous multi-channel observations (Radar Reflectivity, INSAT TIR1, INSAT WV, gridded LLN flash density) into a 5D spatio-temporal tensor $[B, T_\text{past}, C, H, W]$. Pass tensor through an encoder-decoder ConvLSTM or 3D U-Net architecture to generate future sequence frames $[B, T_\text{future}, C_\text{out}, H, W]$ up to $T+12$ steps (3 hours) [RESEARCHED].
  • Problem Fit: High; directly learns atmospheric cell motion, growth, and decay patterns directly from observed image sequences [RESEARCHED].
  • Complexity & Cost: High GPU computational requirements (NVIDIA RTX 4090 / A100 required for training); prone to spatial over-smoothing (loss of peak radar reflectivity and localized lightning spikes) at lead times $> 60\text{ minutes}$ [RESEARCHED].
  • Hackathon vs Production Feasibility: Feasible for hackathon with cropped regional grids ($256 \times 256$ pixels); production deployment requires multi-GPU inference clusters [INFERENCE].

Approach 3: Hybrid Physics-Aligned Vision Transformer + Optical Flow Advection (RECOMMENDED)

  • Mechanism: A dual-branch hybrid deep learning model:
    1. Advection Branch: Computes neural optical flow motion fields ($u, v$) from past radar and INSAT frames, explicitly advecting storm cell structures into future time steps to preserve sharp spatial gradients and prevent blurring [RESEARCHED].
    2. Physics & Electrification Branch: A Cross-Attention Vision Transformer (Swin-UNet) that ingests 3D atmospheric parameters (WRF CAPE, CIN, Wind Shear) and satellite sounder vertical profiles, learning a residual intensity modulation field ($\Delta Z, P_\text{lightning}$) [RESEARCHED].
    3. Fusion: The advected feature map is modulated by the residual intensity field to yield sharp, physically grounded reflectivity and lightning probability grids up to $T+3\text{ hours}$ [INFERENCE].
  • Problem Fit: Exceptional; combines the physical mass-conservation strength of optical flow (sharp cell boundaries) with deep learning's ability to model non-linear storm growth, decay, and electrification [RESEARCHED].
  • Complexity & Cost: High algorithmic design effort; moderate GPU training cost; fast inference ($< 1.5\text{ seconds}$ per frame cycle) [INFERENCE].
  • Hackathon vs Production Feasibility: Optimal for hackathon scoring due to state-of-the-art methodology, high visual accuracy, and strong physical interpretability [INFERENCE].

10. Recommended Approach & Why

Selection Statement

The Hybrid Physics-Aligned Vision Transformer + Optical Flow Advection (Approach 3) is selected as the winning architecture [INFERENCE].

Justification & Rejection of Alternatives

  • Why Approach 1 (XGBoost) was Rejected: XGBoost evaluates each spatial cell independently or with coarse spatial buffers. It fails to represent advective storm motion, spatial shear, and contiguous convective cell shapes, resulting in noisy, fragmented hazard maps [INFERENCE].
  • Why Pure Approach 2 (ConvLSTM) was Rejected: Standard ConvLSTM models minimize Mean Squared Error (MSE), which causes progressive loss of high-frequency spatial details. By $T+90\text{ minutes}$, predicted storm cells blur into diffuse, low-reflectivity blobs, severely underestimating localized severe lightning events [RESEARCHED].
  • Why Approach 3 Wins: Approach 3 explicitly decouples motion (where the storm is moving) from thermodynamic development (whether the storm is intensifying or dying). Optical flow handles motion without spatial blurring, while the Vision Transformer cross-attention module uses INSAT cloud-top cooling rates and WRF CAPE to predict lightning initiation and cell decay [RESEARCHED]. This approach achieves high Critical Success Index (CSI) scores while maintaining sharp operational warning boundaries [INFERENCE].

11. Technical Architecture

Layered Architecture Diagram

====================================================================================================
1. DATA INGESTION & ADAPTER LAYER (Async Ingestion Workers)
   ├─ IMD DWR Feed (NetCDF/BUFR) ──► PyART Parser ──────┐
   ├─ MOSDAC INSAT-3D/3DR (HDF5) ──► GDAL/SatPy Parser  ├──► Spatial Grid Resampler & Aligner
   ├─ IITM LLN Feed (CSV/WebSocket)► Point-to-Raster    │    (WGS84 EPSG:4326, 1 km Mesh)
   └─ Operational WRF (GRIB2) ────► xarray Extractor ──┘
====================================================================================================
2. FEATURE PREPROCESSING & TENSOR BUILDER
   ├─ Normalization & Missing Value Imputation (Spatial Kriging)
   ├─ Multi-Channel Stacking: [Radar Z, VIL, INSAT TIR1, WV, CTT, LLN Density, CAPE, Shear]
   └─ Rolling Spatiotemporal Memory Buffer (T-60m, T-45m, T-30m, T-15m, T0)
====================================================================================================
3. HYBRID AI/ML NOWCASTING INFERENCE ENGINE
   ├─ Branch A: Neural Optical Flow Advection Network (Predicts Motion Vectors u, v)
   ├─ Branch B: Cross-Attention Vision Transformer (Ingests WRF CAPE/Shear + INSAT CTT)
   ├─ Feature Fusion & Advective Warping Layer
   └─ Parallel Prediction Heads:
        ├─ Head 1: Reflectivity Forecast Grid [T+15m ... T+180m] (dBZ Raster)
        └─ Head 2: Lightning Stroke Probability Map [T+15m ... T+180m] (P in [0,1])
====================================================================================================
4. GEOSPATIAL POST-PROCESSING & WARNING ENGINE
   ├─ Polygon Extraction: Marching Squares Contour Algorithm (Z >= 40 dBZ, P_light >= 0.7)
   ├─ District / Station Spatial Overlay Intersect Engine (PostGIS)
   └─ Common Alerting Protocol (CAP v1.2) XML/JSON Alert Generator
====================================================================================================
5. PRESENTATION & DELIVERY LAYER
   ├─ FastAPI REST API & WebSocket Gateway
   ├─ Interactive WebGIS Dashboard (Mapbox GL JS / React / Deck.gl)
   ├─ Mobile FCM / WhatsApp / SMS Alert Notification Service
   └─ Low-Bandwidth GeoJSON Vector Tile Server
====================================================================================================

Detailed Data-Flow Narrative

  1. Ingestion & Parsing: Async Python background workers continuously poll incoming FTP/S3/WebSocket feeds every 5 minutes [INFERENCE]. DWR reflectivity volumes are parsed via PyART, INSAT-3D HDF5 multispectral bands via SatPy, IITM LLN point stroke logs via Pandas/Geopandas, and WRF GRIB2 files via xarray [RESEARCHED].
  2. Resampling & Tensor Stacking: Heterogeneous observation grids are resampled to a uniform $1\text{ km} \times 1\text{ km}$ regional grid over the geographic target domain using bilinear interpolation for continuous fields and spatial point-density accumulation for lightning strikes [RESEARCHED]. The aligned arrays are normalized and stacked into a 5D PyTorch tensor [INFERENCE].
  3. AI Inference Pipeline: The tensor is passed into the PyTorch Triton-optimized model container. The Advection branch calculates motion vectors and warps current reflectivity forward in time [RESEARCHED]. Simultaneously, the Cross-Attention ViT calculates growth/decay factors based on satellite cloud-top temperature drops and WRF atmospheric instability [RESEARCHED].
  4. Post-Processing & Polygon Generation: Predicted reflectivity and lightning probability grids for $T+15, T+30, \dots, T+180\text{ minutes}$ undergo vector contouring via Marching Squares [RESEARCHED]. Hazard polygons ($> 40\text{ dBZ}$ / $> 70%$ lightning risk) are intersected with administrative boundaries (districts, sub-districts, airport buffers) in PostGIS [INFERENCE].
  5. Alert Dissemination: If new hazard polygons intersect populated zones, the alert gateway formats a CAP-compliant XML payload and pushes real-time WebSocket notifications to the WebGIS dashboard and mobile notification services within $< 15\text{ seconds}$ of inference completion [INFERENCE].

12. Technology Stack

Layer Selected Technology Why Selected Alternative Considered Why Alternative Rejected
Frontend UI React + TypeScript + Mapbox GL JS / Deck.gl High-performance WebGL rendering of multi-layered spatial raster overlays and vector polygons at 60 FPS [KNOWN]. Leaflet.js Struggles with rendering high-density time-series animated raster tiles and 10,000+ lightning vector markers [KNOWN].
Backend API FastAPI (Python 3.11) + Uvicorn Native async I/O, auto-generated OpenAPI docs, seamless integration with PyTorch AI runtime [KNOWN]. Node.js / Express Lacks native Python scientific libraries (numpy, xarray, torch, pyart) required for raster data processing [KNOWN].
Geospatial Database PostgreSQL 16 + PostGIS 3.4 Industry-standard spatial indexing (GIST), fast polygon intersection queries, and native raster functions [KNOWN]. MongoDB / GeoJSON Inferior spatial joining performance and lacks specialized GIS projections and spatial functions [KNOWN].
AI/ML Framework PyTorch 2.3 + CUDA 12.1 + TorchScript Superior support for spatiotemporal Vision Transformers, dynamic tensor shapes, and TensorRT acceleration [KNOWN]. TensorFlow / Keras Slower innovation cycle for state-of-the-art vision models; complex multi-modal dynamic graph execution [KNOWN].
Geospatial Processing PyART + SatPy + Rasterio + xarray Native support for weather radar formats (NetCDF/BUFR), satellite HDF5 channels, and multi-dimensional arrays [RESEARCHED]. GDAL CLI Scripts Heavy shell wrappers add execution overhead and lack native Python memory buffers [INFERENCE].
Time-Series / Caching Redis 7.0 Ultra-fast in-memory caching for current T0 spatial tensors, active WebSocket sessions, and rate-limiting [KNOWN]. Memcached Lacks geospatial pub/sub capabilities and complex data structures (hashes, sorted sets) [KNOWN].
Task Queue / Message Broker Celery + RabbitMQ Reliable asynchronous execution of heavy file parsing, raster interpolation, and model inference jobs [KNOWN]. Apache Kafka Overkill for hackathon scale; introduces higher infrastructure setup complexity for student team [INFERENCE].
Containerization Docker + NVIDIA Container Toolkit Ensures exact GPU driver compatibility, library dependency isolation, and reproducible deployments [KNOWN]. Bare-metal execution High risk of "works on my machine" CUDA version mismatches during live hackathon judging [INFERENCE].

13. AI/ML Justification

                                  AI/ML MODEL ARCHITECTURE
┌─────────────────────────────────────────────────────────────────────────────────────────┐
│                                 MULTIMODAL INPUT TENSOR                                  │
│   [ Radar Z (t-4..t0) | INSAT TIR1/WV (t-4..t0) | LLN Density (t-4..t0) | WRF CAPE/Shear ]│
└────────────────────────────┬────────────────────────────────┬───────────────────────────┘
                             │                                │
                             ▼                                ▼
┌───────────────────────────────────────────┐   ┌───────────────────────────────────────────┐
│        NEURAL OPTICAL FLOW BRANCH         │   │   CROSS-ATTENTION VISION TRANSFORMER      │
│  • Computes motion field (u, v)           │   │  • Ingests thermodynamic background       │
│  • Performs backward advective warping    │   │  • Predicts cell growth/decay residual ΔZ │
│  • Preserves sharp reflectivity edges     │   │  • Predicts electrification potential     │
└────────────────────────────┬──────────────┘   └────────────────────────────┬──────────────┘
                             │                                │
                             └────────────────┬───────────────┘
                                              │
                                              ▼
                                ┌───────────────────────────┐
                                │   FEATURE FUSION MODULE   │
                                └─────────────┬─────────────┘
                                              │
                                              ▼
                             ┌─────────────────────────────────┐
                             │    DUAL PREDICTION HEADS        │
                             ├─────────────────────────────────┤
                             │ Head 1: Reflectivity Forecast   │
                             │ Head 2: Lightning Probability   │
                             └─────────────────────────────────┘

Component 1: Neural Optical Flow Advection Branch

  • Purpose: Track storm cell velocity vectors and extrapolate physical motion up to 3 hours ahead without spatial blurring [RESEARCHED].
  • Model Type: Deep Optical Flow Network (RAFT / PIV-Net based) [RESEARCHED].
  • Input: Past 4 consecutive frames ($T-60, T-45, T-30, T-0$) of Radar Reflectivity and INSAT TIR1 imagery [INFERENCE].
  • Output: Dense 2D motion vector field maps $[u(x,y), v(x,y)]$ representing pixel displacement per 15-minute interval [RESEARCHED].
  • Why AI over Rule/Classical? Classical Lucas-Kanade optical flow assumes brightness constancy and uniform motion, failing when storm cells deform, rotate, or split. Deep neural optical flow learns non-linear fluid dynamics and multi-scale atmospheric motion [RESEARCHED].

Component 2: Cross-Attention Vision Transformer (Growth, Decay & Electrification Branch)

  • Purpose: Predict where existing storm cells will intensify/decay and where new convective initiation and lightning strikes will emerge [RESEARCHED].
  • Model Type: Swin-Transformer Encoder-Decoder with Cross-Attention Fusion [RESEARCHED].
  • Input: Warped motion tensor fused with INSAT Cloud Top Temperature (CTT), Water Vapor channel, IITM Lightning stroke density, and WRF CAPE/CIN/Shear maps [INFERENCE].
  • Output: Residual reflectivity modulation matrix $\Delta Z(x,y,t)$ and Lightning Probability Matrix $P_\text{lightning}(x,y,t) \in [0,1]$ for $T+15$ to $T+180\text{ minutes}$ [INFERENCE].
  • Why AI over Rule/Classical? Lightning electrification involves complex microphysical interactions between ice crystals, graupel, and supercooled water droplets above the freezing level. Non-linear cross-attention captures complex correlations between CTT cooling rates ($<-50^\circ\text{C}$), high CAPE ($>2000\text{ J/kg}$), and electrical discharge initiation [RESEARCHED].

Model Evaluation Metrics

  • Critical Success Index (CSI): $\text{CSI} = \frac{\text{Hits}}{\text{Hits} + \text{False Alarms} + \text{Misses}}$ evaluated at thresholds $Z \ge 35\text{ dBZ}$ and Lightning Stroke Probability $\ge 0.5$ [RESEARCHED].
  • Fractions Skill Score (FSS): Evaluates spatial correctness across varying neighborhood scales ($1\text{ km}$ to $20\text{ km}$), preventing harsh spatial displacement penalties [RESEARCHED].
  • Probability of Detection (POD) & False Alarm Ratio (FAR): Target operational benchmark: $\text{POD} > 0.75$, $\text{FAR} < 0.25$ for 30-minute lead time [RESEARCHED].

Model Failure Modes & Human Oversight

  • Failure Mode 1 (False Convective Initiation): Unusually rapid satellite cloud top cooling in non-precipitating cirrus clouds could trigger false lightning warnings [INFERENCE].
  • Failure Mode 2 (Oographic Radar Blocking): In mountain valleys with beam blockage, radar inputs are missing, causing potential false negatives [INFERENCE].
  • Human Oversight Mechanism: The WebGIS dashboard includes an explicit "Forecaster Override" toggle. IMD meteorologists can review AI-generated confidence scores and manually adjust or suppress automatically generated CAP alert polygons prior to public broadcast [INFERENCE].

Explicit Non-AI Rule Enforcement

  • Rule: Simple distance buffering ($< 10\text{ km}$ from active strike) and linear thresholding ($Z \ge 45\text{ dBZ}$) are used for immediate $0-15\text{ minute}$ tactical alerts [INFERENCE]. AI is NOT used for immediate strike echoing, preserving sub-second alert response [INFERENCE].

14. Data Architecture & Offline/Low-Network Design

Spatial Database Schema (PostgreSQL / PostGIS)

-- Active Weather Radar Observations Grid Table
CREATE TABLE radar_observations (
    obs_id BIGSERIAL PRIMARY KEY,
    station_id VARCHAR(10) NOT NULL,
    observation_time TIMESTAMPTZ NOT NULL,
    max_reflectivity_raster RASTER NOT NULL,
    created_at TIMESTAMPTZ DEFAULT NOW()
);
CREATE INDEX idx_radar_obs_time ON radar_observations(observation_time);

-- Lightning Stroke Point Logs (IITM Network Ingestion)
CREATE TABLE lightning_strokes (
    stroke_id BIGSERIAL PRIMARY KEY,
    stroke_time TIMESTAMPTZ NOT NULL,
    location GEOMETRY(Point, 4326) NOT NULL,
    peak_current_ka REAL,
    stroke_type VARCHAR(5) CHECK (stroke_type IN ('CG', 'IC'))
);
CREATE INDEX idx_lightning_geom ON lightning_strokes USING GIST(location);
CREATE INDEX idx_lightning_time ON lightning_strokes(stroke_time);

-- AI Generated Forecast Polygons
CREATE TABLE forecast_hazard_polygons (
    polygon_id BIGSERIAL PRIMARY KEY,
    issue_time TIMESTAMPTZ NOT NULL,
    valid_time TIMESTAMPTZ NOT NULL,
    lead_time_minutes INT NOT NULL,
    hazard_type VARCHAR(20) CHECK (hazard_type IN ('THUNDERSTORM', 'LIGHTNING', 'HAIL')),
    risk_level VARCHAR(10) CHECK (risk_level IN ('YELLOW', 'ORANGE', 'RED')),
    geom GEOMETRY(Polygon, 4326) NOT NULL,
    confidence_score REAL CHECK (confidence_score BETWEEN 0 AND 1)
);
CREATE INDEX idx_hazard_poly_geom ON forecast_hazard_polygons USING GIST(geom);

Low-Network & Offline Architecture

  • Vector Tile Optimization: Instead of streaming heavy PNG raster tiles over cellular networks, the backend converts predicted hazard grids into ultra-compact Mapbox Vector Tiles (MVT / .pbf format) [KNOWN]. File size per tile is reduced by $> 85%$ ($< 15\text{ KB}$ per tile) [INFERENCE].
  • Progressive Web App (PWA) Offline Caching: The mobile/web dashboard uses Service Workers and IndexedDB to cache base geographic maps, district boundaries, and recent warning logs [KNOWN]. When connectivity drops, users can still view the last downloaded 3-hour forecast trend and local emergency guidelines [INFERENCE].
  • SMS Fallback Gateway: In regions with severe network degradation (2G/GPRS), the platform defaults to sending concise SMS text alerts containing district name, risk level, estimated time of arrival (ETA), and safety instructions [INFERENCE].

15. Security, Privacy & Governance

  • Sensitive Data Protection: Weather radar and satellite observations are public domain, but high-resolution military/defense installation radar locations or real-time troop movement zones may be sensitive [KNOWN]. The ingestion pipeline implements spatial masking algorithms over designated defense coordinates [INFERENCE].
  • Authentication & Role-Based Access Control (RBAC):
    • Public Users: Read-only access to generalized district warning polygons via CDN endpoints [INFERENCE].
    • IMD Meteorologists: Passwordless OAuth2 / TOTP authentication granting access to forecaster override controls, raw radar diagnostics, and manual CAP trigger panels [INFERENCE].
    • System Admin: Encrypted SSH/mTLS access to model pipeline containers and DB infrastructure [INFERENCE].
  • Regulatory Compliance & Disaster Governance: Official severe weather advisories in India are legally mandated to be issued by IMD under MoES guidelines [KNOWN]. To prevent panic caused by unvalidated automated warnings, public outputs must clearly state: "Experimental AI-Assisted Forecast - Powered by IMD/MoES Nowcasting Engine" [INFERENCE].
  • System Audit & Explainability: Every generated CAP alert log preserves the exact input tensor timestamp, model version identifier, generated confidence score, and forecaster approval status in an immutable PostgreSQL audit ledger [INFERENCE].

16. MVP Scope (Hackathon Build)

                                  SIH HACKATHON MVP SCOPE
┌──────────────────────────────────────────────────┐ ┌──────────────────────────────────────────────────┐
│              IN SCOPE (MUST BUILD)               │ │         DESCRIBED ONLY / OUT OF SCOPE            │
├──────────────────────────────────────────────────┤ ├──────────────────────────────────────────────────┤
│ • Regional Target Zone (e.g., East India Grid)   │ │ • Pan-India 37+ DWR live streaming hardware sync │
│ • 4-Channel Ingestion (Radar, INSAT, LLN, WRF)   │ │ • Direct CAP integration with telecom operators  │
│ • PyTorch Hybrid AI Nowcast Engine (T+0 to T+2h) │ │ • Hardware-level Doppler radar signal processing │
│ • Interactive WebGIS Dashboard (Mapbox GL JS)    │ │ • Retraining pipelines on multi-terabyte archives│
│ • CAP Alert Generator & WhatsApp/FCM Simulator   │ │ • 24/7 high-availability multi-region cloud cluster│
└──────────────────────────────────────────────────┘ └──────────────────────────────────────────────────┘

In Scope (Must Build for Demo)

  1. Target Demonstration Domain: Crop a representative high-convection region (e.g., Odisha / West Bengal / Gangetic Plain grid, $500\text{ km} \times 500\text{ km}$) at $1\text{ km}$ spatial resolution [ASSUMPTION].
  2. Multi-Modal Preprocessing Pipeline: Fully functional Python parsing pipeline ingesting historical MOSDAC INSAT-3D HDF5 files, open NEXRAD/IMD radar NetCDF samples, synthetic/historical IITM lightning CSV logs, and GFS/WRF GRIB2 atmospheric files [INFERENCE].
  3. Core AI Inference Engine: Trained PyTorch deep learning model executing real-time prediction ($< 5\text{ seconds}$) generating reflectivity (dBZ) and lightning stroke probability maps for 4 lead steps ($T+15, T+30, T+60, T+120\text{ minutes}$) [INFERENCE].
  4. Interactive WebGIS Forecaster Portal: React + Mapbox GL dashboard rendering time-series reflectivity overlays, lightning strike markers, playback controls, and click-to-query station diagnostics [INFERENCE].
  5. Automated CAP Alerting Engine: Real-time generation of valid CAP v1.2 XML warning payloads and push triggers sent via WebSocket to a mobile alerting simulator app [INFERENCE].

Described Only / Out of Scope (Production Phase)

  1. Live automated hardware streaming feeds from all 37+ IMD DWR radar towers across India [INFERENCE].
  2. Direct push integration into National Emergency Telecommunication Grid (SMS Cell Broadcast hardware gateways) [INFERENCE].
  3. Multi-terabyte historical archive ingestion and automated continuous active learning pipeline on cloud GPU clusters [INFERENCE].

17. Live Demo Simulation Plan

To deliver a compelling live demonstration during SIH judging without relying on live government network connections, the team will implement a transparent, realistic simulation pipeline [INFERENCE].

                        LIVE DEMO SIMULATION ARCHITECTURE
┌────────────────────────────────┐                 ┌────────────────────────────────┐
│   HISTORICAL WEATHER EVENT     │                 │   SIMULATED REAL-TIME INGEST   │
│   REPLAY ENGINE                │                 │   STREAMER                     │
│  • Kalboishakhi Storm Event    │                 │  • WebSocket push every 10s    │
│  • Pre-processed NetCDF/HDF5   │────────────────►│  • Simulates T0, T-15, T-30     │
│  • Real historical strikes     │                 │  • Passes frames to AI engine  │
└────────────────────────────────┘                 └───────────────┬────────────────┘
                                                                   │
                                                                   ▼
┌────────────────────────────────┐                 ┌────────────────────────────────┐
│   LIVE MOBILE & WEBGIS         │                 │   AI MODEL INFERENCE & CAP     │
│   ALERT RECEIVER               │                 │   GENERATOR                    │
│  • Displays live animated maps │◄────────────────│  • Runs PyTorch model live     │
│  • Triggers FCM push notification│                │  • Generates alert polygons    │
└────────────────────────────────┘                 └────────────────────────────────┘
  1. Dataset Selection (Historical Storm Event Replay): Select a historic severe thunderstorm event (e.g., a "Kalboishakhi" severe nor'wester storm over West Bengal / Odisha) [INFERENCE].
  2. Real-Time Data Streamer Engine: Build a Python background daemon (demo_streamer.py) that reads pre-processed historical radar, satellite, and lightning slices, pushing them into the Redis input queue every 10 seconds to simulate a live 15-minute operational ingestion loop [INFERENCE].
  3. Live AI Model Execution: The backend receives the simulated $T0$ frame, invokes the PyTorch model live on the host GPU, and returns real-time $T+15$ to $T+180\text{ minute}$ predictions within 2 seconds [INFERENCE].
  4. Interactive Forecaster Experience:
    • Judges can drag the temporal slider on the WebGIS interface to watch predicted storm cells advect, grow, and electrification zones emerge [INFERENCE].
    • Judges can click any district (e.g., Khordha / Bhubaneswar) to inspect predicted reflectivity curves and lightning probabilities [INFERENCE].
    • Trigger an automated CAP alert and display the received alert payload on a connected Android mobile device in real-time [INFERENCE].

18. Implementation Roadmap

Sized specifically against the final deadline of 30 September 2026 [PS]. Assuming a 4-week active development window leading up to final submission:

                                IMPLEMENTATION ROADMAP
┌──────────────────────┬──────────────────────┬──────────────────────┬──────────────────────┐
│ WEEK 1: DATA & BASE  │ WEEK 2: AI MODEL     │ WEEK 3: BACKEND &    │ WEEK 4: GIS DASHBOARD│
│ INGESTION PIPELINE   │ TRAINING & TUNING    │ GEOSPATIAL ENGINE    │ INTEGRATION & DEMO   │
├──────────────────────┼──────────────────────┼──────────────────────┼──────────────────────┤
│ • Parse NetCDF/HDF5  │ • Train PyTorch ViT  │ • PostGIS spatial    │ • Build Mapbox UI    │
│ • Spatial resampling │   advection model    │   polygon engine     │ • Mobile FCM alerts  │
│ • Grid alignment     │ • Evaluate CSI/FSS   │ • Fast-API endpoints │ • Live demo replay   │
│ • Synthetic dataset  │ • Optimize CUDA      │ • CAP XML generator  │ • Final testing &    │
│   preparation        │   inference latency  │ • Redis queue setup  │   documentation      │
└──────────────────────┴──────────────────────┴──────────────────────┴──────────────────────┘

Phase 1: Data Architecture & Preprocessing Pipeline (Week 1)

  • Milestone 1.1: Develop NetCDF (Radar), HDF5 (INSAT-3D), and GRIB2 (WRF) ingestion modules in Python [INFERENCE].
  • Milestone 1.2: Implement spatial grid resampler using rasterio and scipy.interpolate to project all inputs onto a unified $1\text{ km} \times 1\text{ km}$ grid [INFERENCE].
  • Milestone 1.3: Build $T-60\text{m}$ to $T0$ temporal frame buffer and dataset loaders for model training [INFERENCE].

Phase 2: AI Model Development & Evaluation (Week 2)

  • Milestone 2.1: Implement Hybrid Optical Flow + Cross-Attention Vision Transformer architecture in PyTorch [INFERENCE].
  • Milestone 2.2: Train model on historical storm sequences utilizing Focal Loss and SSIM loss functions [INFERENCE].
  • Milestone 2.3: Measure CSI, POD, FAR, and FSS skill scores across $15, 30, 60, 120\text{ minute}$ lead times [INFERENCE].

Phase 3: Backend Services, Database & GIS Engine (Week 3)

  • Milestone 3.1: Deploy PostgreSQL/PostGIS database and implement spatial indexing and vector contouring scripts [INFERENCE].
  • Milestone 3.2: Develop FastAPI REST endpoints and WebSocket channels for streaming predictions and alerts [INFERENCE].
  • Milestone 3.3: Integrate Common Alerting Protocol (CAP v1.2) XML payload generator [INFERENCE].

Phase 4: Frontend WebGIS, Mobile Integration & Demo Polish (Week 4 — Target: Sept 30, 2026)

  • Milestone 4.1: Build React + Mapbox GL JS interactive WebGIS forecaster dashboard with opacity sliders and time player [INFERENCE].
  • Milestone 4.2: Integrate Firebase Cloud Messaging (FCM) mobile alert push notifications [INFERENCE].
  • Milestone 4.3: Execute end-to-end simulation testing using the historical storm replay engine [INFERENCE].

19. Testing & Validation Plan

  • Functional Testing: Verify that multi-sensor inputs (Radar + INSAT + LLN + WRF) parse correctly without missing-value crashes or coordinate projection shifts [INFERENCE].
  • Performance Testing: Ensure the end-to-end execution pipeline (Ingestion $\rightarrow$ Tensor Build $\rightarrow$ AI Model Inference $\rightarrow$ Contour Generation $\rightarrow$ API Delivery) completes within $< 15\text{ seconds}$ on a single GPU node [INFERENCE].
  • AI Model Validation:
    • False Positive Testing: Evaluate model performance on non-precipitating cloudy days to ensure the false alarm ratio remains below $0.15$ [INFERENCE].
    • False Negative Testing: Test severe storm cases ($Z \ge 50\text{ dBZ}$) to verify that severe convective cells are not missed (POD > 0.80) [INFERENCE].
    • Lead Time Skill Decay: Verify that Fractions Skill Score (FSS) remains above operational usefulness ($> 0.5$) at 60-minute lead time [RESEARCHED].
  • Offline Resilience Testing: Simulate network failure during dashboard interaction; verify PWA offline mode correctly renders cached vector warning polygons and displays connectivity warning UI [INFERENCE].

20. Risk Register

Risk Event Likelihood Impact Severity Mitigation Strategy Confidence
Real-time IMD DWR API access unavailable during hackathon High High HIGH Use NOAA NEXRAD open radar grids or pre-downloaded MOSDAC/IMD historical NetCDF archives [INFERENCE]. [ASSUMPTION]
Temporal misalignment between INSAT (30m) and Radar (10m) High Medium MEDIUM Implement temporal linear feature interpolation and forward-propagation frame alignment in Redis buffer [INFERENCE]. [INFERENCE]
Deep learning model causes blurry forecasts at T+2 hours Medium High HIGH Decouple advective motion via Neural Optical Flow and apply Perceptual/Focal Loss instead of pure MSE [RESEARCHED]. [RESEARCHED]
GPU memory overflow during multi-channel tensor processing Medium Medium MEDIUM Crop target domain to $256 \times 256$ or $512 \times 512$ grid tiles and utilize FP16 mixed precision inference [INFERENCE]. [INFERENCE]
Public alert panic due to false positive lightning predictions Low High HIGH Implement forecaster approval gate and require confidence score threshold $> 0.75$ before CAP alert dispatch [INFERENCE]. [INFERENCE]

21. Cost & Scalability

Hackathon Prototype Infrastructure Cost

  • Cloud GPU Compute (RunPod / AWS g4dn.xlarge with NVIDIA T4/A10G): $\sim $0.50 - $1.00 / \text{hour}$ (Total hackathon training/testing expense: $<$50$) [KNOWN].
  • Database & Web Server: Local development machine or free-tier AWS/Render instance ($0) [INFERENCE].
  • Total Hackathon Estimate: Minimal cost suitable for a student budget ($< $50 / \text{approx } \text{₹}4,000$) [INFERENCE].

Production Deployment Infrastructure (MoES / IMD Scale)

  • Compute Cluster: On-premise deployment at IMD/MoES HPC centers (ARCA/ARUNICA supercomputing clusters) or dedicated cloud GPU cluster (4× NVIDIA A100 GPUs for multi-region inference) [RESEARCHED].
  • Storage Infrastructure: High-throughput NVMe storage for fast raster slicing and rolling 30-day radar/satellite archives [INFERENCE].
  • Scalability Bottlenecks & Solutions:
    • Bottleneck: Parsing 37+ simultaneous DWR radar streams during widespread monsoon activity [INFERENCE].
    • Solution: Kubernetes auto-scaling celery worker pods distributed regionally (North, South, East, West radar nodes) [INFERENCE].

22. Differentiation

                                KEY SYSTEM DIFFERENTIATORS
┌─────────────────────────────────┬─────────────────────────────────┬─────────────────────────────────┐
│     FEATURE FUSION ENGINE       │   HYBRID OPTICAL FLOW + ViT     │      CAP & LOW-BANDWIDTH        │
├─────────────────────────────────┼─────────────────────────────────┼─────────────────────────────────┤
│ Combines 4 distinct feeds       │ Eliminates spatial blurring     │ Generates standardized CAP      │
│ (Radar + Satellite + Lightning  │ maintaining crisp 1 km          │ v1.2 alerts & vector tiles      │
│ + NWP) into a single tensor     │ warning polygons up to 3 hours  │ for 2G network mobile delivery  │
└─────────────────────────────────┴─────────────────────────────────┴─────────────────────────────────┘
  1. True Multi-Modal Integration: Unlike existing single-source tools (radar-only optical flow or satellite-only models), this architecture explicitly fuses 4 distinct observational layers (DWR + INSAT-3D + IITM LLN + WRF) [INFERENCE].
  2. Physics-Aligned Neural Advection: Solves the primary technical flaw of standard deep learning models (spatial over-smoothing and blurring) by combining neural optical flow advection with cross-attention growth/decay transformers [RESEARCHED].
  3. Operational Readiness: Integrates native Common Alerting Protocol (CAP v1.2) alert formatting and Mapbox Vector Tile (MVT) low-bandwidth streaming, directly aligning with IMD and NDMA operational workflows [INFERENCE].

23. Future Scope

  1. Dual-Polarization Radar Variable Integration: Incorporate polarimetric variables ($Z_\text{DR}$, $K_\text{DP}$, $\rho_\text{HV}$) as DWR upgrades complete across India to enhance cloud microphysics representation [RESEARCHED].
  2. 3D Volumetric Convective Modeling: Extend 2D max-reflectivity grids into 3D height-resolved reflectivity columns (0–15 km altitude) for aviation turbulence and hail detection [INFERENCE].
  3. Edge Micro-Radar Ingestion: Enable local airport or municipal X-band micro-radar feeds to automatically register into the local nowcasting mesh [INFERENCE].

24. Assumptions & Open Items Log

Consolidated Assumptions [ASSUMPTION]

  1. [ASSUMPTION-01] Regional Target Domain: The hackathon MVP will target a $500\text{ km} \times 500\text{ km}$ regional grid over Eastern India (Odisha/West Bengal) rather than full national pan-India coverage to fit GPU hardware limits.
  2. [ASSUMPTION-02] Radar Data Format: Radar reflectivity files are assumed to be accessible in standard NetCDF4 or IRIS BUFR formats compatible with PyART.
  3. [ASSUMPTION-03] Demo Streaming: A historical replay streamer is accepted by judges as a valid demonstration mechanism for real-time atmospheric data flows.

Consolidated Items Needing Validation [NEEDS VALIDATION]

  1. [NEEDS VALIDATION-01] Direct Real-Time API Access: Availability of unauthenticated live REST/FTP endpoints for IMD DWR and IITM Damini feeds during the hackathon window.
  2. [NEEDS VALIDATION-02] Cloud Top Temperature Thresholds: Exact operational CTT drop rate thresholds ($\Delta\text{CTT}/\Delta t$) used by IMD meteorologists for pre-radar convective initiation validation.

Final Decision Summary

  • Recommended Solution: Hybrid Physics-Aligned Vision Transformer with Neural Optical Flow Advection (Approach 3) fusing DWR, INSAT-3D, IITM LLN, and WRF data [INFERENCE].
  • Recommended Stack: React + Mapbox GL JS (Frontend), FastAPI + Celery + PyTorch (Backend/AI), PostgreSQL + PostGIS + Redis (Data/Cache), Docker (Deployment) [INFERENCE].
  • Biggest Dependency: Access to multi-sensor atmospheric data files (or historical proxy NetCDF/HDF5 datasets) [INFERENCE].
  • Biggest Risk: Spatial over-smoothing and blurring in multi-step predictions, mitigated by neural optical flow warping [RESEARCHED].
  • Biggest Technical Challenge: Real-time spatial alignment and normalization of multi-resolution, heterogeneous observation grids within a $<3\text{ minute}$ operational window [INFERENCE].

First 5 Actions for the Student Team

  1. Download Sample Datasets: Obtain historical MOSDAC INSAT-3D HDF5 files and open radar NetCDF samples (NOAA NEXRAD or IMD sample archive) [RESEARCHED].
  2. Set Up Preprocessing Pipeline: Write Python script utilizing rasterio, satpy, and pyart to project satellite and radar rasters onto a standard $1\text{ km}$ WGS84 grid [INFERENCE].
  3. Build Baseline Neural Optical Flow: Implement a baseline optical flow script to extrapolate reflectivity frames 60 minutes ahead and calculate initial CSI scores [INFERENCE].
  4. Develop Mapbox Dashboard Skeleton: Build a React application rendering animated raster opacity layers and vector polygon overlays [INFERENCE].
  5. Implement Historical Streamer: Create demo_streamer.py to push sequential pre-processed frames into Redis for live demo testing [INFERENCE].

Final Metrics

  • Validation Before Coding: Verify spatial grid projections, verify PyTorch CUDA installation, test PyART NetCDF loading [INFERENCE].
  • Buildability Score: 88/100 (Highly feasible for a skilled 4–6 student team utilizing open Python geospatial and deep learning libraries) [INFERENCE].
  • Overall Plan Confidence: High [INFERENCE].

Research Sources

  1. India Meteorological Department (IMD) - Satellite & Radar Nowcasting Systems
    • URL: https://mausam.imd.gov.in [RESEARCHED]
    • Source Type: Official Government Portal
    • Supported Claim: IMD operates Doppler Weather Radars, INSAT satellites, and issues 3-hourly/district nowcasts and short-term warnings [PS, KNOWN].
    • Reliability: High (Primary Official Source)
  2. Meteorological & Oceanographic Satellite Data Archival Centre (MOSDAC / ISRO)
    • URL: https://www.mosdac.gov.in [RESEARCHED]
    • Source Type: Official Government Data Center
    • Supported Claim: MOSDAC archives and disseminates INSAT-3D/3DR/3DS multispectral satellite products (TIR, WV, CTT) in HDF5 format [RESEARCHED].
    • Reliability: High (Primary Official Source)
  3. Indian Institute of Tropical Meteorology (IITM) - Lightning Location Network & Damini App
    • URL: https://www.tropmet.res.in [RESEARCHED]
    • Source Type: Autonomous Government Research Institute
    • Supported Claim: IITM Pune operates an 83-sensor Lightning Location Network across India providing real-time strike geolocation with $< 500\text{ m}$ accuracy [RESEARCHED].
    • Reliability: High (Primary Official Source)
  4. Press Information Bureau (PIB) - Death due to Lightning Strikes & Damini Infrastructure
    • URL: https://www.pib.gov.in/PressReleaseIframePage.aspx?PRID=1813993 [RESEARCHED]
    • Source Type: Official Government Press Release
    • Supported Claim: IITM lightning network output is shared with IMD and state governments for nowcasting and feeds the Damini mobile app [RESEARCHED].
    • Reliability: High (Official Government Communication)
  5. Google Research - MetNet-2: Deep Learning for 12-Hour Precipitation Forecasting
  6. ResearchGate / IEEE - Deep Learning Approaches for Lightning Nowcasting
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.