Wikidata:Property proposal/District
District edit
Originally proposed at Wikidata:Property proposal/Place
Not done
| Represents | electoral unit (Q192611) |
|---|---|
| Data type | Item |
| Domain | Administrative division |
| Example | Thanjavur (Q41496) or Pattukkottai Assembly constituency (Q7148673) |
| See also | en:List_of_districts_in_India Again for assembly constituency too we need to add district in [1] qualifier electoral district (P768); property located in the administrative territorial entity (P131) |
- Motivation
Currently we use property located in the administrative territorial entity (P131) but this often confusing. Should have seperate property to identify the place by its division. Thanks -- Mdmahir (talk) 09:11, 12 March 2017 (UTC)
- Discussion
Support as "electoral district of place". It would have the same values as the qualifier electoral district (P768), but be applied to places in countries where located in the administrative territorial entity (P131) aren't of much use, due to Gerrymandering and other issues.
--- Jura 10:19, 18 March 2017 (UTC)
Oppose No evidence is given as to why located in the administrative territorial entity (P131) and/ or electoral district (P768) are not adequate. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:20, 19 March 2017 (UTC)- Currently, the suggested datatype "string" doesn't seem to make sense to me. As far as the example goes, an example is supposed to say which items is supposed to be mapped to which other item. I also share Pigsonthewing's concerns that no reasoning is given why the existing properties don't do the job, so
Weak oppose. ChristianKl (talk) 19:03, 25 March 2017 (UTC)
- Yeah, string makes no sense. I changed it to item.
--- Jura 19:08, 25 March 2017 (UTC)
- Yeah, string makes no sense. I changed it to item.
- @Mdmahir: Please can you respond to the query above regarding why the existing properties don't work and also provide an example of how the property will be used (not just examples of items it will be used on). Thryduulf (talk) 21:09, 14 April 2017 (UTC)
- Oppose use located in the administrative territorial entity (P131) --Pasleim (talk) 07:10, 2 June 2017 (UTC)
- Support per Jura. Mahir256 (talk) 21:47, 19 June 2017 (UTC)
Comment I'm not sure this is really useful. Where I live (in New York State, USA) there are (at least) 6 separate "electoral districts" in play: the local party committee electoral district, the town council district, the county legislature district, the state legislature and state senate districts, and the federal congressional district. I believe there are also school, library, and fire department districts. These districts are not nested, their boundaries overlap - except I believe at the lowest "party committee district" level which do have uniform town, county, state, and federal representation across the local district. The local districts are very specific - people on one side of a street may be in one, while those on the other side in another. They may have holes in them (the one I live in contains a big hole for a separate local district for a gated community). And all of these districts may change over time - at least every ten years following a census. I don't even know what wikidata item you would attach a property like this to to have a reasonably accurate mapping of the reality of these districts - on a building-by-building basis? This doesn't seem realistic to include in wikidata at least as it is now structured. ArthurPSmith (talk) 18:50, 20 June 2017 (UTC)
- I would imagine that if an elected body represents a given area, every 1st-level division of that area should have this property with values being the districts of that area. For example, Illinois (Q1204) -> Illinois's 1st congressional district (Q3401698) through Illinois's 26th congressional district (Q5999287) (qualified with start time (P580) and end time (P582) as appropriate), since the United States House of Representatives (Q11701) represents the entire United States. Champaign County (Q110187) -> (whatever state senate and house districts are part of that county), since the components of the Illinois General Assembly (Q1437547) represent the entire state of Illinois. Urbana (Q462184) -> (whatever county legislature districts/precincts are part of that city), for a similar reason.
- As to the issue of borders, those should be resolved within the district items themselves, perhaps through links to KML files delineating those districts at appropriate points in time. Mahir256 (talk) 20:07, 20 June 2017 (UTC)
- I don't see how this represents useful structured information. Having properties on the district (including say a KML file mapping its boundaries) would make more sense to me - located in the administrative territorial entity (P131) on the district for example would satisfy the relationship between Illinois and all of its congressional and other electoral districts and seems more useful than having this as an inverse property. ArthurPSmith (talk) 17:55, 21 June 2017 (UTC)
- Oppose, use located in the administrative territorial entity (P131). Queries can find particular types of entities as necessary. --Yair rand (talk) 23:52, 3 August 2017 (UTC)
- @Yair rand, ArthurPSmith, Mahir256, Pasleim, Mdmahir, Jura1: Not done, stale and more opposing votes than support. ChristianKl (talk) 00:23, 2 November 2017 (UTC)
- I am fed up here to propose new properties. People should learn something about Geography of India before they vote. Please refer en:List_of_districts_in_India India have states and each states have its own districts and each districts have its own Administrative high ranking officer called Collectors. Each districts have many Parliaments constituency and legislative constituencies. Do we have Indians (or Asian) contributors here to explain all these. why you need voting for basic things? -- Mdmahir (talk) 14:31, 30 November 2017 (UTC)