[Tile-serving] [openstreetmap/osm2pgsql] Flex creating polygons from inner ways (holes) where outer ways not in dataset (Issue #1584)

[Jochen Topf]

Adding a "strict" mode would be possible, but it would probably not be very helpful in practice, because most users will not need it and those that do will probably not know that there is this magic option which might fix that problem and probably give you others instead. We thought about giving you the information in the flex config file for each geometry, whether it was derived from complete data or not which would allow you to dynamically decide which things to import and which not. But that is a lot of work for something obscure that will not happen often. It is unlikely people will use that feature or even understand the repercussions. So unfortunately this is something we will not fix unless somebody has some great idea how to do so.

I have [added some information to the documentation](https://osm2pgsql.org/doc/manual.html#handling-of-incomplete-osm-data).

In your case you might be able to download the complete relation creating the problem and merging the OSM data of your extract with that data before import. Or you simply add a check in your flex config file for that one relation and not import it.

-- 
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/1584#issuecomment-991034920
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20211210/ee749d90/attachment.htm>