Opened 7 years ago

Closed 7 years ago

#1775 closed defect (fixed)

False negative motion collision detection in ST_ChangeEdgeGeom

Reported by: strk Owned by: strk
Priority: high Milestone: PostGIS 2.0.1
Component: topology Version: 2.0.x
Keywords: Cc:

Description

While playing with topology edge simplification I encountered a case in which ST_ChangeEdgeGeom allows to change an edge geometry from A to B but doesn't allow it to move back from B to A.

Looking at the movement visually I can see that the movement should never be allowed.

Attachments (1)

collision.png (4.9 KB) - added by strk 7 years ago.

Download all attachments as: .zip

Change History (6)

Changed 7 years ago by strk

Attachment: collision.png added

comment:1 Changed 7 years ago by strk

from orange to green is allowed, from green to orange it is not: ERROR: Edge motion collision at POINT(699288 6901218)

The collision point is correctly reported as the island you see near the bottom.

comment:2 Changed 7 years ago by strk

I confirm that the result of the bogus allowance is an invalid topology (wrong face linking).

comment:3 Changed 7 years ago by strk

Summary: Asymmetric undetected edge motion collisionFalse negative motion collision detection in ST_ChangeEdgeGeom

comment:4 Changed 7 years ago by strk

Found the culprit: ST_SymDifference(EMPTY, POLY) returns EMPTY -- filed #1776 for this. Once that one is fixed this one should also be. We'll want a testcase for this anyway.

comment:5 Changed 7 years ago by strk

Resolution: fixed
Status: newclosed

r9641 fixes ST_SymDifference and r9642 regress-tests this specific use case.

Note: See TracTickets for help on using tickets.