python interpreter crashes on raster.save about telluric HOT 7 CLOSED

Original issue was fixed in GDAL couple of hours ago: OSGeo/gdal@f7c27a8. It is possible to use the similar approach for calculating max factor value: if we already have a 1x1 overview then don't create a new one.

from telluric.

It is the overview code,
disable the overviews and it works:

rr.save('demo.tif', overviews=False)

the problem is the factor calculation

https://github.com/satellogic/telluric/blob/master/telluric/georaster.py#L565

if we create overview only upto factor 32, then the code will pass.

How can we know if the factors make sense?

from telluric.

We can introduce maximum width or height of the smallest overview level like it has been done in recent GDAL (minsize option of gdaladdo).

from telluric.

Thanks @drnextgis! I guess a fix will be released as part of GDAL 2.3.1, or 2.4.0 at most? In any case we should support older versions as well, so perhaps we should do as you say:

We can introduce maximum width or height of the smallest overview level like it has been done in recent GDAL (minsize option of gdaladdo).

from telluric.

Also, thanks for reporting this upstream: rasterio/rasterio#1333

from telluric.

@Juanlu001 what do you think the best place to fix this issue: here or directly in Rasterio?

from telluric.

@drnextgis The rasterio developers have labeled the issue as post-1.0, so I think it would be positive if we have a workaround in place ourselves. But I will leave this issue as good first issue, for potential contributors.

from telluric.