[Tile-serving] [openstreetmap/osm2pgsql] OSM relations and hstore (#605)

[Sarah Hoffmann]

Here is what happens:  first the tags of the relation are filtered according to your style file. With so few entries, that means that for most relations all tags are filtered away. Next osm2pgsql recognizes a multipolygon and starts handling for it. It finds a relation without tags (because of the filtering) and immediately thinks it is an old-style multipolygon (the tagging style where the tags were out on the member ways, not the relations). So it goes and copies the tags from the first way it finds in the relation. Unfortunately, the way still has its full set of tags because you requested to store all tags in hstore. The result is that a polygon ends up in the database with a completely messed up set of tags.

This is actually closely related to #605 and shows that even for the C transform it is wrong to blindly use the way tag filter for determining multipolygons. How about the following: hand in the original tag list. Then check the non-inners if they have a polygon like tag, if one way is completely without polygon tags, discard completely, otherwise do current handling. @pnorman, any opinion?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/605#issuecomment-270757590
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20170105/f858c324/attachment.html>