Property talk:P276

From Wikidata
Jump to navigation Jump to search


physical location of the item. For administrative entities, use P131. For distinct terrain features, use P706.
Descriptionlocation the item, object or event is within. Qualify with start time (P580) and end time (P582) as appropriate.
Representslocation (Q17334923)
Data typeItem
Domainany object or event that can be located (note: this should be moved to the property statements)
Allowed valuesany instance or subclass of location (Q17334923) (note: this should be moved to the property statements)
ExampleMona Lisa (Q12418)Louvre Museum (Q19675)
Great Smog (Q913640)London (Q84)
Battle of the Hornburg (Q1764229)Helm's Deep (Q1641279)
The Dutch mill (Q2611643)Neede (Q1350047)
Battle of Chios (Q4497840)Chios Strait (Q5101461)
Passover (Q121393)worldwide (Q13780930)
bronchitis (Q173022)bronchus (Q181602)
Commons example
SourceSee (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: sameno label (Q42533341)
Tracking: differencesno label (Q55283114)
Tracking: usageCategory:Pages using Wikidata property P276 (Q23909010)
Tracking: local yes, WD nono label (Q55283111)
See alsoheadquarters location (P159), coordinate location (P625), located in the administrative territorial entity (P131), located on terrain feature (P706), located in or next to body of water (P206), location of discovery (P189), work location (P937), located on street (P669), located in protected area (P3018), valid in place (P3005), anatomical location (P927), location of creation (P1071), filming location (P915), location of the point of view (P7108), significant place (P7153)
Proposal discussionProposal discussion
Current uses
Main statement1,775,60597.3% of uses
Qualifier49,1402.7% of uses
Reference118<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “location (Q17334923), geographical object (Q618123), geographic region (Q82794), fictional location (Q3895768), event (Q1656682), mythical place (Q24334893), shell of an astronomical object (Q47495022), extremity (Q20203388), orbit (Q4130), planet (Q634), venue (Q17350442), Lagrangian point (Q190463), space (Q2133296), interior space (Q1299240), organ system (Q188193), organ (Q712378), tissue (Q40397), anatomical structure (Q4936952), part of (Q15989253), club (Q988108), park (Q22698), everywhere (Q89464513): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value location (Q17334923), geographical object (Q618123), geographic region (Q82794), fictional location (Q3895768), event (Q1656682), mythical place (Q24334893), shell of an astronomical object (Q47495022), extremity (Q20203388), orbit (Q4130), planet (Q634), venue (Q17350442), Lagrangian point (Q190463), space (Q2133296), interior space (Q1299240), organ system (Q188193), organ (Q712378), tissue (Q40397), anatomical structure (Q4936952), part of (Q15989253), club (Q988108), park (Q22698), everywhere (Q89464513) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Known exceptions: Earth (Q2), low Earth orbit (Q663611)
List of this constraint violations: Database reports/Constraint violations/P276#Value type Q17334923, Q618123, Q82794, Q3895768, Q1656682, Q24334893, Q47495022, Q20203388, Q4130, Q634, Q17350442, Q190463, Q2133296, Q1299240, Q188193, Q712378, Q40397, Q4936952, Q15989253, Q988108, Q22698, Q89464513, SPARQL, SPARQL (new)
if [item A] has this property (location (P276)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P276#Contemporary, SPARQL, SPARQL (new)
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P276#Conflicts with P31, search, SPARQL, SPARQL (new)
This property is being used by:

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

Why "current"?[edit]

Why only current location? All locations could be listed with start and end dates. Danrok (talk) 10:05, 25 September 2013 (UTC)

This was intended to be used to mean the current location of an object as opposed to the discovery place, production place etc; But this property was created before qualifiers and ranks. Now that we have both of them, I think we can indeed use start date + rank = preferred for the current value (it is more efficient, and easier to retrieve than a qualifier, and sometimes we do not know the exact start date). So I'd like to propose this property for deletion through merging with P766 (P766). -Zolo (talk) 17:04, 15 February 2014 (UTC)


See also collection (P195). --Kolja21 (talk) 23:31, 28 November 2013 (UTC)

relationship to P1134?[edit]

What is the relationship between location (P276) and P1134 (P1134)? It seems like there's considerable overlap. --Delirium (talk) 13:36, 10 December 2014 (UTC)

Probably P1134 is the next item to be merged with P276, although the property is not yet nominated. Its possible nomination is mentioned in the deletion-discussion of 'event location'. Michiel1972 (talk) 15:53, 10 December 2014 (UTC)
I think merging is a good idea, also for the position of the property in the entity suggester. :) Sjoerd de Bruin (talk) 15:56, 10 December 2014 (UTC)

P1134 will be merged with P276, so I will change the description (property can be used now for villages, neighborhoods, parks, etc) Michiel1972 (talk) 22:51, 19 January 2015 (UTC)

Proposal for a different use[edit]

Whenever an item has collection (P195) it is redundant to have the same information with p276. I´d like to have p276 to show the city or place, where the collection is located. In this way we can use both properties in infoboxes: Mona Lisa (Q12418) + p195 => Louvre (Q19675), + p276 => Paris q90. Very often it is quite unclear by the name of the museum alone to know where it is located.--Giftzwerg 88 (talk) 02:07, 19 January 2015 (UTC)

please see located in the administrative territorial entity (P131)--Oursana (talk) 03:15, 20 January 2015 (UTC)
I think p131 is for adminstrative purposes to show the dependencies between administrative units. But if we do agree to use p 131, then p276 should be dropped completely as it is redundant.--Giftzwerg 88 (talk) 10:36, 28 January 2015 (UTC)


Can someone with knowledge of constraints add the constraint that the item added as value for P276 should not be an administrative entity (but not when the subject item is an [subclass of] event). Since we should use P131 instead of P276 for these cases. Michiel1972 (talk) 10:19, 28 January 2015 (UTC)

Ivan? Multichill (talk) 12:38, 15 February 2015 (UTC)
Current constraints set does not allow to check this case. The case is looked very specific, custom report can help maybe. — Ivan A. Krestinin (talk) 17:23, 15 February 2015 (UTC)


P1134 (P1134) was deprecated and this property should be used. Not all translations have been updated yet so you might want to check your language. Multichill (talk) 12:37, 15 February 2015 (UTC)


Is there a qualifier for 'room' when to label the location of an artwork on display? Or should we add the room as wikidata-item and use that as location? --Hannolans (talk) 18:14, 29 October 2016 (UTC)

I think in the meantime you found out that it is handled like the least--Oursana (talk) 00:41, 12 January 2017 (UTC)

non-geographic location[edit]

Is there a similar property to this but for geometric locations? E.g. a painting depicts an apple and its location is (on) the table. My actual use case would be heraldry so I specifically don't want anything that references the image (P18) value (if one exists). /Lokal Profil (talk) 09:49, 8 November 2018 (UTC)

So e.g. relative position within image (P2677) would not be suitable. /Lokal Profil (talk) 10:14, 8 November 2018 (UTC)

"data item"[edit]

What would that be? @So9q: you add this to the description today. --- Jura 09:22, 22 June 2020 (UTC)

For use on data sets. See example here Location is recommended by the data set wikiproject if I understood correctly.--So9q (talk) 13:31, 22 June 2020 (UTC)
I don't think this is currently in scope. We actually lack a property for geographic coverage. It might work in your sample but if the items is a physical map "location" would be meant to mean the place where the physical map is located, not what it covers. --- Jura 13:38, 22 June 2020 (UTC)
Oh. I was not aware of that. The data set in question ONLY contains features located within swedish borders (as opposed to an imaginary data set that also includes features located in Norway). That is what I'm trying to model with "location". In case that does not work could you suggest a new/existing property that does work in this case? Thanks in advance. Oh, and please do revert my edit if you want.--So9q (talk) 20:48, 23 June 2020 (UTC)