We are developing a web based application that lets the user create a cutout for cesium. This gets shown to the user in realtime. It works but we are facing 2 issues:
The tilesets dont show updated shapes in the linked CartoPoly cutout without refreshing the tilesets. We also tryed to delete the rasteroverlay and cartoPoly everytime there is a change and reference it again in the tileset but we dont get an update for the cutout shape.
Because of the first point we have to refresh the tileset a lot. This leads to the problem that sometimes it doesnt how and we get the quota error (429).
Our workaround is to reduce the tileset quality while the user is making the cuout shape and also reducing the tileset refreshes to 1 every 3 second. My question is if there is a better way to handly this kind of situation and if not, if there are other workarounds to reduce the calls we have to make for the tileset refreshes.
Are you using the Refresh function on the raster overlay? If so, it sounds like you’re doing the right thing, and it’s unfortunate to hear that it’s not working. Could you share a Blueprint or some code so we can replicate what you’re doing?
We also just merged a Github PR that includes improvements to the life cycle of the overlay itself, which might relate to your issue. But we can be more certain when we have a minimal reproducible example. Thank you
We used the refresh node on the tileset itself. I will try to use it on the raster overlay this sounds good. I will give an update as soon as i ran some tests.
