Latest Contributions by UndralBatsukh

Hi there,  The Map SDK document gives the link to the new National geographic basemap: https://www.arcgis.com/home/item.html?id=f33a34de3a294590ab48f246e99958c9 The API allows users to add basemaps by choosing one of the named basemaps (shortcut). The name must exist in the table. Since the new version is not listed in the table you cannot add it by trying different names. So you have to add the basemap from the portalItem. The Map.basemap either accepts string (must come from the named table list) or a Basemap. If you click on the basemap link  then the SDK document for the basemap shows many different ways of setting up a basemap for your map.  For the case of national geographic basemap, you do the following. const map = new Map({ basemap: new Basemap({ portalItem: { id: "f33a34de3a294590ab48f246e99958c9" } }) });   ... View more

Hi there,  You can set esriConfig.request.useIdentity to false. Undral   ... View more

Hi there,  So the purge takes place on the client-side. The ageReceived does exactly what it says. The client timestamps features as they arrive in the browser and they are cleared after it exceeds the ageReceived time. You can set the ageReceived to be seconds... For example if you set it to 0.1, features will be cleared out once their received age exceeds 6 seconds. Sounds like you have StreamLayer.timeInfo.startField. If you do then you can set the purgeOptions.age instead. In this case, the client will purge features that exceed the given `age` (in minutes) where `age` refers to the age of the underlying feature (decided by timeInfo.startField). Setting different parameters on purgeOptions can get confusing as they all take effect. I setup this codepen for you to test the purgeOptions. 1. New features are pushed every second (set parameter) and features are cleared every two seconds since the feature was added on the map (received paramter) and 8 observations are visible at a time(ma parameter): https://codepen.io/U_B_U/pen/ExdPpdy?editors=1000&received=0.03&set=1000&max=8 You can modify the url query params to see different behaviors. I added comments where description was added. Hope this helps. ... View more

Hi there,  It should work without any issues. Seems like the issue specific to your case and a reproducible case would be better to find a solution.  The following code snippet sets a definitionExpression on a sublayer for a time-enabled MapImageLayer and it works as expected. const layer = new MapImageLayer({ url: "https://sampleserver6.arcgisonline.com/arcgis/rest/services/Earthquakes_Since1970/MapServer", sublayers:[{ id: 0, definitionExpression: "magnitude >= 8" }] }); ... View more

Hi there,  So once you create the new feature you need to query for that feature from the layer or the layer view  (after it finishes updating). I modified your app so that it queries the layer for the newly added feature and use this feature to highlight the row in the table. You cannot use the graphic you created to add as a feature. Instead of you have to use the feature that exists in the layer. Hope this makes sense. The following is where the changes were made and here is a codepen: https://codepen.io/U_B_U/pen/abajbRz?editors=0010 streetlightsLayer.applyEdits({addFeatures: [graphic]}) .then((results) => { console.log("feature added", results); // How do I select this feature on the map and/or the featureTable //featureTable.selectRows(graphic); // nope! //view.highlight(results.addFeatureResults[0]); // nope! const where = `${streetlightsLayer.objectIdField} = ${results.addFeatureResults[0].objectId}`; let query = streetlightsLayer.createQuery(); query.where = where; query.outFields = ["*"]; streetlightsLayer.queryFeatures(query).then((results) => { console.log("query results", results.features); featureTable.selectRows(results.features[0]); }); newStreetlights.push({ objectId: results.addFeatureResults[0].objectId, feature: results.features[0] }); featureTable.refresh(); // needed? }) .catch((error) => { console.error(error); });   ... View more