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
Currently there are band-specific attributes stored in the attrs. However, this can be potentially lossy when performing xarray operations. So, I am thinking about storing them in the coordinates as arrays along the band dimension. This will also be useful when selecting a specific band as you will only have the subset of data associated with the band.
Proposed coordinates:
nodatavals
scales
offsets
descriptions (maybe)
units (maybe)
Additionally. I am thinking about adding a profile and or metadata coordinate to store the profile information from the raster not stored in other attributes to persist when writing. For example - compression, tiling, etc...
This should make things simpler and more reliable for #76.
Is this related to the issue I'm seeing? Loading a geoTIFF with multiple bands, with their names stored in each band metadata, only the first one is loaded in the attrs:
Activity
snowman2 commentedon Jan 22, 2020
Not much point in adding nodatavals: rasterio/rasterio#1859
clausmichele commentedon Sep 21, 2022
Is this related to the issue I'm seeing? Loading a geoTIFF with multiple bands, with their names stored in each band metadata, only the first one is loaded in the attrs:
rioxarray output:
gdalinfo output:
I attach the geoTIFF I'm using for further tests.
S2_L2A_data.zip
snowman2 commentedon Sep 21, 2022
Yes, it is also related to #296