[Tile-serving] [osm2pgsql-dev/osm2pgsql] Catching overlarge bounding boxes to defend against bad edits (Discussion #2428)

[Jochen Topf]

Here is an idea: We could do this check in Themepark. Allow setting a function for each table that takes a geometry and returns a geometry. It can simply return `nil` if it wants to reject the geometry. Themepark would call this function before doing the insert. We can provide simple stock functions that check for max length or max area and so on and provide a default function that's used if you don't set anything that will reject, say, all areas larger than 10% of the planet.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2428#discussioncomment-14838734
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/repo-discussions/2428/comments/14838734 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20251031/9b4924a5/attachment.htm>