jagnani73P.03
[the record]STATUS: NTU SINGAPORE — AUG 2026

Bharat Beacon

CODE2CREATE 4.0 · BEST 1ST-YR TEAM
disaster response, mapped live — IoT distress signals pinpointed for the authorities
fig. 1 — distress signals polled onto the government dashboard in real timeIoT · MapBox · HTTP polling
GOVERNMENT PORTAL · live mappolling… +0 active
01THE PROBLEMcrises move faster than dashboards

In a disaster, authorities need to see where help is needed, right now — not after the reports are collated.

Bharat Beacon tackles disaster management across three phases — preemptive risk mitigation, mid-crisis response, and post-crisis recovery. It's an IoT-driven system where physical devices transmit distress signals to a central platform. Built at Code2Create 4.0 by ACM VIT, where the team won Best First Year Team.

02THE ARCHITECTUREIoT signals → a live map

I built the Government Portal: a real-time dashboard plotting incoming distress calls as pinpoints on an interactive MapBox map. To stay current without a persistent connection, I used HTTP polling to continuously fetch the latest device signals and metadata.

01

SIGNAL

IoT devices transmit distress

IoT

02

POLL

fetch latest signals + metadata

HTTP polling

03

MAP

plot pinpoints in real time

MapBox API

04

RESPOND

authorities triage live emergencies

dashboard

STACK — JavaScript · Node · MapBox API · HTTP polling
03WHAT I BUILTthe government portal

I owned the authorities' view — a live geographic overview of every active emergency:

01

live distress map

MapBox pinpoints for each incoming signal

02

HTTP polling

fresh signals without a persistent socket

03

device metadata

context attached to every distress call

04

three-phase model

mitigation, response, and recovery

04IN THE WILDplates 01–01 · the government portal