[postgis-users] Re: st_union exception

Obe, Regina robe.dnd at cityofboston.gov
Thu Jan 15 12:09:42 PST 2009


Forgot to mention 1.3.5 is the latest PostGIS stable.

So in summary

GEOS 3.0.3, PostGIS 1.3.5

Though you should be fine with just upgrading your GEOS. 

-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Obe,
Regina
Sent: Thursday, January 15, 2009 3:00 PM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] Re: st_union exception

3.0.3 is the latest stable 

-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Mark
Mitchell
Sent: Thursday, January 15, 2009 2:38 PM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] Re: st_union exception

It is an older version of PostGIS/GEOS (1.3.3 and 2.2.3) -- which
version of GEOS are you using?

-Mark

> Is this an older version of PostGIS/GEOS?  I believe that most of
these
> kinds of problems were addressed in a release of GEOS last year.
>
> Mark Mitchell wrote:
> > Anyone get an error similar to this when unioning a bunch of
polygons
> > with st_union?
> >
> > NOTICE:  TopologyException: no outgoing dirEdge found
(-149.073,61.6101,61.6101)
> > ERROR:  GEOS union() threw an error!
> >
> > I must say before I get into the details only a few of you will read
> > that portion that I've used postgis for a while now (since 1.1.5)
and
> > it is *PHENOMENAL*.  I don't want my only posts to this list in that
> > time frame to be negative -- can't tell you how much
> > faster/better/intuitive I've found postgis over very expensive
> > commercial alternatives :-).
> >
> >
> > My query is similar to the following:
> >
> > SELECT st_multi(st_union(poly)) from (select ... (a bunch of polys)
... ) a;
> >
> > The subselect is operating on a fairly dynamic table, and I've gone
> > months without any problems (with many different sets of polygons
too)
> >
> > I tried st_isvalid() on all polygons returned from the subselect,
and
> > all are valid, and are all non-null...
> > If I have duplicate (or close to duplicate) polygons returned, is
that
> > going to potentially screw up st_union()?
> >
> >
> > I'm running Ubuntu server (x64) 8.04 LTS, and am using the packages
> > for GEOS and postgis from their universe repo:
> >
> > postgis 1.3.3
> > libgeos 2.2.3
> >
> > (postgresql 8.3)
> >
> >
> > Thanks for the help!
> >
> > -Mark
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> >
> >
>
> --
> Martin Davis
> Senior Technical Architect
> Refractions Research, Inc.
> (250) 383-3022
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users



More information about the postgis-users mailing list