Wikidata:Property proposal/Place

Property proposal: Generic Authority control Person Organization
Creative work Place Sports Sister projects
Transportation Natural science Computing Lexeme

See also edit

This page is for the proposal of new properties.

Before proposing a property

  1. Search if the property already exists.
  2. Search if the property has already been proposed.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
  4. Select the right datatype for the property.
  5. Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
  6. Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.

Creating the property

  1. Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
  2. Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
  3. See property creation policy.

On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/02.

Filial church edit

Park edit

Hierarchy of administrative territorial entities edit

Properties proposed in RfC "Countries, subdivisions, and disputed territories" edit

recognition edit

   Under discussion
Descriptioninternational recognition of the statement (use as qualifier for P31, P17, and P131)
Data typeItem
Example 1Armenia (Q399)instance of (P31)sovereign state (Q3624078) → "international recognition of Armenia"
Example 2Crimea (Q7835)country (P17)Russia (Q159) → "recognition of Crimea as a part of Russia"
Example 3Israel (Q801)instance of (P31)sovereign state (Q3624078)international recognition of Israel (Q6055209)

recognized by edit

   Under discussion
Data typeItem
Example 1international recognition of Kosovo (Q23052)United States of America (Q30)
Example 2"recognition of Crimea as a part of Russia" → Sudan (Q1049)
Example 3"international recognition of Armenia" → United States of America (Q30)

not recognized by edit

   Under discussion
Data typeItem
Example 1"international recognition of Armenia" → Pakistan (Q843)
Example 2"recognition of Crimea as a part of Russia" → Italy (Q38)
Example 3international recognition of Kosovo (Q23052)Madagascar (Q1019)

jurisdiction status edit

Motivation edit

These proposed properties are part of a broader proposal at Wikidata:Requests for comment/Countries, subdivisions, and disputed territories. Please comment there. --Yair rand (talk) 07:24, 8 April 2019 (UTC)Reply[reply]

So, this page was specifically not supposed to be the discussion area for the proposals, as mentioned. (See also the lack of a "discussion" section on this page.) The actual proposal is described on the linked RFC page, and is not described on this page. Many of the comments above do not seem to be regarding the actual proposed properties as described in the RFC. The proposal and discussion area are at Wikidata:Requests for comment/Countries, subdivisions, and disputed territories. This page exists to be a pointer to there. --Yair rand (talk) 04:28, 20 July 2021 (UTC)Reply[reply]

  • @Yair rand: Hi - it's been over 2 years since this proposal and RFC were started; there have been a few comments on the RFC since you last commented here, can you respond and perhaps we can settle where to go from here now? Another editor had marked these as ready but I am not sure on that (but they could be!) ArthurPSmith (talk) 18:29, 17 June 2022 (UTC)Reply[reply]
  • After a member of the WikiProject Human rights had asked me today how to model that citizens of certain countries don't have certain rights, I created the proposal (not) officially recognized by . I embarrassingly missed that this proposal already existed ... however seeing that 1) this proposal has been met with opposition because it suggests "recognition" which can just be modeled with statement is subject of (P805) and "jurisdiction status" ... which can also just be modeled with nature of statement (P5102) & statement disputed by (P1310) and 2) that this proposal has apparently been abandoned it's probably good that I created a new proposal.
So please check out my proposal (not) officially recognized by ... I also have examples for human rights, animal rights, religions and atrocities and suggestions for some property constraints :)
--Push-f (talk) 16:28, 11 December 2022 (UTC)Reply[reply]

associated locality edit

Motivation edit

For municipalities in Austria, there are two types of subdivisions: Cadastral communities and localities and there are two numbering systems: cadastral municipality ID in Austria (P8322) and locality number in Austria (P8384). One may say, that the first is about area and the second about population, but this is a very simple view. A physical settlement like Lippmichl (Q92267797) is part of the locality of Matzelsdorf (Q113818753) and part of the cadastral community of Schönberg (Q113818664). The proposed property will help to model this relation similar to associated cadastral district (P10254). Maincomb (talk) 20:50, 7 September 2022 (UTC)Reply[reply]

Discussion edit

It can be seen as "contains the administrative territorial entity (P150)" or as an inverse form of "located in the administrative territorial entity (P131)". In Austria, localities (= everything that has a locality number in Austria (P8384)) are not administrative entities but historically grown and therefore kind of statistical entities. However, the real statistical entities are the de:Zählsprengel and "located in statistical territorial entity (P8138)" should be used here.
It should be used in both directions, from the municipality to the localities in blocked form like in Q695443#P10254 and from the hamlets etc. to the locality like in Q92267797#P10254. I want to create this section de:Hengsberg#Ortschaften with wikidata. --Maincomb (talk) 22:43, 9 September 2022 (UTC)Reply[reply]
  Comment I would be happier if the proposal only went one clear way. Note that we already have located in statistical territorial entity (P8138), which can be used for items which are not administrative entities; or location (P276) which could be used with a suitable object has role (P3831) qualifier. I would be more happy to see either of those patterns used instead of the present proposal; particularly if the proposal is going to keep the current extremely vague proposed label, which looks doomed to be a confuser for significant place (P7153). Jheald (talk) 16:02, 12 September 2022 (UTC)Reply[reply]
We also now have contains the statistical territorial entity (P10888) which was recently created. Middle river exports (talk) 00:52, 14 September 2022 (UTC)Reply[reply]
In Austria, there are three types of localities (in our language: Ortschaft (Q11183787)): localities, that are represented by Ortschaft (Q11183787), localities, that are represented by locality (Q3257686) and localities, that are not represented in wikidata by now. All three types are called de:Ortschaft, the first ones are maintained by municipalities, the second ones are maintained by the federal Statistical Office of Austria and the third are maintained by the postal service of Austria. One may say administrative localities, statistical localities and postal localities, but these are not terms used in Austria, all is just called "Ortschaft". Here in Wikidata, somebody translated locality number in Austria (P8384) with "locality number" and so we (mis-)use "locality" for all objects with this "locality number" instead of Ortschaft (Q11183787), that is now used for localities maintained by municipalities.
A locality (the type maintained by the federal Statistical Office of Austria) is a cultural, economic, residential, historic, administrative and political unit and the Statistical Office sets a statistical view on it. So it is not a statistical entity, but there are data about it. (Localities can extend across municipality boundaries, change their name, united ... so it in not fully usable as statistical entity.)
The Statistical Office of Austria has grid data, census districts, postcodes, localities (mentioned above) and customer defined polygons, as you can see here. All this are artificial units. Then, there are physical units (villages, hamlets, dispersed settlements and some other types where I cannot find an english translation) which also have their statistics and could use location (P276) and contains the statistical territorial entity (P10888) with a object has role (P3831) qualifier. Example: The village of "Puchberg am Schneeberg" only exitsts once, but in wikidata it is represented with different roles: as municiplaity: Puchberg am Schneeberg (Q666478), als cadastral community: Puchberg am Schneeberg (Q113453804), as locality: Puchberg am Schneeberg (Q113453806), and as settlement: Puchberg am Schneeberg (Q113453925).
So all this would be mixed up. It will be easy to make mistakes and it will be hard to find them. What is about maintenance, when one cannot see what to do? And most important: I want to use this list within articles as shown in sl:Zgornji_Osek,_Avstrija#Naselja_v_občini (bulleted list below "Naselji Zgornji Osek so:"). So I want to keep it simple like with associated cadastral district (P10254), where it is clear what to put in and what will come out.
The descriptions of location (P276) and significant place (P7153) do not look proper for my intention. Properties like located in statistical territorial entity (P8138) and contains the statistical territorial entity (P10888) should be used with real statistical territorial entities like grid data and census districts as mentioned above. --Maincomb (talk) 19:43, 14 September 2022 (UTC)Reply[reply]
Could you draw a map showing the relationships between Lippmichl, Matzelsdorf, Hengsberg, Schönberg and Leibnitz District? 2A01:CB14:D52:1200:1543:584A:DA25:6ADD 15:29, 24 April 2023 (UTC)Reply[reply]
I can draw a scheme of Hengsberg (municipality), its six cadastral communities, nine localities and many settlements:
Hengsberg (municipality)
  • Fliessing (cadastral community)
    • Flüssing (locality)
      • Flüssing (settlement)
      • Kleinflüssing (settlement)
  • Hengsberg (cadastral community)
    • Hengsberg (locality)
      • Hengsberg (settlement)
  • Komberg (cadastral community)
    • Komberg (locality)
      • Froschberg (settlement)
      • Komberg (settlement)
      • Voregg (settlement)
  • Kühberg (cadastral community)
    • Kühberg (locality)
      • Guglitz (settlement)
      • Kühberg (settlement)
      • Similipp (settlement)
  • Schönberg (cadastral community)
    • Kehlsdorf (locality)
      • Kehlsdorf (settlement)
      • Schloss Freybühel (settlement)
    • Matzelsdorf (locality)
      • Lippmichl (settlement)
      • Matzelsdorf (settlement)
      • Schatzmühle (settlement)
    • Schönberg an der Laßnitz (locality)
      • Schönberg an der Laßnitz (settlement)
  • Schrötten (cadastral community)
    • Leitersdorf (locality)
      • Leitersdorf (settlement)
    • Schrötten an der Laßnitz (locality)
      • Hofbauer (settlement)
      • Holzbauer (settlement)
      • Schrötten an der Laßnitz (settlement)
      • Wolf (settlement)
Example: Lippmichl is a (small) settlement within the locality of Matzelsdorf. The locality of Matzelsdorf consists of Matzelsdorf itself as settlement, Schatzmühle and Lippmichl as two small settlements. Matzelsdorf is a part of the cadastral community of Schönberg. The cadastral community of Schönberg consists of the localities of Kehlsdorf, Matzelsdorf and Schönberg an der Laßnitz and its settlements within these localities.
I hope this helps to understand the problem of modeling the structure of our municipalities. --Maincomb (talk) 10:16, 1 May 2023 (UTC)Reply[reply]
Thank you very much. 2A01:CB14:D52:1200:D98F:331A:7FE2:BB10 15:17, 1 May 2023 (UTC)Reply[reply]
There is also contains settlement (P1383). It would be useful a template with these properties, like Template:Location properties. Bean49 (talk) 09:33, 24 April 2023 (UTC)Reply[reply]

  Support I now use location (P276) because there is no located in the administrative territorial entity (P131)/contains the administrative territorial entity (P150) for non-administrative territorial entities. I think "associated non-administrative territorial entity" would be even better. --Ruderblatt (talk) 06:50, 24 July 2023 (UTC)Reply[reply]

Code de la collectivité territoriale ayant les compétences départementales edit

   Under discussion
Data typeIdentifiant externe-invalid datatype (not in Module:i18n/datatype)
Example 1Département de l'Ain (Q123220878) : 01D
Example 2Collectivité de Corse (Q17050) : 20R
Example 3Métropole de Lyon (Q16665897) : 69M
Example 4Collectivité territoriale de Martinique (Q19543847) : 972R

Motivation edit

Le code de la collectivité territoriale ayant les compétences départementales est un code attribué par l'INSEE depuis 2021 pour désigner les collectivités territoriales exerçant les compétences d'un département, actuellement au nombre de 100. Cette propriété viendra compléter le panel des codes Insee pour les subdivisions administratives françaises : code Insee d'une commune (P374), code Insee d'un canton (P2506), code Insee d'une région (P2585), code Insee d'un département (P2586), code Insee d'un pays ou territoire étranger (P3422), code Insee d'un arrondissement départemental (P3423). Arpyia (talk) 09:38, 21 January 2024 (UTC)Reply[reply]

  Notified participants of WikiProject France

Discussion edit

Street edit

Body of water edit

Geographic location edit

‎population by ethnic group edit

   Under discussion
DescriptionPart of a larger population isolated for statistical analysis
Data typeQuantity
Allowed valuespositive integers and 0
ExamplePrishtina (Q25270) → 426; point in time (P585) → 1961; ethnic group (P172)Macedonians (Q2436423)
See alsopopulation (P1082), male population (P1540), female population (P1539)

Motivation edit

Ethnic group is a very important linguistic and cultural property, strongly related to first language (Q36870) spoken. Even Wikidata is available in multiple languages. Many statistical offices publish data for this property.

The usage for this property would be the same as for population (P1082), with mandatory qualifier ethnic group (P172).

I think it is more important and more relevant to store this information on Commons in json. --Bean49 (talk) 12:35, 3 May 2023 (UTC)Reply[reply]

Discussion edit

Neighborhood edit

Architectural structure edit

Outer space edit

Please visit Wikidata:WikiProject Space for more information. To notify participants use {{Ping project|Space}}

Other edit

‎FBI UCR data edit

   Under discussion
DescriptionFBI UCR statistics
RepresentsUniform Crime Reporting Program (Q438714)
Data typeTabular data
Template parameteryear, homicide, forcible_rape, robbery, aggravated_assault, violent_crime, burglary, larceny_theft, motor_vehicle_theft, arson, property_crime in en:Template:Infobox UCR
DomainAtlantic City (Q139564) and all other American cities
Allowed valuesnumber
Allowed unitscrime (L3961)
Example 1{{FBI UCR statistics| |year=2007 |homicide=15.1 |forcible_rape=70.4 |robbery=1,146.3 |aggravated_assault=930.1 |violent_crime=2,161.9 |burglary=1,370.0 |larceny_theft=5,422.2 |motor_vehicle_theft=502.8 |arson=40.2 |property_crime=7,335.2}}
Example 2
Example 3
Source etc. →

Motivation edit

Self-evident. Psiĥedelisto (talk) 09:33, 2 April 2023 (UTC)Reply[reply]

Discussion edit

‎located in IANA time zone edit

   Under discussion
Data typeItem
Example 1Cairo (Q85) : Africa/Cairo (Q4689484)
Example 2Indianapolis (Q6346) : America/Indiana/Indianapolis (Q4742656)
Example 3San Francisco (Q62) : America/Los_Angeles (Q4742667)

Motivation edit

An IANA time zone is a time zone that contains only places for which the offset from UTC was the same since 1970. If a change in offset from UTC for such a zone exists it can be recorded in the IANA time zone item.

If IANA is correct all claims about UTC offsets that currently exist on items, including differences between summer and winter for some regions, and relate to data after 1970 can be stored in the IANA zone item and be removed from individual items.

When the EU abandons daylight saving time, the change can be added to Wikidata by editing only ~30 IANA zones (for EU countries) instead of thousands or millions of individual items.

Much less unsourced original research if UTC offsets are stored on time zone items instead of place items.

Discussion edit

TNHR&CE Temple ID edit

   Under discussion
Descriptionidentifier for temples, mutts, charitable endowments and specific endowments supervising by TNHR&CE
Data typeExternal identifier
Domaininstance or subclass of (Q30208840) : Hindu temple (Q842402) : Jain temple (Q2613100), Matha (Q2069741) (Mutt), Charitable Endowments (we don't have any specific item for it), Specific Endowments (we don't have specific any item for it) financial endowment (Q2620430)
Example 1Kapaleeshwarar Temple (Q1587164) → TM000001
Example 2Trilokyanatha Temple (Q26833741) → TM002710
Example 3Embar Jeeyar Mutt (Q124621722) → TM003452
Number of IDs in sourceWithout endowments: 43,761
With endowments: 46,153

Motivation edit

The Goverment of Tamil Nadu (Q1445) Hindu Religious and Charitable Endowments Department supervising Temples and other Hindu and Jain religious buildings in Tamil Nadu. This IDs helps identify the Wikidata items of temples and mutts maintaining by Hindu Religious and Charitable Endowments Department (Q12974460). This contains Hindu temples, Jain temples and mutts, Additionally contains Charitable Endowments and Specific Endowments. We don't have much Endowments (for Tamil Nadu) items in Wikidata, So I think this not compulsory to include in the property, But I would like add this in the proposal. Thank you --Sriveenkat|talk/{PING ME} 17:36, 20 February 2024 (UTC)Reply[reply]

Discussion edit