Select to view content in your preferred language

Layer Visibility Presets (“One-Click Layer Sets”) in Field Maps

72
3
7 hours ago
Status: Open
Labels (3)
LeeBriggs
Emerging Contributor

Description

Field Maps currently allows users to toggle individual layers or grouped layers on/off, but it does not support saving or applying predefined sets of layer visibility states. This creates limitations when different teams require different combinations of layers, especially because Field Maps does not allow duplicated layers, preventing the use of traditional group-layer configurations to solve the problem.

What’s needed:
A feature that lets the map author create Layer Visibility Presets—named presets such as “Team 1 View,” “Team 2 View,” “Survey Mode,” “Inspection Mode,” etc. Users can then switch between these presets with a single tap, instantly updating which layers are visible.

Use Case Example:

  • Team 1 needs layers A, B, C, D

  • Team 2 needs layers B, C, D

  • Team 3 needs layers A, D

Because layers cannot be duplicated in Field Maps, we cannot create multiple group layers (e.g., Group for Team 1, Group for Team 2). Managing these combinations manually is slow and prone to error, especially in the field.

Proposed Solution:
Add the ability to define multiple visibility presets within the web map / Field Maps configuration. Each preset stores a list of layers and their visibility states. Field users can then switch presets using a button, menu option, or toggle in the Layers panel.

Benefits:

  • One-tap switching between complex layer combinations

  • Eliminates manual layer toggling

  • Supports teams with role-specific workflows

  • Avoids the current limitation of no duplicate layers

  • Reduces user errors in the field and speeds up task changes

This feature would make Field Maps much more efficient for operations that require dynamic views or role-specific workflows.

3 Comments
ZachBodenner

I feel like this is a great idea to include across the suite. I'd like to see the same thing with Experience Builder as well!

LindsayRaabe_FPCWA

Agree! A useful idea for any of the applications that have layers. 

ChristopherCounsell

Yes! Literally made a similar idea for task layout UI and functionality on non-task layers.

https://community.esri.com/t5/arcgis-field-maps-ideas/allow-layouts-and-filters-on-non-tasks-layers/...

We've hit so many issues tied to the Task Lists and performance... I don't need Tasks - I just need the buttons and filters!