[PostGIS] #5782: TopoGeo_addLinestring corrups topology: adjacent edges 33 and -32 bind different face (1 and 0)
PostGIS
trac at osgeo.org
Wed Sep 25 11:51:58 PDT 2024
#5782: TopoGeo_addLinestring corrups topology: adjacent edges 33 and -32 bind
different face (1 and 0)
--------------------------------+---------------------------
Reporter: Lars Aksel Opsahl | Owner: strk
Type: defect | Status: new
Priority: high | Milestone: PostGIS 3.4.4
Component: topology | Version:
Resolution: | Keywords:
--------------------------------+---------------------------
Comment (by Lars Aksel Opsahl):
Replying to [comment:21 Lars Aksel Opsahl]:
> Replying to [comment:20 mdavis]:
> > It seems problematic to rely on distance calculation to determine
topology, since it's inherently less precise than the actual geometric
situation.
> >
> > Perhaps the fundamental problem is treating nearly-identical
linestrings as distinct edges. Would it be possible to specify a distance
tolerance, and raise an error if lines contain distinct sections which are
closer than the tolerance?
>
> What you say about tolerance think makes since, because I had big area
missing and it did help some to make cell, but al it did not fix all
problems and I did not expect that .
>
> But then I did only one change switching from
>
>
> {{{
> select topology.CreateTopology ('toplogy_name', 4258, 1e-06);
> }}}
>
> to
>
>
> {{{
> select topology.CreateTopology ('toplogy_name', 4258, 1e-05);
>
> }}}
>
> and all area seems to recovered for that part.
But for resolve-overlap-and-gap/src/test/sql/regress/topology_test_02.sql
i god up to 1e-04
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5782#comment:22>
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.
More information about the postgis-tickets
mailing list