Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#482 closed defect (fixed)

UnaryUnion of a non-simple linestring doesn't node it

Reported by: strk Owned by: strk
Priority: major Milestone: 3.3.2
Component: Default Version: 3.3.1
Severity: Unassigned Keywords:
Cc:

Description

See http://postgis.refractions.net/pipermail/postgis-devel/2011-October/015392.html

I haven't tested 3.4dev and 3.2 branches, 3.3 branch is affected.

Change History (6)

comment:1 Changed 9 years ago by strk

NOTE: Martin added a test for this in TestUnaryUnion?.xml and should add another in UnaryUnionTest?.java. To be ported.

comment:2 Changed 9 years ago by Mike Taves

I assume an example of this bug is with LINESTRING (50 50, 150 150, 50 150, 150 50), which GEOS="3.3.1-CAPI-1.7.1" returns the exact same non-simple geometry while JTS returns a simple geometry

MULTILINESTRING ((50 50, 100 100), 
  (100 100, 150 150, 50 150, 100 100), 
  (100 100, 150 50))

comment:3 Changed 9 years ago by strk

Owner: changed from geos-devel@… to strk
Status: newassigned

I'm working on this

comment:4 Changed 9 years ago by strk

It looks like this bug was introduced by the fix for #392

comment:5 Changed 9 years ago by strk

Resolution: fixed
Status: assignedclosed

r3513 fixes this w/out loosing the robustness improvement introduced for #392.

Martin, if you're reading this, I suggest you take a look for JTS as well...

comment:6 Changed 9 years ago by strk

for the record, r3514 forward-ports this to trunk

Note: See TracTickets for help on using tickets.