NASA-IMPACT / NASA-IMPACT/veda-odd
harmonize titiler.xarray i/o strategy with upstream and downstream applications
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 0
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 3
Description
There are improvements being considered in upstream libraries (xarray + zarr) that might affect the choices we make in titiler.xarray's dataset opening procedure. We should spend some time crafting a strategy that will be crisp for the growing list of downstream applications that use the XarrayReader
related: https://github.com/developmentseed/titiler/discussions/1247
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 with titiler.xarray's dataset opening procedure and the XarrayReader used by downstream applications. Review the related discussion and the improvements being considered in xarray and zarr. Done means a crisp, documented I/O strategy that accounts for upstream changes and the growing set of downstream users.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100