[ 
https://issues.apache.org/jira/browse/LUCENE-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223692#comment-15223692
 ] 

Karl Wright commented on LUCENE-7157:
-------------------------------------

bq. Just like I don't think users need to deal with radians, I don't think they 
should know about concaveness either. I understand that geo3d is different, but 
it needs to not unload the challenges of 3d-ness onto the user but instead use 
it behind the scenes.

While I agree in general, there *is* a specification problem, which is that if 
you describe any polygon on the face of the earth by a series of points, there 
are two possible areas you are in fact describing -- one on one side of the 
polygon, and one on the other.  Geo3D has always required some means of 
specifying which area the user means, but through ways that were difficult to 
use.  ESRI uses clockwise/counterclockwise to allow the user to describe which 
area the user means, which is a lot cleaner, and that is what this ticket is 
about.

The Lucene API's will need to make similar functionality available somehow.  I 
had thought that they adhered to the ESRI mechanism but I'm now confused 
whether this was what you actually intended to do.  I would love to have some 
confirmation one way or another before proceeding to manifest the 
clockwise/counterclockwise functionality into the official Geo3DPoint API.

> 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
>
>
> 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]

Reply via email to