The power of two requirement is due to the "drill-down" seeding mode where we want to seed the child metatiles of a given metatile. It works as expected for the wgs84 and google grids as their resolutions are multiplied by two at each zoom level, but the behavior is less optimal for custom grids that do not enforce this constraint. All in all, I'm not completely satisfied about this constraint, and it might effectively cause an uncomplete seed if you reseed a tileset that was previously accessed with a different metatile size.
-- thomas On Fri, Nov 2, 2012 at 4:54 PM, Lime, Steve D (DNR) <[email protected]>wrote: > Trying to test the new version of mapcache, specifically the seeder, > against a slightly older mapcache configuration file. I’m seeing an error > like:**** > > ** ** > > “metatile size is not set to a power of two, rerun with e.g -M 8,8”**** > > ** ** > > It’s true that the tilesets in my config file have metatile set to 5,5. I > don’t recall why that size, probably just copied directly from example > configs… Those values haven’t cause an issue to date.**** > > ** ** > > I’m wondering why the requirement (power of 2) and what the effects will > be if I do some limited tile regeneration on an existing tileset using a > different metatile size.**** > > ** ** > > Steve**** > > _______________________________________________ > mapserver-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapserver-users > >
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
