Latest Contributions by BlakeTerhune

Unrelated question for you, @JakeSkinner: Do you recommend using del on a cursor even when it's used in a with statement? ... View more

If that hard coded workspace path worked fine, then it's not a problem with the database. I see you are doing some other workspace path manipulation if the input feature class is in a feature dataset. Try some other variations of the path to see if you can get it to fail when hardcoded. My guess is that you're getting something in the workspace that is causing Editor to hang. ... View more

Okay, that looks fine. Now try an isolated test with the arcpy.da.Editor() with that workspace and see what happens. workspace = 'F:\\GIS\\WORKING FILES\\TestProjects\\TestingDB.gdb' with arcpy.da.Editor(workspace, multiuser_mode=False): arcpy.AddMessage('starting edit') # Nothing else, just leave the script. ... View more

Maybe something isn't right with your workspace manipulation. Try messaging out the workspace before you open the editor, then see if it works when you hard code that workspace path (or something else you know to work). ... View more

What version of ArcGIS Pro are you using? ... View more

Ah, yes, sorry about that. The FeatureSharingDraft class has a code sample for publishing a layer and a table. FeatureSharingDraft—ArcGIS Pro | Documentation ... View more

Does this have the information you need? Introduction to sharing web layers—ArcGIS Pro | Documentation Share a table—ArcGIS Pro | Documentation ... View more

Yes, this workflow can be automated. However, it's not efficient to calculate the park name field in playgrounds on a regular basis. Since this is something you need to happen regularly, I recommend creating a relationship class between park and playground and utilize Attribute Rules to automatically populate the park name. This has the benefit of always being updated immediately when the data changes instead of only when you run the script. ... View more

The Calculate Field tool in ArcGIS Pro will now create the field if it doesn't already exist, which is handy and saves a step. Either way, you should be able to have access to the new field in model builder and Python. Without more details, I can't advise further. If you are able to provide a detailed description of your starting tables and what you want the output to be, we might be able to provide some code examples. ... View more

If you can use geoprocessing tools to complete the workflow, it can be automated. If you have a basic working knowledge of Python, you can copy the Python command from Pro and paste it into your IDE to get the code started. Alternatively, if you already have a model built, you can export the model to Python. You would be free to edit variable names and utilize the memory workspace. I'm having trouble fully understanding the workflow from your description so please follow-up with any specific, detailed questions you have. ... View more

You'll probably use the geometryEngine for this. The docs don't clarify what happens when two geometries share a boundary, so you'll have to do a little testing. Seems like crosses or intersects would be a good place to start. Assuming that intersects will return true if they share an edge, you could check if it intersects but doesn't cross. EDIT: It looks like relate is what you want. You'll look for a specific boundary result in the DE-9IM matrix table result values. ... View more

@EdX1 wrote: @BlakeTerhune Would you recommend rebuilding the indexes on a regular basis? Is there any possible repercussions with deleting geoprocessing history from the metadata? This table I am editing contains critical data. Thanks! Yes, you should compress, update statistics, and rebuild indexes on a regular basis. Enterprise geodatabase maintenance tasks—ArcGIS Pro | Documentation The only down side to removing geoprocessing history is that you have to have a process to do it and you won't have a history of geoprocessing operations run on the data. If neither of those things are trouble for you or your organization, then go for it. For me, I try to include the option to not record the gp history in metadata when I run scripts. arcpy.SetLogMetadata(False) SetLogMetadata—ArcGIS Pro | Documentation ... View more

I think maybe you are missing single quotes around the last part of the SQL expression for subType. Is it a string or a number value? Try using f-string to build the expression. f"ROLLNUM15 = '{txtARN}' and SUBTYPE = '{subType}'" ... View more

That is definitely what I would do first. You could also try to rebuild the indexes. Also add the layer to a map and running some gp tool on it. If it's also slow there, you could try deleting geoprocessing history from the metadata. Or you could copy the features into a new feature class for testing and run your script on the new feature class to see if the performance is any different. ... View more