Please answer the following questions for yourself before submitting an issue.
- I am running the latest version
- I checked the documentation and found no answer
- I checked to make sure that this issue has not already been filed
- I'm reporting the issue to the correct repository (for multi-repository projects)
Please complete the following sections of the issue template, removing irrelevant components.
Remove this section if your issue is not a bug. Make sure to add the Type: Bug label if it is.
Please help provide information about the failure.
(Expected behavior that isn't occurring)
(Description of the current, buggy behavior)
Please provide detailed steps for reproducing the issue.
- Step 1
- Step 2
- Etc.
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
- OS:
- Python version:
cw-eval
install method (Conda, pip, Docker):cw-eval
version (release vs. dev) - if you're using an older release, please update and ensure your issue isn't resolved:- Additional relevant environment details (e.g. using a virtual environment or not, version of GDAL and GDAL install method, etc.)
Please include any relevant log snippets, python shell commands and tracebacks, etc. here.
Remove this section if your issue is not a feature request. Make sure to add the Type: Enhancement label if it is.
Please describe the feature you'd like implemented.
If your feature request includes changes to the cw-eval
API, describe that here. Note that any changes to required arguments or argument order in the API will only be made at a major version release. See the contributing guidelines for additional details.
If you did not already include references above, list references to relevant PRs, issues, or other pages here.
Make sure to select a Type label for your issue. The repo maintainers will add other labels, milestones, and projects (if applicable).