-
Notifications
You must be signed in to change notification settings - Fork 29
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
Remove GDAL's Python bindings #222
Conversation
8d3005d
to
7ed4f7c
Compare
This changes the API of the cogify function.
This helps debug dict differences better.
This requires refactoring `add_raster_to_item` to use rasterio instead of GDAL bindings. During this refactor, I discovered that the original implementation was not correctly handling the top bound of the histogram calculation, and so the last bin value was one too low in the tests. The test case was corrected.
7ed4f7c
to
988c691
Compare
@gadomski I think the cogify function could be removed and left to rio-cogeo or gdal_translate, but this PR is fine. Rasterio's copy function calls GDALCreateCopy and thus should be a pretty complete COG maker. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I just had some comments around typing and possible parametrizing some tests. Nothing that should hold back this PR, though.
Related Issue(s): #216, #217
Description: To simplify our dependency tree, this PR removes direct use of the GDAL Python bindings (used in the
addraster
command). This represents a breaking change because it changes the function signature ofcogify
.Additional fix:
cogify
to use rasterio instead of a system call togdal_translate
. This is instead of Remove cogify #217 (and Remove cogify #217 should be closed if this PR is merged).cc @sgillies
Closes #216
Closes #217
PR checklist:
scripts/format
).scripts/lint
).scripts/test
).