> Option 1: Have osm2pgsql write out a list of dirty tiles (options > -e/-o). Process that with render_expired (in mod_tile directory). This > will slow down your osm2pgsql runs by something like 25%, and IMHO it > tends to re-render more than required because it makes an attempt to > understand polygon relations. > > Option 2: (AFAIK this is used in the OSM production system) use a ruby > script to parse the OSC diffs and generate rendering instructions: > http://trac.openstreetmap.org/browser/applications/utils/export/tile_expiry > > Option 3: (used by OpenPisteMap) use a python script that processes OSC > diffs and stores expiry information in a database: > https://subversion.nexusuk.org/trac/browser/openpistemap/trunk/scripts/expi > re_tiles.py
Thank you, this is exactly kind of information I needed. One last sub-question: Is there a way how to delete expired tiles from the cache instead of re-rendering them? Othrerwise, I'd implement tirex-batch -- delete option if possible. Radek Bartoň. _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
