[gdal-dev] Re: Problems with large raster sizes (WMS/TMS)

Tamas Szekeres szekerest at gmail.com
Sat Nov 14 18:33:48 EST 2009


I've created a ticket with this issue and attached the patch trying to
handle both issues.

According to the changes the gdal default block cache implementation
have been replaced with a hashtable based approach for the WMS driver,
and the raster sizes have been limited to INT_MAX with the driver.

I would be happy if someone could review the patch, it seems working
well in my test cases with block_size=256 and up to tile level: 23.

Best regards,


2009/11/13 Tamas Szekeres <szekerest at gmail.com>:
> 2009/11/13 Even Rouault <even.rouault at mines-paris.org>:
>> But I'm surprised you claim it doesn't support auto-grow and cannot store items
>> with the same hash value : those both features are already implemented and
>> unless you prove me wrong, they work ;-)
> Even,
> Yes, you're right!  By looking into the code again it looks pretty
> customizable with those function pointers. I'll be trying to test it
> with the WMS driver to implement an alternative block cache within
> that. I hope it will work well at least up to TileLevel 22.
> Best regards,
> Tamas

More information about the gdal-dev mailing list