Backed multiscale image, problems with scales and dims
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Possible bug with scales
Bug originally reported here from @aeisenbarth in the context of another issue: https://github.com/scverse/spatialdata/pull/348#issuecomment-1702672491.
Rasterschema.validate(MultiscaleSpatialImage) expects all scale levels to have a transform, but the backed image has only the transform in scale0.
Possible bug with dims
Bug originally reported here from @aeisenbarth in the context of another issue: https://github.com/scverse/spatialdata/issues/347
For backed labels, xdata is not a DataArray (where dims is ("y", "x")) but a DataTree where dims is Frozen({"y": 1633, "x": 1290}). See more details in the linked issue in points 2. and 3.
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 reading the linked pull request comment and issue #347 for the missing details about scales and dimensions. Investigate backed multiscale images and backed labels; done means scale validation handles transforms at every level and label data exposes the expected y/x dimensions.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100