The "expire" configuration for a geometry column in the table definition now has an option "diff_expire", which is set to "false" by default but can be set to "true" to get "diff expire", which means expire will be based on the symmetrical difference between old and new geometry.
Note that "diff expire" will only be used for ways and relations that change based on their members. If a way or relation is changed itself, we always do a complete expire. This is needed, because we don't know what changes there are (the tags or attributes could have changed, or even the geometry type). Internally this is implemented by not calculating expire tiles first for the "delete" of the old geometry and then for the "add" of the new geometry, but by writing old and new geometries for each object in a cache and then, after we have collected all geometries, calculating the symmetrical differences between those geometries. You can view, comment on, or merge this pull request online at: https://github.com/osm2pgsql-dev/osm2pgsql/pull/2476 -- Commit Summary -- * Add option for diff expire -- File Changes -- M src/expire-config.hpp (3) M src/flex-lua-table.cpp (9) M src/flex-table-column.cpp (140) M src/flex-table-column.hpp (45) M src/flex-write.cpp (13) M src/flex-write.hpp (7) M src/output-flex.cpp (52) M src/output-flex.hpp (10) A tests/bdd/flex/expire-diff.feature (361) M tests/bdd/flex/lua-expire.feature (42) -- Patch Links -- https://github.com/osm2pgsql-dev/osm2pgsql/pull/2476.patchhttps://github.com/osm2pgsql-dev/osm2pgsql/pull/2476.diff -- Reply to this email directly or view it on GitHub: https://github.com/osm2pgsql-dev/osm2pgsql/pull/2476 You are receiving this because you are subscribed to this thread. Message ID: <osm2pgsql-dev/osm2pgsql/pull/[email protected]>
_______________________________________________ Tile-serving mailing list [email protected] https://lists.openstreetmap.org/listinfo/tile-serving
