Lahore and Walton Cantonment Board candidate split

The app should present this as a working Board assignment with a visible legal limit, not as an open white gap.

Boundary Version

How we know

The app should present this as a working Board assignment with a visible legal limit, not as an open white gap.

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

Record ID

bnd-lahore-walton-cantonment-candidates-2026

Place Id

Boundary Kind

administrative

Administrative Purpose

Board-level routing inside the official PULSE Cantonment control geometry

Boundary Status

reconstructed

Observed Date

2026-08-03

Geometry

Status: reconstructed
Basis: point-sample-inference
Path: source-data/geography/lahore-walton-cantonment-candidates-2026-08-03.geojson
Format: GeoJSON
Geometry Type: Polygon
Coordinate Reference System: EPSG:4326
Feature Count: 2
File Hash: sha256:425cca1d4a60880d631da888b24061e015657309d2ad878bba7caecc4b430d36
Conversion Method: The official PULSE Cantonment control polygon was partitioned between verified Lahore and Walton Board office and locality anchors.
Uncertainty Notes: The outer control geometry is official digital context. The internal Board split is reconstructed and must not be used for title, tax or ward decisions.

Geographic Claim

Assignment Level: territory
Proves: A coordinate inside the official Cantonment control class now receives a concrete Lahore or Walton Board candidate.
Does Not Prove: It does not prove the gazetted Board local area, electoral ward, property tax assessment or land title.
Public Display: context-only

Institution Ids

Evidence Gap

The current gazetted Lahore and Walton local-area descriptions and final ward maps.