On Sep 30, 2011, at 4:14 AM, Alessandro Benedetti wrote:
> Ok this is a good news !
> I will integrate the jar and test the feature :)
> Only one question regarding the indexing process in solrj.
> We could index the location data in format : lat,lon in the geohash field?
> Or we must encode lan &
Ok this is a good news !
I will integrate the jar and test the feature :)
Only one question regarding the indexing process in solrj.
We could index the location data in format : lat,lon in the geohash field?
Or we must encode lan & lon in the geohash string and then index the encoded
string?
Thank
On Sep 29, 2011, at 5:10 PM, Alessandro Benedetti wrote:
> Sorry David, probably I misunderstood your reply, what do you mean?
>
> I'm using Lucid Work Enterprise 1.8, and, as I know , it includes geohashes
> patch.
Solr 3x, trunk, and I suspect Lucid Works Enterprise 2.0 (doubtful 1.8))
suppo
Sorry David, probably I misunderstood your reply, what do you mean?
I'm using Lucid Work Enterprise 1.8, and, as I know , it includes geohashes
patch.
I have to index a multivalued location field and I have to make location
queries on it!
So I figured to use the geohash type ...
Any hint about ind
Hi Alessandro.
I can't think of any good reason anyone would use the geohash field type that
is a part of Solr today. If you are shocked I would say that, keep in mind the
work I've done with geohashes is an extension of what's in Solr, it's not
what's in Solr today. Recently I ported SOLR-2155
Hi all,
I have already read the topics in the mailing list that are regarding
spatial search, but I haven't found an answer ...
I have to index a multivalued field of type : "geohash" via solrj.
Now I build a string with the lat and lon comma separated ( like
54.569468,67.58494 ) and index it in t
