Latest Contributions by JohannesLindner

I'm not quite sure what you mean by combine. Do you want to also get the colors from a symbology with grouped unique values? Or do you have layers with grouped values from multiple fields? Eh, let's do both...   To extract the item dict for different combinations of (multiple fields) and (grouped values), we have to generalize a bit. Let's take a look at how these combinations are represented in Python:   # 4 layers with different Unique Value symbologies layer_names = [ "unique", # just a plain UV symbology "unique_grouped", # UV from a single field, but in groups "unique_multiple", # UV from multiple fields, ungrouped "unique_multiple_grouped", # UV from multiple fields, grouped ] aprx = arcpy.mp.ArcGISProject("current") for name in layer_names: layer = aprx.activeMap.listLayers(name)[0] renderer = layer.symbology.renderer first_item = renderer.groups[0].items[0] print(f"layer:\t{layer.name}\nfields:\t{renderer.fields}\nvalues:\t{first_item.values}\n\n")     layer: unique fields: ['TextField1'] values: [['A']] layer: unique_grouped fields: ['TextField1'] values: [['A'], ['B']] layer: unique_multiple fields: ['TextField1', 'IntegerField1'] values: [['A', '12345']] layer: unique_multiple_grouped fields: ['TextField1', 'IntegerField1'] values: [['A', '12345'], ['C', '2']]   values is a list of lists. There is an inner list for each value in the group. In these lists, there is a (string!) value for each field. We want to use these lists as dictionary keys, but that's impossible, because keys have to be immutable, and lists are mutable, so we change them to immutable tuples. Also, we have to have a separate key for each value in a group. def get_item_dict(symbology): if symbology.renderer.type != "UniqueValueRenderer": raise ValueError("symbology has to be Unique Value!") item_dict = dict() for group in symbology.renderer.groups: for item in group.items: for value_group in item.values: item_dict[tuple(value_group)] = item return item_dict   Also, let's put the color conversion into a separate function to make the code a bit cleaner... def convert_to_hex(color): color_type = list(color.keys())[0] if color_type == "RGB": rgb = color["RGB"][:3] return "#%02x%02x%02x" % tuple(rgb) else: return None   And with these two functions, we can concentrate on the actual workflow: layer_names = ["TestPolygons"] aprx = arcpy.mp.ArcGISProject("current") for name in layer_names: # get the layer layer = aprx.activeMap.listLayers(name)[0] # create a dict {values: item} item_dict = get_item_dict(layer.symbology) # add a new field arcpy.management.AddField(layer, "PW_Zoning_Designation", "TEXT") arcpy.management.AddField(layer, "ColorRaw", "TEXT") arcpy.management.AddField(layer, "ColorHex", "TEXT") # insert the label and color values with arcpy.da.UpdateCursor(layer, ["PW_Zoning_Designation", "ColorRaw", "ColorHex"] + layer.symbology.renderer.fields) as cursor: for row in cursor: # get the item key = tuple([str(x) for x in row[3:]]) # item.values stores values as string try: item = item_dict[key] # no item found -> default value and skip to the next feature except KeyError: row[0] = "No Symbol" cursor.updateRow(row) continue # store the item's label row[0] = item.label # store the raw color row[1] = str(item.symbol.color) # store the hex value row[2] = convert_to_hex(item.symbol.color) # write values cursor.updateRow(row)   ... View more

Glad to help 🙂  If your question is answered, please mark the solution so that this thread shows as answered. ... View more

Hmm, works in Pro and AGOL for me...   Your PM_TOT_VAL looks like a text field. Throw a Number() in there: var x = "12345" return Text(Number(x), "$#,###") ... View more

var fs = Featureset({ fields: [{name:"nojob", type:"esriFieldTypeString"}], features:[ {attributes: {nojob: "abcdefg"}}, {attributes: {nojob: "abcdabc"}}, {attributes: {nojob: "abcd"}}, {attributes: {nojob: "uvwx"}}, {attributes: {nojob: "uvwxabc"}}, ] }) return GroupBy(fs, [{name: "test", expression: "SUBSTRING(nojob, 1, 4)"}], [{name: "test_count", statistic: "COUNT", expression: "1"}] )     ... View more

As it turns out, getting a symbol's color is easy, but there's no built-in way to get the hex value...   If you have defined all your symbol colors in the RGB system, you're good to go: layer_names = ["TestPolygons"] aprx = arcpy.mp.ArcGISProject("current") for name in layer_names: # get the layer layer = aprx.activeMap.listLayers(name)[0] # get the symbology fields and items renderer = layer.symbology.renderer fields = renderer.fields items = renderer.groups[0].items # create a dict {values: iteml} item_dict = {tuple(item.values[0]): item for item in items} # add a new field arcpy.management.AddField(layer, "PW_Zoning_Designation", "TEXT") arcpy.management.AddField(layer, "ColorRaw", "TEXT") arcpy.management.AddField(layer, "ColorHex", "TEXT") # insert the label and color values with arcpy.da.UpdateCursor(layer, ["PW_Zoning_Designation", "ColorRaw", "ColorHex"] + fields) as cursor: for row in cursor: # get the item key = tuple([str(x) for x in row[3:]]) # item.values stores values as string try: item = item_dict[key] # no item found -> default value and skip to the next feature except KeyError: row[0] = "No Symbol" cursor.updateRow(row) continue # store the item's label row[0] = item.label # get the symbol color color = item.symbol.color color_type = list(color.keys())[0] # if it's rgb, convert to hex if color_type == "RGB": rgb = color["RGB"][:3] row[2] = '#%02x%02x%02x' % tuple(rgb) # if it's something else (hsv, hsl, cmyk), you have to convert that in other ways... here I just don't convert else: row[2] = None # store the color value as string for documentation row[1] = str(color) # write values cursor.updateRow(row)   Note that we're storing the whole symbology item in the dictionary (line 12), not only the label. This way, we can access the item's symbol color in the for-loop (line 33). Colors can be defined in different systems (RGB, HSV, HSL, CMYK, ...). Converting from RGB to hex is pretty straightforward (line 38). If you have other color systems, you probably have to convert those values into RGB first (line 41). A good start could be the module colorsys, which is part of the default Python installation. It might be easier to go through your symbology and just switch the system there.     ... View more

 If the expression returns true, however, nothing is written. The condition is true when step7Phone is null. In that case, you try to call attributes (eg contact_name) on a null (non-existing) object in lines 14-16, which results in an error, the expression doesn't return anything. Instead, you want to check if step7Phone is null before you use it. Something like this: var step7Phone = First(Filter(...)) // if no secondary contact info is found, only return the primary info if(step7Phone == null) { return step4Phone } // create the secondary info var step8Phone = ... // return both primary and secondary info return step4Phone + TextFormatting.NewLine + TextFormatting.NewLine + step8Phone ... View more

You can search the closest line feature and then use the new-ish NearestCoordinate function to snap the point to that line. // Calculation attribute rule on the point fc // field: empty function closest_feature(test_feature, compare_feature_set) { // returns the feature of compare_feature_set that is closest to test_feature var min_distance = 9999999 var closest_feature = null for(var f in compare_feature_set) { var d = Distance(test_feature, f) if(d < min_distance) { min_distance = d closest_feature = f } } return closest_feature } // load the other featureset var fs = FeatureSetByName($datastore, "Highways.HIGHWAYMGR.NSG_Network") // get the feature that is closest to the current $feature fs = Intersects(fs, Buffer($feature, 100)) // only analyze close-ish features var f = closest_feature($feature, fs) // abort if we didn't find something if(f == null) { return } // return the intersecting feature's value and snap the point to the found feature return { result: { geometry: NearestCoordinate(f, $feature).coordinate, attributes: {StreetsUID: f.NSG_STREETS_UID} } }     If you don't have access to NearestCoordinate yet, you can use the functions from my answer in this blog. ... View more

NameError: name 'arcpy' is not defined The script is meant to be executed in the ArcGIS Pro Python Window, where arcpy is imported by default. If you want to execute arcpy code outside of the Python Window (eg in custom tools or standalone scripts), you have to import arcpy first.   Your problem is a little different from the other ones in this thread. Your feature class basically already is a match table. You could probably run AddAttachments for each AttachmentField. To make it easier, you can transpose your table. So instead of ID Attachment1 Attachment2 1 a1   2 a2 a3   You get  ID Attachment 1 a1 2 a2 2 a3     This script will take care of the transformation, the MatchID field will contain the ObjectIDs of your fc. in_table = "TestPoints" out_match_table = r"memory\match" attachment_fields = ["TextField1", "TextField2"] import arcpy from pathlib import Path # create match table p = Path(out_match_table) match_table = arcpy.management.CreateTable(str(p.parent), str(p.name)) arcpy.management.AddField(match_table, "Filename", "TEXT") arcpy.management.AddField(match_table, "MatchID", "LONG") # for each row in in_table, insert all attachment names into match table with arcpy.da.InsertCursor(out_match_table, ["FileName", "MatchID"]) as i_cursor: with arcpy.da.SearchCursor(in_table, ["OID@"] + attachment_fields) as s_cursor: for row in s_cursor: oid = row[0] for attachment_name in row[1:]: if attachment_name is not None: i_cursor.insertRow([attachment_name, oid])   Input fc:   Output match table:   Then use that match table in AddAttachments:   Which should attach all specified files:   ... View more

Hah, 200 exactly, nice! Seems like I was extremely active in the first half of 2023. But sadly I don't get to use ArcGIS (or any GIS) in my new job, so I've been much less active since then... I'll have to step up in this year's contest 😅     ... View more

Hey Hlynur,   this scenario is described in this blog: https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/advanced-gdb-attribute-rules-editing-external-features-with-attribute-rules/   ... View more

This was probably 2.8 or 2.9 Make sure you allow symbol property connections (top right of the image under option 3. ... View more