Property talk:P974
Documentation
watercourse that flows into an other one (for lake inflows use P200)
| Description | rivers and streams that flow into larger bodies of water | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Represents | tributary (Q159675) | ||||||||||||
| Data type | Item | ||||||||||||
| Template parameter | left tribs, right tribs en:Template:Infobox river (in case of Wikidata, we can just have tributary and use qualifiers to specify left and right) | ||||||||||||
| Domain | According to this template:
geographical features, mainly bodies of water, though suppose the concept of tributaries can apply to other things
When possible, data should only be stored as statements | ||||||||||||
| Allowed values | instances of watercourse (Q355304) (note: this should be moved to the property statements) | ||||||||||||
| Example | Mississippi River (Q1497) → Missouri River (Q5419) Rivière Saint-Étienne (Q3433806) → Bras de la Plaine (Q2923910) Kropyvianka River (Q46991742) → Bazhanykha River (Q46991743) | ||||||||||||
| Tracking: usage | Category:Pages using Wikidata property P974 (Q26250027) | ||||||||||||
| See also | mouth of the watercourse (P403), inflows (P200) | ||||||||||||
| Lists |
| ||||||||||||
| Proposal discussion | Proposal discussion | ||||||||||||
| Current uses |
| ||||||||||||
| Search for values |
List of violations of this constraint: Database reports/Constraint violations/P974#Type Q355304, Q16338046, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P974#Value type Q355304, Q16338046, Q124714, Q187971, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P974#Item P17, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P974#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P974#Entity types
List of violations of this constraint: Database reports/Constraint violations/P974#Conflicts with P31, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P974#allowed qualifiers, SPARQL
Difference to mouth of the watercourse (P403) edit
Can someone explain me in which sense this property differs from mouth of the watercourse (P403)? --Pasleim (talk) 19:28, 29 October 2013 (UTC)
- @Pasleim:: it is the opposite ! :). --Zolo (talk) 07:15, 22 February 2014 (UTC)
Inverse edit
There should probably be a "Tributary of" property also. (A river would be a tributary of only 1 other water body, except in very exceptional circumstances.) --Closeapple (talk) 08:31, 7 December 2013 (UTC)
Considering this and the previous section, I've proposed aliases at Property talk:P403#Relationship to tributary, to add "tributary of", "flows into", and "water mouth is on" to mouth of the watercourse (P403). Anyone with objections can comment there. --Closeapple (talk) 23:19, 11 July 2014 (UTC)
What the difference with this property? Infovarius (talk) 16:05, 28 August 2015 (UTC)
- tributary (P974) is for rivers flowing into another river, inflows (P200) is for rivers flowing into a lake or sea. --Pasleim (talk) 21:34, 30 August 2015 (UTC)
Use for veins in anatomy edit
OBO defines tributary_of as:
"X tributary_of y if and only if x a channel for the flow of a substance into y, where y is larger than x. If x and y are hydrographic features, then y is the main stem of a river, or a lake or bay, but not the sea or ocean. If x and y are anatomical, then y is a vein."
Can this property be defined that way so that it's also useable for veins?
Notified participants of WikiProject MedicineThe WikiProject Geology WikiProject does not exist. Please correct the name. ChristianKl (talk) 20:44, 1 September 2016 (UTC)
- I don't see the benefits of mixing the two. Same English word, but they don't really interconnect.
--- Jura 22:45, 7 September 2016 (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 10859 violations. Ghouston (talk) 06:10, 7 November 2018 (UTC)
Allowed qualifiers edit
wd:P3871 tributary orientation 462 wd:P560 direction 74 wd:P2148 distance from river mouth 29 wd:P625 coordinate location 24 wd:P276 location 14 wd:P131 located in the administrative territorial entity 10 wd:P2044 elevation above sea level 3 wd:P200 inflows 11
Currently, there is no constraint. Above the ones that are used three and more times.
- P560 should probably be replaced with P3871.
- P276, P625, P131, P2044 might be sufficient on the mouth of watercourse statement of the tributary.
Haven't looked into P200. --- Jura 08:18, 12 May 2021 (UTC)
Suggested qualifiers: tributary orientation and distance from river mouth edit
I removed tributary orientation and distance from river mouth required constraints... it's just going to cause warnings on every river page. Less than 1% of tributaries have those listed, I don't see how it can be made "required". OBender12 (talk) 12:07, 12 May 2021 (UTC)
- I think they should be present on any river. Don't you? I can't really think why they should be missing. Given the level of completeness, I don't think they should be mandatory for now, accordingly I set them as required qualifiers with constraint status "suggested constraint". Note that this question is different from the question above about which qualifiers should be allowed (obviously, these two should be, but maybe also some of the others). --- Jura 17:56, 12 May 2021 (UTC)
use on oceans edit
There were 601 statements on Atlantic Ocean (Q97). See discussion at Wikidata:Project_chat#Q97_is_unusable_now. --- Jura 12:29, 21 May 2021 (UTC)