Hi,
it is consistent this different which causes different results.
Thanks
On Wednesday, July 14, 2021, 11:55:28 a.m. EDT, Martin Davis
wrote:
The overlay operations do not necessarily preserve the exact sequence of input
vertices. This is the case for both GEOS and JTS. If you are
#1114: CAPI STRtree functions swallow errors
+---
Reporter: dbaston | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.10.0
Component: Default | Version: main
Severity:
#1000: behavior of GEOSCoordSeq_isCCW() is unclear when input is not a simple
closed curve
+---
Reporter: sirsigurd | Owner: geos-devel@…
Type: defect | Status: closed
Priority: major | Milestone: 3.10.0
#1000: behavior of GEOSCoordSeq_isCCW() is unclear when input is not a simple
closed curve
+---
Reporter: sirsigurd | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.10.0
Component:
#997: ST_Union performance degradation from GEOS 3.6.x -> 3.7.x
-+---
Reporter: greenlaw | Owner: geos-devel@…
Type: defect | Status: closed
Priority: major| Milestone: 3.10.0
Component: Default |
#755: Overlay ops accept GeometryCollections when headers indicate that they
don't
+---
Reporter: dbaston | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.10.0
Component:
Hi,
I found that the I use intersects the result shows that the first coordinates
is not used.Here is a sample that I did using two same geometries that shows
the issue.I tested similar code in Java using JTS and I don't have this issue.
// SIMPLE SIMULATION OF THE PROBLEM USING
The overlay operations do not necessarily preserve the exact sequence of
input vertices. This is the case for both GEOS and JTS. If you are seeing
a different, preferred order in JTS it's just by chance.
On Wed, Jul 14, 2021 at 7:46 AM Hector Nunez wrote:
> Hi,
>
> I found that the I use
