Skip to content

ResQNet - Hyper-Local Disaster management #18

@dipesh-23

Description

@dipesh-23

Team Name

Seasonal Coders

Hackathon Track

App/Dev

ps-number

3

Email Address

dipeshshitkar2301@gmail.com

Email Addresses of Team Members

aneeshsuvarna2006@gmail.com,ujjwals653@gmail.com

Project Description

Disaster Management Platform
A comprehensive, full-stack disaster management and response ecosystem designed to bridge the gap between citizens reporting incidents and authorities managing disaster relief operations. The platform enables real-time reporting, effective alert dissemination, and seamless centralized management.

🏗️ Project Architecture
The project consists of three main components, each operating from its respective directory:

  1. Admin Dashboard (/admin-dashboard)
    A robust web portal tailored for disaster management authorities and dispatchers.

Tech Stack: React, Vite, Tailwind CSS
Key Features:
Live Dashboard: Real-time overview of active incidents and their statuses.
Reports & Alerts: Interfce to manage citizen reports and broadcast high-priority emergency alerts.
Data Resilience: Capable of queueing operations and intelligently syncing offline reports when connectivity is restored.
Advisory & Prediction Views: Dedicated interfaces to interpret incoming data and dispatch actionable advice.
2. User Application (/user-app)
A mobile application designed for citizens to quickly and securely report emergencies.

Tech Stack: Flutter (Android/iOS)
Key Features:
Cross-platform availability ensuring maximum coverage.
Intuitive interface for easily reporting disaster coordinates and details.
Receive real-time push alerts from the state/admin portal.
3. Backend (/backend)
A centralized, highly scalable server handling business logic, APIs, and data persistence from both frontends.

Tech Stack: Python, FastAPI, Supabase (PostgreSQL)
Key Features:
Asynchronous RESTful APIs.
Integrates securely with Supabase for user authentication, structured report storage, and database management.
🚀 Getting Started
Prerequisites
Node.js & npm (for Admin Dashboard)
Flutter SDK (for User App)
Python 3.8+ (for Backend)
A Supabase project with configured credentials
Run Locally
Backend:

Navigate to /backend.
Create a virtual environment: python -m venv venv
Activate it and install dependencies: pip install -r requirements.txt
Configure your .env file based on .env.example with Supabase details.
Run the server: uvicorn main:app --reload (or respective fast api command).
Admin Dashboard:

Navigate to /admin-dashboard.
Install dependencies: npm install
Start the web client: npm run dev
User App:

Navigate to /user-app.
Fetch standard packages: flutter pub get
Run on an emulator or physical device: flutter run
🔮 Future Scope
To further fortify the platform against catastrophic offline scenarios and unpredictable variables, the following strategic enhancements are planned:

Predictive Intelligence: Integrating advanced machine learning models to forecast disaster trajectories, anticipate critical resource shortages, and preemptively automate warnings before a disaster peaks.
Safe Routing & Crowd Control: Implementing AI-driven dynamic pathfinding to autonomously map safe evacuation routes. This will actively guide citizens away from unfolding hazard zones while dispersing traffic to prevent bottlenecks and panic-induced stampedes.
Offline SMS Connection: Introducing a resilient telecommunication fallback mechanism. In the event of catastrophic internet outages, citizens will still be able to submit geo-tagged incident reports and receive life-saving alert broadcasts strictly via cellular SMS networks.

Inspiration behind the Project

The Inspiration Behind ResQNet
The Problem: The Information Vacuum in Crises When a natural disaster or local emergency strikes, seconds matter. But time and again, we've noticed a fatal flaw in how crises are handled at the ground level: a severe breakdown in hyper-local communication. Centralized news and institutional alerts are often too broad or too delayed to reflect the immediate reality on your specific street or in your exact neighborhood. Misinformation spreads, panic sets in, and people are left wondering, "Is my route safe?" or "What do I do right now?"

The "Aha!" Moment: Communities are the True First Responders We realized that the most effective first responders aren't always institutions—they are the people already on the ground. Neighbors helping neighbors. Delivery drivers avoiding flooded streets. Everyday citizens acting as the eyes and ears of the community. We asked ourselves: What if we could harness that collective, real-time awareness and turn it into an actionable, life-saving tool?

The Vision: Empowering Resilience That realization birthed ResQNet. We didn't just want to build another top-down alert system; we wanted to build a community-driven lifeline.

We were inspired by the power of crowdsourcing to solve complex problems. If crowdsourcing can predict traffic patterns on navigation apps, it absolutely should be used to map disaster zones, report safety hazards, and broadcast calls for help.

Behind every feature of ResQNet lies a focused philosophy:

Real-Time Visual Context: By integrating a live feed and map, we replace panic with clarity. Seeing exact community reports helps people make informed survival decisions.
Democratized Reporting: Giving every user a voice to flag incidents means the data is always live, hyper-local, and incredibly accurate.
Actionable Preparedness: Access to crucial, easy-to-read safety protocols ensures that when the internet is spotty or panic is high, users have a reliable guide right in their pockets.
The Ultimate Goal The true inspiration behind ResQNet is simple: We believe technology should weave the safety net that catches a community when everything else falls apart. We built this project to turn helpless bystanders into an empowered, resilient network capable of saving lives.

Tech Stack

Mobile App (User App)
The user-facing application is built cross-platform natively for mobile.
Framework: Flutter (Dart)
Backend Integration: supabase_flutter (Authentication, Database, Real-time streams)
Mapping & location: flutter_map coupled with latlong2 for real-time incident mapping.
UI/Icons: Material Design & cupertino_icons
2. Admin Dashboard (Web App)
The web-based dashboard used by administrators and emergency dispatchers to view data, metrics, and manage disaster protocols.

Core Framework: React 19 (built with Vite for fast HMR)
Styling Engine: Tailwind CSS (with PostCSS and Autoprefixer)
Routing: React Router (react-router-dom)
Interactive Maps: react-leaflet coupled with leaflet.heat (for incident heatmaps) and leaflet.markercluster (grouping reports).
Data Visualization & Metrics: recharts (for KPI charts and graphs)
UI Utilities:
lucide-react (Modern icon set)
@dnd-kit/core & @dnd-kit/utilities (For drag-and-drop features)
Backend Integration: @supabase/supabase-js
3. Backend API (Microservices / External services)
A robust and fast backend used perhaps for handling complex server-side data processing and interfacing with external ML/AI scripts.

Framework: FastAPI (Python)
Serverless ASGI: Uvicorn
Data Validation: Pydantic
Database Client: supabase (Python Driver)
HTTP Client: httpx
Environment Management: python-dotenv
4. Database & Infrastructure
The foundational layer supporting the entire system with Real-time features.

Platform: Supabase (Backend-as-a-Service)
Database: PostgreSQL (with PostGIS for geospatial queries, managed via supabase_schema.sql)
Core Features Utilized:
Supabase Auth (Managing dynamic email/phone registrations seamlessly)
Realtime Channels (WebSockets for instant feed updates)

Project Repo

https://github.com/ujjwals653/vit-hackathon

Demo Video

https://drive.google.com/drive/folders/16N1ylzPjRTyPQvIwy6L5bl1zvVuxC2qj?usp=sharing

Presentation Link

https://canva.link/amkvo75pc8hd675

Anything Else?

No response

Rules and Code of Conduct

  • I agree to follow this hackathon's Rules and Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions