-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store band specific attributes in coordinates #81
Comments
Not much point in adding nodatavals: rasterio/rasterio#1859 |
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. |
Yes, it is also related to #296 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 theband
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:
nodatavalsAdditionally. I am thinking about adding a
profile
and ormetadata
coordinate to store theprofile
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.
cc: @alfredoahds @justingruca
The text was updated successfully, but these errors were encountered: