GeoProcessing Tool Intersection issue about mapstore2 HOT 7 CLOSED

as agreed with @tdipisa we will harden more the geoprocessingtool adding

• a check that verify that if wpsUrl is not configured or the layer.url is not present it disables the run button by informing the user, this will prevent to run into errors messages that can be avoided with correct configuration
• we can add a default config in the pluginsCfg with "wpsUrl":"https://yourdomain/geoserver/wps"

from mapstore2.

that context was missing a key property as it it the wpsUrl

i have fixed the demo_context cfg of GeoProcessingTool and now it is working

can i close this @tdipisa ?

from mapstore2.

@MV88 I don't think the issue can be closed. I didn't understand which config fix you applied. Can you please better specify it.
In any case it seems the tool now no longer works as before: for each layer I've selected (e.g. for the buffer) I have the following, which leads me to think there is some missconfiguration now:

Can you please review again?

from mapstore2.

yes I misstyped the protocol

this is the cfg added

{
  "cfg": {
    "wpsUrl": "https://gs-stable.geo-solutions.it/geoserver/wps",
    "selectedTool": "buffer",
    "buffer": {
      "quadrantSegments": 200,
      "capStyle": "Round"
    }
  },
  "override": {}
}

try again

from mapstore2.

@MV88 thank you. It is working now. Is there something to fix on the JS documentation for this or something to fix in the plugin default config for contexts? If no, please feel free to close the issue.

from mapstore2.

I think that we could close this issue. the thing is that every time this property is not configured it will cause this issue because

• the source is a generated vector layer
• this needs a geoserver behind

solutions

• we can maybe introduce a default value pointing to out geoservers this would avoid this issue even tough is not ideal.
• otherwise we have to block the run button when this situation occurs

what do you think ?

from mapstore2.

Actually i have found a fix that shows the correct error message, i'll proceed this way instead of changing workflow in the ui
also point 2 makes this fix not working so is better to simply correctly handle the error as proposed here

from mapstore2.