Hello,
I am having to import Raster (.tiff) into Postgres using the raster2pgsql tool.
The raster used is 12MB in size and the Postgres version is 9.1 on Ubuntu 13.10.
The virtual machine has the following hardware specs.
- 17408 Memory
- 4 Processors
- 16GB HDD
)
Sent: Wednesday, December 04, 2013 10:56 AM
To: postgis-users@lists.osgeo.org
Subject: [postgis-users] [postgis] Optimal tile size for Raster
Hello,
I am having to import Raster (.tiff) into Postgres using the raster2pgsql
tool.
The raster used is 12MB in size and the Postgres version
2013 17:43
To: PostGIS Users Discussion
Subject: Re: [postgis-users] [postgis] Optimal tile size for Raster
You are getting fast result because you are not operating at the pixel level.
Only at the raster extent level (converted to geometry). A more usual query
would be to intersect a raster
: Wednesday, December 04, 2013 12:07 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] [postgis] Optimal tile size for Raster
Hi Pierre,
Thanks for the suggestion.
But how could I get a geometry table in Postgres that is sure to intersect
the raster image?
The reason why I
2013 18:31
To: PostGIS Users Discussion
Subject: Re: [postgis-users] [postgis] Optimal tile size for Raster
I guess maybe you are only looking at PostGIS for its capacity to deal with
raster in the database. You have to know that rasters and geometries are
located in space (georeferenced) and might
