Latest Contributions by TomBole

FYI A new issue has been logged through support - BUG-000168999 ArcGIS Pro | Map Layout Legend Not Honoring Elevation Dynamic Range. This issue is specific to the layout legend not updating (as opposed to what you see in the Contents pane) and I believe matches what is described in this thread. Tom ... View more

@BrettFrahm - We have found a reproducible case where the Graphics tab does not appear in the ribbon.  We have ONLY reproduced this with a specific project. Other projects containing graphic layers do not exhibit this bug.  This seems to be a very specific bug. Currently, we do not know what exactly is causing this. I encourage you to continue to submit ticket with support. It is always possible that the bug we are able to reproduce is not exactly the same as the one your are seeing.  I did find a TEMPORARY workaround. I noticed that if you add a new graphics layer - even one that you delete after adding - the tab is now available for the existing graphics layer. Unfortunately, this workaround does not persist with a saved project and needs to be done again. Hopefully, this might help you in the short-term. Thanks for the feedback and taking this to support. Tom ... View more

@BrettFrahm - Thanks! ... View more

Hi @BrettFrahm  I believe what you are seeing is a bug. Accessing the graphics in an activated map frame is already available.  Here is a screenshot I took using 3.3.1. The problem you are running into may be specific to your data/workflow. Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support. Thanks, Tom ... View more

@JamieDodd @SeanGarner @jcokin1  Sorry to hear that you are running into issues. There are a number of possibilities of why this is happening.  1. The fix for the bug referenced - BUG-000112368: Raster statistics fail to update dynamically with display extent when using stretched symbology imagery and dynamic range adjustment (DRA) in ArcGIS Pro - broke with a recent release. Unfortunately, regressions do happen.  2. The fix for BUG-000112368 does not address your specific use case/scenario. Since you're seeing issues with both the legend in the TOC (Contents pane) and the layout legend it is likely that the problem is with the passing of information between the raster layer and the legend(s). There may be a number of code paths that, unfortunately, were not tested.  3.  It is also possible that there is a different bug in the system.  Having bugs reported to Support is important so that we fully understand the workflow and can reproduce the issue. Otherwise, it is an educated guess whether the reported issue and its fix address a specific problem. Sometimes it does, sometimes it does not. Currently, I am unaware of any outstanding issue regarding legends and raster layers. I'll pass this along to the Raster Team to see if they are aware of any issues. I'll post once I have an update. Thanks for the updates. Hopefully, we'll get this resolved soon. Tom ... View more

This capability is already present.  The "Show feature count" does show the count for only features visible in the map frame.  Here is the tooltip for the option: Here is an example of the results with a simply polygon layer symbolized with unique values. An important caveat is that the count is based on the features symbol and not on its geometry as stated in the help "Work with a legend item". ... View more

Hi @BrianMcAuslan1  A separate issue - BUG-000170439 Unassigned layers are unexpectedly appearing in the legend of a duplicated layout when reopening an ArcGIS Pro project file (.aprx) -was recently reported the pre-dated 3.3. The key step to reproduce this issue was to remove legend items from the original legend before the copy/duplication of the layout or legend. Do you recall removing legend items from the legend as part of your workflows when you ran into issues with the legend? If not, we may have another scenario-specific issue.  We've made a pretty low level change in the code that handles source map/map frame pathing when duplicating layouts, layout elements and resourcing map frame and other layout elements for Pro 3.4. We believe this should resolve outstanding legend issues.  Thanks, Tom ... View more

All, A fix for BUG-000167906 A legend item element gets duplicated when copying a layer from a map frame on one layout to another map frame on another layout is available with the 3.3.2 patch for ArcGIS Pro and future releases. ArcGIS Pro 3.3 patch 2 (3.3.2) is now available for users to download from My Esri. Unfortunately, we could not address a separate legend item issue, BUG-000170439 Unassigned layers are unexpectedly appearing in the legend of a duplicated layout when reopening an ArcGIS Pro project file (.aprx), in time for the 3.3.2 patch. We have fixed this issue in version 3.4. There are several key differences between BUG-000170439 and BUG-000167906. BUG-000170439 was reproduced in Pro versions before 3.3, while BUG-000167906 was introduced at 3.3. In BUG-000170439 legend items are removed from the legend before being copied or duplicated In BUG-000170439 the issue is only seen after resaving and reopening the project and is seen with the second layout not the original layout as seen with 000167906 Though I’m currently not aware of any other issues concerning unexpected legend items that does not mean there are no outstanding issues. If you are still experiencing issues with unexpected legend items, please let us know. Commenting on the Community site is always helpful. Even more helpful is contacting esri support (https://support.esri.com/en/contact-tech-support). Getting steps, and data if needed, to reproduce an issue is vital in understanding the issue, fixing the issue, verifying the fix, and incorporating the scenario into out testing and certification framework.   Thanks, Tom ... View more

Hi @JuanitaBorden  I was unable to reproduce the unexpected duplication of legend items by saving the associated layer's symbology to a style. Applying the style also worked as expected. Without knowing the exact steps you are taking it is difficult to confirm that there is an issue with this workflow.  Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support. Tom  ... View more

Hi @TanWent,  Thanks for the idea.  I do have a question.  Are you aware that there are 2 options on the top of the view window that close an activate map frame? I've circled in green the two options to deactivate the  map frame.  These require a single click, whereas clicking an option in a context menu requires a click to open the menu and a click to choose the option.  Perhaps I'm missing something. Is there something about the 2 options circled above that leads to inefficiencies when working with a layout? Thanks. Tom ... View more

Hi @JuanitaBorden  I'm unaware of any fix available in 3.3.1. The fix for the following bug should be available with 3.3.2 - BUG-000167906 A legend item element gets duplicated when copying a layer from a map frame on one layout to another map frame on another layout.  We are also following up on a bug that the layout team has recently became aware of: BUG-000170439 - Unassigned layers are unexpectedly appearing in the legend of a duplicated layout when reopening an ArcGIS Pro project file (.aprx). We believe this issue is different than BUG-000167906 and has been around for a number of releases (FYI @BrianMcAuslan1). We are currently investigating this issue and I will post when I have more information. Thanks for the heads up on symbology/styles workflow. I'll take a look to see if I can repro.  Have you contacted support about this? If so, do you have an incident or bug number? Thanks for the feedback, Tom ... View more

@BrianMcAuslan1,  I understand your frustration. You're in good company! Thanks for reporting this to your local support group. The "duplicating legend item" issue that has been resolved for Pro 3.4 (and hopefully available with 3.3.2) was introduced at 3.3 (released this past spring). That you've been seeing an issue as far back as 9/21 leads me to believe that your bug is not the same as BUG-000167906 A legend item element gets duplicated when copying a layer from a map frame on one layout to another map frame on another layout.  We might get lucky and the fix for the scenarios outlined in BUG-000167906 also addresses similar scenarios we did not know about and specifically test against. Do you know if your local support reported this to Esri Support? If so, is there a bug number or incident number for reference you pass along to me? It would be good to get your scenarios and see if the fix for BUG-000167906 will also work for your scenarios.  Tom  ... View more

@KevinN_CSJ - I cannot reproduce the issue with the steps you provided.   Here are the steps I took: 1. Opened a project with a layout, Layout A and 2 maps where one map (Map A) has layer A and another map (Map B) has layers A and B. 2. Opened Layout A (with a map frame pointing to Map A). 3. Exported Layout A 3 times to .png output type. 4. From the Catalog pane, right-clicked Layout A and duplicated it using the Duplicate command from the context menu. 5. Opened the new duplicate layout, Layout A1. 6. Selected the map frame, opened its properties and changed the source map from Map A to Map B. 7. Activated layout A. I did not see any unexpected legend items in Layout A. Without more information I cannot reproduce your scenario and cannot verify that the fix we made for 3.4 and for 3.3.2 works in your scenario. Please contact Esri support. They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support. Thanks, Tom ... View more

@GISAdminSHN thanks for the feedback.   Unfortunately I'm unaware of any comprehensive list of all similar functionality across ArcGIS Pro and whether they use a visual approach. I can only speak to the expected behavior of layout elements that have the the Feature Display Options (Legends) and the "Visible rows" query option (Dynamic Text, Table Frames and Chart Frames). We had hoped that the term "visible" in the tooltip for these options would indicate the WSYSYG nature of the results. Looks like more information may be needed. I'll pass your comments to the team to see if there is an opportunity to revise any help documentation. Just to sum up. These layout element specific options work off of what is visible (i.e. is the feature symbol visible) in the map frame or within the extent of the current map series index feature. Unlike geoprocessing tools, or the Select by Location tool, these layout element-specific options DO NOT use spatial operators, such as intersect or contained by, on feature geometries.  Tom ... View more

Dynamic elements on the layout (ex: legend items with show only visible option checked on, dynamic text, etc) work with how symbols are drawn on the map - not with feature geometry (point coordinates). It is a visual, WYSIWYG, experience. This allows the layout elements to be database agnostic. This also allows for better performance. There is a trade-off to this approach - the "symbol overlap" issue described in this thread. There is no option to switch from the "symbol" based approach. In cases where geometric accuracy/precision is required I would recommend using Select by Location or a geoprocessing tool to get better results.  ... View more