[postgis-tickets] [PostGIS] #4758: ERROR: XX000: SQL/MM Spatial exception - geometry crosses edge 2, LOCATION: pg_error, lwgeom_pg.c:250

[PostGIS]

#4758: ERROR:  XX000: SQL/MM Spatial exception - geometry crosses edge 2,
LOCATION:  pg_error, lwgeom_pg.c:250
-----------------------+---------------------------
  Reporter:  laopsahl  |      Owner:  strk
      Type:  defect    |     Status:  assigned
  Priority:  blocker   |  Milestone:  PostGIS 3.1.0
 Component:  topology  |    Version:  3.0.x
Resolution:            |   Keywords:
-----------------------+---------------------------

Comment (by strk):

 On further analisys I think I found the culprit.
 The code first nodes to existing edges and AFTER THAT snaps to existing
 elements.
 When snapping, the computed intersection nodes are not considered, and
 thus can result in moving (snapping) those intersection nodes to near-by
 elements (as the case above).
 This should be fixed by simply doing all snapping up-front (before
 noding).
 I'll try this approach.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4758#comment:19>
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.