Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of volker.mische@gmail.com
 designates 72.14.220.155 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=puU52oMxCke4yV2e1BncSwlW4NZQkHBe5SfoxYiJH1XjWBIkb50iydtAoN7GZeh5FG
         Tqc7l0Ti8mawAVPJ4E7oVo/wlh7W7YcWHbEqbXC2hPnCwMxOdnW8JiSc0FHNKp3uvs7j
         Mbmk+F+cD58pvNOifnmWUr+EoQzIY7astpSNs=
Message-ID: <4A358200.6050409@gmail.com>
Date: Mon, 15 Jun 2009 01:04:32 +0200
From: Volker Mische <volker.mische@gmail.com>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: Tim Burgess <timburgess@mac.com>
CC: user@couchdb.apache.org
Subject: Re: Retrieving documents that have a latitude and longitude
 intersection
References: <2C1A5D65-F929-42B8-93CE-A9BB68C8D1DA@mac.com>
 <8508f1c80906141226i2be52f9dt2556c3c1a3d30e15@mail.gmail.com>
 <e282921e0906141334p3ca5b952t3dcd07cdd93007ba@mail.gmail.com>
 <F7141308-72BA-4D12-A15C-F448905A7E6A@mac.com>
In-Reply-To: <F7141308-72BA-4D12-A15C-F448905A7E6A@mac.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

GeoCouch 0.0.1 doesn't solve your problem, only the current code base I
have does. I'll to put some basic documentation together asap, and drop
you a mail with these instructions (off-list).

Cheers,
  Volker

Tim Burgess wrote:
>>>
>>> I suspect I may be misunderstanding what you are trying to do.  If you
>>> want to query for keys from the above view such that: a < doc.lat < b
>>> and x < doc.lng < y, then I think you can do just that:
>>>
>>> startkey = [a, x]
>>> endkey = [b, y]
>>>
> 
> Thanks guys. Yes, using arrays clearly wasn't doing the job after a little
> bit of experimentation - I thought there might have been some 'trick' I was
> missing.
> 
> Volker, if you could point me to your code I would like to try it out. This
> is a 'must have' thing for me as without it, it's pretty much impossible to
> use couchdb for my app. Yes, I could do two queries from the browser but
> paying for unwanted data across the wire and putting extra load on the
> browser is not a solution for me.
> 
> Bounding box is all I need and I could scrape by without anything else
> for the time being so I'd be happy to try GeoCouch. The link to Paul Davis'
> external2 couchdb branch from the link you provided
> goes nowhere on github by the way.
> 
> Cheers, Tim
> 
> 
> 
>> This will also bring back rows with eg the key [b, w] which is outside
>> the wanted range.
>>
>> The simple answer is to have two maps: one by lat and one by long, and
>> query them both, intersecting to find the rows in both queries (or
>> more simply to just query for a longitude range and filter the results
>> by lattitude.) This is not very efficient and hence there are
>> dedicated strategies for geo indexing.
>>
>> GeoCouch is probably the best solution, or you could do the work to
>> integrate another geographic indexer. Adding alternate indexers to
>> CouchDB is about as simple as can be, so don't be put off by the idea.
>>
>>> Is that what you want?
>>>
>>>
>>> + seth
>>>
>>
>>
>>
>> -- 
>> Chris Anderson
>> http://jchrisa.net
>> http://couch.io
> 
> Tim Burgess
> timburgess@mac.com <mailto:timburgess@mac.com>
> 
> Kyoto Podcast - Glimpses of Japan
> www.kyotopodcast.jp <http://www.kyotopodcast.jp>
> 
> 
>