lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "SpatialSearch" by DavidSmiley
Date Mon, 19 Mar 2012 05:41:07 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "SpatialSearch" page has been changed by DavidSmiley:
http://wiki.apache.org/solr/SpatialSearch?action=diff&rev1=81&rev2=82

Comment:
Added SOLR-2155 (geohash) section.

  = Advanced Spatial Search =
  Solr also supports other spatial capabilities beyond just latitude and longitude. For example,
a !PointType can be used to represent a point in an n-dimensional space. This can be useful,
for instance, for searching in CAD drawings or blueprints. Solr also supports other distance
measures. See the FunctionQuery page for more information and look for hsin, ghhsin and others.
  
+ == SOLR-2155 ==
+ [[https://issues.apache.org/jira/browse/SOLR-2155|SOLR-2155]] Refers to an issue in JIRA
that uses spatial search techniques based on edge n-gram'ed geohashes with a PrefixTree/Trie
search algorithm. '''If you are using Solr 3x and want a multi-valued geospatial field (both
filter & sort) then this is for you.''' It has been benchmarked showing great performance
too.
+ 
+ As of September 2011, SOLR-2155 was ported to 3x and was made available as a drop-in add-on
to Solr without any patching. Go to the issue and download the "Solr2155-1.0.3-project.zip"
attachment (or newer version if available). Read the README.txt file.  You do need to build
the code, which is as simple as running "mvn install" which generates a jar file: target/Solr2155-1.0.3.jar.
 Put that on Solr's classpath so it's available, similar to how other Solr contrib jars are
installed.
+ 
  == LatLonType ==
  The !LatLonType is the current default spatial field.  Values for this type are of the form
{{{latitude,longitude}}}, although behind the scenes, the latitude and longitude are indexed
as separate numbers. Fields using !LatLonType must be single valued (i.e. multiValued="false").
 This field type does distance calculations based on Great Circle (haversine).
  

Mime
View raw message