Latest Contributions by BlakeTerhune

Try doing the join in Python using arcpy.AddJoin_management() (see example 2 at the bottom). Once you've done the join, then print the field names and see what you need to use for the search cursor. ... View more

Maybe you have to call your field name as "featureclass.fieldname" beacuse that's how ArcMap renames when you join. Try using ListFields to print the name of the fields on the feature class you're running the SearchCursor on (Texas2) so you can see what you're working with. fields = arcpy.ListFields(fc) for f in fields:     print f.name EDIT: Are you doing the join in Python? ArcGIS Help 10.1 - Add Join (Data Management) ... View more

When doing this with very long lists, I find it helpful to also format the code so it's more readable. Here I organized it by the first letter. cnty = [     "Archuleta",     "Boulder","Broomfield",     "Chaffee","Cheyenne","Clear_Creek","Conejos","Costilla","Custer",     "Delta","Denver","Dolores","Douglas",     "Eagle","Elbert","El_Paso",     "Fremont",     "Garfield","Gilpin","Grand","Gunnison",     "Huerfano",     "Jefferson",     "Kit_Carson",     "Lake","La_Plata","Larimer","Logan",     "Mesa","Moffat","Montezuma","Montrose",     "Ouray",     "Pitkin","Prowers","Pueblo",     "Rio_Blanco","Rio_Grande","Routt",     "Saguache","San_Miguel","Summit",     "Teller",     "Weld",     "Yuma" ]  # End cnty list You could also organize by any other logical groups with comments to make maintenance easier. code = [ ## Some Group     "007","013","014","015","017","019","021","023", ## Another Group     "027","029","031","033","035","037","039","041","043","045","047","049", ## Third Group     "051","055","059","063","065","067","069", ## More Grouping     "075","077","081","083","085","091","097","099", ## Still Grouping     "101","103","105","107","109","113","117","119","123", ## Last Group     "125" ]  # End code list And it works the same way with dictionaries! ... View more

Ah, yes, forgot about that. The actions for the original post are at the top of the post off to the right (under the following, share, bookmark, and like options). ... View more

Does using a search cursor in a list (dictionary) comprehension like this automatically close the cursor when it's finished like when using it in a with block? EDIT: I did a quick test and it looks like the lock does go away. Spiffy! ... View more

Post manage options (edit and delete) are under the Actions menu at the extreme bottom left of each post. ... View more

Instead of checking each row to see if it meets the condition, could you only bring back the rows that meet the condition and delete them all? import arcpy arcpy.env.workspace = r"C:\SouthA\Bolivia.gdb" listFCs = arcpy.ListFeatureClasses("*") field_names = ["field1", "field2", "field6", "field7"] where_clause = "field1 = 0 OR field2 = 0 OR field6 = 0 OR field7 = 0" for fc in listFCs:     with arcpy.da.UpdateCursor(fc, field_names, where_clause) as cur:         for row in cur:             cur.deleteRow() ... View more

I think you've really got two field calcs here: The IF statement to make the two letter codes The long concatenation expression I don't know how those two letter codes fit in to the concatenation expression. ArcGIS Help 10.2 - Calculate Field (Data Management) needs an expression type if you've got a code block to execute. The IF statement you have posted here is a code block in VB. For future compatibility and for the sake of this forum, I'll write it in Python. codeblock = """def findTwoLetter(sccatdesc):     output = None     if sccatdesc == "MAT":         output = "SB"     elif sccatdesc == "MBE":         output = "ME"     elif sccatdesc == "ME":         output = "TEST"     return output""" With that codeblock, you will need to include a call to the code block function (I temporarily called it findTwoLetter) with the field name as the argument. Something like expression = "findTwoLetter (!SCCatDesc!) " The final calculate field code would then be like arcpy.CalculateField_management(PeterTable, "PtrText", expression, "PYTHON_9.3", codeblock) Again, this does not include your concatenation because I don't know how it fits in. ... View more

In your example you only have four feature classes with different prefixe variations (A, B, C, and D). Are those four prefixes always fixed or could they change? If there are more than just those four or if they change, please describe the formatting and/or range of the possible prefixes. Also, I noticed some inconsistencies with your imports: If you import arcpy (like you do on the first line), it includes env. It is redundant to have from arcpy import env if you've already imported everything in arcpy; especially if you're still calling workspace with the full arcpy.env.workspace You import os but I don't see that you're using it anywhere. Might save a little time to just not import it if you're not using it. ... View more

Here is what I was thinking. Where you do the update in the second part of your original script, maybe do it this way. I have not tested this though, code may have bugs/errors. # now do the update: flds = correctFieldList(arcpy.ListFields(fc_out)) with arcpy.da.InsertCursor(fc_out, flds) as curs_out:     for p_id, p_owner in dct.items():         where_clause = '''"{0}" = {1}'''.format(fld_id, p_id)         with arcpy.da.SearchCursor(fc_in, flds, where_clause) as curs_in:             lst_row = list(curs_in.next())             lst_row[flds.index(fld_owner)] = p_owner             curs_out.insertRow(tuple(lst_row)) Not sure if recreating the search cursor every time is going to slow it down though (compared to writing to a dictionary or reading all rows). EDIT: The code syntax highlight keeps adding two extra single quote characters at the beginning of the where clause assignment. EDIT 2: I just noticed the InsertCursor documentation says the insertRow can be a list or tuple of values. Maybe it's not necessary to convert the lst_row back to a tuple on the last line? Sorry if I'm beating a dead horse, I'm still learning. ... View more

Ah, yes, the where clause when you create the cursor! But then you would have to use a dynamic where clause and create a new cursor each time. I agree with you then, it would be silly to do that compared to just popping the item from the dictionary. Thanks for the clarification Xander! ... View more

Thanks Xander, I see it now. I'm just trying to understand the code and your process. So you are iterating through the fc_in rows and then checking if the current ID is in the dictionary before writing the data to fc_out. I was thinking it might be easier to iterate through the dictionary instead of fc_in so you wouldn't have to remove the dictionary item but then I don't know how you would find the correct row in fc_in to copy the data in the rest of the fields. Is there a way to do that? Seems like it could be a faster because you wouldn't have to touch every row of in_fc; you're done after checking every item in the dictionary. ... View more

What is the purpose of removing (and returning) the item from the dictionary just before you write it to the shapefile? I don't see the "tmp" variable used anywhere else. tmp = dct.pop(p_id) ... View more