-
Notifications
You must be signed in to change notification settings - Fork 13
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
Specific file listed in errors? #96
Comments
Yeah it's unfortunate that the file name is not mentioned here. In this package we hook onto the error handler of GDAL, using the API GDAL provides for that. The source code for that is here: https://github.com/JuliaGeo/GDAL.jl/blob/79560db2e494dd41c800df30ee8ab26384360a5c/src/error.jl Lines 36 to 38 in 79560db
So the message that you are seeing is not coming from this package, but from GDAL itself. So the best location to improve this would be in GDAL, you could submit an issue here: https://github.com/OSGeo/gdal. ArchGDAL is using the same error handling. I think it would make it unneccesarily complicated if we were to try to augment some of the error messages that we deem not good enough. This error is thrown because GDAL decides it wants to throw an error. That gets caught in our error callback. |
Sure I get that |
Looks like this comes from https://github.com/OSGeo/gdal/blob/20d44a181f73b87ebb7c1660498bb9e78e572e54/gdal/frmts/aaigrid/aaigriddataset.cpp#L187, so the AAIGrid driver. We're using a somewhat older GDAL version at the moment, 3.0.4, but it's the same in GDAL master. Grepping |
They literally fixed it already: OSGeo/gdal#3054 |
Gotta love Even's dedication :) |
It would be nice if an error like this reported the file name in question:
Especially when looping over large datasets with hundreds of files. I'm not sure how easy that is to do or where to do it exactly - this could be something for ArchGDAL.jl
The text was updated successfully, but these errors were encountered: