Open-EO / Open-EO/openeo-python-client
Eliminate `XarrayDataCube`?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
XarrayDataCube is extremely simple: it just wraps a single xarray.DataArray and nothing more. It offers some IO functionality, but that doesn't mean these have to be XarrayDataCube methods. (There is also a plot method, but I wonder if anybody uses that and I dislike that this drags in a dependency on matplotlib)
It's simple, but it creates an extra abstraction layer in working with UDF, possibly making things more confusing than necessary.
can we just drop (the need for) XarrayDataCube ?
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 XarrayDataCube and reviewing how its xarray.DataArray wrapper, IO methods, plot method, and UDF usage are referenced. Determine the intended replacement and whether the IO and plotting behavior must remain; done means the extra abstraction is no longer required without leaving those responsibilities ambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100