Property talk:P5578

From Wikidata
Jump to navigation Jump to search

Documentation

Indian census area code (2011)
code used for an area for calculations in the 2011 census of India
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5578#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5578#Unique value, SPARQL (every item), SPARQL (by value)
Format “\d{2}|\d{3}|\d{5}|\d{2}.\d{4}|[0-7]\d{5}|[8-9]\d{5}(.\d{4})?: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5578#Format, SPARQL
Type “administrative territorial entity (Q56061): item must contain property “instance of (P31)” with classes “administrative territorial entity (Q56061)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5578#Type Q56061, SPARQL
Item “country (P17): India (Q668): Items with this property should also have “country (P17): India (Q668)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5578#Item P17, search, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5578#Entity types

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Some notes about this property[edit]

  • State codes are of length 2, district codes of length 3, and divisions below the tehsil/taluk/etc. level of length 6.
  • Some considerations must be made at the tehsil/taluk/level, however; for some states, such as Uttar Pradesh, each district is divided into subdistricts (tehsil) and also into development blocks (vikas khand), each with its own code (of length 4 for subdistricts and of length 5 for development blocks), while for other states, such as West Bengal, no such division exists, yet each has codes of length 4 and of length 5. The codes of length 5 are unique, while the codes of length 4 are specific to the state in which the subdistrict is located--i.e. '0040' refers to different entities in Bihar and in Jharkhand. It is therefore appropriate, for those subdistricts in states lacking the sorts of divisions exemplified by the Uttar Pradesh example, to qualify census codes on those items with of (P642) to separate their scopes.
  • Codes of length 6 with value below 800000 should be marked as villages unless they are denoted otherwise (census towns, for example). Codes of length 6 with value 800000 or above should be denoted municipalities/notified areas/cities as appropriate.

Mahir256 (talk) 17:57, 29 August 2018 (UTC)[reply]

Looks like P642 is deprecated, Is there another way to separate the two census codes available for CD blocks of states like West Bengal?
Is it appropriate to create a new property "Indian census block code 2011" to represent the 4 digit CD Block codes? RamSeraph (talk) 13:20, 30 October 2023 (UTC)[reply]