Open-EO / Open-EO/openeo-python-driver
atmospheric_correction: Use options instead of new parameters?
Open
Nobody has claimed this yet.
API
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
As requested the options parameter had been added to atmospheric_correction so that custom options could be exposed.
The custom options VITO exposes are added as new parameters directly, see https://openeo.vito.be/openeo/1.0/processes/backend/atmospheric_correction
Is it intentional that the implemented process does individual parameters instead of using the options parameter?
(Somewhat related question: What is the missionId useful for? Sounds like it should be read from metadata?)
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.
Assessment
This issue has not been assessed yet.