Latest Contributions by Robert_LeClair

One thing I would check is your XY snap tolerance on the Edit core tab -> Snapping group.  By default, my snapping XY tolerance is 10 pixels.  You could change it to one or two map units and retry your editing workflow.  Do the points and lines now snap to the grid as expected? ... View more

I'm thinking a Spatial Join (Analysis) GP tool with a SUM Field Map parameter will do the job here! ... View more

One thing to test in your model - for the output, instead of of geodatabase raster dataset, add .tif right after the name of the output and see if the model works with *.tif's versus GDB raster datasets.  We'll start here on the troubleshooting and see what the result is here first.  Then go from there! ... View more

I think the issue is because with feature linked annotation, the piece of anno should be coming from the line feature class first.  Not the annotation feature class first.  Try this workflow instead: 1.  When you create the new line feature class, add a field called Name then follow the same workflow as you have in the video. 2.  In the LINES layer, create a new line and in the Attribute pane, type a value for the Name attribute field. 3.  In both the LINES layer and the LINES_ANNO layer, you'll see the attribute value.  In the Name field for the LINES layer and the Text String Field in the LINES_ANNO layer. ... View more

Here is an Esri Technical Support help document that describes the error message and provides a workaround/solution.  May help with your workflow. ... View more

Interesting.  So a couple things I tried with similar data is to change the callout type from balloon to background and changed the color to white and changed the outline color to black to see if that made any difference.  Kind of.  Second thing I did was go into the zones area of placement and change the 2 value to the 6 o'clock position vs the 10 o'clock position to see if that helped with placements and overlaps.  Kind of.  Try changing your zones up a bit and see if you get a desired outcome. ... View more

You may want to consider creating an ArcGIS Idea for this item.  The more kudos it receives the more attention it may get from the ArcGIS Pro developers! ... View more

I'm not sure if there's a plan/fix for this item but there is a workflow to Change the Data Type of an Existing Field to another field type that you can reference here.  Might help. ... View more

I tested the sort ascending and descending on an attribute field that does not have a coded value domain on it and it sorts as expected.  Nulls first, Type 1 next and Type 2 lastly.  There is BUG-000158191 - "Sort ascending and descending on a field with missing coded value domains in the attribute table does not work."  It's reproducible in ArcGIS Pro 3.1.1 and 2.9.5 and is currently under review.  I would put values in the Null fields and test again. ... View more

To get a list of map views in your ArcGIS Pro project, you can use the Python code here in this Esri Community post. To get a list of all data sources used in an ArcGIS Pro project, you can use the Python code here from the GIS Stack Exchange. Maybe there's a way to combine the 2 scripts into 1 script.  Not sure as I'm not a Python user. ... View more

Another way is to split your yellow polygon into 2 polygons using the Split tool in the Modify Features Pane.  Add a new field to your yellow polygon FC, called Transparency.  For the larger polygon, edit the transparency field to be 0.  For the smaller polygon, edit the transparency field to be 100.  Then go to your Symbology pane for the yellow polygon, click the Vary Symbology by attribute button (second from the left).  Click the dropdown arrow for Transparency, choose your Transparency attribute field.  Set the high value to 100% and the low value to 0%.  Voila!  Where the red polygon overlaps the yellow polygon is now invisible. 1 2 3 ... View more

@AndyIngall  - there is a great Technical Support article here that may be a start for troubleshooting the popup issue. ... View more

Do you have a screen grab of the GP tool that we can visualize to assist with troubleshooting?  Here is a breakdown of each error message: 000622: Failed to execute (<value>). Parameters are not valid.—ArcGIS Pro | Documentation 000354: The name contains invalid characters.—ArcGIS Pro | Documentation ... View more

I'm sure there's a functional limit to the number of layouts in an *.aprx but the standard messaging is unlimited number of layouts. ... View more

Certainly Jack - happy to assist where I can.  Have you contacted Esri Support Services to see if they can assist you further? ... View more