nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Attribute Rule to Intersect only visable polygons?

amarcz_cc

Hello,

I am attempting to run an Attribute rule that runs an Intersect on a polygon layer with stacked polygons. Think of this as Floor levels of a building.

I am attempting to create an attribute rule that will intersect only the visible features on a map and return the existing value.

My code (arcade) is:

var fs = FeatureSetByName($datastore, "DBO.EAMFacility", ["fullname"])
var fsIntersect = [Intersects(fs, $feature)]
var loc = Back(fsIntersect)
if (fullname == null) return {"errorMessage": "Area not found."}

return loc.fullname

Instead of intersecting layers that are turned on (I'm using definition queries to isolate Assets and Facilities based on Floor level), it is returning the first polygon it encounters.

Any help would be appreciated.

Trouver plus de publications taguées avec

Desktop

Accepted answers

All comments

amarcz_cc

The only issue I am seeing is on Line 5

else if ($feature.FloorNumber == 1){return "something"}

Where I'd want the $feature.FloorName to read the input of the User, then check for a similar attribute in the DBO.EAMFacility fullname field to return a result. Any ideas on how to make that occur?

ZachBodenner

If you have the ability to do that I think it would be a good idea but of course it's not always a given that we can control the data schema.

amarcz_cc

Thanks for your response, I suppose my only issue with adding an IF statement is that the Asset layer, the one I'm attempting to get Facility info into, currently doesn't have FloorNumber field in it. I was attempting to make it as simple as possible so my Staff doesn't have to think about it.

Ideally, when the paired feature classes are turned on in the Web Application (IE: Facilities of City Hall Floor 1 & Assets of City Hall Floor 1) as a grouped Feature Service. When you add a new Asset, it reads the Facilities Room and adds it to the location field.

You may be correct where I have to preload the Asset with that Floor level to get the Attribute rule to identify its location.

ZachBodenner

If you've got definition queries that are working to restrict visibility, I assume you've got good attribute data - that's what I'd rely on in this case. Include a check against an attribute as part of the IF statements. As an example, you might attempt something like:

var fs = FeatureSetByName($datastore, "DBO.EAMFacility", ["fullname"])
var fsIntersect = [Intersects(fs, $feature)]
var loc = Back(fsIntersect)
if (fullname == null) return {"errorMessage": "Area not found."}
else if ($feature.FloorNumber == 1){return "something"}
//etc

return loc.fullname

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.