[
https://issues.apache.org/jira/browse/LUCENE-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223710#comment-15223710
]
Karl Wright edited comment on LUCENE-7157 at 4/4/16 6:15 AM:
-------------------------------------------------------------
Here's the latest; not much different from before but iterates over the
directional test to be sure its inherent pole choice algorithm is not a factor.
Beasting passes for me too.
was (Author: [email protected]):
Here's the latest; not much different from before but iterates over the
directional test to be sure its inherent pole choice algorithm is not a factor.
> Geo3DPoint implementation should pay attention to the ordering of lat/lon
> points
> --------------------------------------------------------------------------------
>
> Key: LUCENE-7157
> URL: https://issues.apache.org/jira/browse/LUCENE-7157
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Karl Wright
> Attachments: LUCENE-7157.diff, LUCENE-7157.diff, LUCENE-7157.diff,
> LUCENE-7157.diff, LUCENE-7157.diff
>
>
> The LatLonPoint API implementation pays attention to the order of the points;
> "clockwise" means one side of the polygon boundary, and "counterclockwise"
> means the complement. We need to use that in Geo3DPoint and convert into
> whatever the underlying GeoPolygonFactory method requires.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
