These fields preserve the complete public record for checking and reuse. They are not needed for the main answer above.
- Record ID
- bnd-lahore-road-environment-map-context-2026
- Boundary Kind
- other
- Administrative Purpose
- Resident-facing orientation to traffic signals, pedestrian crossings, railway crossings, motorway junctions, mini roundabouts and the very limited mapped street-light sample 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-road-environment-2026-08-04.geojson
- Format
- GeoJSON
- Geometry Type
- Point
- Coordinate Reference System
- EPSG:4326
- Feature Count
- 975
- File Hash
- sha256:ee8be9d8fcc38a6f417daf3637f7efc204429dec1b7278ec85e385e2244fff34
- Conversion Method
- Six useful road-control and crossing classes in the 3 August 2026 Geofabrik Pakistan OpenStreetMap extract were retained when each point fell inside the official PULSE Lahore district polygon.
- Uncertainty Notes
- OpenStreetMap is community maintained. The 975 points include 76 traffic signals, 544 pedestrian crossings, 290 railway crossings, 63 motorway junctions, one mini roundabout and one street light. The street-light count demonstrates severe lighting incompleteness.
- Geographic Claim
- Assignment Level
- context-only
- Proves
- The displayed point and any name were present in the pinned community-map extract. Separate official evidence verifies TEPA's general Lahore traffic-signal role.
- Does Not Prove
- It does not prove that the asset still exists, its condition, legal owner, operator, road controller, power supply, maintenance office or whether TEPA controls a selected point.
- Public Display
- context-only
- Evidence Gap
- A current official signal, crossing, street-light, controller, pole, meter, circuit, owner, operator, fault-route and maintenance-contract register across all Lahore road bodies.