idea Arcade within() actually queries the feature it is within in Attribute Rules Ideas

Arcade within() actually queries the feature it is within

JonathanMcDowell1 — Wed, 06 Sep 2023 20:45:19 GMT

I am using the within() function to query an underlying feature class. Then calculating fields based on the values pulled from the within(). If the feature is an odd shape it will return nothing or the wrong value. I am using this syntax, within( querylayer ,centroid($feature)). Sometimes the centroid is outside of the feature.

In the image below, the within function is using the red point to query the 31E33AD polygon. I need the function to query the 31E33 polygon using the green point. If I remove the centroid function, within() returns nothing.

Red is the centroid used by the within() function.

My suggestion is to create a function that uses a center point within the selected feature. Or fix the centroid function to place the point within the feature.

Re: Arcade within() actually queries the feature it is within - Status changed to: Needs Clarification

MikeMillerGIS — Wed, 06 Sep 2023 21:01:03 GMT

Have you tried using https://developers.arcgis.com/arcade/function-reference/geometry_functions/#relate

Re: Arcade within() actually queries the feature it is within

JonathanMcDowell1 — Wed, 06 Sep 2023 21:08:20 GMT

I am not sure this will work. I am using the values from one feature class to calculate values of another feature class. In this cause, the is a index feature class storing key values for the parcel layer. I use the attribute rule to pull a value from the index feature class. Then using that value calculate fields in the parcel layer.

If I am understanding the linked documentation, it is just performing a check to see if the features are related.

Re: Arcade within() actually queries the feature it is within

MikeMillerGIS — Wed, 06 Sep 2023 21:15:35 GMT

It used DE-9IM to determine the spatial relationship. You can use https://developers.arcgis.com/arcade/function-reference/geometry_functions/#intersects to get all intersecting points and if you need to ensure it is in your polygon, use related to ensure the point is in and not on the boundary.

Or maybe Intersect is enough for what you are looking for

Re: Arcade within() actually queries the feature it is within

MikeMillerGIS — Wed, 06 Sep 2023 21:16:35 GMT

Sorry, wrong link, try this version of Intersects:

https://developers.arcgis.com/arcade/function-reference/featureset_functions/#intersects

Re: Arcade within() actually queries the feature it is within

JakeSimms1 — Thu, 07 Sep 2023 11:32:36 GMT

@JonathanMcDowell1 is the 31E33 polygon a curved or "moon" shaped feature such as below. When getting geometry of the centroid it is actually outside the feature.

I have run into this issue before and the solution was to create a negative buffer object with the Buffer() function then use that object as the innerGeometry for the Within() function.

Note: I noticed in your first comments you had within( querylayer ,centroid($feature)), this is reversed how you want it. The syntax for within is Within(innerGeometry, outerGeometry). In your case, would the innerGeometry want to be the centroid($feature) and the outerGeometry be the querylayer? within( centroid($feature),querylayer).

Re: Arcade within() actually queries the feature it is within

JonathanMcDowell1 — Thu, 07 Sep 2023 15:38:36 GMT

@JakeSimms1 This is the exact problem I am dealing with. The feature I am working with is a long curving railroad right-of-way. It is 60' wide and 2 miles long. I did try a negative buffer, however it did not move the point close to where it is needed. In this case, the features I am using for the within() are topologically identical. So a within() should work.

Thanks for pointing out the syntax. I will switch the inputs and see what happens.

My next test is to use intersect() with the negative buffer. If I am correct, I want to use the offset() function?

Re: Arcade within() actually queries the feature it is within

JakeSimms1 — Thu, 07 Sep 2023 17:11:54 GMT

@JonathanMcDowell1 You should be able to use the Intersect() to get the field values you need without using Offset().

Code might not be what you're looking for but how you would roughly do it.

var bufferFeature = Buffer($feature,-10)//of some number var fcIntersect = Intersects(FeatureSetByName($datastore, ["featureToIntersect"], ["fieldValue1","fieldValue2"], false), bufferFeature) if (IsEmpty(fcIntersect)){ return; } if (Count(fcIntersect) >= 1) { var select = first(fcIntersect) return { "result": { "attributes": { "field1": select.fieldValue1, "field2": select.fieldValue2 } } } }

Re: Arcade within() actually queries the feature it is within

JonathanMcDowell1 — Thu, 07 Sep 2023 17:50:17 GMT

@JakeSimms1 is exactly what I want to do. However, it throws an error when I try saving it. The error states the expression for line 2 is invalid. It cannot preform the function on an empty geometry.

Re: Arcade within() actually queries the feature it is within

HNTZK46 — Thu, 07 Sep 2023 20:56:42 GMT

Hi @JonathanMcDowell1 ,

I may be wrong but the error thrown is because the "false" in the line 2.

Change the "false" to "true" like this:

var fcIntersect = Intersects(FeatureSetByName($datastore, ["featureToIntersect"], ["fieldValue1","fieldValue2"], true), bufferFeature)

Re: Arcade within() actually queries the feature it is within

JonathanMcDowell1 — Fri, 08 Sep 2023 15:49:50 GMT

Esri nees to add an 'inside' parameter to the centroid() function, for example, centroid($feature, 'inside'). This addition has the potential to save developers a lot of time tryting to code around the problem.

Re: Arcade within() actually queries the feature it is within

DeanAnderson2 — Sat, 23 Sep 2023 12:51:21 GMT

The following code uses intersect and gets the largest intersecting polygon to make the assignment. It appears to be an OK workaround.

// Get map number from mapindex polygon layer using interesect
// Do interesect and county features.

var fsMapIndex = FeatureSetByName($datastore,"MapIndex",["MapNumber","ORMapNum","County"])
var fsIntersectMap = Intersects(fsMapIndex,$feature)
var MapIndex = first(fsIntersectMap)
var intcount = Count(fsIntersectMap)

// If no features return error

if (MapIndex == null) return {"errorMessage": "No Map Index Feature Found"}
if (MapIndex.Mapnumber == null) return {"errorMessage": "MapNumber is empty"}

// If count is one then return values

if (intcount == 1) return {
"result": {
"attributes" :{
"MapNumber" : MapIndex.MapNumber,
"ORMapNum" : MapIndex.ORMAPNum,
"County" : MapIndex.County
}
}
}

// if county > 1 (taxlot overlaps mapindex) then
// loop thru and keep intersect with largest area.

else {
var MapNumber = " "
var ORMAPNum = " "
var County = 0
var intersectarea = 0
for (var f in fsIntersectMap){
var newintersectarea = Area(Intersection($feature,f))
if (newintersectarea > intersectarea){
var MapNumber = f.MapNumber
var ORMAPNum = f.ORMAPNum
var County = f.County
intersectarea = newintersectarea}
}

return {
"result": {
"attributes" :{
"MapNumber" : MapNumber,
"ORMapNum" : ORMAPNum,
"County" : County
}
}
}
}

Re: Arcade within() actually queries the feature it is within

MikeMillerGIS — Mon, 25 Sep 2023 12:38:45 GMT

Do not call Count and First on the FeatureSet. This will cause unnecessary database queries. Just loop over the featureset and handle if the results are empty(none) and get the largest.

Re: Arcade within() actually queries the feature it is within

DeanAnderson2 — Mon, 25 Sep 2023 12:43:56 GMT

Thanks - that makes sense. Built this off of old code and was just pretty focused on making the area check work.

Re: Arcade within() actually queries the feature it is within

DeanAnderson2 — Mon, 25 Sep 2023 12:52:54 GMT

Better code - Again Thanks !

// Get map number from mapindex polygon layer
var fsMapIndex = FeatureSetByName($datastore,"MapIndex",["MapNumber","ORMapNum","County"])
var fsIntersectMap = Intersects(fsMapIndex,$feature)

if (fsIntersectMap == null) return {"errorMessage": "No Map Index Feature Found"}

var MapNumber = "None"
var ORMAPNum = "None"
var County = 99
var intersectarea = 0
for (var f in fsIntersectMap){
var newintersectarea = Area(Intersection($feature,f))
if (newintersectarea > intersectarea){
var MapNumber = f.MapNumber
var ORMAPNum = f.ORMAPNum
var County = f.County
intersectarea = newintersectarea}
}

return {
"result": {
"attributes" :{
"MapNumber" : MapNumber,
"ORMapNum" : ORMAPNum,
"County" : County
}
}
}

Re: Arcade within() actually queries the feature it is within

MikeMillerGIS — Mon, 25 Sep 2023 13:08:43 GMT

Looking good, just a little clean up

No reason to check the FS for null. Think of a FS as a database cursor. Just cycle over it and check if the results are null afterwards

Declare your variables outside the loop

// Get map number from mapindex polygon layer var fsMapIndex = FeatureSetByName($datastore, "MapIndex", ["MapNumber", "ORMapNum", "County"]) var fsIntersectMap = Intersects(fsMapIndex, $feature) var MapNumber = null; var ORMAPNum = null; var County = null; var intersectarea = 0 var newintersectarea for (var f in fsIntersectMap) { newintersectarea = Area(Intersection($feature, f)) if (newintersectarea > intersectarea) { MapNumber = f.MapNumber ORMAPNum = f.ORMAPNum County = f.County intersectarea = newintersectarea } } if (MapNumber == null) { return { "errorMessage": "No Map Index Feature Found" } } return { "result": { "attributes": { "MapNumber": MapNumber, "ORMapNum": ORMAPNum, "County": County } } }

Re: Arcade within() actually queries the feature it is within

DeanAnderson2 — Mon, 25 Sep 2023 13:09:43 GMT

Thanks! Always good to have somebody cleanup my code. Much appreciated.