Shortcut: WD:PP/PLACE

Wikidata:Property proposal/Place

From Wikidata
Jump to navigation Jump to search


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

See also[edit]

This page is for the proposal of new properties.

Before proposing a property

  1. Check if the property already exists by looking at Wikidata:List of properties (manual list) and Special:ListProperties.
  2. Check if the property was previously proposed or is on the pending list.
  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. Start writing the documentation based on the preload form below and add it in the appropriate section.

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 proposal, by a property creator or an administrator.
  3. See steps when creating properties.

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 2019/01.

Geographic location[edit]

historical region[edit]

   Under discussion
Descriptiongeographic area which at some point in time had a cultural, ethnic, linguistic or political basis, regardless of present-day borders
Representshistorical region (Q1620908)
Data typeItem
Template parameter"země" in cs:šablona:Infobox - sídlo
Domainhuman settlement (Q486972)
Allowed valuesinstance of (P31) historical region (Q1620908)
Example 1Prague (Q1085)Bohemia (Q39193)
Example 2Brno (Q14960)Moravia (Q43266)
Example 3Wrocław (Q1799)Silesia (Q81720)
Example 4Nantes (Q12191)Brittany (Q327)
Planned useInfoboxes, queries
See alsolocation (P276), located in the administrative territorial entity (P131), located in present-day administrative territorial entity (P3842)

Motivation[edit]

Historical regions are sometimes a very strong part of the local identity. Some of them could be a past administrative entity, some of them not.

In my opinion in this case location (P276) is too general, located in the administrative territorial entity (P131) with start time (P580) and end time (P582) qualifiers is inaccurate, as some of these regions were not an administrative entity, but mainly end time (P582) qualifiers in inappropriate, as people still feel to be part of the historical region, even it has been dissolved or divided. Jklamo (talk) 12:08, 14 August 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support this does sound helpful, we seem to get a lot of questions from users about this sort of thing. ArthurPSmith (talk) 19:29, 14 August 2018 (UTC)
  • Symbol support vote.svg Support. Thierry Caro (talk) 20:37, 14 August 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 08:03, 15 August 2018 (UTC)
  • Symbol support vote.svg Support Matěj Suchánek (talk) 14:06, 17 August 2018 (UTC)
  • Symbol support vote.svg Support JAn Dudík (talk) 20:15, 19 August 2018 (UTC) For settlements in the Czechia is it very useful property. Add yes, it should be limited to settlements, because this usually were in one region. JAn Dudík (talk) 12:40, 25 August 2018 (UTC)
  • Pictogram voting comment.svg Comment This could be rephrased as "former region" or "prior region" and potentially cause less bias, but it seems that the cultural identity is important here with a nod about its history, regardless of causing some bias with the term "historical". There are those folks that will elevate this with the idea of "historically important" and we should be careful and mention in its description that the importance of a region is not what this property is about, but that "a region had a prior name and cultural identity that may still remain in part even today". Thadguidry (talk) 14:48, 20 August 2018 (UTC)
    • Historical region as a label was proposed because of historical region (Q1620908) label and its clear definition at en:Historical region as well as enwiki categorization. "former region" or "prior region" are good aliases, but "historical region" is clearly defined and widely used.--Jklamo (talk) 08:47, 22 August 2018 (UTC)
  • Some things to consider:
    • Should use of this be limited to human settlements, as suggested above, or perhaps also be used for provinces and districts and such? (I imagine we want to restrict it somehow, to prevent it being used on every building and territorial entity and natural feature, but I'm not sure that human settlements is the right choice.)
    • Should this property be used even if the former region is already indicated via located in the administrative territorial entity (P131)?
    • What counts as a historical region? Should this include every single former country or geopolitical unit of any level that has covered that spot?
    • Should this be used for settlements that no longer exist, to point to historical regions that also no longer exist?
  • --Yair rand (talk) 22:56, 20 August 2018 (UTC)
    • (As these points remain unclear, I Symbol oppose vote.svg Oppose creating this for the time being.) --Yair rand (talk) 21:11, 16 October 2018 (UTC)
  • Symbol oppose vote.svg Oppose Statement on Wikidata generally aren't time-bound. It's better to use the existing ways of specifying regions and with appropriate qualifiers. Maybe we even need new ways to qualify a new type of regions, but I don't think going over time is the right way. ChristianKl❫ 16:19, 23 August 2018 (UTC)
  • Symbol oppose vote.svg Oppose loose term. When the entity was of the administrative kind, it should be used located in the administrative territorial entity (P131) with qualifiers. When not... I guess location (P276) does the job here. strakhov (talk) 12:53, 24 August 2018 (UTC)
  • Symbol oppose vote.svg Oppose I think located in the administrative territorial entity (P131) will work very well, with the appropiate qualifiers. --Giovanni Alfredo Garciliano Díaz diskutujo 16:14, 3 September 2018 (UTC)
  • Symbol oppose vote.svg Oppose per the above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:40, 12 October 2018 (UTC)
  • Symbol support vote.svg Support Cwf97 (talk) 17:08, 16 October 2018 (UTC)
  • Symbol support vote.svg Support Useful for Incubator, we the Incubator users wanna it, please send petition emails to those oppose users above, to convert their unfair opposition of developing Incubator supports to fair supports. --Liuxinyu970226 (talk) 14:20, 20 October 2018 (UTC)
  • Symbol oppose vote.svg Oppose I don’t see how this is needed when we can say “location” or “located in administrative territory” = some historical region, with start and end times. In any case, if we have this property it should be called “located in historical region”. - PKM (talk) 01:35, 1 December 2018 (UTC)
    • @PKM: There is a problem with your solution. It is still located in this historical region. It did not cease to be located there; the region is just not administratively recognized any more. Sometimes, the region was never administrative in the first place. Understand it as "located in non-administrative entity". --Vojtěch Dostál (talk) 13:50, 16 January 2019 (UTC)
      • Symbol support vote.svg Support Okay, I'm convinced. - PKM (talk) 20:29, 16 January 2019 (UTC)

taxa found at location[edit]

   Under discussion
Descriptionplant or animals taxon described as present in location. Requires reference.
Data typeItem
Domainitem for geographic location (<20 values) or item for biology of geographic location. Not countries or first level administrative divisions.
Allowed valuestaxon if statement includes a reference. References used should cover a limited number of taxa (e.g. Flamingos) or specific locations (a bog).
Example 1Crawford Bog (Q56693695) -> Sarcophagidae (Q978302) reference Q56695871 p. 9
Example 2Crawford Bog (Q56693695) -> Sarracenia leucophylla (Q1752921)
Example 3Crawford Bog (Q56693695) -> Sarracenia flava (Q1499289)
Example 4Crawford Bog (Q56693695) -> Sarracenia psittacina (Q1624202)
Example 5Crawford Bog (Q56693695) -> Drosera filiformis (Q366314)
Example 6Africa (Q15) -> lion (Q140)
Sourcedocument used as reference
Expected completenessalways incomplete (Q21873886)
See alsotaxa protected

Motivation[edit]

Following discussion at Wikidata_talk:WikiProject_Taxonomy#Location_survey. @Brya, Succu: thanks for your input. (Add your motivation for this property here.) --- Jura 12:11, 13 October 2018 (UTC)

Discussion[edit]

  • Pictogram voting comment.svg Comment. The extent of this new property should be discussed beforehand. Should species kept (P1990) keep species in protected areas or should its focus be reduced back to zoos only? Thierry Caro (talk) 17:34, 13 October 2018 (UTC)
    • Protected areas generally don't "keep" any species, all present are protected. I think this property should work there. The sample bog above is located in a protected area. --- Jura 18:20, 13 October 2018 (UTC)
  • Pictogram voting comment.svg Comment. I'd have slightly different use - protected areas often list the species which are specifically protected there. However, that list can become quite lengthy, e.g. the official announcement for Doi Phu Kha non-hunting area (Q28104754) lists 170 species [1]. Ahoerstemeier (talk) 21:08, 6 November 2018 (UTC)
    • I see. I'm wondering if this should be handled with a qualifier, P1990, or a new location specific property. Supposedly a species could be protected without actually being present. --- Jura 17:26, 7 November 2018 (UTC)
    • @Ahoerstemeier: given the last point, I think we should have another, separate property for these. What do you think? --- Jura 05:02, 12 November 2018 (UTC)
    • I created a separate proposal for that taxa protected. --- Jura 09:15, 17 November 2018 (UTC)

Who's on First ID (WOFID)[edit]

   Under discussion
DescriptionIdentifier from the Who's on First database. Who's On First is a gazetteer of all the places in the world.
RepresentsWho's on First (Q57967241)
Data typeExternal identifier
Domainitem (instances of geographic location (Q2221906))
Allowed values[1-9]\d*
Example 1New York City (Q60)85977539
Example 2Helcmanovce (Q1186980)101843889
Example 3Čebovce (Q338024)101785253
Example 4Gaël (Q216544)101883255
Sourcehttps://www.whosonfirst.org/
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Number of IDs in source26 million
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://spelunker.whosonfirst.org/id/$1/

Motivation[edit]

Who's on First already includes wikidata in the concordances. Adding this property would add a reverse reference from Wikidata to Who's on First. The entire Who's on First database can be downloaded so a bot could be created to import all of the external ids into Wikidata. U+1F360 (talk) 03:00, 30 October 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support David (talk) 07:06, 30 October 2018 (UTC)
  • Symbol oppose vote.svg Oppose for now. At first sight this is a very useful resource. But, for example, they link their 101750467 to Birmingham (Q2256); and not their 85684283. This is the opposite of what one would expect (compare the two shape files), and could cause problems for us in future. [As an side, I'm a Birmingham resident born and bred, and do not recognise the former boundary in any context.] Some analysis of the frequency of such issues, and how to resolve them, is needed before we decide whether to make his property. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:47, 30 October 2018 (UTC)
@Pigsonthewing: I didn't mean to imply that Who's on First is a source of truth. I think it's totally acceptable if we decide that the id should be different, or if we have multiple ids (as in, one Wikidata item relates to multiple WOFIDs) --U+1F360 (talk) 13:50, 30 October 2018 (UTC)
@Pigsonthewing: To be fair, 101750467 is a locality where 85684283 is a region. Regardless of the map (which I agree is wrong), Birmingham (Q2256) says that it is a city, so the proper link (in my opinion) would be 101750467. U+1F360 (talk) 14:03, 30 October 2018 (UTC)
  • I would like to see in the property description a bit of information about what kind of website whosonfirst happens to be. ChristianKl❫ 13:25, 10 December 2018 (UTC)
@ChristianKl: I added a link to https://www.whosonfirst.org in the description. The dataset used to be a part of Mapzen, but this dataset has been spun off into it's own project which is part of the Linux Foudnation. More information on the dataset can be found at: https://www.whosonfirst.org/what/ U+1F360 (talk) 18:18, 13 December 2018 (UTC)
@U+1F360: The description field doesn't allow for wikitext or other formatting. I just want a one sentence description of the kind of data that it contains. ChristianKl❫ 11:21, 14 December 2018 (UTC)
@ChristianKl: Done! U+1F360 (talk) 14:02, 14 December 2018 (UTC)

Hierarchical administrative subdivision codes[edit]

   Under discussion
Descriptioncodes to represent names of country subdivisions
RepresentsHierarchical Administrative Subdivision Code (Q3013341)
Data typeString
Domainadministrative territorial entity (Q56061)
Example 1DE.NW.BE → Kreis Bielefeld
Example 2DE.NW.CE → Kreis Coesfeld
Example 3DE.BW.EM → Landkreis Emmendingen
Source[2]
Number of IDs in source41,000
Expected completenesseventually complete (Q21873974)
See alsoStatoids ID (P3175)

Motivation[edit]

en:Hierarchical administrative subdivision codes (HASC) are codes to represent names of country subdivisions, such as states, province, regions. It would be very cool to use this in wikidata. Stefan Kühn (talk) 15:55, 10 November 2018 (UTC)

Discussion[edit]

  • Pictogram voting comment.svg Comment These are not a recognized standard as far as I can see. How do they compare with ISO 3166-2? (for which we have ISO 3166-2 code (P300). ArthurPSmith (talk) 20:00, 12 November 2018 (UTC)
  • Answer HASC goes depper then ISO 3166-2. For example Alabama has "US-AL" in ISO 3166-2. For the Chilton County, Alabama there is nothing in ISO. HASC had this: "US.AL.CI". So you get an easy identifier for this county. If you look at Wikidata Q111266 for the identifier, there is nothing so easy like this. The identifiere there are all huge numbers or so. - An other positiv thing about HASC is the 2 letter design. For example ISO 3166-2:AT say "Steiermark"="AT-6". In HASC it is "AT.ST". Easy to use and easy to learn. -- Stefan Kühn (talk) 16:54, 15 November 2018 (UTC)
  • Who uses those codes? ChristianKl❫ 19:31, 14 November 2018 (UTC)
  • Answer I don't know. I used HASC in this project c:Commons:Brück & Sohn for the sorting of all this postcards in counties. Today I use it for some other projects. - I found some other maybe-users: Link1, Link2, very interesting: Link3 (cite: "Due to shortcomings of related de-jure standards a hierarchical set of subdivision codes, called Hierarchical Administrative Subdivision Codes (HASC), has been devised, extending in many cases to secondary administrative divisions.") - Someone insert HASC in Openstreetmap (at the moment only for Tunisia). -- Stefan Kühn (talk) 17:15, 15 November 2018 (UTC)

exonym[edit]

   Under discussion
Descriptionname given to an entity in a language that is not the official language of the place or country of this entity (useful if the entity changed its name at some point and using the label could cause an anachronism)
Representsexonym (Q81639)
Data typemonolingual text or lexeme-invalid datatype (not in Module:i18n/datatype)
Domainplaces, organizations
Example 1Examples can be found for example here : https://en.wikipedia.org/wiki/Geographical_renaming#Exonyms_and_endonyms
Example 2MISSING
Example 3MISSING
Planned useavoid anachronism in infoboxes, per community demands
See alsoofficial name (P1448) View with SQID

Motivation[edit]

As stated in the description, some entity change their names. We handle this with official name (P1448) View with SQID in the native language of the entity, but we don’t have an equivalent for names in different countries. author  TomT0m / talk page 14:40, 13 November 2018 (UTC)

see also
a discussion in Project chat Wikidata:Project_chat/Archive/2018/11#Questions_about_names_:_«_unofficial_»_names_given_by_foreigners_and_the_future_of_names_in_the_lexeme_era ( pinging participants @Jmabel, AnonMoos: ) author  TomT0m / talk page 09:15, 14 November 2018 (UTC)

Discussion[edit]

  • Pictogram voting comment.svg Comment Would you consider having this as a Lexeme-valued property, rather than monolingual text? ArthurPSmith (talk) 21:21, 13 November 2018 (UTC)
  • Pictogram voting comment.svg Comment I agree it should be lexeme related property. KaMan (talk) 05:11, 14 November 2018 (UTC)
  • Answer @KaMan, ArthurPSmith: Actually I would have sweared I had putted « monolingual text or lexeme » as datatype in the proposal but it seems I did not /o\ Done now

(also Ash Crow
Dereckson
Harmonia Amanda
Hsarrazin
Jura
Чаховіч Уладзіслаў
Sascha
Joxemai
Place Clichy
Branthecan
Azertus
ToJack
Jon Harald Søby
PKM
Pmt
Sight Contamination
MaksOttoVonStirlitz
BeatrixBelibaste
Moebeus
Dcflyer
Looniverse
Aya Reyad
Orr Deanna LeiAnn HeaveLEI
Pictogram voting comment.svg Notified participants of WikiProject Names author  TomT0m / talk page 09:07, 14 November 2018 (UTC)

  • Symbol support vote.svg Support OK, support as lexeme-valued property. Even though there are a lot of examples on the link you give, it would be nice to see some examples laid out explicitly the way you would like them done (also maybe one or two not in English). ArthurPSmith (talk) 15:12, 14 November 2018 (UTC)
  • Pictogram voting comment.svg Comment name (P2561) could generally be used. It avoids debating if the name is an exonym or not. --- Jura 12:50, 15 November 2018 (UTC)
    @Jura1: I’m unconfortable with this solution in this case, there is at least a need to discriminate between several kind of names and the generic property is not enough. A solution to define an exonym could anyway to create a mandatory qualifier « name given by », after all it’s a ternary relationship as an exonym is associated to an entity that gives the name, always. But it could also fit on the lexeme if we use the lexeme datatype which is the consensus at this point - another difference with this property. author  TomT0m / talk page 12:59, 15 November 2018 (UTC)
    What about name (P2561) with qualifier issued by (P2378)? --Pasleim (talk) 18:02, 20 November 2018 (UTC)
  • @TomT0m: Please put in the examples in the way the property is supposed to be used. That information clarifies the proposed semantics of a proposed property. ChristianKl❫ 23:40, 16 December 2018 (UTC)
  • Symbol oppose vote.svg Oppose Given unclearness of the semantics. ChristianKl❫ 19:26, 17 January 2019 (UTC)

river bank side[edit]

   Under discussion
Descriptionposition of an object (i.e. city) at a river depending on flow direction
Representsbank (Q2897058)
Data typeItem
Domaingeographical object (Q618123)
Allowed valuesleft bank (Q27834806), right bank (Q27834918)
Example 1Brodské (Q924922)located in or next to body of water (P206)  Morava (Q179251)left bank (Q27834806)
Example 2Loreley (Q4168)located in or next to body of water (P206)  Rhine (Q584)right bank (Q27834918)
Example 3Munich (Q1726)located in or next to body of water (P206)  Isar (Q106588)left bank (Q27834806) AND right bank (Q27834918)

Motivation[edit]

see https://www.wikidata.org/wiki/Q924922 https://en.wikipedia.org/wiki/Brodsk%C3%A9 (corresponding article in wikipedia) I want to express the statement "Brodské is a small village lying on the left side of the Morava river." in wikidata. In the wikidata article it is expressed with property/ qualifier tributary orientation (P3871). In my opinion the use of tributary orientation (P3871) here is wrong. I want to have a new property to substitute the qualifier P3871 in this article.

Rio.Negro (talk) 15:34, 17 November 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg SupportMichaelSchoenitzer (talk) 22:01, 17 November 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 07:43, 18 November 2018 (UTC)
  • Symbol oppose vote.svg Oppose, remodel P3871, and make that more general, for canals, railways etc., and expand the allowed values accordingly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:42, 18 November 2018 (UTC)
    • P3871 is sometimes (more than 300 times) used as a property (Surprisingly for me) - example Alz (Q450584). That is one reason for me why P3871 should not be generalized. (But if you have a good idea, then let's talk about it.) The usage for the new property should be a property qualifier. Rio.Negro (talk) 20:28, 19 November 2018 (UTC)
    • About railways: Normally trains use them in both directions. The usage of left / right is not applicable in that case. I agree that it would be nice to have a property for railways, roads etc, but at the moment I have no idea how to do it. Rio.Negro (talk) 20:28, 19 November 2018 (UTC)
  • Pictogram voting comment.svg Comment. I am under the feeling that located in or next to body of water (P206) itself is a poorly designed property. So I'm reluctant to add qualifiers to that property. Thierry Caro (talk) 18:47, 23 November 2018 (UTC)
  • Symbol oppose vote.svg Oppose P3871 needs to be very slightly remodelled and it will suit well for this purpose, won't it? --Vojtěch Dostál (talk) 13:08, 16 January 2019 (UTC)

taxa especially protected in area[edit]

   Ready Create
Descriptionspecies and other taxons especially protected in a region
Data typeItem
Domainprotected areas (not countries)
Allowed valuesany taxon
Example 1Doi Phu Kha non-hunting area (Q28104754) → some 170 species (see [3])
Example 2Trockenhänge am Donaurandbruch (Q58870700)Yellow-bellied toad (Q606431), Cypripedium calceolus (Q156124), Dicranum viride (Q310409), Lucanus cervus (Q190491), Greater mouse-eared bat (Q723413) (source [4])
Example 3MISSING
See alsotaxa found

Motivation[edit]

Following the discussion at taxa found with @Ahoerstemeier:. The scope would be different from the other proposal, as the values would only be species that are specially protected in an area with a special protection scheme. The species could actually be present or not. This shouldn't be use for state-wide red-lists and the like. (Add your motivation for this property here.) --- Jura 09:20, 17 November 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support As Jura created this proposal because my intended use did not match the related proposal, I of course support it. I just worry if this property is usable for those cases 100+ taxa could be listed, at least the current UI would break... Ahoerstemeier (talk) 14:07, 23 November 2018 (UTC)
  • Symbol support vote.svg Support Could also be used in instances of of biotope (Q175208) --GPSLeo (talk) 09:44, 21 December 2018 (UTC)
    I think, for the related "taxa found" proposal fits better, which however is intended for a specific geographic area, and not a class of them. Ahoerstemeier (talk) 10:03, 21 December 2018 (UTC)

99of9
Achim Raschka (talk)
Brya (talk)
Dan Koehl (talk)
Daniel Mietchen (talk)
Faendalimas
FelixReimann (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
MargaretRDonald
Mellis (talk)
Michael Goodyear
MPF
Mr. Fulano (talk)
Nis Jørgensen
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
Rod Page
Soulkeeper (talk)
Strobilomyces (talk)
Tinm
Tom.Reding
Tommy Kronkvist (talk)
TomT0m
Tubezlob
RaboKarbakian
Circeus
Enwebb
Manojk
Tris T7
Pictogram voting comment.svg Notified participants of WikiProject Taxonomy ChristianKl❫ 22:44, 4 January 2019 (UTC)

linear reference[edit]

   Under discussion
Descriptioncommon way to describe location along a route. 'Linear reference' is defined by operator/authority and might not reflect physical distances (like distance from river mouth does).
RepresentsLinear referencing (Q1741425)
Data typeString
Template parameteren:Template:Routemap
Domainproperty
Example 1Q583999 → km 2.5
Example 2Strasen lock (Q21571320) → km 2.7
Example 3Q1807536 → km 1.94
Planned usenavigable waterways: qualify locks, bridges, marinas
See alsoWikidata:Property_proposal/Place#river_bank_side

Motivation[edit]

my first try: feel free to correct/ extend my proposal DeltaIndiaRomeoKilo-- (talk) 14:20, 30 December 2018 (UTC)

Discussion[edit]

  • Pictogram voting comment.svg Comment Is this used only in certain countries (Germany?) or is it quite universal for items on waterways? Do you want "string" datatype or would quantity be better (which would display as "2.5 km" rather than "km 2.5" for example? ArthurPSmith (talk) 17:11, 2 January 2019 (UTC)
It is quite universal: highways, railways, waterways. I would prefer "string" datatype (since it does not necessarily reflect physical distances). It is a man-made/defined feature to describe a location. --DeltaIndiaRomeoKilo-- (talk) 18:45, 2 January 2019 (UTC)
  • Symbol support vote.svg Support Ok, I think it makes sense - a similar linear reference number is used to indicate road exits in the US, and may be supplemented by a letter (Exit 25B, etc.) though I'm not sure we'd actually have Wikidata items for those points, at least it's plausible the property could be used for that purpose. ArthurPSmith (talk) 17:08, 3 January 2019 (UTC)
  • From reading the description it's not clear to me what the property does. Can you write a descriptions that makes it more easy to assess the meaning? ChristianKl❫ 17:42, 5 January 2019 (UTC)
  • Pictogram voting question.svg Question How do you model the starting point from which this is calculated? If I understood correctly, this works like road milestones (example: incident at the 256th kilometer of Strada Statale 1) --Sabas88 (talk) 21:22, 14 January 2019 (UTC)

located in urban area[edit]

   Under discussion
Descriptionthe settlement is located in the urban agglomeration
Data typeItem
Domainhuman settlement (Q486972)
Example 1Paris (Q90)Paris urban area (Q1081404)
Example 2MISSING
Example 3MISSING

Motivation[edit]

Infoboxes for cities currently often state the population of the urban area in which the city is located. Having this property allows standardized linking of a city with it's urban area. ChristianKl❫ 18:53, 30 December 2018 (UTC)

Discussion[edit]

  • Is this the same thing as a "metropolitan area"? Also, would this be used only for cities, and not other entities located in an urban agglomeration? --Yair rand (talk) 03:05, 31 December 2018 (UTC)
  • @Yair rand: I think it's the same meaning as "metropolitan area" and I'm open to changing the word if others consider that word to be better fitting.
What examples do you have in mind when you speak about other enitties? ChristianKl❫ 11:00, 1 January 2019 (UTC)

vodnimlyny.cz ID[edit]

   Under discussion
Descriptionidentifier in the database of water mills in the Czech Republic
Representswatermill (Q185187)
Data typeExternal identifier
Template parametercurrently none
Domainitems which are instances (or subclass of) water mills
Allowed valuesany number
Allowed unitsnone
Example 1Q12038817671
Example 2Q48604294 → 3759
Example 3Q21019491 → 384
Sourcehttp://vodnimlyny.cz/mlyny/objekty/
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usestart with import from URLs already used in Wikipedia (using Linksearch), then possibly negotiate with database owners
Number of IDs in source7265
Expected completenesseventually complete (Q21873974)
Formatter URLhttp://vodnimlyny.cz/mlyny/objekty/detail/$1

Motivation[edit]

This database is fairly prevalent in Czech Wikipedia's external links and I'd like to centralize links in Wikidata Vojtěch Dostál (talk) 13:33, 16 January 2019 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support good idea --Frettie (talk) 17:17, 16 January 2019 (UTC)
  • Symbol support vote.svg Support Quite complex database of czech water mills. --marv1N (talk) 19:51, 16 January 2019 (UTC)
  • Symbol support vote.svg Support David (talk) 07:55, 17 January 2019 (UTC)

Neighborhood[edit]

Conservation status[edit]

State of conservation / state of use[edit]

   Not done
DescriptionTo indicate state of conservation / state of use of a building, monument, etc. It is not related with its heritage protection (heritage designation (P1435)), but to its present state of conservation or use. Ex.: ruinous, demolished, reformed, correct, abandoned, in use, temporarily closed, etc.
Representsconservation status (Q55553838)
Data typeItem
Template parameterestat_us in ca:template:infotaula edifici.
status in en:template:Infobox_building.
erhaltungszustand in de:Vorlage:Infobox Burg.
stato attuale in it:Template:Infobox stazione della metropolitana.
estado in es:Plantilla:Ficha de túnel
etc.
Domaingeographical object (Q618123), construction (Q811430), human-made geographic object (Q35145743) and its subclasses
Allowed valuesThis property is multi-value. Some exemple, but not exclusives, are:
operatively: in use (Q55654238), open to the public (Q55570821), closed to the public (Q55570340), temporarily closed (Q55653430), closed, ....
conservation: correct, reformed, abandoned, in danger (Q55555088), ruins (Q109607), demolished, destroyed artwork (Q21745157), destroyed settlement (Q22674930), destroyed city (Q14616455), etc.
Some combinations could seems contradictorial, but are possible; for instance: ruins (Q109607) + open to the public (Q55570821) in a archaeological site (Q839954)
Item should be subclass of conservation status (Q55553838).
Possible qualifiers: start time (P580), end time (P582), point in time (P585), applies to part (P518) (when refers to a specific part), but not only.
Allowed unitsN/A
Example 1Parthenon (Q10288) → partially destroyed or ruins (Q109607) + open to the public (Q55570821)
Example 2London Eye (Q160659)in use (Q55654238)
Example 3World Trade Center (Q11235) → value destroyed (P585=2001)
Example 4Casa Vicens (Q746333) → open to the public (P580=2017)
Format and edit filter validationN/A
SourceAs a exemple, but not the only source. In any case, this property may hold an "unofficial" description of a changeable value. So, the sources may be anyone.
Planned useincorporate in building infobox to get WD contents instead to be a manual parameter
Number of IDs in sourceDon't know. Probably, they must be moved from present values in infoboxes
See alsoDiscussion that promoted this proposal

Motivació

Incorporate as a WD property the most popular Infoboxes concepts that are now only available manual parameters. The goal is to be able to get all the common and usual parameters from WD. Amadalvarez (talk) 08:35, 15 July 2018 (UTC)

Discussion

  • Symbol support vote.svg Support Seems like a sensible suggestion. Only thought that came to mind looking at the examples is that a building could have more than one of these - so the London Eye (Q160659) is both "in use" and "Open to the public", but I think that is OK. JerryL2017 (talk) 10:17, 15 July 2018 (UTC)
  • @JerryL2017: Yes, you're right. In fact, "in use" should be an exceptional use, because "no info" should means "normal status", "in use", etc. in order to avoid overload this information. Thanks, Amadalvarez (talk) 20:10, 15 July 2018 (UTC)
  • Symbol support vote.svg Support Very useful. - PKM (talk) 18:37, 15 July 2018 (UTC)
  • Symbol support vote.svg Support. But I think that we should keep generic items for allowed values (i.e. "destroyed" and not destroyed artwork (Q21745157), destroyed settlement (Q22674930), destroyed city (Q14616455)). — Ayack (talk) 11:07, 16 July 2018 (UTC)
    • @Ayack: In fact, my idea is have an open list. I just created a list of possible values to help people to use it, when approval. I agree with you that generics are better. However, the Q21745157, Q22674930, Q14616455 already existed. Thanks, Amadalvarez (talk) 17:59, 19 July 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 11:13, 16 July 2018 (UTC)
  • Symbol support vote.svg Support --Pere prlpz (talk) 21:12, 19 July 2018 (UTC)
  • Symbol support vote.svg Support --Yeza (talk) 06:03, 20 July 2018 (UTC)
  • Symbol support vote.svg Support --Voll (talk) 09:16, 23 July 2018 (UTC)
  • Symbol support vote.svg Support --ChristianSW (talk) 20:11, 24 July 2018 (UTC)
  • Symbol support vote.svg Support For usage with buildings with values like proposed building or structure (Q811683) or Q41668850 it may be extremly useful.--Jklamo (talk) 12:03, 1 August 2018 (UTC)
  • Symbol support vote.svg Support I missed something like this several times. Dissociating status from P31 and P793 is IMHO pretty helpful. strakhov (talk) 15:29, 1 August 2018 (UTC)
  • I would not limit its use to present state though. Using statements qualified with end time (P582) should be OK. strakhov (talk) 15:34, 1 August 2018 (UTC)
  • Symbol support vote.svg Support Very useful. Workarounds like former building or structure (Q19860854) have never really seemed appropriate to me. --AndreasPraefcke (talk) 13:25, 8 August 2018 (UTC)
  • Symbol oppose vote.svg Oppose "State of conservation" and "state of use" are two entirely distinct concepts, and should not be conflated in this manner. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:23, 14 August 2018 (UTC)
  • Pictogram voting comment.svg Comment. I agree with the previous comment. This should be focused on 'state of conservation' only. Otherwise Symbol oppose vote.svg Oppose. Thierry Caro (talk) 23:46, 23 August 2018 (UTC)
  • Pictogram voting comment.svg Comment. Andy Mabbett is right. @Amadalvarez, JerryL2017, PKM, Pere prlpz, Yeza, Voll: @ChristianSW, Jklamo, Strakhov, AndreasPraefcke: Do you agree to keep only "state of conservation" in this proposal (and to create a new one for "state of use"? — Ayack (talk) 13:21, 24 August 2018 (UTC)
  • Pictogram voting comment.svg Comment marking as not ready while the discussion continues − Pintoch (talk) 21:39, 31 August 2018 (UTC)
  • Pictogram voting comment.svg Comment. Is very difficult to approve one property (45 days till today). Even some proposals are rejected with a recomendation to use a "more generic property" as has parts of the class (P2670) or significant event (P793). That's why I gather the concepts in one similar (generic ?) property. However, if you feel better with two differents instead one, it's not a problem to me, but I just ask to approve both together and avoid to go to the start of the process again. Thanks, Amadalvarez (talk) 20:16, 1 September 2018 (UTC)
  • Symbol support vote.svg Support But only as «state of conservation». «State of use» must be another property, both concepts are quite different. --Giovanni Alfredo Garciliano Díaz diskutujo 19:13, 3 September 2018 (UTC)

Discussion (2)

  • Symbol support vote.svg Support Thanks @Ayack: to prepare the split to make easier the decission. Amadalvarez (talk) 11:41, 4 September 2018 (UTC)
  • Symbol support vote.svg Support Cwf97 (talk) 12:23, 23 September 2018 (UTC)

state of conservation[edit]

DescriptionTo indicate state of conservation of a building, monument, etc. It is not related with its heritage protection (heritage designation (P1435)), but to its present state of conservation. Ex.: ruinous, demolished, correct, etc.
Representsconservation status (Q55553838)
Data typeItem
Template parameterestat_us in ca:template:infotaula edifici.
status in en:template:Infobox_building.
erhaltungszustand in de:Vorlage:Infobox Burg.
etc.
Domaingeographical object (Q618123), construction (Q811430), human-made geographic object (Q35145743) and its subclasses
Allowed valuesThis property is multi-value. Some exemple, but not exclusives, are: correct, reformed, abandoned, in danger (Q55555088), ruins (Q109607), demolished, destroyed artwork (Q21745157), destroyed settlement (Q22674930), destroyed city (Q14616455), etc.
Item should be subclass of conservation status (Q55553838).
Possible qualifiers: start time (P580), end time (P582), point in time (P585), applies to part (P518) (when refers to a specific part), but not only.
Allowed unitsN/A
Example 1Parthenon (Q10288) → partially destroyed or ruins (Q109607)
Example 2London Eye (Q160659) → preserved
Example 3World Trade Center (Q11235) → destroyed (P585=2001)
Example 4Casa Vicens (Q746333) → preserved (P580=2017)
Format and edit filter validationN/A
SourceAs a exemple, but not the only source. In any case, this property may hold an "unofficial" description of a changeable value. So, the sources may be anyone.
Planned useincorporate in building infobox to get WD contents instead to be a manual parameter
Number of IDs in sourceDon't know. Probably, they must be moved from present values in infoboxes
See alsoDiscussion that promoted this proposal

state of use[edit]

   Done: state of use (P5817) (Talk and documentation)
DescriptionTo indicate state of use of a building, monument, etc. It is not related with its heritage protection (heritage designation (P1435)), but to its present state of use. Ex.: reformed, in use, temporarily closed, etc.
Representsconservation status (Q55553838)
Data typeItem
Template parameterstato attuale in it:Template:Infobox stazione della metropolitana.
estado in es:Plantilla:Ficha de túnel
etc.
Domaingeographical object (Q618123), construction (Q811430), human-made geographic object (Q35145743) and its subclasses
Allowed valuesThis property is multi-value. Some exemple, but not exclusives, are: in use (Q55654238), open to the public (Q55570821), closed to the public (Q55570340), temporarily closed (Q55653430), closed, ....
Possible qualifiers: start time (P580), end time (P582), point in time (P585), applies to part (P518) (when refers to a specific part), but not only.
Allowed unitsN/A
Example 1Parthenon (Q10288)open to the public (Q55570821)
Example 2London Eye (Q160659)in use (Q55654238)
Example 3World Trade Center (Q11235) → N/A (?)
Example 4Casa Vicens (Q746333) → open to the public (P580=2017)
Format and edit filter validationN/A
SourceAs a exemple, but not the only source. In any case, this property may hold an "unofficial" description of a changeable value. So, the sources may be anyone.
Planned useincorporate in building infobox to get WD contents instead to be a manual parameter
Number of IDs in sourceDon't know. Probably, they must be moved from present values in infoboxes
See alsoDiscussion that promoted this proposal

@ديفيد عادل وهبة خليل 2, FranSisPac, ChristianSW, Jklamo, Medol, Barcelona: @Thierry Caro, Amadalvarez, Germartin1, Giovanni Alfredo Garciliano Diaz, Voll, Strakhov: @PKM, JerryL2017, Pere prlpz, Pintoch, Pigsonthewing, Yeza: @Anvilaquarius, AndreasPraefcke, Ayack: ✓ Done: state of conservation (P5816), state of use (P5817). − Pintoch (talk) 07:50, 10 September 2018 (UTC)

Outer space[edit]

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