Skip to content
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

Layer name, description and layer other atributes are bypassing SITMUN administrator configuration #55

Open
RicardCots opened this issue Sep 20, 2024 · 0 comments
Assignees
Labels
question Further information is requested

Comments

@RicardCots
Copy link

RicardCots commented Sep 20, 2024

Describe the bug
That's something related with how API SITNA works. Once API SITNA is given a WMS it uses that service to retreive all parameters that is going to need directly form the WMS capabilities (layer name, description, associated WFS, legend URL, Data URL, metadata URL ...). So any change introduced in the SITMUN administrator will not apply.

It may be a Proxy enchancement, but, as I'm not sure, I've registered this as a bug in SITMUN viewer.

To Reproduce
Steps to reproduce the behavior:

  1. Go to SITMUN administator and change the name or description of a layer in the layer tree form and in the tree form.
  2. Open SITMUN viewer containing that layer/tree
  3. See how the name or the description has not changed

Expected behavior
Every change introduced in SITMUN manager, applies in SITMUN viewer.

Screenshots
image

Example:

In the service https://sitmun.diba.cat/wms/INSPIRE/USGOVSERV? the title of the layer as expressed in the capabilities is 'Barcelona Provincial Council utility and governmental services - Administrative and social governmental services'

This is the title that API SITNA is going to us, no matter what is configured in de SITMUN Administrator. See how https://ide.cime.es/stm3/admin this layer is configured in the 'IDE Barcelona - Generic ' tree. See image above

@fjlopez fjlopez added enhancement New feature or request question Further information is requested and removed enhancement New feature or request labels Sep 20, 2024
@fjlopez fjlopez self-assigned this Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants