Apache Solr Reference Guide Covering Apache Solr 6.0

maxDistErr
worldBounds
Defines the highest level of detail required for indexed data. If left blank, the default is
one meter – just a bit less than 0.000009 degrees. This setting is used internally to
compute an appropriate maxLevels (see below).
Defines the valid numerical ranges for x and y, in the format of ENVELOPE(minX,
maxX, maxY, minY) . If geo="true" , the standard lat-lon world boundaries are
assumed. If geo=false, you should define your boundaries.
distCalculator Defines the distance calculation algorithm. If geo=true, "haversine" is the default. If
geo=false, "cartesian" will be the default. Other possible values are "lawOfCosines",
"vincentySphere" and "cartesian^2".
prefixTree
maxLevels
Defines the spatial grid implementation. Since a PrefixTree (such as
RecursivePrefixTree) maps the world as a grid, each grid cell is decomposed to
another set of grid cells at the next level. If geo=true then the default prefix tree is " g
eohash", otherwise it's " quad". Geohash has 32 children at each level, quad has 4.
Geohash can only be used for geo=true as it's strictly geospatial. A third choice is " p
ackedQuad", which is generally more efficient than plain "quad", provided there are
many levels -- perhaps 20 or more.
Sets the maximum grid depth for indexed data. Instead, it's usually more intuitive to
compute an appropriate maxLevels by specifying maxDistErr .
And there are others: normWrapLongitude, datelineRule, validationRule, autoIndex,
allowMulti
Overlap, precisionModel. For further info, see the note about spatialContextFactory implementations
referenced above, especially the link to the JTS based one.
Once the field type has been defined, define a field that uses it.
Beyond this reference guide, there are some details that remain at the Solr Wiki at http://wiki.apache.org/s
olr/SolrAdaptersForLuceneSpatial4
RptWithGeometrySpatialField
The RptWithGeometrySpatialField field type is a derivative of SpatialRecursivePrefixTreeFieldT
ype that also stores the original geometry in Lucene DocValues, which it uses to achieve accurate search. It can
also be used for indexed point fields. The Intersects predicate (the default) is particularly fast, since many
search results can be returned as an accurate hit without requiring a geometry check. This field type is
configured just like RPT is.
An optional in-memory cache can be defined in solrconfig.xml, which should be done when the data tends to
have shapes with many vertices. Assuming you name your field "geom", you can configure an optional
cache in solrconfig.xml by adding the following – notice the suffix of the cache name:
Apache Solr Reference Guide 6.0
375