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

[Jochen Topf]

Thinking some more about this, I am asking myself whether this is really about the geometry itself, not just the expire tiles. Drawing a 1000km² building is already a problem even if there is no expiry involved. That would give us also more options on how to do the checking. We can do this today, calculate the area or the length of a feature in Lua. It isn't a problem to not write such a geometry to an output table in which case it would also no show up in an expire list. So if somebody changes a building and makes it 1000 times bigger than before it would simply vanish, triggering an expiry of the tiles covering the old geometry. (Actually detecting that this is a problematic change and leaving the old object in place would be better, but that's a whole other can of worms.)

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

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