About Gurugram Water Intelligence
An open-source water intelligence platform for Indian cities, built to make public data accessible and actionable.
Sections are collapsed by default. Click any heading to expand it.
What we track for Gurugram
Gurugram is governed by Gurugram Metropolitan Development Authority with civic services under Municipal Corporation of Gurugram (36 wards).
Reading this dashboard
How “Days of Water Left” Works
We compute three scenarios based on current reservoir storage, daily consumption, and inflow patterns:
What each page shows for Gurugram
Per-page methodology documentation for Gurugram is pending. See the dedicated Chennai about page (/chennai/about) for the canonical methodology pattern.
Intelligence & AI narratives
Daily AI briefings, longer-form weekly narratives, and per-ward AI profiles are pending for Gurugram- the underlying summary stores aren't yet multi-city. Until those land, the page surfaces raw data without an AI commentary layer.
Data sources for Gurugram
All operational data is collected by the Python pipeline and supporting scripts that power the dashboard. Raw source data and Earth Engine summaries are upserted into Supabase (PostgreSQL) and then exposed as small, readable product signals.
Reservoir & weather
Free, no-auth daily weather data: precipitation, temperature, humidity, ET0, wind. ECMWF / ERA5-Land base. For cities with the provisional-rainfall layer, its archive API also fills the months IMD's gridded series hasn't published yet - rendered as asterisked provisional months that IMD supersedes automatically.
India Meteorological Department 0.25-degree gridded rainfall, 1970-present. Used for monsoon-context overlays.
Groundwater
Daily and seasonal manual + telemetric (DWLR) groundwater readings from the Central Ground Water Board's National Hydrograph Network.
Annual block-level Dynamic Groundwater Resource Assessment (Safe / Semi Critical / Critical / Over Exploited).
Water bodies & restoration
Base geometry for water-body polygons and the rivers polyline.
Rivers & pollution
Flood & civic infrastructure
Satellite & remote sensing
Base geometry & AI
AI city narratives and per-ward profiles. Live for Chennai; pending for Gurugram.
Data quality & limitations
How we classify river health
CPCB publishes two parallelriver-water-quality classification systems, and they don't always agree. Knowing which one we use - and why - matters for reading our river status badges honestly.
Designated Best-Use classes (A-E)
Computed from current dissolved-oxygen, BOD and coliform thresholds at each NWMP station. Updates every reading. Class A = drinking with disinfection only; Class B = outdoor bathing; Class C = drinking with conventional treatment; Class D = fisheries/wildlife; Class E = irrigation only. Below E = practically dead.
Polluted River Stretch (PRS) Priority I-V
A historical, multi-yearstretch-level designation reflecting cumulative pollution. Slow to update; once a river stretch is on the Priority list it tends to stay there even if recent readings improve. Priority I = worst (BOD > 30 mg/L sustained); Priority V = least bad of the polluted stretches.
Our status badges ("dead", "severely degraded", "degraded", "stressed", "healthy") are computed from current readings via the Designated Best-Use thresholds- not from the PRS Priority list. We take the worst classification across a river's monitored stations and surface that as the river-level status.
Practical consequence: a river on CPCB's PRS Priority list (e.g. the Madurai-Manamadurai stretch of the Vaigai is Priority III) won't automatically render as "severely degraded" here. If the underlying NWMP readings show only Class C/D conditions, the badge reflects that. The PRS designation belongs in the river description as historical context, not as the live status.
Status thresholds follow CPCB's published Designated Best-Use criteria; readings are from CPCB NWMP annual River Water Quality reports.
Known Limitations
- Estimates are approximations. Actual water availability depends on factors not modeled (groundwater extraction, Krishna water transfer, distribution losses, industrial use).
- Utility-published feeds may occasionally be stale (weekends, holidays, portal outages). Each surface shows a freshness indicator, and the freshness registry names any feed that has stopped updating.
- Groundwater data from OpenCity may lag by months. The map always shows the most recent available period.
- Forecasts use ARIMAX (AutoARIMA with inflow/outflow as exogenous regressors) and work best with 2+ years of daily data.
- Risk scores are relative indicators for comparison between wards, not absolute measures of water safety.
- Satellite spread is a summary of surface water extent, not a direct measure of storage volume, water quality, or inflow source. A lake can look broad and still hold less usable water than expected.
- Reservoir catchment polygons are reviewed operational geometries for rainfall context, not official legal boundaries. This matters especially in Chennai's managed canal and transfer system.
- Current satellite context relies on optical Sentinel-2 observations. During persistently cloudy periods, some water bodies may temporarily lose this insight until a radar fallback is added.
About the project
Disclaimer
Not an official government tool. Neer Vazhvu is an independent, open-source project. It is not affiliated with, endorsed by, or connected to any water utility, municipal corporation, pollution control body, or other government agency whose published data it cites.
Informational purposes only. All data, estimates, and forecasts are provided “as is” for general awareness. Always refer to official CMWSSB advisories for critical decisions.
No personal data collected. Neer Vazhvu does not collect, store, or process any personal information. There are no user accounts, cookies, or analytics trackers.
Open Source
Neer Vazhvu is fully open source. The code, data pipeline, and methodology are transparent and available on GitHub. Contributions, bug reports, and data corrections are welcome.
View on GitHubSupport this project
Neer Vazhvu is free and open source. If you find it useful, consider supporting us on Patreon to help cover satellite data, hosting, and API costs.
Support on Patreon