These fields preserve the complete public record for checking and reuse. They are not needed for the main answer above.
- Record ID
- bnd-lahore-drainage-map-context-2026
- Boundary Kind
- other
- Administrative Purpose
- Resident-facing orientation to mapped drains, stormwater channels and other waterways near a selected Lahore road
- Boundary Status
- reconstructed
- Observed Date
- 2026-08-04
- Geometry
- Status
- reconstructed
- Basis
- derived-source-vector
- Path
- source-data/geography/lahore-drainage-map-context-2026-08-04.geojson
- Format
- GeoJSON
- Geometry Type
- Mixed
- Coordinate Reference System
- EPSG:4326
- Feature Count
- 256
- File Hash
- sha256:c6b7c915f4d498df3e4d564e82f8fa85d60da6a0fe4983420ae0396b66463dd5
- Conversion Method
- Canal, drain, ditch and stream lines in the 3 August 2026 Geofabrik Pakistan OpenStreetMap extract were retained when at least one vertex fell inside the official PULSE Lahore district polygon. Exact normalized names join Satto Katla Drain and Cantonment Drain to their separate official asset identities.
- Uncertainty Notes
- OpenStreetMap is community maintained. Unnamed lines and spelling variants are preserved. A line does not prove ownership, a current operating office, catchment, flow direction, capacity, condition or desilting status.
- Geographic Claim
- Assignment Level
- context-only
- Proves
- The displayed line and name were present in the pinned community-map extract. Exact normalized names connect two lines to separately verified official drain identities.
- Does Not Prove
- It does not assign a selected road to that line or prove the public authority, inlet, catchment, pumping route, outfall, capacity, condition or current desilting status.
- Public Display
- context-only
- Evidence Gap
- Current official drain, inlet, pumping-station, ponding-point, catchment, work-order and desilting GIS with segment-level public-authority assignments.