[
https://issues.apache.org/jira/browse/LUCENE-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430235#comment-16430235
]
Karl Wright commented on LUCENE-8245:
-------------------------------------
Reformatted, for easier reading:
{code}
[junit4] 1> The following edges should intersect the travel/testpoint
planes:
[junit4] 1> Travel plane: [lat=-1.4506713533447755,
lon=-1.2251247551355924([X=0.04060395941016342, Y=-0.11274773940940182,
Z=-0.9927936672533157])] -> [lat=4.9E-324, lon=0.0([X=1.0, Y=0.0, Z=4.9E-324])]
[junit4] 1> Test point plane: [lat=-1.4506713533447755,
lon=-1.2251247551355924([X=0.04060395941016342, Y=-0.11274773940940182,
Z=-0.9927936672533157])] -> [lat=4.9E-324, lon=0.0([X=1.0, Y=0.0, Z=4.9E-324])]
[junit4] 1> Travel plane: [lat=4.9E-324, lon=0.0([X=1.0, Y=0.0,
Z=4.9E-324])] -> [lat=0.13953211802880663,
lon=-2.443438340098597([X=-0.7585849990851791, Y=-0.6365576248361361,
Z=0.139079795174987])]
[junit4] 1>
[junit4] 1> Considering edge [lat=-0.6183600459696781,
lon=-2.770488856855538([X=-0.7593628058597481, Y=-0.29549354861758625,
Z=-0.5796996565482825])] -> [lat=-1.4506713533447755,
lon=-1.2251247551355924([X=0.04060395941016342, Y=-0.11274773940940182,
Z=-0.9927936672533157])]
[junit4] 1>
[junit4] 1> Considering edge [lat=-1.4506713533447755,
lon=-1.2251247551355924([X=0.04060395941016342, Y=-0.11274773940940182,
Z=-0.9927936672533157])] -> [lat=4.9E-324, lon=0.0([X=1.0, Y=0.0, Z=4.9E-324])]
[junit4] 1> Travel inner point [X=1.0, Y=-1.336807223683658E-12,
Z=-1.1771178322187736E-11]
[junit4] 1> Test point inner point [X=0.7540698997149413,
Y=-0.07411317803504912, Z=-0.6525992822440454]
[junit4] 1> Edge added 2 to innerCrossingCount
[junit4] 1> Test point outer point [X=0.7540698997131706,
Y=-0.07411317803527853, Z=-0.6525992822460656]
[junit4] 1> Edge added 1 to outerCrossingCount
[junit4] 1>
[junit4] 1> Considering edge [lat=4.9E-324, lon=0.0([X=1.0, Y=0.0,
Z=4.9E-324])] -> [lat=0.13953211802880663,
lon=-2.443438340098597([X=-0.7585849990851791, Y=-0.6365576248361361,
Z=0.139079795174987])]
[junit4] 1> Travel inner point [X=1.0, Y=-1.3368072236836578E-12,
Z=2.920754816285907E-13]
[junit4] 1> Edge added 1 to innerCrossingCount
[junit4] 1> Travel outer point [X=1.0, Y=6.831927763163421E-13,
Z=-1.4926898632243605E-13]
[junit4] 1> Edge added 1 to outerCrossingCount
{code}
As you can see, there's one edge that adds TWO inner crossings and one outer
crossing. Quite a feat. Figuring out how it does that is the trick.
> GeoComplexPolygon fails when intersection of travel plane with edge is near
> polygon point
> -----------------------------------------------------------------------------------------
>
> Key: LUCENE-8245
> URL: https://issues.apache.org/jira/browse/LUCENE-8245
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/spatial3d
> Reporter: Ignacio Vera
> Assignee: Karl Wright
> Priority: Major
> Fix For: 6.7, 7.4, master (8.0)
>
> Attachments: LUCENE-8245-case2.patch, LUCENE-8245.patch
>
>
> When a travel plane crosses an edge close to an edge point , it is possible
> that the above and below planes crosses different edges. In the current
> implementation one of the crosses is missed because we only check edges that
> are crossed by the main plain and the {{within}} result is wrong.
> One possible fix is to check always the intersection of planes and edges
> regardless if they are crossed by main plane. That fixed the above issue but
> shows other issues like travel planes crossing two edges when it should be
> only one due to the fuzziness at edge intersections.
> Not sure of a fix so I add the test showing the issue.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
