At the moment we do tile expire of polygons by bbox, so it is actually bbox,
but I am working on fixing that. Hopefully soon it is the area that matters (or
the length of the polygon boundary, if expiry is set to only do the boundary),
or, even more exact, the number of tiles affected. But bbox is a proxy that's
cheap to generate and relatively easy to understand for users.
Using "tiles" as measure is problematic because people don't necessarily have a
good intuition how large tiles are in specific zoom levels. And a building
that's right at a tile corner can invalidate 4 tiles but is usually much
smaller than a tile. Using "area" is probably better than tiles, but it still
suffers from the usual problem: Is that m² or km² or whatever and is that real
area or Web Mercator units. (Although bbox also has a similar problem.)
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2428#discussioncomment-14825517
You are receiving this because you are subscribed to this thread.
Message ID:
<osm2pgsql-dev/osm2pgsql/repo-discussions/2428/comments/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
