Hi, Thanks, sounds great. I wonder where all this is documented? I have been reading this page which does not mention "mode=delete" or "force" http://www.mapserver.org/trunk/mapcache/seed.html. Doy you know of any other valuable but hidden features?
-Jukka- ________________________________ thomas bonfort wrote: On 7 June 2013 17:48, Rahkonen Jukka <[email protected]<mailto:[email protected]>> wrote: Hi, How well does Mapcache seeder tool handle the case when the original big aerial image coverage is updated little by little so that the hole cycle takes 3 to 6 years? Reseeding the whole cache every time when a batch of new images is received does not feel like a reasonable solution. you can look into the ogr support in the seeder, by giving a wkt/shapefile/whatever of the area you want to reseed. A) Can the seeder tool ake a fast delete for all tiles which intersect the update area geometry so that it is guaranteed that outdated tiles are not delivered. Only high zoom levels (Z greater than X) should be purged. Low zoom levels may stay as they are because they are not used for interpretation. depends on what you call fast... the tiles intersecting the area of interest need to be iterated and deleted, depending on the area and zoom levels that can take some time. mode=delete ogr source => where you want to delete tiles zoom=X,21 B) Can the seeding tool reseed those areas? force ogr source zoom=X,21 C) Is the behaviour similar for disk cache and Berkeley DB cache? the behavior is identical. the performance is up to you to measure (I have no metrics to give you). regards, thomas -Jukka Rahkonen- _______________________________________________ mapserver-users mailing list [email protected]<mailto:[email protected]> http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
