From OpenStreetMap Wiki
Jump to: navigation, search

visibility of rivers

I'd really like to see rivers show up in mapnik at a higher zoomlevel than only ≥ z12. Even riverbank/water are only showing up as early as z7 ! Rivers can be seen from space much earlier than any motorway. why not show them as early as z6 ?!? --katpatuka 08:36, 23 August 2008 (UTC)

Direction of flow

Is there any guidlines to which way to track a river? For instance the direction of flow. I have always tracked rivers the way the water flow, that is from the mountains to the sea. --Skippern 13:22, 19 October 2008 (UTC)

The article says "Direction of the way should be downstream." axk 17:29, 8 April 2009 (UTC)

I just got involved in a "don't use oneway=yes on waterways" discussion. I've read some information about it and find it unsatisfactory. The rule "direction of the way should be downstream" is easy enough, but what about waterways that are tagged from satellite images where the flow of direction isn't known? And can it be guaranteed that people tagging waterways do it correctly? I wouldn't say so and I think an additional tag is needed. Although I consider using oneway=yes only "creative" some people seem to consider it plainly "wrong". So an alternative tag would look like a good compromise, but the discussion so far doesn't seem to have led to any generally accepted result (or at least there is no such result mentioned in "map features" as a tag). Should a new discussion be started? Tesche 10:00, 24 August 2012 (UTC)

There seems to be a disagreement on this, still. To-Fix says that rivers (inherently one-way, as opposed to an estuary, which is bi-di) which are tagged oneway=yes are incorrect and need fixing. And yet, there seem to be a bunch of rivers in a Canadian import (GeobaseNHN_Import_2009) that got imported with oneway=yes. It is reasonable to tag a river as oneway=yes, and not tag an estuary as oneway. Or maybe we should introduce a waterway=estuary which is implicitly bi-directional, while a river is implicitly oneway. RussNelson (talk) 22:57, 9 November 2014 (UTC)
IMHO, this use of the tag oneway=yes is contradictory to the current definition of oneway : This means that this tag should be used when this way can only be used in one direction. Beeing "used" isn't something to be consider from the water standpoint, but from humans point of view (And even if, water doesn't "use" the river). So the oneway tag should have nothing to do with the rivers's flow but the humans access restrictions on that said river. In other words, if I find a oneway=yes tag on a waterway, I'd consider this waterway beeing only allowed to boats in the direction of the flow (which might really be an extremly rare situation beside maybe some rare canals), and most likely a mapper's mistake.
The need to record the fact that the river's flow is unknown by the armchair mapper still remains. I guess a fixme=unknown flow direction could do the work. sletuffe (talk) 16:42, 10 November 2014 (UTC)

Rivers near their source

I have been tracing rivers from NPE lately and followed them back to close to their source. However, I am not clear on whether I should really be tagging them as streams once they get pretty thin. Often the NPE continues to mark them as "River Clun", etc. Should I be tagging those thin stretches near the source as streams, but keep the "River Clun" name tag, or just stick to river for the whole length? --Davespod 09:34, 30 July 2009 (UTC)

When they disappear into a cave

  • tag the end-node of the way as waterway= {soakhole|sinkhole|karst|dolite} ?
This is the end node of a stream where it disappears into a hole/cave, as you might find in limestone country. Presumably it pops back out somewhere else as a spring. Possible aka's: "soakhole", "sinkhole", "dolite", or "karst". Sinkholes (with or without water flowing into them) can be quite big, so can be both areas and nodes. --Hamish
Why not use natural=cave_entrance? In combination with waterway=stream(e.G.) and tunnel=yes the objects could be described pretty exact imo. No need to invent too specific tags. -- Malenki 12:05, 25 April 2010 (UTC)
PS: I imply you mean it's the end of the waterway on layer=0, continuing on layer=-1, not really the end of the waterway at all.

this looks good myfanwy 01:32, 23 April 2010 (UTC)

Uploaded as waterway=soakhole for the LINZ bulk import, and will merge those nodes into the river ways once the rivers are uploaded. (we have no info about where the streams go underground, so not bothering with layer=-1) --Hamish 00:20, 27 December 2010 (UTC)

River Confluence

I've been thinking about how to make specific reaches of rivers searchable. For example, in older paleontological literature the position of a fossil locality is sometimes given in relation to a river confluence. For someone unfamiliar with the region, it would be useful to be able to search on this type of relationship.
Maybe some combination of these tags would work?
confluence=river a name;river b name
name=confluence of river a and river b

--Mattbk16:25, 21 September 2011 (BST)

More detailed classification

The current classification between stream and river is not very satisfactory. How can we improve it, drawing on established practice elsewhere