> Placing both lat and long in the same field is good when used internally
The initial filtered range query should be much faster this way. Is it possible to then extract the lat and long out of the geohash for the narrowing portion? On Thu, Sep 18, 2008 at 11:08 AM, patrick o'leary (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632239#action_12632239 > ] > > patrick o'leary commented on SOLR-773: > -------------------------------------- > > Hey guys > > Placing both lat and long in the same field is good when used internally, the > majority of users > of localsolr have separate fields representing lat long, so make sure the > representation > does not effect the original document. > > WKT uses point as the naming convention for single item's and I'd suggest > that rather than just str, it would > also be nice to get to a KML wt format as well. I've done some stuff > integrating in mapping components and > KML goes down real well. > > However be aware as soon as you start supporting WKT, you will be asked for > ERSI support, and poly support, > ray tracing, collision and a lot more fun things :-) > > P > >> 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. > >
