Property talk:P469

Documentation

lake on watercourse
lake or reservoir through which the river or stream flows

Description

lakes the river flows through or into. See also inflows (P200), outflows (P201) and mouth of the watercourse (P403).

Represents

lake (Q23397)

Data type

Item

Template parameter

"SEEN" or "STAUSEEN" in de:Template:Infobox Fluss

Domain

According to this template: rivers - river (Q4022)

According to statements in the property:
watercourse (Q355304), fictional river (Q16338046) or fictional lake (Q15709969)

When possible, data should only be stored as statements

Allowed values

body of water (Q15324), mainly lake (Q23397) (note: this should be moved to the property statements)

Example

Missouri River (Q5419) → Lake Sharpe (Q6477698)
Aare (Q1675) → Lake Brienz (Q14442)

Tracking: usage

Category:Pages using Wikidata property P469 (Q26678448)

Lists

Proposal discussion

Current uses

Total	5,163
Main statement	5,159	>99.9% of uses
Qualifier	4	<0.1% of uses

Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “watercourse (Q355304), fictional river (Q16338046), fictional lake (Q15709969)”: item must contain property “instance of (P31)” with classes “watercourse (Q355304), fictional river (Q16338046), fictional lake (Q15709969)” or their subclasses (defined using subclass of (P279)). (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/P469#Type Q355304, Q16338046, Q15709969, SPARQL

Value type “body of water (Q15324), fictional river (Q16338046), fictional lake (Q15709969)”: 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 body of water (Q15324), fictional river (Q16338046), fictional lake (Q15709969) (or a subclass thereof). (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/P469#Value type Q15324, Q16338046, Q15709969, SPARQL

Conflicts with “reservoir created (P4661)”: this property must not be used with the listed properties and values. (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/P469#Conflicts with P4661, search, SPARQL

Scope is as main value (Q54828448): 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/P469#Scope, SPARQL

This property is being used by:

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

Flows into

Hi. Current description contains phrase "...flows through or into". Are we need duplicate every mouth of the watercourse (P403) with lake value using this property? For example: need I add claim Volga (Q626) <lake on watercourse (P469)> Caspian Sea (Q5484)? — Ivan A. Krestinin (talk) 17:47, 9 March 2014 (UTC)[reply]

Support Remove "or into" - LaddΩ chat ;) 00:35, 19 April 2014 (UTC)[reply]

Flows out

There are rivers which only flow out of a lake but not through or into it, e.g. Limmat (Q14338) commences at the outfall of Lake Zurich (Q14407). Should we add Limmat (Q14338)lake on watercourse (P469)Lake Zurich (Q14407) ? --Pasleim (talk) 08:01, 11 August 2015 (UTC)[reply]

I believe Limmat (Q14338)origin of the watercourse (P885)Lake Zurich (Q14407) is more appropriate.

Also, I wouldn't say that bodies of water that river flows out of or into are "on river" really. I'm going to amend description here accordingly. 2001:7D0:88DD:F880:7123:AF0C:FE7E:F095 12:35, 1 February 2018 (UTC)[reply]

Inverse property

What about creating new "throughflow (river)" property? Currently we can use outflows (P201) and inflows (P200) for this purpose, but separate property would allow to avoid repeating the same value for current properties. I'm not sure about English label for this property though, neither "throughflow", "flowthrough" or "runthrough" is too common. Is there a common English term for this in context of rivers/lakes? Like German Durchfluss or Estonian läbivool. Or should it say "river that flows through lake" or simply "flows through"? 90.191.81.65 07:52, 17 February 2018 (UTC)[reply]

Waterfalls?

Nearly two years ago English-language description and aliases were changed in a way suggesting that property value can be waterfall as well (Special:Diff/813684599/813684641). Waterfalls are not lakes, are they? I think this should be undone. 2001:7D0:81F7:B580:858C:CD2:A18B:D3C4 17:59, 3 December 2020 (UTC)[reply]

Done--Trade (talk) 22:08, 12 December 2020 (UTC)[reply]

Trade, thank you. Description still mentions "waterfalls". 2001:7D0:81F7:B580:D164:CF65:BD57:F3B0 08:31, 13 December 2020 (UTC)[reply]