JuliaDataCubes / JuliaDataCubes/YAXArrayBase.jl
make getspecialmetadata interface
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 3
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
We should have an interface to handle special metadata like for example crs, offset, scale , multiscales.
The idea would be that the frontend e.G, YAXArrays, Rasters... could define which special metadata keys they need and the backend can specify which special metadata keys it can provide.
This would also help in handling fill_value because this is a special key in netcdf but not in Zarr.
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
No files, tests, or entry points are identified in the issue. Start by mapping the current metadata handling in YAXArrayBase.jl and how frontends and backends exchange metadata; done means an agreed interface covering crs, offset, scale, multiscales, and fill_value across NetCDF and Zarr.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100