Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- All Communities
- :
- Products
- :
- ArcGIS Enterprise
- :
- ArcGIS Enterprise Ideas
- :
- Live Legend for current map extent
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Follow this Idea
- Printer Friendly Page
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My idea is that there should be an option for each legend item (in REST and SOAP Api) to only list features in the legend that are actually visible in the current map extent.
For example:
If there is a unique value renderer containing 100 items and more (eg. geology) it would be very useful to display only items which are shown in the current map extent. Map extent could be a parameter for GetLiveLegend.
For example:
If there is a unique value renderer containing 100 items and more (eg. geology) it would be very useful to display only items which are shown in the current map extent. Map extent could be a parameter for GetLiveLegend.
My idea is that when Data Driven Pages is enabled, there should be an option for each legend item (in the legend properties) to only list features in the legend that are actually visible in the extent of that page. - See more at: https://community.esri.com/ideas/2439
Limit the features shown in the Legend to input geometry extents of the features being used for the Data Driven Pages in lieu of the simple map Extent.
Without this the Legend is displaying features that are within the simple map extent, but not actually within the Data Driven extent. (displayed but not applicable to the purpose of the map).
Setting the "Clip Data Frame to Current Data Driven Extent" option for the data frame should fix this but the Legend does not adhere to this setting.(not displayed in the data frame, but still in the Legend 😞
- See more at: http://ideas.arcgis.com/apex/ideaSearchResults?s=live+legend&searchButton=search#sthash.knR0NL2D.dpu...Without this the Legend is displaying features that are within the simple map extent, but not actually within the Data Driven extent. (displayed but not applicable to the purpose of the map).
Setting the "Clip Data Frame to Current Data Driven Extent" option for the data frame should fix this but the Legend does not adhere to this setting.(not displayed in the data frame, but still in the Legend 😞
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.