You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the eodc backend, we updated the process definitions to be compliant with v2.0.0. This is fine for the backend specific editor but leads to a problem with the aggregator:
The loading of the collection is still expected to return a raster-cube, while our backend specific processes such as sen2likeexpect a datacube. For the processes that are available on other backends as well, the old specification is used, so these do not show the warning.
Would it be an option to switch off this check or to allow a raster-cube when a datacube is expected?
The warning looks like this:
The text was updated successfully, but these errors were encountered:
In the eodc backend, we updated the process definitions to be compliant with v2.0.0. This is fine for the backend specific editor but leads to a problem with the aggregator:
The loading of the collection is still expected to return a
raster-cube
, while our backend specific processes such assen2like
expect adatacube
. For the processes that are available on other backends as well, the old specification is used, so these do not show the warning.Would it be an option to switch off this check or to allow a
raster-cube
when adatacube
is expected?The warning looks like this:
The text was updated successfully, but these errors were encountered: