Well thats an easy one.
If they *exactly* join,
http://postgis.refractions.net/documentation/manual-1.4/ST_Union.html
if they are a bit squishy, then one simple way is to:
- st_buffer the multiple polygons all individually outwards by say 10km,
- st_union them into a single polygon
- st_buffer
On Mon, 12 Aug 2013, Peter wrote:
Well thats an easy one.
If they *exactly* join,
http://postgis.refractions.net/documentation/manual-1.4/ST_Union.html
if they are a bit squishy, then one simple way is to:
- st_buffer the multiple polygons all individually outwards by say 10km,
- st_union
Hei Håvard,
Er det ei internt SL-liste det er snakk om?
Ja. Men kanskje det er nyttig å ha en generell postgis list for norge?...
OK, jeg har gjort en nå. e-post til
postgis-norge+subscr...@googlegroups.com å bli med eller
postgis-no...@googlegroups.com for diskusjonen.
La oss
Hello
I'm trying to copy polygons from one column to another to reduce vertex
numbers
my columns are geom (geom geometry(MultiPolygonZ,3004))
and geom_simply (geom_simply geometry(MultiPolygonZ,3004))
With this query
UPDATE mytable
SET geom_simply=ST_SimplifyPreserveTopology(geom, 100)
I get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/08/2013 13:19, Pietro Rossin ha scritto:
UPDATE mytable SET
geom_simply=ST_SimplifyPreserveTopology(st_multi(geom), 100)
ERROR: Geometry type (Polygon) does not match column type
(MultiPolygon) SQL state: 22023
Why?
Try
SET
Just thought I'd respond to say I've finally got this working. Thank
you to all of your for your help. It turned out that running the below
command before trying to use pg_restore sorted my problem:
psql -d [yourdatabase] -f legacy.sql
So in summary I have just upgraded PostgresSQL 9.0 with
Thanks Paolo
It worked like this:
set geom_simply=ST_Multi(ST_SimplifyPreserveTopology(geom, 100))
Bie
Pietro
2013/8/12 Paolo Cavallini cavall...@faunalia.it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/08/2013 13:19, Pietro Rossin ha scritto:
UPDATE mytable SET
Glad to hear you got it working! What is legacy.sql? Did my other steps help?
-Original Message-
From: postgis-users-boun...@lists.osgeo.org
[mailto:postgis-users-boun...@lists.osgeo.org] On Behalf Of James David Smith
Sent: Monday, August 12, 2013 7:33 AM
To: PostGIS Users Discussion
To be honest Brian I'm not quite sure what legacy.sql did. It is
listed here though, and it's not something I'd noticed before so
thought it was worth a go!
http://postgis.net/docs/manual-dev/postgis_installation.html#create_new_db
I guess it deals with compatibility issues somehow.
James
On
Perfect, I will make a note of this myself.
Brian
-Original Message-
From: postgis-users-boun...@lists.osgeo.org
[mailto:postgis-users-boun...@lists.osgeo.org] On Behalf Of James David Smith
Sent: Monday, August 12, 2013 7:55 AM
To: PostGIS Users Discussion
Subject: Re: [postgis-users]
It seems a lot of changes have been done today which has made the PostGIS
bots very angry.
http://trac.osgeo.org/postgis/ticket/2425#comment:1
This needs to be resolved before we can release.
I also found an issue with the ST_Dwithin which I can only replicate with
proprietary data at the
11 matches
Mail list logo
