Latest Contributions by UndralBatsukh

Hi there,  Thanks for letting us know. This sample is using deprecated service that is not longer being updated. We will update the sample to use the latest service. Please use the first layer in this feature layer portal item in your app instead - https://jsapi.maps.arcgis.com/home/item.html?id=f42ecc08a3634182b8678514af35fac3 Here is the direct link to the first layer - https://services2.arcgis.com/FiaPA4ga0iQKduv3/ArcGIS/rest/services/Transportation_v1/FeatureServer/0   ... View more

Hi there,  I apologize for taking a long time to reply. Just looked at your app. I do indeed say the issue. We just created an issue to fix this and I will update you once we have a fix.  Thanks ... View more

Hi there,  The behavior you’re seeing is expected. You’re creating your polylines in WGS84 and adding them directly to a FeatureLayer that’s also set to use the WGS84 spatial reference. However, the features need to be projected to EPSG:3031 on the fly to display on the map. When features are projected, the feature tile extent is also projected into the data’s spatial reference (in this case, from 3031 to WGS84). As a result, the extent doesn’t intersect with the geometry, leading to the behavior you’re observing. To resolve this, you can: Set the layer’s spatial reference to match the view’s spatial reference. Provide geometries in the same spatial reference as the view. Or densify the geometry so that points will intersect with the tile extent. Here is your codepen updated - https://codepen.io/U_B_U/pen/MYKGBgp?editors=1001  In this code, I am setting the layer's spatialReference to 3031 so that it matches the view's spatialRefrence. Hope this helps, -Undral ... View more

Hi there, This issue is addressed at version 4.34. You can test the fix using our next version. Here is your codepen updated to point to the next version: https://codepen.io/U_B_U/pen/EaVePpv?editors=1000 Thanks ... View more

Hi there, Thank you for sharing the codepen. However, I’m already very familiar with this behavior, so a basic example won’t help us investigate the issue you originally described. To properly assess and address the performance concerns, we need access to your actual webmap. Starting with version 4.19, the ArcGIS Maps SDK for JavaScript began supporting the fetching of all features from point feature services at initialization, provided certain conditions are met. As of version 4.33, this behavior has been extended to AGOL-hosted feature services with polygon, polyline, and multipoint geometries, again assuming the appropriate conditions are satisfied. This enhancement improves app responsiveness by loading all features at once and eliminating repeated server requests as users interact with the map. We need to examine your webmap directly to determine how your data aligns with these conditions. This will help us assess performance and potentially fine-tune the behavior further. Would you be able to share the webmap with us? ... View more

Hi there,  Is it possible for you to share your webmap url with me? You can direct message me if you dont want to share publicly.  ... View more

https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-WMSLayer.html#fetchImage - should work in this case. Have you looked at it? You can do something like   const image = await layer.fetchImage(view.extent, view.width, view.height); console.log(image.src); ... View more

That should not happen. Repro case would be useful in this case. Which version of the API are you using? ... View more

I am not able to reproduce the issue in this simple test app - https://codepen.io/U_B_U/pen/MYYqErz?editors=1000   ... View more

Can you please post the geometry (json representation) that is in question here?  ... View more