Village Codes information
LGD Code vs Census Village Code: Detailed Comparison
LGD codes and Census village codes are not the same thing. Both can identify a village-related record, but they come from different systems, are maintained for different purposes and can reflect different administrative structures.
The safest approach is to keep the two identifiers in separate fields. Use the LGD code when you need the current Local Government Directory record, and use a Census code when you are working with Census geography or historical Census data.
Quick comparison
| Point | LGD code | Census village code |
|---|---|---|
| Main system | Local Government Directory | Census reference geography |
| Main purpose | Current administrative and local-government identification | Identification within a Census reference structure |
| Time reference | Can reflect administrative updates after a Census year | Tied to a Census reference such as Census 2011 |
| Village page use | Primary current identifier on Village Codes | Historical/supporting cross-reference when available |
| Can the number match? | Yes. Matching digits do not make the two systems identical. | |
| Can one be missing? | LGD code is required for an LGD village record | A usable Census cross-reference may be absent |
What is an LGD village code?
An LGD village code identifies a village record in the Local Government Directory. LGD is used to organise administrative and local-government entities such as States and Union Territories, districts, sub-districts, villages, development blocks and local bodies. Because LGD is maintained as administrative structures change, it is the main current identifier used on Village Codes.
What is a Census village code?
A Census village code identifies a village in the geography used for a particular Census reference. A Census 2011 village code is therefore best understood as a historical reference to Census 2011 geography. It can be valuable when linking an LGD village to Census tables, village amenities, population information or other datasets organised using Census identifiers.
Why can LGD and Census codes differ?
Administrative geography does not remain fixed forever. A village may be reorganised, moved between administrative units, split, merged or represented differently after the Census reference year. LGD can reflect later administrative arrangements, while a Census 2011 code continues to refer to the Census 2011 structure. For that reason, the two codes can differ even when they refer to a place with the same or very similar name.
Why can the numbers sometimes be the same?
Some source records contain the same numeric value in both fields. Village Codes still labels them separately. The meaning comes from the system and field name, not only from the digits. A number recorded as an LGD village code remains an LGD identifier; the same digits recorded as a Census 2011 code remain a Census reference.
Why is a Census code sometimes not shown?
A current LGD record does not always carry a usable Census cross-reference. The source can contain an empty value or a zero-filled placeholder such as 000000. Village Codes treats those values as unavailable. Showing 000000 as if it were a genuine Census village code would be misleading.
For example, if an LGD village row has a valid LGD code but its Census 2011 field is 000000, the page will keep the LGD code and state that no usable Census 2011 code is available in the source snapshot.
Which code should you use?
- Use the LGD code when your work is based on current LGD administrative records, Panchayat/local-body systems, current village directories or datasets that explicitly request an LGD identifier.
- Use the Census code when you are matching data to Census 2011 tables, historical Census village profiles or another source that explicitly uses Census geography.
- Keep both when building a crosswalk between current administrative data and historical Census data.
Practical use cases
1. Linking Census statistics to a current village directory
A researcher may have Census 2011 population data keyed by Census village code and a current administrative dataset keyed by LGD code. A verified cross-reference allows the researcher to retain both identifiers without pretending that one replaces the other.
2. Checking a village after administrative reorganisation
A current village may now sit in a different district, sub-district or State/UT arrangement from the one used in 2011. The current LGD hierarchy should be used for current administrative context, while the historical Census directory helps interpret the older geography.
3. Building data APIs or directories
Applications should store LGD code and Census code in separate columns. This prevents an accidental join where a Census identifier is treated as a current administrative code.
4. Resolving repeated village names
When names repeat, compare the LGD code, State/UT, district and sub-district first. A Census code can then provide an additional historical cross-check where available.
State and Union Territory changes after Census 2011
Census 2011 predates some later administrative changes. Telangana was created as a separate State after Census 2011. Ladakh became a Union Territory after Census 2011. Dadra and Nagar Haveli and Daman and Diu were merged into one Union Territory later. Historical Census directories therefore follow the geography appropriate to the 2011 reference period rather than inventing a new Census 2011 host for a later administrative entity.
Historical Census directories on Village Codes
Village Codes keeps historical Census directories on State/UT subdomains and keeps the current LGD directory on the main domain. This separation is intentional. It helps users understand whether they are looking at a current LGD record or a Census-era reference.
Best practice when matching the two systems
- Start with the exact LGD village code and current hierarchy.
- Use the Census 2011 field only when a usable code is supplied.
- Do not treat blank or all-zero Census values as real codes.
- Check State, district, sub-district and village name when creating a crosswalk.
- Keep the source date and Census reference year with the matched record.
- For official or high-stakes use, verify the match with the relevant government source.
Summary
The LGD code answers, “Which current Local Government Directory record is this?” A Census village code answers, “Which village record was used in this Census reference geography?” They can be related, but they are not interchangeable. Keeping both identifiers clearly labelled makes administrative and historical data safer to use.