Re: [geos-devel] RE: GEOS errors from PostGIS

2011-01-13 Thread strk
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

Re: [geos-devel] RE: GEOS errors from PostGIS

2011-01-13 Thread Martin Davis
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

RE: [geos-devel] RE: GEOS errors from PostGIS

2011-01-13 Thread james.sew...@lisasoft.com
Thanks Martin, I'll install the latest nightly build of GEOS, recompile PostGIS and hope for the best. Reading the thread does that mean that st_union(geom, geom) should work in this case? I had previously done some testing and it didn't seem to, I'll test again though. Cheers, James Sewell

Re: [geos-devel] RE: GEOS errors from PostGIS

2011-01-13 Thread Martin Davis
In the case of lines, I think GEOS Unary Union just delegates to union(lines, empty point). So you could try running st_union(lines, empty point) and see if that works. If this doesn't work, it could just be a case where the snapping heuristic tolerances aren't being set large enough to

RE: [geos-devel] RE: GEOS errors from PostGIS

2011-01-13 Thread james.sew...@lisasoft.com
Sorry false alarm, the UNION wasn't working properly and was getting overlapping polygons (so not really doing anything). Once I fixed this I got the same error when using: SELECT st_union(ST_snaptogrid(the_geom,10E-10), ST_SetSRID('LINESTRING EMPTY', 4283)) AS the_geom I'll try and get some