Property talk:P2048

From Wikidata
Jump to navigation Jump to search


vertical dimension of an entity
Representsheight (Q208826)
Associated item
Data typeQuantity
Allowed valuesall (note: this should be moved to the property statements)
Allowed unitsInstances of: unit of length
millimeter (Q174789), centimeter (Q174728), meter (Q11573), kilometer (Q828224), inch (Q218593) and foot (Q3710)
ExampleEiffel tower (Q243) → 324 meter
Kenza Tazi (Q15709800) → 166 centimeter
Tracking: sameno label (Q38403050)
Tracking: differencesno label (Q38403059)
Tracking: usageCategory:Pages using Wikidata property P2048 (Q20989793)
Tracking: local yes, WD nono label (Q38403054)
See alsowidth (P2049), elevation above sea level (P2044), thickness (P2610), vertical depth (P4511), topographic prominence (P2660), length (P2043), horizontal depth (P5524)
Proposal discussionProperty proposal/Archive/34#P2048
Current uses422,781
[create] Create a translatable help page (preferably in English) for this property to be included here
Units: “millimeter (Q174789), centimeter (Q174728), meter (Q11573), kilometer (Q828224), inch (Q218593), foot (Q3710): value unit must be one of listed. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2048#Units, SPARQL (new)
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P2048#Conflicts with P31, hourly updated report, SPARQL, SPARQL (new)
Range from “0” to “1000000”: values should be in the range from “0” to “1000000”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2048#Range, 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.)

Pictogram voting comment.svg Unsuitable height for human
Person with height and bigger than 2.72m or 272cm (Help)
Violations query: SELECT DISTINCT ?item WHERE { ?item wdt:P31 wd:Q5; p:P2048 [ psn:P2048 [ wikibase:quantityAmount ?height; wikibase:quantityUnit ?unit ] ] . FILTER ( ?height > 2.72 ) . }
List of this constraint violations: [[Wikidata:Database reports/Complex constraint violations/P2048#Unsuitable height for human|Database reports/Complex constraint violations/P2048#Unsuitable height for human]]


Shouldn't this property also be used for height of other elements than just buildings, e.g., paintings, people, etc.? — Finn Årup Nielsen (fnielsen) (talk) 16:02, 10 September 2015 (UTC)

The initial editor of the page, User:Ayack, changed the French definition [1]. — Finn Årup Nielsen (fnielsen) (talk) 16:13, 10 September 2015 (UTC)
The word height is too ambiguous, and it looks like this property is duff in it's present form. The definition has been altered and no longer matches the approved proposal, which was something specific to do with the elevation of a train station. Danrok (talk) 23:38, 18 September 2015 (UTC)
I have just put a second example with a person. If this not a good idea, revert. Thierry Caro (talk) 15:03, 22 September 2015 (UTC)
I don't think it is. --- Jura 09:42, 26 September 2015 (UTC)
I don't know how this turns out in other languages, but in my language (Dutch) the word 'hoogte' is quite absurd when applied to a person. I hesitate to change this to 'lengte' (as would be the appropriate word for persons), because this would be wrong for buildings. I vote against combining this property for buildings and persons. Vinkje83 (talk) 19:54, 6 July 2016 (UTC)

This property has now been used widely for paintings, see an example here: Portrait of a woman in a red skirt (Q37432121). — Finn Årup Nielsen (fnielsen) (talk) 16:44, 22 August 2017 (UTC)

Constraint check[edit]

@Andrew Gray, Jura1: With this SPARQL query you can check if a person has a height bigger than 2.72m or 272cm: --Pasleim (talk) 09:07, 6 October 2015 (UTC)

Can you add this to Special:ConstraintReport as well, this way users can check the accuracy of their entry and (in the future) will get warned when doing an incorrect entry? Besides, that way, we don't have to wait for Andrew Gray to fix them all. ;) --- Jura 09:09, 6 October 2015 (UTC)
I don't know how Special:ConstraintReport works but I can create a database report. --Pasleim (talk) 11:12, 6 October 2015 (UTC)
Pretty neat, thanks! I note that Template:Constraint:Range (for the talkpage constraint reports, not the special page ones) handles dates & integers, but not sure if it can cope with quantities yet. Andrew Gray (talk) 19:36, 8 October 2015 (UTC)
✓ Done @Pasleim, Jura1:--Edoardo88 (talk) 15:29, 5 July 2016 (UTC)

@Andrew Gray, Pasleim, Jura1, Edoardo88: there seems to be something wrong with the query: no resultats but there was some to be expected like Windsor del Llano (Q8024748) (that I corrected, qv. Special:Diff/493194973). Cdlt, VIGNERON (talk) 15:27, 1 June 2017 (UTC)

@Pasleim:, please take a look. :) Sjoerd de Bruin (talk) 09:21, 23 October 2017 (UTC)
fixed, but I don't understand why the previous query didn't work. --Pasleim (talk) 09:39, 23 October 2017 (UTC)

Buildings: how to define the differents heights?[edit]

To take the example of Q243, it has an architectural height of 300 m, a tip height of 324 m and a top floor height of 324 m. How do we describe them? The RedBurn (ϕ) 12:40, 1 March 2017 (UTC)

I've set it up with pinnacle and architectural heights like I found on some other items. I'm not sure how to record a top floor height though. Ghouston (talk) 01:15, 8 October 2017 (UTC)


For underground features (e.g. depth of a mine or cave or tunnel), can this be used (as a negative number) for distance beneath the surface? Or should a new property be proposed for that? SJK (talk) 09:50, 13 June 2017 (UTC)

I would rather say no. I think it would be better to suggest a new property. — Finn Årup Nielsen (fnielsen) (talk) 16:41, 22 August 2017 (UTC)