[ZOO-Discuss] ZOO Execute requests
Gérald Fenoy
gerald.fenoy at geolabs.fr
Mon May 17 01:34:07 PDT 2010
Daisuke-san,
I really thank you for this effort as we heard a lot about the needs for this kind of virtual machine image.
About the error messages you get in your apache error log, it is only a debug message displaying what was passed by ZOO Kernel to the Python module function as output value. Indeed in the released ZOO Kernel it now fill the output dictionary with the default output defined in the zcfg file if none was specified when the service was requested. This way you can overwrite the "value" field only from your Python module rather than creating a full output dictionary. I think it is better to handle things this way.
A note here about default values, in the released ZOO Kernel we also fill all the default inputs parameters even if they are optional. I would like to get feedbacks for this specific implementation. Indeed, in some process it makes sense to handle things this way, the Buffer service for instance get then the default value for BufferDistance input but I wonder if it makes sense for each processes. Indeed, some process, like the ones shown by Soeren using GRASS a backend, seems to define some parameters with default value but don't want to get them filled to ensure that they wasn't passed to the service. In fact in this case they are really optional. In the Buffer service, even if the BufferDistance is optional, then in the code of the Buffer function we have to use a default value. So I thought that it can be a good thing to get the default value directly filled by ZOO Kernel, this way we don't have to think about the default value (as they are settled in different files, the defalut value was set in the zcfg and the default value should also be used in the code of the service function). So if the code evolve the zcfg have to be corrected to follow the new implementation.
So maybe we can think about adding a field specifying if the value was get from the request or automatically filled by the ZOO Kernel before running the process. This way even if optional values was passed, the service developer can know if the value have to be used or not.
Hope to get your ideas on this.
Best regards,
Le 17 mai 2010 à 02:40, Daisuke YOSHIDA a écrit :
> Gerald-san and Luca,
>
> ZOO Execute request worked under my Mandriva2010.0 64bit and Ubuntu
> 10.4 32bit machines after adding PYTHONPATH in [env].
>
> But there are still error messages as below,
> [Mon May 17 09:22:39 2010] [error] [client 127.0.0.1] MAP => [Result]
> [Mon May 17 09:22:39 2010] [error] [client 127.0.0.1] [DataType] => [string]
> [Mon May 17 09:22:39 2010] [error] [client 127.0.0.1] [UOM] => [meter]
> [Mon May 17 09:22:39 2010] [error] [client 127.0.0.1] [value] => [NULL]
>
> But it is working at least.
>
> I created an OVF virtual image (2.7GB) and linked the following page.
> http://www.zoo-project.org/trac/wiki/ZooDocumentation/ZOOKernel/DebianLike_installation
>
> It can be imported to VirtualBox or other virtual applications.
> # I use VMware fusion.
> Using virtual machine is good for beginners and workshop.
>
> Best regards,
>
> Daisuke Yoshida
>
> On Sun, May 16, 2010 at 5:21 PM, Luca Delucchi <lucadeluge at gmail.com> wrote:
>> 2010/5/12 James Sewell <James.Sewell at ardec.com.au>:
>>> Hey Nick,
>>> Thanks for the reply. I am working on CentOS. I used the cgic from the
>>> thirds directory (as mentioned DescribeProcess and GetCapabilities work fine
>>> via HTTP).
>>
>> if you using python process maybe the problem is in your main.cfg,
>> where you can try to add
>>
>> [env]
>> PYTHONPATH=<YOUR_PYTHONPATH>
>>
>>> Cheers,
>>> James Sewell
>>
>> cheers
>> Luca
>> _______________________________________________
>> Zoo-discuss mailing list
>> Zoo-discuss at gisws.media.osaka-cu.ac.jp
>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>
> _______________________________________________
> Zoo-discuss mailing list
> Zoo-discuss at gisws.media.osaka-cu.ac.jp
> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
Gérald Fenoy
gerald.fenoy at geolabs.fr
GEOLABS
Siège social :
Futur Building I
1280, avenue des Platanes
34970 Lattes
Tél. fixe : 04 67 53 67 37
Tél. portable : 06 70 08 25 39
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/zoo-discuss/attachments/20100517/40708d91/attachment.html>
More information about the Zoo-discuss
mailing list