Surat flood risk
Surat's flooding arrives from upstream. Rain lands on eight municipal zones, Ukai decides what passes downstream, the weir-cum-causeway inside the city is either under water or not, and five khadis - Kakara and Bhedwad in Udhana, Mithi and Bhatena in Limbayat, Simada in Varachha - carry it to the streets. The corporation publishes a live reading and its own trigger level at every one of those links, which is what the dashboard's headroom card is built on. This page carries the rest: where to watch during an event, and what is not published at all.
External monitoring sources - 4
We don't republish these; tracking dam-gauge live state lives elsewhere. These are the operational portals to use during a flood event.
The operational feed. Five tables through the day in monsoon: Ukai's level and inflow/outflow, the weir-cum-causeway and whether the causeway is open, zone-wise rainfall across the eight zones, the season total, and each khadi against its published danger level. This is the source behind the headroom hero.
Ukai is not the corporation's dam. SMC attributes its dam and weir rows to the Irrigation Department and the Collector's office, and the release decision that sets Surat's flood risk is taken at state level, in this department.
Nowcasts and district rainfall warnings for Surat, upstream of anything SMC's own gauges record. The corporation reports rain that has already fallen on the city; a release decision at Ukai is made against rain that has fallen on the catchment.
The national flood-forecast portal. Listed as the place to look rather than as a known feed: no level or inflow forecast station for the Tapi at Surat has been identified on it, which is itself recorded as a gap below.
What we don't have (Surat)
- NO MODELLED INUNDATION. There is no Surat equivalent of Chennai's CFLOWS return-period zones or Mumbai's iFLOWS. No hazard choropleth, no depth extents, no return-period map, and no published waterlogging-spot register. This route therefore carries no map at all rather than an empty one.
- NO KHADI GEOMETRY. SMC publishes a danger level for each of the five monitored khadis and a live reading against it, and no centreline, no catchment and no cross-section for any of them. The numbers are precise and the creeks cannot be drawn.
- NO WARD GEOMETRY. Three competing ward schemes exist for Surat and none has downloadable boundaries: WFS is disabled on the corporation's own GIS server. Every ward-keyed surface on this platform is therefore off for Surat, not thinned.
- NO STORM-WATER NETWORK, NO DESIGN STANDARD. Neither the drainage geometry nor a published carrying capacity has been found. Kolkata publishes that its sewers were built for 6 mm of rain an hour, which is what makes measured rainfall comparable against a network; no equivalent figure is available here.
- THE LIVE FEED HAS NO ARCHIVE. SMC's page holds a rolling window of about ten readings, with no dated URL, no API and no download. Every day the scraper does not run is lost permanently, so the series on this platform starts the day it first ran and never implies a longer record than that.
- NO CWC FORECAST STATION IDENTIFIED for the Tapi at Surat. The release that drives the city's flooding is decided upstream at Ukai, and no public forecast of it - as opposed to a reading of what has already been released - has been found.
- AUGUST 2006 IS NOT PRIMARY-SOURCED. Surat's defining flood, and the obvious thing to render today's release against, is deliberately absent. Every figure for it currently traces to Wikipedia, news coverage or advocacy reports. It returns from the People's Committee on Gujarat Floods report or the Surat Citizens' Council Trust report, and not before.
Chennai's flood-risk page renders modeled hazard zones, 2015/2020 hotspots, drainage and sewerage overlays - none of which exist publicly for this city. This page surfaces what's actually available rather than papering over the gap with synthetic data.