Re: [OSM-dev] Documentation about Tirex update strategies configuration
Look for tirex-batch, tirex-tiledir-check, and tirex-tiledir-stat on http://wiki.openstreetmap.org/wiki/Tirex/Commands and read the man pages. Thank you. But if I understand it correctly, tirex-batch can only send request for immediate rendering. What I'm looking for is how to set expration time of set of tiles so they are re-rendered when accessed from mod_tile? Another taks not explained is how do I derive what tiles has changed since the last replication interval as described at http://wiki.openstreetmap.org/wiki/Minutely_Mapnik -- Ing. Radek Bartoň Faculty of Information Technology Department of Computer Graphics and Multimedia Brno University of Technology E-mail: black...@post.cz Web: http://blackhex.no-ip.org Jabber: black...@jabber.cz ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Documentation about Tirex update strategies configuration
But if I understand it correctly, tirex-batch can only send request for immediate rendering. What I'm looking for is how to set expration time of set of tiles so they are re-rendered when accessed from mod_tile? I'm not totally sure but I think this is impossible to configure in mod_tile. Check for expiration is a global configuration option and done the same way for every tile in code. Perhaps you write your own solution that checks sets of tiles and if they are expired you submit a render request to tirex for this set of tiles. Should not be that difficult. best regards philipp ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Documentation about Tirex update strategies configuration
Dne pondělí 10 Leden 2011 15:49:28 Philipp Borgers napsal(a): I'm not totally sure but I think this is impossible to configure in mod_tile. Check for expiration is a global configuration option and done the same way for every tile in code. IIRC, it is possible for mod_tile+renderd. Perhaps you write your own solution that checks sets of tiles and if they are expired you submit a render request to tirex for this set of tiles. Should not be that difficult. Writing own parser of osc.gz files that determines which tiles are affected by the change is quite complex task and I'm quite sure there must be something already (it must run on the official OSM tile server). I just don't know how it's called and how can I setup it. -- Ing. Radek Bartoň Faculty of Information Technology Department of Computer Graphics and Multimedia Brno University of Technology E-mail: black...@post.cz Web: http://blackhex.no-ip.org Jabber: black...@jabber.cz ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Documentation about Tirex update strategies configuration
Hi Radek, Radek Bartoň wrote: Writing own parser of osc.gz files that determines which tiles are affected by the change is quite complex task and I'm quite sure there must be something already (it must run on the official OSM tile server). I just don't know how it's called and how can I setup it. There are different ways to do that. It is not something that is done in tirex (or renderd for that matter) because these systems do not know when data is updated in the database. You need something that processes the .osc files. There's more than one way to do it (tm): 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/expire_tiles.py - On some tile servers I run, I simply use the tirex-create-stats-and-update-tiles.sh script from tirex/utils. This script completely ignores any changes from the OSC diffs, and simply finds the oldest tiles on disk an re-renders them. This is somewhat low-tech but also quite robust. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Documentation about Tirex update strategies configuration
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 dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Documentation about Tirex update strategies configuration
Radek, Radek Bartoň wrote: 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. render_expired has a --delete-from option; it will delete expired tiles that are on the given zoom level or on a higher zoom level. tirex-batch doesn't yet have such an option. You're of course welcome to add functionality to tirex, but if you don't need to mix re-rendering and deleting, maybe it would be easier to write a generic metatile deletion script that does not require tirex. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Documentation about Tirex update strategies configuration
On Sat, Jan 01, 2011 at 04:19:01PM +0100, Radek Bartoň wrote: I'm looking for documentation how to configure Tirex update strategy as described at http://wiki.openstreetmap.org/wiki/Tirex/Tile_Update_Strategies . Look for tirex-batch, tirex-tiledir-check, and tirex-tiledir-stat on http://wiki.openstreetmap.org/wiki/Tirex/Commands and read the man pages. Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Documentation about Tirex update strategies configuration
Hello everyone. I'm looking for documentation how to configure Tirex update strategy as described at http://wiki.openstreetmap.org/wiki/Tirex/Tile_Update_Strategies . Thank you. -- Ing. Radek Bartoň Faculty of Information Technology Department of Computer Graphics and Multimedia Brno University of Technology E-mail: black...@post.cz Web: http://blackhex.no-ip.org Jabber: black...@jabber.cz ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
