Currently, that behavior is as expected due to the application of the specified tile size from the upper-left corner. To minimize the tiles with large swaths of NODATA, you should try to use a tile size that is cleanly divisible (no remainder) by the raster's width and height or a size with a large remainder. I usually recommend tile sizes of 100x100 or smaller though sizes around 50x50 are even faster. In terms of performance, the smaller the time size, the better the performance.
-bborie On Sun, Aug 26, 2012 at 10:22 AM, Jakub Hettler <jakub.hett...@gmail.com> wrote: > Hi all, > I would like to ask if there is a way how to import tiled raster into > PostGIS through raster2pgsql, but I need to make tiled raster, say 256x256, > but at the end of raster I have last tiles (on the east and south side) > which is on half out of the original raster (raster ends fe in the middle of > last tile). If I try to load imported raster into QGIS or use gdal_translate > I have nodata value on this place in the raster. Is there a way how to > import the raster with the smaller last tiles on the east and south edges? > > Thanks > > Jakub > > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users > -- Bborie Park Programmer Center for Vectorborne Diseases UC Davis 530-752-8380 bkp...@ucdavis.edu _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
