District split
Old and new indicators may cover different populations even when the district name appears similar.
Boundary Versioning
Every map and place-based statistic needs a known geographic version.
Administrative boundaries change. Districts split, names change, wards are redrawn and datasets use different geographic units. Boundary versioning prevents false comparison and preserves a traceable place history.
Why versioning matters
Without it, change in the map can look like change in the outcome.
Ward redrawing
A local trend can be distorted when boundaries change between elections or planning cycles.
Name variation
Renaming, spelling and language forms can create duplicate records for the same place.
Source disagreement
Different agencies may publish incompatible codes, shapes or effective dates.
Aggregation error
Village, block, city and district data cannot be combined without a documented crosswalk.
False progress
Apparent improvement or decline may reflect changed geography rather than changed lives.
Location record schema
Store identity, hierarchy, geometry and time separately.
Schema 01
Stable identity
Assign a durable platform ID that does not change when the display name or boundary geometry changes.
location_idStable internal identifier.
official_codeSource-specific government code.
display_nameCurrent public name.
alternate_namesLanguage and historical forms.
Change events
Treat every boundary change as a documented event.
| Event | Required record | Data treatment | User-facing disclosure |
|---|---|---|---|
| Split | Parent, successors, effective date and source. | Do not assign historical values to new units without method. | Show comparability warning. |
| Merge | Predecessors, successor and aggregation method. | Preserve original records and crosswalk. | Explain changed coverage. |
| Transfer | Area moved between parent units. | Version both hierarchies and geometry. | State effective period. |
| Rename | Old and new names with same identity where appropriate. | Maintain aliases for search and citation. | Show current and historical name. |
| Geometry correction | Source revision without administrative change. | Increment geometry version and document reason. | Update boundary metadata. |
Comparison rule: a time series should state whether data uses contemporary boundaries, fixed historical boundaries or a harmonised crosswalk.
Map publication standard
Every geographic layer should carry enough metadata to be challenged.
Boundary source
Publishing organisation, dataset and access reference.
Version and date
Geometry version, valid period and last update.
Geographic level
State, district, block, city, ward, village or other unit.
Join method
How statistics were matched to geographic records.
Known gaps
Missing units, disputed matches and incomplete coverage.
Comparison warning
Whether boundary change affects trends or rankings.
Build place intelligence that survives administrative change.
Use stable IDs, versioned boundaries, lineage and transparent comparison rules.