|
On 2014-05-26 18:10, Marc Gemis wrote :
You might add a nearer (better) neighborhood for that wrong "is part of", but you will start a never ending game ;-) Seriously, the problem, as you conclude, is of course defining a neighborhood with a node. The wiki says it can be tagged on polygons but, sadly, isn't clear about relations, this is why it's a pity... I have the same problem with the ubiquitous concept or region (place=region). That is the funniest tag ever: it cannot be put on a node, nor on a way, nor on an area nor on a relation!!! ;-) I have made a region Ourthe-Amblève with a boundary=region relation (that I'd better call touristic_region). It is not an administrative boundary, so, it has no admin_level. (yet, I used admin_center for the tourist desk). I should try to make it a plain multipolygon with place=region. In that case, the boundary is well defined because the region is a set of municipalities and I reused their borders as outer ways and subareas. But what if those fuzzy borders are not well defined as in your case? Well, that could be very simple in my mind. One uses a relation that has no borders (hence not a boundary and not a multipolygon) and one puts as members of this relation as many map elements as necessary and aesthetically to best define it: streets, any node, landuse areas, etc... Just a few nodes define your neighborhood reasonably. The Nominatim's job is then to choose the place= relation whose members surround the target. The Renderer's job is, as the best option failing to have a border to outline the area, to highlight all of its members. Simple enough isn't it? And probably just a few details to settle with Nominatim and Standard Map. And that would make less fuzzy place=region place=... articles too. Hoping this can help.
|
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
