[Tagging] Tagging a named river bend

[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 key "natural" is so weighted with controversy already, I'd prefer not
to use that one either. But I'm not opposed if we can all agree on its use
here.

On Fri, Sep 28, 2018 at 7:54 AM Joseph Eisenberg <joseph.eisenberg at gmail.com>
wrote:

> "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 used for a bend in a canal, for example.
>
> "place=*" doesn't say anything about if the feature is natural or a
> settlement, and it isn't usually used for water features.
>
> Another option would be natural=bend or natural=river_bend, because
> natural=* is used for all sorts of geographic features in the natural
> landscape, including water features like bays, straights, etc.
>
> Joseph
>
> On 9/28/18, Dave Swarthout <daveswarthout at gmail.com> wrote:
> > 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, like place=locality it doesn't give any indication that this
> is
> > a bend or curve in a river.
> >
> > 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 schemes and
> > would be relatively easy to implement. A look at Taginfo tells me that
> the
> > "place"  key has been misused quite a bit but I think place=river_bend
> > would be a logical and easily understood new use of the key.
> >
> > See Taginfo: https://taginfo.openstreetmap.org/keys/place#values
> >
> > On Thu, Sep 27, 2018 at 11:38 PM Ture Pålsson <ture at turepalsson.se>
> wrote:
> >
> >> And again, with a link, this time! =)
> >>
> >>
> >>
> https://kso.etjanster.lantmateriet.se/?e=749899&n=7312843&z=9&profile=default_background_noauth
> >>
> >>
> >> 27 sep. 2018 kl. 18:36 skrev Ture Pålsson <ture at turepalsson.se>:
> >>
> >>
> >> 27 sep. 2018 kl. 13:03 skrev Yves <yvecai at mailbox.org>:
> >>
> >> 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.
> >>
> >>
> >>
> >> A simple place=locality gives no hint to a renderer that this is a water
> >> feature, and I can easily imagine a map style where one wants to do
> >> something special with those, like using blue text.
> >>
> >> Look at this example from northern Sweden, where features in the river
> >> (Bredselet, Trångforsen and Vidselet) have lent their names, but in
> >> different grammatical form, the the nearby villages/hamlets of Bredsel,
> >> Trångfors and Vidsel.
> >>
> >> (Follow there river and you'll see several other named rapids (-fors)
> and
> >> stretches of smooth water between them (-sel).
> >>
> >>
> >> _______________________________________________
> >> Tagging mailing list
> >> Tagging at openstreetmap.org
> >> https://lists.openstreetmap.org/listinfo/tagging
> >>
> >
> >
> > --
> > Dave Swarthout
> > Homer, Alaska
> > Chiang Mai, Thailand
> > Travel Blog at http://dswarthout.blogspot.com
> >
>


-- 
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20180928/f0b3616d/attachment-0001.html>