Property talk:P201
Latest comment: 1 month ago by Vicarage in topic Renaming as "outflows"
Documentation
outflows
rivers and other outflows waterway names. If evaporation or seepage are notable outflows, they may be included. Some terms may not be place names, e.g. evaporation
rivers and other outflows waterway names. If evaporation or seepage are notable outflows, they may be included. Some terms may not be place names, e.g. evaporation
| Description | Rivers and other outflow waterways. If evaporation or seepage are notable outflows, they may be included. For inflows, see inflows (P200). | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Represents | channel runoff (Q2478921) | |||||||||
| Data type | Item | |||||||||
| Domain | According to this template:
lake (Q23397)
According to statements in the property:
When possible, data should only be stored as statementsbody of water (Q15324), lake system (Q104347069), hydraulic structure (Q2466889) or spring (Q124714) | |||||||||
| Allowed values | watercourse (Q355304) - Some terms may not be place names, e.g. evaporation. (note: this should be moved to the property statements) | |||||||||
| Example | Lake Ontario (Q1062) → St. Lawrence River (Q134750) Lake Geneva (Q6403) → Rhône (Q602) Sea of Galilee (Q126982) → Jordan River (Q40059) Lake Balkhash (Q134485) → evaporation (Q132814) | |||||||||
| Tracking: same | no label (Q42533351) | |||||||||
| Tracking: usage | Category:Pages using Wikidata property P201 (Q26210238) | |||||||||
| See also | inflows (P200) | |||||||||
| Lists |
| |||||||||
| Proposal discussion | Proposal discussion | |||||||||
| Current uses |
| |||||||||
| Search for values |
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “body of water (Q15324), lake system (Q104347069), hydraulic structure (Q2466889), spring (Q124714)”: item must contain property “instance of (P31)” with classes “body of water (Q15324), lake system (Q104347069), hydraulic structure (Q2466889), spring (Q124714)” 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/P201#Type Q15324, Q104347069, Q2466889, Q124714, SPARQL
Value type “watercourse (Q355304), body of water (Q15324), evaporation (Q132814)”: 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 watercourse (Q355304), body of water (Q15324), evaporation (Q132814) (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/P201#Value type Q355304, Q15324, Q132814, SPARQL
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Riddarfjärden (Q965439), Loch na Davie (Q1867284), Loch Katrine (Q1867269), Loch Arklet (Q24640719), Loch Oich (Q1444214)List of violations of this constraint: Database reports/Constraint violations/P201#Single value, SPARQL
Allowed entity types are Wikibase item (Q29934200): 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/P201#Entity types
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/P201#Scope, SPARQL
What if the outflow of a lake doesn´t satisfy the notability guidelines? edit
Sometimes the outflow of a lake is a small canal, which does not satisfy the Wikipedia notability guidelines. This canal flows into a river or lake with an article. At the moment, I don´t add P201 to such a lake. A solution for that problem could be, that the allowed value is a "body of water" (Q15324) (including rivers and lakes) and we should say something like this as the new description: "the next possible body of water downstream (...)". A qualifier is needed in the case that the outflow is not notable, but the following lake or river. Maybe a qualifier telling that this is an approximation? Actually we write at de:WP into the infobox behind the tag "outflow" "zum <body of water>". "zum" means "something that leads to the <body of water>". By the way, "still waters" (Q337567) would be better than "lake". Another problem is that sometimes there is no outflow (above ground). At the moment I´m adding in this case the "no value" value, which isn´t allowed. --Molarus 13:44, 13 November 2015 (UTC)
- Notability guidelines for creating items at Wikidata are not the ones to create articles at Wikipedia: While Wikipedia generally mentions the names of a person's spouse or parents, it doesn't necessarily create articles for these. To include the same information on Wikidata, one needs to create separate items and link them with properties.
- Similarly for your case, if the outflow is mentioned in the article, you might want to create an item for it. This way it can get additional properties, e.g. coordinates. If it fails one or the other constraint checks, these could be adapted.
- Personally, I think an item "no outflow" is preferable to a standard novalue claim. It would allow to define labels for "no outflow" in different languages and makes it easier to query it. --- Jura 13:22, 16 November 2015 (UTC)
- Most of the time these small outflows are not mentioned in the article. "zum <body of water>" is a construction which doesn´t tell the name of the outflow, just that it is connected to the <body of water>. I think, such an outflow is something like a en:Ditch. Some ditches from the 16th to the 19th centuries are found at en:Upper Harz Ditches and there are some with an wp:article, but this water system is a german cultural monument and therefore those ditches are notable (and they even have a name). But I give you a typical example, see de:Großer Labussee and en:Großer Labussee. The german text says: "Kanal zur Quassower Havel zum Woblitzsee" (eng. canal to river Havel to lake Woblitzsee), while the en:WP only says: "River Havel". The german article adds, that the canal to river Havel is 600 meter long, not more. Should this 600 m long canal get a Wikidata item? I don´t think so.
- Concerning the item "no outflow": The description of this property mentions "evaporation" as a value. Maybe Q132814 (evaporation) is better than "no outflow" and it is used 6 times already.
- --Molarus 14:28, 16 November 2015 (UTC)
@Molarus, Jura1: I brought up this topic at the project chat. --Njardarlogar (talk) 20:41, 13 August 2018 (UTC)
Rivers edit
Rivers and marshes can also have efluents, i don't know how to adapt the restrictions. Please help.--Flamenc (talk) 12:25, 14 April 2018 (UTC)
Renaming as "outflows" edit
As per [Wikidata:Project_chat#Specification_of_what_a_hydroelectric_power_plant_takes_its_water_from] I've make "outflows" the primary label, so it can be used more generally for hydroelectric plants, reservoirs etc. Vicarage (talk) 09:51, 5 March 2024 (UTC)