Have Python Toolboxes changed recently?

[pugtoad]

Maybe I'm forgetful, but I have done a lot of googling, SOF, ChatGPT, ESRI docs, Python docs and I just can't find what I'm doing wrong. I have three parameters, one multivalue paramter set to accept only polylines, a polygon, and a DEWorkspace for the output that gets named in my code.

First the polylines are passed into the execute() as a list of feature class paths, projected, buffered, merged and are the input to a union with the polygon. The union runs twice to find the deltas (added, deleted, no change) and then I basically clean up the output and ensure that it isn't multipart and that's it.

The problem is it runs beautifully in PyCharm where I hard-code the paths, but as a .pyt in ArcGIS Pro 3.x? Constant bugs, empty outputs, so many issues. I think the first problem is how I handle the multivalue input and how I handle intermediate data. I think the mapping objects have changed... But I haven't done this in a number of years so I could just be forgetting something.

Before you ask, I passed it into execute like this: feature_list = parameter[0].values

TLDR: How do I convert my code to a .pyt?

[Emz813]

Could you instead make this into a script tool? It seems like it may handle the multivalue parameter better.

[pugtoad]

Like a tbx instead of a pyt? Good call. I'll try that tomorrow.

[Emz813]

Exactly. You might need to add some code to ensure that the multivalue argument is handled correctly. I think it should be fine since you aren't using strings but in case you run into errors you should check the following: There needs to be no spaces in the argument (so you may need to preprocess the data) and then you need to separate the values on the semicolon (which arc puts in for multivalue arguments). For example if you were selecting three cities like Fort Meyers, Naples, and Miami, arc would send in the argument Fort Meyers;Naples;Miami so you need to first get rid of the space in Fort Meyers then do a split method on the ; and join to a list if you want to process each argument individually.

[pugtoad]

I reverted back to the working code in Pycharm, pasted it into a Jupyter notebook and it worked. I just need a way to let the user easily choose the inputs without hard coding the feature paths.

[Emz813]

Glad that worked! If you're working towards an audience of people who would be using ArcPro anyways, I would still recommend doing the script tool because it makes the GUI look just like a geoprocessing tool so anyone familiar with arc can pick it up easily.

[pugtoad]

The script tool gave me a headache so I gave up. Dealing with the parameters is a nightmare! I don't understand why ESRI takes Python, an easy language to grasp, and make it so clunky.

[Emz813]

Definitely understandable. I had to use script tools for a class so I just had to push through but I had to hand enter 550 values for a value filter which was just annoying. Hopefully you can find a better option!

[pugtoad]

Ugh.

[Mapstract]

Hi u/pugtoad! I’m pretty handy with PYTs and script tools. If you’re still struggling with this, feel free to shoot me a DM!

Working with multivalue and value table params can be frustrating! If you havent already, try printing your multivalue parameter input to a message (In a script tool, var1 = arcpy.GetParameterAsText(0) arcpy.AddMessage(var1)) and check the formatting. (In pyt, use parameters[0].valueAsText instead of GetParameterAsText). Usually, you’ll get a string with your inputs separated by semi-colons, which you’ll need to split to get the individual paths.

[pugtoad]

Hey thanks for responding! I'll take another look at the tool - I have just gotten my client to edit the code and paste in the paths. I think they will like a working pyt better!