[jira] [Commented] (LUCENE-7906) Spatial relationship between Geoshapes

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Commented] (LUCENE-7906) Spatial relationship between Geoshapes

JIRA jira@apache.org

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

Karl Wright commented on LUCENE-7906:

Hi [~ivera],

In Geo3D, there is currently only support for computing the intersection with shapes that implement GeoArea.  These only include GeoBBox (2D) and XYZSolid (3D).  Currently, GeoPolygon objects do *not* implement GeoArea.  This is by design.  There are many cases and corner cases that would need algorithmic development to properly implement polygon intersection.

If you need to support this case, feel free to supply a patch where GeoPolygon extends GeoArea.  You will need to implement getRelationship() for GeoComplexPolygon, GeoConvexPolygon, GeoConcavePolygon, and GeoCompositePolygon.  I would also urge you to include many test cases to be sure your code is working as designed.

> Spatial relationship between Geoshapes
> --------------------------------------
>                 Key: LUCENE-7906
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7906
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/spatial3d
>            Reporter: Ignacio Vera
>            Assignee: Karl Wright
> Hi,
> Working with geosahpes and trying to resolve spatial relationships between them I came accross a big limitation when trying to solve the relationship between two geopolygons. This object does not expose the internal structure. In particular at some point, it is necessary to check if one polygon intersects the edges of the other polygon which currently is not possible as edges are not exposed.
> To be able to perform such operation it can be several options. The ones I can think of are:
> 1) Expose the edges of the polygon ( and probably the notable points for the edges) adding getters in the GeoPolygon interface. Easy to implement and leave users the responsability of coding the spatial relationship.
> 2) Extends GeoPolygon interface to extends geoarea and leave the object make the spatial relationship.
> 3) Extends GeoShape  interface so all shapes can infer the spatial relationship with other GeoShapes.
> I might be bias as my interest is in 2d Shapes in the unit sphere and there might be some cases which what I propose cannot be implemented or are againts the aim of the library.
> What do you think?
> Cheers,
> Ignacio

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]