Latest Contributions by JohnGrayson

Even if there currently isn't an elevation profile widget, there are many resources and techniques that can help you create one. Sometimes the geometries already contain Z values and then it's just a matter of sending those elevation values to your favorite charting library. Other times we can use the Elevation Sampler api class to extract elevation values from the current display or elevation layer, and then chart those values. In some cases you might want to use elevation values derived from an elevation service, and to help you do that you can use some of the Esri Elevation Analysis services. Here's an old demo which uses the Sketch tools to define the geometry and then uses the ElevationSampler class to get elevations used in the current display view: Demo: Elevation Profiles & Interesting Places GitHub: Create Elevation Profiles We hope this helps. ... View more

Do you have a codepen of jsbin showing the issue? ... View more

At 4.15, the correct way to manipulate features in a client-side FeatureLayer is via the applyEdits() method. From the FeatureLayer | 'Read more' | 'Add an array of client-side features' section: "If features are added, removed or updated at runtime, then use applyEdits() to update the features then use queryFeatures() to return updated features. Check out add or remove graphics from a FeatureLayer sample to see this in action. Attribute values used in attribute queries executed against client-side feature layer, and layer views are case sensitive." ... View more

I'm not sure doing this via the renderer is the best way to handle this use case.  Have you instead tried looking at the  effect (FeatureEffect) property of the FeatureLayerView?  By setting the effect property you can configure the FeatrueLayerView to display features that don't have a specific route name to be more transparent. ... View more

Correct, it's just a Polygon and not a different type of geometry; this means it will always be just 'lots of points'.  The way I like to think of it is that the Circle class facilitates and simplifies how those points get created, just like the sketch related tools. The only additional benefit of returning a Circle instead of a Polygon would be to have some of the Circle specific properties, but it wouldn't change the underlying list of points as those would be exactly the same for both the Circle or Polygon. This sounds like a good enhancement request or ArcGIS Ideas. ... View more

Try using the watchUtils, it might do what you need. watchUtils.whenFalseOnce(view, 'updating' function(evt){ query('.esri-slider__label')[0].classList.add("hide"); });‍‍‍‍‍‍ ... View more

From the Help doc:(FeatureLayer | ArcGIS API for JavaScript 4.15) "This property may only be used in a SceneView".  Try controlling the layer order based on the order in the Map.layers collection.  If you need to reorder the layers after they've been added you can use the 'reorder()' method of the Map (Map | ArcGIS API for JavaScript 4.15) ... View more

There's no circle geometry type in the API. If necessary, one option is to call the geometryEngine to get the distance between the center and any one of the points. ... View more

Have you tried using the PromiseUtils 'debounce' method:  https://jscore.esri.com/javascript/latest/api-reference/esri-core-promiseUtils.html#debounce  ... View more

Pete,    I believe the issue you are seeing is that the attribute value you are editing will have no effect on the defintionExpression or renderer of that feature layer and that is why the layer does not change.  The "Vlakken - gereed" layer is the one that that will be affected by the edit and is the one we want to call refresh() on. https://codepen.io/john-grayson/pen/dyoVKqX?editors=1001  ... View more

Working with the correct layer that is already in the view is one issue we can address simply.  Unfortunately, I'm still confused as to what you're trying to do and what is expected behavior.  Some additional checks would be to look at the renderer and the  definitionExpression property of the layer(s) to make sure they don't conflict with the edits being made.  Currently, your code only works with and edits 1 layer.  However, your Web Map has 3 Feature Layers and your comment about a FeatureLayer having 2 layers is misleading; a FeatureLayer instance only references 1 layer as indicated by the 'layerId' property.  Also, I don't understand how changing the 'Dat_uitv' value will affect either the rendering or defintionExpression, so what is it you expect to happen when you update this value? Here's a modified version of the codepen, but I still don't understand what the overall goal is for this task: https://codepen.io/john-grayson/pen/dyoVKqX?editors=1001  ... View more

To find a layer that is currently in the view, you can find it via the 'layers' collection of the map: view.when(()=>{ const myFeatureLayer = view.map.layers.find(layer=>{ return (layer.title === "Vlakken - gereed"); }); console.info(myFeatureLayer.title, myFeatureLayer.id); );‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The id of the layer in the Web Map is different than the id of the portal item. ... View more

Is your intent to work with the layers in the Web Map?  If so, you should find the specific FeatureLayer you want to update that has been added to the map (via the Web Map) instead of creating a new instance. ... View more