This used to not be the case but it's suddenly popping up, I don't know what happened.
Suddenly the 'bounds' parameter from stackstac.stack function messes up the original coordinates of the images.
When using the 'bounds' parameter, instead of preserving the original x/y coordinnates, stackstac modifies them and they'll give you float values:
This used to not be the case but it's suddenly popping up, I don't know what happened.
Suddenly the 'bounds' parameter from stackstac.stack function messes up the original coordinates of the images. When using the 'bounds' parameter, instead of preserving the original x/y coordinnates, stackstac modifies them and they'll give you float values:
Will give you
While removing the 'bounds' will give you the
will give you the original integer like x, y coordinnates