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
When I init a new instance of a geoarray, e.g. by its wrapper calls full_like, a new geoarray is created. BUT some attributes are copied over from the like-array, which makes sense but not for _fobj. This is done in geoarray/core.py, line 281, fobj is passed on. But in the write section of geoarray/gdalio.py line 160, _fobj is taken by default for creating the output GDAL bands from the new geoarray.
This means that all the previous data manipulation is pointless as the original array's _fobj is taken.
This should be changed, likely by removing _fobj from the argument list in geoarray/core.py.
(It took my like 2 hours to figure that out. I also assume that the current behavior leads to bugs.)
The text was updated successfully, but these errors were encountered:
When I init a new instance of a
geoarray
, e.g. by its wrapper callsfull_like
, a new geoarray is created. BUT some attributes are copied over from thelike
-array, which makes sense but not for_fobj
. This is done ingeoarray/core.py
, line 281,fobj
is passed on. But in the write section ofgeoarray/gdalio.py
line 160,_fobj
is taken by default for creating the output GDAL bands from the new geoarray.This means that all the previous data manipulation is pointless as the original array's
_fobj
is taken.This should be changed, likely by removing
_fobj
from the argument list ingeoarray/core.py
.(It took my like 2 hours to figure that out. I also assume that the current behavior leads to bugs.)
The text was updated successfully, but these errors were encountered: