[PostGIS] #5786: Side-location conflict: new edge starts in face 42 and ends in face 10

[PostGIS]

#5786: Side-location conflict: new edge starts in face 42 and ends in face 10
--------------------------------+---------------------------
  Reporter:  Lars Aksel Opsahl  |      Owner:  strk
      Type:  defect             |     Status:  new
  Priority:  medium             |  Milestone:  PostGIS 3.5.1
 Component:  topology           |    Version:  master
Resolution:                     |   Keywords:  robustness
--------------------------------+---------------------------
Comment (by Lars Aksel Opsahl):

 Replying to [comment:11 strk]:
 > Oh you are right, we are able to silently create an invalid topology
 with the last testcase (the one adding a single point). I believe that's
 due to #5787 basically

 I have been testing on this setup today.

 {{{
 POSTGIS="3.6.0dev 3.5.0-13-g290fffd11" [EXTENSION] PGSQL="160"
 GEOS="3.13.0beta2-CAPI-1.19.0" PROJ="9.3.0 NETWORK_ENABLED=OFF
 URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj
 DATABASE_PATH=/usr/local/share/proj/proj.db" (compiled against PROJ
 9.13.0) LIBXML="2.9.13" LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0
 (Internal)" TOPOLOGY
 }}}

 1) When running on the master topology where I do COPY in data from
 working sub topologies area get lost. I did see that a lot line that could
 form a face but left_fact right_face was wrong.

 2) If I instead used Topology.AddLinstring from the temp toplogies into
 the master topology the missings faces turn out OK.

 (I have to test more on this but now this servers are used for trying
 fixing prod
  data, so I have to test more on this later)
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5786#comment:12>
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.