What is wrong with our data

Every dataset this platform uses has defects. Most organisations discover theirs when someone else points them out. This page is our list, published before anyone asks, and updated automatically by the ingestion pipeline.

Errors

Must be fixed before this data is authoritative

Warnings

Known, tolerated, documented

5451

Units loaded

pending verification

Dataset status

This boundary data has NOT been verified against official sources

Version geo-2026-08-28-r1 is marked PENDING_VERIFICATION and its authority level is community derived. Community-derived open datasets. Boundaries are indicative and MUST be verified against Election Commission of India and Survey of India publications before being marked ACTIVE or used for any statutory purpose. International boundaries as depicted are not authoritative.

Nothing on this platform treats it as authoritative. Constituency mappings shown to citizens carry this caveat, and the map repeats it in its legend.

Errors

Defects that make part of the data unusable. These are not cosmetic.

No errors in the current ingestion.

The Assembly Constituency layer is out of date

This Assembly Constituency dataset has no boundaries for Telangana. That indicates it predates subsequent reorganisation of States. Do not treat this layer as current for any State until it is replaced with a verified Election Commission of India source.

States with no Assembly boundaries in this dataset:

Telangana

What the platform does about it

Address resolution reports the Assembly Constituency as data unavailable for those States, with the reason shown to the user. It does not fall back to the old pre-reorganisation constituencies.
Those constituencies are excluded from address autocomplete, so nobody is offered a seat in the wrong State.
Signup still works: a citizen is mapped to State, district and Lok Sabha seat, and told what is missing.

Delimitation labels present in the source: Pre delimitation (522), unlabelled (3626)

Warnings by type

Known and tolerated. Each one is a decision we made rather than a thing we missed.

DUPLICATE DISTRICT2

A district name appeared more than once for one State. The largest polygon was kept.

STATE OUTLINE DERIVED2

The source shipped no separate outline for this unit, so its largest district polygon was used - correct for single-district Union Territories.

ID COLLISION RESOLVED54

Two units shared a generated identifier - usually a genuine case, such as two constituencies numbered 1 in Union Territories that were later merged. Both were kept and disambiguated by name.

AC UNNAMED RECORD SKIPPED34

The source contains unnamed records that are State outlines or water bodies rather than constituencies. They were skipped rather than given invented names.

AC COVERAGE MISSING1

Coverage by State and Union Territory

How many boundaries are actually loaded at each level. A zero in the Assembly column for a State that has a Legislative Assembly is a gap, not a fact about that State.

State / UT	Type	Districts	Lok Sabha	Assembly
Andaman and Nicobar Islands	Union Territory · no Assembly	3	1	n/a
Andhra Pradesh	State	13	25	175
Arunachal Pradesh	State	25	2	61
Assam	State	33	14	133
Bihar	State	38	40	243
Chandigarh	Union Territory · no Assembly	1	1	n/a
Chhattisgarh	State	27	11

Where this data came from

India district boundaries (Census 2011 codes, post-2019 UT reorganisation)
community derived
Publisher:
udit-001/india-maps-data (derived from DataMeet Community Maps)
Licence:
Open Data Commons ODbL 1.0 (verify before production use)
Retrieved:
28 Aug 2026, 7:05 pm
Checksum:
e724c14bc5ee68bc
https://raw.githubusercontent.com/udit-001/india-maps-data/main/geojson/india.geojson
Parliamentary Constituencies of India, 2019 delimitation (simplified)
community derived
Publisher:
DataMeet Community Maps
Licence:
Open Data Commons ODbL 1.0 (verify before production use)
Retrieved:
28 Aug 2026, 7:05 pm
Checksum:
54840686c3c5ceab
https://raw.githubusercontent.com/datameet/maps/master/parliamentary-constituencies/india_pc_2019_simplified.geojson

What has to happen before this is authoritative

1Obtain constituency boundaries published by the Election Commission of India, including the current Assembly delimitation for every State.
2Verify the depiction of international and State boundaries against Survey of India publications.
3Have a named person record the verification, with the date and what was checked.
4Promote the version to ACTIVE through a two-approver request, which is itself audited.
5Retain this version permanently, so historical issues still resolve against the boundaries in force when they were raised.

Ingestion last run 28 Aug 2026, 7:05 pm. Rerun with npm run geo:ingest. See Legal & Compliance for the wider position.