
Hi all, this is a follow up of http://gis.19327.n8.nabble.com/Commit-r4398-revert-changes-from-r4397-is-in-... Attached is a new file which contains additional ways w28 .. w30 and w26 was changed from expected="?" to "in". The new ways are all very close to the residential polygon(s), but completely outside. I think w26 and w30 show very common cases in OSM. Some mappers prefer to "glue" landuse polygons to highways, others don't. There are probably good reasons for both methods. Because of the poor precision the current code in mkgmap adds mkgmap:residential to both of them. See http://gis.19327.n8.nabble.com/is-in-filter-tp5890564p5890566.html where Carlos stated that this would be welcomed (at least if the ways were e.g. highway=secondary instead of footway). If I change the code to be a lot more precise w30 would not be tagged. On the other hand, if you ask for landuse=cemetery you probably don't want to change a cycleway next to it. Any ideas how to handle this dilemma? Gerd P.S. In my hometown the cemetery expanded during the years and it now stretches across a residential road "Lehmkuhlenweg". See https://www.openstreetmap.org/way/11760536 I think in reality the cemetery is split into two parts, there are gates on the footways and barrier=fence or barrier=hedges along the road, but nobody mapped them until now.