Re: Equivalent LatLongDistanceFilter in Lucene 4.4 API

Hi James, The spatial module in v4 is completely different than the one in v3. It would be good for you to review the new API rather then looking for a 1-1 equivalent to a class that existed in v3. Take a look at the top level javadocs for the spatial module, and in particular look at SpatialExa

Re: Spatial indexing: IndexOutOfBounds in QuadPrefixTree

Just finished: http://wiki.apache.org/solr/SpatialForTimeDurations - Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Spatial-indexing-IndexOutOfBounds-in-QuadPrefixTree-tp4040511p4045998.html Se

Re: Spatial indexing: IndexOutOfBounds in QuadPrefixTree

Paul, FYI: http://lucene.472066.n3.nabble.com/InvalidShapeException-when-using-SpatialRecursivePrefixTreeFieldType-with-custom-worldBounds-tt4045351.html I suggested to file a bug report. ~ David Paul Alexandrow wrote > Hi List, > > I've encountered this problem using Solr (4.1.0), but as fa

Re: DiskDocValues vs Lucene42Codec

Thanks Robert; that's very helpful. - Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/DiskDocValues-vs-Lucene42Codec-tp4044061p4045935.html Sent from the Lucene - Java Users mailing list archive

DiskDocValues vs Lucene42Codec

DiskDocValues is a codec (or part of a codec, apparenlty) for accessing the DocValues from disk, with minimal RAM usage for things like offsets. Lucene42Codec alternatively puts all of DocValues in RAM. Is the actual disk resident data format the same between them? And how do you pick & choose t

Re: question re lucene spatial toolkit aka LSP aka spatial4j

I responded to the solr-user thread. - Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/question-re-lucene-spatial-toolkit-aka-LSP-aka-spatial4j-tp3999889p425.html Sent from the Lucene - Java

Re: Spatial Search

Amir, CachedDistanceValueSource is indeed poorly named; I need to get renaming it on the TODO list; I've identified this before. Calculating the distance is computationally cheap enough to calculate for the X number of results (top-20-ish) you are returning in your search results to not bother tr

Re: Spatial Search

Amir, The geo query's score happens to be the distance but I don't expect that to remain so. I plan for it to be 1/distance which is a better relevancy value -- a "score" is supposed to be about relevancy after all. If you want to get the distance for a search result, I recommend calculating it

Re: Spatial Search

I have a couple comments on your code after briefly looking through it. * If you want to work with miles, initialize SimpleSpatialContext with DistanceUnits.MILES. I see you chose KM but your leading statistics are in miles. Perhaps that is the reason for the discrepency in your numbers. * You a

Re: Spatial Search

Lance Java wrote > > Hi, I'm trying to keep this a lucene only project rather than bring in > solr > which, as I understand, needs to run in a separate web container. I'd like > to use a single webapp for my project as I'm unsure of the implications of > hosting such a project on the cloud. > B

Re: Spatial Search

Hi Lance. LSP has the concept of a "SpatialStrategy" which encompasses all the algorithms and what-not to index and query, filter, and sort shapes. The TwoDoublesStrategy aims to basically work like Solr's LatLonType, however it isn't completely implemented as you found out -- it doesn't do circl