[Tilecache] Where in TC code is metatile cutting?
no-reply at neogeo-online.net
Thu Jan 14 03:10:39 EST 2010
I've also pointed out previously that PIL is generated default jpeg
images, i.e. with 75 % compression. If the wms server itself sends 75%
compressed images, that can give pretty ugly images, and make people
wonder why the quality is different when using metatile or not. As this
should be avoided I've suggested to use a 95 % compression (100 %
doesn't even quantize, and produces fat images). Here is the diff on
> elif self.extension == 'jpeg':
Le jeudi 14 janvier 2010 à 08:09 +0100, Ivan Mincik a écrit :
> On Thursday 14 January 2010, Roger André wrote:
> > Hi All,
> > I'd like to take a stab at fixing the problem TileCache has with cutting up
> > 8-bit quantized metatiles. I'm trying to find where in the code PIL is
> > invoked to do this, but can't seem to put my finger on it. Can someone
> > save me a bit of time and tell me where I can find this?
> Hi Roger,
> I am very happy that someone is trying to solve this (if we mean the same problem). I have spend lot of time trying to
> fix this. By my opinion, it is PIL issue which can not be done without hacking PIL code. You can find my post in PIL
> mailinglist - with no help, but I am not very skilled programmer, more GIS person, so maybe You can make it easily.
> Here You can find my ticket with all info, code sample and test file.
> Good luck and give us know about Your progress, even if not successfull.
> Tilecache mailing list
> Tilecache at openlayers.org
More information about the Tilecache