User:Frodrigo/Relation:Waterway
Jump to navigation
Jump to search
Tags
Key | Value | Comment |
---|---|---|
type | waterway | |
waterway | river, canal, stream... | Really needed ? All part of waterway may have different type; but this can help distinguish main aspect of this waterway. |
name | Waterway name | Optional but recommended |
ref:* |
Members
Type | Role | Recurrence | Comment |
---|---|---|---|
![]() |
main_stream (or none) | one or more | waterway=river , waterway=canal , waterway=stream ...
|
![]() |
side_stream | optional | Same relation kind as this, a branch of main stream than return to it.
Ordered by end of side stream (integrated in tributary sort). |
![]() |
side_stream | optional | waterway=river , waterway=canal , waterway=stream ... a branch of main stream than return to it.
|
![]() |
tributary | optional | Same relation kind as this, for direct tributary.
Ordered from upstream to downstream (integrated in side stream sort). Recurse on tributary relation member allow rebuild of drainage basin from any part. Avoid need of relation |
![]() |
waterway=* . Include way as role tributary only when this way is not part of an other type=waterway relation and the way is a direct tributary. This case is for short waterway in one way (like small stream). By construction, this relation schema don't allow tributary on tributary way.
| ||
![]() |
riverbank | optional | Multipolygone of waterway like in Relations/Proposed/Rivers. Relation can have waterway=riverbank , but all way part of this relation already have it.
|
![]() |
spring | optional | natural=spring
|
Links
- WikiProject_Rivers and it talk page
- Relations/Proposed/Rivers and it talk page