Implement HC 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 based on the example table content from the mock-up screens
• the table contains the content for DC1 Reference study (The content will be retrieved from the table-state-rest-api)
• 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 GUI following the Mock-Up and the approach described here.

HC Table GUI

The table compares current conditions against three future scenarios (or 9 scenarios, if we take time periods into account)

• Column 2 is the hazard related to the baseline scenario (current climate conditions)
• columns 3-5 are the hazard for three different RCPs for one selected time period (e.g. 2020-2050).

What is missing in the mock-up are the different time periods (3 time periods). A drop-down select-box could be added. Selecting a different time period changes columns 3-5 only!

Initial Mock-Up

HC Table state model

• Column 1: Hazard, possibly grouped! So maybe add an empty row for group name
• Column 2: It can be low, medium, high or an absolute numerical value, depending on the hazard! In case of a numerical value, the unit should be shown (e.g. in header row). See 1st Data Package: 01 HC Layers data-package#8 (comment).
• columns 3-5: low,medium, high
• legend: example in mock-up invalid! low, medium, high has different meaning in column 2 than in columns 3-5! ignore colors in column 2, to be discussed later. legend for column 3-5: is low / medium / high increase with respect to the baseline climate

Correct Mock-Up (explanation here)

Example for grouping:

Mapping Data Package to HC Table state model

tbd @p-a-s-c-a-l
Table content is not part of the Data Package Meta-Data stored in CSIS! Data has to be obtained from WCS and has to be aggregated and normalised! Find possibilities for delegating this task, e.g. METEOGRID could implement a simple REST API that returns JSON compliant to the state model.

[therter]

@ghilbrae @luis-meteogrid: An example for the table state model:

{
    "data": [{
            "hazard": "Heat Wave Duration",
            "baseline": "Medium",
            "earlyResponseScenario": "Low",
            "effectiveMeasuresScenario": "Medium",
            "businessAsUsualScenario": "High",
            "period": "2030-2040"
        },
        {
            "hazard": "River Flooding",
            "baseline": "Medium",
            "earlyResponseScenario": "Heigh",
            "effectiveMeasuresScenario": "Medium",
            "businessAsUsualScenario": "Medium",
            "period": "2030-2040"
        }, {
            "hazard": "Heat Wave Duration",
            "baseline": "Medium",
            "earlyResponseScenario": "Low",
            "effectiveMeasuresScenario": "Medium",
            "businessAsUsualScenario": "High",
            "period": "2041-2070"
        },
        {
            "hazard": "River Flooding",
            "baseline": "Medium",
            "earlyResponseScenario": "High",
            "effectiveMeasuresScenario": "Medium",
            "businessAsUsualScenario": "Medium",
            "period": "2041-2070"
        }
    ]
}

[ghilbrae]

We've read the issue and we need to analyse it further before committing to it.

When you say

Data has to be obtained from WCS and has to be aggregated and normalised!

do you mean that all this data will be available from the layers that are going to be uploaded to geoserver? Will there be other sources?

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

do you mean that all this data will be available from the layers that are going to be uploaded to geoserver?

I hope so. :) Data is on your server, did you check if the properties needed to construct the table are available in the hazard datasets? @therter was not able to request any other format from than geotiff from the WCS (timeout). For the normalisation (low, medium, high) you'll need information on the thresholds which will probably be part of the Data Package Meta-Data.

[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 based on the example table content from the mock-up screens
• the table contains the content for DC1 Reference study
• 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.