Property talk:P4511
Documentation
vertical distance from a horizontal area to a point below. Compare with "horizontal depth" (P5524)
List of violations of this constraint: Database reports/Constraint violations/P4511#Units
List of violations of this constraint: Database reports/Constraint violations/P4511#Conflicts with P31, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Changing labels edit
I can not see from the discussion that the property is for waterdepths only so I have changed the labels accordingly. Breg Pmt (talk) 23:36, 16 November 2017 (UTC)
- Most values are likely to be ;) . I added is as alias and restored the original label (see proposal discussion).
--- Jura 07:44, 17 November 2017 (UTC)
Average or maximum depth? edit
As per original proposal this property seems to be mainly for lakes. However there is no indication on whether it stores average or maximum depth, which is a common distinction in hydromorphological datasets. en:Template:Infobox body of water also has respective fields.
Now, in order to clear this up, we might use distinctive qualifiers, but this would probably make data model overly complicated. As both average and maximum depth are quite common data for water bodies, then perhaps we should introduce separate properties for these and leave current property for general use (like the earth quake example)?
Ping User:Thierry Caro, as I see you've been busy importing depth data from French Wikipedia lately. 90.191.81.65 13:18, 3 January 2018 (UTC)
- I've imported the maximum depths. The rest I'm open about. Thierry Caro (talk) 13:24, 3 January 2018 (UTC)
- Getting an overview on what current values of this property are about is probably tricky, if not impossible. For example, Lake Harku (Q621853) where I bumped into it, has average depth, because import source makes no distinction. So, even if most values were maximum depth then, in order to make it clear, simply renaming the property label probably wouldn't be a good option either. 90.191.81.65 13:39, 3 January 2018 (UTC)