Hi,

TL;DR; I would like to remove part of the API (creation and open options)
from the TileDB driver and move it to the GDAL multi-dimensional API.

The TileDB GDAL driver (new in 3.0) supports multiple attributes per pixel
value and also a version of copying netCDF and HDF files within the
standard SUBDATASET model. It seems this is better suited to the
multi-dimensional API within GDAL
https://gdal.org/user/multidim_raster_data_model.html

I didn't document these additional pixel attribute options in
https://gdal.org/drivers/raster/tiledb.html#creation-options and you would
only really know about them if you looked at the tests -
https://github.com/OSGeo/gdal/blob/master/autotest/gdrivers/tiledb_write.py#L113

Any objections if I remove this functionality and support for SUBDATASETS
and move it to the multi-dimensional API? It makes this driver easier to
maintain and use.

Norman
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to