Class SpatialStrategy
The SpatialStrategy encapsulates an approach to indexing and searching based on shapes.
Different implementations will support different features. A strategy should document these common elements:
- Can it index more than one shape per field?
- What types of shapes can be indexed?
- What types of query shapes can be used?
- What types of query operations are supported? This might vary per shape.
- Does it use the FieldCache, or some other type of cache? When?
Note that a SpatialStrategy is not involved with the Lucene stored field values of shapes, which is immaterial to indexing and search.
Thread-safe.
@lucene.experimental
Inheritance
Inherited Members
Assembly: Lucene.Net.Spatial.dll
Syntax
[Serializable]
public abstract class SpatialStrategy
Constructors
Name | Description |
---|---|
SpatialStrategy(SpatialContext, String) | Constructs the spatial strategy with its mandatory arguments. |
Fields
Name | Description |
---|---|
m_ctx |
Properties
Name | Description |
---|---|
FieldName | The name of the field or the prefix of them if there are multiple fields needed internally. |
SpatialContext |
Methods
Name | Description |
---|---|
MakeDistanceValueSource(IPoint) | See MakeDistanceValueSource(IPoint, Double) called with a multiplier of 1.0 (i.e. units of degrees). |
MakeDistanceValueSource(IPoint, Double) | Make a ValueSource returning the distance between the center of the
indexed shape and |
MakeFilter(SpatialArgs) | Make a Filter based principally on SpatialOperation
and IShape from the supplied If a subclasses implements MakeQuery(SpatialArgs) then this method could be simply:
|
MakeQuery(SpatialArgs) | Make a Query based principally on SpatialOperation
and IShape from the supplied
|
MakeRecipDistanceValueSource(IShape) | Returns a ValueSource with values ranging from 1 to 0, depending inversely
on the distance from MakeDistanceValueSource(IPoint).
The formula is |
ToString() |