-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GDALRasterSource will read corrupt jp2 successfully #3547
Comments
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.
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
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
The text was updated successfully, but these errors were encountered: