[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):

 Performance is not of my concern in this stage, but correctness is.

 Your idea boils down to basically implement "snap-to-segment", which was
 one idea I have been in mind for some time now. But this means NOT buying
 the argument of "vertices are more important than lines", do you think
 this is correct ?

 Note that even if we snap to segments, we'll _need_ to split the first
 segment and the two resulting edges might slightly move anyway (due to
 need to represent that node). The movement should be small so hopefully
 won't create another collision, but this has to be kept in mind.


 So, do you still think incoming vertices should snap to existing edges
 (not vertices) ? If so I could look into doing this.

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