Refactor and speed-up SpatialData query funtions
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Task for the Proteomics Hackathon (Berlin, Mar 2026).
Relevant issues:
- https://github.com/scverse/spatialdata/issues/225
- https://github.com/scverse/spatialdata/issues/724
- https://github.com/scverse/spatialdata/issues/742
- https://github.com/scverse/spatialdata/issues/233
- https://github.com/scverse/spatialdata/issues/893
CC @MeyerBender
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 reviewing the related issues #225, #724, #742, #233, and #893 to understand which SpatialData query functions are in scope. The issue does not name files, tests, benchmarks, or acceptance criteria, so clarify the target functions and define how the speed-up and refactor will be measured before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100