Re: [geos-devel] [GEOS] #960: Exception when creating geometry buffer

2020-09-14 Thread GEOS
#960: Exception when creating geometry buffer
---+---
 Reporter:  allenkim0129   |   Owner:  geos-devel@…
 Type:  defect |  Status:  new
 Priority:  blocker|   Milestone:
Component:  Default| Version:  3.6.2
 Severity:  Unassigned |  Resolution:
 Keywords:  Buffer, TopologyException  |
---+---

Comment (by mdavis):

 Replying to [comment:3 strk]:
 > Martin can the usability range be computed to avoid such occurrences ?

 Maybe.  It might be that if the length of the end segments is less than
 the buffer distance then there may be visual artifacts present.  That
 would certainly include this case.  It's an overly aggressive heuristic
 though, since it would prevent running lots of cases which would not show
 artifacts.

 A more sophisticated heuristic would be to check if the end cap line
 intersected any of the side offset lines.

 But if what you are suggesting is throwing an error such as "Unable to
 compute buffer for given buffer distance", then this could just be emitted
 as the error when a TopologyException occurs.

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

Re: [geos-devel] [GEOS] #960: Exception when creating geometry buffer

2020-09-14 Thread GEOS
#960: Exception when creating geometry buffer
---+---
 Reporter:  allenkim0129   |   Owner:  geos-devel@…
 Type:  defect |  Status:  new
 Priority:  blocker|   Milestone:
Component:  Default| Version:  3.6.2
 Severity:  Unassigned |  Resolution:
 Keywords:  Buffer, TopologyException  |
---+---

Comment (by strk):

 Martin can the usability range be computed to avoid such occurrences ?

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

Re: [geos-devel] [GEOS] #980: GEOSBuffer emits invalid buffering a collection

2020-09-14 Thread GEOS
#980: GEOSBuffer emits invalid buffering a collection
+---
 Reporter:  komzpa  |   Owner:  geos-devel@…
 Type:  defect  |  Status:  new
 Priority:  major   |   Milestone:
Component:  Default | Version:  3.7.0
 Severity:  Unassigned  |  Resolution:
 Keywords:  |
+---

Comment (by strk):

 I'd like to test this with current GEOS but there's in input in this
 ticket ?
 Martin where did you find the input ?
 Both exhibit1 and exhibit2 are self-intersecting multipolygons.
 In both cases Buffer(0) output a still-invalid geometry, while UnaryUnion
 fixes the invalidity.
 I don't think by contract Buffer(0) is to be guaranteed to output a valid
 geometry from an invalid one ?

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