Closed Zach10a closed 2 years ago
I cannot seem to recreate this anymore on the latest develop
branch code. Is this is still an issue?
Managed to recreate this, will be working on it now the new version is out.
It appears that the issue is due to the max and min x and y values being shown as infinite when it is resized. Something to do with the bound function.
NaN issue only occurs when the user attempts to resize when the image has been zoomed in on for the second time. It comes down to the function in line 34 of utils. The proj.transform appears to be spitting out infinites.
Does this actually cause any problems, or is it a spurious console output? If the former is false, then this can be closed.
So this is caused by bounds_poly
being passed in as None
to the function. You can add a check for this and just return sensible/default raster dimensions if it is the case otherwise calculate as normal.
Resizing cases the following error message:
Fixing #20 would solve this