Open bossie opened 3 months ago
Hey @bossie thx for reporting! Are u sure that's the GeoTrellis issue and not the underlying bindings? Have u tried to reproduce it via the bare bindings code?
I wonder if smth could be swallowed on the bindings lvl.
Hi @pomadchin. Thanks for the quick response.
Hey @bossie thx for reporting! Are u sure that's the GeoTrellis issue and not the underlying bindings? Have u tried to reproduce it via the bare bindings code?
I have not so it's entirely possible that it's within the bindings code but I'm not familiar with that.
What I initially tried was significantly lowering geotrellis.raster.gdal.number-of-attempts
because that seemed to make it fail but:
So I guess that's unrelated and I'm on the wrong track here.
Oooh interesting. Yest, that's definitely the bindings thing: https://github.com/geotrellis/gdal-warp-bindings/blob/v3.9.0/src/com_azavea_gdal_GDALWarp.c
That's been a way to fight with the not nicely fited for the JVM parallelism GDAL Datasets access.
Check the completely opposite scenarios:
Describe the bug
I can create a
GDALRasterSource
from a corrupt JPEG2000 file and successfully read from it. I would expect it to throw an exception instead of silently proceeding with wrong data.To Reproduce
This will successfully read a corrupt JPEG2000 file and write it to a GeoTiff that looks funky. GDAL will output erorr messages along the way look like this:
Expected behavior
I would expect it to throw an exception instead of silently proceeding with wrong data.
gdalinfo
for example, will output error messages instead:Environment