Latest Contributions by DrewFlater

You do not need to use arcpy mp or ApplySymbology to symbolize an output dataset of a script tool. There are three approaches: 1. Open the script tool properties, go to the Parameters page, find the output feature class parameter, scroll right to the Symbology column  click in the cell and then browse to your layer file. This is the easiest for always symbolizing the output the same way. 2. If you need to symbolize differently depending on the output shape type or some other factors you may want to write code to symbolize the output. You have access to a parameter's same Symbology property set through the UI above available in tool validation. See here: Setting output symbology in scripts—Geoprocessing and Python | Documentation  3. There is a new arcpy function, arcpy.SetParameterSymbology also exactly for this purpose. This allows you to keep the Symbology logic in your source code instead of validation or the tool properties. Arcpy mp is for mapping workflow automation not GP output symbolization. These other methods give you a ton of options for performing the latter. ... View more

Peter MacKenzie‌ did you set the environment in the Python window via arcpy.env.maintainAttachments = False, and then run the tool through the Geoprocessing pane UI? Once the project environments are established, changing the arcpy.env does not impact the environment settings for your project or the tools run in the Geoprocessing pane UI. You can think about it as a one way street - the environments set in the project are automatically derived into arcpy.env, but changes in arcpy.env don't flow up to the project environments. This could be a reason why the tool is stuck at 100% for a long time - the maintain attachments setting never got disabled for tools run in the Geoprocessing pane UI. Transferring attachments is a post process of creating new relationship classes and transferring potentially large amounts of binary information in blob fields into a new table in the geodatabase. The progress bar accounts for the feature transfer, but not for the attachment transfer which is a much less deterministic process, as each attachment can be a different size and require more or less processing time. Dan Patterson‌ had a hunch about that output named g.gdb\_1 -- the geodatabase does allow this name, and I could successfully run CopyFeatures with an output named _1.  Russell Brennan‌'s suggestion about Fiddler would help to debug if queries are still being made to the service or if things are stuck on the client side for a long period of time. Working with Esri Tech Support would help to do some of this troubleshooting for you. ... View more

Marjorie Jerez‌ This issue has been resolved in Alpha snapshots of ArcGIS Pro 2.6. The issue is due to loading new records into a shapefile and that shapefiles do not automatically recalculate a new spatial index/extent that includes those new features. As a temporary workaround you should be able to run the Add Spatial Index (Data Management) tool against the shapefile to get the shapefile to draw correctly. ... View more

Dan Patterson‌ I just reviewed that tech support bug and the case logged is non repro in current Pro versions. The weighted mean computation appears correct. Here is the math I used for the black border polygon summarizing the two colored polygons inside it. The mean Score calculated for the output is based on the ratio of overlap between the two summary features. The yellow feature accounts for 95% of the total overlap, so the weighted score will be much closer to that value. The orange polygon has a higher value, but only accounts for ~5% of the overlap, so it just nudges the mean value up a little. ... View more