-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geoprocessing Tools plugin #9263
Comments
* #9263 Geo Processing Tools * wip * wip * #9263 implementing geoprocessing tools * fix build * fix doc * fix review changes requested * Finalized review and fixed locales * fix it locales * fix test * fix tests * fix after review * fix with toWKT * fix call to toWkt * clear console.error * changes after latest review * refactor after latest changes * changes to the wfslayers selector * fixed tests * little fix * fix lint and epics * fix test * fix messages * Adding pagination to the select features combobox * fix toggle highlight on close and also fix bug with ft info zoom to * Update web/client/selectors/layers.js * Update web/client/selectors/layers.js * Update web/client/actions/additionallayers.js * Apply suggestions from code review * Apply suggestions from code review --------- Co-authored-by: Lorenzo Natali <[email protected]>
It's correct to show the highlighted layers on reopening, |
Once the new layer has been created from any geoprocessing operation, this layer:
|
@SESMAPS thank for getting in touch with us:
I confirm, not yet. It could be an interesting enhancement.
It is possible indeed but from 2023.02.02
No, MS doesn't provide any capability at the moment to publish new layers from scratch. Editing capabilities are anyway possible through the attribute table through WFS-T but not for vector layers created by the geoprocessing tool client side at the moment. For further exchanges on this topic I can suggest you to use the mailing list. You can find links to subscribe here. |
Description
The plugin can be embedded into the main MapStore project.
Based on the requirements, it is intended that only the following WPSs must be maintained:
We also understand that, for both layer selections, a feature from one of the layers present in map need to be selected for both the WPS. This means:
The result is, in both cases, a new vector client side layer added in TOC that can be saved within the map.
It will be also necessary to include in the UI all the other possible parameters requested from the above mentioned WPSs along with the possibility to choose the name of the resulting vector layer in TOC.
An extendable WPS tool needs to be implemented for MapStore for these kinds of purposes leveraging the existing support to manage asynchronous requests.
Acceptance criteria
Summarizing the UI & ACs here:
Buffer (WPS geo:buffer):
Intersection (WPS gs:IntersectionFeatureCollection):
General ACs:
Other useful information
more details here https:/geosolutions-it/MapStore-C265/issues/4
The text was updated successfully, but these errors were encountered: