Hello everyone.
Is there any way to control the visibility of layers already saved in a webmap / Map Viewer via a custom URL (without adding them back to the map)?
I know there is a "layers=show" parameter. However, this always seems to add the service back to the map, and my goal is to control the layers already saved in it (keeping the symbology settings, fields, popups, etc.), without adding them again.
A little context: I have a project analysis layer and this process has several distinct steps. I intend to create Dashboards to monitor each of the steps and display a special symbology for that step on an embedded map. I would like each Dashboard to open with the map already configured for that step, including the layer that should be initially visible and those that should be turned off, without the user having to keep turning the respective layer on or off.
The only way I know of would be to create separate webmaps with this view configuration, however, this makes the maintenance process more expensive, in addition to creating several unnecessary map items.
Any help would be appreciated. Thanks.
Solved! Go to Solution.
Hey,
I do not believe this would be possible with URL parameters and so using numerous web maps will likely be needed.
While this can lead to a lot of overheads in maintaining different web maps, there are other workflows that could be used to assist with this. For example the ArcGIS API for Python does facilitate the creation and cloning of Web Maps.
It would need a lot of work to get everything setup, but if this is going to be a heavily used workflow then this might be the best way of achieving this.
Hope that helps,
David
Hey,
I do not believe this would be possible with URL parameters and so using numerous web maps will likely be needed.
While this can lead to a lot of overheads in maintaining different web maps, there are other workflows that could be used to assist with this. For example the ArcGIS API for Python does facilitate the creation and cloning of Web Maps.
It would need a lot of work to get everything setup, but if this is going to be a heavily used workflow then this might be the best way of achieving this.
Hope that helps,
David
This is not a very common workflow, so setting up the API would probably be more work. But it's good to know that this is possible.
Thanks for the clarification.