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

Gebruik van FeatureSetBy-functies in Arcade om door te klikken naar andere lagen en tabellen

XanderBakker

<\/HEAD>

Vandaag werd een geweldige blog gepost door Paul Barker<\/A> over de nieuwe FeatureSet-functies: Wat is er nieuw met Arcade: Een wandeling door FeatureSets (Deel 1)<\/A> en ook Kelly Gerrow<\/A> deelde een geweldig document over dit onderwerp: https:\/\/community.esri.com\/community\/gis\/web-gis\/arcgisonline\/blog\/2018\/12\/10\/overlapping-features-in-pop-ups-quick-introduction-to-using-featuresets-with-arcade<\/A> . <\/P>

<\/P>

Ik wilde niet achterblijven, dus ik dacht dat ik wat voorbeelden zou delen met hydranten, de onderhoudsgeschiedenis en sub sectoren en hydraulische sectoren om te laten zien wat je kunt bereiken met de nieuwe Arcade-functies die op 5 december in ArcGIS Online zijn uitgebracht.<\/P>

<\/P>

Stel dat we een webkaart hebben met verschillende lagen en een tabel:<\/P>

<\/P>

Hidrantes<\/EM> is een puntlaag met hydranten<\/LI>Sub Sector<\/EM> is een polygoonlaag met een onderverdeling van het interessegebied<\/LI>Sector Hidraulico<\/EM> is een polygoonlaag die sub sectoren samenvoegt tot hydraulische sectoren<\/LI>Hist Mantenimiento<\/EM> is een tabel met de historische onderhoudsgegevens voor elke hydrant<\/LI><\/UL><\/P>Allereerst passen we wat Arcade toe om de hydranten te visualiseren op basis van hun leeftijd. Dit was al mogelijk in de vorige release, dus hier nog geen nieuwe dingen. We hebben de installatiedatum opgeslagen in het veld FECHAINSTALACION en we kunnen de DateDiff<\/EM> en Now<\/EM> functies gebruiken om de leeftijd in jaren te bepalen, wat gebeurt in de eerste twee regels. Daarna classificeren we de waarde in significante bereiken:<\/P>var<\/ fecha_inst =<\/ $feature.<\/FECHAINSTALACION;<\/ var<\/ edad =<\/ DateDiff<\/(Now<\/()<\/, fecha_inst, "years"<\/);<\/ var<\/ clase_edad =<\/ ""<\/;<\/ if<\/ (<\/edad ><\/ 50<\/) {\n clase_edad =<\/ "Ouder dan 50 jaar"<\/;\n} else if (edad > 40) {\n clase_edad = "Tussen 40 en 50 jaar";\n} else if (edad > 30) {\n clase_edad = "Tussen 30 en 40 jaar";\n} else if (edad > 20) {\n clase_edad = "Tussen 20 en 30 jaar";\n} else if (edad > 10) {\n clase_edad = "Tussen 10 en 20 jaar";\n} else if (edad > 5) {\n clase_edad = "Tussen 5 en 10 jaar";\n} else {\n clase_edad = "Jonger dan 5 jaar";\n}\nreturn clase_edad;<<EMOJI_0><<EMOJI_1><<EMOJI_2><<EMOJI_3><<EMOJI_4><<EMOJI_5><<EMOJI_6><<EMOJI_7><<EMOJI_8><<EMOJI_9><<EMOJI_10><<EMOJI_11><<EMOJI_12><<EMOJI_13><<EMOJI_14><<EMOJI_15><<EMOJI_16><<EMOJI_17><<EMOJI_18><<EMOJI_19>
Het resultaat is een tekst die de leeftijd beschrijft, waarvoor we representatieve symbolen kunnen definiëren (hier met behulp van de Firefly-symbolen):

Geen opvallende symbolen voor de andere twee polygoonlagen om te voorkomen dat de aandacht wordt afgeleid van de hydranten.

We willen in het pop-upvenster van elke hydrant graag de lijst tonen van alle onderhoud dat aan de hydrant is uitgevoerd. Zowel de onderhoudsgeschiedenistabel als de hydrantlaag bevatten het ID van de hydrant. De tabel bevat ook de data en het type onderhoud.

In de configuratie van de pop-up van de hydranten kunnen we een Arcade-expressie toevoegen zoals deze:

var tbl = FeatureSetByName($datastore,"Hist_Mantenimiento");
var codigo = $feature["COD_HIDRANTE"];
var sql = "COD_HIDRANTE = '" + codigo + "'";
Console(sql);
var mantenimientos = Filter(tbl, sql);
var cnt = Count(mantenimientos);
var historia = "";
if (cnt > 0) {
   historia = cnt + " Onderhoud(s):";
     <SPAN class="keyword token">voor</SPAN> <SPAN class="punctuation token">(</SPAN><SPAN class="keyword token">var</SPAN> mantenimiento <SPAN class="keyword token">in</SPAN> mantenimientos<SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">{</SPAN>
      <SPAN class="keyword token">var</SPAN> txt_fecha <SPAN class="operator token">=</SPAN> <SPAN class="token function">Text</SPAN><SPAN class="punctuation token">(</SPAN>mantenimiento<SPAN class="punctuation token">.</SPAN>Fecha_Mantenimiento<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">' - (Y/MM/DD) '</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
      <SPAN class="keyword token">var</SPAN> txt_man <SPAN class="operator token">=</SPAN> txt_fecha <SPAN class="operator token">+</SPAN> mantenimiento<SPAN class="punctuation token">.</SPAN>Mantenimiento<SPAN class="punctuation token">;</SPAN>
      historia <SPAN class="operator token">+=</SPAN> TextFormatting<SPAN class="punctuation token">.</SPAN>NewLine <SPAN class="operator token">+</SPAN> txt_man<SPAN class="punctuation token">;</SPAN>
   <span class="punctuation token">}</span>
<span class="punctuation token">}</span> <span class="keyword token">anders</span> <span class="punctuation token">{</span>
   historia <span class="operator token">=</span> <span class="string token">"Geen onderhoud"</span><span class="punctuation token">;</span>
<span class="punctuation token">}</span>

<span class="keyword token">return</span> historia<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>‍</span><span>‍</span><span>‍</span><span>‍</span><span>‍</span><span>‍</span><span>‍</span><span>‍</span><span>‍</span></span>

Eerst openen we de tabel met de onderhoudsgeschiedenis en wijzen deze toe aan een variabele tbl. Vervolgens lezen we de id van de huidige brandkraan waarvoor we de pop-up willen maken. We definiëren een SQL-expressie met behulp van de hydrant ID die vervolgens wordt gebruikt om de geschiedenis tabel te filteren. Het resultaat wordt opgeslagen in een variabele genaamd mantenimientos. We kunnen een Count doen om het aantal onderhoudsbeurten aan de brandkraan te verkrijgen. Als de count (cnt) groter is dan 0, beginnen we met het uitlezen van de details en construeren we een lijst van onderhoud inclusief de datum en het type onderhoud.

Het resultaat zal er zo uitzien nadat we een eenvoudige aangepaste html hebben geconfigureerd om de attributen en het resultaat van de Arcade-expressie in de pop-up te tonen:

Laten we nu verder gaan met het gebruiken van deze nieuwe Arcade-functies om wat data over brandkranen op subsectorniveau te krijgen. Aangezien het aantal onderhoudsbeurten uiteraard afhangt van de leeftijd van de brandkraan, zou het fijn zijn om hier wat details over te krijgen op subsectorniveau.

In de pop-up configuratie van de sub sectoren kunnen we de volgende Arcade-expressie toevoegen:

<SPAn class="keyword token">var</SPAn> fs <SPAn class="operator token">=</SPAn> <SPAn class="token function">FeatureSetByName</SPAn>( $datastore , "Hidrantes" ) ;
<SPAn class="keyword token">var</SPAn> hidrantes <SPAn class="operator token">=</SPAn> <SPAn class="token function">Intersects</SPAn>( fs , $feature ) ;
<SPAn class="keyword token">var</SPAn> cnt <SPAn class="operator token">=</SPAn> <SPAn class="token function">Count</SPAn>( hidrantes ) ;

<SPAn class="keyword token">var</SPAn> edad_tot <SPAn class="operator token">=</SPAn> 0 ;
<SPAn class="keyword token">voor</SPAn>( <SPAn class="keyword token">var</SPAn> hidrante <SPAn class="keyword token">in</SPAn> hidrantes ) {
    <SPAn class="keyword token">var</SPAn> edad <SPAn class="operator token">=</SPAn> <SPAn class="token function">DateDiff</SPAn>( <SPAn class="token function">Now</SPAn>( ), hidrante.FECHAINSTALACION , "years" ) ;
    edad_tot += edad ;
}

<SPAn class="keyword token">var</SPAn> resultado <SPAn class="operator token">=</SPAn> "" ; 
<SPAn class="keyword token">als</SPAn>( cnt > 0 ) {
    <SPAn class="keyword token">var</SPAn> edad_media <SPAn class="operator token">=</SPAn> edad_tot / cnt ;
    resultado = "Er zijn " + cnt + " brandkranen in de sub sector" ;
    resultado += TextFormatting.NewLine + "De gemiddelde leeftijd van de brandkranen is " + Round( edad_media , 2 ) + " jaar" ;
} anders {
    resultado = "Er zijn geen brandkranen in de sub sector" ;
}

<span class='keyword'>return</span> resultado;<br>
<spanclass='line-numbers-rows'><spanspan><<EMOJI_19>></spanspan><<EMOJI_20>><<EMOJI_21>><<EMOJI_22>><<EMOJI_23>><<EMOJI_24>><<EMOJI_25>><<EMOJI_26>><<EMOJI_27>><<EMOJI_28>><<EMOJI_29>><<EMOJI_30>><<EMOJI_31>><<EMOJI_32>><<EMOJI_33>><<EMOJI_34>><<EMOJI_35>><<EMOJI_36>><<EMOJI_37>><<EMOJI_38>></spanspan></PRE><P></P><P>DDeze expressie zal:<br><ul><li>Aanroepen van de laag Hydrants<br><li>EEN intersect uitvoeren met het huidige sub sector object<br><li>Tellen hoeveel brandkranen er in de sub sector zijn<br><li>Berekent voor elke brandkraan de leeftijd en telt alle leeftijden op<br><li>Berekent de gemiddelde leeftijd van de brandkranen en formatteert de tekst met deze informatie<br><ul><P></P><P></P><P>PHet resultaat zal er zo uitzien:<br><P></P><P>&nbsp;<img alt='' src='https://us.v-cdn.net/6038851/uploads/legacyfs/online/431475_pastedImage_15.png' /></p><P>PIn dit geval zijn er 93 brandkranen in de sub sector en is de gemiddelde leeftijd 20,64 jaar.<br><P>PDit is leuk, maar kunnen we ook de namen tonen van de sub sectoren die worden omvat door een hydraulische sector met behulp van deze nieuwe Arcade functies? Het antwoord is ja. Laten we volgende expressie toevoegen aan hydraulische sectoren:<br><P></P><P>&nbsp;<pre style='white-space: pre-wrap;'>var fs = FeatureSetByName($datastore, "Sub Sector");
var subsectores = Intersects(fs, $feature);
var cnt = Count(subsectores);

var resultado = "Lijst van de " + cnt + " Subsectoren:";
<span>  class="keyword token">voor<\/SPAN> <SPAN class="punctuation token">(<\/SPAN><SPAN class="keyword token">var<\/SPAN> subsector <SPAN class="keyword token">in<\/SPAN> subsectores<SPAN class="punctuation token">)<\/SPAN> <SPAN class="punctuation token">{<\/SPAN>
&nbsp;&nbsp;&nbsp; resultaat <SPAN class="operator token">+<\/SPAN><SPAN class="operator token">=<\/SPAN> TextFormatting<SPAN class="punctuation token">.<\/SPAN>NewLine <SPAN class="operator token">+<\/SPAN> subsector<SPAN class="punctuation token">.<\/SPAN>IDSAP<SPAN class="punctuation token">;<\/SPAN>
<SPAN class="punctuation token">}<\/SPAN>

<SPAN class="keyword token">return<\/SPAN> resultaat<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><\/CODE><\/PRE><P><\/P><P>Toegang krijgen tot de sub sectoren laag en Intersect met het huidige hydraulische sector en voila, toch? Nee, niet zo juist. Wanneer je een Intersect gebruikt tussen twee polygonen lagen, zal het waarschijnlijk te veel features teruggeven vanwege het feit dat wanneer twee polygonen een overeenkomende grens hebben, ze waarschijnlijk in het resultaat worden opgenomen, wat leidt tot meer sub sectoren dan we willen.<\/P><P><\/P><P>Een manier om dit te vermijden is door een kleine negatieve buffer te gebruiken op de hydraulische sector en de Intersect uit te voeren met die gebufferde geometrie zoals dit:<\/P><PRE class="lia-code-sample line-numbers language-none"><CODE><SPAN class="keyword token">var<\/SPAN> fs <SPAN class="operator token">=<\/SPAN> <SPAN class="token function">FeatureSetByName<\/SPAN><SPAN class="punctuation token">(<\/SPAN>$datastore<SPAN class="punctuation token">,<\/SPAN><SPAN class="string token">"Sub Sector"<\/SPAN><SPAN class="punctuation token">)<\/SPAN><SPAN class="punctuation token">;<\/SPAN>
<SPAN class="keyword token">var<\/SPAN> feature_buf <SPAN class="operator token">=<\/SPAN> <SPAN class="token function">Buffer<\/Span>(<$feature>, -100, 'meters');
<span class="keyword token">var</span> subsectores = Intersects(fs, feature_buf);
<span class="keyword token">var</span> cnt = Count(subsectores);

<span class="keyword token">var</span> resultaat = "Listado de los " + cnt + " Subsectores:";
<span class="keyword token">voor</span> (<span class="keyword token">var</span> subsector <span class="keyword token">in</span> subsectores) {
&nbsp;&nbsp;&nbsp; resultaat += TextFormatting.NewLine + subsector.IDSAP;
}

<span class="keyword token">return</span> resultaat;
<span class="line-numbers-rows"><span><<EMOJI_10>></span><span><<EMOJI_11>></span><span><<EMOJI_12>></span><span><<EMOJI_13>></span><span><<EMOJI_14>></span><span><<EMOJI_15>></span><span><<EMOJI_16>></span><span><<EMOJI_17>></span><span><<EMOJI_18>></span><span><<EMOJI_19>></span></span>

Let op de Buffer met een negatieve afstand die wordt gemaakt op regel 2 en gebruikt op regel 3 om de juiste polygonen te krijgen.

De resulterende pop-up zal er zo uitzien:

Eerlijk gezegd vind ik de ongesorteerde lijst van sub sectoren niet leuk, dus laten we deze lijst ordenen met behulp van OrderBy:

var fs = FeatureSetByName($datastore, "Sub Sector");
var feature_buf = Buffer($feature, -100, 'meters');
var subsectores = OrderBy(Intersects(fs, feature_buf), 'IDSAP ASC');
var cnt = Count(subsectores);

var resultaat = "Listado de los " + cnt + " Subsectores:";
voor (var subsector in subsectores) {
&nbsp;&nbsp;&nbsp; resultaat += TextFormatting.NewLine + subsector.IDSAP;
}

return resultaat;
<span class="line-numbers-rows"><span><<EMOJI_21>></span><span><<EMOJI_22>></span><span><<EMOJI_23>></span><span><<EMOJI_24>></span><span><<EMOJI_25>></span></span>

Wat zal resulteren in een gesorteerde lijst van sub sectoren:

Ik hoop dat deze voorbeelden je zullen helpen te begrijpen wat mogelijk is met Arcade met de laatste update in ArcGIS Online, maar voordat je erin duikt en begint met het maken van fantastische Arcade expressies wil ik even Uncle Ben (Spider-Man) citeren:

Met grote kracht komt grote verantwoordelijkheid...

Zoals Paul Barker vermeldt in zijn blog, wees voorzichtig en valideer altijd dat de prestaties van je expressies resulteren in een acceptabele reactietijd voor je eindgebruiker.

Vind meer berichten getagd met

Reacties

ChrisMartin8

Hi @XanderBakker

This post has been super helpful. I've read through it and all the comments. I have a very similar use case but need a slightly different output.

I have a polygon layer of buildings and a table of category codes that are included in a relationship class. The field that links them is an ID field which is called "UID" in the buildings layer and "UID_Child" in the category code table. I am trying to edit my output so that in the case of multiple occurrences of the same category code within one building, that code would be listed once along with a count of how many times it occurs, rather than listing duplicate codes. Here's my current code:

//identify related table data
var related_table = FeatureSetById($datastore, "11");

//filter relate table for records matching unique ID
var filter_query = "UID_Child = '" + $feature["UID"] + "'";
Console('filtering related data records')
var related_data_filtered = Filter(related_table, filter_query);

//count records matching UID in related table 
var related_data_filtered_count = Count(related_data_filtered);
var output = []
Console('records filtered: '+ related_data_filtered_count)

//push catcode value from related data table to output 
if (related_data_filtered_count > 0) {
  for (var related_data_row in related_data_filtered) {
    Push(output, related_data_row.CATCODE)
  }
} else {
  return "No Related Records."
}
Console(output)

And here's what the popup looks like:

So for this feature for example, I would want it to read "610112 (10 or however many times it occurs)" I think I need to use a for loop to count how many times each catcode occurs. I've tried a ton of different variations with no success. I'll put one sample below. Do you have any ideas?

var filter_query = "UID_Child = '" + $feature["UID"] + "'";
var related_data_filtered = Filter($datastore["11"], filter_query);
var related_data_filtered_count = Count(related_data_filtered);

Console("Filtered data count: " + related_data_filtered_count);

var catcodeCounts = {}; // Object to store counts of each unique CATCODE

if (related_data_filtered_count > 0) {
  Console("Processing related records...");
  
  // Loop through the filtered related features
  for (var i = 0; i < related_data_filtered_count; i++) {
    var feature = related_data_filtered[i];
    var catcode = feature["CATCODE"]; // Accessing the CATCODE attribute directly
    
    // Increment count for the current CATCODE or initialize count to 1
    if (!catcodeCounts[catcode]) {
      catcodeCounts[catcode] = 1;
    } else {
      catcodeCounts[catcode] += 1;
    }
    
    Console("Processed CATCODE: " + catcode);
  }
  
  // Construct output with counts of each unique CATCODE
  var output = "";
  for (var catcode in catcodeCounts) {
    output += "CATCODE " + catcode + ": " + catcodeCounts[catcode] + "\n";
  }
  
  Console("Output: \n" + output);
  return output;
}

Console("No related records found.");
return "No Related Records.";

XanderBakker

Hi @jschuckert ,

Good question... The FeatureSetByRelationshipName function is available in ArcGIS Online, but was not available in ArcGIS Enterprise at version 10.5.1. This might make the request to the server invalid or perhaps the response is not getting through correctly. Have you verified if there is something in the logs of ArcGIS Server?

jschuckert

Hi @XanderBakker

I am attempting to pull attribute information from a related table, although I am not getting an error but rather a blank result. Is FeatureSetByRelationshipName compatible in ArcGIS Online going against a 10.5.1 ArcGIS Server map service?

Thanks,

Jared

XanderBakker

Hi @TSmith ,

Sorry for the delay in my reply.

My first guess would be the date. You need to convert it to epochs to ensure that it is taken as a date when creating the featureset.

You can do something like:

var epoch = DateDiff(insdate, Date(1970, 0, 0));

TSmith

Hi Xander,

I currently am trying to populate dashboard widgets with info from a related table (and some info from the primary table) using the code below:

var features = [];
var feat;
for (var v in valvefs){
    var relatedrecords = OrderBy(FeatureSetByRelationshipName(v, 'System_Valve_Inspection', ["insdate", "turns", "fintorque"],false),'insdate DES');
    var recentrecord = First(relatedrecords);
   if (Count(relatedrecords)>0){
         
        var feat = {
           attributes: {
               'assetid': v["assetid"],
               'insdate': recentrecord["insdate"],
               'diameter': v["diameter"],
               'turns': recentrecord["turns"],
               'fintorque': recentrecord["fintorque"],
           }
       }
       Push(features,feat);
   };
};   
var joinedDict = {
    fields: [
     { name: "assetid", type: "esriFieldTypeString" },
     { name: "insdate", type: "esriFieldTypeDate" },	
     { name: "fintorque", type: "esriFieldTypeDouble" },
     { name: "turns", type: "esriFieldTypeDouble" },
     { name: "diameter", type: "esriFieldTypeDouble" },
    ],
    geometryType: '',
    features: features
};
return FeatureSet(Text(joinedDict))

This code (as it stands right now) returns an empty resultset. Could I try something similar to what you have here, or does the output of a data expression HAVE to be a featureset?

Thanks so much for any help!

KylieRyan

Hi @XanderBakker !

Thank you so much for your help! I looked into it a bit further and could only thing I could come up with was that the layer (being the Council's main property information layer) was not a feature layer but an map image layer - would that be the issue?

XanderBakker

Hi @KylieRyan ,

Not sure what might be going wrong with the expression. The only thing I can think of is it doesn't find the layer in the map (check the exact name) or the feature does not intersect with any features from the featureset or there are differences in coordinate systems between the feature and the featureset.

I reorganized the expression a bit, but no big changes:

function getAttributeFromLargestArea(geom, fs, field) {
    var items = Intersects(fs, geom);
    var counts = Count(items);

    if (counts == 0) {
        return {'errorMessage': 'No intersection found'};
    }

    if (counts == 1) {
        var result = First(items);
        return result[field];
    }

    var largest = -1;
    var result;

    for (var item in items) {
        var size = Area(Intersection(item, geom));

        if (size > largest) {
            largest = size;
            result = item[field];
        }
    }

    return result;
}

// var layerName = $layer;
var fieldName = "parcel_title";
var fs = FeatureSetByName($map, "council_data.property");

return getAttributeFromLargestArea(Geometry($feature), fs, fieldName);

KylieRyan

I have been trying for months to get the parcel details from a property layer to autopopulate in the popup for a data capture layer for a weed point...

I was provided the following to use, however all it returns is "Execution Error:Invalid Parameters for Count" and I have no idea why or how to fix. I'm losing my mind!! Can someone please help?

var layerName = $layer;
var fieldName = "parcel_title";

var set = FeatureSetByName($map,"council_data.property")

function getAttributeFromLargestArea(feat, set, field) {
var items = intersects(set, feat);
var counts = count(items);

if (counts == 0) {
return { 'errorMessage': 'No intersection found' };
}

if (counts == 1) {
var result = first(items);

return result[field];
}

var largest = -1;
var result;

for (var item in items) {
var size = area(intersection(item, feat));

if (size > largest) {
largest = size;
result = item[field];
}
}

return result;
}

getAttributeFromLargestArea($feature, set, fieldName)

XanderBakker

Hola @Carlos_AndresCamacho_Acuña , cómo estás?

Revisando el primer bloque me di cuenta de algunos errores pequeños. Al comienzo el signo "=" después de "var tbl ". Y hacia el final sobraba una corcheta.

// Inicialmente, se relaciona la dbase table que almacena los registros de operaciones realizadas a la válvula
var tbl = FeatureSetByRelationshipName($datastore,"OperacionValvula");

// Se relaciona el atributo en el feature Class que actúa como llave entre el feature y la tabla relacional
var codigo = $feature["GlobalID"];

// Se establece el query que se creará en la tabla para filtrar los registros de operaciones de la válvula seleccionada
var sql = "ID_GLOBAL = @codigo";
Console(sql);

// Se generan los filtros
var operaciones = Filter(tbl, sql);

// Se realiza el conteo de operaciones
var cnt = Count(operaciones);
var historia = "";
if (cnt > 0) {
    historia = cnt + " Operaciones realizadas a la válvula:";
} else {
    historia = "No hay operaciones realizadas a la válvula";
}

return historia;

En la segunda parte te falta declarar el variable resultado:

var fs = FeatureSetByName($map, "Valvulas_IBAL_2021");
var valvulas = Intersects(fs, $feature);
var cnt = Count(valvulas);

var resultado = "";
if (cnt > 0) {
    resultado = "Hay " + cnt + " valvulas en la comuna";
} else {
    resultado = "No hay valvulas en la comuna";
}

return resultado;

Carlos_AndresCamacho_Acuña

hola quería generar un atributo que hiciera el conteo de la cantidad de registros de una operación de válvulas . ( estas controlan el paso del agua en un acueducto ) utilizando el ejemplo de Hidrantes que tienen en la web, sin embargo me genera error y no se como solucionarlo, el código es:

// Inicialmente, se relaciona la dbase table que almacena los registros de operaciones realizadas a la válvula
var tbl FeatureSetByRelationshipName($datastore,"OperacionValvula");

// Se relaciona el atributo en el feature Class que actúa como llave entre el feature y la tabla relacional
var codigo = $feature["GlobalID"];

// Se establece el query que se creará en la tabla para filtrar los registros de operaciones de la válvula seleccionada
var sql = "ID_GLOBAL = '" + codigo + "'";

// Se generan los filtros
Console(sql);
var operaciones = Filter(tbl, sql);

// Se realiza el conteo de operaciones
var cnt = Count(operaciones);
var historia = "";
if (cnt > 0) {
historia = cnt + " Operaciones realizadas a la válvula:";
}
} else {
historia = "No hay operaciones realizadas a la válvula";
}

return historia;

El feature tiene un campo llamado "OPERACION_QUE_REALIZA" que le da la simbología a las válvulas, este atributo es el único que se debe diligenciar en el feature antes de diligenciar la información en la tabla relacional.

Adicionalmente, quería hacer el conteo de válvulas por comuna ( Localidad) y la siguiente expresión me genera error:

var fs = FeatureSetByName($map,"Valvulas_IBAL_2021");
var valvulas = Intersects(fs, $feature);
var cnt = Count (valvulas);

if (cnt > 0) {
resultado = "Hay " + cnt + " valvulas en la comuna";

} else {
resultado = "No hay valvulas en la comuna";
}

return resultado;

agradezco la ayuda

XanderBakker

Hi @JussiLehtonen ,

The Field Calculation profile only supports $feature and $datastore. So this means that the data you want to use in the calculation must be in the same $datastore (FGDB, EGDB, hosted feature layer, etc). Although the FeatureSetByPortalItem is available, I haven't been able to use it successfully in ArcGIS Pro for a field calculation.

With the latest version of ArcGIS Dashboards, you can create featuresets on the fly with Arcade and use them as data source. This uses FeatureSetByPortalItem to access the data, so I assume that it a matter of time it will be able to use data from different data sources in an Arcade expression to calculate a field.

Jussi_Lehtonen

Is it possible to reference other layers in ArcGIS Pro project? I can refer to other layers in a webmap but how about ArcGIS Pro map or project? I am looking for a way to calculate distances to objects on other layers in ArcGIS Pro field calculator.

RickardNasstrom

Thanks for testing and your quick reply. I just tried with the same feature layer in AGOL Classic MapViewer where it works.

This is how my pop-up looks in Beta

And here is in classic:

I'll try to get rid of my special charachters, see if it helps.

Thanks for a great guide!

XanderBakker

Hi @RickardNasstrom ,

It is strange that it would not work in Map Viewer Beta, since it should. I just did a test with the example that I constructed for this post and it works as expected in the Map Viewer Beta:

The first thing where I would look at is renaming the layer and not using special characters provides a valid result. I don't see anything else that could explain this behaviour.

RickardNasstrom

Hi @XanderBakker ,

Thanks for a great example and workflow. I am basically trying to replicate this workflow, but I get stuck when trying to summarize the info in my subsectors in MapViewer Beta in AGOL. When using MapViewer Classic in Portal it works.

I wanted to use MapViewer Beta for this, and since our Portal is currently on 10.8 I shared the data through a distributed collaboration to our AGOL account. I get the previous expressions for summarizing related table records for individual assets to work.

In my Arcade window in MapViewer beta it all looks great and I get a correct looking result, in my pop-ups however, I only get a result when there is no objects in the sub-sector.

This is what it looks like when I write my expression. - It recognises dates and the number of objects.

I am quite novice in terms of using Arcade, but my guess here is that it has something to do with me not accessing the data correctly, however it seems strange to me that I get a result in the Arcade window?

Here is my code: (basically just copy/paste frome yours)

var fs = FeatureSetByName($map,"Belysningsstolpar_Gävle");
var belysning = Intersects(fs, $feature);
var cnt = Count(belysning);
Console(cnt)

var age_tot = 0;
for (var lyse in belysning) {
var age = DateDiff(Now(), lyse.Installationsdatum, "years");
age_tot += age;
Console(age_tot)
Console(lyse.Installationsdatum)
}

var resultat = "";
if (cnt > 0) {
var age_media = age_tot / cnt;
resultat = "Det finns " + cnt + " Belysningsstolpar i subsektorn";
resultat += TextFormatting.NewLine + "Medelåldern är " + Round(age_media, 2) + " år";
} else {
resultat = "Inga belysningsstolpar i subsektorn";
}

return resultat;

Could it be accessing the data or is there something different when you use MapViewer Beta?

Best Regards

Rickard

CarstenRisager

Hi Xander,

Thank you for this great example and all your answers, it's an Arcade goldmine.

I'm trying to replicate the popup functionality in one of my own webmap on a portal, but I keep running into the same error: "Execution Error:Runtime Error: Variable must be declared before it is used.." but I can't see any undeclared variables in the code.

--------------------

-------------------------------

The map is shared on: https://gis.nst.dk/portal/home/webmap/viewer.html?webmap=b8be8d61e775431c8f5a92887b49860e

I have tried almost the same code in ArcGIS Pro ($datastore instead of $map in the first line) to calculate a field and in this environment I don't get any errors.

Note: I tried the code on ArcGIS Online and it ran without any problems, so I assume that it must be the portal security kicking in somehow.

XanderBakker

Hi Michael Layne ,

Good question. As far as I know, the Attribute Calculation Rule profiel only has support for $datastore, which makes me believe that it is not possible if the information is not in the same datastore. Maybe in the feature support for other data sources will be added so that this will be possible. For now, if possible, it might be good to include the other layer in the same datastore to be able to use Attribute Rules and Arcade or schedule a task (python script) to update the information at a certain frequency.

Anonymous User

Hey Xander,

Is it possible to use arcade to reference data from another gdb?

For example, we are trying to create an attribute rule (for lines and points), where by they acquire an attribute of an intersecting polygon from another geodatabase. We are wanting to create this rule using arcpy. I've gotten it to work using $datastore with a polygon inside the same gdb, but we'd like to be able to cross reference databases. Any idea?

Anonymous User

Appreciate your efforts Xander. I had a phone call with Support and I didn't quite understand their explanation on that second parameter - I was told if it's from SQL it can be blank but if its hosted it needs it? I think you are correct in that if the layer only has one relationship, empty quotes works because it doesn't need to search through multiple relationships. Not sure why it worked for him though and not on my setup.

I did test my data by publishing as a hosted service in my Portal and the Arcade expressions all work wonderfully. So I've narrowed it down to something with SQL. My options are to backup my data, blow away the current SQL DB, create a new one and try to set this up again and see if that helps. My other option is to publish my data as it is now as a hosted service and forget trying to use SQL. I'm debating the pros/cons of doing that as I don't want to get in the middle of this data effort and hit limitations with the route I chose. Honestly nobody is editing the SQL data directly - it would all be done through Portal and Survey123, so hosted may be the way to go. Especially if this Arcade stuff works fine on the hosted data.

This project needs to be deployed next week so if I can't get this expression stuff figured out it won't prevent the project from moving forward, I was just hoping to get something simple working.

XanderBakker

Hi Nathan Fazer ,

I did some tests and providing an empty string in the FeatureSetByRelationshipName did not work for me. I don't think it is the correct way of using the function.

XanderBakker

Hi Nathan Fazer ,

I think they managed to not only the confuse you but me as well. The second parameter is not optional, and providing an empty string is not documented in the help. Maybe if you have a single relationshipclass, providing an empty string just takes the first one available and everything works, but I see no documentation to aid that assumption. Let me run some tests and get back to you.

XanderBakker

Hi Paul Sweeney ,

I am not really aware of what limitations there are when using Arcade in the dynamic text. Maybe you could use other functions like Portal and FeatureSetByPortalItem to get access to the data you need. You can also pre-calculate the data in a new field and use that static information in the map series.

Regarding your comment on using the pop-up in the map series... a pop-up will only be present when you click on a feature. You could use labeling, but Arcade functions in this profile are very limited.

Anonymous User

Xander, I sent Esri tech support my sample data with related tables and related feature classes. They brought it into a SQL environment and published it to Portal and sent me an email that this - FeatureSetByRelationshipName($feature,"",["householdcontacts_casename"]) - resulted in a successful test. When I do it, it's empty. What I found odd is in his test there is nothing in the quotes between $feature and [fieldname]. I thought that was a crucial piece of making this work is the relationship name needed to be there, like this - FeatureSetByRelationshipName($feature, "Cases_householdcontacts", ["housecontactname"].

So now I'm really confused how Esri tech support was able to get a successful test missing information and I can't get anything trying 10 variations. This seems so simple yet I either get errors or empty results.

PaulSweeney3

i want it to be an expression built into the map series. When you select dynamic text you have the option to use an arcade expression if you are inserting an attribute value or a table. They are not in the same feature service, i had not realised that was what the $datastore represented on Arcgis online but it makes sense now. it would be useful if you could essentially show your pop up on Arcgis online in a map series.

XanderBakker

Hi Paul Sweeney ,

Where do you want to calculate the count? Is that in a Field Calculation? Are the polygon and point layer part of the same feature service (are they in the same $datastore)? I haven't worked with Arcade in combination with map series, so I don't have a straight answer for you.

PaulSweeney3

Hi Xander Bakker i have created a map series from an Arcgis online Map in Arcgis pro based on a series of polygons and i wanted to count the number of intersecting points on another layer. The arcade expression works fine on ArcGIS online but in the map series it does not recognise the layer i reference in the featuresetbyname function when i use $datastore. From you responses above it sounds like there is no way to reference ArcGIS online layers in an Arcgis pro map series using arcade or am i missing something?

XanderBakker

Hi nfazer_midlandcounty ,

If Esri support provides a solution please share it here so that other user may benefit from it too.

Anonymous User

Hi Xander

Yep I just updated to 10.8.1 this past Friday from 10.8, so this should be working. I've got an open case right now with Esri so I'll pass this info along to them and see what they may be able to figure out. I appreciate the help. It works pretty well in AGO, unfortunately this project is in Portal. My other thought was to try a test on our Portal with a hosted service and see if that makes a difference, instead of referencing data in our SQL.

XanderBakker

Hi Nathan Fazer ,

Quick questions... is your Enterprise 10.8 or later? The FeatureSetByRelationshipName was introduced in Arcade version 1.8 and became available starting with Enterprise 10.8.

If you have 10.7.x you could use FeatureSetByName together with a filter on the key field to get the related records.

Have a look at:

Version Matrix | ArcGIS for Developers
and in the function reference you will find in which version it was introduced: Data Functions | ArcGIS for Developers

Anonymous User

Appreciate the help (and quick replies). I probably should have provided all the relevant info. Here's the entire code I got working in AGO based on what I've found here and in other posts. Replicating this in Portal however, gives me the error invalid parameters for count. Everything is the same - layer names, relationships, etc. So even though I made progress in my testing in AGO, this actually has to be in Portal as it's for our Health Department.

return result;

So now I'm baffled as to why this works in AGO but not in Portal.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle links

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