lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7906) Spatial relationship between Geoshapes
Date Thu, 20 Jul 2017 10:22:00 GMT


Karl Wright commented on LUCENE-7906:

Hi [~ivera], I think it is OK to include a reference to the containing GeoPolygon in the constructor
-- but then you'd also need a pointer to the enclosing GeoPolygon in the constructor for GeoCompositePolygon,
because they can be nested (and the factory constructs them in a nested fashion).

I don't think you'll be able to have GeoCompositePolygon simply call the getRelationship()
methods of its child GeoPolygon members.  I think you'll need to compute the intersection
from first principles in GeoCompositePolygon itself, by asking the child polygons if any of
their external edges get intersected etc.  That may require the addition of a new method to
GeoPolygon, but that's what I think is needed.

> Spatial relationship between Geoshapes
> --------------------------------------
>                 Key: LUCENE-7906
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/spatial3d
>            Reporter: Ignacio Vera
>            Assignee: Karl Wright
>         Attachments: LUCENE-7906.patch, LUCENE-7906-test.patch
> 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
> 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:
For additional commands, e-mail:

View raw message