[geos-devel] Re: [GEOS] #488: TopologyException unioning valid geometries [JTS fails]

2011-12-15 Thread GEOS
#488: TopologyException unioning valid geometries [JTS fails]
+---
 Reporter:  sky |Owner:  geos-devel@…  
 Type:  defect  |   Status:  reopened  
 Priority:  major   |Milestone:  GEOS Future   
Component:  Default |  Version:  svn-trunk 
 Severity:  Unassigned  |   Resolution:
 Keywords:  jts fails   |  
+---

Comment(by strk):

 self-unioning an operand becoming invalid after snap fixes this case.
 Attaching an updated reduced version with expected result (obtained with
 this heuristic)

-- 
Ticket URL: http://trac.osgeo.org/geos/ticket/488#comment:27
GEOS http://geos.refractions.net/
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] [GEOS] #504: Consider replacing -ffloat-store with -fexcess-precision=standard

2011-12-15 Thread GEOS
#504: Consider replacing -ffloat-store with  -fexcess-precision=standard
+---
 Reporter:  strk|   Owner:  geos-devel@…  
 Type:  task|  Status:  new   
 Priority:  major   |   Milestone:  3.3.2 
Component:  Default | Version:  3.3.1 
 Severity:  Unassigned  |Keywords:
+---
 See:
 http://archives.postgresql.org/pgsql-hackers/2011-12/msg00647.php

 And see if such switch would bring us closer to JTS numeric handling

-- 
Ticket URL: http://trac.osgeo.org/geos/ticket/504
GEOS http://geos.refractions.net/
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] Change in overlay failure handling heuristic

2011-12-15 Thread Sandro Santilli
Dear overlayers and exception catchers,

as of r3552 the heuristic used for trying to get to some kind of overlay
result in case of robustness issues (BinaryOp) has been augomented
to perform an additional check to the results of snapping the input
geometries each-other, and running a self-union whenever such snapped
geoms result invalid.

Such behavior is to fix the cases in which snapping
creates self-intersections thus introducing problems
for later computations.

It is known to fix at least one case:
http://trac.osgeo.org/geos/ticket/488

Additional work is required to check for validity, but you'd never
get to that point unless the _original_ run (w/out snaprounding)
worked.

Please test the new behavior as I plan to ship it with upcoming 3.3.2.
Thank you.

--strk; 

  ,--o-. 
  |   __/  |Thank you for PostGIS-2.0 Topology !
  |  / 2.0 |http://www.pledgebank.com/postgistopology
  `-o--'

___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel