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; } } }

How to nest Arcade If statements

NaomiBegg2

I am working through a loop of intersecting layers, in which I want to choose the largest value.

I have tried to use create a list of numbers using += . This worked fine when I was using a combo of text and numbers, but because I am now just looking at numbers it sums the values, == replaces the values. I could not see how to make a list which I could then use the MAX function with.

My next attempt was to nest an if statement so that I am only getting the largest number out but I have an illegal return statement.

Below is an example of what I am currently doing.

var intersectLayer = Intersects(FeatureSetByName($map, "layer"), $feature)
var Zones = "";
var Zones1 = "";
for (var f in intersectLayer){
   if(Zones == ""){
      Zones = f.Shape__Area
   } else {
   Zones1 = f.Shape__Area
      if (Zones < Zones1){
      Zones == Zones1
      }else{
      Zones1 == ""
      }
}
}

Xander Bakker‌ Is this something you can help me with? I'm expecting there to be a much easier way then I have thought of yet.

Najděte více příspěvků označených jako

Accepted answers

XanderBakker

Hi Naomi Begg ,

According to what I see in your script you intersect with a single layer (is it really called "Layer" in your map?) and you loop through the intersected feature to determine the largest area (this is the largest area of the polygon, not the largest area of the overlap with the intersecting polygon). If that is the case, I assume you could do something like this:

<SPAN class="keyword token">var</SPAN> intersectLayer <SPAN class="operator token">=</SPAN> <SPAN class="token function">Intersects</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="token function">FeatureSetByName</SPAN><SPAN class="punctuation token">(</SPAN>$map<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"layer"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">,</SPAN> $feature<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
<SPAN class="keyword token">var</SPAN> max_area <SPAN class="operator token">=</SPAN> <SPAN class="number token">0</SPAN><SPAN class="punctuation token">;</SPAN>

<SPAN class="keyword token">for</SPAN> <SPAN class="punctuation token">(</SPAN><SPAN class="keyword token">var</SPAN> f <SPAN class="keyword token">in</SPAN> intersectLayer<SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">{</SPAN>
    <SPAN class="keyword token">if</SPAN> <SPAN class="punctuation token">(</SPAN>f<SPAN class="punctuation token">.</SPAN>Shape__Area <SPAN class="operator token">></SPAN> max_area<SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">{</SPAN>
        max_area <SPAN class="operator token">=</SPAN> f<SPAN class="punctuation token">.</SPAN>Shape__Area<SPAN class="punctuation token">;</SPAN>
   <SPAN class="punctuation token">}</SPAN>
<SPAN class="punctuation token">}</SPAN>

<SPAN class="keyword token">return</SPAN> max_area<SPAN class="punctuation token">;</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

All comments

XanderBakker

HI Naomi Begg ,

So you are right the $map is not available in the field calculation.

However, $datastore is. Have a look below.

Error when using $map in the field calculation:

But, using $datastore it will work (if your data reside in the same datastore😞

XanderBakker

Hi njbegg ,

Strange, this should work in Pro in the Field Calculation too. I will do a simple test when I have a moment and post back my findings.

XanderBakker

Hi Naomi Begg ,

On one hand I totally agree. I would be very interesting to be able to use these functions in the symbology profile. On the other hand, I can imagine that when a complex expression has to be executed for each feature that is being drawn every time you zoom or pan your map, this would seriously affect the rendering time.

I am not a fan of using IE. I prefer Chrome or Firefox or if nothing else is available, Edge. This might well be due to limitations of IE as a browser. In case you can, you should move away from IE, since it is the worst browser I have worked with.

XanderBakker

Hi Naomi Begg ,

If you layer is really called "NZParcels_Enviornment_Identity4", it should be used in the Arcade expression. In that case line 1 would become:

<SPAN class="keyword token">var</SPAN> intersectLayer <SPAN class="operator token">=</SPAN> <SPAN class="token function">Intersects</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="token function">FeatureSetByName</SPAN><SPAN class="punctuation token">(</SPAN>$map<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"NZParcels_Enviornment_Identity4"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">,</SPAN> $feature<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

NaomiBegg2

Xander Bakkerhow do I populate a field with this query? I am wanting to symbolise using it, but I also want to be able to view it in a table in Pro. I've tried to build the query in the symbol query builder, and I have tried to use it in the Calculate Field tool in Pro. Both seem to be upset with the use of $map,"layer" within the intersect query.

NaomiBegg2

I just wish that I could now use this as a query to symbolise a layer. It is frustrating that the attribute expressions are viewable for popup information but you have to build it from scratch if you want to use that as a symbol field - plus it doesn't seem to allow for the intersect with another layer (featuresetbyname is not available).

As a side question, why does Arcade in popups not work when viewing in IE browsers?

NaomiBegg2

Thanks Xander

After spending most of a day looking at it I had definitely over complicated the solution!

"Layer" is actually called NZParcels_Enviornment_Identity4 A horrible name after a handful of attempts of figuring out the best way to look at our enviornmens layer in the context of parcels.

XanderBakker

Hi Naomi Begg ,

<SPAN class="keyword token">var</SPAN> intersectLayer <SPAN class="operator token">=</SPAN> <SPAN class="token function">Intersects</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="token function">FeatureSetByName</SPAN><SPAN class="punctuation token">(</SPAN>$map<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"layer"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">,</SPAN> $feature<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
<SPAN class="keyword token">var</SPAN> max_area <SPAN class="operator token">=</SPAN> <SPAN class="number token">0</SPAN><SPAN class="punctuation token">;</SPAN>

<SPAN class="keyword token">for</SPAN> <SPAN class="punctuation token">(</SPAN><SPAN class="keyword token">var</SPAN> f <SPAN class="keyword token">in</SPAN> intersectLayer<SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">{</SPAN>
    <SPAN class="keyword token">if</SPAN> <SPAN class="punctuation token">(</SPAN>f<SPAN class="punctuation token">.</SPAN>Shape__Area <SPAN class="operator token">></SPAN> max_area<SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">{</SPAN>
        max_area <SPAN class="operator token">=</SPAN> f<SPAN class="punctuation token">.</SPAN>Shape__Area<SPAN class="punctuation token">;</SPAN>
   <SPAN class="punctuation token">}</SPAN>
<SPAN class="punctuation token">}</SPAN>

<SPAN class="keyword token">return</SPAN> max_area<SPAN class="punctuation token">;</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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