Latest Contributions by BlakeTerhune

I just noticed the ExportAttachments() function in 3.3. Maybe you could try that too if you're able to upgrade Pro.

Sorry, I have not worked with images much, but you could try ImageMagick or wand.

More information in the ArcGIS Pro Blog. Additionally, ArcGIS Pro 3.3 requires Microsoft Edge WebView2 Runtime version 117 or later. If it is not already installed on the machine, use the Evergreen Bootstrapper or Evergreen Standalone installer from Microsoft. Learn more in this blog.

@AlfredBaldenweck wrote: No idea how I missed that. I looked right at it and moved on. The documentation for mapType says, "Returns a string value that reports the Map object's type information. If the Map is 2D, MAP is returned. If the Map is 3D, SCENE is returned." It implies those are the only two options, which is clearly not the case. I am submitting feedback on that page to be more descriptive of the mapType property.

Apologies if I'm missing something obvious, but would it be the isBasemapLayer property on the layer object?

Using the Catalog View in ArcGIS Pro, you can drag and drop a feature class from one gdb to another and it will also copy the relationship class and related feature class/table. It only does the direct relationships though. Grandchild relates are ignored so you'll have to copy those separately or script it with Python to walk through all the relationships of the input feature class.

CreateDatabaseConnectionString() only connects to an edbms, not a file geodatabase. Therefore, CreateFileGDB() doesn't accept a database connection string; the parameters are for an output folder and name. I see you've also included a code snippet for Buffer. Is there something else you're trying to do?

Then add an input parameter (DEWorkspace) and have the user set the database connection manually to whatever they want.

If everyone is using the same database connection and it's not changing often, maybe you can create the database connection in the script when it's run? Just output to a temp directory that will get cleaned up when the script finishes. Or you can try a database connection string instead of using .sde files.

Using arcpy.GetParameter() returns the object that was input for that parameter when running the tool; whatever you have set as the parameter datatype. In the case of your tool here, if it isGPFeatureLayer or GPLayer, the return value of GetParameter() will be a Layer object so you'll have access to all that object's properties and methods. connectionProperties, dataSource, longName, or name might be the property you're looking for. layer = arcpy.GetParameter(0) def main(layer): arcpy.AddMessage(f"connectionProperties: {layer.connectionProperties}") arcpy.AddMessage(f"dataSource: {layer.dataSource}") arcpy.AddMessage(f"longName: {layer.longName}") arcpy.AddMessage(f"name: {layer.name}") if __name__ == "__main__": main(layer)

The Query widget in Experience Builder has a spatial filter option.

Ah, boo. I see what you're saying. Off to Python Ideas!

I would like to be able to use a database connection to get workspace properties from Describe. Using Pro 3.1.3, accessing any of the workspace properties everything results in OSError: "CIMDATA=<CIMStandardDataConnection xsi:type=...rest of connection string" does not exist If I'm building paths to layers and tables in a script, I sometimes use Describe to get workspace information from one layer to build another. It's also helpful in debugging. Here's a question discussion for reference.

In this case, since you are pointing at a layer input by the user, I would suggest that the user have the database connection pointed to the correct version when it's input. If not, you could either create a new database connection (or connection string) pointed to the version you want. Or you can try useing Change Version.

I'm testing out the new arcpy.management.CreateDatabaseConnectionString() with a connection to a 10.8.1 enterprise geodatabase in Oracle, but I can't seem to get any workspace properties from Describe. Everything results in OSError: "CIMDATA=<CIMStandardDataConnection xsi:type=...rest of connection string" does not exist If I create the connection with an object_name and schema so it points to a feature class, I can get layer properties from Describe and use things like ListFields(). So I know it can make some kind of usable connection. When testing, I'm only specifying database_platform, instance, username, and password. Is there something I'm doing wrong?

My Ideas

Latest Contributions by BlakeTerhune

Re: Convert blob/image to Python Image

Re: Convert blob/image to Python Image

Re: Unable to update to ArcGIS 3.3

Re: Map Object Properties: How do I tell if it's a basemap programmatically?

Re: Map Object Properties: How do I tell if it's a basemap programmatically?

Re: Copy features with related table

Re: How to create geodatabase with database string connection

Re: Access EGDB from SDE regardless of filepath

Re: Access EGDB from SDE regardless of filepath

Re: Enable edit session for particular layer in a versioned geodatabase

Re: When you're feeling stuck but believe there must be a solution!

Re: Describe Workspace properties don't work from CreateDatabaseConnectionString()

Update Describe to handle connection strings

Re: Enable edit session for particular layer in a versioned geodatabase

Describe Workspace properties don't work from CreateDatabaseConnectionString()

Re: Convert blob/image to Python Image

Re: Map Object Properties: How do I tell if it's a...

Re: Copy features with related table

Re: Access EGDB from SDE regardless of filepath

Re: arcpy.da.Editor Hanging up Script Tool

GIS Jobs

Python Snippets