[ https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240243#comment-15240243 ]
Karl Wright edited comment on LUCENE-7212 at 4/13/16 11:39 PM: --------------------------------------------------------------- For 2D, there's quite a bit to choose from, e.g. the O( N ) cross-product solution described here: http://stackoverflow.com/questions/471962/how-do-determine-if-a-polygon-is-complex-convex-nonconvex For 3D it's more challenging. I'll keep thinking about it, of course... was (Author: kwri...@metacarta.com): For 2D, there's quite a bit to choose from, e.g. the O$(n$) cross-product solution described here: http://stackoverflow.com/questions/471962/how-do-determine-if-a-polygon-is-complex-convex-nonconvex > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org