Lahore rapid-transit corridors and stations

The public map keeps official system facts separate from community-map geometry and live service claims.

Boundary Version

How we know

The public map keeps official system facts separate from community-map geometry and live service claims.

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

Record ID

bnd-lahore-rapid-transit-context-2026

Place Id

Boundary Kind

service

Administrative Purpose

Resident-facing discovery of Lahore Metrobus and Orange Line corridors and stations before checking current service information

Boundary Status

reconstructed

Observed Date

2026-08-03

Geometry

Status: reconstructed
Basis: derived-source-vector
Path: source-data/geography/lahore-rapid-transit-context-2026-08-03.geojson
Format: GeoJSON
Geometry Type: Mixed
Coordinate Reference System: EPSG:4326
Feature Count: 55
File Hash: sha256:d48edb1bbd15830ad7ef1ae79f3662cdd6af2c25b48b0996ccc6bb4596ef6ac6
Conversion Method: Official PMA pages establish the two systems and their station counts. Two pinned OpenStreetMap route relations supply 2 corridor MultiLineStrings and 53 station points. Missing segments or stops were not invented.
Uncertainty Notes: OpenStreetMap is community maintained. PMA confirms the route identities and counts but does not publish the same machine-readable geometry.

Geographic Claim

Assignment Level: asset
Proves: The official operator publishes the two rapid-transit systems and matching station counts. The displayed geometry was present in the pinned community-map route relations.
Does Not Prove: The layer does not prove live operation, frequency, fare, accessibility, disruption state, a complete walking route or ordinary bus and feeder coverage.
Public Display: context-only

Service Function Id

Institution Ids

Evidence Gap

Current machine-readable feeder and electric-bus routes, stop-level schedules, accessibility, fares, disruptions and operating contracts.