Karl Wright commented on LUCENE-8245:

I believe I've come up with a better way to do this.  It involves two basic 
(1) using only actual intersections with the envelope planes, so no "zone" is 
needed, and the envelope planes go back to being exactly MINIMUM_RESOLUTION 
from the main travel planes; and
(2) evaluating the envelope plane intersections, one at a time, for whether 
they constitute a "crossing" from the main travel plane "zone" outside of that 

The second requires the generation of a pair of adjoining points, also on the 
edge plane, that are about MINIMUM_RESOLUTION away from the intersection.  We 
look at both points, and if one is inside the travel plane "zone" and the other 
is not, then we call it a crossing.

I'm coding this up now but it's already a very busy work day and this probably 
won't be completed and debugged until tonight at the earliest.

> 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.jpg, 
> LUCENE-8245.patch, LUCENE-8245_Polygon.patch, LUCENE-8245_Random.patch, 
> LUCENE-8245_case3.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

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to