Latest Contributions by Luke_Pinner

Unrelated to your issue, but this line is not correct temp = arcpy.env.scratchGDB + "\\temp" From the Scratch GDB documentation: The Scratch GDB environment is read-only; you cannot set the location directly. Instead use Scratch Workspace temp = arcpy.env.scratchWorkspace + "\\temp"   ... View more

@Trippetoe wrote: Maybe i'm quibbling here (plus don't fully understand conda environments), but isnt the purpose of a conda environments to remove dependencies on other 'environments'?  I think the error message is a little misleading. But regardless, the version of arcpy in your cloned  environment needs to match the version of ArcGIS Pro to ensure binary compatibility, this is a common issue with other python packages that use C/C++ extension libraries.   If your script that uses arcgis API doesn't use arcpy (and doesn't require any arcpy functionality), you can create a stand-alone conda env with arcgis that doesn't include arcpy and thus doesn't depend on a specific version of ArcGS Pro. E.g. from the command line:   conda create -n arcgisapi -c esri arcgis   https://developers.arcgis.com/python/guide/anaconda     ... View more

Region Group (Spatial Analyst)  Lookup (Spatial Analyst) on count  ... View more

Please clarify whether you mean "6 features" or 6 feature classes.  A geodatabase (either file or enterprise) can hold multiple feature classes. A feature class can have multiple features.  To use a file system analogy, a directory/folder (geodatabase) can hold many text files (feature classes). A text file can store many lines of text (features). Truncate means to remove all features from a feature class, the feature class is not removed. The code I provided does that for the 6 specified feature classes.  Do you actually mean you have 6 features you need to delete from a single feature class in one gdb and then replace those features with 6 features selected from another feature class in a different gdb? If so, truncate is definitely not what you want. You need to select the features you want to delete (e.g. select by attribute/location tools or make feature layer tool with a where clause) in your script and then run delete features tool. ... View more

Get the output csv filename as a parameter (output direction) and use df.to_csv to write it out. input_csv = arcpy.GetParameterAsText(0) output_csv = arcpy.GetParameterAsText(1) df = pandas.read_csv(input_csv) #do some calcs df.to_csv(output_csv, index=False) ... View more

Assuming two separate geodatabases with all feature classes having the same name and schema: feature_classes = ["fc1", "fc2", "fc3", "etc..."] for feature_class in feature_classes: arcpy.management.TruncateTable(f"dir:/path/to/connection1.sde/schema.{feature_class}") arcpy.management.Append([f"dir:/path/to/connection2.sde/schema.{feature_class}"], f"dir:/path/to/connection1.sde/schema.{feature_class}", "TEST") ... View more

Not an answer to the question as asked, but you may wish to consider expanding your toolkit... Look at open-source options such as GDAL/OGR for commandline data conversion or QGIS for a full GIS suite.  Converting a bunch of KMZs to something ArcGIS can consume is pretty trivial. ... View more

And `yield` is the syntax for creating a generator function. ... View more

Inline variable substitution But I didn't know that was applicable to tools as well as model builder. ... View more

@AFackler_NAPSG wrote: Not sure how exactly to run that tool, but Pro is locally installed version 3.0.3 Example at the bottom of the page Dan linked to. ... View more

The ToolValidator class is used by script tools in custom toolboxes (legacy .tbx or new .atbx), not by Python Toolboxes (.pyt). In python toolboxes (.pyt) all the validation is done is the updateMessages and updateParameters methods of the tool class itself  Customize tool behavior in a Python toolbox   ... View more

Yes, this is a very different idea to "Link - Allow support for virtual / computed fields in Oracle/SQL Server versioned geodatabases" or native database functionality.  It's more akin to storing label/popup definitions in a layer (lyrx/aprx map layer) in that the virtual fields would be properties of the layer, not the data source and could be generated on the fly using Arcade or python expressions. A simple use case that I constantly run up against - data source: read-only corporate data. I need to do some calcs on an attribute (concat two or more fields, split a field, change case of some text values, etc.) e.g for using in symbology. I know  I can manually change symbology entries or group them, but that's manual and tedious and I know I can export the table or feature class to a copy that I can edit, but that's an issue for data management.  And query layers are fiddly and don't work on non-GDB datasources. ... View more