Latest Contributions by JohannesLindner

There are no syntax errors, so this error message is somewhat perplexing. There are however other problems with your expression: You say you want to return the x coordinate, but you actually return the y coordinate. x is index 0. You calculate the vertex count of the whole multipart geometry and then return that index from the first part. That works for singlepart features, but it will give an error for multipart features, as vertex_count will be greater that the length of the first part. You can do it with a single line: // no need to convert to Dictionary, you can just call paths // index -1 gets the last element of an array. paths[-1][-1] gets the last point of the last part. return Geometry($feature).paths[-1][-1].x   Try this expression. If the error still occurs, try setting the rule manually. ... View more

There are two basic ways of doing this:   Use a query This would be easier if the lots had a common attribute. But for so few features, you can also use the unique key of the lots (like a parcel id or object id or globalid).  open the layer's property pane (double click or right click -> Properties) switch to Definition Query click on New definition query choose your key field, "includes the values", and then write in or select the values of your lots.   Make a local copy You couldn't delete stuff in the layer, because you don't have thte persmission to do so. Imagine everyone being allowed to insert, change, or delete lots... But if you make a local copy, you can then delete everything you don't need. Righ click -> Data -> Export Features   By default, it will save into the ArcGIS Project's default geodatabase. If you want to save as a Shapefile (.shp), choose a folder. Type in a name, click OK.   Make ... View more

completed_surveys is a Featureset, a collection of features. You can only call the field name on single features. So you have to extract a feature from the featureset. One way to do it: var completed_surveys = ... // just get the first feature var survey = First(completed_surveys) // we have to check that survey is not null, else we would produce an error // by calling a member property of null if(survey == null) { Console("survey is null -> completed_surveys is empty") } else { Console(survey.job_wo) } ... View more

Without a relationship class, you have to do the filtering yourself: // load the permit table var all_permits = FeatureSetByPortalItem(...) // get the permits that belong to the parcel var parcel_id = $feature.GlobalID var parcel_permits = Filter(all_permits, "ParcelID = @parcel_id") // return a default value if no permits were found if(First(parcel_permits) == null) { return "No permits found for this parcel" } // build your output var output = [] for(var p in parcel_permits) { var line = `Permit ${p.PermitNumber}, issued on ${p.PermitDate} to ${p.PermitOwner}` Push(output, line) } // conctenate and return return Concatenate(output, TextFormatting.NewLine) ... View more

If a number is used for a feature in a class and then that feature is deleted, when a new feature is inserted does that number get reused or is it burned, and the next unused number comes up? The database sequence doesn't know and doesn't care about where its values are used. All it does is count up when you say so. So when you delete and then insert a feature, the sequence will count up. Just to clarify: The number isn't "burned", and the next number isn't "unused". These concepts would imply that the sequence has knowledge of where the values are used. It does not have that knowledge. It counts up.   can the sequence be used in 'Calculate Field'? Yes.   Personally, my unique key rules look like this: // Calculation rule on the key field // triggers: Insert, Update // if the key field is empty, get the next value of the sequence // else return what's already in there return IIF($feature.KeyField == null, NextSequenceValue("SequenceName"), $feature.KeyField)   ... View more

It's probably doable with some tool (eg GenerateNearTable and then joining the output to the inputs somehow), but you can also rig up a quick script like this: in_features = "Points" # distance field will be added to this fc near_features = "Polygons" in_key = "polygon_id" near_key = "id" distance_field = "DISTANCE" # read near_features as dictionary {key: geometry} near_geometries = {key: shp for key, shp in arcpy.da.SearchCursor(near_features, [near_key, "SHAPE@"])} # add field to in_features arcpy.management.AddField(in_features, distance_field, "DOUBLE") # calculate with arcpy.da.UpdateCursor(in_features, [in_key, distance_field, "SHAPE@"]) as cursor: for key, dist, shp in cursor: try: dist = shp.distanceTo(near_geometries[key]) except KeyError: dist = None print(f"key {key} could not be found in {near_features}.") cursor.updateRow([key, dist, shp])   ... View more

<a href="{Website}" target="_blank">{Website}</a> ... View more