lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan McKinley <ryan...@gmail.com>
Subject Re: Spatial package plans
Date Thu, 23 Apr 2009 00:16:16 GMT
Patrick's original version of localluce included geotools -- to make  
it Apache license compatible we took that out and make the distance  
calculations pluggable.

The hardcoded miles part should be changeable -- feel free to post any  
patches and we can make it a better solution.

best
ryan


On Apr 22, 2009, at 6:39 PM, Wouter Heijke wrote:

> The amount of replies and the state of the code make me think making  
> my
> own distance filter using a real GIS solution like geotools is the  
> way to
> go.
> I wonder anyway if GIS code should be in any Lucene package..
>
> Wouter
>
>> Yeah it's hard coded to use miles, 5 years in the US gets to you..
>> But the functionality doesn't change radius is double so you just  
>> need to
>> convert km to miles
>> for the DistanceQueryBuilder and just convert back from miles to km  
>> to
>> display.
>>
>> On Mon, Apr 20, 2009 at 8:14 AM, Wouter Heijke <wheijke@xs4all.nl>  
>> wrote:
>>
>>>
>>> I'm working on local search functionality and am about to use the
>>> spatial
>>> code in contrib.
>>> I managed to have a proof of concept running using
>>> LatLongDistanceFilter.
>>> The only problem I have with this filter is that it is hardcoded  
>>> to use
>>> Miles!
>>>
>>> Basically my question is what are the plans for the spatial code?  
>>> Is it
>>> going to stay the way it is?
>>>
>>> Wouter
>>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message