These fields preserve the complete public record for checking and reuse. They are not needed for the main answer above.
- Record ID
- bnd-lahore-legacy-feeder-route-context-2026
- Boundary Kind
- service
- Administrative Purpose
- Resident-facing orientation for four current PMA feeder-route identities where a dated side-project line can be shown separately from the official route record
- Boundary Status
- reconstructed
- Observed Date
- 2026-04-06
- Geometry
- Status
- reconstructed
- Basis
- derived-source-vector
- Path
- source-data/geography/lahore-legacy-feeder-route-context-2026-04-06.geojson
- Format
- GeoJSON
- Geometry Type
- Mixed
- Coordinate Reference System
- EPSG:4326
- Feature Count
- 72
- File Hash
- sha256:a3084fb8158d563d4ee7aa5ce6d93ae0d59728b40d0aba084a3a7091e95077e1
- Conversion Method
- Four encoded legacy route paths were decoded to LineStrings. Referenced stop coordinates were retained as route-specific points. A route was included only when its route number and both endpoints still matched the current PMA page after punctuation-insensitive comparison.
- Uncertainty Notes
- The side-project paths follow roads between legacy points. They were not published by PMA. A current matching route identity does not prove the exact line, stop position or present operation.
- Geographic Claim
- Assignment Level
- asset
- Proves
- The map preserves a dated working reconstruction for four feeder-route identities whose route number and endpoints still match current PMA records.
- Does Not Prove
- The layer does not prove an official or current route line, an exact stopping position, present operation, frequency, fare, accessibility, disruption state, timetable or vehicle location.
- Public Display
- context-only
- Evidence Gap
- Current machine-readable PMA feeder-route geometry, stop coordinates, schedules, accessibility, fares and disruptions.