[ 
https://issues.apache.org/jira/browse/LUCENE-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725265#comment-14725265
 ] 

Karl Wright commented on LUCENE-6759:
-------------------------------------

The path is a four-point one.  The part of the path that contains the point is 
the first segment.  This segment has four bounding planes and four corner 
points.  The point in question has the following coordinates:

{code}
   [junit4]   2> Point.x = 1.0005691667476262; point.y=0.023149205146987442; 
point.z=0.023676292209381222
{code}

My augmented output for getting the bounds for the segment shows that it is the 
upper connecting plane that determines the maxX boundary for the shape:

{code}
   [junit4]   2>  upperConnectingPlane...
   [junit4]   2>     computing Z bound
   [junit4]   2>     not degenerate
   [junit4]   2>     computing X bound
   [junit4]   2>     not degenerate; B=-0.5302912804708979; 
C=-0.5331856607581867
   [junit4]   2>       Point = [X=1.0005682443631527, Y=0.022204817350270467, 
Z=0.02459563634844797]; this.evaluate(point)=0.0; 
normalizedXPlane.evaluate(point)=4.163336342344337E-17
   [junit4]   2>     computing Y bound
   [junit4]   2>     not degenerate
{code}

The point of maximum excursion's X value, though, is X=1.0005682443631527.  The 
actual X value of the point we're checking is Point.x = 1.0005691667476262.  So 
that's the disagreement.  The next step is to see how that difference arises.  
Specifically, the point found is on the upperConnectingPlane (eval = 0.0), and 
on the plane I have constructed that should represent a perpendicular to the 
upperConnectingPlane going through the point of maximum excursion.  I'll have 
to verify that that is indeed the case.


> Integrate lat/long BKD and spatial 3d, part 2
> ---------------------------------------------
>
>                 Key: LUCENE-6759
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6759
>             Project: Lucene - Core
>          Issue Type: New Feature
>            Reporter: Michael McCandless
>         Attachments: LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, 
> LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, 
> LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, 
> LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch
>
>
> This is just a continuation of LUCENE-6699, which became too big.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to