[Tagging] RFC #2: Lake, pond, and reservoir proposal

[Brian M. Sperlongano]

On Mon, Jan 3, 2022 at 8:15 AM Dave F <davefoxfac63 at btinternet.com> wrote:


> I agree that landuse=reservoir tag should be swapped to natural=water,
> water=reservoir. It will fit in with all the other water=* tags. Britain
> is now devoid of 'waterway=riverbank' 'landuse=lake' tags
>
> I see no reason why it can't be done on mass. It was why the software to
> do it was written. There will be no creation of new errors, just
> existing ones moved to a different tag. Automatic edits will always
> produce fewer errors than anyone mistyping or selecting the incorrect
> choice from a pop down menu when editing individual objects.


For those of you familiar with my activities regarding rivers, it should
come as no surprise that I looked into doing this for reservoirs (at least
starting in the United States).  The main problem is that there is a vast
number of objects that are mis-tagged as something else, typically a basin,
or a water treatment pond, or a cattle tank.  In addition, there are some
major hangover effects from old imports - 40,000 landuse=reservoir GNIS
nodes in the US that need to get merged, traced, or deleted.  Just north of
the border in Canada, there are thousands upon thousands of misplaced
cattle tanks that are so wildly divorced from reality that they're better
off being deleted than fixed.  Since we've been using the new tagging here
for quite some time, I felt that landuse=reservoir served as a marker of
sorts for old tagging that needed a human inspection.  The
waterway=riverbank tag was a bit easier to deal with on a larger scale, as
they encompassed both canals and rivers, and canal systems were pretty easy
to detect on a visual scan and some clues about the topography of the
region.  So, I've not pursued a universal replacement of landuse=reservoir
because of the nuances of the objects that are currently tagged that way.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220103/c93aecae/attachment.htm>