Property talk:P2048
Latest comment: 2 years ago by Jura1 in topic paintings: keep units in sync with "width" (P:P2049)
Documentation
height
vertical length of an entity
vertical length of an entity
[create Create a translatable help page (preferably in English) for this property to be included here]
Units: “millimetre (Q174789), centimetre (Q174728), metre (Q11573), kilometre (Q828224), inch (Q218593), foot (Q3710), pixel (Q355198), table cell (Q7673190), storey (Q831691), character (Q3241972)”: value unit must be one of listed. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Hello Kitty (Q191794), smurf (Q15720641)List of violations of this constraint: Database reports/Constraint violations/P2048#Units
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2048#Conflicts with P31, hourly updated report, SPARQL
Range from “1e-17” to “1000000000000”: values should be in the range from “1e-17” to “1000000000000”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P2048#Range
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P2048#single best value, SPARQL
Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P2048#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P2048#Entity types
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Unsuitable height for human
Person with height and bigger than 2.72m (man) or 2.48m (women) (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P2048#Unsuitable height for human
Person with height and bigger than 2.72m (man) or 2.48m (women) (Help)
Violations query:
SELECT ?item WHERE { ?item wdt:P31 wd:Q5; wdt:P21 ?sex. ?item p:P2048 ?stmnode. ?stmnode psn:P2048 ?valuenode. # normalised value ?valuenode wikibase:quantityAmount ?height. VALUES (?maxHeight ?relatedSex) { (2.72 wd:Q6581097) (2.48 wd:Q6581072) } FILTER (?height > ?maxHeight && ?sex = ?relatedSex) }List of this constraint violations: Database reports/Complex constraint violations/P2048#Unsuitable height for human
Human > 2.10 m without occupation
Human(s) without occupation (P106) (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P2048#Human > 2.10 m without occupation
Human(s) without occupation (P106) (Help)
Violations query:
SELECT ?item ?height WHERE { ?item p:P2048 _:b1 . _:b1 psn:P2048/wikibase:quantityAmount ?height. filter (?height > 2.10) ?item wdt:P31 wd:Q5. FILTER NOT EXISTS { ?item wdt:P106 []. } }List of this constraint violations: Database reports/Complex constraint violations/P2048#Human > 2.10 m without occupation
Human > 2.10 m without medical condition gigantism
Human(s) without medical condition (P1050) = gigantism (Q501829) (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P2048#Human > 2.10 m without medical condition gigantism
Human(s) without medical condition (P1050) = gigantism (Q501829) (Help)
Violations query:
SELECT ?item ?height WHERE { ?item p:P2048 _:b1 . _:b1 psn:P2048/wikibase:quantityAmount ?height. filter (?height > 2.10) ?item wdt:P31 wd:Q5. MINUS { ?item wdt:P1050 wd:Q501829. } }List of this constraint violations: Database reports/Complex constraint violations/P2048#Human > 2.10 m without medical condition gigantism
Check units
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P2048#Check units
(Help)
Violations query:
SELECT ?item ?unit WHERE { ?item p:P2048/psv:P2048/wikibase:quantityUnit ?unit. MINUS { ?unit wdt:P31 wd:Q1978718. }. FILTER (?unit NOT IN (wd:Q468402, wd:Q355198, wd:Q28171715)). FILTER (?item NOT IN (wd:Q55402287, wd:Q191794)). }List of this constraint violations: Database reports/Complex constraint violations/P2048#Check units
Unsuitable height for human
Person with height smaller than 50 cm (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P2048#Unsuitable height for human
Person with height smaller than 50 cm (Help)
Violations query:
SELECT ?item WHERE { ?item wdt:P31 wd:Q5; wdt:P21 ?sex. ?item p:P2048 ?stmnode. ?stmnode psn:P2048 ?valuenode. # normalised value ?valuenode wikibase:quantityAmount ?height. FILTER (?height < 0.5). FILTER (?item NOT IN (wd:Q38579198)) }List of this constraint violations: Database reports/Complex constraint violations/P2048#Unsuitable height for human
Scope edit
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)
- I don't think it is. --- Jura 09:42, 26 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)
- 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)
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: tinyurl.com/ooc7epv --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)
Depths edit
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)
can we change the main japanese label to this 高さ?
See Wikidata_talk:WikiProject_sum_of_all_paintings#units_of_height_and_width. --- Jura 13:45, 18 November 2021 (UTC)