Latest Contributions by Justin_P

Is there any way to change the default color schemes applied to raster layers in ArcGIS Pro? I am specifically concerned with the Suitability Modeler since it constantly refreshes the suitability map and transformed layers with the default symbology. I am colorblind and the default symbology is difficult to use.   ... View more

Hi, I am using the GeoAccessor module inside arcgis.features to enable spatial features in pandas dataframes to process some data as part of a python toolbox tool. I was able to convert a database table to a pandas dataframe and perform all the necessary data manipulation, but when I try to bring it back into a GIS table in_memory it doesn't seem to work. # Convert my pandas dataframe 'sdf_table' to a GIS database table in_memory processed_table = sdf_table.spatial.to_table('in_memory/processed_table') ... # After additional processing, copy this table to the user specified output database table output_table = arcpy.CopyFeatures_management(processed_table, output_table) This code fails on the Copy Features function, saying that the in_memory table does not exist or is not supported. It DOES work if I skip the in_memory output and just output directly to the final database location in the to_table() method. This leads me to believe that the arcgis.features.GeoAccessor.spatial.to_table() method does not support in_memory output, but I can't find any documentation saying that. Can anyone confirm this? I find it strange that there are no errors or warnings if the output path is not supported. File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 3886, in CopyFeatures retval = convertArcObjectToPythonObject(gp.CopyFeatures_management(*gp_fixargs((in_features, out_feature_class, config_keyword, spatial_grid_1, spatial_grid_2, spatial_grid_3), True))) File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 511, in <lambda> return lambda *args: val(*gp_fixargs(args, True)) arcgisscripting.ExecuteError: Failed to execute. Parameters are not valid. ERROR 000732: Input Features: Dataset in_memory\processed_table does not exist or is not supported   ... View more

I recently finished developing a python toolbox tool that ends up calling the arcpy.AddField_management() function about 25 times or so. I first developed it as a standalone script to get it working before I connected it up to my python toolbox. When I started testing the tool with the exact same data I found that the run time went up from ~20 seconds in standalone to ~80 seconds when run from a python toolbox inside an ArcGIS Pro map, a 4x increase. After playing around some more I found that it was definitely the AddField tool slowing it down, and then I noticed that if I close the attribute table in the Pro map the run time goes down to ~50 seconds. So what I think is happening is that that the Pro map is busy revalidating locks and updating the GUI, etc. unnecessarily mid-script. I also notice that when the add field tools are called the "Add" and "Calculate" field buttons start alternating being grayed out, like it is cycling through locks and UI updates or something. These alternate being gray Is there any way to prevent this from happening? Can I somehow pause all that validation or whatever it is for the duration of my script? If not, is there a more efficient method to add fields? These short runtimes may not seem like a big deal but I now realize that I have many tools that have a LOT of calls to AddField and this is likely something that happens throughout my toolbox. I would like to make sure my code is as clean and efficient as practical. All of the feature classes that have the add field function called on are in_memory layers, and are copied to new feature classes for the output layers. ... View more