On 2014-02-27 18:01, Bborie Park wrote:
When using raster2pgsql, you wouldn't pass the -C flag. If you're
going to use the generated SQL file, remove the SELECT
AddRasterConstraints... line.
You can add the raster constraints that you want added later with the
AddRasterConstraints() function.
[postgis-users-boun...@lists.osgeo.org] On Behalf Of Eloi [e...@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
On 2014-02-28 16:22, Pierre Racine wrote:
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.
I just wont to make sure I
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
Maybe you can try to separate raster2pgsql and psql .
First use raster2pgsqland output it to a file on you filesystem.
Then use psql
to execute this file.
You could see how much time each step takes, and how much space the sql
temp file is.
Maybe you could use the -Y flag to make it faster?
On 2014-02-27 11:19, Rémi Cura wrote:
Maybe you can try to separate raster2pgsql and psql .
First use raster2pgsqland output it to a file on you filesystem.
Then use psql
to execute this file.
You could see how much time each step takes, and how much space the
sql temp file is.
Maybe you
On 2014-02-27 11:19, Rémi Cura wrote:
Maybe you can try to separate raster2pgsql and psql .
First use raster2pgsqland output it to a file on you filesystem.
Then use psql
to execute this file.
You could see how much time each step takes, and how much space the
sql temp file is.
The sql file
Do you need the maximum extent constraint? Generally, it is safe to disable
the maximum extent constraint.
-bborie
On Thu, Feb 27, 2014 at 7:06 AM, Eloi Ribeiro e...@openmailbox.org wrote:
On 2014-02-27 11:19, Rémi Cura wrote:
Maybe you can try to separate raster2pgsql and psql .
First
When using raster2pgsql, you wouldn't pass the -C flag. If you're going to
use the generated SQL file, remove the SELECT AddRasterConstraints... line.
You can add the raster constraints that you want added later with the
AddRasterConstraints() function.
-bborie
On Thu, Feb 27, 2014 at 8:31 AM,
: mauricio@gmail.com
Subject: Re: [postgis-users] Import Raster with 3 bands to PostgreSQL
Which software? The software has to interpret himself the three bands as RGB.
I don't think QGIS does that...
There is nothing in PostGIS stating that a three bands raster is a TIFF or
JPEG file
Date: Mon, 10 Dec 2012 16:25:19 -0200
From: mauricio@gmail.com
To: pierre.rac...@sbf.ulaval.ca
CC: postgis-users@lists.osgeo.org
Subject: Re: [postgis-users] Import Raster with 3 bands to PostgreSQL
Sorry but I didn't understand what you're trying to do. Could you
elaborate more?
Were
Dear all,
I import with sucess a 3 band image to PostgreSQL 9.1
with the raster2pgsql in Ubuntu 12.04LTS. But when I try to visualize in
another software I can't see the image and it looks like the values
from the other bands glue only in the first band. Do you know if there’s
any problem
...@lists.osgeo.org [mailto:postgis-users-
boun...@lists.osgeo.org] On Behalf Of José Pedro Santos
Sent: Monday, December 10, 2012 11:26 AM
To: postgis-users@lists.osgeo.org
Subject: [postgis-users] Import Raster with 3 bands to PostgreSQL
Dear all,
I import with sucess a 3 band image
[mailto:postgis-users-
boun...@lists.osgeo.org] On Behalf Of José Pedro Santos
Sent: Monday, December 10, 2012 11:26 AM
To: postgis-users@lists.osgeo.org
Subject: [postgis-users] Import Raster with 3 bands to PostgreSQL
Dear all,
I import with sucess a 3 band image to PostgreSQL 9.1
14 matches
Mail list logo
