You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Loading layers into a tree using the 'Load from service' functionality #227
Describe the bug
The ‘load from service’ functionality in the layer tree produces an error when in the SITMUN manager there are two layers with the same name ( of the respective service capabilities).
When among the layers that you want to register in the tree there is one that has a name ( of the capabilities) that is repeated among the layers registered in the SITMUN administrator (this happens when two layers of different WMS services have the same name), the administrator gets confused and loads the first of the two that it finds, not the one that corresponds to the service to which it belongs.
To Reproduce
Steps to reproduce the behavior:
Configure those two WMS services with the respective layers:
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.
Validation: Reopened — stale/bot NOT_PLANNED. A later comment asked to check this bug; the import still does not limit the match to the selected service.
Status: OPEN_DEFECT (evidence:confirmed). createNewNodeWithCapabilities picks the first layersList row whose layers.join() equals the capabilities name, with no service id filter.
Validation: DONE (evidence:confirmed). Evidence: createNewNodeWithCapabilities matches the layer name and the selected service id. Spec repeated capabilities name. On dev as merge bb644e17 (#507).
Activity
fjlopez commentedon Oct 16, 2024
The form has all the information to select only cartographies from the selected service. It is clearly a bug of the administrator.
github-actions commentedon Apr 9, 2025
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.
github-actions commentedon Apr 26, 2025
This issue has been automatically closed due to inactivity. If it is still valid, please post a comment.
fjlopez commentedon Apr 27, 2025
Check this bug as it can be related with a model issue.
fjlopez commentedon Oct 22, 2026
Validation: Reopened — stale/bot NOT_PLANNED. A later comment asked to check this bug; the import still does not limit the match to the selected service.
Status: OPEN_DEFECT (evidence:confirmed).
createNewNodeWithCapabilitiespicks the firstlayersListrow whoselayers.join()equals the capabilities name, with no service id filter.fjlopez commentedon Oct 22, 2026
Validation: DONE (evidence:confirmed). Evidence:
createNewNodeWithCapabilitiesmatches the layer name and the selected service id. Specrepeated capabilities name. Ondevas mergebb644e17(#507).