[
https://issues.apache.org/jira/browse/LUCENE-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221580#comment-15221580
]
Karl Wright commented on LUCENE-7157:
-------------------------------------
Hi Robert,
I'm not sure what you are talking about? The only thing that has been forked,
near as I can tell, is the implementation of GeoUtils.checkLatitude() and
GeoUtils.checkLongitude(). That's relatively constrained. I have not yet even
begun to try to add the API method that requires Polygon objects; I'm trying to
wait until the dust settles before doing that. But I was confused about some
aspects of your API and am trying to figure out where you are coming from.
> 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
>
> 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]
