Re: [Tagging] Tagging a named river bend

Fine for me. Yves Le 30 septembre 2018 06:19:21 GMT+02:00, Dave Swarthout a écrit : >Correct. I will split the river way at either end of the bend and apply >the section tags to that piece only. The river continues to have its >own >name tag while the bend has only the tags needed to identify

Re: [Tagging] Tagging a named river bend

Correct. I will split the river way at either end of the bend and apply the section tags to that piece only. The river continues to have its own name tag while the bend has only the tags needed to identify it as a section with special characteristics, and also a name On Sun, Sep 30, 2018 at

Re: [Tagging] Tagging a named river bend

I think this is a good solution for your situation; tagging bends and reaches. It should work for other types of waterways too. I assume in this example you will be splitting the way (waterway=river) at the beginning and end of the bend? So there are no overlapping or duplicate ways. On Sun, Sep

Re: [Tagging] Tagging a named river bend

Unfortunately, this topic has gotten split into two threads making it difficult to follow. In trying to summarize, let's not be overly concerned with rendering issues or whether this scheme can be fully modeled on OSM. We can deal with rapids, hazards, etc., using existing tagging or develop new

Re: [Tagging] Tagging a named river bend

Re: "I would not discard the idea of using some kind of relation for this (type=route is not suitable, or is it?). It is the most flexible way to tag as it allows for overlapping entities and avoids duplication of ways." In theory, it would be great to be able to build up a long river from many

Re: [Tagging] Tagging a named river bend

sent from a phone > On 28. Sep 2018, at 02:39, Dave Swarthout wrote: > > I keep coming back to Martin's place=river_bend. Adding a name=Harper Bend > along with that tag would solve the problem in a straightforward manner, > would not be confused with the specialized whitewater tagging

Re: [Tagging] Tagging a named river bend

Am 28.09.2018 um 03:06 schrieb Dave Swarthout: @Joseph - I wanted to avoid using that particular top-level tag, waterway, because there would be no simple way to add a name different from that of the waterway=river itself. Unless we invent a new tag something like name:bend=Harper Bend. The

Re: [Tagging] Tagging a named river bend

I think it would be hard to restrict natural=* to a node, but then, which way? Not a good idea IMHO. Yves ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Tagging a named river bend

Oh, I see. I was thinking about use on a node only, where this would not be a problem. Place=* tags are usually used on nodes, perhaps on areas (controverially) but not on ways. This reminds me of the problem with naming mountain ranges and ridges. Right now we can name part of an individual

Re: [Tagging] Tagging a named river bend

@Joseph - I wanted to avoid using that particular top-level tag, waterway, because there would be no simple way to add a name different from that of the waterway=river itself. Unless we invent a new tag something like name:bend=Harper Bend. The key "natural" is so weighted with controversy

Re: [Tagging] Tagging a named river bend

"waterway=" is usually used for features that have to do with linear water features; values include dam, weir, lock, etc. Since the name of a bend would be most useful for boaters and kayakers who are using a river as a waterway, I would recommend using "waterway=bend". This could then also be

Re: [Tagging] Tagging a named river bend

At first, the use of "section" seemed useful to consider. The tag "whitewater:section_name" has not been defined in the Wiki but might be adapted to this issue. However, the word "whitewater" would be misleading IMO because this is a flat river that whitewater enthusiasts would not seek out. Also,

Re: [Tagging] Tagging a named river bend

And again, with a link, this time! =) https://kso.etjanster.lantmateriet.se/?e=749899=7312843=9=default_background_noauth > 27 sep. 2018 kl. 18:36 skrev Ture Pålsson : > > >> 27 sep. 2018 kl. 13:03 skrev

Re: [Tagging] Tagging a named river bend

> 27 sep. 2018 kl. 13:03 skrev Yves : > > Place=locality makes sense, I guess the name is also used for the area close > to the bend by extension. > Locality on a node is always troublesome, and I wonder if anybody uses > description=* to describe further the place, here this would be

Re: [Tagging] Tagging a named river bend

Section_name, is there not something like this in the whitewater tagging scheme? Yep: https://wiki.openstreetmap.org/w/index.php?title=Key:whitewater:section_name=edit=1 And yes, this tagging scheme extend to brown/blue/green river sections. Yves Le 27 septembre 2018 16:14:47 GMT+02:00, Martin

Re: [Tagging] Tagging a named river bend

On 27/09/2018 15:17, Michael Patrick wrote: */a reach is just any length of a stream or river/* * * It would seem odd to tag a bend as a reach, as the classic definition of a reach is 'A portion of a river, channel, or lake which lies between two bends or which can be seen in one view'.

[Tagging] Tagging a named river bend

> It does not communicate the quality of "riverness" at all. This bend may or may not lend its name to a locality but it is primarily a feature of the river, not the name of a settled place. Generally, the term 'Reach' is most appropriate for subsections of flowing water: (From

Re: [Tagging] Tagging a named river bend

sent from a phone > On 27. Sep 2018, at 15:57, Dave Swarthout wrote: > > This bend may or may not lend its name to a locality but it is primarily a > feature of the river, not the name of a settled place. locality is explicitly for toponyms that don’t refer to settlements or their parts.

Re: [Tagging] Tagging a named river bend

I would resist the use of the locality tag (also the other pro-node arguments) even though it's an easy answer to my problem. It does not communicate the quality of "riverness" at all. This bend may or may not lend its name to a locality but it is primarily a feature of the river, not the name of

Re: [Tagging] Tagging a named river bend

sent from a phone > On 27. Sep 2018, at 12:21, Joseph Eisenberg > wrote: > > To confirm, this name is for the section of river, not for the semi-circle of > land inside of the bend? practically I would expect the name to extend to this piece of land as well (often). cheers, Martin

Re: [Tagging] Tagging a named river bend

sent from a phone > On 27. Sep 2018, at 12:10, Warin <61sundow...@gmail.com> wrote: > > I'd use > place=locality > name=* I don’t oppose this, but I feel it would be time to introduce an additional tag for localities that states which kind of toponym it is (where it comes from or what is

Re: [Tagging] Tagging a named river bend

I guess this can also apply to named straight bits as well? http://onthethames.net/reaches-river-thames/ On 2018-09-27 11:58, Dave Swarthout wrote: > I'm working on adding islands and other features in the Tanana River in > Alaska. There are many named sloughs (side channels), islands and in

Re: [Tagging] Tagging a named river bend

Place=locality makes sense, I guess the name is also used for the area close to the bend by extension. Locality on a node is always troublesome, and I wonder if anybody uses description=* to describe further the place, here this would be something like description=river bend. Le 27 septembre

Re: [Tagging] Tagging a named river bend

+1 If it's a well defined area, I would tag an area tagged place=* , name=* If it's an island, I would tag place=island. If no regular place-value fits, then place=locality. If it's a normal thing, like when all bends in the river have a name, then I would probably enter a new place-value, e.g.

Re: [Tagging] Tagging a named river bend

I agree that a node is best, because it is debatable where a river bend starts and ends, but it is easy to put a node at the center. To confirm, this name is for the section of river, not for the semi-circle of land inside of the bend? I agree that a separate tag is needed, as you said, because

Re: [Tagging] Tagging a named river bend

I'd use place=locality name=* Fits, renders and searchable. Put it on a node. On 27/09/18 19:58, Dave Swarthout wrote: I'm working on adding islands and other features in the Tanana River in Alaska. There are many named sloughs (side channels), islands and in some areas curves or bends that

[Tagging] Tagging a named river bend

I'm working on adding islands and other features in the Tanana River in Alaska. There are many named sloughs (side channels), islands and in some areas curves or bends that have a name. In my example there is a large bend in the river that has its own name, Harper Bend. I'm looking for a way to