Consider adding `.uns` or `.attrs` to `SpatialData`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Consider adding metadata to the SpatialData level. This has been asked by @quentinblampey and will also be required for storing coordinate transformations for this refactoring: https://github.com/scverse/spatialdata/milestone/2
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 at the SpatialData object and review milestone 2, especially the stated need to store coordinate transformations. Determine the metadata model and whether .uns or .attrs fits; the work is done when the chosen approach supports SpatialData-level metadata and the refactoring requirements.
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
- 25/100