lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7936) Extend Geoshape interfaces so objects can be copied/serialized
Date Tue, 22 Aug 2017 23:16:01 GMT


Karl Wright commented on LUCENE-7936:

[~dsmiley], I don't think we'd thought much about the representation; more interested right
now in how we do it than the exact details.  We'd clearly want a minimal representation for
a GeoPoint and I think that would be a lat and a lon and we'd take the hit on deserialization.

[~ivera], I think David's suggestion is a good one: maybe create a new ticket to handle the
spatial-extras contributions?  The codec should become much simpler and I'd hope that David's
interfaces could be extended to allow spatial4j objects to be similarly encoded/decoded. 
Once again, I'll be looking at the geo3d serialization design later in the week when I actually
have time -- or, [~ivera], if you have time before then you could propose an implementation.
 But this is separate entirely from the TileIterator stuff.  We should do one thing at a time
I think.

> Extend Geoshape interfaces so objects can be copied/serialized
> --------------------------------------------------------------
>                 Key: LUCENE-7936
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/spatial3d
>            Reporter: Ignacio Vera
>            Assignee: Karl Wright
>         Attachments: GeoBinaryCodec.patch, LUCENE-7936.patch, Spatial4j.patch
> Hi [],
> I would like to propose to extends the GeoShape interfaces to be able to copy/serialized
the objects. The current status and  propose change is as following:
> GeoPoint: It can be serialized by using x, y, z
> GeoCircle:  It can be serialized by using getCenter() and getRadius() and getPlanetModel()
> GeoCompositeShape: It can be serialized by accesing shapes using size() and GetShape(int
> GeoPath: add methods to the interface getPoints() and getCutoffAngle()
> GeoPolygon: This is the most complicated one as we have different types:
>    1.- GeoCompositePolygon is just a composite
>    2.- GeoConcavePolygon and GeoConvexPolygon: Create a new interface for those polygons
which exposes the points, holes, internaledges and concavity/convexity
>    3.- GeoComplexPolygons: Do nothing, they are too complex to be serialize??
> I am intersested in accesing the discreatization of the polygons into convex and concave
ones for other reasons as well. I think this should be expose as they end result can be used
for other use cases.
> Cheers,
> I.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message