(dimension_size, ...) ==
nBands
Is there a bug or an artificial limitation by the current netCDF driver
implementation ?
Pierre
> On 12 Mar 2024, at 14:16, Pierre Chatelier via gdal-dev
> wrote:
>
> Le 12/03/2024 à 13:48, Even Rouault a écrit :
>>
>> Le 12/03/2024 à
Le 12/03/2024 à 13:48, Even Rouault a écrit :
Le 12/03/2024 à 13:33, Pierre Chatelier a écrit :
But I can't figure out how to customize the , which is
Band1, Band2, Band3...
I tried GDALRasterBand::SetDescription(), but without success
Looking at netcdfdataset.cpp line 9625, the netCDF var
But I can't figure out how to customize the , which is
Band1, Band2, Band3...
I tried GDALRasterBand::SetDescription(), but without success
Looking at netcdfdataset.cpp line 9625, the netCDF variable name for a
band is extracted from the NETCDF_VARNAME band metadata item of the
source band.
dimensional API. Cf
https://github.com/OSGeo/gdal/blob/master/autotest/gdrivers/netcdf_multidim.py
. h5py is also quite convenient
Even
Le 07/03/2024 à 09:47, Pierre Chatelier via gdal-dev a écrit :
Hello,
I just had my first encounter with a NetCDF file. GDAL opens that
flawlessly, I can ide
Hello,
I just had my first encounter with a NetCDF file. GDAL opens that
flawlessly, I can identify the subdatasets and open/read them thanks to
the SUBDATASET_n_NAME, as advertised in
https://gdal.org/drivers/raster/netcdf.html
However, I am confused by the ability to create such a file wit
