nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Enhanced Layer List Widget

RobertScheitlin__GISP

All,

Here is my latest widget for Flex Viewer. It is the first 3.4 widget I have been able to publish due to some issues with ArcGIS.com.

This is my replacement to the TOC Widget

This widget provides an enhanced version of the Layer List Widget for the Flex Viewer. This enhanced version contains UI enhancements that are currently request for the OTB version, such as extended layer menu that contains collapse all, expand all, zoom to make visible, and changed behavior on the description option. The enhanced version also supports legends for CSVLayer and GeoRSSLayers as well a default legends for basemap rasters, annotation and raster catalogs.

It is recommended that you use this widget in Application Builder 3.4 as it has been fully integrated into the App Builder GUI and you will not have to deal with XML.

http://www.arcgis.com/home/item.html?id=58d9bb5693c94918a3934781d7234d18

Find more posts tagged with

Accepted answers

All comments

NatashaManzuiga

Robert, how can I refresh eLayerList visible Status if I change programmatically the visibility from another widget??

Thanks,

Naty

rzufelt

Whoops, can't believe I didn't try that first. But yes, it does behave that way with the OTB widget. Guess I'll have to learn to not uncheck the box.

RobertScheitlin__GISP

Rhett,

Does it act the same way with the OTB LayerListWidget?

rzufelt

Hi Robert,

Not sure if you are already aware of this as I'm not real confident in the "new" forum search results. However, Utilizing your eLayerListWidget 3.6.2 in compiled version FV3.6.

I have a single service with multiple feature classes in it. Loading it as dynamic, but have a couple grouped layers with many of the sublayers set up to be able to edit with the edit widget.

If I preload="closed" the edit widget, then everything seems to be OK, but, once the edit widget has been opened (doesn't matter if you close it again or not), If I un-check the box next to the layer (as named in the config.xml), it will un-check all the point layers inside the grouped layers, but not the line layers.

The above is what it looks like BEFORE edit widget has been opened.

This is what it does once edit widget has been opened.

Also, I know all these are out of scale range in my example, but same result even if they are all visible.

Is this a known issue with the eLayerListWidget and EditWidget, or have I done something to make it "behave" this way?

RobertScheitlin__GISP

Matt,

Great news, because I was not finding anything.

MattPohl

I believe that this is related to grouped sub layers of a service. If I turn on a layer that is part of a group, and then turn off a layer that is not part of a group, the group layers automatically turn off too. My above post had the excluded layer inside a group layer. So even though the configuration is a little different, both scenarios are creating the same end result. Any one else seeing this?

Matt

Not sure how or why, but this is no longer an issue anymore and the expected behavior is what I am getting. I didn't do anything different to the service, mxd, or code, so I am not sure what happened. This is a great widget Robert, thank you.

Matt

MattPohl

I am running into a slight problem when trying to exclude a sublayer from the eLayerList. I am using the following for the exclusion:
Code:

<excludelayers>
<excludelayer mapservice="serviceNameInConfig">7</excludelayer>
</excludelayers>

This works fine when the viewer loads, sublayer 7 is not listed in the widget. Being that I have it turned on in the mxd it displays when the viewer loads as well, which is great. However, when I turn a layer on or off in the widget, the sublayer that is excluded turns off too. Once it turns off I can not get it to turn back on as it is excluded from the widget. I am using the latest version of both the viewer and the eLayerList. Any thoughts would be greatly appreciated.

Thanks,

Matt

I believe that this is related to grouped sub layers of a service. If I turn on a layer that is part of a group, and then turn off a layer that is not part of a group, the group layers automatically turn off too. My above post had the excluded layer inside a group layer. So even though the configuration is a little different, both scenarios are creating the same end result. Any one else seeing this?

Matt

RobertScheitlin__GISP

Matt,

Hmm. I will have to look into this one when I get some free time.

MattPohl

Sorry... I posted the below to the wrong thread:

I am running into a slight problem when trying to exclude a sublayer from the eLayerList. I am using the following for the exclusion:
Code:

<excludelayers>
<excludelayer mapservice="serviceNameInConfig">7</excludelayer>
</excludelayers>

This works fine when the viewer loads, sublayer 7 is not listed in the widget. Being that I have it turned on in the mxd it displays when the viewer loads as well, which is great. However, when I turn a layer on or off in the widget, the sublayer that is excluded turns off too. Once it turns off I can not get it to turn back on as it is excluded from the widget. I am using the latest version of both the viewer and the eLayerList. Any thoughts would be greatly appreciated.

Thanks,

Matt

RobertScheitlin__GISP

Matthew,

Neither of your requests are currently possible in the widget.

MatthewColwin

Hi, I've downloaded 3.6.2, mostly because I really liked the Description feature as a way to more easily and succinctly describe the data layer to a user.

However, I have a couple questions. I have 3 services in my application. A feature service, a map service, and a dynamic map service. The first two are single datasets, while the dynamic map service was added so that 5 different published datasets would be grouped together as one layer in the layer list (also for labeling, but that is unimportant). When using the eLayerList widget, the 5 grouped datasets work exactly as I want, where there is a Layer called "Regions" that can be expanded to see the 5 datasets, and when each of these datasets are expanded, you see their symbology. However, the other two datasets that aren't part of a 'group' also require that the user expands two layers (i.e. expand "Projects", and then expand a second "Projects" entry) before the symbology shows. Is there a way to make single layers not have to be expanded twice to view symbology?

Second, is there a way to only have certain layers be expanded when the widget loads? So if I have my 3 layers, but only 2 of them are turned on when it loads, can I make it so those two layers are expanded, but the layer that is turned off is not?

Thanks for your help, this is a great widget!

RobertScheitlin__GISP

Arthur,

Version 3.6.2 is now released that fixes the group layer issue.

ArthurRodriguez

I think part of my issue was what you pointed out about the group layers. I don't have any groups, but I am seeing that now all my services have the two check boxes by them. One for the Service Name, and then one for the layer/classification title. Just have to figure out the best way to direct users to finding the right tools, next to the right layers.

Thanks again for all the help, Robert!

RobertScheitlin__GISP

Arthur,

I think you found a bug on your number 2 question. I will have to get the "Zoom to make layer visible" fixed on certain layers.

RobertScheitlin__GISP

Arthur,

So I have code in the widget that if the layer is a ArcGISTiledMapServiceLayer it will run a getDetails request from the Rest Service endpoint and if those details have a Service Description or a copyright then a string using the description + line break + copyright are set as that layers internal tooltip and that is what is displayed in the popup description dialog.
The "Zoom to make layer visible" does nothing with re-centering the map it just sets the maps scale to make the layer visible based on the layers minscale or maxscale as reported in the Rest Service endpoint. Make sure if the layer is grouped you are executing this option from one of the sub layers.

ArthurRodriguez

Hello Robert,

Thank you for providing such a useful tool! I did have a couple of (hopefully) quick questions:

1) When using the "ESRI Descriptions Off" option, it looks like the descriptions are not coming through for my tile services, or at least the description button is not available. All of my feature services have the "Description" option, and if I turn "On" the ESRI Descriptions, then it does show up as an option for all services. When that is off, however, the Description option is no longer available for tile services. I have checked, and these services do have a description shown on the Rest page. Any idea why this may be?

2) What should the "Zoom to make layer visible" zoom to? Should it just be the center of the map, and then zoom to the visible extent scale of the given layer? Or is that set in the mxd when making the initial service? I have several layers this could work great for, but at the moment that button does not seem to be doing anything for them.

Thanks again!!
-Arthur

RobertScheitlin__GISP

Aaron,

I don't know what to tell you either as I just tested the eLayerList Widgets live preview site using the latest version of Chrome and it did not have any issue with moving layers

AaronKreag

Robert-

So I went through and deleted all of the layer widgets. I deleted all of the zipped elayerlist widget installer files too. Once it was all clean and no trace of the widget anywhere I went to the gallery and re-downloaded the latest 3.6 elayerlist widget. I used the 3.6 Viewer for Flex and installed the custom widget successfully. I added it to the map. Cleared out everything..caches, history, etc. I opened the web map and the enhanced layer list widget is still goofing up with the "move up" and "move down". Moving the top layer down puts it into the second from last position. Saying then move up, moves it down to the last position. Not sure where to go at this point....

I am using the latest version of Google Chrome.

Thank you. Aaron

RobertScheitlin__GISP

Aaron,

The listing of layers is in keeping with the 'norm'. You will see it the same way in the OTB layer list widget. As far as the moving of layer issue I have not seen any behavior like this since my older TOC Widget. I tested the eLayer List widget a couple of time just now and can not reproduce what you are seeing. Is it possible that you have the OTB LayerList widget and the eLayerList widget in the same app? You don't have my OLD TOC Widget in the app do you?

AaronKreag

Edited- Robert, actually it is taking the order of the layers under the operationallayers tag but it is taking them from the bottom of the list up so they display in the TOC/Legend in the opposite order they are listed in the main config.xml.

Robert,

I am using the elayerlistwidget and noticed a couple different things.

The widget does not honor the layer order in which they fall under the operationallayers tag in the main config.xml. For some reason I have six rest services in here and it defaults to listing them in the TOC in alphabetical order based on the label name that is used in the main config.xml.

Do you know if its possible (and how) to tell it to honor the order the layers are listed in the main config?

Also, when I have the TOC open and click on the small down arrow arrow to the right of my layer name in the TOC and say "move down", it moved down three layers instead of just one. When I click it again and say "move up", it actually moves it down one. Not sure whats up there.

Any insight? Thank you! Aaron

GISDev1

Thanks for you advice. I have gone back to the mxd and set the full extent to the proper extent and republished. The zoom to function for the service works, but the individual layers don't behave consistently for the zoom to function. Some work, some don't.

So for the problem layers that don't zoom properly, do they zoom to a really small extent showing the whole world or down to (0,0) or what happens when you click Zoom To? For these problem layers, do they function properly in the mxd and in the javascript viewer?

DerekHunter1

Thanks for you advice. I have gone back to the mxd and set the full extent to the proper extent and republished. The zoom to function for the service works, but the individual layers don't behave consistently for the zoom to function. Some work, some don't.

Have you checked the full extent parameter in your REST service, to make sure it is correct? Try the zoom to function on the same layers that are causing the issue in the arcgisonline javascript viewer and see if it zooms to the proper location.

GISDev1

I am having issues with the Zoom to option. In certain grouped and non-grouped layers in a given service the Zoom to option zooms to latitude 0 longitude -105. When the zoom to function works incorrectly, it crashes the viewer.

Please let me know if any of your users has experienced the same.

Have you checked the full extent parameter in your REST service, to make sure it is correct? Try the zoom to function on the same layers that are causing the issue in the arcgisonline javascript viewer and see if it zooms to the proper location.

DerekHunter1

I am having issues with the Zoom to option. In certain grouped and non-grouped layers in a given service the Zoom to option zooms to latitude 0 longitude -105. When the zoom to function works incorrectly, it crashes the viewer.

Please let me know if any of your users has experienced the same.

Erickson_Contract_Surveying_

Awesome. Thx.

Derek,

Not exactly, but you could place it in a panel in the main config.xml:

    <widgetcontainer paneltype="left" initialstate="open" size="300">
            <widget label="Map Contents"
                config="widgets/eLayerList/eLayerListWidget.xml"
                url="widgets/eLayerList/eLayerListWidget.swf"/>
    </widgetcontainer>

RobertScheitlin__GISP

Derek,

Not exactly, but you could place it in a panel in the main config.xml:

    <widgetcontainer paneltype="left" initialstate="open" size="300">
            <widget label="Map Contents"
                config="widgets/eLayerList/eLayerListWidget.xml"
                url="widgets/eLayerList/eLayerListWidget.swf"/>
    </widgetcontainer>

Erickson_Contract_Surveying_

Myself not being a programmer, I am wondering if it is possible to have the eLayerList span (in height) the browser from below the FV header?

RobertScheitlin__GISP

Nancy,

This must be a bug and I will have to look into it for a future release.

deleted-user-OvQ2biYmIWQS

Robert,

Thanks so much for the quick find/fix. You can see the difference in the settings, however I'm still seeing the option for certain layers. It seems that the "zoom to" option is still available but not sure why. I am looking at the REST end point information and the only thing that differs between the layers that have the "zoom to" option and that have them removed is the scale dependent drawing of the layer. The layers that display "zoom to" option regardless of whether I have the option disabled are only shown after about 4k, those that have the option removed display up to 150k. Is there a way to remove the "zoom to" for all layers but keep the "zoom to make visible" for those layers that are scale dependent? I have attached the picture of what I'm seeing and circled what I want to remove in blue if that helps. [ATTACH=CONFIG]28313[/ATTACH]

FlexZoomToHelp.jpg

RobertScheitlin__GISP

Nancy,

Version 3.5.1 now fixes this Bug.

RobertScheitlin__GISP

Nancy,

That looks like a Bug in the widget. I will update and release a fix ASAP.

deleted-user-OvQ2biYmIWQS

Hi Robert,

First of all thanks for this widget, it is great as well! I am using ArcGIS Viewer for Flex 3.5 and it works as described but was wondering if there was a way to disable the "zoom to" option for all layers as it is confusing since it pans over to where I saved the map at before I published it and not necessarily to the scale dependent layer itself. The layers are dynamic if that makes a difference.

[ATTACH=CONFIG]28231[/ATTACH]

I have tried to set the <disablezoomtomenuoption> to both false and true and that doesn't make a difference for what I am doing. I like the zoom to make visible option however, it is very helpful and only want that one.

Here is the eLayerListWidget.xml:

<?xml version="1.0" ?>
<configuration>
    <labels>
        <visibilitylabel>Layer Visibility</visibilitylabel>
        <expandall>Expand All Layers</expandall>
        <collapseall>Collapse All Layers</collapseall>
        <zoomtomakevisible>Zoom To Make Visible</zoomtomakevisible>
    </labels>
    <tocsettings>
        <collapselegends>false</collapselegends>
        <disablezoomtomenuoption>false</disablezoomtomenuoption>
        <expanded everything="false">false</expanded>
    </tocsettings>
    <excludegraphiclayers>true</excludegraphiclayers>
    <excludebasemaplayers>true</excludebasemaplayers>
    <usenewesridescription>false</usenewesridescription>
    <excludelayers>
        <excludelayer mapservice="Property Web"/>
    </excludelayers>
</configuration>

Any ideas on how I can achieve this?

FlexZoomTo.png

GiosiaPoma

Hi Robert,
great job! Thank you.

I've implemented, in the old TOC, some code to hide layer not visible in scale range: in the addChild of TocITem.as I've inserted as filterFunction my function.
This function is overridden in TocMapLAyerItem.as and TocLayerInfoItem.as. It checks if isInScaleRange is true. Now I can't know where insert the children.refresh() . In the old TOC widget I've inserted the refresh in the TocItem.as in set scaledependat function. Now? I try to insert the parent.children.refresh() in the setIsInScaleRange... There is a better place for doing this kind of job?

Thank you for the support.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.