<div dir="ltr">Ramon,<div><br></div><div>It really depends on whether the rasters are stored in the database (in-db) or out of the database (out-db)</div><div><br></div><div>If out-db, I recommend using the block size returned when running gdalinfo on the raster...</div><div><br></div><div><font face="monospace, monospace"># gdalinfo raster/test/regress/loader/testraster.tif <br></font></div><div><div><font face="monospace, monospace">Driver: GTiff/GeoTIFF</font></div><div><font face="monospace, monospace">Files: raster/test/regress/loader/testraster.tif</font></div><div><font face="monospace, monospace">Size is 90, 50</font></div><div><font face="monospace, monospace">Coordinate System is `'</font></div><div><font face="monospace, monospace">Image Structure Metadata:</font></div><div><font face="monospace, monospace"> INTERLEAVE=PIXEL</font></div><div><font face="monospace, monospace">Corner Coordinates:</font></div><div><font face="monospace, monospace">Upper Left ( 0.0, 0.0)</font></div><div><font face="monospace, monospace">Lower Left ( 0.0, 50.0)</font></div><div><font face="monospace, monospace">Upper Right ( 90.0, 0.0)</font></div><div><font face="monospace, monospace">Lower Right ( 90.0, 50.0)</font></div><div><font face="monospace, monospace">Center ( 45.0, 25.0)</font></div><div><font face="monospace, monospace">Band 1 <b>Block=90x30</b> Type=Byte, ColorInterp=Red</font></div><div><font face="monospace, monospace">Band 2 Block=90x30 Type=Byte, ColorInterp=Green</font></div><div><font face="monospace, monospace">Band 3 Block=90x30 Type=Byte, ColorInterp=Blue</font></div></div><div><br></div><div>I've bolded the important bit.</div><div><br></div><div>If you're storing the raster in the database, I have no specific suggestions. The reason for no suggestion is that it really depends on the characteristics of the raster (number of bands, pixel type of each band) and the server environment.</div><div><br></div><div>Having said that, I personally use the output from gdalinfo even for in-db rasters.</div><div><br></div><div>-bborie</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 16, 2015 at 8:23 AM, Stephen Mather <span dir="ltr"><<a href="mailto:stephen@smathermather.com" target="_blank">stephen@smathermather.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><p dir="ltr">Hi Ramon,</p><p>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.</p><p>Best,</p><p>Steve</p><p dir="ltr"><br></p><p dir="ltr"><br></p>
<div class="gmail_quote">On Mar 16, 2015 4:24 AM, "Ramon de Leon" <<a href="mailto:r.a.deleon80@gmail.com" target="_blank">r.a.deleon80@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Hi Steve,</div><div><br></div><div>Hope you are doing well.</div><div><br></div><div>Just wondering if there is a good rule-of-thumb thing for choosing tile_size in importing raster datasets via raster2pgsql.</div><div><br></div><div>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.</div><div><br></div><div>I want to test importing some fairly large rasters to the DB like Globcover (<a href="http://www.un-spider.org/links-and-resources/data-sources/globcover-esa" target="_blank">http://www.un-spider.org/links-and-resources/data-sources/globcover-esa</a>) but I still lack knowledge on the import process good practices and optimization. Would appreciate general tips in importing rasters (specially larger datasets)!</div><div><br></div><div>Thanks!</div><div><br></div><div><br></div><div>- Ramon</div></div>
</blockquote></div>
</div>
<br>_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br></blockquote></div><br></div>