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
Proposal: function to create a raster from a bounding box #276
Comments
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 20, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 20, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 20, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 20, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 20, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 21, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 21, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 21, 2022
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Dec 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the HRA rewrite, it was helpful to be able to create a raster directly from a bounding box (function implementation and where it's used) rather than by creating a vector of the bbox for the more circuitous
pygeoprocessing.create_raster_from_vector_extents
.I propose creating a new function that derives from the HRA implementation with the following modifications:
target_nodata
will be a required parameter, to matchcreate_raster_from_vector_extents
.The text was updated successfully, but these errors were encountered: