[Talk-us-massachusetts] well, so much for the Lynn Woods effort

[hobbit at techno-fandom.org]

After reading a lot of the surrounding history, I'm a bit clearer on

    > In short: never add landcover tags to landuse-type objects.

I'm with ya on that, at least now I am, having seen the historical battles.
I'd be happy, as time permits, to go in on various areas and map the *actual
wooded areas* with the right tags, which I expect would mostly be larger than
the park boundaries but hopefully 100% independent. With the park boundaries
showing up as the darker borders, such as in the West Virginia example and
others.

But the problem I was having, particularly last night, is that inner polygons
that are relations apparently don't behave right in OSM-carto.  I've also
read a bunch of the issues at gravitystorm's Carto github, and the seemingly
endless "forest covers the wrong thing" issues, and between that and what I'm
told on the help forum it looks like 1> that's quite the deficiency in Carto,
and 2> it is sometimes possible to work around it by adding the segment ways
and hope the renderer realizes what's on which side.  I suspect that if I try
to file a new issue at Github saying "why not respect inner relations", it'll
only piss people off.

If inner relations are a no-no, the documentation should reflect that.  I could
find NO specific statements either way, really.  I tried.

This is being a STEEP learning process.  But all I really want, in the end,
is woods showing up as woods.  As a side-effect of "correct" mapping, as you
say.  There are a lot of bad examples out there, I'm sure you know, with
administrative boundaries tagged as landuse/landcover/natural.  I see splitting
those into the official boundaries vs. the *real woods* as a starting point,
which could expand outward from there.  Is that still thinking wrong?  Another
problem is that it's impossible to copy large objects in iD.  Installing JOSM
or something is not presently an option here, and I don't think my ordinary
casual trail fix-ups are really worth that.

The other real asskicker problem is that the carto tiles on the OSM website
take *forever* to catch up with edits, giving seriously confusing visual
results.  And that's *with* trying to dirty the tile cache and force it.

_H*