Latest Contributions by BlakeTerhune

‎07-09-2021

This is an interesting problem but I think I found a solution using defaultdict. # import arcpy from collections import defaultdict # Example pipe data pipe_data = [(12, 'red', 1.5), (12, 'blue', 2.2), (12, 'red', 3.3), (24, 'blue', 4.99), (24, 'red', 1.05), (24, 'blue', 4.2)] # Real pipe data # pipe_fields = ["diameter", "material", "SHAPE@LENGTH"] # pipe_data = [row for row in arcpy.da.SearchCursor(pipe_fc, pipe_fields)] pipe_diameters = {row[0]: None for row in pipe_data} for diameter in pipe_diameters: # Collect all rows with the given diameter diameter_materials = [(row[1], row[2]) for row in pipe_data if row[0] == diameter] # Define and build dictionary with total lengths for each material in the given diameter material_lengths = defaultdict(float) for material, length in diameter_materials: material_lengths[material] += length # Put the resulting material/lengths as a value for the diameter pipe_diameters[diameter] = dict(material_lengths) # Total length of all materials for this diameter pipe_diameters[diameter]["diameter_length"] = sum(material_lengths.values()) # Report data for demonstration purposes. # dict.pop() is destructive, removing the diameter_length entry from each diameter. # Do not do this if you need to use diameter_length again later! for diameter, values in pipe_diameters.items(): print(f"{diameter} diameter total length: {values.pop('diameter_length')}") for material, length in values.items(): print(f"\t{material} length: {length}") Also, reading your code sample was really hard to follow because of your variable names. Try using more descriptive names to make the code more "self documenting". Your successors will thank you! Also, this might be a copy/paste issue, but standard Python formatting calls for exactly four spaces as indentation.

‎07-09-2021

Does it matter how ties are broken (if two or more fields have the same maximum value)?

‎07-08-2021

I may be mixing up projects and grids but I think you get the idea. Just do the spatial join, put it into a dictionary with project as key and the value is a list of intersecting grids. Then you can do what you need with it, like write it back to your feature class as a comma separated list of values. from collections import defaultdict try: # Perform spatial join between grid and project features. grid_project_spatialjoin_inmem = r"in_memory\grid_project_spatialjoin" arcpy.SpatialJoin_analysis( target_features=projectFeatures, join_features=gridFeatures, out_feature_class=grid_project_spatialjoin_inmem, join_operation="JOIN_ONE_TO_MANY" ) # Create dictionary keys of projects and values with list of grids project_grids = defaultdict(list) with arcpy.da.SearchCursor(grid_project_spatialjoin_inmem, ("projectPageName", "gridLabel")) as sCursor: for projectPageName, gridLabel in sCursor: project_grids[projectPageName].append(gridLabel) finally: arcpy.Delete_management("in_memory") # Write the intersecting grids for each project as comma separated list with arcpy.da.UpdateCursor(gridFeatures, ("projectPageName", "gridLabel")) as uCursor: for projectPageName, gridLabel in uCursor: grid_list = project_grids.get(projectPageName, "") uCursor.updateRow((projectPageName, ", ".join(grid_list))) EDIT: fixed a comment for creating the dictionary

‎07-08-2021

So would a rule be that if the number is over 4 digits, the remainder is taken from the beginning of the number and used as the zone? So if the number was 2361867, the zone would be 236?

‎07-07-2021

@JamesWilcox1970, this is a new requirement from your initial post. Please describe all the rules in which these projects are grouped into index grids and we can help you find a solution.

‎07-07-2021

I like dict.get() because it returns None by default if the key is not found. You can specify a different value in the second argument but None is redundant.

‎07-07-2021

Here's a blog you should read. It's got some techniques for doing stuff like this that I have found very useful. Turbo Charging Data Manipulation with Python Curso... - Esri Community Basically you'll read your "look up" data into a dictionary and reference it by some id to get the value you want to write elsewhere. If I'm understanding your logic correctly, it would look something like this. # UpdateCursor to add all index grid cells for each label gridList = {label: pageName for label, pageName in arcpy.da.SearchCursor(intersectOut, ("Label", "PageName"))} # List from intersection arcpy.AddMessage("Grid list = {}".format(gridList)) # For debugging with arcpy.da.UpdateCursor(indexTable, ("Label", "PageName")) as uCursor: for label, pageName in uCursor: gridList_pageName = gridList.get(label) arcpy.AddMessage(gridList_pageName) # Before going to the next record in the site index table # write the PageName from gridList if there is one. if gridList_pageName: uCursor.updateRow((label, gridList_pageName)) else: arcpy.AddWarning("Label {} not found in gridList; nothing updated.".format(label))

‎07-06-2021

Try changing line 11 to include the field name you are trying to get (PARCELNUM) parcelnum = feat.PARCELNUM; Also, it looks like you're only getting the PARCELNUM of the first record from the first query and the second query is only highlighting the first record. Is that correct?

‎07-06-2021

If you use the "NO_TEST" option for schema_type, you also need to use the field_mapping parameter to specify which fields can get mapped together. I've never tried NO_TEST without field_mappings but maybe this is the result. Append in memory workspace should work.

‎07-06-2021

How you are dividing up 34 zones? I mentioned in my post that if you are using the first digit, you'll only get nine zones before it starts repeating (1 through 9).

‎07-02-2021

What about this spiffy trick where you can reference the values of a row by field name using a dictionary? def rows_as_dicts(cursor): colnames = cursor.fields for row in cursor: yield dict(zip(colnames, row)) with arcpy.da.SearchCursor(r'c:\data\world.gdb\world_cities', '*') as sc: for row in rows_as_dicts(sc): print row['CITY_NAME'] Getting arcpy.da rows back as dictionaries | ArcPy Café (wordpress.com)

‎07-02-2021

Is your goal to have one feature class with everything smashed into it (as many spatial joins) or to have separate feature classes, each spatial joined to only Parcels?

‎07-01-2021

Did you restart Web AppBuilder after you copied the files into ..\client\stemapp\widgets

‎06-30-2021

Spatial join is an inherently intensive operation and there's not much you can do to improve that. Indexes, multithreading, maybe using memory workspace. The looping is how I would go about doing it. You could consider using field mappings when you copy the data to memory and keep only the necessary fields but that's a lot more work because you have to have a list of keep fields for every feature class. Also, looking at your code, it looks like you'll end up spatial joining fc1 to its self when it gets to that in the fcs list.

‎06-28-2021

Is there some new requirement that you only need to null out fields that are not null? It's okay if CalculateField nulls an already null field value; you don't need to query them out. If you want to do a query first, either use Select Layer By Attribute first or (what I would recommend) is using the UpdateCursor method mentioned by @curtvprice.

My Ideas

Latest Contributions by BlakeTerhune

Re: Nesting multiple dictionaries into a dictionary in a single dictionary?

Re: How to populate a field by the field name having the maximum value across the rows?

Re: Best way to add values to a string for UpdateCursor

Re: Printing the highest value between a range of values of a field

Re: Best way to add values to a string for UpdateCursor

Re: Best way to add values to a string for UpdateCursor

Re: Best way to add values to a string for UpdateCursor

Re: Querying one feature layer to use to query another layer (problem grabbing result of first layer)

Re: Appending features using two feature classes in "memory" using Python in ArcGIS Pro

Re: Printing the highest value between a range of values of a field

Re: Writing a script to self indexing list of fields

Re: Multi batch spatial joins

Re: eSearch widget

Re: Multi batch spatial joins

Re: Update Multiple fields at once

Re: What's New in ArcGIS Experience Builder (June ...

Re: The connection property set was missing a requ...

Re: High Portal content views

Re: DevSummit 2026: The Second Time Around is Diff...

Re: Transfer Expereince Builder to another organiz...

Experience Builder Tips and Tricks

GIS Jobs

ArcGIS Arcade

Python Snippets