[
https://issues.apache.org/jira/browse/LUCENE-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-4388:
---------------------------------
Attachment: LUCENE-4388_ShapeValues_and_ShapeMatcher.patch
> ShapeMatcher and ShapeValues
> ----------------------------
>
> Key: LUCENE-4388
> URL: https://issues.apache.org/jira/browse/LUCENE-4388
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/spatial
> Reporter: David Smiley
> Attachments: LUCENE-4388_ShapeValues_and_ShapeMatcher.patch
>
>
> This patch provides two key interfaces: ShapeMatcher and ShapeValues. The
> ShapeMatcher concept is borrowed from [~ryantxu]'s JtsGeoStrategy which has a
> similar GeometryTester. ShapeValues is basically a
> ValueSource/FunctionValues for shapes. This isn't working; I didn't modify
> any existing classes.
> I haven't completely thought this through but a SpatialStrategy might expose
> a makeShapeValues(IndexReader) and/or makeCenterShapeValues(IndexReader) (the
> latter is the center points of indexed data). A generic Distance ValueSource
> could easily be implemented in terms of makeCenterShapeValues(). And a
> strategy could support any query shape simply by implementing
> makeShapeValues().
> I've been thinking about how the API handles strategies supporting indexing
> multiple shapes and I wonder if that could happen simply via a new
> MultiShape<Shape>.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
