Open jsolbrig opened 4 months ago
It appears this may have been done intentionally to mask false errors: https://github.com/rasterio/rasterio/blob/main/rasterio/_env.pyx#L91 I agree it is probably best to raise an issue with rasterio so they can determine why the colormap needs to be written first now.
Bug Report
This may be an issue with GDAL or rasterio rather than with GeoIPS. If so, please raise an issue on the rasterio repository to report the problem. It's a problem that might be masking other errors, too, so it's worth submitting an issue or fixing as appropriate, even if we no longer encounter this issue after fixing #544.
What happened?
In the
geotiff_standard
OutputFormatter, whendst.write_colormap(1, cmap_dict)
is called, if GDAL raises an error (e.g. #544), the error is printed toLOG.info()
rather than actually raising an exception. In the case of #544, this masked the error that was occurring and allowed processing to continue.What should have happened?
When the GDAL error was encountered, a fatal exception should have been raised.
Suggested Solutions
Determine whether the log statement is coming from GDAL, rasterio, or geoips and:
I'm fairly sure that rasterio is the culprit here and that it is calling
LOG.info
when it should be raising an error in this situation.Replicating the Issue
pyproject.toml
to requirerasterio==1.3.10
../tests/scripts/ahi.tc.WV.geotiff.sh > ahi.tc.WV.geotiff.sh.log
.The resulting log file should contain this line which indicates that GDAL encountered an error but the error was unhandled and inappropriately passed to
LOG.info
:Environment
Checklist for Completion
Related Issues
544