|
Hello, I was looking at this relation and notice that the outer polygons are tagged with 4 ways. 107246847, 116118801, 372485691, 439018546, Three of the 4 ways are tagged as outer. However, way 116118801 is not tagged as an outer way. Is there any reason for that?Should it be tagged as an outer way? |
|
Yes, it looks like it should be tagged outer. Incidentally, it also looks like way 166580594 is tagged inner, but has the same name as the parent relation, and is on or beyond other outer ways. Could this way just be deleted? |
|
I do not have enough knowledge of the forest and the area to update it. I did notice the way 116118801 should possibly be tagged as outer. If someone is familiar with this area and this forest, can you please update it? |
That forest-relation is one big mess, and worst in the south-west corner. Inners crossing each other, crossing the outer, and even a single big 'inner' crossing several other inners AND outer in zigzag.... It's amazing that this forest appears at all, how much Mapnik and a few other powerful apps can work around so many errors by assumptions and guessing. But it certainly would be great if you could really clean it up so that it will appear in ALL apps again. For example here too:
http://osm-wms.de/index.html?zoom=12&lat=48.94191&lon=2.11107&layers=B000FFT
And it would make sense to split it completely along the broad railway gaps, using several independant, closed outer rings.
Some more missing messy forests:
http://osm-wms.de/index.html?zoom=13&lat=49.1129&lon=1.583&layers=B000FFT
Looks like a LOT of work to do in the area, good luck...