[Tagging] Definition of lake/pond as applied to stream/plunge pools

[Joseph Eisenberg]

It's normal for the areas of rivers to be split at rather arbitrary
locations, since it is a maintenance nightmare if a whole river is mapped
as one large polygon.

Normally waterway=riverbank (and water=river) areas do not have a name tag

But if a particular part of a river, like a plunge pool, has a name, then
it would be appropriate to map that area as a waterway=riverbank (or
water=river) polygon with a name=* tag

-- Joseph Eisenberg

On Mon, Dec 21, 2020 at 11:10 AM Paul Allen <pla16021 at gmail.com> wrote:

> On Mon, 21 Dec 2020 at 18:51, Brian M. Sperlongano <zelonewolf at gmail.com>
> wrote:
>
>>
>>
>>> I think you need to expand a little on how to "conflate" a pool with a
>>> river.  The
>>> disadvantage of doing so is that the pool then cannot have a name
>>> assigned.
>>>
>>
>> Sorry, my words were not clear enough here.  By "conflate" I mean that
>> the pool would simply be part of the river polygon.  See this example near
>> Boston:
>> https://www.openstreetmap.org/way/91082432#map=16/42.2615/-71.2764
>>
>
> I knew what you meant by "conflate."  Others may not.
>
>>
>> Note that I explicitly included the phrase "if they are named or
>> significant in size" to cover the case where a stream pool has a name.  My
>> intent is to craft the definition in such a way that it allows either
>> scheme without preference (i.e. part of the river polygon, or a separate
>> pond/lake polygon with a name).
>>
>
> It feels more natural to map a side pool of a wide river which has a river
> polygon
> by expanding the polygon.  But such a pool cannot be named.  It feels
> unnatural to tack a pond onto the side of a river polygon.  But I suppose
> it will work.
>
> --
> Paul
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20201221/a4010eb3/attachment.htm>