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
Values read by NCDatasets and ZarrDatasets were inconsistent with xarray for this file, because it was interpreted as Int16 data but the attributes had an _Unsigned = true key, so the element type should have been UInt16 instead.
using AWSS3, FilePathsBase
download(p"s3://noaa-goes16/ABI-L2-SSTF/2020/210/00/OR_ABI-L2-SSTF-M6_G16_s20202100000205_e20202100059513_c20202100105456.nc", "noaa.nc")
using Rasters, NCDatasets
Raster("noaa.nc")
# or whichever other way you care to load it
In short, this is a lot of work for some feature that never made it to the CF conventions and has been long
been superseded by native unsigned types in NetCDF4.
But if somebody would like to make a PR, I am happy to review it.
I guess that this can be used similar to other special attributes like scale_factor, units which affect also the element type of an array:
Describe the bug
Values read by NCDatasets and ZarrDatasets were inconsistent with xarray for this file, because it was interpreted as
Int16
data but the attributes had an_Unsigned = true
key, so the element type should have beenUInt16
instead.You can see the debugging history in rafaqz/Rasters.jl#735
To Reproduce
Please provide a minimal julia code example which reproduces the behavior (bug, performance regression, ...).
Expected behavior
I would expect that the array is somehow reinterpreted to the appropriate unsigned type.
Environment
The text was updated successfully, but these errors were encountered: