Skip to content

Loading layers into a tree using the 'Load from service' functionality #227

Closed

Description

@RicardCots

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:

  1. Configure those two WMS services with the respective layers:

https://www.cartociudad.es/wms-inspire/direcciones-ccpp

https://sitmun.diba.cat/wms/INSPIRE/AD

Both layers contain a layer called AD.Address

  1. Try to load from service on a tree of those services. The function will load the first layer that finds.
  2. Check the layer atributes in the layer tree and see the error.

Expected behavior
The function 'Load From layer' sould check not only the layer name but also the service where it belongs.

Screenshots
imagen

Activity

  1. fjlopez commented on Oct 16, 2024

    @fjlopez
    Contributor

    The form has all the information to select only cartographies from the selected service. It is clearly a bug of the administrator.

  2. github-actions commented on Apr 9, 2025

    @github-actions

    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.

  3. github-actions commented on Apr 26, 2025

    @github-actions

    This issue has been automatically closed due to inactivity. If it is still valid, please post a comment.

  4. added theissue type on Apr 27, 2025
  5. fjlopez commented on Apr 27, 2025

    @fjlopez
    Contributor

    Check this bug as it can be related with a model issue.

  6. fjlopez commented on Oct 22, 2026

    @fjlopez
    Contributor

    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.

  7. added
    confirmedReproduced / accepted defect; exempt from stale bot
    and removed on Oct 22, 2026
  8. fjlopez commented on Oct 22, 2026

    @fjlopez
    Contributor

    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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingconfirmedReproduced / accepted defect; exempt from stale bot

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions