[postgis-users] import raster

[Pierre Racine]

Importing a big raster as a coverage with a huge number of small tiles always takes a long time. Two options:

-Increase the size of your tiles. They don't have to be that small to get good performance with intersections.

-Do you really need the raster to be inside the database? Try adding the -R raster2pgsql option. The import step will be way faster and up to now we haven't seen much difference in terms of intersection/extraction performance when the raster data is kept outside the db.

Pierre
________________________________________
From: postgis-users-bounces at lists.osgeo.org [postgis-users-bounces at lists.osgeo.org] On Behalf Of Eloi [eloi at openmailbox.org]
Sent: Thursday, February 27, 2014 5:03 AM
To: Lista PostGIS users
Subject: [postgis-users] import raster

Hi all,

My SELECT PostGIS_Full_Version() is: "POSTGIS="2.0.3 r11128"
GEOS="3.3.8-CAPI-1.7.8" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL
1.10.0, released 2013/04/24" LIBXML="2.9.0" LIBJSON="UNKNOWN" RASTER"

I am importing a GeoTIFF (1 band, Type = Byte,  Not Compressed file size
= 933.5 MB, columns/rows 43200, 21600, Pixel Size =
0.008333333333333,-0.008333333333333) into PostGIS and is taking more
than one hour by now. Is that normal?

This is the command I have used:
raster2pgsql -s 4326 -d -I -C -M -t 5x5 /path/file_name.tif
schema_name.table_name|psql -d db_name

Yes, very small tiles. The goal is to intersect this raster with point
features. But the issue right now is the import it self that is taking
to much time.
I can see now that the first 1:30 were for inserts and now is starting
with the constraints. Is this the normal speed or am I missing
something?

Thanks. Cheers,

Eloi
_______________________________________________
postgis-users mailing list
postgis-users at lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users