Repository navigation
ESA WorldWater (DHI) #114
Description
ESA WorldWater UDP
- basic record creation with link to UDP in worldwater repo
- DHI to check if UDP works as expected
- default job options to be added to udp if needed
- 'vito' branch in worldwater to be merged into main branch?
- Improve record/UDP description
- check UDP for parameter naming compliance
Activity
JanssenBrm commentedon Dec 11, 2025
Update 11/12
JanssenBrm commentedon Feb 18, 2026
Update 18/02 (WorldWater/EO4WI and APEx coordination)
JanssenBrm commentedon Mar 5, 2026
Feedback 25/02
Dear APEx/VITO team,
Following the meeting last week we hereby share the updated worldwater GitHub branch that should now work with both the VITO and CDSE backends:
Updated branch: https://github.com/DHI-GRAS/worldwater-toolbox/tree/new-udp
You can test it using the functions available in the test workflow here: https://github.com/DHI-GRAS/worldwater-toolbox/blob/new-udp/tests/test_workflow.py
According to the update, the functions process_single_month and process_annual_water are currently running correctly on both backends.
However, when running the workflow through the generated UDP, it still fails—either by ignoring Sentinel 2 data or by raising errors related to Sentinel Hub collections.
Can you please pick up from here and adapt the UDP as needed. In case of questions or clarification please contact @Walid Ghariani or @Alkiviadis Koukos directly, thanks.
Cheers,
JanssenBrm commentedon Mar 5, 2026
As you can see in the current preview of the record, the description on the page is very limited. This is read from the
descriptionfield from the UDP. It is beneficial for users if the UDP contains a clear description, as this is loaded in several tools automatically.Things to complete the record integration (based on #118):
You can preview the changes on https://esa-apex.github.io/apex-algorithms-catalogue-web/pr-preview/pr-118/?q=world+water
JanssenBrm commentedon Apr 9, 2026
Update 09/04
JanssenBrm commentedon Apr 10, 2026
Feedback from DHI: Basically, the workflow works as expected when we run the process_single_month function (or just _water_extent_for_month), but when we used the generated udp it fails. Based on the output, it looks like it always ignores Sentinel-2 data, even If we set the only_s1 parameter to False. Could you take a look on this?
JanssenBrm commentedon Apr 15, 2026
Linking issue: DHI-GRAS/worldwater-toolbox#11
Patrick1G commentedon Sep 16, 2026
@JanssenBrm @jdries any chance of unblocking this?