Check for regular chunks before writing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
If chunks are irregular (for instance we had problems due to this previous bug https://github.com/scverse/spatialdata/issues/821), an error is raised upon saving. We could catch this possible error early by moving the code to check for regular chunks (it's a private function from dask.array, see here https://github.com/scverse/spatialdata/pull/861) into RasterModel.validate().
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 with RasterModel.validate() and the regular-chunk check from dask.array referenced in pull request 861; review issue 821 for the prior irregular-chunk failure. Confirm validation runs before saving and verify that irregular chunks produce the intended early error rather than failing during save.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100