[Tile-serving] [osm2pgsql] Bad multipolygon tags (#80)

[Petr Morávek]

@pnorman Sorry for the mistake, you're right, it's not admin boundary, but this specific example is not really important for this issue (it was just the relation that alerted me to the problem).

I still think that there is no tagging error in the mentioned relation, but let me give you another example - imagine you don't care about e.g. water related feature, so you delete the line with waterway from your import.style. Suddenly all the riverbank multipolygons are considered "old-style" and get tags from their member ways resulting in completely different features than if you wouldn't have deleted the waterway line from import.style. In this case I doubt you will argue that it is caused by wrong tagging.
The only way how to reliable force osm2pgsql to treat the multipolygon relation as "new-style" tagging is to add area=yes to the multipolygon relation, which is just silly tagging for "renderer".

I agree that this needs to be discussed more widely, but since the behavior has already changed, I would suggest to resolve this issue before 0.84 to limit the import to a single BC break between two versions.

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/80#issuecomment-24859747
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20130921/50d69284/attachment.html>