Latest Contributions by JohannesLindner

Ah. In that case, you would need to do the unique symbology on an Arcade expression. Click on the expression button to open the editor:   Use this expression (modify it to fit your actual field names and values): var asset_group = $feature.AssetGroup // if this is not a FlowControlDevice, just return the asset group if(asset_group != 300) { return asset_group } // if this is a FlowControlDevice, return 301 if the switch is open, else 302 if($feature.SwitchIsOpen == 1) { return 301 } return 302   ... View more

That sounds like you want to symbolize with Unique Values. ... View more

Ah OK. You have to do just a little bit more. Intersect the fc with itself delete all features of the intersection where FID1 = FID2 use Join Field to copy the Shape_Area field into the intersection. Do this twice (join with FID1 and with FID2). use Calculate Field to calculate how much the intersection covers the respective features Percentage_1 = Area_Intersection / Area_1 * 100 Percentage_2 = Area_Intersection / Area_2 * 100 Select Layer By Attribute to select those features where both percentages are above a certain threshold, eg 90% export those features. The OBJECTID is the GroupID, the two FID fields are the OBJECTIDs of the features that are part of the group. You can use Join Field to get the GroupID Into the original feature class use Delete Identical on the exported fc with the Shape field     fc = "TestPolygons" out_folder = "memory" out_name = "Groups" # read fc as {oid: geometry} geo = dict([row for row in arcpy.da.SearchCursor(fc, ["OID@", "SHAPE@"])]) # intersect the fc with itself and read the result as [ [ geometry, fid_1, fid_2 ] ] intersection = arcpy.analysis.Intersect([fc, fc], "memory/intersect", "ONLY_FID") fid_fields = [f.name for f in arcpy.ListFields(intersection) if f.type=="Integer"] intersect = [row for row in arcpy.da.SearchCursor(intersection, ["SHAPE@"] + fid_fields)] # create output out_table = arcpy.management.CreateFeatureclass(out_folder, out_name, "POLYGON", spatial_reference=fc) arcpy.management.AddField(out_table, "FID_1", "LONG") arcpy.management.AddField(out_table, "FID_2", "LONG") with arcpy.da.InsertCursor(out_table, ["SHAPE@", "FID_1", "FID_2"]) as cursor: for shp, fid_1, fid_2 in intersect: # skip if fids are the same if fid_1 == fid_2: continue # get the corresponding original polygons shp_1 = geo[fid_1] shp_2 = geo[fid_2] # if they are sufficiently same-ish, write the fids into the output table if (shp.area / shp_1.area > 0.9) and (shp.area / shp_2.area > 0.9): cursor.insertRow([shp, fid_1, fid_2]) arcpy.management.DeleteIdentical(out_table, "Shape")       ... View more

With tools: Intersect the both feature classes use Join Field to copy the !Shape_Area! fields from the fcs into the intersection use Calculate Field to calculate how much the intersection covers the respective features Percentage_1 = Area_Intersection / Area_FC1 * 100 Percentage_2 = Area_Intersection / Area_FC2 * 100 Select Layer By Attribute to select those features where both percentages are above a certain threshold, eg 90% export those features. The OBJECTID is the GroupID, the two FID fields are the OBJECTIDs of the features that are part of the group. You can use Join Field to get the GroupID Into the original feature classes    Example (yellow polygons labeled with yellow OBJECTIDs, black outlined Polygons labeled with black OBJECTIDs, groups not symbolized but labeled with red OBJECTIDs. Polygons without group don't have enough overlap.)     You can do the same with arcpy, but the field mappings are a hassle. It's easier using Cursors: fc_1 = "TestPolygons" fc_2 = "TestPolygons_1" out_folder = "memory" out_name = "Groups" # read fcs as {oid: geometry} geo_1 = dict([row for row in arcpy.da.SearchCursor(fc_1, ["OID@", "SHAPE@"])]) geo_2 = dict([row for row in arcpy.da.SearchCursor(fc_2, ["OID@", "SHAPE@"])]) # intersect the fcs and read the result as [ [ geometry, fid_1, fid_2 ] ] intersection = arcpy.analysis.Intersect([fc_1, fc_2], "memory/intersect", "ONLY_FID") fid_fields = [f.name for f in arcpy.ListFields(intersection) if f.type=="Integer"] intersect = [row for row in arcpy.da.SearchCursor(intersection, ["SHAPE@"] + fid_fields)] # create output out_table = arcpy.management.CreateFeatureclass(out_folder, out_name, "POLYGON", spatial_reference=fc_1) for fid in fid_fields: arcpy.management.AddField(out_table, fid, "LONG") with arcpy.da.InsertCursor(out_table, ["SHAPE@"] + fid_fields) as cursor: for shp, fid_1, fid_2 in intersect: # get the corresponding original polygons shp_1 = geo_1[fid_1] shp_2 = geo_2[fid_2] # if they are sufficiently same-ish, write the fids into the output table if (shp.area / shp_1.area > 0.9) and (shp.area / shp_2.area > 0.9): cursor.insertRow([shp, fid_1, fid_2]) ... View more

Arcade: Add a function to merge multiple Featuresets  Arcade: Add a function that quickly converts a Featureset into an Array  ... View more

Hey Josh, thanks that's good stuff!   I should note, I'm not timing individual feature loads in the last step, just how long it takes to do a for loop onallfeatures. Yeah, I did that too, which makes the time discrepancy even starker. After you spent a lot of time getting the first feature, it's not nearly instantaneous to access a feature, but all features.     when multiple functions are chained together, the Arcade compiler actually combines them into a single request. That's good to know!    If you have to extensively use a single FeatureSet, you can load the whole thing into memory by looping through and pushing each feature into a new FeatureSet. [...] What Arcade really needs is a function to quickly convert a FeatureSet into an Array... Yeah, that's the way I went in this case. I had to merge three featuresets and then compare each feature to each other feature. Pushing the features into the array is where this question cropped up, because it took a long time. I'm gonna open ideas for an Array conversion and Merge.     Pinging the World Atlas is a good idea and raises two other interesting points:   If you load a layer form the Living Atlas in the Arcade Playground, the FeaturesetBy* function returns instantly.   Loading the First() feature takes much less time for a layer from the Living Atlas compared to a service from my AGOL:     The time to load the layer is approximately the same. But the expression loads the First() feature from the World Atlas in 10 milliseconds, and from my AGOL in 460 milliseconds. That's a somewhat extreme difference. ... View more

That's the same error as in your previous reply. Did you actually change the fc path to include the databas?   ... View more

Literally anything. You just want to trigger the Attribute Rule, and the rule will calculate a new value for the Parish field. //Parish = "abc" ... View more

You forgot the path to the database. fc = "path:/to/your/database.sde/CorGIS.CORMGR.Blablabla" ... View more

Yeah, you can't just take that expression and use it in the field calculator. The Attribute Rule calculates multiple fields at once, you can't do that in the calculator. To apply the rule on an existing feature: create the rule, be sure that it triggers on update make any edit to the feature For bulk updates, just use the field calculator to update a field (let's call it Field1) to the value that is alread in that field: // Field1 = return $feature.Field1 ... View more

Yes. fc = "C:/bla/database_connection.sde/Points" ... View more