I’m evaluating TileDB for storage of dense 3D model output arrays. Only 16 bit precision is required and by converting our float64 input data to int16 we get much better compression ratios and the on disk size of the TileDB ends of being ~15% of original.
The builtin scaling of xarray/netCDF handles this precision reduction well but I don’t see anything similar in TileDB.
Is there a way to have TileDB handle this, or is there a good pattern for storing the scale factor in metadata? Right now I’m doing the transformation at the edge of read/write to TileDB.