D4Science Infrastructure

I tried to save the algorithm and republish it but this did not solve the issue.

@emmanuel.blondel@fao.org, I just ran the script in the online instance of RStudio, and it returns an error regarding the 'ReadWFS' function (below). Do you think it could be an issue with the algorithm not properly loading the RFigisGeo package? Thank you

Reading WFS http://geoserver-dev.d4science-ii.research-infrastructures.eu/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=W_mpa:eez&cql_filter=mrgid_eez = '5677'
Error in fetchFeatures(baseUrl = "http://geoserver-dev.d4science-ii.research-infrastructures.eu/geoserver/ows?", :
could not find function "readWFS"
Timing stopped at: 0.004 0 0.002

if(class(selected_area) != "SpatialPolygonsDataFrame" || nrow(slot(selected_area,"data")) == 0){

• stop(sprintf("Error with selection of %s '%s'", areaType, areaId))
• } Error: Error with selection of EEZ '5677'

@levi.westerveld@gmail.com I've reported this in #7323 for which i suspect the RFigisGeo package was not re-installed correctly by the automate package installation job. I've added you as watcher in this ticket.

I just ran it again (I saw this ticket was set to 100% and Feedback) but the issue remains on DataMiner.

The computation bfccc604-7a53-4e47-87b8-6814660d14e8 of Mpa Intersect V2 has failed.
java.lang.RuntimeException: Logs of the script can be found at http://data.d4science.org/cHBvVmMyQXdZaGRVQ0dJbWozM2phMG1NUkc2dUF1R0tHbWJQNStIS0N6Yz0-VLT

Thank you for the quick help.

Hi Levi, the issue is the one reported by Emmanuel, this ticket will be automatically closed when the parent ticket will be solved. Sorry for the misunderstanding.

I understand. Thanks for the update.

Just FYI, I was able to run the algorithm through the VRE an hour ago on the French EEZ and it worked. I tried again and it seems to not work again... Levi

I've executed right now the algorithm successfully. The problem is still there for you? Could you re-try please?

Hi. I ran a few tests and it seems to be working. I think we can close the ticket. Thanks for the immediate attention. I think we had a similar problem before though... Any precautions we could take to make the service more reliable on our side? It's a bit worrying to see the algorithm failing, especially thinking forward when we will advertise this service for external usage.