lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7936) Extend Geoshape interfaces so objects can be copied/serialized
Date Fri, 25 Aug 2017 15:49:02 GMT


Steve Rowe commented on LUCENE-7936:

My Jenkins found a couple reproducing failures for RandomBinaryCodecTest:

On branch_7x:

ant test  -Dtestcase=RandomBinaryCodecTest  -Dtests.seed=AA9F2C61D6F622BD -Dtests.slow=true
-Dtests.locale=hr-HR -Dtests.timezone=America/Argentina/La_Rioja -Dtests.asserts=true -Dtests.file.encoding=UTF-8

On master:

ant test  -Dtestcase=RandomBinaryCodecTest  -Dtests.seed=A97EB454B3179214 -Dtests.slow=true
-Dtests.locale=fr-LU -Dtests.timezone=WET -Dtests.asserts=true -Dtests.file.encoding=UTF-8

> 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
>             Fix For: 6.7, master (8.0), 7.1
>         Attachments: GeoBinaryCodec.patch, LUCENE-7936-GeoComplexPolygon.patch, LUCENE-7936.patch,
LUCENE-7936.patch, LUCENE-7936.patch, LUCENE-7936-test.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