These fields preserve the complete public record for checking and reuse. They are not needed for the main answer above.
- Record ID
- bnd-lesco-lahore-subdivision-candidates-2026
- Boundary Kind
- service
- Administrative Purpose
- Resident lookup across the 113 official subdivisions under LESCO's four Lahore circles
- Boundary Status
- reconstructed
- Observed Date
- 2026-08-04
- Geometry
- Status
- reconstructed
- Basis
- point-sample-inference
- Path
- source-data/geography/lesco-lahore-subdivision-candidates-2026-08-04.geojson
- Format
- GeoJSON
- Geometry Type
- Polygon
- Coordinate Reference System
- EPSG:4326
- Feature Count
- 113
- File Hash
- sha256:e6ca5025551fc955f387ee715becaad8cfc987a8395b1595625370c64f320529
- Conversion Method
- Each official five-digit subdivision was seeded from an exact public locality label, a privacy-safe bill or NEPRA complaint observation, or a low-confidence parent-division orientation point. Nearest-area cells were clipped to Lahore District.
- Uncertainty Notes
- The 113 codes and their parent divisions and circles are official. The cells are working lookup areas. LESCO has not published official subdivision polygons.
- Geographic Claim
- Assignment Level
- territory
- Proves
- Every official Lahore subdivision is inspectable with its code, parent division and parent circle. The cell gives a working first match for a point.
- Does Not Prove
- It does not prove the account, feeder, transformer or official subdivision boundary for a property. The five-digit subdivision code on the bill is stronger.
- Public Display
- context-only
- Evidence Gap
- Official digital subdivision and feeder boundaries plus an address-to-account office lookup.