AO appraisal step for advanced screening study

[DenoBeno]

Summary: in advanced screening, differentiate between "AO Identification" and "AO appraisal" steps.

• Define new templates for these two steps and adm to test study type
• In AO identification allow the users to explore the available adaptation options
• In AO appraisal, allow the users to define the adaptation strategy
• In AO appraisal, allow the users to trigger re-calculation
• In AO appraisal, allow the users to explore the difference between situation with and without adaptation options.

[DenoBeno]

I have defined a new "test" workflow that extends and improves the "Advanced screening". Some of it works as designed, some doesn't and will require your attention:

1. Possibility to trigger re-calculatioon directly from AO Appraisal step (easy to implement, I presume)
2. Possibility to use scenario analysis in this step. Currently nothing is shown at all, no idea why.
3. Possibility to visualize before/after situation in a map component. Currently the map works, but this is not possible.
4. Ideally, we should also be able to show simple cost / benefit analysis - currently not available AFAIK.

Test study is here: https://csis-dev.myclimateservice.eu/study/163/view/intro

I have linked it to an existing study so that I can see how emikat results are displayed. Triggering new calculation doesn't work on dev server.

[patrickkaleta]

2. Possibility to use scenario analysis in this step. Currently nothing is shown at all, no idea why.

Reason for that was that the View had a filter applied, which allowed only GL-steps with the EU-GL methodology tax. term = "Risk and Impact Assessment". I've removed that filter and now the Scenario Analysis app is also shown in this AO appraisal step.

[p-a-s-c-a-l]

Possibility to visualize before/after situation in a map component. Currently the map works, but this is not possible.

Adaptation Map is now implemented on DEV instance and can be tested here:

Test Template: Adaptation Options Appraisal is also updated. Note that the maps don't show any difference, this is probably just a matter of updating the styles in EMIKAT WMS. Furthermore, impact with adaptation options applied is still siglty higher. See also #154 (comment)

Moreover, I've updated all tables to include all columns and adaptation scenarios when downloading the tables as JSON or CSV, so you can compare data offline.

[p-a-s-c-a-l]

2. Possibility to use scenario analysis

ATM I'm stuck here until the issues with aggregated "view.2994" are fixed and/or with adaptation results randomly disappearing.

[p-a-s-c-a-l]

Scenario Analysis has been updated on CSIS-DEV. ATM all indicators available in EMIKAT view.2994 are shown, Pluvial Flood indicators yet to come.

I'm not sure about the cost and the unit of "Heat Wave Impact", though. Furthermore, adaptation scenarios as well as some values randomly appear and disappear.

@DenoBeno Furthermore, there is no difference between Scenario Analysis in RA/IA and AOAP Step. So the only difference is the Map, which shows Baseline (left) and Adaptation Scenarios (right) in the new AOAP step. I don't know if this minor difference really justifies a new AOAP step or if we better just change the map in the RA/IA step.

[p-a-s-c-a-l]

Now with pluvial flood:

Example Study 25 on CSIS DEV.

Note: Scenario Analysis on PROD-CSIS is broken since EMIKAT API changed.

Before I make a new public release, please let me know if you want any change of indicator name / units @claudiahahn @DenoBeno @mattia-leone

[claudiahahn]

This might be an unqualified comment, but without an explanation of the indicators they'll not be very helpfull for the user.
I have been on vacation, so maybe I have missed the discussion about that. But it seems that the indicators are not explained in any of the tabs under the "Risk/Impact" step. What does heat wave impact mean, or damage class mean?

[p-a-s-c-a-l]

What does heat wave impact mean, or damage class mean?

This is a good question. I think this information is somewhere hidden in vulnerability whereas I'm not sure whether is this conceptually consistent or not.

Anyway, this should be explained in the respective resource so that it is visible on the RA/IA data tab.