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. prefixTreeĭefines the spatial grid implementation. Other possible values are lawOfCosines, vincentySphere and cartesian^2. If geo=false, cartesian will be the default. distCalculatorĭefines the distance calculation algorithm. If geo=false, you should define your boundaries. If geo='true', the standard lat-lon world boundaries are assumed. worldBoundsĭefines the valid numerical ranges for x and y, in the format of ENVELOPE(minX, maxX, maxY, minY). This setting is used internally to compute an appropriate maxLevels (see below). If left blank, the default is one meter – just a bit less than 0.000009 degrees. Spring Data for Apache Solr DATASOLR-462 Add pt and sfield parameter to geodist function with simpleQuery. SEVERE: .SolrException: can not sort on unindexed field: geodist() lat, long distance geodist (). distErrPct defaults to 0.15 for that field.ĭefines the highest level of detail required for indexed data. However, it doesn’t affect distances embedded in WKT strings, (e.g., BUFFER(POINT(200 10),0.2)), which are still in degrees.įor 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. It is applied to nearly all distance measurements involving the field: maxDistErr, distErr, d, geodist and the score when score is distance, area, or area2d. This can be degrees, kilometers or miles. This is used to specify the units for distance measurements used throughout the use of this field. If a given shape is parseable as 'lat,lon' or 'x y' then that is always supported. Spatial4j governs this feature and supports other formats. Defaults to WKT but GeoJSON is another popular format. formatĭefines the shape syntax/format to be used. If false, the coordinates will be generic X & Y on a 2D plane using Euclidean/Cartesian geometry.

If true, the default, latitude and longitude coordinates will be used and the mathematical model will generally be a sphere. The default blank value does not support polygons. There are two built-in aliases for known implementations: Geo3D and JTS.

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. What I get is: - Score : 1.0 Doc : Document stored, indexed, tokenized, omitNorms, indexOptions = DOCS_ONLY > - Score : 1.0 Doc : Document stored, indexed, tokenized, omitNorms, indexOptions = DOCS_ONLY stored, indexed, tokenized, omitNorms, indexOptions = DOCS_ONLY > - Score : 1.This should be solr.SpatialRecursivePrefixTreeFieldType. Make multivalued field scoring aware of field values count with Lucene That's why the two documents with two David occurences are on top and with the same score, despite of their different lengths, and the shorter document with just one match is the last one with the lowest score. LTR plugin with geodist() Id be interested to see if anyones successfully got the LTR plugin working using geodist() as one of the input features For me it doesnt seem to work because I cant find a way of accessing geodist() as a field, since its calculated at query time but not stored. As you can see now the termFreq wins and the fieldNorm is not taken into account at all.

Geodist solr