Issue with aggregation when `.attrs` is replaced instead of `.attrs['transform']`
Open
Nobody has claimed this yet.
method: transforms 🔃
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
- I have found a weird bug with transformations (unrelated to this PR, but spotted during debugging), you can see the comment in https://github.com/scverse/spatialdata/blob/d10a42e0a349320343431083d785f710d2324dc5/src/spatialdata/_core/operations/transform.py#L438
- I will open a separate issue to track it.
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 comment around line 438 of src/spatialdata/_core/operations/transform.py and investigate the reported aggregation behavior when .attrs is replaced rather than .attrs['transform']. Reproduce the transformation case described there and define the expected result before adding coverage for the corrected behavior.
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
- 30/100