[postgis-tickets] [PostGIS] #5234: ring geometrically not-closed on 3D topology

[PostGIS]

#5234: ring geometrically not-closed on 3D topology
----------------------+---------------------------
 Reporter:  amsilva   |      Owner:  strk
     Type:  defect    |     Status:  new
 Priority:  medium    |  Milestone:  PostGIS 3.3.1
Component:  topology  |    Version:  3.2.x
 Keywords:            |
----------------------+---------------------------
 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 [https://lists.osgeo.org/pipermail
 /postgis-users/2022-September/045636.html 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.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5234>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.