gisat s1 changedetection - draft

[sivasanarul]

This pull request contributes a script developed under the Sentinel 1-Amazonas project in gisat. The script processes Sentinel-1 backscatter time-series data by stacking 10 temporal slices and generating a binary change map. It is part of our workflow for detecting land-cover change using Sentinel-1 data.

[JanssenBrm]

Thank you for updating the branch @sivasanarul! I noticed that a dedicated record.json for gisat. You can find an example in the other PR: https://github.com/ESA-APEx/apex_algorithms/pull/123/changes#diff-7e8ac09cd317024b2958fdf55d4d03df6d6595bba953a3966a35221ccebcb865 . However, the logo links are still missing in that record.

I wanted to provide the update myself, but I'm not able to push changes to your fork.

[JanssenBrm]

It seems that his file only contains the process_graph. A valid UDP should contain an ID, a more comprehensive description and the parameters. Could you share how the UDP definition was generated?

[sivasanarul]

I have changed the process graph. the latest one is generated from this:
https://github.com/Gisat/dev-S14amazonas/blob/main/apex_generate.py

[JanssenBrm]

Thank you for the updates @sivasanarul! I have generated a preview PR where you can see how the record would be shown on the algorithm catalogue:

• General page: https://esa-apex.github.io/apex-algorithms-catalogue-web/pr-preview/pr-372/
• Specific record: https://esa-apex.github.io/apex-algorithms-catalogue-web/pr-preview/pr-372/apps/sentinel1_changedetection/#execution-information

Although the record is now showing properly in the catalogue, I would like to suggest some minor improvements:

• The description on the details page is fetched from the description field of the UDP. As you can see in the preview, the description is quite limited and doesn't provide much for visitors. A more comprehensive description (providing insights into the methodology, limitations, use cases, ...) is advised, as this will also be shown in other tooling, such as the openEO Web Editor.
• You can also add additional links to the sidebar where users can get more information. The documentation provides how you can use the links section in your record to do so. An example was already prepared for you in a separate PR, but could be copied to this one.

However, the above points are not required in any way. If you feel it is sufficient as-is, let me know, and I will merge the PR.

[sivasanarul]

Hi @JanssenBrm There are some limitations to the algorithm that I would like to mention in the description. I have some urgent work to finish now. I will update this today late afternoon, and monday morning. And then it would be ready for merging

[sivasanarul]

Just to be clear, I need to update the description in the UDP in my forked apex repo and create a new pull request?
Is there any change from your side that needs to be synced first and is this the only change needed?

[JanssenBrm]

Just to be clear, I need to update the description in the UDP in my forked apex repo and create a new pull request? Is there any change from your side that needs to be synced first and is this the only change needed?

You can update the description in this PR - I will trigger the update in the preview manually for now so that we can keep it simple.