Latest Contributions by JohannesLindner

If you want to do this in the CalculateField tool, you can use this expression, modified for each statistic: // load the whole feature class var fs_buildings = FeatureSetByName($datastore, "BuildingFC", ["BlockID", "BuildingID", "BuildingHeight", "BuildingArea"], false) // only select rows with the current feature's BlockID var id = $feature.BlockID var fs_buildings_block = Filter(fs_buildings, "BlockID = @ID") // edit this line for each statistic and field return Min(fs_buildings_block, "BuildingHeight") ... View more

If you're triggering on both Insert and Update, you have to either create 2 rules or take care of your current edit type. In your case, when you move a point, you both update the existing polygon's location and also create a new polygon. your updates array is wrong, I'm surprised that it actually works. For documentation on the Attribute Rule return keywords, go here: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/attribute-rule-dictionary-keywords.htm  You also have to think about what happens if you manually delete a buffer polygon. Then you will get ExceptionErrors, because your code doesn't find the feature, so bufferedFeature will be null, and then you try to call attributes on null, which doesn't work. So you have to include null checks, just like you did for the park feature. Personally, I find it much easier to create and fill the adds, updates, anad deletes array in my code and just use those arrays in the return dict. Makes it much more readable and also easier to write, because you don't have to care about the brackets that much.   So, with all that (switch behavior dependent on edit mode, do null checks, fill the edit arrays inside the code blocks), we end up with something like this: // determine our edit mode ("INSERT", "UPDATE", or "DELETE") var mode = $editcontext.editType // return early if we're updating the $feature and the geometry didn't change var geometry_is_unchanged = Equals(Geometry($feature), Geometry($originalfeature)) if(mode == "UPDATE" && geometry_is_unchanged) { return } // get park feature var fsPark = FeatureSetByName($datastore, "Parks", ["NAME", "ParkID"], false) var fsParkIntersect = Intersects(fsPark, Geometry($feature)) var park = First(fsParkIntersect) // return error if $feature doesn't intersect a park if (park == null) return {"errorMessage": "Point must be in Park."} // create the result dict // we do this here, because we need some of the fields in the edit arrays var result = { "attributes": { "NAME": "Point " + park.NAME, "ParkNAME": park.NAME, "ParkID": park.ParkID } } // initialize the edit arrays for adds, updates, and deletes var adds = [] var updates = [] var deletes = [] // depending on edit type, fill the corresponding array var bufferedGeometry = Buffer($feature, 500) if(mode != "INSERT") { // get the buffer polygon (we don't need that if we're inserting) var globalId = $feature.GlobalID var fsBuffers = FeatureSetbyName($datastore, "TestPolygons", ["GlobalID"], false) var bufferedFeature = First(Filter(fsBuffers, "PointGuid = @globalId")) if(mode == "UPDATE") { if(bufferedFeature == null) { // somehow, there is no buffer polygon (eg we deleted it). // in that case, use the insert code mode = "INSERT" } else { var update = { "globalID": bufferedFeature.GlobalID, "geometry": bufferedGeometry "attributes": {"NAME": result.NAME} } Push(updates, update) } } if(mode == "DELETE") { if(bufferedFeature == null) { // somehow, there is no buffer polygon (eg we deleted it). // in that case, we don't need to edit the buffer polygons, // we can just return return } else { var delete = {"globalID": bufferedFeature.GlobalID} Push(deletes, delete) } } } if(mode == "INSERT") { var add = { "geometry": bufferedGeometry, "attributes": { "PointGuid": $feature.GlobalID, "NAME": result.NAME } } Push(adds, add) } // return return { "result": result, "edit": [ { "className": "TestPolygons", "adds": adds, "updates": updates, "deletes": deletes } ] }   ... View more

When I just use $feature.TextField, it works:   When I use the label style tags, ArcGIS probably switches to HTML, where ampersand is a special character, so the expression breaks in these features (your code): "<FNT name = 'Arial' style = 'Regular' size = '12'>" + $feature.TextField + "</FNT>"     You have to escape the ampersand as an HTML entity: "<FNT name = 'Arial' style = 'Regular' size = '12'>" + Replace($feature.TextField, "&", "&amp;") + "</FNT>"     ... View more

Arcade expressions are only evaluated on command, e.g. when you open a popup when you trigger an attribute rule when you use Arcade in the CalculateField when you show a feature with Arcade in its label or symbology on the map   That means: You can get and set Arcade expressions with the CIM module. You cannot get the expressions' outputs with Python.   For example, Genus, species, common name are all separate fields but are often concatenated for display. I don't need it concatenated in my main data, but for this particular workflow (labelling things), I'd like to have that information. If this is just for labelling, you can just use an expression in the Label Class. You can only access teh $feature, for performance reasons the Arcade Labeling Profile doesn't allow the FeatureSetBy*() functions. But what you want could be as simple as this: var genus = "Genus"// $feature.Genus var species = "Species"// $feature.Species var name = "Common Name"// $feature.CommonName return `${genus} ${species} (${name})`   ... View more

When you test your Arcade expression, it only checks one feature (I think it's the first). So if that feature doesn't intersect a feature of your filtered layer, you will get an empty intersect feature set. Your loop will run 0 times and then the expression will return null. If you call First() on an empty feature set, the result is null, which is why you get the ExecutionError when you try to return null.Field Something like this should do the trick: var filtered_parcels = Intersects(FeatureSetByName($map,"Name of layer with subset of all tax parcels"), $feature); var parcel = First(filtered_parcels) // get the first feature // if filtered_parcels is empty, parcel is null // in that case, return a default value if(parcel == null) { return "No intersecting subset parcel found." } // else return the field value return parcel.NameOfField   When you test that expression, it should show the default result. When you actually open a popup, it should show either the default result or the field of the subset layer, depending on whether there is a subset parcel intersecting the queried feature. ... View more