Latest Contributions by UndralBatsukh

Have you tried dialog-create event? https://developers.arcgis.com/javascript/3/jsapi/identitymanager-amd.html#event-dialog-create ... View more

Hi there,  You need to specify the bandIds on the ImageryLayer so that renderer uses the right band. We will update RasterStretchRenderer documentation to indicate that one needs to set the bandIds when working with multi-band image services. With that said, we will look into improving the current behavior.  I set up a simple codepen app: https://codepen.io/U_B_U/pen/VwQmPdg?editors=100 In this app, I am setting the bandIds to first band (magnitude band) and applying the raster stretch renderer. The color ramp is honored in this case.   ... View more

HI there,  At 4.23, we added a support for contingent attribute values in FeatureForm: https://developers.arcgis.com/javascript/latest/release-notes/#featureform You should be able to use this without having write a code to keep the integrity of your data. ... View more

Hi there,  You can use geometryEngine.geodesicArea method to calculate the polygon area while user is reshaping the polygon.  I updated the sample you linked to showcase how to check if the polygon area is less than 1000 acres. Then let user make a change otherwise, force user to reshape the polygon. Having it equal to one number will probably be a challenge for users unless you help to set the area. My changes are in onGraphicUpdate function. https://codepen.io/U_B_U/pen/qBxbWOy?editors=1000 -Undral ... View more

Hi there,  Please take a look at the FeatureLayer.applyEdits doc. To update features, you must pass in array or collection of features! So you have to update your code to query the features your want to update, then update the attributes of the features and pass in those features to the FeatureLayer's updateFeatures param.  So you'd have to something like the following:  // editFeature is a feature you got from your feature layer editFeature.attributes[announcement] = newAnnouncement; // Setup the applyEdits parameter with updates. const edits = { updateFeatures: [editFeature] }; featureLayer.applyEdits(edits).then((editsResult) => { console.log(editResult); }) .catch((error)=>{ console.log(error); });   Please take a look at the following two samples as they both use FeatureLayer.applyEdits: https://developers.arcgis.com/javascript/latest/sample-code/sandbox/?sample=editing-applyedits  https://developers.arcgis.com/javascript/latest/sample-code/sandbox/?sample=layers-featurelayer-collection-edits   ... View more

You are getting this error because you are corrupting your polyline geometry. For example, the polyline is going from: [9316221.444425754, 5694060.22603468] [10270155.5574245, 6091609.210145776] To 11311599 [10270155.5574245, 6091609.210145776]   You should use Polyline.setPoint method to update the vertices or the other methods to change the polyline geometry. Or you have to make sure that you are changing the right values in the array without corrupting the array of vertices. The following for example works in your app: copyGraphic.geometry.paths[0][0][0] = firstGraphic.geometry.paths[0][0][0] + 300000; copyGraphic.geometry.paths[0][0][1] = firstGraphic.geometry.paths[0][0][1] + 300000;   ... View more

The codepen app uses picture marker symbols with 40px x and y offset for point features. Layer has popuptemplate which uses hitTest. The hittest precision is already way better.  Is this what you not see? Can you please provide me a reproducible code if you do not see it fixed in the next version.  ... View more

Hi there,  We overhauled the MapView.hittest implementation at 4.23 to return all features at a given hit point, not just the topmost ones, and changed the implementation to perform on GPU. The issue you are describing is a known issue and we addressed this issue at 4.24. You can check the fix using our next version. This simple codepen app shows the fix: https://codepen.io/U_B_U/pen/abEMrzq?editors=1000.  We cannot do a patch for 4.23 at this time.  Undral ... View more

Adding more information for my previous comment. ImageryTileLayer internally uses raster information model, which supports NoData pixels. When a pixel or tile is missing or has a nodata mask, it's required to honor it as NoData. The raster has a resolution (corresponds to finest LOD), and uppersampling happens beyond that --- that's the "overzoom" you can see. This design is consistent with ArcGIS Pro, and consistent with ImageryLayer (if the same elevation cache dataset is published as a dynamic image service) --- when using world elevation 3D service for display. The primary purpose of World elevation3D service is still providing elevation for 3D. In future, we can look into adding some special logic/flags to handle this in the JS API. ... View more

Hi there,  This is not a bug! The API working as designed. ImageryTilelayer does a raster level overzoom not a tile based over zooms. It will over zoom the data from the last available LOD. There is no data for areas such as Tibet at the last available LOD. So when we over zoom, we don't show data since there is no data available at the last available LOD. We can add a boolean flag to resample tiles from its last available LOD. However, in this case the result will be incorrect completely.    -Undral ... View more