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

Paul Norman notifications at github.com
Thu Oct 30 07:36:01 UTC 2025


>From https://github.com/osm2pgsql-dev/osm2pgsql/pull/2427

> We might still want some checks in the future to catch overlarge bounding boxes to defend against bad edits that will lead to a large number of tiles to be expired, but that is a different issue.

I've been thinking about this as well but haven't yet seen discussion. I think detections will need to vary with the tagging so belong in the lua code of a transform. A 1000 square km building is an obvious bad edit but could be a valid lake.

Right now it's possible to do some detection in flex transforms and reject objects. Is there additional information that would help flex code detect bad edits? Do we need something more sophisticated than rejecting objects?

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

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


More information about the Tile-serving mailing list