[postgis-users] raster2pgsql: -t TILE_SIZE

[Stephen Mather]

Hi Ramon,

I am not an expert on this by any measure. Better to check with the postgis
user group (cc'd). I know the better size choices have changed a lot since
Bborie optimized / rewrote in C.

Best,

Steve



On Mar 16, 2015 4:24 AM, "Ramon de Leon" <r.a.deleon80 at gmail.com> wrote:

>
> Hi Steve,
>
> Hope you are doing well.
>
> Just wondering if there is a good rule-of-thumb thing for choosing
> tile_size in importing raster datasets via raster2pgsql.
>
> I usually use 100x100 or 128x128 just because it is most that I see on
> examples. Sometimes I use the "auto" but I don't know if that helps in
> optimization when the table gets into Postgres.
>
> I want to test importing some fairly large rasters to the DB like
> Globcover (
> http://www.un-spider.org/links-and-resources/data-sources/globcover-esa)
> but I still lack knowledge on the import process good practices
> and optimization. Would appreciate general tips in importing rasters
> (specially larger datasets)!
>
> Thanks!
>
>
> - Ramon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20150316/c99731a6/attachment.html>