atmospheric_correction: Use options instead of new parameters?

[m-mohr]

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?)

[m-mohr]

EODC is also using the options since today.

[soxofaan]

FYI: I added options support to python client on EODC request: Open-EO/openeo-python-client@1f02360

[m-mohr]

Thanks. Are the options also available in ard_surface_reflectance?

[soxofaan]

ard_surface_reflectance in python client now also supports atmospheric_correction_options and cloud_detection_options : Open-EO/openeo-python-client@9d372b9