A third choice is “ packedQuad”, which is generally more efficient than plain 'quad', provided there are many levels - perhaps 20 or more. Geohash can only be used for geo=true as it’s strictly geospatial. Geohash has 32 children at each level, quad has 4. If geo=true then the default prefix tree is “ geohash”, otherwise it’s “ quad”. 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. Other possible values are 'lawOfCosines', 'vincentySphere' and 'cartesian^2'.ĭefines the spatial grid implementation. If geo=false, 'cartesian' will be the default. If geo=false, you should define your boundaries.ĭefines the distance calculation algorithm. If geo='true', the standard lat-lon world boundaries are assumed. This setting is used internally to compute an appropriate maxLevels (see below).ĭefines the valid numerical ranges for x and y, in the format of ENVELOPE(minX, maxX, maxY, minY). If left blank, the default is one meter – just a bit less than 0.000009 degrees. distErrPct defaults to 0.15 for that field.ĭefines the highest level of detail required for indexed data. Note: For RPTWithGeometrySpatialField (see below), there’s always complete accuracy with the serialized geometry and so this doesn’t control accuracy so much as it controls the trade-off of how big the index should be. At query time this can be overridden in the query syntax, such as to 0.0 so as to not approximate the search shape. Bigger distErrPct values will make queries faster but less accurate. However, more precise indexed shapes use more disk space and take longer to index. The closer this number is to zero, the more accurate the shape will be. If a given shape is parseable as 'lat,lon' or 'x y' then that is always supported.ĭistanceUnits replaces the units attribute which is now deprecated and mutually exclusive with this attribute.ĭefines the default precision of non-point shapes (both index & query), as a fraction between 0.0 (fully precise) to 0.5. Spatial4j governs this feature and supports other formats. Defaults to WKT but GeoJSON is another popular format. If false, the coordinates will be generic X & Y on a 2D plane using Euclidean/Cartesian geometry.ĭefines the shape syntax/format to be used. If true, the default, latitude and longitude coordinates will be used and the mathematical model will generally be a sphere. (note: prior to Solr 6, the '4j' part was '' and there used to be no convenience JTS alias) If you require polygon support, set this to JTS – an alias for .jts.JtsSpatialContextFactory otherwise it can be omitted. This is a Java class name to an internal extension point governing support for shape definitions & parsing. Solr requires a field type to parallel these in order to use them. But be aware that the Lucene spatial module includes some other so-called 'spatial strategies' other than RPT, notably TermQueryPT*, BBox, PointVector*, and SerializedDV. This should be solr.SpatialRecursivePrefixTreeFieldType. There are many options for this field type. To use RPT, the field type must be registered and configured in schema.xml. Introduction to Scaling and Distribution.SolrCloud with Legacy Configuration Files.Using ZooKeeper to Manage Configuration Files.Setting Up an External ZooKeeper Ensemble.Authentication and Authorization Plugins.Adding Custom Plugins in SolrCloud Mode.RequestHandlers and SearchComponents in SolrConfig.Schema Factory Definition in SolrConfig.DataDir and DirectoryFactory in SolrConfig.Uploading Structured Data Store Data with the Data Import Handler.Uploading Data with Solr Cell using Apache Tika.Understanding Analyzers, Tokenizers, and Filters.

Working with External Files and Processes.Working with Currencies and Exchange Rates.Overview of Documents, Fields, and Schema Design.Using the Solr Administration User Interface.

Geodist solr