[Imports] Fwd: Importing West Virginia State Forests Boundary

[Mateusz Konieczny]

Aug 11, 2021, 22:15 by frederik at remote.org:

> There's a bunch of bubbly residential areas that nobody tracing from aerial imagery would classify as such. For example, why is > https://www.openstreetmap.org/way/863679643>  shaped the way it is and why does it have this little hole in the South? If that is the "official" data then maybe OSM is better off without it.
>
looking at Bing aerial it seems reasonable mapping and at level of average mapping.
Worse than what experienced mapper would map, better than what a newbie would map.
Personally I would consider it as OK and still improving map.

> Why do neighbouring large landuse polygons duplicate tens of thousands of nodes instead of being modelled as relations both sharing one way?
>
There are two parts:
(1) node duplication: that is a problem that should be fixed, I wrote about it in
https://www.openstreetmap.org/changeset/93033483

(2) multipolygons are evil
Why way duplication/lack of multipolygons would be a problem?
Multipolygonised landuse is horrific to edit, even to experienced mappers
and effectively blocks mapping by a new users

Lack of unneeded multipolygons is a big plus, NOT a problem.

> Furher east, I find https://www.openstreetmap.org/way/685277039 which is an older forest that was simply overlaid with new data without any attempt at proper conflation.
>
that is a problem, commented in https://www.openstreetmap.org/changeset/93150714

> Where was that huge Rhode Island import even discussed?
>
this is also a problem (also asked in https://www.openstreetmap.org/changeset/93033483 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20210812/392339a5/attachment.htm>