Latest Contributions by KristianEkenes

I write about how you can do this in a few places. Basically, you can follow the pattern in this sample: https://developers.arcgis.com/javascript/latest/sample-code/visualization-update-data/ This is also described in this "Time styles" guide: https://developers.arcgis.com/javascript/latest/visualization/data-driven-styles/time/#attribute-animation Here are some blog posts that provide context and more examples: https://www.esri.com/arcgis-blog/products/js-api-arcgis/mapping/six-ways-to-visualize-change-over-time-in-web-maps/ https://www.esri.com/arcgis-blog/products/js-api-arcgis/mapping/animate-and-explore-covid-19-data-through-time/ https://www.esri.com/arcgis-blog/products/js-api-arcgis/mapping/mapping-large-datasets-on-the-web/ If you get it working, I'd love to see how it turns out. ... View more

I wrote a blog article about how to do this a few years ago. The live samples are using older versions of the API, but the pattern for coloring the bins should be the same. https://www.esri.com/arcgis-blog/products/js-api-arcgis/mapping/make-your-histogram-legendary/  ... View more

Thanks for pointing this out. I can easily reproduce from your app. Can you contact Esri support and have them log an issue, so we can get this in our system to fix? That way you can also track the progress of the bug report. ... View more

I would reach out to Esri support and show them the app where this is occurring. It appears to be originating in the rendering engine somewhere, but we won't know for sure until we see a live reproducible case. Once Support verifies it's an issue, it's submitted as a bug and the dev team will take a look at it. ... View more

I suggest reaching out to Esri support if you suspect this is a bug. They will attempt to reproduce the issue independently then log a bug so the dev team can take a look at it. ... View more

I'm not sure I follow the scenario 100%, but it sounds like you could just use the smart mapping functions for this: https://developers.arcgis.com/javascript/latest/api-reference/esri-smartMapping-renderers-type.html#createRenderer The smart mapping functions generate renderers based on the underlying data. The createRenderer function for unique values works for all "feature layer-like" types, including GeoJSON. Here's an example: https://codepen.io/kekenes/pen/wvNPGXJ?editors=100  ... View more

Not necessarily a performance benefit. Just an alternative that is fewer lines. I try to go with the shortest expression. Though I'd say the for loop version is more readable than the reduce approach. ... View more

@KenBuja  is correct. You should use the Expects function for this case if using a for loop. The rendering engine for Online (JS API) is optimized for performance. So it only requests the data that's required by the layer's style by default. If you specify a field outside of an Arcade expression, the API knows to request data from that field for rendering. In the case of Arcade, the expression is evaluated for the fields required to make it work. When $feature.FIELDNAME is used, it's easy for the engine to figure out the required fields. That's why the alternative expression works. However, you can use Expects to directly tell the rendering engine which fields it should expect to request from the service. This can be a list of fields as Ken points out, or  you can also define template strings like the following: Expects("*"); // requests all fields. Don't do this if you have a ton of attributes. Expects("Year_*") // requests all fields that begin with "Year_". (e.g. "Year_2000", "Year_2010") would be requested, but "Y2004" wouldn't). On a side note, you could take advantage of the number function to condense the initial expression like this: Expects($feature,'*_20*'); var fieldList = ['Dorian_2019','Sally_2020','Ian_2022','Nicole_2022','Idalia_2023']; var total = 0; for (var f in fieldList) { // adds 1 if "YES" // adds 0 if not "YES" total += Number($feature[fieldList[f]] == 'YES'); } return total; Or use the reduce function to avoid a for loop altogether. You still need Expects for this to work... Expects($feature,'*_20*'); var fieldList = ['Dorian_2019','Sally_2020','Ian_2022','Nicole_2022','Idalia_2023']; function add (total, fieldName){ total + Number($feature[fieldName] == 'YES') } Reduce(fieldList, add, 0);   ... View more

The UniqueValueInfo.description is intentionally left out of the documentation as it does not have a use in the current API. You should use the label property in stead of the description. ... View more

> the still undocumented JSON structure for specifying it with uniqueValueGroups The JSON structure has actually been documented in the web map specification ever since the concept was introduced. You can find it here:  https://developers.arcgis.com/web-map-specification/objects/uniqueValueRenderer/ https://developers.arcgis.com/web-map-specification/objects/uniqueValueGroup/ https://developers.arcgis.com/web-map-specification/objects/uniqueValueClass/ It includes examples with multiple scenarios. Perhaps we should improve the JS documentation to link to the web map specification. ... View more

This sounds like a potential bug in the rendering engine. I advise reaching out to Esri Support so they can validate the issue and get it logged into our system. ... View more

It could be. I also don't think we save renderers directly to the service anymore (on the Online side anyway). It would be worth checking in with someone on the Pro/Enterprise side... ... View more