Latest Contributions by RyanSutcliffe

A very late response to an old post, but the trick I recently found that, so far, has gotten around this problem well is to hold off calling .refresh until after the layer has finished loading: So the setThreshold function in the codepen becomes something like: function layerCompletelyDrawnAndVisible(layer, view) { let [watchUtils] = await loadModules(["esri/core/reactiveUtils"]); let layerView = await view.whenLayerView(layer); let layerId = await new Promise((resolve) => { if (layerView.updating) { watchUtils.when( () => !layerView.updating, () => { return resolve(layer.id); }, { once: true, } ); } else return resolve(layer.id); }); return layerId; } function setThreshold() { thresholdVal = parseInt(threshold.value); let { colors, stops } = getRasterStopsAndColors( 5000, thresholdVal, seedColors ); //lercLayer.max = 3000; lercLayer.threshold = thresholdVal; lercLayer.stops = stops; lercLayer.colors = colors; //lercLayer.refresh(); layerCompletelyDrawnAndVisible(lercLayer, view).then(v => lercLayer.refresh()) } // @ts-ignore threshold.addEventListener("change", setThreshold); that seems to deal with the problem nicely!   ... View more

Posted request for 512x512 3D Raster Tile layer support or 512x512 tiled basemaps here! Go give it a kudos to get this idea traction. ... View more

The testing we did was far from anything authoritative but we noted on comparison that because of browser  limits of 6(?) concurrent fetches to a domain it was noticeably faster to download 512x512 tiles due to less fetches. We looked at load time of a static area on app load. Of course this was done on large hi-res screens with fast CPU. Results would probably vary based on device. ... View more

Thanks for the clarification. We've seen performance benefits from using 512x512 tile sizes over 256x256 on high-res or large screens. Removing the basemap isn't really ideal although I confirmed that it works. If supporting mixed tile sizes (even limited to 256 and 512) in 3D is complex, perhaps another idea would be ESRI 512x512 basemaps? Something I can raise over in ideas. ... View more

The video was from Firefox. Note that it is import to return to your initial zoom extent. You want to zoom in, say 4x, then zoom back out 4x to return to the initial zoom level. I probably should have added a zoom element displayed in the codepen to show that. I wasn't able to reproduce the problem every time. If I changed the threshold and waited for a few seconds too long before zooming I did not seem to get the issue. Also note there it looks like there are tiles that aren't drawing at all now whereas my initial example where we'd see the old filtered tile data remain? At the office here I was eventually able to reproduce the issue (ff) though it too a few tries. In Chrome the only way I was able to reproduce in the office now, is if I throttle the network speed. Then the problem is really easy to reproduce in your example (missing tiles, not old cached tiles). Try setting the network to 'Fast3G' to see what I mean. Its certainly tricky though. Let me know if there's anything else I can do. Thanks for looking into.   ... View more

I just tested your code pen but I am still able to reproduce the problem I demonstrated above. Or at least there seems to be tiles not drawing correctly. Here is a video: ... View more

Thanks for the update. I just tested our app with the next version of the ArcGIS JavaScript API ArcGIS Maps SDK and it works! Thank you for the fix. Look forward to the upcoming release of 4.27. ... View more

Thanks for your prompt response. The problem is that these request for the count of features take really long-- as I've described in the linked posts. This prevents the layers from loading in a SceneView the same as it did in our MapView. In 2D, disabling "snapshot mode" allowed those layers to continue to work because these types of requests were no longer made. I would like to do the same in a SceneView.  Perhaps disabling these calls to 'returnCountOnly' is not possible? I know that in a SceneView, there are parameters like maximumNumberOfFeatures that are applied to LayerViews.  More Detail: When I load the sceneView, I see two different types of calls for returnCountOnly for each layer: there is first one for the total layer count (where1=1). Subsequent to that, there is calls for the count within a specific area (tile). I think it is the first that are the problematic ones.  I will do some sandbox testing to check further. If you can clarify that disabling these calls for returnCountOnly are not able to be disabled for SceneView and perhaps provide a bit of guidance why that would probably answer this question.  I might open different ones to explore other ways to deal with this problem as I test more. Since I can't share our own large MapService layers, I'll probably start by pursuing the question/issue further with ESRI Canada technical support. ... View more

I just realized that I seem to be sometimes having the same problem when creating a SceneView and the above doesn't fix it there. I've created a new Post for help with this. ... View more