1st Data Package: 02 Hazard Local Effects Layers for Heat Waves

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

Create Hazard Local Effects Layers and make them available in CSIS.

This encompasses the following steps:

• ZAMG to provide plain HC Data: done. netcdf avialble on sftp
• METEOGRID to create HC-LE layers based on input layers prepared by ATOS
• METEOGRID to expose Layers (WCS/WMS) via their GeoServer
• METEOGRID to define some simple styling for Layers (no need to consider thresholds as explained here)
• CIS to create Data Package Meta-Data in CSIS
• ??? to provide meta-data for Data Management Plan
  Both HC-LE and respective input layers are open data that eventually to deposited in zenodo (if we have calculated the HC-LE data for whole Europe)

Important Notes:

• This tasks depends on Hazard Local Effects Modelling Workflow Implementation, currently HC-LE Data is not yet available!
• The Impact Model shall use HC-LE Data (500m grid), not plain HC Data (12.5km grid)
• There is already MUKLIMO HC data available for Naples. Although this data is meant for the Expert Workflow, we could use it temporarily in the screening workflow as substitute for the HC-LE data which yet has to be calculated.

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

Could somebody please update the status? E.g. AFAIK HC-LE HW Layers are now available for all HC HW Layers from clarity.meteogrid.com.

[maesbri]

Currently, in Meteogrid's Geoserver there are these Local Effects layers:

• clarity__Heat_wave_temperature_historical_hight_hazard_Naples
• clarity__Heat_wave_temperature_historical_low_hazard_Naples
• clarity__Heat_wave_temperature_historical_medium_hazard_Naples
• clarity__Heat_wave_temperature_historical_very_hight_hazard_Naples

@ghilbrae , for each of them I need the following metadata information in order to properly describe them within the Naples data package I am preparing (see https://github.com/clarity-h2020/data-package/blob/master/examples/dc1-naples/datapackage.json):

• title (not the layer name)
• brief description
• temporal extent (starting and ending time periods that are comprehended by this resource)
• sources of the data used for the calculation of this resource
• temperature

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

This information should be in our CKAN: https://ckan.myclimateservice.eu/dataset/historical-heat-wave-temperature-local-effects

[maesbri]

yes, I had already checked it but the information required is not there

[ghilbrae]

@maesbri I'll check with my colleagues and come back with an answer for you.

[ghilbrae]

Currently, in Meteogrid's Geoserver there are these Local Effects layers:

• clarity__Heat_wave_temperature_historical_hight_hazard_Naples
• clarity__Heat_wave_temperature_historical_low_hazard_Naples
• clarity__Heat_wave_temperature_historical_medium_hazard_Naples
• clarity__Heat_wave_temperature_historical_very_hight_hazard_Naples

@ghilbrae , for each of them I need the following metadata information in order to properly describe them within the Naples data package I am preparing (see https://github.com/clarity-h2020/data-package/blob/master/examples/dc1-naples/datapackage.json):

• title (not the layer name)

• brief description

Heat Wave Hazard in Napoli considering different base Temperatures.

• temporal extent (starting and ending time periods that are comprehended by this resource)

Baseline for current time.

• sources of the data used for the calculation of this resource

The resource was generated based on the data generated/downloaded by ATOS.

• temperature

Base temperatures are: 32 (low), 34 (medium), 36 (high) and 38 (very high).

[maesbri]

Currently, in Meteogrid's Geoserver there are these Local Effects layers:

• clarity__Heat_wave_temperature_historical_hight_hazard_Naples
• clarity__Heat_wave_temperature_historical_low_hazard_Naples
• clarity__Heat_wave_temperature_historical_medium_hazard_Naples
• clarity__Heat_wave_temperature_historical_very_hight_hazard_Naples

@ghilbrae , for each of them I need the following metadata information in order to properly describe them within the Naples data package I am preparing (see https://github.com/clarity-h2020/data-package/blob/master/examples/dc1-naples/datapackage.json):

• title (not the layer name)

• brief description

Heat Wave Hazard in Napoli considering different base Temperatures.

• temporal extent (starting and ending time periods that are comprehended by this resource)

Baseline for current time.

What is the current time? 2019? The date time of the original temperature data used for the calculations?

• sources of the data used for the calculation of this resource

The resource was generated based on the data generated/downloaded by ATOS.

Again, too vague. We need the concrete references to the data sources used. For temperature data, which were your sources, EURO-CORDEX?

• temperature

Base temperatures are: 32 (low), 34 (medium), 36 (high) and 38 (very high).
ok, thanks. I would suggest to rename the layers in your geoserver by replacing "low", medium", etc. by the temperature degrees as the naming used looks to me subjective (32ºC can be low for Naples but very high for other European regions)

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

IMHO the wrong resources (HC-LE Input Layers) are currently referenced in the Naples DataPackage. This is also related to clarity-h2020/csis#22 (comment) and clarity-h2020/map-component#15

[therter]

@maesbri @ghilbrae The wms layer for Historical heat wave temperature in Naples (34ºC)(local effects) (Local_Effects:Heat_wave_temperature_historical_very_hight_hazard_Naples) does not exist in the wms. So the map-component cannot show this layer.

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

As agreed with @humerh Local Effects Hazard Layers which are based on Events chosen by the user for whole Europe will be served from EMIKAT API! The Data Package has to be updated accordingly. The EMIKAT API for hazard with local effects events will be accessed by parametrised URLs. Parameters are project id (=study id), study area bbox, event type (frequen, occasional, rare), RCP and time period. EMIKAT will then return hazard values for the table component (preferably in JSON or CSV) and for the Map Component (WMS).

We need only one HC-LE resource per Hazard type. The resource contains two different URLs (references), one for map request (WMS) and one for table data (REST/JSON). The URLs support parameters e.g. $studyId, $studyArea, $hazardType, $rcp, $TimePeriod which are replaced by the ReactJS Components (table and map) by actual values extracted from the study context (obtained via Drupal JSON API). Furthermore, the user has to chose a one event from the baseline and one corresponding event from a specific RCP / time period.

The Data Package / HC-LE Resources has to be updated accordingly once @humerh provided sample, request URIs for the EMIKAT API.

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

Parameters are project id (=study id), study area bbox, event type (frequen, occasional, rare), RCP and time period.

The URLs support parameters e.g. $studyId, $studyArea, $hazardType, $rcp, $TimePeriod which are replaced by the ReactJS Components (table and map) by actual values extracted from the study context (obtained via Drupal JSON API).

Alternatively, instead of sending $hazardType, $rcp, $timePeriod to the EMIKAT API for Impact Calculation, we could send two $eventIds: One for the baseline and a corresponding one ogf the same type (frequent || occasional || rare) chosen by the user in the Scenario Selection UI.

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

• the respective Heat Hazard HC-LE Resource is described here.
• Flood Hazard HC-LE Resource still pending

[DenoBeno]

As discussed today: For the flood hazard, we should at most put out few example resources until we can define the resources to work with variables.

maybe we should rename this into "...for heat". close it and open a new issue for the flood hazard?