Latest Contributions by KristianEkenes

A couple of things on this: 1. You can tell if a feature represents a cluster if the isAggregate property of the feature is `true`.  Checking for `cluster_count` is pretty reliable for clusters, but unreliable if you want to check if a feature represents an aggregate from binning or clustering. 2. You cannot tell if a feature is an aggregate from a layer query (e.g. `layer.queryFeatures()`). This will always result in returning features from the underlying service, not from the client. At this point, clusters (and bins) are always generated client-side. Therefore, you cannot query them from a service. However, you may query them on the layerView. 3. You can query aggregates (i.e. clusters or bins) from the layer view using the queryAggregates() method. This will only query aggregates in the view, and not return any individual features. 4. If you query an aggregate that you want to drill into further (e.g. you query for a cluster with 5,000 features) you can use the resulting aggregate graphic of that query to query the features represented by (or contained within) that cluster. You can do this by calling the queryFeatures() method on the layer view and by setting the aggregateIds property to include the id of the aggregate feature you had just queried. 5. How can I determine whether a feature has been clustered or not? This depends on the origin of the feature. You can easily find out through hitTest if you are getting the feature from a click event. Simply check the isAggregate property. If you are getting the feature from a service query, then it's a bit more complicated. You would need to query all aggregates, iterate through each, then query all features included in each aggregate and check for a match. This is a pretty fast operation since these are all client-side queries. Here's an example of how to do this: https://codepen.io/kekenes/pen/MWMOrVP?editors=1000 In that sample I query a feature from the service, then highlight the cluster to which it belongs (even though it is not rendered in the view). const highlightCluster = async (layerView, id ) => { if (highlightHandle) { highlightHandle.remove(); highlightHandle = null; } const { features } = await layerView.queryAggregates(); features.forEach( async (f) => { const aggId = f.getObjectId(); const q = layerView.createQuery(); q.aggregateIds = [ aggId ]; const { features } = await layerView.queryFeatures(q); const result = features.find(f => f.getObjectId() === id); if(result){ highlightHandle = layerView.highlight([aggId]); } }); }; Hopefully this helps. ... View more

> Is there a way to generate the heat map using the data in the map view, what's in the current view extent? This is how this method works. It only takes into account what is in the view. > if I load the map being zoomed in with no data in the view, the heatmap is completely washed out.  That's because there is no data in the view. You will only see anything meaningful if you zoom to the area where you have data and want to create a heatmap. > Or, can I set the zoom dynamically before loading the Heatmap, so the data is in the view? Yes. You can set this with the goTo method or by setting the view extent. ... View more

I suggest contacting Esri support (support@esri.com ) with this issue. We're about to make another update, so it would be good to get this recorded in our our bug triage system to address it as soon as possible. ... View more

This looks like it could be a bug. Could you reach out to Esri support and report to them? That way we can can a repro case on our end and an issue logged in our system that you can track the progress on. ... View more

For performance issues and rendering bugs, I recommend you reach out to Esri Support (support@esri.com). They'll validate the issue you're seeing and create a bug report in our system so we can take a look at it. You'll also be able to track the planning and progress for the bug when reporting through that channel.  ... View more

Yikes. Do you mind logging an issue with support so we can get this into the system for fixing ASAP? ... View more

You can test it out using https://js.arcgis.com/next/ ... View more

This should be fixed in the next update of the JS API (v4.29). ... View more

You need to define aggregate fields for them to come through in $feature. That's what I meant by featureReduction.fields. This sample demonstrates how to do that. https://developers.arcgis.com/javascript/latest/sample-code/featurereduction-cluster-aggregate-fields/    ... View more

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