-
Notifications
You must be signed in to change notification settings - Fork 65
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
NDR use of cutline is intolerant of minor geometry issues #1412
Labels
Comments
phargogh
added
bug
Something isn't working
in progress
This issue is actively being worked on
labels
Sep 15, 2023
phargogh
added a commit
to phargogh/invest
that referenced
this issue
Oct 6, 2023
phargogh
added a commit
to phargogh/invest
that referenced
this issue
Oct 6, 2023
phargogh
added a commit
to phargogh/invest
that referenced
this issue
Oct 6, 2023
phargogh
added a commit
to phargogh/invest
that referenced
this issue
Oct 6, 2023
phargogh
added a commit
to phargogh/invest
that referenced
this issue
Oct 6, 2023
phargogh
added a commit
to phargogh/invest
that referenced
this issue
Oct 9, 2023
This is more compatible with more versions of pygeoprocessing. Using numpy to derive the dtype, while functional, was more complicated and feature-rich than what we actually need here. RE:natcap#1412
phargogh
added a commit
to phargogh/invest
that referenced
this issue
Oct 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We had a recent issue on the forums where the issue was that the user had 3 ring self-intersections (see below) that were causing the cutline option to
gdal.Warp
to fail due to invalid geometry.Years ago we removed the
cutline
functionality frompygeoprocessing.warp_raster
because of its fragility, so I think we should refactor these masking function calls to either usepygeoprocessing.mask_raster
, or a combination ofrasterize
andraster_map
.The text was updated successfully, but these errors were encountered: