Jal Setu

Inspiration

Urban water resilience brings together several connected questions: where rainfall may create flood risk, which neighborhoods face water stress, where recharge could help, and how essential water deliveries might be planned. We wanted to explore what a shared, map-first command view could make easier to understand before a response is chosen.

What it does

Jal-Setu is a simulated water-resilience command centre for Faridabad. Its map shows 20 synthetic ward catchments with flood-risk, water-stress, and recharge-potential layers. Users can adjust a hypothetical rainfall scenario, review ward priorities, allocate simulated recharge, and calculate heuristic tanker routes across 12 modeled vehicles. A demo Field Crew role is limited to its assigned route and can record a simulated stop completion. An impact view separates synthetic baseline values from new allocations and estimated outcomes. A rule-based Copilot streams a short briefing based on the active scenario.

How we built it

The dashboard is built with HTML, CSS, and JavaScript. A Python/FastAPI service serves the UI and API from one origin, using deterministic synthetic data and transparent formulas for rainfall and risk estimates. Recharge allocation respects modeled site capacities; tanker routes use a deterministic heuristic. MapLibre GL JS renders the thematic map using OpenFreeMap tiles. The Copilot is rule-based, and the admin/crew selector is for demonstration only—not production authentication.

Challenges

The key challenge was making the demo useful without implying that its figures were real forecasts or operational results. There are no live municipal feeds or ground-truth data, so we used synthetic inputs, labeled simulated actions, kept estimated impacts distinct from baseline values, and avoided claiming model accuracy that could not be verified. We also had to make admin planning actions and the crew's assigned-route actions visibly distinct.

What we learned

A command-centre dashboard needs more than a map and KPIs: users must be able to tell what is a baseline, what is a proposed action, and what is only an estimate. Clear assumptions, visible demo boundaries, and role-scoped workflows are essential to making a planning simulation understandable and trustworthy.

Built With

• climate-resilience
• css3
• fastapi
• geospatial-mapping
• html5
• javascript
• maplibre-gl-js
• openfreemap
• python
• rest-api
• server-sent-events
• simulation
• urban
• water-management