[LUCENE-4388] ShapeMatcher and ShapeValues

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: modules/spatial
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: David Smiley
• Created: 14/Sep/12 15:10
• Updated: 28/Aug/22 13:27

Description

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>.