WASA Lahore local drainage complaint routes

The resident map treats complaint routing and hydraulic infrastructure as separate layers.

Boundary Version

How we know

The resident map treats complaint routing and hydraulic infrastructure as separate layers.

These fields preserve the complete public record for checking and reuse. They are not needed for the main answer above.

Record ID

bnd-wasa-lahore-drainage-circle-candidates-2026

Place Id

Boundary Kind

operating

Administrative Purpose

Give a resident a reproducible first drainage complaint office candidate without calling an O&M area a hydraulic catchment

Boundary Status

reconstructed

Observed Date

2026-08-05

Geometry

Status: reconstructed
Basis: point-sample-inference
Path: source-data/geography/wasa-drainage-circle-candidates-2026-08-05.geojson
Format: GeoJSON
Geometry Type: Mixed
Coordinate Reference System: EPSG:4326
Feature Count: 8
File Hash: sha256:44534b79e81e3f42f476e6bb880cda7d6b98c96da3ca4b9f4044cb7169145fa1
Conversion Method: Six separately named drainage circles in the 23 May 2025 roster were paired to their O&M section areas. Shalimar and Jubilee were retained as section-level drainage routes because the captured roster did not list separate drainage circles for them.
Uncertainty Notes: These areas route complaints. They are not published storm-water or sewer catchments and do not assign a road to an inlet, drain, pump or outfall.

Geographic Claim

Assignment Level: territory
Proves: Every coordinate inside the dated WASA footprint receives a named drainage circle where one was published, or the narrowest verified section route where it was not.
Does Not Prove: It does not prove a hydraulic catchment, local inlet, drain path, disposal station, outfall, current line or live officeholder.
Public Display: context-only

Service Function Id

Institution Ids

Operating Unit Ids

Evidence Gap

A current official drainage-circle map and street-to-catchment asset register.