You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to ingest netCDF files into tileDB as Sparse or Dense Arrays. GDAL claims to be able to translate netCDF to DenseArrays with gdal_translate. I used the tool and got an array with quite a bit bigger dimensions then in the source data, so I do not really trust the tool. Also it loses the dimensionnames.
Hence tileDB only starts to perform better then standard netCDF in case of sparse array data (as described in the publication) I see great benefits in supporting netCDF files in form of a load_netcdf() method.
The text was updated successfully, but these errors were encountered:
cc @normanb about the GDAL issues, multidimensional support in GDAL is a bit of a hack (it's actively getting worked on in GDAL 3+), so I am not surprised there are issues in conversion.
You are right that having a native reader in python is probably what we should shoot for (and hdf5, rasterio, ...)
It would be nice to be able to ingest netCDF files into tileDB as Sparse or Dense Arrays. GDAL claims to be able to translate netCDF to DenseArrays with gdal_translate. I used the tool and got an array with quite a bit bigger dimensions then in the source data, so I do not really trust the tool. Also it loses the dimensionnames.
Hence tileDB only starts to perform better then standard netCDF in case of sparse array data (as described in the publication) I see great benefits in supporting netCDF files in form of a load_netcdf() method.
The text was updated successfully, but these errors were encountered: