Implement RA/IA Table

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

Status:

• GUI implementation ("html wireframe") as React AJAX web Application following the respective Product Mock-Ups
• Integration into the respective GL-Step as External ReactMount Application
• Design of a simplified internal state data model in JSON (the "table model") and definition of static JSON constants (example) as initial reference / example data from the EMICAT Rest Interface
• the table contains the content for DC1 Reference study (The content will be retrieved from the emicat server). When this server contains the content for DC1 Reference study, the table will also contain this content
• Mapping of the actual Data Package Data Model to the internal JSON state data model with help of the JSON:API and/or REST Views and additional REST Micro Services for simple data aggregation and transformation.

Implement the GUI following the description in this issue and the approach described here.

RA/IA Table GUI

The table shows the output of the impact model calculation. Note: The Mock-Ups aren't valid any more (see also clarity-h2020/csis#45 (comment)):

Outdated Mock-Up

Actual Mock-Up: The table should look like this:

RA/IA Table state model

• Column 1: Hazard
• Column 2: Exposure (Element at Risk) grouped by Hazard. e.g. Heat Wave has no impact on buildings or infrastructure, therefore there is no HW/Buildings Group.
• Column 3: The Vulnerability Classes of the respective Element at Risk
• Column 4: Unit
• Column 5-8: number of elements at risk impacted by hazard and grouped by damage classification D1 - D4 (see legend)

Mapping Data Package to HC Table state model

The Impact is calculated by the Risk & Impact Calculation Service (EMIKAT), therefore the data for the table should be retrieved from the EMIKAT REST Service. Ideally, the JSON data obtained from EMIKAT matches directly the internal state model of the RA/IA Table. To be discussed with @bernhardsk and @humerh
The REST URI can be obtained from the path property of respective RA/IA Data Resource of the Data Package. However, since the table data is rather small, the JSON could be stored directly in the data property of the Data Resource.

[therter]

@humerh @bernhardsk : An example for the table state model:

{
    "data": [
        {
            "hazard": "HW",
            "elementAtRisk": "Population",
            "vulnerabilityClass": "Age group 0-14",
            "unit": "pop/km2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "HW",
            "elementAtRisk": "Population",
            "vulnerabilityClass": "Age group 15-64",
            "unit": "pop/km2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "HW",
            "elementAtRisk": "Population",
            "vulnerabilityClass": ">65",
            "unit": "pop/km2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Population",
            "vulnerabilityClass": "Age group 0-14",
            "unit": "pop/km2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Population",
            "vulnerabilityClass": "Age group 15-64",
            "unit": "pop/km2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Population",
            "vulnerabilityClass": ">65",
            "unit": "pop/km2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Buildings",
            "vulnerabilityClass": "Continuous Residential (S.L. > 80%)",
            "unit": "m3/m2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Buildings",
            "vulnerabilityClass": "Med-Hi Density Discontinuous Res. (30% < S.L. < 80%)",
            "unit": "m3/m2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Buildings",
            "vulnerabilityClass": "Low Density Discontinuous Res. (S.L. < 30%)",
            "unit": "m3/m2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Buildings",
            "vulnerabilityClass": "Non Residential",
            "unit": "m3/m2",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Infrastructure",
            "vulnerabilityClass": "Roads",
            "unit": "ml",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        },
        {
            "hazard": "FL",
            "elementAtRisk": "Infrastructure",
            "vulnerabilityClass": "Railways",
            "unit": "ml",
            "damageLevel1P": "1",
            "damageLevel2P": "3",
            "damageLevel3P": "2",
            "damageLevel4P": "3",
            "damageLevel5P": "5",
            "damageLevel6P": "7"
        }
    ]
}

[bernhardsk]

Progress update by @bernhardsk (AIT) and @humerh (AIT):

A first version of the Impact Calculation Module has been implemented in AIT EMIKAT.
Impact was calculated for Hazard Index Type "heat-wave:consecutive-summer-days" using example data and based on the impact model descriptions provided by PLINIVS.

As described above, the RA/IA Table should look like this:

In order to provide the values required by the RA/IA table as shown above, a view has been created in EMIKAT to aggregate the results from the impact calculation, which currently looks like this:
View (as Table): Damage level of Elements at Risk of each Vulnerability Class for a specific Impact Scenario/Hazard Index (without listing IDs):

However the discussions during the CLARITY Developers/co-creation meeting in Vienna showed that the impact modelling should be changed slightly. The following changes should be carried out:

1. The impact calculation has to focus on 1 specific hazard event at a time (e.g. for heat wave: 6 consecutive days over 30°C max). Therefore it makes no sense to include information about the time period and the emissions scenario (rcp).
2. As input for the hazard event data, the impact calculation should use the Hazard-Local Effect layer/data.
3. The way how the vulnerability functions/tables are taken into account should be changed (due to the changes in bulletpoint "1)").

Next steps will focus on

1. correcting the impact calculation as described above and changing the RA/IA table view accordingly.
2. connecting EMIKAT with the front-end in order to exchange the neccessary data to be shown to users in the front-end RA/IA table. As for the next steps, only impact will be calculated and show. Risk will follow at a later stage.
3. implementing another example scenario (e.g. pluvial flood) using already available or otherwise dummy data.

[therter]

@bernhardsk @humerh
I assume that Emicat (with the url https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_VULNERABILITY_FUNC.1837/table/data) should be used to get the data for the table. Do I understand correctly that the hazard and the element at risk can be extracted from the field "impact case" and which value of the field "Damage Level x" should be shown in the D1...D6 columns of the table or should all values be shown?

[therter]

current status:

• GUI implementation ("html wireframe") as React AJAX web Application following the respective Product Mock-Ups
• Integration into the respective GL-Step as External ReactMount Application
• Design of a simplified internal state data model in JSON (the "table model") and definition of static JSON constants (example) as initial reference / example data from the EMICAT Rest Interface
• the table contains the content for DC1 Reference study (The content will be retrieved from the emicat server). When this server contains the content for DC1 Reference study, the table will also contain this content
• Mapping of the actual Data Package Data Model to the internal JSON state data model with help of the JSON:API and/or REST Views and additional REST Micro Services for simple data aggregation and transformation.

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

@therter Table broken due to changes in EMIKAT RA/API data format.

We will update the table once this has stabilised.

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

Additional query parameters to be supported. See clarity-h2020/data-package#42