Bounding box query APIs slowed down by join operations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
The edits in src/spatialdata_plot/pl/utils.py from this PR https://github.com/scverse/spatialdata-plot/pull/765/changes highlight an opportunity to improve performance in the bounding box query APIs.
I suggest to check this only after we are done with the coordinate transformation refactoring, since after that the code in spatial_query.py will become much easier to read.
CC @timtreis who worked on this in spatialdata-plot.
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
Wait until the coordinate transformation refactoring is complete. Then review the edits in src/spatialdata_plot/pl/utils.py from pull request 765 and read spatial_query.py, focusing on the bounding box query APIs and their join operations. Done means improving the performance of those queries without changing their intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100