[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631992#action_12631992
]
Ryan McKinley commented on SOLR-773:
------------------------------------
LocalLucene/Solr are currently designed to do exactly points 1-4.
As for storing lat/lon in a single field... that sounds really interesting.
Currently the local lucene stuff uses two fields and
[NumberUtils.java|http://svn.apache.org/repos/asf/lucene/solr/trunk/src/java/org/apache/solr/util/NumberUtils.java]
to index/store the distance. It does a lot of good work to break various
bounding box levels into tokens and only performs math on the minimum result
set.
We should consider a geohash field type: http://en.wikipedia.org/wiki/Geohash
to store lat/lon in a single string. This has some really interesting features
that are ideal for lucene. In particular, checking if a point is within a
bounding box is simply a lexicographic range query.
Here is a public domain python geohash implementation:
http://mappinghacks.com/code/geohash.py.txt
> Incorporate Local Lucene/Solr
> -----------------------------
>
> Key: SOLR-773
> URL: https://issues.apache.org/jira/browse/SOLR-773
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Priority: Minor
>
> Local Lucene has been donated to the Lucene project. It has some Solr
> components, but we should evaluate how best to incorporate it into Solr.
> See http://lucene.markmail.org/message/orzro22sqdj3wows?q=LocalLucene
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
