[
https://issues.apache.org/jira/browse/LUCENE-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137529#comment-16137529
]
David Smiley commented on LUCENE-7936:
--------------------------------------
Hello [~ivera] and [~daddywri]. BTW I'm on travel and on vacation so I'm not
as responsive as I'd like.
It's exciting to see some progress in this area. Having Geo3D shapes be able
to serialize and deserialize themselves using core Java APIs (only) in
particular would be great. This would allow their internal details to be less
exposed. I have a strong preference for not using Lucene APIs here since it
allows 3rd parties to use the jewel that is Spatial3D by itself without having
to bring in Lucene-core. For example perhaps someone is doing pure in-memory
calculations without Lucene in the picture. Any way, speaking of the format...
would this theoretically write 3 doubles per vertex? :-/ Though if we write
lat-lon then there's math to do at read-time.
Additions to the lucene-spatial-extras module -- Geo3D SpatialContext impl,
with BinaryCodec impl seems like a separate issue to me.
> Extend Geoshape interfaces so objects can be copied/serialized
> --------------------------------------------------------------
>
> Key: LUCENE-7936
> URL: https://issues.apache.org/jira/browse/LUCENE-7936
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/spatial3d
> Reporter: Ignacio Vera
> Assignee: Karl Wright
> Attachments: GeoBinaryCodec.patch, LUCENE-7936.patch, Spatial4j.patch
>
>
> Hi [~david.wri...@bksv.com],
> 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 index)
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
