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
We previously discussed having a convert_nodata option to Raster.astype() to ensure nodata is supported, and avoid problems when writing etc..., which is now the default:
However, if the type is the same, astype will still update the nodata value, which is not intuitive (made me look for a bug in tests for an 1h when running raster_equal(). Should we skip convert_nodata in the case where astype() is the same as the existing type, and (potentially) raise a warning?
The text was updated successfully, but these errors were encountered:
We previously discussed having a
convert_nodata
option toRaster.astype()
to ensure nodata is supported, and avoid problems when writing etc..., which is now the default:geoutils/geoutils/raster/raster.py
Line 1444 in 1594501
However, if the type is the same,
astype
will still update thenodata
value, which is not intuitive (made me look for a bug in tests for an 1h when runningraster_equal()
. Should we skipconvert_nodata
in the case whereastype()
is the same as the existing type, and (potentially) raise a warning?The text was updated successfully, but these errors were encountered: