Latest Contributions by JohannesLindner

In which table do you want to create the validation rule? ... View more

It's possible, just a little more complicated. Instead of getting the First() intersecting feature, you need to get all of them, and then get the one with the greatest intersection length / area. // load the other featureset var fs = FeatureSetByName($datastore, "Highways.HIGHWAYMGR.ElectoralDivisions") // get all features from fs that intersect the current $feature var i_fs = Intersects(fs, $feature) // find the ElectDiv of the feature with the greatest intersection with $feature var greatest = 0 var electdiv = null for(var i_f in i_fs) { var current = Length(Intersection($feature, i_f)) if(current <= greatest) { continue } greatest = current electdiv = i_f.ElectDiv } return electdiv   If both featuresets ($featureset and fs) are polygon fcs, you should use Area() instead of Length() in line 9. ... View more

How should the extraced value look? Do you want the id of the closest feature, no matter if it's a point or line? Or do you want something like "closestpoint.id, closestline.id"   Things I noticed at a first glance: GYinspIntersection and GYfeaturesWithDistances are not defined Buffer and Distance have a unit attribute that takes the following values: feet | kilometers | miles | nautical-miles | meters | yards. You supply "m". I haven't tested if that works as replacement for "meters", but it's best to avoid undocumented features. Your null check is the wrong way around. Either check for !IsEmpty(...) (is not empty) or swap lines 37 and 40. ... View more

To post code:     Overlaps takes two geometries/features as arguments. You are trying to run it with two featuresets. You have to get the intersecting features first, then loop over those features and test if they overlap the current $feature. // get all polygons that are intersected by the current feature var fs_polygons = FeaturesetByName($datastore, "HydrographySrf", ["*"], true) var i_polygons = Intersects($feature, fs_polygons) // loop over those polygons for(var i_poly in i_polygons) { // if the polygon overlaps the current feature if(Overlaps($feature, i_poly)) { return false } } return true   ... View more

Oh wow, I somehow never knew about this... Time to break some apps while trying to fix some insignificant details... ... View more

Arcade is your friend here.   // extract the line's start and end points var start_point = Geometry($feature).paths[0][0] var end_point = Geometry($feature).paths[-1][-1] // load the point fc var point_fc = FeaturesetByName($datastore, "TestPoints", ["TextField"], false) // get the intersecting points' names var i_start = First(Intersects(start_point, point_fc)) var i_end = First(Intersects(end_point, point_fc)) var names = [ IIf(i_start == null, "", i_start.TextField), IIf(i_end == null, "", i_end.TextField), ] // concatenate and return return Concatenate(names, "")     Change the names of the point fc and the name field in lines 6, 12, and 13. You can use this expression in the field calculator (switch to Arcade) or in an Attribute Rule.     ... View more

Hey, welcome to the Community! What product are you working with? ArcGIS Pro? Is this a one-time operation or do you need that to calculate automatically? ... View more

You iterate over the csv file, but arcpy expects you to iterate over the UpdateCursor. Are you sure UpdateCursor is what you need? It seems like you could actually want InsertCursor. ... View more

While you won't get around doing things manually, you can at least make it easier.   Label your features with the area That way you don't have to switch tools. The label won't update while you modify vertices, so you still have to complete the edit before seeing the new area. Use a label expression like this: Round(Area($feature, "square-meters"), 2) + " m²"     Use Attribute Rules Create a new double field in you polygon feature class. This field will store the target area. Create an Attribute Rule for your polygon feature class. Use this expression (use the new field's name in line 7!): // Calculation Attribute Rule // field: Shape // Triggers: Insert, Update // if you did not specify a target area, return the current geometry var target_area = $feature.DoubleField if(target_area == null) { return Geometry($feature) } // these two parameters specify how close the rule will get to your target area // the rule will keep on trying to get to your target area until one condition is met: // either the relative error (target-current)/target drops below max_rel_error // or the number of tries goes above max_iter. // at that point, the rule returns the current try. // decreasing max_rel_error and increasing max_iter returns better results, but it takes much more time. var max_rel_error = 0.001 var max_iter = 200 var current_geometry = Geometry($feature) var rel_error = (target_area - Area(current_geometry, "square-meters")) / target_area for(var iter = 0; iter < max_iter; iter++) { current_geometry = Buffer(current_geometry, rel_error, "meters") rel_error = (target_area - Area(current_geometry, "square-meters")) / target_area if(Abs(rel_error) <= max_rel_error) { break } } return current_geometry   The workflow would be something like this: create a rough outline of where you want the trees to be   Change the value of your target area field (DoubleField in my test data). The rule triggers and tries to get the polygon as close to the target area as possible.   Delete the target area value. That hinders the rule from constantly changing you polygon in the next step. Use the Edit Vertices tool to iteratively change vertices until you hit your target area. Remember, the label isn't updated while you drag a vertex, so you will have to complete the edit to see the new area.   ... View more