Create Data Package for DC1

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

Create local Data Package for DC1 "Adaptation Scenarios for Metropolitan Resilience Planning in Naples".

To be discussed if this is the same as the 1st Data Package?

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

1st Data Package currently being produced should contain resources for screening on European Level, so the DC1 Data Package is different. DC1 Data Package will support screening using local data from the city of Naples, so we can make a comparison / validation of our models.

There are however some open issue to discuss. E.g. European-Level Population Data doesn't include information on age group distribution, while the local data does. The question here is, also directed at @bernhardsk and @humerh, whether the screening impact models/ algorithms for HW/Population now don't take vulnerability classes and probably also damage classes at all into account?

[bernhardsk]

1) Vulnerability classes still to be considered? MAYBE!: According to the revised impact calculation for heat waves from PLINIVS, the vulnerability functions do not distinguish between vulnerability classes, which means that the "weight" put on each vulnerability class from the impact calculation will be the same. However, the exposure of elements at risk (people per vulnerability class) will be different. (e.g. there are probably more "Age15-65" people per cell than "Age<14" people). We can either keep the vulnerability classes to show the difference in the number of exposed people per vulnerability class to users (if the (regional) data is available) (however, the total sum will be the same when calculating impact with or without vulnerability classes) or remove the support for vulnerability classes. @alecapolupo What do you think about this? For the current implementation in AIT EMIKAT it doesn't really make to big of a difference (statement to be checked by @humerh ).

From the current flooding model, I do not know whether the vulnerability functions for flooding will support different vulnerability classes. @alecapolupo can you help us/me out here? Could you provide us with the documentation?

2) Damage classes still to be considered? YES!: The heat wave impact calculation methodology still supports damage classes and even added 1 dimension of damage levels:

Categorization 1:

• D0 = no damage;
• D1 = Death (= "incremental mortality rate" meaning additional deaths) starting with 1.3% @21.5°C apparent temperature for mediterranean areas and 1.3% @18.2°C apparent temperature for north-continental areas) (see slide 16 from the link below)

Categorization 2:

• D0 = No damage (for UTCI from 9 to 26);
• D1 = Caution (moderate heat stress, warm) (for UTCI from 26 to 32);
• D2 = Extreme caution (strong heat stress, hot) (for UTCI from 32 to 38);
• D3 = Danger (extreme heat stress, very hot) (for UTCI from 38 to 46);
• D4 = Extreme danger (sweltering) (for UTCI from 46 to 54);

Both types of categorization are to be applied.

Categorization 1 has the apparent temperature (TA) as Input, while categorization 2 has the UTCI as Input).

Tmrt (mean radiant temperature) is calculated by the local effect calculation. UTCI can be calculated from Tmrt and 1 constant value for wind and 1 constant value for humidity. (+ more? @alecapolupo ) The apparent temperature (TA) can be calculated from UTCI and some other inputs. (@alecapolupo which ones?) The apparent temperature is NOT air temperature.

Some of the documentation can be found here: https://newrepository.atosresearch.eu/index.php/apps/files?dir=/CLARITY/Events/Project%20Events/Plenary%20Meetings/2019-07-03_05%20Project%20Meeting%20(Vienna)/Presentations&fileid=132746 File: "CLARITY_WP_v0.2"

@alecapolupo please check if all of my above statements are correct ;)

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

The heat wave impact calculation methodology still supports damage classes and even added 1 dimension of damage levels:

OK, but please keep in mind that this is something to be considered later, not now. Supporting two categories of impact in one study is something we are not going to support in the first place. This adds additional complexity which we cannot afford at the moment. We need a minimal viable product ASAP. Therefore we'll start with implementing Categorization 1 and then, once the complete system is fully operational, we can gradually increase complexity.

[ghost]

Hi everyone,

we have just uploaded the documentation related to HW impact calculation.

Regards, Ale

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

It seems that there is quite some misunderstanding on what the CSIS is able to offer in terms of Data Packages. The CSIS can manage the Meta Data represented by Data Packages and Data Package Resources but it is within the sole responsibility of the user to make the actual data available and accessible via public services.

The Data Package for DC1 does not yet exist. The data is available on CLARITY sFTP but not yet accessible via EMIKAT and OGC WMS as required by CSIS, the dataset descriptions (meta-data) are available in CKAN, but not yet as Data Package metadata in CSIS.

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

FYI: I've create a wiki page that explains how to use Template Resources in Data Packages. An example can be found here.

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

I had a look at DC1 data described in CKAN and CLARITY sFTP (sftp://5.79.69.49/clarityftp/dc1-naples/), but I have no clue how to map this to respective Hazard, exposure, Impact, .. resources in the Data Package. Furthermore, the data has to be made available

• on CLARITY GeoServer in order to show it on CSIS maps
• in EMIKAT to be able to perform the impact calculation.

Again, I have no idea what this data is about (e.g. sftp://5.79.69.49/clarityftp/dc1-naples/local_effects_results%20/Muklimo_outputs/sample_area_2/muklimo_V141010_100.nc) and where and how make it available online for integration in CSIS.

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

Data Package in CSIS (incomplete): DC1 - Naples Metropolitan Area Data Package