I don't believe ST_Band or most functions will have the outasin flag added.
ST_AsBinary is for exporting rasters from PostGIS unlike ST_Band which creates
a new raster within PostGIS.
If anything, a function that converts an out-db band to in-db band may be
useful.
-bborie
-Original Mess
Duncan,
I'll have to double check but I think ST_Intersects is converting the geometry
to a single pixel raster under the hood. If true, I'll optimize it so that
points aren't being converted as the conversion is pointless.
-bborie
-Original Message-
From: Duncan Golicher
Sender: postg
That message can be safely ignored assuming you're not getting any
error messages preceding it. The message itself indicates that the band
had no values worth counting...
-bborie
On 07/12/2013 11:41 AM, Pierre Racine wrote:
> Hi,
>
> I do this query for counting the frequency of values in a rast
hich is just OK:
>
> # ldconfig -r | grep pgsql
> search directories:
> /usr/lib:/usr/X11R6/lib:/usr/local/lib:/usr/local/pgsql/lib
> 328:-lpgtypes.3.3 => /usr/local/pgsql/lib/libpgtypes.so.3.3
> 329:-lecpg.6.4 => /usr/local/pgsql/lib/libecpg.so.6
Marcelo,
See if rtpostgis-2.2.so can find the PostgreSQL libs.
ldd /usr/local/pgsql/lib/rtpostgis-2.2.so
-bborie
On 07/10/2013 12:32 PM, Marcelo Bacha wrote:
> Thanks Bborie.
>
> I went back to PostgreSQL, to check the warnings from compilation. I
> Corrected a couple of things, applied a rece
ds,
>
> Hugues
>
> -Message d'origine-
> De : postgis-users-boun...@lists.osgeo.org
> [mailto:postgis-users-boun...@lists.osgeo.org] De la part de dustymugs
> Envoyé : mardi 2 juillet 2013 19:09
> À : postgis-users@lists.osgeo.org
> Objet : Re: [postgis-user
Hugues,
Another possibility if you have PostGIS 2.1 is ST_Neighborhood().
http://www.postgis.net/docs/manual-dev/RT_ST_Neighborhood.html
-bborie
On 07/02/2013 09:47 AM, Hugues François wrote:
> Hello,
>
> Given a one band raster made of numerous tiles and a point geometry from
> which I selec
Hugues,
You should be able to use ST_MapAlgebraNgb if you have PostGIS 2.0. But
there may be challenges working with neighboring tiles.
PostGIS 2.1 has more robust handling with ST_MapAlgebra.
http://www.postgis.net/docs/manual-2.1/RT_ST_MapAlgebra.html
See the example with the description "Com
Daniel,
Is it safe to assume that the OutOfMemoryException exception is coming
from NHibernate? It doesn't look like something PostgreSQL or PostGIS
would emit.
How big is the source raster file that is causing that error?
It doesn't look like there is the capability to import the WKB. Can you
f
Assuming you have a recent version of PostgreSQL, you might be able to
try the foreign data wrapper for Oracle.
http://wiki.postgresql.org/wiki/Foreign_data_wrappers#oracle_fdw
-bborie
On 06/24/2013 02:07 PM, John Callahan wrote:
> I know this is more of a Postgres question than PostGIS...
>
>
On 06/12/2013 11:52 AM, Graeme B. Bell wrote:
> Hi again bborie,
>
> "in-db and out-db does matter. Your SQL asks the database to fetch some
> data and the size of said data (and where that data is) will affect the
> performance of the SQL."
>
> I agree that in-DB vs out-DB has a general effect u
On 06/12/2013 11:06 AM, Graeme B. Bell wrote:
>> Have you considered storing your rasters outside the database with
>> raster2pgsql's -R flag? I usually recommend this if the rasters are
>> readonly. This also minimizes the amount of information stored within
>> the database to just the metadata of
Can you file a ticket for this? Make sure to include your example. It
looks like something is wrong in GDAL's GDALFPolygonize() function.
-bborie
On 06/06/2013 01:50 PM, Jean Marchal wrote:
> I am using GDAL 1.9.2, yep ST_PixelAsPolygons() works fine,
>
> Jean
>
>
ST_DumpAsPolygons() is special as that calls a GDAL function while
ST_PixelAsPolyons() is completely internal to PostGIS. I'll do some digging.
-bbori
On 06/06/2013 01:50 PM, Jean Marchal wrote:
> I am using GDAL 1.9.2, yep ST_PixelAsPolygons() works fine,
>
> Jean
>
>
What version of GDAL are you using? ST_DumpAsPolygons() uses GDAL for
processing. I notice that ST_PixelAsPolygons() works correctly...
-bborie
On 06/06/2013 01:04 PM, Jean Marchal wrote:
> Bborie,
>
> I used ST_Value to prove that the value for pixel with coordinates (8,2)
> does exist. I did n
Something else is wrong. The following works just fine...
CREATE TYPE foo AS (a text, b int, c geometry);
CREATE TABLE baz (d integer, e foo[]);
-bborie
On 04/17/2013 02:49 PM, Michael Sacauskis wrote:
> Hi
>
> I'm trying to implement a composite data type with PosgresSQL/PostGIS.
> Somethin
91 postgresql91-server postgresql91i postgresql91-libs
> postgresql91-contrib uuid postgresql91-plpython postgresql91-devel
> postgis2_91"
>
> --Jack
>
> -Original Message-
> From: postgis-users-boun...@lists.osgeo.org
> [mailto:postgis-users-boun...@lists
Jack,
Which repos are you checking? I believe the one recommended by
PostgreSQL and PostGIS is yum.postgresql.org.
-bborie
On 02/21/2013 08:15 AM, Gold, Jack L (US SSA) wrote:
> Anyone know why the postgis raster support files (rtpostgis.sql,
> rt_postgis_upgrade_20_minor.sql, rtpostgis_legacy
Hey Laurent,
The following should work. It works on my production server.
WITH foo AS (
SELECT ST_AddBand(ST_MakeEmptyRaster(5, 5, -1987330.654, -39780.983,
1000, -1000, 0, 0, 97125), 1, '8BUI', 1, 0) AS rast
)
SELECT
ST_SRID(rast),
ST_SRID(ST_Transform(rast, 3310))
FROM
The only problem you have in your query is the expression being provided
to ST_MapAlgebraExpr(). That expression should be:
[rast1.val]*[rast2.val]
The notice itself can safely be ignored. In the normal use case, your
source rasters are tiled into smaller chucks. And between these smaller
chuc
rtpostgis.sql is still present. You'll want to check with the rpm packager.
-bborie
On 02/08/2013 08:09 AM, Gold, Jack L (US SSA) wrote:
> I recently changed my installation process and allowed one of my company
> admins to install postgis 2.0 with the RHEL 5.9 installation, but I noticed
> w
ST_PixelAsPoints() isn't part of PostGIS 2.0 but is found in PostGIS 2.1.
As for the second never completing, you'd need to provide more information.
1. How big is sfdem? How many rows? Width/height of each rast in each row?
2. Never completing? How long have you waited? Have done a test cas
gvSIG 2.0 appears to have a PostGIS raster extension.
-bborie
On 01/29/2013 03:32 PM, José María wrote:
> Hello everybody!!
>
> I spent two days to convert a .tif file to Postgis table. I used *
> raster2pgsql* and the resulted was a table with three columns like that: *rid,
> rast, filename*.
The combination of PostgreSQL 9.2 and PostGIS 1.5 is not supported.
http://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS
-bborie
On 01/23/2013 03:56 PM, Max Pyziur wrote:
>
>
> Greetings,
>
> I've done a fresh install of F18 on a Dell Latitude D630 laptop.
>
> Until now, most issues
24 matches
Mail list logo
