Latest Contributions by DrewFlater

Oh and one more follow up - if you re-add the output dataset from Catalog/Add Data back to the map, you get the default/normal single symbol right? ... View more

@RTPL_AU are you running a custom or system tool that produces the messed up symbology? This looks like a BUG that we would want to resolve. When a tool operation is something like a copy (might not be an exact copy, but some modification like a Clip, but the geometry type and fields from the input are the same), the geoprocessing framework determines if the input used is a layer, and in an effort to make the new output look similar to the input layer, the input layer properties including symbology, charts, popup definitions, and more, are applied to the new output. In general this was what a lot of users were expecting and made them more productive because they didn't have to re-set the layer properties with a post process themselves. But it's clear from your example case that it is not working as expected, which should be logged as a software defect.  We can leave the Idea open as it's still a valid idea, though for your case we obviously don't want it to be messing up the grouped labels, etc.  ... View more

Use the Join one To first join operation of Add Join for a case insensitive join. https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-join.htm#:~:text=One%2Dto%2Dfirst%20joins%20are%20not%20case%20sensitive%3B%20one%2Dto%2Dmany%20joins%20are%20case%20sensitive. ... View more

Refactoring the Calculate Field tool into a toolbar in the attribute table view is being researched for a near term release. Attribute Rules provide a lot of the functionality described above for storing a calculation expression with a field and automatically performing the calculation on data changes. Learn more about calculation attribute rules here: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/calculation-attribute-rules.htm  ... View more

@jbcypreste Spatial Join is about summarizing/transfering attributes from a join layer to a target layer based on spatial relationship of those two layers. Select By Location is about selecting features in an input layer that have a certain spatial relationship with features in the selecting layer. Spatial Join handles 1:m relationships where one target shares a spatial relationship with many join features, and you can either summarize the m attributes into one value, or get the value from the join feature that is the closest or has the most overlap. So in your parks and districts example, which layer is the input (the one that gets selection applied) and which is the selecting layer? For a spatial join it's likely you want something like the district ID that overlaps the most with the park to be transferred to each park. What is the scenario for Select By Location? The parks layer likely has dozens of parks features even for a small town and maybe a few districts, and maybe some of the parks overlap multiple districts. If the parks are the input and the districts are the selecting features, all parks are going to get selected because they all overlap districts. If you only have one park and you want to select which district overlaps it the most, that could be useful and you would set the districts as the input and the 1 selected park as the selecting features. But when there are multiple parks it is likely every district is going to get selected since each of them will likely be the district that overlaps with at least one park. Select By Location only adds a selection it doesn't in this example add the information about which district has the largest overlap with each park.  I am not sure what the expectation is here, which is why this idea is still in Needs Clarification status. ... View more

We are treating the Security warning on Refresh as a defect at this time, to be addressed in the near term.  If you only use Python Toolboxes from yourself/your organization which are all trusted, you could consider setting BlockNonSystemPythonToolbox to No. https://pro.arcgis.com/en/pro-app/latest/get-started/geoprocessing-settings.htm#ESRI_SECTION1_88A083A5D68B430D96BD4D81DBCD2D47  ... View more

Python toolboxes (PYT) support parameter descriptions authored in the ArcGIS Pro tool metadata editor, as described here https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/document-a-custom-tool.htm  When the parameters have descriptions, the arcpy function for sharing an sddraft from the tool result can be made.  Also in recent versions of ArcGIS Pro, the parameter descriptions are now optional when sharing the tool as a service.  ... View more

ArcGIS Pro's Calculate Field tool supports adding a new field to calculate values into.  ... View more

This is not offered as part of Buffer, but for the last several releases of ArcGIS Pro we have had the tool Remove Overlaps (multiple) in the Analysis Tools toolbox, that can be used for the described purpose. I wrote the intermediate buffers into memory, then removed their overlap using the Centerline option to split the overlapping buffer shapes with output to a final output feature class.   ... View more

This is in the Pro 3.5 Beta. ... View more

What I described is available in the Pro 3.5 Beta. XY Table To Point supports appending the new points into an existing feature class.   ... View more

Hi @wayfaringrob , @LarsArneson , @Anthony  I apologize that you ran into the defect you've described with the Export tools and field map control.  I was not able to reproduce the problems that were described in the comments on this Idea, using the Export Features tool with Pro 3.4 or 3.5 Beta, using file geodatabase or feature service input.  In earlier Pro release, a format specific problem related to the export tool field map was logged: https://support.esri.com/en-us/bug/export-features-in-arcgis-pro-does-not-support-editing-bug-000162878  This defect was fixed in ArcGIS Pro 3.3, and backported to Pro 3.2.2. Because this is a bug, I'm closing this idea. Please refer to the ArcGIS Ideas Submission Guidelines and Statuses: https://community.esri.com/t5/community-help-documents/arcgis-ideas-submission-guidelines-and-statuses/ta-p/904874#U904874  2. No bugs please. Idea Exchanges are not the right place to log software bugs or crashes.  Keep in mind that just because it isn’t the right fit as an Idea does not mean that we aren’t here to help.  Bugs and crashes should be logged with Technical Support.  If working in ArcGIS Desktop/ArcGIS Pro, crashes can be reported by sending an error report.  If you are using a version after ArcGIS Pro 3.3 and still encountering a defect related to the field map, please use the link above to log a new Esri Support incident. Thank you! ... View more