Hi, this looks like an interesting issue.

So you mean that once your JS Service has one query failing then all the requests sent afterward also failed. This looks very strange, every request should use different variables so this should not happen. Still, I would like to know if you can provide the !Javscript code to make me able to reproduce this issue.

I hoep to hear from you.

You will need to go to the LINZ site, register, and generate an API key. You can try these coordinates for testing: -40.374848 175.609335 -40.344985 175.670925 -37.283333 176.25

var coordinate=inputscoordinate?value?; var url = '​https://data.linz.govt.nz/services;key=<ADD_YOUR_API_KEY_HERE>/wfs'; var serviceParam = 'WFS'; var versionParam = '2.0.0'; var requestParam = 'GetFeature?'; var typeNamesParam = 'layer-1153'; var cqlFilterParam = 'CONTAINS(GEOMETRY,POINT('+coordinate+'))';

coastline and islands service var myInputs = { service: serviceParam, version: versionParam, request: requestParam, typeNames: typeNamesParam, CQL_FILTER: cqlFilterParam }; var myRequestResult=ZOO.Request.Get(url, myInputs); var searchResult = myRequestResult.search("gml:id"); var result = ;

if(searchResult > 0) {

result = 1; 'Not in the sea';

} else {

result = 0; 'In the sea or invalid coordinate';

}

return {result: ZOO.SERVICE_SUCCEEDED, outputs: [{name:"Result", value: result}]};

My curl version is 7.35.0

I've updated to curl version 7.54.1. Still having same issue.

Many thanks for providing the information.

I do apologize cause I realized that similar issue has been reported already there ​https://lists.osgeo.org/pipermail/zoo-discuss/2017-May/001622.html. I have now applied the patch to the trunk. So, I would like to invite you to run the following commands:

# Upgrade to the latest source code
svn up
# cleanup everything 
make clean
make && sudo make install

I suppose that this will solve your issue.

Hi.

I downloaded the latest truck and followed your instructions. I am still getting the same error message.

So it means that I have made a mistake in the commit I have made to fix this issue.

I think that this time I will create an account then try your example locally to make sure everything is in working.

Please, stay tune, I will try my best to answer shortly.

Hi. How are you going regarding resolving this bug? I created another issue with trying to chain services together using Zoo API and was also getting the same error message as this bug. Might be similar issue. Cheers.

Hi, thanks a lot for the reminder, I should have tried earlier, sorry I forgot.

After creating an account, I was able to reproduce the same error.

Nevertheless, after changing 2 lines in the source code of the service, I am able to make it successfully running, the modifications of the JavaScript service was at the end, that now looks like this:

First syntax (works):

    outputs["Result"]["value"]=result;
    return {result: ZOO.SERVICE_SUCCEEDED, outputs: outputs};

Second syntax (works):

    return {result: ZOO.SERVICE_SUCCEEDED, outputs: {"Result":{"value": result}}};

So, I suppose that this will solve your issue. Still, I think that it would be better that the ZOO-Kernel give more details about this kind of issue.

I hope this helps.

In case you need arrays, there is also a third optional syntax that can be used which is the following:

    return [ZOO.SERVICE_SUCCEEDED,{"Result":{"value": result}}];

Thanks that helped.

We can now close this issue.