Write some simple guidelines for saving data that will be visualized with deck.gl-raster.
For example in Zarr animation, you don't want to load different frames as separate Zarr chunks. If you plan to animate data, you want to be able to load one or a few 4D chunks, rather than a separate chunk for every timestep. cc @gadomski
This should also point to other more substantial guides including https://guide.cloudnativegeo.org/ and https://developmentseed.org/datacube-guide/latest/visualization/overview.html
Write some simple guidelines for saving data that will be visualized with deck.gl-raster.
For example in Zarr animation, you don't want to load different frames as separate Zarr chunks. If you plan to animate data, you want to be able to load one or a few 4D chunks, rather than a separate chunk for every timestep. cc @gadomski
This should also point to other more substantial guides including https://guide.cloudnativegeo.org/ and https://developmentseed.org/datacube-guide/latest/visualization/overview.html