| Name |
Description |
| DisjointSpatialFilter |
A Spatial Filter implementing SpatialOperation.IsDisjointTo in terms of a SpatialStrategy's support for SpatialOperation.Intersects. A document is considered disjoint if it has spatial data that does not intersect with the query shape. Another way of looking at this is that it's a way to invert a query shape. @lucene.experimental |
| DistanceStrategyTest |
|
| DistanceStrategyTest.Param |
|
| SpatialArgsTest |
|
| SpatialExample |
This class serves as example code to show how to use the Lucene spatial module. |
| 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?
If a strategy only supports certain shapes at index or query time, then in general it will throw an exception if given an incompatible one. It will not be coerced into compatibility. 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 |
| SpatialTestCase |
A base test class for spatial lucene. It's mostly Lucene generic. |
| SpatialTestCase.SearchResult |
|
| SpatialTestCase.SearchResults |
|
| SpatialTestData |
This class is modelled after SpatialTestQuery. Before Lucene 4.7, this was a bit different in Spatial4n as SampleData & SampleDataReader. |
| SpatialTestQuery |
Helper class to execute queries |
| StrategyTestCase |
|
| TestTestFramework |
|