LocalLayerWidget Version 2.5 and AccessifizrWidget Layer - 09/28/2017
More to add. The problem appears when one or more sublayers of a service are turned off by default in the mxd being published. Here is an example:
Note the "Alaska" dynamic service, which is turned off by default using the Local Layer widget. In it, all three layers (Eastern Alaska Range, Pebble Cu-Au-Mo..., and Seward Peninsula) are on by default (as set in mxd). But in the Seward layer, one of the sublayers (ASTER, shown in red above) is off by default. This causes a slew of problems. When the Alaska service is turned on in WAB app, the Seward Landsat 8 data (shown in blue above) are displayed as they should be, but its attributes will not show in the Legend widget, and the ID widget will not show any results for it when a pixel is clicked. If the ASTER sublayer is turned on, then all behavior becomes normal (Legend is shown and ID widget works). It looks like an initialization problem that is removed once sublayers are toggled.
Of course, the effect of the problem can be minimized by always making all sublayers turned on (or off) by default in the mxd, but this constraint is unfortunate as it limits the ability to customize how complex WAB apps appear when they are first opened.
If the Landsat 8 sublayer is moved to above the ASTER sublayer before the service is published, the same problems occur.
This is a major problem with the Local Layer widget that effects the behavior of default and custom WAB widgets. Please let me know if you need more info.
----
Edit: The problem can also be solved by moving the "Seward Peninsula" layer above the "Eastern Alaska" and "Pebble..." layers in the mxd before publishing.
I am trying out the local layer widget and I have some problems that I’m not sure if I’m doing it wrong or if it’s a widget problem or a known issue that I’m not aware of.
- When I update the opacity of the esri imagery service basemap it still shows solid.
{
"type": "Basemap",
"name": "basemap",
"layers": {
"layer": [
{
"url": "https://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer",
"opacity": 0.56,
"displayLevels": null,
"isReference": false
}
]
}
},
Changing the opacity of a dynamic or feature layers still works fine, it’s just the basemap that isn’t working.
- The bold legend title shows the name of the service and I wanted to update the legend title without changing the service name. When I enter the layer name in the local layer the layer list wiget shows that new name, just not the legend.
- When I add a dynamic service layer is there a way to hide certain sub-layers from the legend and the layer list? Or even hide the whole layer from the legend?
- Is there a way to remove sub-layers of a dynamic layer from the map without removing them from the mxd and publishing a new service? I was thinking that the red x under sub-layer actions would remove that sub-layer but I guess it just removes the popup if you made one.
- I did have a half way work around where I created a portal map with imagery and set the opacity of the basemap in the web map. Then in the deployed app I update the config.json itemId to the portal map id and it worked for the trasparent basemap. (This only works when I don’t have a basemap set in locallayer) I can also add one additional layer and hide sublayers in the legend but it only lets me add one layer and any additional layers don’t show up.
"map": {
"3D": false,
"2D": true,
"position": {
"left": 0,
"top": 40,
"right": 0,
"bottom": 0
},
"itemId": "b4d44ccb75814ddd946618fb4509705f",
"mapOptions": {
"extent": {
"xmin": -12817519.037675126,
"ymin": 4329033.604186857,
"xmax": -12816866.934277477,
"ymax": 4329534.625020763,
Any thoughts or suggestions are much appreciated.
