[
https://issues.apache.org/jira/browse/LUCENE-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222377#comment-15222377
]
Karl Wright edited comment on LUCENE-7157 at 4/1/16 10:11 PM:
--------------------------------------------------------------
Still working on this problem.
There are two issues -- one having to do with pole selection, and the other
having to do with polygons spanning more than 180 degrees. I'm introducing
GeoConcavePolygon to help handle the latter case but I need to rework the
GeoPolygonFactory method that breaks up non-convex polygons to generate these,
and that is turning out to be algorithmically complex. Probably will be
working on it all weekend...
was (Author: [email protected]):
Still working on this problem.
There are two issues -- one having to do with pole selection, and the other
having to do with polygons (spanning more than 180 degrees). I'm introducing
GeoConcavePolygon to help handle the latter case but I need to rework the
GeoPolygonFactory method that breaks up non-convex polygons to generate these,
and that is turning out to be algorithmically complex. Probably will be
working on it all weekend...
> 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]
