Property talk:P4530
Jump to navigation
Jump to search
Documentation
Bangladesh administrative division code (pre-2017)
code used for an area for census calculations in Bangladesh
code used for an area for census calculations in Bangladesh
Description | code used for an area for census calculations in Bangladesh | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Associated item | Bangladesh Bureau of Statistics (Q2882475) | ||||||||||||
Data type | External identifier | ||||||||||||
Domain | According to this template:
divisions, districts, subdistricts, union councils, municipalities, and villages in Bangladesh
According to statements in the property:
When possible, data should only be stored as statementsadministrative territorial entity (Q56061) | ||||||||||||
Allowed values | \d\d( \d\d( \d\d( \d\d( \d\d\d?( \d\d\d( \d\d)?)?)?)?)?)? | ||||||||||||
Example | Barisal Division (Q459723) → 10 Barishal District (Q1763301) → 10 06 Agailjhara Upazila (Q3346000) → 10 06 02 Bagdha Union (Q4841524) → 10 06 02 13 Ambala (Q4740953) → 10 06 02 13 019 | ||||||||||||
Source | According to this template:
Bangladesh Population and Housing Census 2011, Community Report: Barisal Zila (Q21973589), the 63 other related reports, and data from past censuses
According to statements in the property:
When possible, data should only be stored as statementshttp://bbs.gov.bd | ||||||||||||
Related to country | Bangladesh (Q902) (See 9 others) | ||||||||||||
See also | Bangladesh administrative division code (2017-) (P6895) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “
List of violations of this constraint: Database reports/Constraint violations/P4530#Format, hourly updated report, SPARQL\d\d( \d\d( \d\d( \d\d( \d\d\d?( \d\d\d)?)?)?)?)?
”: value must be formatted using this pattern (PCRE syntax). (Help)Item “country (P17): Bangladesh (Q902)”: Items with this property should also have “country (P17): Bangladesh (Q902)”. (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/P4530#Item P17, search, 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/P4530#Type Q56061, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P4530#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P4530#Single value, hourly updated report, SPARQLAllowed 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/P4530#Entity types
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Some notes when using this property
[edit]- For consistency across time periods, it is appropriate to encode the division even where some sources do not explicitly add the division number to the start of the code. This necessarily also requires that for Barisal, Rangpur, and Sylhet Divisions, two codes must be present per administrative entity within those divisions, one (to be marked deprecated) for the original division a certain entity was in and one (with either original or preferred rank) for the new division the entity is in. (This, of course, does not mean those three newer divisions themselves get two codes.)
- As yet there is no official geocode for Mymensingh Division, given that it was created after the latest updates to the geocoding scheme. For this reason, until the 2021 census (or until the geocoding scheme is officially revised, whichever comes first), these should be marked (normally) as being part of Dhaka Division ("30"). A similar policy also applies to the proposed Comilla and Faridpur Divisions with respect to Chittagong ("20") and Dhaka ("30") Divisions respectively should those proposed divisions be created in the meantime. Once one of the aforementioned events occurs, the original code should be marked deprecated and another code added with the revised division number.
- All other code changes resulting from changes in the district/upazila that contains a union/village should be dated to the specific census in which the code is recorded (unless the changes to the codes themselves are explicitly noted as having occurred between the censuses). Mahir256 (talk) 07:05, 5 March 2018 (UTC)
Categories:
- Bangladesh-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with format constraints
- Properties with constraints on items using them
- Properties with constraints on type
- Properties with unique value constraints
- Properties with single value constraints
- Properties with entity type constraints