Non-uniform spatial resolution of cutouts leads silently to unexpected results
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 402
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Version Checks (indicate both or one)
-
I have confirmed this bug exists on the lastest release of atlite.
-
I have confirmed this bug exists on the current
masterbranch of atlite.
Issue Description
Atlite adopts the silent assumption of uniform spacing of latitude and longitude axes that may not hold true.
For unknown reasons, the cutouts generated with atlite, sometimes, do have a non-uniform spacing.
See:
When that happens, the assumption of uniform spacing does not hold, though it is used, and the result is that the calculations are not performed on the expected region
Reproducible Example
Expected Behavior
No response
Installed Versions
Replace this line.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with an atlite cutout and inspect the latitude and longitude axes for non-uniform spacing. Trace where the cutout axes are used in calculations and determine how the affected region is selected. Done means non-uniform spacing is handled or rejected explicitly, so calculations do not silently use an unexpected region.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100