[ZOO-Discuss] GIS GRASS ZOO integration

[Soeren Gebbert]

Hello Eugenio,
sorry for the delay.

2010/10/7 Eugenio Realini <eugenio.realini at gmail.com>:
> Hi Soeren, hi Luca,
>
> this is our situation now:
>
> 1) we have re-generated the WPS.1.0.0 python modules with PyXB 1.1.1,
> this solved the problems we had with it

nice.

> 2) we faced the Xerces issue Soeren was talking about, so we
> recompiled GDAL with it and also this was solved

well done.

> 3) launching "python ZOOGrassModuleStarter.py" does not give any error

good to hear.

> 4) launching "r_univar" through ZOO gives us this exception:
>
> <ows:ExceptionText>
> TRACE : invalid literal for int() with base 10: 'NULL'
> TRACE : <type 'exceptions.ValueError'>
> Unable to run your python process properly. Please check the following
> messages : ['  File "/usr/lib/cgi-bin/r_univar.py", line 4, in
> r_univar\n    service.fromMaps("r.univar", inputs, outputs)\n', '
> File "/usr/lib/cgi-bin/ZOO_Project/ZOOGrassModuleStarter.py", line
> 110, in fromMaps\n    self._createInputOutputMaps()\n', '  File
> "/usr/lib/cgi-bin/ZOO_Project/GrassModuleStarter.py", line 214, in
> _createInputOutputMaps\n    self._checkBandNumber()\n', '  File
> "/usr/lib/cgi-bin/ZOO_Project/GrassModuleStarter.py", line 331, in
> _checkBandNumber\n    self.bandNumber = int(self.inputMap[i])\n']
> </ows:ExceptionText>
>
> To my understanding, it does not like getting 'NULL' as
> 'grass_band_number', since it expects an integer.
>
> You can read the contents of the logfile here: http://pastebin.com/pxG1VVaz
>
> This is the link to the r_univar execute request:
> http://131.175.143.108/cgi-bin/zoo_loader.cgi?Service=WPS&Request=Execute&Version=1.0.0&Identifier=r_univar&DataInputs=map=DTM_108.tif
>
> Any idea on how to proceed from here?


try to add:
grass_band_number=1
to your request to specify a band number for processing. It seems that
the ZOOGrassModuleStarter expects an integer value or None as default
value from the zoo_loader, not 'NULL' which is C-specific.

Best regards
Soeren


> Thanks!
> Eugenio
>
>
> 2010/10/4 Luca Delucchi <lucadeluge at gmail.com>:
>> 2010/9/29 Soeren Gebbert <soerengebbert at googlemail.com>:
>>> Hello Eugenio,
>>
>> hi soeren and eugenio
>>
>>>>
>>>> Still not working also with PyXB 1.1.1
>>>
>>> Well this is strange ... .
>>
>> with PyXB 1.1.1 I also have an error but is different from the eugenio one...
>>
>>>>> import WPS_1_0_0.OGC_WPS_1_0_0 as wps
>> Traceback (most recent call last):
>>  File "<stdin>", line 1, in <module>
>>  File "/usr/lib/cgi-bin/WPS_1_0_0/OGC_WPS_1_0_0.py", line 132, in <module>
>>    Namespace.addCategoryObject('typeBinding', u'DataType', DataType)
>>  File "/usr/local/lib/python2.6/dist-packages/pyxb/namespace/__init__.py",
>> line 330, in addCategoryObject
>>    raise pyxb.NamespaceUniquenessError(self, '%s: name %s used for
>> multiple values in %s' % (self, local_name, category))
>> pyxb.exceptions_.NamespaceUniquenessError:
>> http://www.opengis.net/wps/1.0.0: name DataType used for multiple
>> values in typeBinding
>>
>>
>>>
>>>>
>>>> Since the error is in _ows.py, that I've seen it was generated by
>>>> PyXB, could I try to generate it again from scratch?
>>>
>>> Yes you can try to generate the WPS.1.0.0 python modules with PyXB
>>> 1.1.2 by yourself:
>>>
>>> mkdir WPS_1_0_0
>>> cd WPS_1_0_0/
>>> pyxbgen -u http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd -m OGC_WPS_1_0_0
>>> touch __init__.py
>>>
>>> Then replace the WPS_1_0_0 dir with the new one.
>>
>> I tried also this but I have the same problem...
>>
>>
>>> I hope you are able to run it. Please use the latest svn version of
>>> the wps-grass-bridge, i fixed some bugs.
>>>
>>
>> i update my svn to today
>>
>>> Best regards
>>> Soeren
>>>
>>
>> thanks and regard
>> Luca
>>
>