Property talk:P403

Documentation

mouth of the watercourse
the body of water to which the watercourse drains

Description

Body of water at the end of a watercourse. See also lake on watercourse (P469).

Represents

river mouth (Q1233637)

Data type

Item

Domain

According to this template: watercourse (Q355304)

According to statements in the property:
watercourse (Q355304), fictional river (Q16338046), mythical river (Q24336031), spring (Q124714), valley (Q39816), glacier (Q35666), lake system (Q104347069), drainage system (Q285451), body of water (Q15324), still waters (Q337567) or wadi (Q187971)

When possible, data should only be stored as statements

Allowed values

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

Example

Vltava (Q131574) → Elbe (Q1644)
Rivière des Remparts (Q3433902) → Indian Ocean (Q1239)
Okavango River (Q188773) → Okavango Delta (Q650872)

Tracking: same

no label (Q42533397)

Tracking: usage

Category:Pages using Wikidata property P403 (Q26249996)

See also

distance from river mouth (P2148), outflows (P201), discharge (P2225), distributary (P5998), tributary orientation (P3871)

Lists

Proposal discussion

Current uses

Total	135,584
Main statement	133,573	98.5% of uses
Qualifier	2,009	1.5% of uses
Reference	2	<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), mythical river (Q24336031), spring (Q124714), valley (Q39816), glacier (Q35666), lake system (Q104347069), drainage system (Q285451), body of water (Q15324), still waters (Q337567), wadi (Q187971)”: item must contain property “instance of (P31)” with classes “watercourse (Q355304), fictional river (Q16338046), mythical river (Q24336031), spring (Q124714), valley (Q39816), glacier (Q35666), lake system (Q104347069), drainage system (Q285451), body of water (Q15324), still waters (Q337567), wadi (Q187971)” 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/P403#Type Q355304, Q16338046, Q24336031, Q124714, Q39816, Q35666, Q104347069, Q285451, Q15324, Q337567, Q187971, SPARQL

Value type “body of water (Q15324), fictional body of water (Q16500104), valley (Q39816), still waters (Q337567), wadi (Q187971), sewer network (Q156849)”: 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 body of water (Q16500104), valley (Q39816), still waters (Q337567), wadi (Q187971), sewer network (Q156849) (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/P403#Value type Q15324, Q16500104, Q39816, Q337567, Q187971, Q156849, SPARQL

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). Known exceptions: Crinan Canal, section from Crinan to Cairnbaan (Q56664718), Féith Chàm (Q112729719)
List of violations of this constraint: Database reports/Constraint violations/P403#single best value, SPARQL

Qualifiers “tributary orientation (P3871), located in the administrative territorial entity (P131), coordinate location (P625), reason for deprecated rank (P2241), reason for preferred rank (P7452), elevation above sea level (P2044), location (P276), start time (P580), end time (P582), OS grid reference (P613), subject named as (P1810), object named as (P1932), end cause (P1534)”: this property should be used only with the listed qualifiers. (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/P403#allowed qualifiers, 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/P403#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

List of violations of this constraint: Database reports/Constraint violations/P403#Entity types, hourly updated report

This property is being used by:

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

Coordinates[edit]

There is Nile (Q3392), Mississippi River (Q1497), Amazon (Q3783) and probable others with this property (mouth of the watercourse (P403)) and coordinate location (P625) for its location. I think it could be better if the coordinate location (P625) is a qualifier for mouth of the watercourse (P403). There is opportunity to provide property with coordinates as qualifier as well for the other side (spring (Q124714)) of the river (Q4022). The coordinate location (P625) shall not be used as standalone property for watercourse (Q355304) classes. Paweł Ziemian (talk) 12:11, 2 August 2013 (UTC)[reply]

I think this property can be used standalone, but point to the middle of the river. It will useful for {{coord|...|display=title}} For springhead and mouth we need separate properties, see Wikidata:Property proposal/Place#coordinates of the beginning (en) / координаты начала (ru)/ координати початку (uk). — Ivan A. Krestinin (talk) 17:35, 2 August 2013 (UTC)[reply]

No, you cannot point to the middle of a river. There is no official source doing that, and how would you proceed to do so? Clicking somewhere into the wild, what appears to be the middle?

Another issue: In some cases rivers have more than one mouth, and they even do not need to be conflucences with the same waterbody. However most official sources cite only one mouth. --Matthiasb (talk) 10:02, 16 October 2015 (UTC)[reply]

I think the problem is resolved with applies to part (P518) as qualifier, see for example Weser (Q1650). Paweł Ziemian (talk) 15:40, 16 October 2015 (UTC)[reply]

WD:Database reports/Constraint violations/P403#Types statistics_2[edit]

Just curious about the currently 4 red entries for "national historic site of Canada (Q1568567)" . Which items are these? Do they have only Q1568567 or is this in addition to the one of the "green" entries? -- Docu at 14:52, 15 September 2013 (UTC)[reply]

Looks like bug. It is additional value to "green" entry. I try fix this in near time. — Ivan A. Krestinin (talk) 15:21, 15 September 2013 (UTC)[reply]
- ah .. I guess that's why it didn't make sense to me ;) Let me dig further once it works. -- Docu at 17:20, 15 September 2013 (UTC)[reply]
  - I english knowledge does not allow me be sure that I understand you correctly. Problem was in summary. Main report works correctly. Problem in summary is fixed. Bot will update pages in next 1-3 hours. — Ivan A. Krestinin (talk) 18:04, 15 September 2013 (UTC)[reply]
    - Excellent. It actually works how it should.
      The risk now is that we get circles as with categories on Commons (e.g. A=>B=>C=>D=>A). Currently, class properties are rare, so this might not be an issue yet. -- Docu at 21:56, 15 September 2013 (UTC)[reply]

Relationship to tributary[edit]

This appears to be a compliment to tributary (P974). It seems reasonable that a watercourse should have its (probably) single mouth/outlet as a property. So:

Is there any reason not to add "tributary of", "flows into", and "water mouth is on" as aliases for this property?
Any reason this property shouldn't have {{Constraint:Inverse|property=tributary (P974)}} and tributary (P974) have {{Constraint:Inverse|property=mouth of the watercourse (P403)}}?

Also, just so I'm sure: This property is intended to name the water body that this water body flows into, right? Or was it also designed for cases where a mouth or fork point has its own name also? (I don't know of any of those, but it seems like such a place might have Wikipedia articles or Commons categories.) --Closeapple (talk) 23:01, 6 July 2014 (UTC)[reply]

mouth of the watercourse (P403) values are not only watercourses, but also lakes, seas etc. The latter use inflows (P200) to link back to watercourse, and so such inverse constraint wouldn't work well. 2001:7D0:81F7:B580:D875:2633:4FD3:87B9 06:35, 15 May 2021 (UTC)[reply]

Add qualifiers[edit]

We should be able to add the qualifier left bank (Q27834806) or right bank (Q27834918). Thx --YanikB (talk) 12:46, 22 February 2017 (UTC)[reply]

Is it OK if I use instance of (P31) as qualifier and add left bank (Q27834806) or right bank (Q27834918) to it (see Rivière Maskinongé (Q20899945) ? --YanikB (talk) 21:08, 6 March 2017 (UTC)[reply]

country (P17)[edit]

I've removed the constraint that items with this property should also have country (P17). Rivers don't generally stay within a single country. Deryck Chan (talk) 20:37, 4 November 2017 (UTC)[reply]

Not really a problem: you can add all countries with P17. You might have noticed that most rivers have this property.
--- Jura 20:56, 4 November 2017 (UTC)[reply]

single-value constraint (Q19474404)[edit]

Hello. There are many watercourse (Q355304) that have multiple distributary (Q591942). How can we keep the constraint and still manage to take those cases into account? Thierry Caro (talk) 18:58, 23 December 2017 (UTC)[reply]

P4614 (drainage basin) constraint[edit]

I'm deleting this constraint, since it doesn't seem very relevant: you shouldn't need to know about a river's drainage basin (and create an item for it) before you can name its mouth or tributary. It has 36387 violations. Ghouston (talk) 06:07, 7 November 2018 (UTC)[reply]

Accept more qualifiers[edit]

May we accept as qualifiers coordinate location (P625) and located in the administrative territorial entity (P131) ?. The draining basin is not enough to know the exact point of mouth of the watercourse (P403) described in terms of coordinates and as administrative territory. Above are an old discussion from 2013 talking about the coordinates points in the middle of the river. In my opinion, this is a concept completely obsolete since we have a much more sophisticated cartography tools to draw starting and ending point of the river. Regarding the P131, is not enough as a main property because the river usually start, cross and ends in different entity and, sometimes, different country. No argued answer, means OK. Thanks, Amadalvarez (talk) 17:27, 9 September 2019 (UTC) cc.@Pere_prlpz:[reply]

Mouth[edit]

The property mouth only accepts one data. But in this case Q1997895 —there are many more– the mouth changed (this can be, as in this case, by a human intervention, or for other rivers, by the forces of nature). Until 1961 the river ended in the Leybucht, directly in the see. From 1961 on it ended in the new build canal Störtebekerkanal. Both facts are important data to understand the hydrography of that river. Thank you for your help.--Flamenc (talk) 09:54, 10 June 2020 (UTC)[reply]

Left or right?[edit]

How to specify to which side of the parent body (if sides are applicable) does the current watercourse discharge? Incnis Mrsi (talk) 17:45, 14 July 2020 (UTC)[reply]
Found Property:P3871. Why we see no documentation on availability of this qualifier? Incnis Mrsi (talk) 18:03, 14 July 2020 (UTC)[reply]

Accept start/end time as qualifiers[edit]

Could mouth of the watercourse (P403) accept start time (P580) and end time (P582) as qualifiers? For example, Niderbach (Q109303067) changed its mouth in 2021. --Sascha (talk) 20:24, 28 October 2021 (UTC)[reply]

Looked as reasonable. Or you can specify the item as exception. — Ivan A. Krestinin (talk) 20:40, 28 October 2021 (UTC)[reply]

Type constraint too generic[edit]

@YanikB, Saarik: why you added classes "body of water" and "still waters" under type constraint? Currently this property is incorrectly used for 128 lake items (are not watercourses). However constraint now misses these due to these too generic classes. 2001:7D0:81DA:F780:50DE:590:CB16:50C6 13:26, 14 February 2022 (UTC)[reply]

Added start and end time as qualifiers[edit]

I've added start time (P580) and end time (P582) to the allowed qualifiers constraint (diff). Per Kirkhope Cleuch (Q24640130), the river mouth emptied into Daer Water (Q15212518) until 1956, and into the new Daer Reservoir (Q5208267) from 1956. We need start and end times to represent this common occurrence. --Tagishsimon (talk) 14:58, 6 March 2022 (UTC)[reply]