Questions On Creating An Optimized Web App Using Views or Lists

[CRP00]

Hello,

I currently have a map with over 100 layers and was looking for a way to optimize it for certain users, possibly reducing load size/times. Specifically, the map would need to be able to zoom in to different sites and turn off or completely remove unnecessary data from the layers list, keeping the focus on a much smaller group of items. There may also be a future need to connect the big map to a separate dashboard or 3D scene. I have looked into using the section widget and creating views; however, I'm not sure if this is the best route for what I am trying to achieve. Some research also suggested using the list widget for filtering. Any suggestions or experiences with this?

[JeffreyThompson2]

If you can use Custom Widgets, here's one that allows users to add/remove layers at will and loads layers by thematic groups.

https://community.esri.com/t5/experience-builder-custom-widgets/add-remove-layers-3-0-full-settings-...

For native support of thematic layer groups, there is this design.

https://community.esri.com/t5/experience-builder-tips-and-tricks/native-support-for-thematic-layer-g...

Some other ways for handling groups of layers.

https://community.esri.com/t5/experience-builder-tips-and-tricks/five-ways-to-handle-groups-of-layer...

[CRP00]

Thank you! I'll look into these; however, I need to make this as easy to use as possible for the end users and also give them limited control with adding/removing data. This is due to the fact that they are not the most GIS-savvy individuals.

[JeffreyThompson2]

That Custom Widget was designed for users with little GIS experience. From their end, they just pick layers from a menu.

I will second what @JonathanMcD is saying. Experience Builder is simply not well designed for making a choose-your-own-adventure style application with a large number of starting layers. If you are going to attempt it, it's probably best to either use a Custom Widget or split your layers over multiple Maps and Pages.

Here are some of the issues you will encounter when using that many layers:

1. High server and user memory: Everytime the user loads the application all the layers in the Webmap will have to load on their computer, whether they are visible or not, leading to slow performance on their computers and the server.
2. No good way to switch between groups of layers: See the blog posts above, but none of these solutions are great. They are just the best available.
3. No popup replacement widget: The standard ESRI popup works ok. But if you want something that doesn't cover the Map, there isn't an option without bringing in another Custom Widget.
4. Try to please everyone, wind up pleasing no one.

[CRP00]

I completely agree with you both. I think to your point I have to also take a "data is not a democracy" approach as funny as that sounds. I will review these options and choose a direction!

[JonathanMcD]

Perhaps a little direct, must question why.you have a map.with so many layers ? I would have to question what you are trying to show, the structure of the data, and what do you wish for a user experience ? 

I ask our planners to review their map structure when, given the are.planners, they want to chuck everything and the kitchen sink into.one map thinking the user will understand. 

[CRP00]

Not at all, I have asked the same question. I have tried to demonstrate the benefits of relying on separate, more focused apps; however, there is prominent fear of data loss and fear of the unfamiliar. I figured the best compromise was to optimize what people are comfortable working with as best as I can(even this may be a rejected solution).