Latest Contributions by UndralBatsukh

Hi there,  Have you seen this post https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/simplemarkersymbol-outline-not-rendering-correctly/m-p/1586428/highlight/true#M86532?   ... View more

Hi there,  We addressed this issue in our upcoming release (version 4.32). You test the fix in next (4.32) version. Here your codepen updated: https://codepen.io/U_B_U/pen/YPKBGVj?editors=1000 Thank you for reporting this issue, -Undral ... View more

Hi there,  It appears that the computeHistograms method isn't gathering all the necessary settings from the layer when it's autocast (i.e., when an object is passed directly to the method). To resolve this, please create a new ImageHistogramParameters instance, rather than relying on autocasting. You can do this with the following code:   const params = new ImageHistogramParameters({ geometry: view.extent, pixelSize: pixelSize }); ... View more

Hi there,  This is expected behavior. When calling setStyleLayer, even if it modifies an existing layer—or adds a new one—the layer may have a different query or layout. As a result, we need to access the PBF (protocol buffer) and reprocess the features to ensure they align with the updated configuration. We fetch pbf for visible tiles. ... View more

Hi there,  There are couple of issues in the app you provided.  1. Geometries of features added to the StreamLayer must be in the spatial reference of the view, because the layer's spatialReference is always set to the spatial reference of the view. To avoid overhead, the stream layer does not do any additional processing or reprojecting on features as they arrive. This behavior is documented here.  So you either need to use a basemap in WGS84 or your features need to have geometries in Web Mercator.  2. StreamLayer.sendMessageToClient() states that when sending features message then your features have to be esri JSON feature object. Based on this, I updated your codepen: https://codepen.io/U_B_U/pen/QwLqrpd?editors=1000   ... View more

Hi there,  You could query for all attachments. The attachments query returns an object containing AttachmentInfos grouped by the source feature objectIds. Then use the objectsIds to highlight the features. Here is a simple codepen app showing the concept.    https://codepen.io/U_B_U/pen/qEWbPgj?editors=1000 ... View more

Hi there,  I recommend using StreamLayer, especially since you mentioned that your data is updated frequently. StreamLayer is specifically designed for handling high-frequency data updates. You can integrate it with a custom websocket, or use the client-side StreamLayer for seamless integration depending on your needs. You can find an example of the custom websocket implementation here, and a sample for the client-side StreamLayer here. This sample shows how to add 100,000 features to a cllient-side FeatureLayer without blocking the UI. However, please note that client-side FeatureLayers are not optimized for handling data that updates at a high frequency. Additionally, I recommend reviewing the Visualization Guide Docs, which offer specific guidance on how to visualize high-density data effectively.     ... View more