search

Open-EO / openeo-api

The openEO API specification
http://api.openeo.org
Apache License 2.0
91 stars 11 forks source link

Predefined error for process graph that doesn't work out #388

Closed jdries closed 3 years ago

jdries commented 3 years ago

I have a case where a process graph is basically valid and supported by our backend, but it still generates an error during execution. In this particular case, the labels set on the band dimension do not match the actual data, which is generated by UDF's.

Do we need a specific error related to unmatching dimension labels. Or can we (also) have a more generic 4xx one, for all cases where something turns out to be wrong due to a logical error in the construction of the process graph?

jdries commented 3 years ago

Seems like we already have a few occurences of this, that are handled like: raise OpenEOApiException(message="""Process "sar_backscatter" is not applicable for collection {c}.""" .format(c=collection_id), status_code=400) And actually the api does explain it here: https://api.openeo.org/#section/API-Principles/Error-Handling I was just looking at the predefined errors here, which of course can't contain this type of error. Closing this one!