[
https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242911#comment-15242911
]
Karl Wright commented on LUCENE-7212:
-------------------------------------
I'm still holding off on doing anything here for two reasons:
(1) I need to finish figuring out the math of producing a bound that is
constrained by distance for geo3d, and
(2) I want to wait until the docvalues field is pulled out of the corresponding
LatLon classes before introducing geo3d classes.
If I'm not very much mistaken, (1) is crucial for this functionality to be a
performance win, so I need to make sure the math works first. I whacked away
at it for a good chunk of my non-meeting hours yesterday before getting
distracted by general large polygon performance concerns, but I ran into
trouble with expression complexity related to the ellipsoid nature of WGS84. I
probably need to transform the problem in some way to make it tractable, and I
tried one way already that looked like it would work, but it wound up still
making too messy an expression to deal with. Working more on this this
weekend...
> Add Geo3DPoint equivalents of LatLonPointDistanceComparator and
> LatLonPointSortField
> ------------------------------------------------------------------------------------
>
> Key: LUCENE-7212
> URL: https://issues.apache.org/jira/browse/LUCENE-7212
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: master
> Reporter: Karl Wright
> Assignee: Karl Wright
>
> Geo3D has a number of distance measurements and a generic way of computing
> interior distance. It would be great to take advantage of that for queries
> that return results ordered by interior distance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
