You know I like to complicate things 🙂
I'm mostly worried about not compatibility between our format and others.
So, I'm doing that. At least is not so difficult to pack in subdatasets and
make another iteration to translate them.
People just remember about the -sds option if want to translate al
Le 21/05/2025 à 20:53, Abel Pau a écrit :
Okay, thanks!
So the interpretation we are aiming for is option *a)*:
Each band is treated independently, and each one has its own NODATA
value. The NODATA value of one band is unrelated to that of the others.
That said, the question is whether this beh
Okay, thanks!
So the interpretation we are aiming for is option a):
Each band is treated independently, and each one has its own NODATA value. The
NODATA value of one band is unrelated to that of the others.
That said, the question is whether this behavior is consistently supported
across all for
Abel,
there is a subtelty:
a) If bands may have invalid pixels at different locations on different
bands, and that those bands have a different nodata value, then using
GDALRasterBand::SetNoDataValue() is the way to go.
b) If a given pixel is invalid only if its value on all bands matches
On Wed, 21 May 2025, Schumacher, Mia via gdal-dev wrote:
I am trying to use new gdal raster reproject to georeference image chunks
using ground control points. I figured that for some of these chunks, due
to ship movement, the lower left & lower right image coordinates are
switched, which (und
Dear gdal community,
I hope this is the right spot to ask questions?
I am trying to use new gdal raster reproject to georeference image
chunks using ground control points. I figured that for some of these
chunks, due to ship movement, the lower left & lower right image
coordinates are switc
Mia,
please file an issue at https://github.com/OSGeo/gdal/issues with the
source dataset + command line to reproduce
Even
Le 21/05/2025 à 14:56, Schumacher, Mia via gdal-dev a écrit :
Dear gdal community,
I hope this is the right spot to ask questions?
I am trying to use new gdal raster
Hello,
I am implementing a driver that allows different NODATA values for each band in
a dataset.
>From what I understand in the documentation, I should use the NODATA_VALUES
>metadata item to document these values. However, I don't see a clear way to
>indicate that a specific band has no NODATA
Hi,
On writing side nodata=none seems to work.
gdalwarp -of VRT -dstnodata "0 none 0" p4433h.tif nodata.vrt
gdalinfo nodata.vrt
...
Band 1 Block=512x128 Type=Byte, ColorInterp=Red
NoData Value=0
Overviews: 6000x6000, 3000x3000, 1500x1500, 750x750, 375x375, 188x188
Band 2 Block=512x128 Type=B
