BIAS2 UDP Preview

[JanssenBrm]

Preview of #316

[algorithm-services-catalogue]

🔍 Catalogue's Preview Site Deployed

Your changes have been deployed to the preview site:

🔗 Preview URL: https://esa-apex.github.io/apex-algorithms-catalogue-web/pr-preview/pr-378/

This preview will be updated automatically when you push new changes to your PR.

[JanssenBrm]

@zacdezgeo - You can preview the record here: https://esa-apex.github.io/apex-algorithms-catalogue-web/pr-preview/pr-378/

Let me know if everything looks OK for you. After your approval, I'll merge the record.

[JanssenBrm]

@zacdezgeo - while testing the catalogue, I noticed that the record contains a reference to openeo.cloud while the notebook uses CDSE. Is there any specific reason for this? Can this be aligned to use CDSE in the record?

[zacdezgeo]

@JanssenBrm ; it looks great! I don't have the right to push to this branch, but I'm happy to align with the CDSE in the record.

[JanssenBrm]

I have updated the reference to use the CDSE backend @zacdezgeo , but it seems that the UDP is not validating, preventing me to execute the service.

You can replicate this by going to the preview page and clicking the "Execute Service" button or by navigating to https://editor.openeo.org/?wizard=UDP&wizard%7Eprocess=bais2&wizard%7EprocessUrl=https%3A%2F%2Fraw.githubusercontent.com%2FESA-APEx%2Fapex_algorithms%2Frefs%2Fheads%2Fds_bias_preview%2Falgorithm_catalog%2Fdevelopmentseed%2Fbais2%2Fopeneo_udp%2Fbais2.json&server=openeofed.dataspace.copernicus.eu

Can you have a look at what could be causing the validation errors?

[JanssenBrm]

I believe you should have received an invitation that will allow you to make changes in this PR.

[zacdezgeo]

I reproduced this and it looks like a CORS/auth-header issue, not a bais2 UDP schema issue.

• The UDP URL is reachable (GET to raw.githubusercontent.com returns 200).
• But in the CDSE editor flow, the request includes Authorization.
• That triggers a browser preflight (OPTIONS) with Access-Control-Request-Headers: authorization, and GitHub Raw responds 403.
• Result: Axios throws ERR_NETWORK before backend UDP validation even runs.

The current error is caused by cross-origin header handling in the editor/CDSE context, not by invalid bais2.json.

Some potential workarounds:

• Import/paste the UDP JSON locally in the editor, or
• host the JSON on an endpoint that allows CORS preflight with Authorization.

@JanssenBrm, have you come across this before? any preferred solutions for hosting the udps? cc: @emmanuelmathot

[JanssenBrm]

Thank you for investigating this @zacdezgeo! However, whenever I go through the process, I don't really see any CORS errors in the browser tools. At what stage did you encounter them?

I am able to go through the wizard, but at the last step, to actually launch the job, the UI disables the button as the validation return errors. Looking into the network console, I see a POST request to https://openeofed.dataspace.copernicus.eu/openeo/1.2/validation which returns the following response (as shown in the screenshot)

{
    "errors": [
        {
            "code": "UpstreamValidationInfo",
            "message": "Backend 'cdse' reported validation errors"
        },
        {
            "code": "ProcessParameterRequired",
            "message": "Process 'linear_scale_range' parameter 'x' is required."
        }
    ]
}

[JanssenBrm]

I also notice the following when I import the UDP JSON from the PR (https://raw.githubusercontent.com/ESA-APEx/apex_algorithms/refs/heads/ds_bias_preview/algorithm_catalog/developmentseed/bais2/openeo_udp/bais2.json) in the web editor:

Could it be related to how linear_scale_range parameters are defined in the UDP versus how CDSE expects them?

Looking at the UDP I see the parameters input_min, input_max, data:

Whereas, looking at the process documentation in both the CDSE documentation and the Web Editor, I see the inputMin, inputMax, x.

@soxofaan - pinging you as well to share thoughts

[JanssenBrm]

BTW @zacdezgeo , I did find the CORS error while testing another service. It indeed happens whenever you are using https://editor.openeo.org to execute a service. I believe this is an issue on CDSE side, I'll report it.

[zacdezgeo]

thanks for the catch @JanssenBrm! I’ve updated the UDP JSON in the PR to use the CDSE-compatible argument names for linear_scale_range.