Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of volker.mische@gmail.com
 designates 209.85.220.163 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:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=FJ2iVFgAZMKuZ4Pod3kg+m3V60ZEqUZWtUMHr3uL5WdRr8x7nSPSBSEUUhjr50xKIq
         TdtfDlByXY71JCUyXmQGNw4s4MdfT8+4MdhhNJKidKhLm7JyGL2PCHl+43zQ20ffJ2VX
         f7epPxOsGtOOIYAMoUKrBTd4LmD1SS73dAz1Q=
Message-ID: <49C79AB9.8020202@gmail.com>
Date: Mon, 23 Mar 2009 15:20:41 +0100
From: Volker Mische <volker.mische@gmail.com>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: using couchdb for 100GB geodata from openstreetmap
References: <186b32bc0903221439k7bdc1c15vf1a960aa2047d4c1@mail.gmail.com>
 <49C6BC80.4090504@gmail.com>
 <186b32bc0903221545k7f41a2ccl62b55902cf740557@mail.gmail.com>
 <49C6C1B8.9090605@gmail.com>
 <1C3347CF-EBFE-47A1-A2CE-EA5681AD343E@apache.org>
 <49C6C4C2.6080202@gmail.com> <20090323055830.GK31847@translab.its.uci.edu>
In-Reply-To: <20090323055830.GK31847@translab.its.uci.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

James Marca wrote:
> On Mon, Mar 23, 2009 at 12:07:46AM +0100, Volker Mische wrote:
>> Is there a difference between a custom view engine and the approach I
>> try to pursue with GeoCouch? It still comes down to the fact that you
>> need to store the spatial information in some kind of (external) spatial
>> index.
> 
[...]
> 
> The Geo Couch approach, as I understand it (again, forgive any
> ignorance on my part) is an external process that responds to queries,
> right?  So there isn't an index that CouchDB understands, and you
> can't run map/reduce type queries over it.  At least, that's why I
> didn't try to load up GeoCouch.  I was looking for a view engine that
> was a bit more native to the map/reduce aspects of CouchDB.

This is how it works at the moment. The next thing I'll be working on is
_external and view intersection. This means that the external process
returns some results which will be combined with the results of a view.
This way you get (hopefully) the power of CouchDB for attribute queries,
but high speed for the spatial part of the query.

Cheers,
  Volker