Incremental reading APIs
Open
Nobody has claimed this yet.
I/O 💿
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
We have a single read() function that is internally reading the single elements one by one as private functions. We need to expose public APIs for incremental reading, as we do also for writing.
Related to https://github.com/scverse/spatialdata/issues/521 and https://github.com/scverse/spatialdata/issues/293.
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 tracing the existing read() function and its private element-reading helpers, then compare them with the public writing APIs. Review related issues #521 and #293 to clarify the intended incremental-reading design; done means the required public reading APIs are exposed with behavior consistent with the existing writing interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100