Latest Contributions by KristianEkenes

The JS API does support various blend modes and effects on the layer level.  https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#blendMode https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#effect  We also have a guide to visualizing high density data where we talk about bloom as a way to accomplish this: https://developers.arcgis.com/javascript/latest/visualization/high-density-data/bloom/ There are other techniques as well, like using opacity. Hopefully this helps. ... View more

It looks like this is posted in the wrong community since this is a Runtime snippet and not a JavaScript one. I suggest posting in one of these: https://community.esri.com/t5/arcgis-runtime-sdks/ct-p/arcgis-runtime-sdks  ... View more

Hi @quooston , Can you create a small test app that reproduces the issue? This should work...so I'll need an app to help debug to help isolate the issue. You can also reach out to Support if the data you're working with is private or sensitive. They can set up a similar test dataset and help reproduce as well.   ... View more

Yep. The server-side solution would request bins from the server, not individual features. Though you would be able to query a bin for its individual features. ... View more

@JamesNurse  We're targeting server-side binning sometime next year. We're already doing research on the project now, but it won't be available until at least March of 2023 (this is not a release date, just a very loose estimate on the earliest you would see it).  ... View more

Hi @LukeCalladine, The difference between FeatureLayer labeling and MapImageLayer labeling is that FeatureLayer labels render client-side, whereas MapImageLayer labels render server-side. The JS API rendering engine is used for all client-side visualizations. MapImageLayer doesn't rely on that rendering engine. Rather, it renders using the same rendering engine you would see in Pro/Enterprise. So that explains how the labels will look the same on MapImageLayer in the web as they do in Pro. The rendering happens on the server and the client requests an image of that rendering, which is then overlaid on the map view. Regarding basemap labels. They likely come from a layer in the Basemap.referenceLayers If you move that layer representing basemap labels from the basemap to the Map.layers, then it will render in the order of the Map.layers. Here's an example of how you can move the label layer to the map operational layer so the labels render below the feature layer: https://codepen.io/kekenes/pen/dymgxgw?editors=100  ... View more

This is odd. I haven't observed it before. Are you able to share the dataset or reproduce it with a public layer? ... View more

Yeah. Understood that the current workflow is a bit awkward. I'll pass this along to the labeling engine folks and see what they say. ... View more

That's correct. This isn't supported in the JS API, and I don't think it's on the roadmap either. You could try separating out the bolded line as a separate label class. That's the only work around I can think of. ... View more

I just re-read your post and now see how the data is managed 😅. You should be able to use Arcade in this scenario. ... View more

Are you able to add a new field to the table to indicate which sales area the zip code belongs to? How are you managing the data for which zip codes belong to each sales area? If you had a separate field for the area, you would only need to define 3 unique value infos and I would expect performance to work just fine.  If you are unable to add a new field to the underlying data, you can also write an Arcade expression to return the sales area name/id based on the zip code value. This would be a large expression, but I imagine you could use the same logic you're currently using in JavaScript to set the colors as you do in the Arcade... This would also only require you setting up one symbol per sales area. This sample demonstrates how you could set up the classification with Arcade: https://developers.arcgis.com/javascript/latest/sample-code/visualization-arcade/  Hopefully that helps. ... View more

Hi @AntonioGallo , The configuration API for cluster labels and popups is very similar to the layer labels and popups. To label clusters and individual features, you need to use the following: layer.featureReduction = { type: "cluster", labelingInfo: [ // define label classes here for clusters ] }; layer.labelingInfo = [{ // define label classes here for individual features }];   This sample application does both, though I admit the label classes are a bit more complex as they handle different styles and label placements at various scale levels: https://developers.arcgis.com/javascript/latest/sample-code/featurereduction-cluster-filter-slider/  See the image below:  The green point indicated by the red arrow is an individual power plant. It is not labeled with a "1", but rather with the information for the plant itself in the layer.lablingInfo property (since it is not a cluster). The other blue symbols are clusters of 4 and 5 power plants respectively. Those labels are defined on the layer.featureReduction.labelingInfo property. Notice the label placement is different. That is because each label comes from a different label class, which is defined based on the average size of power plant in the cluster. Hopefully that helps. Kristian ... View more