REGRESSION: ring geometrically not-closed on 3D topology
|Reported by:||amsilva||Owned by:||strk|
When adding an edge to the topology with totopogeom sometimes it gives this error "Corrupted topology: ring of edge x is geometrically not-closed".
I reduced the problem to an example with two lines. The first line is added with no errors to the topology but the second one throws this error. The second line intersects with the first one, but there's no vertex on the intersection. (example attached)
This bug results of a postgis-user post where Sandro Santilli confirmed the bug and complemented with this:
Gory details: the problem likely lays in _lwt_MakeRingShell which was recently changed to NOT use GEOS but rather do things internally, to reduce overhead. The internal implementation is NOT dropping the Z as the geos implementation did.
Change History (11)
comment:1 by , 5 months ago
|Milestone:||PostGIS 3.3.1 → PostGIS 3.2.4|
|Priority:||medium → high|
|Summary:||ring geometrically not-closed on 3D topology → REGRESSION: ring geometrically not-closed on 3D topology|