Latest Contributions by BlakeTerhune

Cool, is this for Pokemon Go? If you're using calculate field, I think what you want is:     # Expression setLandmarkType(!LandmarkName!, !LandmarkType!) # Code block def setLandmarkType(landmark_name, landmark_type): if "park" in landmark_name.lower(): landmark_type = "Park" return landmark_type     Be careful though, you will almost certainly get false positives by broadly grabbing anything with "park" in the name. EDIT: I just noticed the part about the Special field for EX Raids... With Calculate Field:   # Expression setSpecial(!LandmarkName!, !Special!) # Code block def setSpecial(landmark_name, special): if landmark_name.lower().endswith(" ex"): special = "EX Raid" return special   With an update cursor:     with arcpy.da.UpdateCursor(path_to_fc, ["LandmarkName", "LandmarkType", "Special"]) as cursor: for landmark_name, landmark_type, special in cursor: if "park" in landmark_name.lower(): landmark_type = "Park" if landmark_name.lower().endswith(" ex"): special = "EX Raid" cursor.updateRow([landmark_name, landmark_type, special])     ... View more

I really appreciate you posting the solution when you found it. Many people don't, and it's a shame. Could you format the code in a code block? ... View more

This all seems rather arbitrary. How do you know which row in the destination table is for which calculation? If you want to hard code the calculations like your original request, my original code sample should work (again, assuming you have the same number of rows in the destination table as you have calculated values). If you want to read the calculated values from a table and insert them (instead of hard coding the values), you can do that too (again, add error handling in case you have more rows in the destination table than you have calculated values):   calcval_table_path = path_to_calcval_table_here with arcpy.da.SearchCursor(calcval_table_path, ["OBS1", "OBS2", "OBS3", "OBS4"]) as search_cursor: for row in search_cursor: lookup_values = row destination_table_path = path_to_destination_table_here with arcpy.da.UpdateCursor(destination_table_path, ["Field1", "Another_Field_ifyouwant"]) as update_cursor: for enum, row in enumerate(update_cursor): row[0] = lookup_values[enum] update_cursor.updateRow(row) The SearchCursor portion will make the lookup_values. It'll be whatever is the last row in that calculated values table.   ... View more

Do either have these tables have a key id field that links a record from one table to the other? ... View more

Where you access the parameters in the execute portion, get it with the value property instead of valueAsText. From there, you can get the catalogPath from Describe. arcpy.Describe(the_layer_obj).catalogPath   Use the catalogPath when you create the cursor. Apologies if this is oversimplified for your use case. I haven't worked with multi-value inputs. ... View more

Yeah, this sounds like it's going down a dark path. Maybe look into creating geoprocessing tools in a Python Toolbox? Or maybe Attribute Rules? Or a custom add-in, if you're willing to step away from Python development. Or heck, maybe you can publish some feature layers and create a web app to edit the data. Either a custom JS app or built with Experience Builder. ... View more

This should technically work, but you have an extra line calling updateRow() that should be removed. I don't know if the logic is what you want to happen though. Can you clarify exactly what happens when it doesn't work? Is there an error message? ... View more

Some operations you can do on a feature class in a geodatabase might not be possible with a feature service. For example, you can't truncate/append, you would have to delete all rows, then insert all rows (for a traditional feature service hosted in standalone ArcGIS Server) and it would take considerably longer compared to a gdb fc. Also, you can't use something like arcpy.Editor or calculate field; although you can do more with GeoAnalytics tools if you have access to that. So, it depends on a lot of different things. I would guess that "pretty complex" scripts have more than just some arcpy cursors making a few data edits. You'd have to find matching capabilities in the ArcGIS API for Python or the ArcGIS REST API directly. ... View more

Can you clarify how the feature services are hosted/accessed? (Standalone ArcGIS Server, hosted in Portal data store, uploaded to ArcGIS Online?) ... View more

So to put it another way, you want to have one tool that can accept inputs of a gdb feature class or feature service and perform the same logic? ... View more

I'm not quite following because you mention wanting to use the API for Python to work with feature services, but you explained only how your scripts use file geodatabases. What do you plan to do with feature services? You could take a look at this thread about modularizing Python Toolboxes for inspiration. I do something similar with our Python scheduled tasks, they import a custom library with commonly used functions. Python Tool Management System - Esri Community ... View more

Yeah, this is pretty close! I haven't dived into the Esri Cartographic Information Model (CIMSymbol) yet. Thank you for this. ... View more

For the calculate field to multiply all the fields together, try this. I'm assuming you're using ArcGIS Pro. This won't work in ArcMap. # Use the Field Calculator to calculate the product poa_fields_expr = ",".join([f"!{f.name}!" for f in poa_fields]) expr = f"my_calc_func({poa_fields_expr})" # *args allows any number of arguments to be passed into the function. code = '''def my_calc_func(*args): result = 1 for poa_value in args: result = result * poa_value return 1 - result ''' arcpy.management.CalculateField( in_table=layer, field="Product_poa", expression=expr, expression_type="PYTHON3", code_block=code )   As for the other part of your code sample wehre you are setting the first field to 1, I recommend using calculate field because it will be consistent with using calculate field for multiplying the fields and you can explicitly name the field you're calculating rather than implicitly expecting the first field to be the one you want to calc. # Set the default value for "the field name here" arcpy.management.CalculateField( in_table=layer, field="the field name here", expression="1" )   Which brings me to a final point: I see you are setting that field to a string "1" instead of an integer 1. If your other poa fields are strings, you will need to convert them to a number in your code. Here is a final code (untested) that also forces the field values to be a number. import arcpy # Get the selected layer layer = arcpy.GetParameterAsText(0) # Set the default value for "the field name here" arcpy.management.CalculateField( in_table=layer, field="the field name here", expression="1" ) # Format the list of fields for calculate field. poa_fields_expr = [f"!{f.name}!" for f in arcpy.ListFields(layer, wild_card="poa*")] # Build expression and code block to calculate the Product_poa field. expr = f"my_calc_func({poa_fields_expr})" # *args allows any number of arguments to be passed into the function. code = '''def my_calc_func(*args): result = 1 for poa_value in args: result = result * float(poa_value) return 1 - result ''' arcpy.management.CalculateField( in_table=layer, field="Product_poa", expression=expr, expression_type="PYTHON3", code_block=code ) ... View more