Home / CPHEEO / Chapter 6
CHAPTER 6

Catchment Characterisation and Drainage Districts

Catchment Delineation & Drainage Districts

Methodology for delineating drainage catchments + sub-catchments — topographic survey, digital elevation models (DEM/SRTM), GIS-based catchment derivation, drainage district identification, imperviousness mapping, future build-out projection, integration with city master plan + land-use zoning.

🗺 Catchment & Drainage DistrictsManual on Storm Water Drainage Systems1st Edition (2019), with AMRUT 2.0 + Smart Cities Mission updates referenced

Key formulas

  • Imperviousness fraction f_imp = (paved + roof + roads area) / total catchment area
  • Effective imperviousness EIA = directly-connected impervious area / total area
  • Catchment slope (avg) = (max elev − min elev) / longest flow path length
  • Drainage density = total stream length / catchment area (km/km²)
  • Future imperviousness projection = current_imp + (master_plan_FAR × 0.65) for residential; × 0.85 for commercial

Key values & thresholds

drainage district typical size
10-50 ha urban; 50-200 ha suburban
imperviousness dense business
85-95 %
imperviousness dense residential
60-80 %
imperviousness medium residential
40-60 %
imperviousness villa low density
25-45 %
imperviousness park open space
5-15 %
DEM resolution for design
5-10 m raster (cm-grade for critical underpass design)
SRTM global resolution
30 m (free, suitable for screening only)
LiDAR resolution indian smart cities
0.5-1 m raster (Smart Cities Mission deliverable)
min topographic survey density
10 m grid, 0.10 m vertical accuracy

Clause-level requirements

  • Drainage districts shall be delineated based on natural topography + existing drain alignment, not administrative boundaries.
  • Imperviousness mapping shall use current land-use survey + future build-out per master plan; design for future, not current.
  • Topographic survey for design shall be 5-10 m grid resolution with 0.10 m vertical accuracy at critical points.
  • DEM-based catchment derivation shall be cross-checked with field walk-down — DEM artefacts + buildings + roads can mislead automated extraction.
  • Drainage district boundaries shall be coordinated with sewerage zone boundaries to avoid divergent infrastructure planning.
  • Each drainage district shall have an identified outfall point + receiving water body.
  • Effective Imperviousness (EIA) — accounting only for directly-drain-connected impervious surfaces — shall be used for design, not gross imperviousness.

Practitioner notes — what goes wrong in the field

  • Use Bhuvan (ISRO) for free 30 m DEM nationwide; Smart Cities datasets give 0.5-1 m LiDAR for those specific cities.
  • 30 m SRTM is screening-grade only — useful for identifying districts but not for designing inlets or storage.
  • Field walk-down of DEM-derived catchment is mandatory — DEMs miss raised footpaths, walls, building foundations that act as flow barriers.
  • Drainage districts that cross municipal ward boundaries are common — get inter-ward coordination on the master plan or projects fragment.
  • Imperviousness mapping: use latest satellite (Sentinel-2 free, 10 m; Cartosat 2.5 m paid) + supervised classification + ground-truth.
  • Future build-out estimate: take master-plan FAR × developable area × imperviousness factor (0.65 for residential, 0.85 for commercial). Reality often exceeds this by 10-20 % due to encroachment.
  • Effective Imperviousness (EIA) excludes pavement that drains to soakaway / pervious area — usually 5-15 % less than gross imperviousness for low-density development.
  • AMRUT 2.0 city plan deliverables now include GIS-based drainage district maps + imperviousness layers — leverage these where available.
  • For old city cores, drainage districts often follow historical drain alignment (1800s+) — preserve where functional, replace where collapsed.
  • Document drainage district boundaries + outfalls in city's drainage master plan; feeds all downstream design + capex planning.

FAQs

How do I delineate a drainage district?
Start with DEM-based catchment derivation in GIS (QGIS+GRASS or ArcGIS); cross-check with existing drain network + topographic survey + field walk-down. Use natural topography, not administrative boundaries. Typical size: 10-50 ha urban, 50-200 ha suburban. Each district = one outfall point.
What DEM resolution do I need?
30 m SRTM (free, ISRO Bhuvan) for screening + master plan; 5-10 m for design; 0.5-1 m LiDAR for critical underpass/intersection design. Smart Cities Mission funded LiDAR for 100+ Indian cities — leverage these datasets where available.
Should I design for current or future imperviousness?
Future — use master-plan build-out (typically 25-30 year horizon). Current imperviousness undersizes the system. Account for FAR × developable area × 0.65 (residential) or × 0.85 (commercial) imperviousness factor.
What's Effective Imperviousness (EIA)?
Imperviousness that's directly connected to the drain network — excludes paved areas that drain to soakaway, pervious garden, or rainwater harvesting pit. Typically 5-15 % less than gross imperviousness for medium-density development. EIA is the correct input for runoff calculation, not gross imperviousness.
How do I handle drainage districts that cross ward boundaries?
Get inter-ward / inter-jurisdictional coordination at master-plan stage. Master plan should be city-wide, not ward-by-ward. Without this, projects fragment + outfalls/trunk drains end up unplanned. AMRUT 2.0 city plans are city-wide by design.

Cross-references

Indian Smart Cities Mission (DEM + LiDAR datasets)Survey of India open data portal (1:50000 toposheets)Bhuvan ISRO geoportalAMRUT 2.0 City Water Plan templateIRC SP 50:2013QGIS + GRASS GIS hydrology modules

Tags

drainage districtcatchment delineationDEMGIS drainageimperviousnesstopographic surveyfuture land usedrainage master plansubcatchment

Engineer's notes

Catchment characterisation is the spatial foundation of every drainage design. Get the catchment boundaries wrong and the design serves the wrong area; get the imperviousness wrong and you over- or under-size the entire network.

The modern workflow is GIS-based: start with a DEM (Digital Elevation Model), derive catchments using flow-accumulation + flow-direction algorithms in QGIS+GRASS or ArcGIS, then cross-check against existing drain alignments + a topographic walk-down. Free SRTM 30 m is screening-grade; project-grade designs need 5-10 m DEM (paid Cartosat) or LiDAR-derived 0.5-1 m raster (Smart Cities Mission datasets where available).

For critical infrastructure — railway underpass, metro entry, hospital — use LiDAR + topographic survey at sub-decimeter accuracy. The cost of getting the contour wrong at a low point is the cost of flooding it every monsoon.

Drainage districts are the planning units — typically 10-50 ha urban, 50-200 ha suburban. Each district has one outfall to a trunk drain or natural receiving water. Districts must be delineated by natural topography, not by administrative boundaries (wards, zones). Cross-jurisdictional coordination at master-plan stage is essential — fragmented planning = fragmented infrastructure.

Imperviousness mapping is where reality diverges from idealised land-use plans. The master plan says 40 % FAR + 30 % open space; the reality is 65 % paved + 15 % open + 5 % water-harvested + 15 % illegally encroached. Map current imperviousness from satellite (Sentinel-2 10 m free, Cartosat 2.5 m paid), and project future build-out using FAR × imperviousness factor (0.65 residential, 0.85 commercial). Add a 10-20 % margin for inevitable over-development.

Effective Imperviousness (EIA) — only the impervious area that drains directly to the storm drain — is the correct input for runoff calculation. Soakaway-drained patios, rain-garden-fed roof drains, and rainwater-harvested driveways don't add to peak flow. For low-density residential with mandatory RWH, EIA can be 10-20 % less than gross.

Where this chapter sits: catchment delineation + imperviousness mapping define the spatial inputs (A, C, sub-catchment topology) for runoff calculation in chapters 3-4. Get this chapter right and the rest of the design has a chance; get it wrong and no amount of clever hydraulics fixes it.

Download full manual from MoHUA →
Manual on Storm Water Drainage Systems · 1st Edition (2019), with AMRUT 2.0 + Smart Cities Mission updates referenced · Central Public Health and Environmental Engineering Organisation (CPHEEO), Ministry of Housing and Urban Affairs, Government of India.
InfraLens provides chapter summaries for search — full manual is the authoritative reference.