[postgis-tickets] [PostGIS] #4990: getfacecontainingpoint fails on i386
PostGIS
trac at osgeo.org
Fri Sep 24 13:18:35 PDT 2021
#4990: getfacecontainingpoint fails on i386
-----------------------------+---------------------------
Reporter: Bas Couwenberg | Owner: strk
Type: defect | Status: new
Priority: medium | Milestone: PostGIS 3.2.0
Component: topology | Version: master
Resolution: | Keywords:
-----------------------------+---------------------------
Comment (by strk):
The macro was good, the *caller* of the macro was not (and no compiler
warnings by default, which we should fix -- #5002).
After fixing the the call, with
[9042ee9fae5f7350cd3b2cd6798fb24e093719c7/git], this is the debugging
output:
{{{
DEBUG: [lwgeom_topo.c:lwt_GetFaceContainingPoint:7097] Shortest line to
closest edge 26: LINESTRING(7 31,7.1 31)
DEBUG: [lwgeom_topo.c:lwt_GetFaceContainingPoint:7103] Closest point on
closest edge: POINT(7 31)
DEBUG: [lwgeom_topo.c:lwt_GetFaceContainingPoint:7209] Closest point is
NOT a node
DEBUG: [lwgeom_topo.c:lwt_GetFaceContainingPoint:7236] Closest segment to
edge 26 is 0
DEBUG: [lwgeom_topo.c:lwt_GetFaceContainingPoint:7239] Closest segment to
edge 26 is LINESTRING(0 5.31406e-315, 5.32539e-315 5.31406e-315)
}}}
My PR was fixing the alignment-requiring reads of shortestLine but the
problem seems to be in closestSegment...
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4990#comment:23>
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