Add BAIS2 UDP entry for Development Seed

[zacdezgeo]

Create provider record, add BAIS2 service record and UDP JSON, and include preview/thumbnail images from the notebook output.

[JanssenBrm]

You can also use the notebook as rel type. This would redirect the user to an APEx JupyterLite instance which will load in the notebook for the user to execute. However, it could be good to double check if the notebook is actually running properly.

[zacdezgeo]

just noting that i need to come back to this one.

[zacdezgeo]

updated in recent commit pointing to: https://raw.githubusercontent.com/developmentseed/openeo-udp/refs/heads/main/notebooks/sentinel/sentinel-2/fire_and_disaster_monitoring/bais2_burned_area.ipynb. cc: @emmanuelmathot

[JanssenBrm]

Is there also a webapp link that we could add, similar to the other UDPs? This would allow the user to directly navigate to a UI for executing the service.

[zacdezgeo]

just noting that i need to come back to this one.

[zacdezgeo]

added link pointing to: "https://editor.openeo.org/?wizard=UDP&wizard%7Eprocess=bais2&wizard%7EprocessUrl=https://raw.githubusercontent.com/ESA-APEx/apex_algorithms/refs/heads/main/algorithm_catalog/developmentseed/bais2/openeo_udp/bais2.json&server=openeo.cloud

I followed the pattern for the other udps, but i don't think this will be available until we make a copy of this branch on this repository directly.

[JanssenBrm]

Thank you @zacdezgeo for this initial PR and setting up the records. My apologies for the many comments, but it seems that the records are still requiring some information to pass the unit test.

I see that our documentation is missing a part where you can execute the unit tests locally, but I did this by following these steps:

1. Installing the APEx QA tooling by running pip install qa/tools
2. Executing the validation of the records through pytest qa/unittests/tests/test_records.py

I would expect the unit tests to be running from the PR automatically, but it seems that they are not getting started...

Unfortunately, there is also a known bug where the preview function of the catalogue is not working from remote forks. However, I suggest that once the records have been updated, we duplicate the branch to this repository, allowing you to visually inspect how the record would look like in the catalogue.

[zacdezgeo]

Thank you so much for the detailed review and for taking the time to leave all of these comments. I really appreciate it.

This is my first contribution to the apex_algorithms repository, and your feedback is extremely helpful for understanding the expected schema requirements (especially around provider metadata and link conventions). It’s been a great guide for getting the records into the shape needed to pass the unit tests and display correctly in the catalogue.

I’ll work through the requested updates and rerun the QA validation locally with pytest qa/unittests/tests/test_records.py before pushing the next commit.

Thanks again for the support in navigating the contribution process here, it’s very appreciated.

[zacdezgeo]

I followed up on your comments regarding the record's links, but I still need to add the platform's logo (dark and light) based on the results from running: pytest qa/unittests/tests/test_records.py. I'll follow-up.