Deliverables for Integration tasks:

• Adapted GUI for FAO-WOCAT.

for FAO-WOCAT we want to allow the user to use the advanced settings for fao - wocat
chat to Cesar Garcia on the code

UI Updates:

• Add FAO-WOCAT radio box
  

• When the radio box is chosen then the user should be able to access the same settings and advanced settings as that used for the Trends Land use data
  

The FAO-WOCAT data interface needs to be available for the all indicators option and the land productivity option

We have the GEE code for the FAO-WOCAT data and need to meet with Cesar to check if the advanced setting parameters are correct for the analysis.

For FAO-WOcat the period is important to define in the beginning.

Code : https://code.earthengine.google.com/0fe1c192e5137151df30a0d2ff7f6039
can we move the period choice options to above the NDVI options.

remove the start and end and replace them with just one box to add a period -> only for the FAO advanced options.

remove the climate option to keep FAO-WOCAT

performance should be replaced with Initial Biomass

only allow users to edit low and high boxes and the mid value is shown but not editable.

We need to make the remote server processing work based on the Code here:
https://code.earthengine.google.com/0fe1c192e5137151df30a0d2ff7f6039
in the conservation international GH
@azvoleff needs to give @Samweli access. it may be useful to add Danang or Dimas.

@Samweli I've given you admin access to the trends.earth API server, which is needed to deploy this feature (following the process outlined here).

In addition to the GUI changes gee/sdg-15-3-1-sub-indicators/src/main.py will need to be modified to correctly handle the new FAO-WOCAT parameterization, as will gee/productivity/src/main.py for the case of users running just the productivity dataset but not the full SDG.

New code for actually running the calculations (the code running the algorithm itself as opposed to just calling our API) should go somewhere in te_algorithms/gee (perhaps in te_algorithms/gee/productivity.py - but that script is getting a bit long and likely needs to be split up).

As a side note, the code in trends.earth-algorithms cannot depend on QGIS. We intentionally keep code that relies on QGIS within the trends.earth repo as the code in trends.earth-algorithms is run on headless servers for testing and automated production of the default data for UNCCD.

Thanks

@Samweli I've given you admin access to the trends.earth API server, which is needed to deploy this feature (following the process outlined here).

In addition to the GUI changes gee/sdg-15-3-1-sub-indicators/src/main.py will need to be modified to correctly handle the new FAO-WOCAT parameterization, as will gee/productivity/src/main.py for the case of users running just the productivity dataset but not the full SDG.

New code for actually running the calculations (the code running the algorithm itself as opposed to just calling our API) should go somewhere in te_algorithms/gee (perhaps in te_algorithms/gee/productivity.py - but that script is getting a bit long and likely needs to be split up).

As a side note, the code in trends.earth-algorithms cannot depend on QGIS. We intentionally keep code that relies on QGIS within the trends.earth repo as the code in trends.earth-algorithms is run on headless servers for testing and automated production of the default data for UNCCD.

Thanks @azvoleff, I will create new issues for each of these action items and work on them.

In addition to the GUI changes gee/sdg-15-3-1-sub-indicators/src/main.py will need to be modified to correctly handle the new FAO-WOCAT parameterization, as will gee/productivity/src/main.py for the case of users running just the productivity dataset but not the full SDG.

@azvoleff from the chat with Cesar he mentioned that the new FAO-WOCAT should be only available remotely, doesn't modifying these gee scripts make it also available locally?