> I don't understand why you just ignore multipolygons with more than one
> polygon in it. You'll loose data that way.
Yes, but the data is bad anyways because relations on parking areas tend to be
broken in the sense that the tagging rarely make sense.
> It seems to me it would be much simpler to iterate over all polygons in the
> multipolygon and insert each one on its own
> ([example](https://osm2pgsql.org/examples/buildings/)). That way you have all
> the data and don't need to mess around with multipolygons in the database.
Ah, that is good to know. But I would also have to handle the tags on the
relation vs. the members, which I don't have a setup for for performance
reasons for now… and even then, the tags are hard to merge due to tagging
conflicts between the sets of tags :-/
Maybe something like https://github.com/osm2pgsql-dev/osm2pgsql-website/pull/72
can give this more visibility. I can copy that to the V2 docs should that be
mergable…
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2357#discussioncomment-13808180
You are receiving this because you are subscribed to this thread.
Message ID:
<osm2pgsql-dev/osm2pgsql/repo-discussions/2357/comments/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
