Feature request #4002
Enhancement: Option to display title in layer panel from wfs/wms plugins
Status: | Closed | ||
---|---|---|---|
Priority: | Normal | ||
Assignee: | - | ||
Category: | Web Services clients/WMS | ||
Pull Request or Patch supplied: | No | Resolution: | |
Easy fix?: | No | Copied to github as #: | 13990 |
Description
The wms and wfs add layer plugins now display the name of the layer selected in the layers panel (TOC). It would be great if there is an option to display the layer title instead. Some layer names can be very cryptic and if several layers are loaded, it becomes very hard to distinguish one layer from another. Renaming the layer in situ can be rather tedious.
Incidentally, the layer list in the wfs plugin has columns: Title, Name, Abstract, while the wms plugin has columns in the order:Name, Title, Abstract. It would be most helpful if these could be synchronised.
Thanks
Associated revisions
wms: use titles in layer name (fixes #4002)
History
#1 Updated by Paolo Cavallini almost 13 years ago
- Category set to Web Services clients/WMS
- Pull Request or Patch supplied set to No
#2 Updated by Giovanni Manghi almost 13 years ago
- Target version set to Version 1.7.4
#3 Updated by Giovanni Manghi over 12 years ago
- Target version changed from Version 1.7.4 to Version 2.0.0
#4 Updated by Pirmin Kalberer about 12 years ago
- Target version changed from Version 2.0.0 to Future Release - Nice to have
#5 Updated by Casper Børgesen almost 11 years ago
I'm curious about this issue. Displaying the name tag instead of the title tag for wms/wfs layers seems to me as a simple change to do. But I recon (without having dived into the source) that these two data sources/providers might be the only ones who uses a title to complement their properties. The required change here should it be to extend all providers with a display name / title to solve this issue? Maybe combined with a checkbox in the settings whether to use name or display name for layers. Or is it much more complicated than this?
I don't think I'm qualified to make such a change though. But I would like to understand why a thing this visible to many users remains unsolved?
#6 Updated by Jürgen Fischer almost 11 years ago
- Status changed from Open to Closed
Fixed in changeset 675746c2d7bdba0b7e3f15a3c96b5a5c2709a41f.