This is a follow-up task that was mentioned in #2074 (where we removed the tag default from all core views).
Now with Views in core and also with admin_views in core, I think that it would make sense to be adding:
- a core tag for all views provided by core
- a custom tag for all views manually added to the site
- a %module name% tag for all views regardless of whether they are core/contrib/custom (we currently have a "Default (module-provided)" indication in the "Storage State" column, which is not very useful, but it would be if the module providing the view was also indicated). If not a tag, this could be a new provided-by property.
As it is now, these tags would have no value, but if we added an instant search filter at the top of the views list (#503), then it would be very useful, because as you must have also experienced yourselves, most sites end up with a few dozens of views.
Anyways, I have previously filed #1897 in which I mention the same issue. Similar/related but different problems.
Recent comments
for instance, to set up a layer for water basins and another for mining concessions... Are those tiles from a tile server, or some GeometryCollection in local file in json...
Layer management in Leaflet
Thanks for responding. I was expecting that it be relatively easy to manage overlay layers (not the base layers that are indeed controlled form the Leaflet More Maps module's settings page)....
Layer management in Leaflet
We were able to add overlays and polygons to leaflet with a custom module as mentioned in https://github.com/backdrop-contrib/leaflet/issues/73#issuecomment-2907873081 with a combination of php...
Layer management in Leaflet