Latest Contributions by JohnGrayson

Are you using a GraphicsLayer, or a FeatureLayer defined with client-side Graphics?  Here's a simple CodePen that shows how to apply client-side updates to either one: https://codepen.io/john-grayson/pen/oNeWLqr   ... View more

BTW: I updated the codepen to show how we can use the dynamic ElevationSampler from the GroundView to update the mesh graphic as you move around the view.  For really long lines like the one you show in your screenshot, it will get tricky as the densification distance will affect both performance and accuracy.  I would recommend you break the line into smaller sections so each one will require less densification and thus display more accurately individually when viewing from a nearby perspective, and that will also improve performance.  If desired, you could also factor in the distance between a line and the current view position to make further refinements on the overall user experience. ... View more

The bottom of the mesh geometry is only calculated once and we didn't ask for a specific resolution, so that is one possible aspect to research for your use-case.  Also the ground in the display is dynamic but our mesh is not; if you want your geometry to more closely follow the ground as the user interacts with the display you could listen to the elevationSampler 'change' event and regenerate the mesh geometry when the user stops interacting with the display.  Also, the distance used to densify the path will greatly affect this task.  These are all considerations to investigate for your use-case. ... View more

On startup we waited for the groundView elevationSampler to be available after the view is finished updating the first time.  There are other ways to model this workflow, for example, creating an elevationSampler just for the area of interest and only when needed.  I've updated the codepen to show this other alternative.  How we model the geometry will depend on your use-case and workflow. ... View more

So you want to have two different exaggerations in the same display?  I don't think that using a clippingArea or setting the fullExtent will not work for that use case.  You'd have to modify the elevation values in such a way where you provide a smooth elevation transition at the edges of the overall extent of your area of interest.  Another possibility is to publish a new Elevation Layer that already has the elevation values exaggerated and smoothed at the edges to ensure a good visual transition between your area of interest and the rest of the display. ... View more

One possible way to do this is to use a local viewing mode and set the clip area as needed.  I updated the codepen example to show this concept. ... View more

Here's a modified version of the example that shows how to control which elevation values get exaggerated: https://codepen.io/john-grayson/pen/YzxXKLO   ... View more

Gary, for this use-case, I would take the Graphic that is currently being edited in the previous view and re-created it in the GraphicsLayer being used by the SketchViewModel of the new view, then instead of 'create', call 'update' using the new Graphic you just re-created in this new view. ... View more

I wonder if the 'Pricing' tab at the top of the page (and linked in the post by Andy) might have some of the details you're looking for: https://developers.arcgis.com/pricing/  If not, you should reach out directly as Andy suggested. ... View more

The layer displays via the online Map Viewer, but there are many complex features at the default minimum scale, so you might want to adjust it so the feature visibility is more appropriate for the type of data. ... View more

The URL seems to be for a FeatureLayer so try: var dynSvc = new FeatureLayer("https://services8.arcgis.com/HPJsu0I9OjNDnQ7I/arcgis/rest/services/tl_2020_42_tabblock20_ViewLayer/FeatureServer/0", {"opacity": 0.5});   ... View more

Thought it was a different issue.  Yes, I can see the error being thrown when removing the features.  I can't spot anything obvious in this sample, especially since it only happens when we enable feature reduction and only when removing features.  Unless someone else in the community can find a workaround, I think this is probably best handled by logging in a new incident via Tech Support. ... View more