Open-EO / Open-EO/openeo-python-client
add_dimension: infer 'type' from name?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Found this in an expert notebook:
cube.add_dimension(name="bands",label="coh_VV_amp")
The user clearly intended to add a dimension with type 'bands', but he got a dimension with type 'other'. This lead to subsequent hard to find bugs.
The client can do 2 things here: set the type based on the name if not set explicitly, or log a warning when this name is used but type is defaulted to 'other'.
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 from the cube.add_dimension entry point and reproduce the expert-notebook example with name="bands" and label="coh_VV_amp". Compare the behavior when type is omitted with the two proposed outcomes: infer "bands" from the name or warn when defaulting to "other"; confirm the intended choice with maintainers before defining done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100