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
The "old" NetCDF 3 format doesn't have explicit support for unsigned integer types and therefore a recommendation/convention exists to set the variable attribute _Unsigned='true', see NetCDF docs, section Unsigned Data.
Are there any plans to interpret the _Unsigned attribute?
I'd really like to help out, but I fear I still don't know enough about dask to provide an efficient PR for that.
My workaround is to manually convert the variables in question which are of type int8, same data as mentioned in #1576:
unsigned_var = signed_int8_var & 0xff
which results in an int16, which is ok but still 1 byte more than the desired uint8.
The text was updated successfully, but these errors were encountered:
We are trying to get everything together for a big 0.10 release, so it will be a bit longer. I don't have a timeframe yet, but hopefully in a week or two!
The "old" NetCDF 3 format doesn't have explicit support for unsigned integer types and therefore a recommendation/convention exists to set the variable attribute
_Unsigned='true'
, see NetCDF docs, section Unsigned Data.Are there any plans to interpret the
_Unsigned
attribute?I'd really like to help out, but I fear I still don't know enough about dask to provide an efficient PR for that.
My workaround is to manually convert the variables in question which are of type
int8
, same data as mentioned in #1576:which results in an
int16
, which is ok but still 1 byte more than the desireduint8
.The text was updated successfully, but these errors were encountered: