> Your goal is to restrict documents search results to spatial extends
> similar to the syntax which restricts documents based on their
> (creation/modification) date within a given time period.
Yes... That's the immediate goal, which I have already achieved
by using quadTrees and the GeoFilter c
2005/5/2, Guillermo Payet <[EMAIL PROTECTED]>:
> > If you're only searching for any term using *, I'm not sure why you're
> > using Lucene?
>
> Most searches are not as simple, and for those the GeoFilter does
> the trick. I'm just trying to optimize for the few searches for
> all items within an
> If you're only searching for any term using *, I'm not sure why you're
> using Lucene?
Most searches are not as simple, and for those the GeoFilter does
the trick. I'm just trying to optimize for the few searches for
all items within an area.
On Mon, May 02, 2005 at 08:24:07AM -0500, [EMAIL P
I don't really need any geographical scoring. I just need to be able
to show all items within a region. Since a lot of the complexity of
"Query" has to do with scoring, would it be better to just use the
GeoFilter, and to search for *? Are there any performance issues
with this?
You might try
I guess the solution is to forget about using IndexSearcher and
Query at all and to write a simple "GeoSearcher" that opens the
regular index, plus the QuadTree, and uses the same approach I used
in GeoFilter to generate a group of hits. Like this:
GeoQuery geoSearcher = new GeoSearcher("path
A thought
I don't really need any geographical scoring. I just need to be able
to show all items within a region. Since a lot of the complexity of
"Query" has to do with scoring, would it be better to just use the
GeoFilter, and to search for *? Are there any performance issues
with this
