Using Dask `GeoDataFrame` for lazy representation of shapes.
Open
Nobody has claimed this yet.
element: points ⊙
element: shapes ▲
I/O 💿
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Feature that will be implemented as part of the IO refactoring.
To make things ergonomic, we should before/at the same time, use GeoDataFrame for points https://github.com/scverse/spatialdata/issues/233 and thus unify points and circles (https://github.com/scverse/spatialdata/issues/46, to be reopened if needed).
Related:
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 IO refactoring work and the linked issues 233, 46, 41, and 153 to understand the intended shape representation. The goal is a lazy Dask GeoDataFrame representation for shapes, while unifying points and circles through GeoDataFrame. No files, tests, or entry points are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100