JuliaDataCubes / JuliaDataCubes/YAXArrays.jl
savecube does not write .zmetadata file for zarr data
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 132
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
I am not entirely sure what the purpose of the .zmetadata file is and therefore I am not sure whether this is supposed to be written or not.
This is just something that is different when opening and saving one of the Geozarr examples.
I will add the link to the example datasets when I have a more reliable internet connection
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 reproducing the difference when opening and saving one of the Geozarr examples, then investigate the purpose of the .zmetadata file and whether savecube is expected to create it. Done means the intended behavior is established and savecube handles the file accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100