JuliaDataCubes / JuliaDataCubes/YAXArrays.jl
using Metadata type from DimensionalData instead of Dicts
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 132
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
I am wondering whether we should switch to using the Metadata type from DimensionalData.Lookups instead of Dictionaries.
I ran into the problem because I tried to save a DimArray via savecube into a Zarr store and then it failed because the merge between a Dict and a NoMetadata type failed.
I think, it would be good to streamline this, so that users would not have to deal with the mix of Metadata types.
Contributor guide
No contributing guide indexed for this repository
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 savecube when writing a DimArray to a Zarr store, focusing on the merge between Dict and NoMetadata values. Review how DimensionalData.Lookups.Metadata is used alongside dictionaries, then determine the scope of making metadata handling consistent. Done means the savecube path no longer fails from mixing these metadata types and users do not need to handle both forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100