[
https://issues.apache.org/jira/browse/LUCENE-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135460#comment-16135460
]
Karl Wright commented on LUCENE-7936:
-------------------------------------
{quote}
This class is used to generate docValues which at the same time is used by the
SerializedDVStrategy to check the relationship between indexed and query
shapes. If we achieve this, we can pass through the interfaces the Geo3dShapes
and use it with Lucene (I have already done it with very promising results).
{quote}
[~ivera], the conversion to docvalues actually should live in the package
org.apache.lucene.spatial3d. There are classes in there already that implement
doc values fields, distance comparators, and DV logic. If these are
insufficient for what you're trying to do, please let me know why.
As for the polygon pixelation, there are two considerations. First, this
statement is not correct:
{quote}
The library requires polygons to be convex therefore for concave polygons I
need to break them into the equivalent convex ones, which is what the
GeoPolygonFactory actually does.
{quote}
GeoPolygonFactory generates concave polygons in the case where that's the best
representation. It either generates ONE concave polygon or potentially
MULTIPLE convex polygons. So perhaps you are going to need to do something
different anyway?
In fact, I'm not certain that it's always possible to tile a concave polygon
with convex polygons without adding vertices by interpolation.
> 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: LUCENE-7936.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
