On Fri, Mar 27, 2015 at 12:27 AM, Mike Hansen wrote:
> There are a few things which could probably help with performance.
> Each document has only around say 30 polygons. You could do a binary
> search which would help reduce the cost. Additionally, I have a
> distinguished point contained inside
On Thu, Mar 26, 2015 at 9:06 PM, david.w.smi...@gmail.com
wrote:
> The second, (non-easy) part seems like it could be pretty slow:
>
> To determine “the smallest polygon which contains the point” for the
> current matching document, you’d have to iterate over them in
> smallest-to-largest-1 order
Hi Mike,
The second, (non-easy) part seems like it could be pretty slow:
Additionally, I'd like to have access to the
> numerical value of the smallest polygon which contains the point
> (something like makeDistanceValueSource).
To determine “the smallest polygon which contains the point” for t
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
Thanks heaps for the quick reply David...
Computing the distance on the client is not an issue, however I was
wondering as you are already computing the distances, there is any caching
mechanism that I could retrieve the computed values. I looked into
CachedDistanceValueSource class etc, but appar
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
Hi David,
I'm implementing a project using your RecursivePrefixTreeStrategy and it
works fine when I'm only querying
based on the geo field as I can sort and can get the distance from the score
of the results. However I couldn't figure out how to sort and get the
distance when I combine the geoque
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
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
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
On Sun, Jan 1, 2012 at 6:18 AM, Lance Java wrote:
> But I'm a bit worried about this solution since Yonik has pointed out that
> the tier based approach is broken. Yonik, any more info on why this is
> broken? Perhaps a bounding box that works is better than a circle that
> doesn't ;)
Haven't use
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.
I downloaded lucene-spatial-playgro
On Sat, Dec 31, 2011 at 11:52 AM, Lance Java wrote:
> Hi, I am new to Lucene and I am trying to use spatial search.
The old tier-based stuff in Lucene is broken and considered deprecated.
For Lucene, this may currently be your best hope:
http://code.google.com/p/lucene-spatial-playground/
Solr
I am sorry to trouble, problem solved (in fact problem is absent :) ).
Calculated distances saved in ScoreDoc (actually FieldDoc).
2011/3/30 Dmytro Barabash :
> Hi all!
> I need 1) sort search results by distance from some point and 2) show
> these distances for end-user together with other docum
14 matches
Mail list logo
