Property talk:P403

From Wikidata
Jump to navigation Jump to search


mouth of the watercourse
the body of water to which the watercourse drains
DescriptionBody of water at the end of a watercourse. See also lakes on river (P469).
Representsriver mouth (Q1233637)
Associated item
Data typeItem
According to this template: watercourse (Q355304)
According to statements in the property:
watercourse (Q355304), fictional river (Q16338046), mythical river (Q24336031) and spring (Q124714)
When possible, data should only be stored as statements
Allowed valuesbody of water (Q15324) (note: this should be moved to the property statements)
ExampleVltava (Q131574)Elbe (Q1644)
Rivière des Remparts (Q3433902)Indian Ocean (Q1239)
Okavango River (Q188773)Okavango Delta (Q650872)
Tracking: sameno label (Q42533397)
Tracking: usageCategory:Pages using Wikidata property P403 (Q26249996)
See alsodistance from river mouth (P2148), lake outflow (P201), discharge (P2225), distributary (P5998)
Proposal discussionProperty proposal/Archive/10#P403
Current uses76,707
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Value type “body of water (Q15324), fictional body of water (Q16500104), no label (Q4114033): 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), no label (Q4114033) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P403#Value type Q15324, Q16500104, Q4114033, SPARQL, SPARQL (new)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P403#Single value, SPARQL, SPARQL (new)
Item “country (P17): Items with this property should also have “country (P17)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P403#Item P17, search, SPARQL, SPARQL (new)


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)

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)
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)

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)

  • 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)
    • 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)
      • 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)
        • 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)

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:

  1. Is there any reason not to add "tributary of", "flows into", and "water mouth is on" as aliases for this property?
  2. 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)

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)

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

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)

  • 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)

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)

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)