JuliaDataCubes / JuliaDataCubes/YAXArrays.jl
Roadmap: Move DAT and registration.jl into separate package that depends on DiskArrayEngine
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 132
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
We are planning to further separate the loading of the data from the analysis and processing steps.
The way forward is to move the DAT module and the registration.jl code into a separate module which would then depend on DiskArrayEngine and should be able to work on all DiskArrays or DiskArray backed array types.
Then we would be able to process Raster and YAXArray similarly.
This move should also help in making the processing available for other large raster data from other fields such as astronomy or microscopy.
We would still need a good name for the new package.
@meggart
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 locating the DAT module and registration.jl code, then read how they currently connect loading with analysis and processing. Review the DiskArrayEngine dependency and the existing Raster and YAXArray paths. Done means the agreed package boundary and name are implemented so the processing works across the stated DiskArray-backed array types.
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
- 25/100