Re: [postgis-users] Postgres 9.2
You can't use PostGIS compiled for one version of PostgreSQL on a different version of PostgreSQL. They are not compatible binaries across versions. We'll have 2.0.1 for PostgreSQL 9.2 available for Windows probably sometime next week. However -- we do have PostGIS 2.1.0SVN available for 9.2 already. You should be able to just copy the files into your 9.2 and run CREATE EXTENSION postgis; as usual. No incompatibilities have been introduced in 2.1.0, just faster and more functionality - http://www.bostongis.com/blog/index.php?/categories/21-waiting_postgis_21 so if you have an app that relies on 2.0 it should work just dandy with 2.1.0 SVN. http://www.postgis.org/download/windows/pg92/buildbot/ and if you restore your 9.1 backup on 9.2 (assuming you used CREATE EXTENSION), it will automatically upgrade itself. You'll want to be on 2.1.0 for 9.2 anyway since that will have features -- SPGist (not yet committed) specifically designed for leveraging 9.2 Hope that helps, Regina and Leo http://www.postgis.us _ From: postgis-users-boun...@postgis.refractions.net [mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Chris Haste Sent: Wednesday, September 12, 2012 6:50 AM To: postgis-users@postgis.refractions.net Subject: [postgis-users] Postgres 9.2 Hello List, Has anyone successfully installed PostGIS 2.0.1 with Postgres 9.2 on a windows platform? I have tried (using the PostGIS for Postgres 9.1 installer and specifying the 9.2 path during installation) but I keep getting the error when I try and create a DB using CREATE EXTENSION. ERROR: could not load library C:/Program Files/PostgreSQL/9.2/lib/postgis-2.0.dll: The specified module could not be found. But the DLL is there in that location! Any ideas? Thanks *** This communication has been sent from World Fuel Services Corporation or its subsidiaries or its affiliates for the intended recipient only and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any review, disclosure, copying, use, or distribution of the information included in this communication and any attachments is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this communication and delete the communication, including any attachments, from your computer. Electronic communications sent to or from World Fuel Services Corporation or its subsidiaries or its affiliates may be monitored for quality assurance and compliance purposes.*** ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
[postgis-users] Behavior of ST_MapAlgebraFctNgb
Hey all,
I'm trying to make use of ST_MapAlgebraFctNgb to do some inverse
distance weighting and noticed some unexpected behavior.
{{{
CREATE OR REPLACE FUNCTION ngb_test(matrix float8[][], nodatamode text,
VARIADIC args text[])
RETURNS float8
AS $$
DECLARE
BEGIN
RAISE NOTICE '%', matrix;
RETURN 255;
END;
$$ LANGUAGE 'plpgsql';
WITH foo AS (
SELECT
ST_SetValues(
ST_AddBand(
ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0)
, 1, '8BUI', 0, 0
)
, 1, 1, 1, ARRAY[
[ 1, 2, 3, 4, 5],
[ 6, 7, 8, 9,10],
[11,12,13,14,15],
[16,17,18,19,20],
[21,22,23,24,25]
]::double precision[]
) AS rast
)
SELECT
(ST_PixelAsPoints(
st_mapalgebrafctngb(rast, 1, NULL, 1, 1,
'ngb_test(float8[][],text,text[])'::regprocedure, 'NULL', NULL)
)).*
FROM foo
}}}
In testing the neighborhood, the ngb_test function is only being called
for the interior pixels. The function isn't called for the pixels found
at the edges.
Is this expected behavior? My guess is no as far as my understanding of
the specs...
http://trac.osgeo.org/postgis/wiki/WKTRaster/SpecificationWorking02
3) ST_MapAlgebraFctNgb(rast raster, band int, pixeltype text, radius
int, funcname text[, funcargs text]) - A one raster version taking a
user defined function (with optional parameters) of the set of first,
second, etc... neighbours of a pixel. The function is a user defined
PL/pgSQL function taking a matrix containing the neighbour values and
returning one value. Code do not exist yet but will be very much similar
to 2). Out of bound pixels values are set to NULL. This version requires
the user to write a PL/pgSQL function. Many predefined function should
be delivered.
The key part for me is that Out of bound pixels values are set to
NULL., which isn't how ST_MapAlgebraFctNgb is currently behaving.
-bborie
___
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] CentOS PostGIS installation problem
Your answer is there, libgeos_c.so.1: cannot open shared object file for some reason your postgis can't find your libgeos. The usual reason is that it got installed in /usr/local/lib, but the linker doesn't know about /usr/local/lib. This can be fixed by adding /usr/local/lib to /etc/ld.so.conf and running /sbin/ldconfig P. On Thu, Sep 13, 2012 at 6:34 PM, Carol Peck carolap...@gmail.com wrote: Hi, I'm trying to get PostGIS running on CentOS 5.8 (on a VPS). I have Postgres 8.4 installed from rpm. I built PostGIS 1.5 from source, install and make went properly. When I try to run postgis.sql I get the following, starting with the first line: psql:/usr/share/pgsql/contrib/postgis-1.5/postgis.sql:59: ERROR: could not load library /usr/lib64/pgsql/postgis-1.5.so: libgeos_c.so.1: cannot open shared object file: No such file or directory and then later after aborted transaction errors: psql:/usr/share/pgsql/contrib/postgis-1.5/postgis.sql:7782: ERROR: type box2d does not exist psql:/usr/share/pgsql/contrib/postgis-1.5/postgis.sql:7783: ERROR: type geometry does not exist psql:/usr/share/pgsql/contrib/postgis-1.5/postgis.sql:7791: ERROR: type geometry[] does not exist Thanks in advance for any help! ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
