On Sun, Jan 23, 2011 at 09:53:17PM -0800, Martin Davis wrote:
FWIW, I ran this data through JTS 1.11 using both union(geom, geom) and
union(geom), and both operations completed without errors.
Not sure what this says about the GEOS issue - other than more debugging
required...!
Time
Of strk
Sent: Tuesday, 18 January 2011 2:48 AM
To: GEOS Development List
Subject: Re: [geos-devel] RE: GEOS errors from PostGIS
On Mon, Jan 17, 2011 at 11:05:42AM +1030, james.sew...@lisasoft.com wrote:
The latest daily doesn't help the problem so I've reverted to 3.2.2 and
performed some more
On Mon, Jan 17, 2011 at 11:05:42AM +1030, james.sew...@lisasoft.com wrote:
The latest daily doesn't help the problem so I've reverted to 3.2.2 and
performed some more testing.
I have a dataset where:
ST_Union(the_geom, ST_SetSRID('LINESTRING EMPTY', 4283))
Fails, yet
Of
james.sew...@lisasoft.com
Sent: Friday, 14 January 2011 5:29 PM
To: GEOS Development List
Subject: RE: [geos-devel] RE: GEOS errors from PostGIS
Heya,
The particular error I had in front of me isn't fixed by ST_Union(the_geom,
the_geom), but it is fixed by ST_Union(the_geom, ST_SetSRID
Message-
From: geos-devel-boun...@lists.osgeo.org
[mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of strk
Sent: Sunday, 16 January 2011 6:55 PM
To: Martin Davis
Cc: geos-devel@lists.osgeo.org
Subject: Re: [geos-devel] RE: GEOS errors from PostGIS
On Fri, Jan 14, 2011 at 05:37:05PM -0800
On Fri, Jan 14, 2011 at 05:37:05PM -0800, Martin Davis wrote:
Yes, I know it's a bad msg - it was a slip when commiting. Too late to
change now though.
Ok, reviewed... UnaryUnionOp is still unported to GEOS,
all the rest is up to date.
If anyone is willing to sponsor the port I'm available.
On Thu, Jan 13, 2011 at 07:51:16PM -0800, Martin Davis wrote:
James,
I suspect this may be caused by a known bug in the Unary union. This
was identified in this thread on the JTS list:
Rev 110
Modification was to switch to using SnapIfNeededOverlayOp
private Geometry unionNoOpt(Geometry g0)
{
Geometry empty = geomFact.createPoint((Coordinate) null);
return SnapIfNeededOverlayOp.overlayOp(g0, empty, OverlayOp.UNION);
}
On 1/14/2011 4:44 AM, strk
On Fri, Jan 14, 2011 at 08:14:40AM -0800, Martin Davis wrote:
Rev 110
Modification was to switch to using SnapIfNeededOverlayOp
private Geometry unionNoOpt(Geometry g0)
{
Geometry empty = geomFact.createPoint((Coordinate) null);
return
Yes, I know it's a bad msg - it was a slip when commiting. Too late to
change now though.
On 1/14/2011 10:18 AM, strk wrote:
On Fri, Jan 14, 2011 at 08:14:40AM -0800, Martin Davis wrote:
Rev 110
Modification was to switch to using SnapIfNeededOverlayOp
private Geometry
On Wed, Jan 12, 2011 at 12:53:01PM +1030, james.sew...@lisasoft.com wrote:
Sorry, I didn't include the actual error:
You didn't include PostGIS and GEOS versions as well:
SELECT postgis_full_version();
An example is:
NOTICE: TopologyException: found non-noded intersection between LINESTRING
James,
I suspect this may be caused by a known bug in the Unary union. This
was identified in this thread on the JTS list:
http://sourceforge.net/mailarchive/forum.php?thread_name=4C0FB4A5.2010304%40refractions.netforum_name=jts-topo-suite-user
I fixed this in JTS, in the
://www.lisasoft.com/
http://www.terrapages.comhttp://www.terrapages.com/
From: geos-devel-boun...@lists.osgeo.org
[mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Martin Davis
Sent: Friday, 14 January 2011 2:51 PM
To: geos-devel@lists.osgeo.org
Subject: Re: [geos-devel] RE: GEOS errors from
*Sent:* Friday, 14 January 2011 2:51 PM
*To:* geos-devel@lists.osgeo.org
*Subject:* Re: [geos-devel] RE: GEOS errors from PostGIS
James,
I suspect this may be caused by a known bug in the Unary union. This
was identified in this thread on the JTS list:
http://sourceforge.net/mailarchive/forum.php
Subject: RE: [geos-devel] RE: GEOS errors from PostGIS
Heya,
The particular error I had in front of me isn't fixed by ST_Union(the_geom,
the_geom), but it is fixed by ST_Union(the_geom, ST_SetSRID('LINESTRING EMPTY',
4283)). This is good news (although the errors seem to sometimes occur
Sorry, I didn't include the actual error:
An example is:
NOTICE: TopologyException: found non-noded intersection between LINESTRING
(143.861 -36.881, 143.861 -36.881) and LINESTRING (143.861 -36.881, 143.861
-36.881) at 143.861 -36.881
This particular one is a two very small identical lines,
16 matches
Mail list logo
