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

Student Innovation-There is a need to design drones and robots that can solve some of the pressing challenges of India such as handling medical emergencies, search and rescue operations, etc.

Description: Student Innovation-There is a need to design drones and robots that can solve some of the pressing challenges of India such as handling medical emergencies, search and rescue operations, etc.
Organization: AICTE
Department: AICTE, MIC-Student Innovation
Category: Software
Theme: Robotics and Dronestd>
Youtube Link: Not provided
Dataset Link: Not provided
Contact info: Not provided

1. Executive Snapshot

This research and architectural dossier establishes an end-to-end blueprint for "GarudaResQ"—a Software-First Autonomous Drone & Robot Rescue Orchestration Platform [INFERENCE] designed to address India's urgent medical emergency logistics and disaster Search & Rescue (SAR) challenges [PS]. While the problem statement highlights hardware deployment in complex Indian topographies [PS], the competition entry is officially categorized under Software [PS]. GarudaResQ bridges this gap by delivering a unified, edge-resilient Mission Control & Swarm Dispatch System [INFERENCE] capable of interfacing directly with open-source autopilots (PX4/ArduPilot via MAVLink and ROS2) [KNOWN] while executing full Software-In-The-Loop (SITL) simulations [KNOWN] for live judging. The platform integrates autonomous lawnmower/spiral search path planning [KNOWN], edge-based AI survivor detection using thermal/optical feeds [RESEARCHED], payload-drop stability monitoring for emergency medical delivery [RESEARCHED], and an offline-first mesh synchronization engine for zero-connectivity disaster zones [INFERENCE]. Operating strictly within the Indian regulatory framework mandated by the DGCA Drone Rules 2021 and DigitalSky airspace maps [RESEARCHED], this document provides a complete technical design, data schema, risk assessment, and hackathon roadmap targeted for completion before 30 September 2026 [PS].

Metadata Summary

Metadata Field Details
Problem Statement ID SIH26201 [PS]
Title Student Innovation - Drones and Robots for Medical Emergencies and Search & Rescue [PS]
Organization All India Council for Technical Education (AICTE) [PS]
Department AICTE, MIC-Student Innovation [PS]
Category Software [PS]
Theme Robotics and Drones [PS]
Submission Deadline 30 September 2026 [PS]
Ideas Counter 0 / 500 [PS]
Fundamental Objective Build a tactical, offline-resilient GCS software platform that orchestrates autonomous aerial/ground robotic swarms for rapid medical payload delivery and AI-driven thermal survivor detection under DGCA DigitalSky compliance [INFERENCE].

2. Problem Deconstruction

The explicit problem statement provided in the source JSON reads: "Student Innovation-There is a need to design drones and robots that can solve some of the pressing challenges of India such as handling medical emergencies, search and rescue operations, etc." [PS]

To make this actionable for a software-track student hackathon team, the requirement is deconstructed into atomic functional units, explicitly distinguishing between stated requirements and derived operational implications:

  • REQ-01: Core Domain Scope - Medical Emergency Handling
    • Source Text: "...handling medical emergencies..." [PS]
    • Interpretation: The platform must support rapid dispatch, flight pathing, and drop-zone coordination for life-saving payloads (e.g., blood bags, anti-venom, defibrillators, vaccines, diagnostic samples) [INFERENCE].
    • Implementation Implication: Payload weight/balance monitoring, telemetry tracking of thermal enclosure conditions, and automated pin-point landing/drop path planning [INFERENCE].
    • Confidence: [PS]
  • REQ-02: Core Domain Scope - Search and Rescue (SAR) Operations
    • Source Text: "...search and rescue operations..." [PS]
    • Interpretation: The system must enable autonomous aerial/ground scouting over large, hazardous, or inaccessible areas to locate missing or stranded individuals during floods, earthquakes, or landslides [INFERENCE].
    • Implementation Implication: Implementation of automated coverage algorithms (lawnmower, expanding square, perimeter search), multi-spectral video ingestion (thermal + RGB), and edge AI object detection for human detection [INFERENCE].
    • Confidence: [PS]
  • REQ-03: Multi-Agent Heterogeneous Robotics (Drones and Robots)
    • Source Text: "...design drones and robots..." [PS]
    • Interpretation: The control architecture must not be limited to single quadcopters; it must manage heterogeneous fleets comprising aerial UAVs (scout and heavy-lift cargo) and Unmanned Ground Vehicles (UGVs) / ground robots for debris navigation [INFERENCE].
    • Implementation Implication: Multi-vehicle telemetry stream processing, uniform message definitions using MAVLink micro-services and ROS2 nodes, and dynamic task allocation across ground and air agents [INFERENCE].
    • Confidence: [PS]
  • REQ-04: Software Track Execution (Category Alignment)
    • Source Text: "category": "Software" [PS]
    • Interpretation: Because physical custom hardware fabrication is not strictly required or evaluated in the software category, the system must deliver full Ground Control Station (GCS) software, mission routing algorithms, edge vision pipelines, and high-fidelity SITL simulation environments [INFERENCE].
    • Implementation Implication: Provisioning PX4/Gazebo multi-vehicle SITL containerized environments that allow judges to execute real-time automated rescue missions [INFERENCE].
    • Confidence: [INFERENCE]
  • REQ-05: Contextual Adaptation to Indian Operational Realities
    • Source Text: "...pressing challenges of India..." [PS]
    • Interpretation: System must accommodate Indian geographical diversity (Himalayan cold/altitude, Northeast jungle canopy, urban slum collapse, monsoon flooding), poor cellular infrastructure during disasters, and DGCA DigitalSky regulatory compliance [RESEARCHED].
    • Implementation Implication: Offline mesh networking capabilities, lightweight low-bandwidth data protocols, and airspace boundary parsing (Green/Yellow/Red zones) [INFERENCE].
    • Confidence: [INFERENCE]

3. Stakeholders & User Needs

Stakeholder Group Primary Goal Current Pain Point Core System Need
NDRF / SDRF Disaster Response Commanders [KNOWN] Rapidly survey collapse/flood zones and locate survivors within the critical "golden hour" [KNOWN]. Ground teams are delayed by blocked roads, debris, flooded terrain, and lack of real-time situational maps [RESEARCHED]. Unified GIS Dashboard displaying real-time SAR heatmaps, survivor GPS coordinates, and autonomous multi-drone coverage progress [INFERENCE].
Emergency Medical Response Officers (108 ERSO / PHC Doctors) [RESEARCHED] Transport urgent medical supplies (anti-venom, blood, organs, vaccines) to cut-off rural or disaster-hit primary health centres [RESEARCHED]. Ambulances locked in traffic or delayed by damaged roads; sample/blood degradation in transit [RESEARCHED]. One-click medical dispatch workflow with live thermal/payload temperature telemetry and automated safe-drop zone selection [INFERENCE].
Field Drone Pilots & Mobile Operations Operators [KNOWN] Safely fly search-and-rescue sorties under stress without risking vehicle collisions or airspace violations [KNOWN]. Manual flight control of multiple drones is prone to pilot fatigue, loss of signal, and airspace violations [INFERENCE]. Autonomous waypoint generation, one-key auto-takeoff/return-to-launch (RTL), and dynamic obstacle/no-fly zone avoidance [INFERENCE].
Ground Search Units (First Responders on Foot) [KNOWN] Navigate directly to trapped victims with necessary medical aid [KNOWN]. Inefficient manual grid searches in dangerous environments without precise coordinates [INFERENCE]. Mobile companion app with offline tactical map caching victim location pins and optimal ground walk paths [INFERENCE].
District Disaster Management Authorities (DDMA) [RESEARCHED] Ensure all disaster operations strictly comply with national civil aviation laws and airspace safety [RESEARCHED]. Risk of unauthorized flights near military zones, airports, or hazardous power lines during relief operations [RESEARCHED]. Automated DGCA DigitalSky Airspace map integration (Green/Yellow/Red zone verification) and flight log auditing [INFERENCE].

4. Requirements Traceability

Feature / Module Addressed Requirement Technical Justification
Autonomous Lawnmower & Spiral Path Planner REQ-02 (SAR Operations) [PS] Guarantees 100% spatial coverage over search polygons without manual pilot intervention [KNOWN].
Edge YOLOv8/v10 Thermal & RGB Detection Engine REQ-02 (SAR) & REQ-05 (Indian Realities) [PS] Processes video streams at 30+ FPS directly on companion computers (Jetson/Pi 5) to identify human thermal signatures through canopy or smoke [RESEARCHED].
Medical Payload Drop & Thermal Monitoring Module REQ-01 (Medical Emergencies) [PS] Tracks real-time payload container temperature and actuates Servo release mechanisms upon reaching verified drop coordinates [RESEARCHED].
Heterogeneous Multi-Agent ROS2 Bridge (PX4/ArduPilot) REQ-03 (Drones & Robots) [PS] Enables simultaneous telemetry ingestion, state estimation, and command translation for both aerial quadcopters and ground UGVs [KNOWN].
PX4 / Gazebo SITL Multi-Vehicle Simulator REQ-04 (Software Track Execution) [PS] Allows full end-to-end evaluation and live demonstration of swarm SAR and medical dispatch without needing live physical airspaces during judging [INFERENCE].
Off-Grid LoRa / Wi-Fi Mesh Peer-to-Peer Sync REQ-05 (Indian Realities) [PS] Ensures tactical telemetry and victim location data are synced between field workers and command tents when 4G/5G towers are down [INFERENCE].
DigitalSky Airspace Geo-Fence Checker REQ-05 (Indian Realities & DGCA Rules) [PS] Parses official Indian airspace XML/JSON geo-json data to restrict flight paths within permitted Green zones or warn on Yellow/Red zone intersections [RESEARCHED].

5. Constraints & Environment Realities

Developing drone and robotic rescue software for Indian field conditions introduces distinct operational realities that dictate system architecture:

+-----------------------------------------------------------------------------------+
|                            INDIAN FIELD CONSTRAINTS                               |
+-----------------------------------------------------------------------------------+
|  Connectivity : 80% cellular outage in disaster zones (floods, landslides, quakes)|
|  Geography    : High-altitude low air density (Himalayas) vs. Dense jungle canopy |
|  Battery Life : Micro-drones restricted to 20-30 min flight times                 |
|  Regulations  : DGCA Drone Rules 2021, DigitalSky Green/Yellow/Red airspace limits |
|  User Base    : Non-technical field rescue workers requiring simple touch UI      |
+-----------------------------------------------------------------------------------+
  1. Network Degradation & Cellular Breakdown: In disaster scenarios (e.g., Assam floods, Uttarakhand landslides), cellular infrastructure (4G/5G) is frequently destroyed [KNOWN]. The system cannot rely on cloud-hosted backends for real-time flight control or image processing [INFERENCE]. Edge compute and off-grid radio mesh are mandatory [INFERENCE].
  2. Topographical & Weather Diversity: High-altitude deployment (e.g., Lahaul-Spiti, Himachal Pradesh) causes thinner air and up to 30% reduction in battery performance and rotor lift [RESEARCHED]. Dense forest canopies (Northeast India) obstruct standard GPS signals [RESEARCHED]. The software must handle GPS-degraded positioning fallback and compute energy-aware battery return margins [INFERENCE].
  3. Regulatory Compliance (DGCA & DigitalSky): Indian airspace is governed by the Drone Rules 2021 [RESEARCHED]. Drones under 500kg must comply with DigitalSky airspace classifications [RESEARCHED]:
    • Green Zone: Up to 400 ft AGL, no prior permission required [RESEARCHED].
    • Yellow Zone: Controlled airspace requiring Air Traffic Control (ATC) approval [RESEARCHED].
    • Red Zone: Strictly prohibited (near international borders, airports, military installations) [RESEARCHED].
    • The software must automatically overlay DigitalSky spatial layers and enforce No-Fly-Zone (NFZ) hard limits [INFERENCE].
  4. Hardware & Power Limitations: Tactical field units run on battery power. Ground Control Station laptops and drone edge computers (Nvidia Jetson Orin Nano / Raspberry Pi 5) have finite compute and battery budgets [KNOWN]. Deep learning vision pipelines must be quantized (TensorRT/ONNX INT8) to consume under 15W [INFERENCE].
  5. User Digital Literacy: Field rescue personnel under extreme pressure require minimal manual inputs—single-tap mission confirmation, clear visual hazard warnings, and automated alert generation [INFERENCE].

6. Research Questions

To ensure technical viability, the student team must investigate the following core research questions:

  1. Algorithmic Search Efficiency: How does a spiral search path compare to a lawnmower grid search in minimizing search completion time over uneven mountainous terrain when constrained by a 25-minute battery limit? [INFERENCE]
  2. Edge Vision Optimization: What is the inference latency and mAP (mean Average Precision) of YOLOv8-Nano vs. YOLOv10-Nano quantized to TensorRT on an Nvidia Jetson Orin Nano when processing 1080p thermal infrared feeds at 30 FPS? [RESEARCHED]
  3. Offline Mesh Telemetry: What is the maximum throughput and packet drop rate of LoRa (865-867 MHz Indian ISM band) vs. Wi-Fi Direct mesh protocols when transmitting compressed MAVLink telemetry and victim coordinates across 2 km non-line-of-sight (NLOS) forest terrain? [RESEARCHED]
  4. DigitalSky Integration: How can the platform dynamically parse DGCA airspace GeoJSON boundaries offline to calculate 3D geometric intersections with planned flight paths? [RESEARCHED]
  5. UGV-UAV Heterogeneous Hand-off: What protocol best handles task switching where an aerial drone discovers a trapped human and dispatches a ground UGV to navigate debris and deliver first-aid kits? [INFERENCE]

7. Data Requirements & Sources

Data Type Operational Purpose Ideal Real-World Source Hackathon Substitute Access Method Availability Privacy Sensitivity Confidence
Airspace Boundaries & Geo-Fences Prevent illegal entry into airport/military zones. DGCA DigitalSky Portal [RESEARCHED] Synthetic GeoJSON matching Indian Green/Yellow/Red zone schemas. REST API / Static File Ingestion Static files available publicly; API restricted [RESEARCHED] Public domain regulatory data [KNOWN] [RESEARCHED]
High-Resolution Elevation Models (DEM) Terrain-following flight path generation in valleys/mountains. ISRO Bhuvan / USGS SRTM 30m DEM [RESEARCHED] NASA SRTM 30m open raster tile datasets. HTTP Download / GeoTIFF parsing Fully open access [KNOWN] Non-sensitive geospatial data [KNOWN] [KNOWN]
Thermal & RGB Human Detection Imagery Training/testing AI models for survivor detection. Live FLIR Lepton / Boson sensor streams [KNOWN] OpenDatasets (FLIR Thermal Dataset, SARTAG SAR UAV Dataset) [RESEARCHED] Kaggle / Roboflow Direct Download Public academic datasets available [RESEARCHED] Anonymized thermal profiles; low privacy risk [INFERENCE] [RESEARCHED]
Vehicle Flight Telemetry Real-time position, attitude, battery, and GPS health. Live Pixhawk 4 / PX4 MAVLink output [KNOWN] PX4 SITL MAVLink UDP stream over local socket. MAVSDK-Python / MAVROS node Freely generated in simulation [KNOWN] Operational security only [INFERENCE] [KNOWN]
Medical Payload Health Data Ensure temperature-sensitive medicine (blood/vaccines) remains viable. External IoT sensor payload bay (DS18B20 temp sensor) [KNOWN] Simulated MQTT JSON payload stream (temp_c: 4.2, lock_status: SECURE). Serial / MQTT topic Synthetically scriptable [INFERENCE] Non-personal IoT data [INFERENCE] [ASSUMPTION]

8. Existing Solutions & Gap Analysis

To justify GarudaResQ, existing commercial, open-source, and government solutions were evaluated:

+-------------------------------------------------------------------------------------+
|                             EXISTING SOLUTIONS & GAPS                               |
+-------------------------------------------------------------------------------------+
| QGroundControl / Mission Planner : Great single-vehicle fly tool; NO edge AI or SAR |
| ICMR i-DRONE Platform           : Great point-to-point medical flight; NO SAR/Swarm |
| Zipline / Commercial Logistics  : Closed proprietary ecosystem; fixed hub dependency|
| ROS2 Academic Swarm Frameworks  : Highly complex; NO user-friendly tactical UI      |
+-------------------------------------------------------------------------------------+

Comparative Analysis

  1. QGroundControl / Mission Planner (Standard Open-Source GCS)
    • Description: Standard open-source ground station software for MAVLink-based drones [KNOWN].
    • Strengths: Robust flight telemetry, mission planning, parameter configuration [KNOWN].
    • Weaknesses: Designed for single-vehicle manual setup; lacks automated multi-agent SAR path generators, edge AI object detection integration, and tactical off-grid team synchronization [INFERENCE].
    • Gap: No native disaster SAR workflows or thermal AI overlay [INFERENCE].
    • Confidence: [KNOWN]
  2. ICMR i-DRONE Platform (Indian Medical Supply Logistics)
    • Description: Indian Council of Medical Research initiative for vaccine and blood delivery in Northeast India and Himachal Pradesh [RESEARCHED].
    • Strengths: Proven BVLOS medical delivery in extreme terrain (Keylong, Manipur) [RESEARCHED].
    • Weaknesses: Specialized purely for fixed point-to-point medical transport; cannot execute search-and-rescue grid operations or deploy ground robots [RESEARCHED].
    • Gap: Lacks real-time search and rescue detection engines and heterogeneous vehicle coordination [INFERENCE].
    • Confidence: [RESEARCHED]
  3. Academic ROS2 Swarm Frameworks (e.g., Aeras, UAVros)
    • Description: Open-source academic ROS2 packages for multi-UAV SAR and mapping [RESEARCHED].
    • Strengths: High algorithmic fidelity for SLAM and swarm pathing [RESEARCHED].
    • Weaknesses: Require heavy command-line setup; lack an intuitive tactical GUI for non-technical first responders; no built-in DGCA airspace compliance check [INFERENCE].
    • Gap: Poor usability for field operations and zero regulatory integration [INFERENCE].
    • Confidence: [RESEARCHED]

9. Candidate Solution Approaches

When designing a software system to satisfy SIH26201, three candidate technical architectures were evaluated:

Approach Comparison Matrix

Evaluation Criteria Approach 1: Pure Cloud Web GCS (SaaS) Approach 2: Monolithic Desktop ROS2 GCS Approach 3: Hybrid Edge-Swarm Node + Tactical Mesh GCS + Cloud Command (RECOMMENDED)
System Mechanism Web browser connects via 4G/5G to cloud server; cloud relays MAVLink commands and runs cloud AI vision. Single heavy C++ Qt/ROS2 desktop app running directly on a field laptop. Local edge compute on drone companion computer (AI detection); local P2P Web/Electron GCS on field laptop; async cloud sync when online.
Problem Fit Low [INFERENCE]. Fails in off-grid disaster zones due to connectivity reliance [INFERENCE]. Medium [INFERENCE]. Strong offline capability, but rigid UI and poor multi-device field sharing [INFERENCE]. High [INFERENCE]. Perfectly matches Indian off-grid field conditions while maintaining modern UI and edge AI performance [INFERENCE].
Accuracy / Latency High compute potential, but unviable due to 200ms-2s cloud round-trip video latency [INFERENCE]. Zero network latency, but bound to laptop GPU capabilities [INFERENCE]. Sub-30ms local edge video inference; real-time low-bandwidth MAVLink local mesh transmission [INFERENCE].
Data Requirements Continuous high-speed broadband connection required [INFERENCE]. Local map tiles and offline spatial files [INFERENCE]. Local offline vector map tiles, lightweight MAVLink packets over LoRa/Wi-Fi Direct [INFERENCE].
Complexity Low system integration, high network reliability burden [INFERENCE]. High C++/ROS2 native compilation complexity [INFERENCE]. Moderate: Modular split between Web UI (React/TypeScript), Node/Python backend gateway, and C++/Python ROS2 edge nodes [INFERENCE].
Cost High recurring cloud infrastructure fees [INFERENCE]. Zero cloud fees; requires high-end field laptop [INFERENCE]. Low cost; standard laptop + low-cost edge companion hardware (Raspberry Pi / Jetson) [INFERENCE].
Hackathon Feasibility High [INFERENCE]. Low [INFERENCE]. Difficult to build polish and present in short window. Very High [INFERENCE]. Clear separation allows team members to build UI, SITL backend, and AI pipeline in parallel [INFERENCE].
Production Feasibility Unviable for rural disasters [INFERENCE]. Feasible, but poor fleet scale [INFERENCE]. Highly Feasible; aligns with modern military/disaster tactical software architecture [INFERENCE].

10. Recommended Approach & Why

Selected Architecture: Hybrid Edge-Swarm Node + Tactical Mesh GCS (Approach 3)

The team selects Approach 3: The Hybrid Distributed Rescue Orchestration Architecture [INFERENCE].

+-----------------------------------------------------------------------------------+
|                           RECOMMENDED SYSTEM HYBRID                               |
+-----------------------------------------------------------------------------------+
|  [ EDGE DRONE COMPUTER ]  ---> TensorRT YOLOv8 Vision + MAVLink Controller        |
|            | (LoRa / Local Wi-Fi Mesh)                                            |
|  [ TACTICAL FIELD GCS  ]  ---> Electron/React Web GIS + PX4 SITL + Mesh Gateway   |
|            | (Cellular / Satcom when available)                                   |
|  [ CLOUD COMMAND DASH  ]  ---> Strategic Overview + DigitalSky Sync + Audit Logs  |
+-----------------------------------------------------------------------------------+

Why Alternative Approaches Were Rejected

  1. Rejection of Pure Cloud Web GCS (Approach 1): In Indian disaster zones (floods in Assam/Uttarakhand, landslides in Himachal Pradesh), cellular towers are routinely disabled or congested [RESEARCHED]. Requiring continuous cloud connectivity to stream video for AI analysis or send flight commands introduces catastrophic single points of failure [INFERENCE].
  2. Rejection of Monolithic Desktop ROS2 App (Approach 2): While fully offline, compiling a monolithic C++/Qt application creates high development friction during a hackathon, makes responsive UI design difficult, and prevents field responders on tablets or mobile phones from viewing the map tactical layer [INFERENCE].

Core Justification for Approach 3

  • Modular Separation: The computational heavy-lifting (YOLO thermal vision) runs directly on the drone's companion computer at the edge [RESEARCHED].
  • Local Reliability: The Ground Control Station runs locally on a laptop as a light Node.js/Python server servicing a Web-based React GIS UI, requiring zero external internet [INFERENCE].
  • Resilient Data Flow: MAVLink telemetry travels over direct 900MHz/865MHz radio links or local Wi-Fi mesh, ensuring total independence from public telecommunication grids [INFERENCE].

11. Technical Architecture

Layered System Architecture Diagram

===================================================================================
1. USER INTERFACE LAYER (Tactical Field GCS & Commander Dashboard)
   - Web GIS Dashboard (React + Mapbox GL JS / Leaflet)
   - Mission Planner (Lawnmower SAR Generator, Pin-Point Medical Drop Target)
   - Real-Time Telemetry HUD (Altitude, Speed, Battery, Thermal Cam Feed)
   - Mobile Field Companion App (PWA / React Native - Offline Victim Vector Maps)
===================================================================================
                                      || WebSocket / WebRTC Protocols
===================================================================================
2. GCS LOCAL BACKEND GATEWAY LAYER (Node.js Express + Python FastAPI)
   - MAVLink Telemetry Parser (MAVSDK-Python / PyMAVLink)
   - DigitalSky Airspace Boundary Geo-Fence Evaluator (R-Tree Indexing)
   - Mesh Gateway Manager (UDP / Serial Bridge to LoRa radio)
   - Offline GIS Map Tile Server (MBTiles / Vector Tile Server)
===================================================================================
                                      || Local RF / UDP MAVLink Communications
===================================================================================
3. EDGE COMPUTE & AUTONOMY LAYER (Drone / UGV Companion Hardware)
   - ROS2 Humble / Micro XRCE-DDS Middleware
   - AI Perception Pipeline: OpenCV Video Capture -> ONNX/TensorRT YOLOv8 Thermal Engine
   - Waypoint Dispatcher & Emergency Fail-Safe Handler (Auto-RTL on Low Power/Geofence)
   - Medical Payload Bay Actuator Service (GPIO / Serial Servo Release + Temp Monitoring)
===================================================================================
                                      || Serial MAVLink (UART)
===================================================================================
4. HARDWARE AUTOPILOT / SIMULATION LAYER
   - PX4 Autopilot / ArduPilot Flight Controller (Physical Pixhawk 4 OR SITL Gazebo)
   - Sensors: GPS/GNSS, IMU, Barometer, Optical Flow, Thermal Camera (FLIR)
   - Actuators: ESCs, Brushless Motors, Payload Release Servos
===================================================================================

Detailed Data-Flow Narrative

  1. Pre-Flight DigitalSky Safety Check:
    • The Operator selects a search polygon on the React GIS Map [INFERENCE].
    • The GCS local backend loads cached DGCA DigitalSky GeoJSON boundaries and performs a 2D spatial intersection check [INFERENCE].
    • If the search polygon intersects a Red Zone (e.g., airport radius), mission generation is hard-blocked [INFERENCE]. If in a Yellow Zone, a warning requires operator confirmation [INFERENCE].
  2. Autonomous Search Path Generation & Dispatch:
    • The GCS converts the polygon into an optimized lawnmower waypoint path considering altitude, camera Field-of-View (FOV), and overlap percentages [KNOWN].
    • The path is serialized into standard MAVLink mission items (MAV_CMD_NAV_WAYPOINT) and pushed over UDP/Serial to the PX4 flight controller [KNOWN].
  3. In-Flight Edge Vision & Detection:
    • During execution, the drone's thermal camera streams raw frames to the edge companion computer (Jetson/Pi 5) [RESEARCHED].
    • The TensorRT-optimized YOLOv8 model inspects frames at 30 FPS [RESEARCHED].
    • Upon detecting a human heat signature above confidence threshold (e.g., >0.85), the edge computer extracts the vehicle's exact GPS coordinates, altitude, and frame thumbnail [INFERENCE].
    • A high-priority MAVLink STATUSTEXT / custom message is transmitted back to the GCS over the radio link [INFERENCE].
  4. Medical Dispatch & Drop Execution:
    • The Operator verifies the victim detection on the GCS HUD and clicks "Dispatch Medical Aid" [INFERENCE].
    • The GCS calculates the optimal drop route for a heavy-lift cargo drone, accounting for wind vector and battery budget [INFERENCE].
    • Upon arriving over the drop target, the drone initiates a precision hover at 5m AGL, verifies surface obstacle clearance via downward LiDAR/Sonar, and triggers the GPIO servo lock to release the insulated medical container [INFERENCE].

12. Technology Stack

Architecture Layer Selected Technology Technical Justification Evaluated Alternative Reason Alternative Rejected
Frontend Framework React 18 + TypeScript + Mapbox GL JS Fast vector map rendering, highly responsive components, rich open-source GIS library support [KNOWN]. Angular / Native C++ Qt Qt has steep learning curve and slow web integration; Angular is overly boilerplate-heavy for hackathons [INFERENCE].
GCS Local Backend Node.js (Express) + Python 3.12 (FastAPI) Dual stack: Python handles heavy MAVLink/GIS math; Node.js handles ultra-fast WebSocket UI streaming [INFERENCE]. Pure Java / Spring Boot High memory footprint; slow startup time on field laptops [INFERENCE].
Drone Edge Autonomy ROS2 Humble Hawksbill + MAVSDK-Python Native microsecond inter-process communication, pub-sub architecture, industry-standard robotics framework [KNOWN]. ROS1 Noetic ROS1 is end-of-life and lacks native real-time QoS (Quality of Service) policies [KNOWN].
AI Perception Framework PyTorch -> ONNX -> TensorRT (YOLOv8-Nano) Quantized 8-bit model delivers 45+ FPS on Jetson Orin Nano with minimal battery drain [RESEARCHED]. Full TensorFlow / OpenCV Haar Cascades TensorFlow is heavier with higher latency; Haar cascades fail under varying thermal conditions [RESEARCHED].
Autopilot Middleware PX4 Autopilot Ecosystem Modern, highly modular, native Micro XRCE-DDS integration with ROS2, robust SITL simulation support [KNOWN]. ArduPilot ArduPilot is excellent but ROS2 integration requires more complex MAVROS bridges compared to PX4 [INFERENCE].
Database & Caching SQLite (GCS Local) + IndexedDB (Browser) Embedded, zero-configuration relational database ideal for off-grid desktop/PWA environments [KNOWN]. PostgreSQL / MongoDB Requires running active database daemons, unnecessary overhead for field GCS [INFERENCE].
Off-Grid Connectivity MAVLink over 865-867 MHz LoRa / Wi-Fi Mesh Operates within legal Indian unlicensed ISM bands; penetrates light foliage [RESEARCHED]. 4G/5G Dongles Unreliable during actual Indian disaster events due to tower failures [RESEARCHED].
Simulation Engine Gazebo Harmonic + PX4 SITL Accurate multi-vehicle physics, sensor simulation (thermal camera, LiDAR), native ROS2 bridge [KNOWN]. AirSim Microsoft AirSim is archived/deprecated and extremely resource-heavy for student laptops [KNOWN].

13. AI/ML Justification

AI should only be applied where traditional deterministic code fails. Below is the strict justification breakdown:

+------------------------------------------------------------------------------------+
|                                AI vs. RULE-BASED LOGIC                             |
+------------------------------------------------------------------------------------+
|  USE AI         : Thermal & Optical Survivor Detection (Unstructured video frames)|
|  DO NOT USE AI  : Flight Stability & Motor Control (Deterministic PID Loops)       |
|  DO NOT USE AI  : DigitalSky Airspace Geofencing (Exact 2D/3D Polygon Geometry)   |
|  DO NOT USE AI  : Fail-Safe Return-to-Launch (Hardcoded Altitude & Battery Limits)|
+------------------------------------------------------------------------------------+

Component 1: Thermal & Optical Human Survivor Detection

  • 1. What exact problem does AI solve? Distinguishing human bodies (alive/emitting heat) from warm debris, solar-heated rocks, animals, or water reflections in unstructured thermal/optical video feeds [INFERENCE].
  • 2. Input: Raw 1080p / 640x480 thermal infrared video frames (8-bit or 16-bit radiometric array) [KNOWN].
  • 3. Output: Bounding boxes [x_min, y_min, x_max, y_max], class label (human_survivor), and confidence score [0.0 - 1.0] [KNOWN].
  • 4. Why can a simpler rule/system not solve it? Threshold-based thermal blobs fail completely when background ambient ground temperatures reach 37°C or when bodies are partially covered by rubble/foliage [RESEARCHED].
  • 5. What data is required? FLIR Thermal Dataset, SARTAG SAR dataset, and custom annotated aerial thermal images [RESEARCHED].
  • 6. How will it be evaluated? Precision, Recall, and Mean Average Precision ([email protected]) on test validation split [KNOWN]. Target: >85% [email protected] [INFERENCE].
  • 7. What happens when it is wrong?
    • False Positive: Operator sees false pin on map; checks visual video overlay and dismisses pin (low impact) [INFERENCE].
    • False Negative: A survivor is missed during an automated aerial sweep (high impact) [INFERENCE].
  • 8-13. Model Architecture Details:
    • Requires Training? Yes (Supervised object detection) [KNOWN].
    • Requires Fine-Tuning? Yes (Fine-tuning pre-trained COCO YOLOv8-Nano weights on thermal datasets) [RESEARCHED].
    • Requires RAG / LLM? No. Strictly Computer Vision [INFERENCE].
    • Requires Computer Vision? Yes [INFERENCE].
    • Requires Speech / Forecasting? No [INFERENCE].
  • 14. Is human oversight required? YES. Every AI detection generates a "Candidate Victim Alert" on the GCS. The human rescue commander must manually confirm before dispatching ground units or dropping supplies [INFERENCE].

Non-AI / Rule-Based Operations (Where AI MUST NOT Be Used)

  1. Flight Control & Motor Actuation: Must use deterministic PX4 PID loops and state machines [KNOWN]. Neural net flight controllers are unpredictable during sensor noise [INFERENCE].
  2. Airspace Boundary Checking: Must use exact spatial computational geometry (Ray-Casting / R-Tree polygon intersection algorithms) against DigitalSky boundaries [KNOWN].
  3. Fail-Safe Execution: Battery low (<20%), radio loss (>30s), or geofence breach must trigger hardcoded deterministic Return-To-Launch (RTL) routines [KNOWN].

14. Data Architecture & Offline/Low-Network Design

Offline Data Schema (SQLite / Local JSON DB)

-- Missions Table
CREATE TABLE missions (
    mission_id TEXT PRIMARY KEY,
    name TEXT NOT NULL,
    type TEXT CHECK(type IN ('SEARCH_RESCUE', 'MEDICAL_DELIVERY', 'RECON')),
    status TEXT CHECK(status IN ('PLANNED', 'ACTIVE', 'COMPLETED', 'ABORTED')),
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    boundary_geojson TEXT NOT NULL
);

-- Vehicles Table
CREATE TABLE vehicles (
    vehicle_id TEXT PRIMARY KEY,
    type TEXT CHECK(type IN ('QUADCOPTER', 'HEAVY_LIFT_HEXA', 'UGV_GROUND_ROBOT')),
    firmware_version TEXT,
    battery_level INTEGER,
    last_known_lat REAL,
    last_known_lon REAL,
    status TEXT CHECK(status IN ('DISCONNECTED', 'ARMED', 'IN_FLIGHT', 'RTL'))
);

-- Survivor Detections Table
CREATE TABLE detections (
    detection_id TEXT PRIMARY KEY,
    mission_id TEXT FOREIGN KEY REFERENCES missions(mission_id),
    vehicle_id TEXT FOREIGN KEY REFERENCES vehicles(vehicle_id),
    latitude REAL NOT NULL,
    longitude REAL NOT NULL,
    altitude_m REAL,
    confidence REAL NOT NULL,
    thermal_snapshot_blob BLOB,
    status TEXT CHECK(status IN ('UNCONFIRMED', 'VERIFIED_VICTIM', 'FALSE_POSITIVE', 'RESCUED'))
);

-- DigitalSky Airspace Cache
CREATE TABLE airspace_zones (
    zone_id TEXT PRIMARY KEY,
    zone_type TEXT CHECK(zone_type IN ('GREEN', 'YELLOW', 'RED')),
    min_altitude_ft REAL,
    max_altitude_ft REAL,
    geometry_geojson TEXT NOT NULL
);

Off-Grid Synchronization & Conflict Resolution Logic

+-----------------------------------------------------------------------------------+
|                        OFFLINE MESH SYNC ARCHITECTURE                             |
+-----------------------------------------------------------------------------------+
| [ Field Operator A (Tablet) ]      [ Field Operator B (Laptop) ]                  |
|               \                               /                                   |
|                \---- LoRa / Wi-Fi Mesh ----/                                      |
|                          |                                                        |
|             Vector Clock Conflict Resolution                                      |
|             "Master Commander Override Wins"                                       |
+-----------------------------------------------------------------------------------+
  1. Local Tile Caching Strategy: Mapbox vector tiles (MBTiles format) up to zoom level 16 for operational districts are pre-downloaded and stored in local IndexedDB / SQLite disk cache [INFERENCE].
  2. Bandwidth Reduction Strategy:
    • Raw 1080p video stream stays on the local edge network or companion computer [INFERENCE].
    • Over long-range radio (LoRa 865MHz), only 16-byte telemetry packets (lat, lon, alt, battery, state) are broadcast every 1000ms [INFERENCE].
    • When a detection occurs, only a compressed 128x128 grayscale thermal thumbnail (approx. 3 KB) is sent alongside detection coordinates [INFERENCE].
  3. Conflict Handling: Multi-operator environments use Vector Clocks + Last-Write-Wins (LWW) with explicit role hierarchy [INFERENCE]. If a field operator marks a detection as "False Positive" while the Field Commander marks it as "Verified", the Commander's role cryptographically overrides the field operator's state [INFERENCE].

15. Security, Privacy & Governance

  1. PII & Victim Privacy Protection:
    • Visual optical feeds capturing disaster victims could expose facial identity or private property [INFERENCE].
    • Mitigation: Edge video streams apply an automated OpenCV Gaussian blur to detected facial regions before saving images or streaming to external monitors [INFERENCE]. Raw thermal feeds contain no identifiable visual features [KNOWN].
  2. Telemetry & Flight Control Security:
    • Unencrypted MAVLink radio links are vulnerable to packet spoofing or hijack attacks [RESEARCHED].
    • Mitigation: Enable MAVLink v2 packet signing with SHA-256 HMAC authentication keys pre-shared between GCS and PX4 flight controller [RESEARCHED].
  3. Authentication & Role-Based Access Control (RBAC):
    • Commander: Full flight authorization, payload release control, mission abort override [INFERENCE].
    • Pilot / Operator: Flight path planning, candidate victim verification [INFERENCE].
    • Observer / Medical Staff: View-only access to GIS map and victim locations [INFERENCE].
  4. Regulatory Compliance & Liability Disclaimer:
    • The platform provides automated DigitalSky airspace checking based on pre-cached government data [INFERENCE].
    • Disclaimer Notice: The software acts as a decision support system. Final flight authorization and safety remain the legal responsibility of the DGCA-certified Remote Pilot-in-Command (PIC) as per Indian Drone Rules 2021 [RESEARCHED].

16. MVP Scope (Hackathon Build)

To guarantee deliverability before the 30 September 2026 deadline [PS], the project scope is divided into clear functional tiers:

+-----------------------------------------------------------------------------------+
|                            HACKATHON MVP SCOPE                                    |
+-----------------------------------------------------------------------------------+
| MUST BUILD   : 2-Drone SITL Simulation, React GIS HUD, Lawnmower SAR Generator,   |
|                YOLOv8 Edge Thermal AI, MAVSDK Telemetry Stream, DigitalSky Check  |
| SHOULD BUILD : UGV Ground Robot Telemetry Bridge, Medical Drop Lock Trigger UI    |
| NICE TO HAVE : LoRa Radio Hardware Loop Test, Mobile PWA Offline Map Viewer       |
| OUT OF SCOPE : Custom Drone Hardware Assembly, Live Physical Airspace BVLOS      |
+-----------------------------------------------------------------------------------+

In Scope (MUST BUILD & DEMO)

  1. Dual-Vehicle SITL Environment: Containerized Gazebo/PX4 multi-vehicle simulation spawning 1 Quadcopter Scout Drone and 1 Heavy-Lift Cargo Drone [INFERENCE].
  2. Tactical Web GIS Interface: React Mapbox dashboard with live telemetry meters (altitude, speed, heading, battery, flight mode) [INFERENCE].
  3. Autonomous Lawnmower SAR Path Generator: Interactive polygon drawing tool that automatically compiles grid waypoints and uploads mission items to PX4 [INFERENCE].
  4. Edge Thermal AI Pipeline: Synthetic/Pre-recorded thermal video stream fed through TensorRT YOLOv8-Nano model, placing live victim markers on the GCS map upon detection [INFERENCE].
  5. DigitalSky Airspace Geo-Fencer: Offline spatial intersection engine checking planned flight routes against mock Indian Green/Yellow/Red GeoJSON zones [INFERENCE].
  6. Medical Payload Drop Command: Interactive HUD button that sends MAVLink servo command (MAV_CMD_DO_SET_SERVO) to simulate releasing a medical box over target coordinates [INFERENCE].

Described Only / Out of Scope (DO NOT BUILD DURING HACKATHON)

  1. Physical drone hardware frame fabrication or custom carbon fiber arm assembly [INFERENCE].
  2. Applying for actual DGCA BVLOS operational waivers or live field deployments in restricted airspaces [INFERENCE].
  3. Custom hardware satellite communication transceivers (Iridium SBD) [INFERENCE].

17. Live Demo Simulation Plan

Because live drone flights inside judging venues are unsafe, illegal, or physically infeasible, the team must execute a high-fidelity Software-In-The-Loop (SITL) Live Simulation [INFERENCE].

+-----------------------------------------------------------------------------------+
|                        LIVE DEMO SIMULATION PIPELINE                              |
+-----------------------------------------------------------------------------------+
| [ PX4 SITL + Gazebo ] --(MAVLink UDP)--> [ GarudaResQ Local Node Backend ]        |
|          |                                              |                         |
| (Simulated FLIR Video Feed)                   (WebSocket Real-Time Feed)          |
|          v                                              v                         |
| [ YOLOv8 Thermal Detection ] ------------> [ React Web GIS Map Dashboard ]        |
+-----------------------------------------------------------------------------------+

Step-by-Step Simulation Architecture

  1. Backend Execution: Run px4_sitlgazebo-classic via Docker on the demonstration laptop. Spawns two virtual vehicles at coordinates matching a real Indian disaster site (e.g., Wayanad, Kerala or Kedarnath, Uttarakhand) [INFERENCE].
  2. Synthetic Camera Feed Ingestion: A GStreamer virtual video loopback pipeline feeds a pre-recorded aerial thermal dataset (containing human targets) into the AI vision node, synchronized with the drone's simulated flight coordinates [INFERENCE].
  3. Live Interactive Demo Narrative:
    • Minute 0:00 - 1:00: Presenter introduces GarudaResQ, shows the offline map tiles, and loads Indian DigitalSky airspace boundaries [INFERENCE].
    • Minute 1:00 - 2:30: Draw a search polygon over a simulated landslide region. Click "Generate SAR Path". System executes DigitalSky check (Green Zone verified) and uploads waypoints to Scout Drone [INFERENCE].
    • Minute 2:30 - 3:30: Scout Drone takes off in Gazebo 3D view. Live thermal feed appears on HUD. AI detects a human signature (Confidence: 91%). A red alert pin flashes on the map with exact GPS coordinates [INFERENCE].
    • Minute 3:30 - 4:30: Presenter clicks "Dispatch Medical Drone". Cargo Drone automatically plans route, flies to target GPS, enters 5m hover, and triggers payload release servo. Payload temperature telemetric status reports SUCCESS [INFERENCE].
    • Minute 4:30 - 5:00: Cut field laptop Wi-Fi network completely to prove off-grid functionality; dashboard continues updating local MAVLink telemetry seamlessly [INFERENCE].

18. Implementation Roadmap

The roadmap is structured backward from the deadline of 30 September 2026 [PS]:

+-----------------------------------------------------------------------------------+
|                               TIMELINE ROADMAP                                    |
+-----------------------------------------------------------------------------------+
| Phase 1: Arch & SITL Setup        (May 2026 - Jun 2026)                          |
| Phase 2: Core GCS & Path Generator (Jun 2026 - Jul 2026)                          |
| Phase 3: AI Vision & Telemetry     (Jul 2026 - Aug 2026)                          |
| Phase 4: Integration & Edge Mesh   (Aug 2026 - Sep 15, 2026)                      |
| Phase 5: Demo Lock & Freeze        (Sep 16, 2026 - Sep 30, 2026)                  |
+-----------------------------------------------------------------------------------+
  • Phase 1: Foundation & SITL Environment Setup (01 May 2026 – 15 June 2026)
    • Set up multi-vehicle PX4 SITL + Gazebo Harmonic environment in Docker [INFERENCE].
    • Configure MAVSDK-Python middleware scripts to parse telemetry [INFERENCE].
    • Obtain and parse Indian SRTM DEM elevation raster files and DigitalSky GeoJSON samples [RESEARCHED].
  • Phase 2: Tactical GCS UI & Core Mission Engine (16 June 2026 – 31 July 2026)
    • Develop React 18 Mapbox GIS interface with offline vector tile rendering [INFERENCE].
    • Implement Lawnmower and Expanding Spiral polygon search algorithms [KNOWN].
    • Integrate DigitalSky 2D spatial collision detection module [INFERENCE].
  • Phase 3: AI Thermal Vision & Payload Module (01 August 2026 – 20 August 2026)
    • Train/Fine-tune YOLOv8-Nano on FLIR/SARTAG datasets; export to ONNX/TensorRT [RESEARCHED].
    • Integrate OpenCV GStreamer video processing pipeline [INFERENCE].
    • Build payload release trigger logic and simulated IoT temperature monitoring stream [INFERENCE].
  • Phase 4: Multi-Agent Coordination & Offline Testing (21 August 2026 – 15 September 2026)
    • Implement dual-drone workflow (Scout Drone detection triggers Cargo Drone route) [INFERENCE].
    • Conduct network disconnect testing to verify 100% off-grid system resilience [INFERENCE].
    • Perform performance optimization (achieve sub-50ms UI update latency) [INFERENCE].
  • Phase 5: Demo Freezing, Simulation Polishing & Final Dossier (16 September 2026 – 30 September 2026)
    • Record fallback video demos in case judging environment has hardware constraints [INFERENCE].
    • Freeze code base, finalize presentation slides, and complete deployment docs [INFERENCE].
    • Final Deadline: 30 September 2026 [PS].

19. Testing & Validation Plan

Test Category Target Metric / Scenario Validation Methodology Success Threshold
Functional Flight Test Lawnmower waypoint upload and auto-mission execution in SITL. Automated MAVSDK test script verifying mission completion. 100% mission item execution without flight command timeouts [INFERENCE].
AI Perception Performance Precision and Recall on thermal human detection under partial occlusion. Test inference on 500 ground-truth thermal test images. [email protected] >= 0.85; Inference speed >= 30 FPS on TensorRT [INFERENCE].
Airspace Safety Validation Detect intentional flight path overlap into simulated Indian Red Zones. Unit tests passing 50 illegal GeoJSON polygons through fencer. 100% illegal paths hard-blocked with zero false negatives [INFERENCE].
Offline Resilience Disconnect physical WAN/Internet cable during multi-vehicle mission execution. Kill active internet gateway during live flight in SITL. Local GCS continues receiving MAVLink telemetry and displaying map tiles without crash [INFERENCE].
Telemetry Latency End-to-end packet delay from PX4 SITL to React GIS UI meters. Timestamp log comparison between MAVLink emit and WebSocket UI render. Latency < 100 ms over local network loopback [INFERENCE].
UI Usability Test Time taken by non-technical user to dispatch a rescue drone upon alert. User study measuring task completion time for 5 test subjects. Complete dispatch workflow in < 3 button clicks / under 15 seconds [INFERENCE].

20. Risk Register

Risk Event Likelihood Impact Severity Technical Mitigation Strategy
High SITL Laptop Resource Consumption (Gazebo + Docker + Web UI crashes student laptop during live presentation) High [INFERENCE] High [INFERENCE] CRITICAL Pre-configure lightweight headless Gazebo options (gz sim -s); split frontend and SITL onto two laptops via local Ethernet cable if needed [INFERENCE].
AI Thermal False Positives (Hot rocks/animals flagged as disaster victims) Medium [INFERENCE] Medium [INFERENCE] MODERATE Require multi-frame verification (target must persist across 5 consecutive video frames) and enforce human commander visual confirmation [INFERENCE].
MAVLink Signal Loss in Off-Grid Mesh (Radio packet drop over long ranges) High [INFERENCE] High [INFERENCE] HIGH Implement automatic drone fail-safe: if radio link is lost for >30 seconds, vehicle completes search pattern autonomously or executes auto-RTL [KNOWN].
Incomplete DigitalSky Airspace Data (Official DGCA API unavailable or restricted during build) High [RESEARCHED] Medium [INFERENCE] MODERATE Build a robust offline parser that ingests standard GeoJSON files matching official DigitalSky zone schemas [INFERENCE].
Payload Balance Instability (Medical box drop causes drone aerodynamic flip) Low [INFERENCE] High [INFERENCE] HIGH Simulate payload release only when drone is in stabilized low-altitude hover (<0.2 m/s velocity) [INFERENCE].

21. Cost & Scalability

Hackathon MVP Build (Zero Hardware Cost Strategy)

  • Software Stack: 100% Open Source (React, Node.js, Python, ROS2 Humble, PX4 Autopilot, Gazebo Harmonic, SQLite) [KNOWN] = ₹0.
  • Simulated Compute: Existing student laptops running Linux/WSL2 [INFERENCE] = ₹0.
  • Geospatial Data: OpenStreetMap tiles, NASA SRTM DEM 30m, Synthetic DigitalSky GeoJSON [KNOWN] = ₹0.
  • Total Estimated Hackathon Budget: ₹0 - ₹2,000 (Optional: USB LoRa telemetry module for physical hardware demo display) [INFERENCE].

Production Deployment (Field Deployment Scale)

  • Edge Companion Computer: Nvidia Jetson Orin Nano 8GB [RESEARCHED] = ~₹45,000 / vehicle.
  • Tactical Rugged Field GCS Laptop: IP65 Sun-readable Windows/Linux Panasonic Toughbook [INFERENCE] = ~₹1,500,000 [NEEDS VALIDATION].
  • Long-Range Mesh Telemetry Radios: 900MHz / 865MHz 1W Encrypted MAVLink Telemetry Radios [RESEARCHED] = ~₹15,000 / pair.
  • Thermal Camera Payload: FLIR Boson 320 Radiometric Thermal Core [RESEARCHED] = ~₹250,000 / vehicle.
  • Cloud Operations Center Server: Dual AWS EC2 instances for post-mission data aggregation and fleet lifecycle logging [INFERENCE] = ~₹20,000 / month.

22. Differentiation

To stand out from generic SIH submissions, GarudaResQ incorporates distinct operational capabilities directly linked to SIH26201 requirements:

+------------------------------------------------------------------------------------+
|                             KEY DIFFERENTIATORS                                    |
+------------------------------------------------------------------------------------+
| 1. Dual-Domain Heterogeneous Coordination (Scout UAV + Cargo UAV + Ground UGV)    |
| 2. DGCA DigitalSky Offline Parser (Built specifically for Indian Airspace Rules)    |
| 3. Bandwidth-Adaptive Mesh Protocol (Translates video to 3KB thermal thumbnails)   |
| 4. 100% Off-Grid Operability (Runs complete GCS stack on local loopback)           |
+------------------------------------------------------------------------------------+
  1. Heterogeneous Multi-Agent Workflow: Most submissions demo a single flying drone. GarudaResQ demonstrates a complete rescue chain: Scout UAV discovers victim -> Cargo UAV drops medical aid -> Ground UGV approaches debris [INFERENCE].
  2. Native DigitalSky Airspace Integration: Explicitly parses Indian civil aviation zone structures (Green/Yellow/Red), ensuring legal compliance out-of-the-box [INFERENCE].
  3. Low-Bandwidth Thermal Compression: Rather than attempting to stream high-definition video over congested radio links, the edge computer extracts thermal bounding box thumbnails (<3KB), guaranteeing real-time alerts over 865MHz LoRa radios [INFERENCE].
  4. Zero-Cloud Dependency: Designed from the ground up for Indian rural disaster realities where internet connectivity is completely lost [INFERENCE].

23. Future Scope

Post-hackathon development can extend the system into a commercially viable product:

  1. 5G Private Network Slicing: Integrating private 5G ultra-reliable low-latency communications (URLLC) for urban disaster zones [INFERENCE].
  2. Tethered Long-Endurance Drone Stations: Supporting continuously tethered quadcopters that act as high-altitude cellular/Wi-Fi relay towers for ground teams [INFERENCE].
  3. Satellite Direct-to-Cell Synchronization: Integrating Iridium SBD or Starlink Direct-to-Cell links for global remote telemetry sync [INFERENCE].
  4. Hardware Customization & Physical Prototyping: Partnering with Indian drone OEMs (e.g., Garuda Aerospace, IdeaForge) to flash GarudaResQ ROS2 edge nodes directly onto commercial hardware [RESEARCHED].

24. Assumptions & Open Items Log

Consolidated Assumptions Log [ASSUMPTION]

  1. [ASSUMPTION] Student team will have access to at least one mid-spec Linux/Windows laptop (Intel i7/Ryzen 7, 16GB RAM) capable of running Gazebo multi-vehicle SITL simulation.
  2. [ASSUMPTION] IoT medical payload enclosure uses a simple UART/GPIO relay lock actuated via PX4 standard MAVLink servo commands.
  3. [ASSUMPTION] Synthetic GeoJSON zone boundaries accurately reflect official DGCA DigitalSky spatial polygon formats.

Consolidated Open Items & Validation Log [NEEDS VALIDATION]

  1. [NEEDS VALIDATION] Exact pricing and procurement lead-time for IP65 rugged tactical laptops in India.
  2. [NEEDS VALIDATION] Physical radio range limit of 865-867 MHz LoRa modules through dense Himalayan forest canopy under non-line-of-sight (NLOS) conditions.
  3. [NEEDS VALIDATION] Direct REST API access endpoints for live DigitalSky airspace zone queries for non-governmental software developers.

Final Recommendation

Build GarudaResQ as an offline-first, ROS2 and PX4-powered Tactical Ground Control Station with edge-based YOLOv8 thermal vision and automated DigitalSky airspace safety enforcement [INFERENCE]. Focus the hackathon build on delivering a flawless dual-vehicle SITL simulation that proves end-to-end autonomous search, human victim discovery, and precision medical payload dispatch [INFERENCE].

Recommended Stack

  • Frontend: React 18, Mapbox GL JS, TypeScript [KNOWN].
  • Backend Gateway: Node.js Express (WebSockets) + Python 3.12 FastAPI (MAVSDK) [INFERENCE].
  • Autopilot & Sim: PX4 Autopilot, ROS2 Humble, Gazebo Harmonic Docker [KNOWN].
  • AI Vision: PyTorch -> ONNX -> TensorRT quantized YOLOv8-Nano [RESEARCHED].
  • Database: SQLite + IndexedDB [KNOWN].

Biggest Dependency

PX4 SITL + Gazebo multi-vehicle simulation stability on the demonstration laptop [INFERENCE].

Biggest Risk

Laptop hardware lag or crashes during live evaluation while rendering 3D Gazebo physics alongside React Mapbox GIS maps [INFERENCE].

Biggest Technical Challenge

Achieving low-latency, real-time synchronization between edge AI object detection bounding boxes, MAVLink drone telemetry coordinates, and map overlay renders [INFERENCE].

First 5 Actions

  1. Clone PX4 Autopilot repository and verify containerized Gazebo SITL multi-vehicle simulation environment [KNOWN].
  2. Build a basic React 18 + Mapbox GL JS map interface capable of rendering offline MBTiles [INFERENCE].
  3. Write a Python MAVSDK script to connect to SITL over UDP and display live latitude/longitude telemetry [KNOWN].
  4. Download the FLIR Thermal dataset, fine-tune a YOLOv8-Nano model, and benchmark ONNX export inference speed [RESEARCHED].
  5. Construct an offline GeoJSON spatial intersection module to test flight path overlapping against Indian Red Zone coordinates [INFERENCE].

Validation Before Coding

  • Verify that the development laptop supports Docker GPU passthrough for Gazebo simulation [INFERENCE].
  • Confirm Mapbox offline vector tile generation (MBTiles) works without requiring an active Mapbox API key during offline state [INFERENCE].

Buildability Score /100

88 / 100 [INFERENCE] (High feasibility: The software stack relies entirely on mature, open-source robotics and web technologies (PX4, ROS2, React, YOLOv8) with zero requirement for physical hardware manufacturing during the hackathon phase).

Confidence

HIGH [INFERENCE] (The solution perfectly aligns with the explicit Software category of problem statement SIH26201, addresses real-world Indian operational constraints, and provides a clear path to live demonstration).

Research Sources

  1. LeDroit India - Drone Regulations: "Digital Sky" Platform and Compliance
  2. IncorpX - Drone Startup Registration in India: DGCA Type Certificate Process (2026)
  3. PMC - Implementation of drone based delivery of medical supplies in North-East India
    • URL: https://pmc.ncbi.nlm.nih.gov/articles/PMC10275566/ [RESEARCHED]
    • Source Type: Peer-Reviewed Academic Publication (PubMed Central)
    • Supported Claim: Documents ICMR i-DRONE operational trials for medical supply delivery in remote Indian terrains.
    • Reliability Assessment: Very High.
  4. Kodainya - Disaster Management Drones in India: NDRF, AI, and Emergency Response
  5. SciOpen - A Survey of Pixhawk/PX4 Autopilot and Its Impact on Research and Education
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.