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 GrantIngersoll.
http://wiki.apache.org/solr/SpatialSearch?action=diff&rev1=25&rev2=26

The Trie* fields are perfect for representing lat/lon in two distinct fields. Additionally,
as of https://issues.apache.org/jira/browse/SOLR1131, there is now a !PointType that supports
transparently representing a point in ndimensional space in a rectangular coordinate system.
Thus, the !PointType might not be appropriate if distance along a sphere or ellipse are desired.
==== Example ====
 {{{<fieldType name="location" class="solr.PointType" dimension="2" subFieldSuffix="_d"/>
... <field name="store" type="location" indexed="true" stored="true"/> }}}
+ {{{
+ <fieldType name="location" class="solr.PointType" dimension="2" subFieldSuffix="_d"/>
+ ...
+ <field name="store" type="location" indexed="true" stored="true"/>
+ }}}
+
=== LatLonType ===
The !LatLonType combines a latitude/longitude point. All input is interpreted as latitude
then longitude. The LatLonType is similar to !PointType, but it does distance calculations
based on Great Circle (haversine) and is only two dimensional (lat/lon).
@@ 84, +89 @@
== Spatial Filter QParser ==
See https://issues.apache.org/jira/browse/SOLR1568.
 ''NOTE: Depending on the !FieldType, different calculations for distance will be applied''.
For instance, the !PointType uses a rectangular coordinate system and uses the Euclidean
distance.
+ ''NOTE: Depending on the !FieldType, different calculations for distance will be applied''.
For instance, the !PointType uses a rectangular coordinate system and uses the Euclidean
distance while !LatLonType uses Haversine by default.
See !SpatialFilterTest for examples of the various points.
