incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Volker Mische <volker.mis...@gmail.com>
Subject Re: Error in Spatial-Index-Creation ?
Date Mon, 23 Jul 2012 10:24:37 GMT
Hi Markus,

yes 1.3.x support is of course planned. There's also refuge_spatial [1]
which is basically GeoCouch with some stuff added and based on the
CouchDB 1.3.x code base. Though I don't know if it's compatible with
Apache CouchDB 1.3.x or only rcouch [2]. I'm sure Benoit Chesneau can
tell more about it :)

You can try polygon queries now using the couchdbgeom branch I've pushed
to my Github repository [3]. It works with CouchDB 1.2.x.

[1] https://github.com/refuge/refuge_spatial
[2] https://github.com/refuge/rcouch
[3] https://github.com/vmx/geocouch/tree/couchdbgeom

Cheers,
  Volker

On 07/23/2012 12:06 PM, ScubbX wrote:
> Thank you for this information!
> I guess geocouch will work with coucdb 1.3.x at some point in time?
> (looking foreward to polygon-queries)
> 
> About the error I described: After creating a new design-document to
> store my views and stopping using double-quotes but single-quotes in my
> views, they work again. :-)
> 
> 
> Am 2012-07-23 11:49, schrieb Volker Mische:
>> On 07/21/2012 04:40 PM, ScubbX wrote:
>>> Hello!
>>>
>>> I get an error-return when executing a spatial view for the first time.
>>> Everything goes fine when using non-spatial views. The index-generation
>>> is aborting and the following error is displayed:
>>>
>>> |{"error":"{function_clause,
>>>   [{couch_spatial_updater,process_result,
>>>   [[<<\"railway\">>||,[<<\"8091320\">>,<<\"node\">>,<<\"halt\">>]]]},
>>>   {couch_spatial_updater,'-process_results/1-fun-0-'||,2},
>>>   {lists,foldl,3},
>>>   {lists,map,2},
>>>   {lists,map,2},
>>>   {lists,map,2},
>>>   {couch_spatial_updater||,spatial_docs,2},
>>>  
>>> {couch_spatial_updater,spatial_compute,2}]}","reason":"{gen_server,call,[<0.18574||.0>,{request_group,445226},infinity]}"}|
>>>
>>>
>>>
>>> This happens with different CouchDB installations (Ubuntu 12.04, a
>>> self-compiled 1.2.0 and an older CouchBase in a VirtualMachine) on large
>>> databases (in this case 440.000 entries, the error happens after about
>>> processing 18.000). The view worked fine when executed on a database
>>> with only about 2.300 entries.
>>>
>>> The spatial view looks like this (it has become a bit bloated because of
>>> debugging):
>>>
>>> function(doc) {
>>>      if(doc.geometry && doc.properties) {
>>>          if(doc.properties.tags && doc.geometry.coordinates){
>>>              if(doc.properties.tags.amenity) {
>>>                  if(doc.properties.tags.amenity == "bicycle_parking") {
>>>                      emit(doc.geometry, 1);
>>> }}}}}
>>>
>>> I tried other spatial-views but they produce the same error. It seems to
>>> me like an internal problem, or could there be something wrong with the
>>> data? The document that produced the error is this:
>>>
>>> {"total_rows":445220,"offset":413135,"rows":[
>>> {"id":"node8091320",
>>> "key":"node8091320",
>>> "value":{
>>>      "_id":"node8091320",
>>>      "_rev":"1-2eb0febff1242a1aa7514991a03a5e05",
>>>      "geometry":{
>>>          "type":"Point",
>>>          "coordinates":[16.3148334,48.2232677]},
>>>      "type":"Feature",
>>>      "properties":{
>>>          "changeset":9169859,
>>>              "uid":129531,
>>>              "tags":{
>>>                  "railway":"halt",
>>>                  "uic_ref":"8100271",
>>>                  "name":"Hernals"
>>>              },
>>>              "timestamp":"2011-08-30T18:27:09Z",
>>>              "version":28,
>>>              "user":"almich"
>>>          }
>>>      }
>>> }
>>> ]}
>>>
>>> I hope you can see something wrong her and would appreciate your help or
>>> comment.
>>>
>>> Greetings,
>>> Markus
>>>
>>> PS: The installations of the master-branch of CouchDB is going fine, but
>>> the master of GeoCouch does not compile for me.
>>>
>> Hi Markus,
>>
>> your "PS" are the important bits. Currently GeoCouch doesn't work with
>> the master branch of CouchDB (which will become 1.3.x). You have to use
>> the 1.2.x branch (or the 1.2.0 release). In order to get GeoCouch to
>> work with that, you also have to use the correct branch of GeoCouch,
>> which would be the "couchdb1.2.x" branch.
>>
>> Cheers,
>>    Volker
> 


Mime
View raw message