We currently have a RasterLayer in deck.gl-raster which manages drawing a spatially oriented texture, and we have tile utilities (implementing Tileset2D) but then the actual implementation of the TileLayer is in COGLayer and now duplicated into ZarrLayer.
We should add a RasterTileLayer into deck.gl-raster package that abstracts a lot of the getTileData and renderTileData.
It should support a custom RasterTileset2D subclass. (I think like upstream TileLayer we can allow the user of RasterTileLayer to override the Tileset2D implementation?)
Perhaps we could look at the "geo cell layers" in upstream deck.gl, like how the A5Layer is super simple because it only defines indexToBounds.
Ideally this should be generic enough such that Lonboard can use it directly instead of its current extra code
We currently have a
RasterLayerindeck.gl-rasterwhich manages drawing a spatially oriented texture, and we have tile utilities (implementingTileset2D) but then the actual implementation of the TileLayer is in COGLayer and now duplicated into ZarrLayer.We should add a
RasterTileLayerintodeck.gl-rasterpackage that abstracts a lot of thegetTileDataandrenderTileData.It should support a custom
RasterTileset2Dsubclass. (I think like upstreamTileLayerwe can allow the user ofRasterTileLayerto override theTileset2Dimplementation?)Perhaps we could look at the "geo cell layers" in upstream deck.gl, like how the
A5Layeris super simple because it only definesindexToBounds.Ideally this should be generic enough such that Lonboard can use it directly instead of its current extra code