lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Wolanin <>
Subject Re: what data type for geo fields?
Date Thu, 28 Jul 2011 14:24:39 GMT
Thanks for the feedback.  I'll have look more at how geohash works.

Looking at the sample schema more closely, I see:

 <fieldType name="double" class="solr.TrieDoubleField"
precisionStep="0" omitNorms="true" positionIncrementGap="0"/>

So in fact "double" is also Trie, but just with precisionStep 0 in the example.


On Wed, Jul 27, 2011 at 9:57 AM, Yonik Seeley
<> wrote:
> On Wed, Jul 27, 2011 at 9:01 AM, Peter Wolanin <> wrote:
>> Looking at the example schema:
>> the solr.PointType field type uses double (is this just an example
>> field, or used for geo search?)
> While you could possibly use PointType for geo search, it doesn't have
> good support for it (it's more of a general n-dimension point)
> The LatLonType has all the geo support currently.
>>, while the solr.LatLonType field uses
>> tdouble and it's unclear how the geohash is translated into lat/lon
>> values or if the geohash itself might typically be used as a copyfield
>> and use just for matching a query on a geohash?
> There's no geohash used in LatLonType
> It is indexed as a lat and lon under the covers (using the suffix "_d")
>> Is there an advantage in terms of speed to using Trie fields for
>> solr.LatLonType?
> Currently only for explicit range queries... like point:[10,10 TO 20,20]
>>  I would assume so, e.g. for bbox operations.
> It's a bit of an implementation detail, but bbox doesn't currently use
> range queries.
> -Yonik

Peter M. Wolanin, Ph.D.      : Momentum Specialist,  Acquia. Inc. : 978-296-5247

"Get a free, hosted Drupal 7 site:"

View raw message