Sean,
Le 09/11/2022 à 01:08, Sean Gillies a écrit :
Argh, I typed "unsigned char" when I meant "signed". Changing GDT_Byte
to *signed char* is too big of a change, I guess?
I don't believe that would be something reasonable to consider. The
impact of such a change would be huge on the GDAL
Even,
Argh, I typed "unsigned char" when I meant "signed". Changing GDT_Byte to
*signed char* is too big of a change, I guess?
I like the plan for PIXELTYPE.
Sorry about the noise, everybody!
On Tue, Nov 8, 2022 at 5:04 PM Even Rouault
wrote:
> Sean,
>
>
> Changing GDT_Byte to unsigned char i
Sean,
Changing GDT_Byte to unsigned char is too big of a change, I guess? I
can work with that.
GDT_Byte semantic is already unsigned char / uint8. What did you mean?
Is there any advantage to a GDT_UInt8 type that can't be changed by a
PIXELTYPE option?
That would be super confusing if w
Sorry, please disregard my previous email (from my phone at lunch). I had a
poor recollection of the GDALDataType enum.
Changing GDT_Byte to unsigned char is too big of a change, I guess? I can
work with that.
Is there any advantage to a GDT_UInt8 type that can't be changed by a
PIXELTYPE option?
Le 04/11/2022 à 15:28, ni hao a écrit :
Hi list,
Is Sentinel-3's NetCDF-4 format supported in GDAL?
It can be read with the generic netCDF driver
It consists of many *.nc files and 'xfdumanifest.xml'
The manifest file is not read
If so, since which version?
Forever
Thank you!
__
Yes please! The friction from not having GDT_Int8 keeps coming up again
and again. It is extra rough on beginners who hit this case.
But I would like to hear any voices for not doing this incase there is
something I haven't thought of.
On Tue, Nov 8, 2022 at 2:43 AM Even Rouault
wrote:
> Hi,
Hi,
I've posted in https://github.com/OSGeo/gdal/pull/6634 a new RFC to add
a new GDT_Int8 data type, for signed 8-bit integer data, to the
GDALDataType enumeration, which cleans up the current support we already
have for that data type.
Even
--
http://www.spatialys.com
My software is free,
