Latest Contributions by TomBole

Hi @David_Brooks  We do have an internal bug. Currently it is sitting in our backlog. I do not know when we will get to it. I'll make note of your query and perhaps it might be something we can bump up in priority.  Unfortunately, this internal bug cannot be tracked outside of Esri. If you want to keep track of this issue you should contact support and enter a bug with them. Entering an issue with support also helps us gage how many are being affected by a bug and helps us prioritize our work. Having a bug number generated from a customer such as yourself makes a real difference.   Tom ... View more

Hi @ZeMadmapper  This capability is already available with ArcGIS Pro. Adding a thousand separator to your grid labels is done using a formatting tag. Here is a screenshot of how it looks in ArcGIS Pro. For more information please see the help topic Work with grid labels tags .  Hope this helps, Tom ... View more

Hi @JonathanDandois  Currently, you can utilize the date/time stored in a bookmark in order to create a Bookmark Map Series that sets the time for the map frame. You can use dynamic text to display the date/time. One caveat, you won't be able to set a page query on layers such as you can with Spatial Map Series. This may not be the clean workflow/solution you're looking for, but it might help you get "most" of the job done in the meantime. Hope this helps, Tom   ... View more

Hi @HajarAlqayoudhi  You asked how to disable the spell check. This can be done in the Options dialog (Proofing tab). For more information please see the help topic Set proofing options. Hope this helps, Tom ... View more

Hi @iticki  It is probable that you are running into BUG-000162418. This occurs when the the map is rotated and the map frames height is greater than its width. If your scenario is such that the map is not rotated and the map frame's height is not greater than its width then you may be running into an issue, though similar, that is different than BUG-000162418. If so, please contact support. Thanks, Tom ... View more

Hi @Amanda__Huber,  There are no specific issues that I'm aware of that would cause this not to work.  I was able to do this successfully using 3.4. In the screenshot below I was applying a "Custom query". I was also successful with "Visible rows" and "Map series rows".  I noticed that the error stated that no features were found (with, I presume, the custom query). I tested this as well and found no problem. There could be an issue specific to you data. Could you contact 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

Hi @ChrisShaffer  How large is the map frame - in page units?  Are you zoomed into the layout page?   Tom   ... View more

Hi @MattMurray1 ,  I apologize if my response made it appear that "you can either have layer clipping or layer blending but not both." This is NOT the case. Both should work together.  In the screenshot below you can see in the map frame an example of a vector tile service layer (USA_Topo_Maps) blended with a red map background using the "Mulitply" blending option. The layer is also clipped. On the right is the clipped layer without blending.  I would assume any case where this is not working to be a bug. Since there are many different layer type\blend option combinations it is quite possible that there may be a bug with a specific combination when clipped. Or, there could be another variable that is interfering with the drawing in your case. For instance, is this issue only occurring with a map frame (page layout) or do you see it in a map view? I found some related issues that have been addressed: BUG-000154946 Blend and Clip behavior on Layouts with CMYK are not WYSIWYG. This issue was fixed with release version 3.2. BUG-000151718 The clip to an outline option in Layout View causes the entire map frame to go white when activated on hill shade imagery that has a layer blend of Multiply applied to it. This issue was fixed with release version 3.1. BUG-000142625 Setting the layer blending mode to 'Darken' with a map series enabled causes the 'Exclude layers from clipping' settings in the Clip Layers section to not apply. This issue was fixed with release version 3.1. BUG-000141559 The Clip Layers tool does not work correctly in ArcGIS Pro 2.8.x for layers that are excluded from clipping if Layer Blend is set to a different option than Normal or Exclusion. This issue was fixed with release version 3.0. Currently, I'm not aware of any outstanding issue concerning blending and clipping. If you are using version after 3.2 you may be running into a new bug.  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. Hope this helps, Tom ... View more

Hi @HollyTorpey_LSA  I can confirm the behavior you outline - when the Export pane is set for a non-PDF output type that supports map series but does not support a single file (ex: PNG) the Files setting is carried over to the PDF. Though it is a valid setting for PDF, Pro should not be changing this based on the setting for a different output type. If this is an issue you want to monitor I would recommend contacting support. They can be contacted at https://support.esri.com/en/contact-tech-support. In the meantime, I'll take this to the team.   Thanks for the feedback! Tom   ... View more

Hi @PaulBartschi  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 @Brooks_Wilson  I tested the basic scenario adding the same feature class to a map that is different than the source map of the legend. With 3.3.1 I can reproduce the duplicating legend item bug.  The fix for this issue should be available with 3.3.2 (along with 3.4). I can confirm the fix also applies to using the Catalog pane to add layers.  Tom ... View more

@GayleNeufeld  The issue/bug most likely has to do with a negative offset for the label.  The screenshot below shows labels with a positive offset (black) and a negative offset (red). I cannot think of any option that would help the negative offset placement be more centered with the tick/gridline. Checking on the option "Draw parallel to grid edges" helps if the labels are relatively close to the edge, however, it is not a clean solution.  I do not see any existing issue for this.  I'll enter an internal issue for investigation. If this is something you want to track I would highly recommend contacting support. They can be contacted at https://support.esri.com/en/contact-tech-support. As for a workaround, if the end product is a printed map or export for publication you should be able to convert the grid to graphics or a feature class. This will enable you to reposition each label as you see fit. Tom ... View more

@AlfredBaldenweck ,  Query layers as a map series index layer should already be supported. However, there was a bug submitted - BUG-000165446 REGRESION: Query Layers can no longer be used as index layer of a spatial map series - which was addressed in the ArcGIS Pro 3.3. release. I've confirmed Query layers work as a map index layer with Pro version 3.4.  Tom ... View more

Hi @CynthiaCebrian,  I appreciate your frustration. The fix for the specific bug mention above - BUG-000141980 - was installed in 3.1 which was released 02/23/2023.  You can see the status for the issue here. I found it with a google search on "esri BUG-000141980". I tested the scenario described in this bug with version 3.4 and found no regression. Since you are still seeing issues with 3.3 I think it safe to assume that you are running into a separate issue.  Here are the outstanding custom grid issues that I am aware of. The last 3, without bug numbers, are issues discovered by esri staff. BUG-000169960 No option to select placement of grid labels when using clipped layers Adding a definition query to the custom grids layer doesn't refresh the custom grid Custom grid does not completely draw when the map frame is rotated more than 23 degrees UI sync issue when changing the vertical properties for 2 different label components within a single custom grid What kind of issue are you running into?  Are you getting the wrong results?  Is it a UI issue? If so, can you describe the issue?  What your steps?  We did do some work in the last few releases trying to improve the custom grid UI.  Not knowing the specifics of the issue you are running into there is no way I can say whether or not it is fixed in 3.4. This is one of the main reasons we encourage people to contact support and log a bug, even if it might be a duplicate of an existing bug. Only by having actual data/steps can we validate the fix for the specific problem someone is reporting. Otherwise, we are validating the fix against our data/steps and understanding of the problem. Sometimes this matches bugs not reported, sometime it doesn't. I highly encourage you to take your specific issue to 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