Basic European Wide Data Package for Basic Screening Studies

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

A copy of the European Data Package that is usable in Basic Screening Studies has to be created with all EMIKAT resources removed and some additional exposure and impact resources added. There are no dedicated exposure datasets available in the European Data Package apart from those calculated by EMIKAT. They are, however, usable in Automated Screening Studies only. Same applies to Impact.

Basic Screening Studies

The user can perform a "basic screening study" to get an idea of which climate hazards may affect which elements at risk in a specific area. No impact (calculation) is available. Main feature is the ability to show hazard indices produced by WP3 related to a specificity RCP / time period and exposure data on a map in a study area defined by the user, make screen shots of the maps, add a few "twins" (hazard twins, solution offers, showcases), select some generic adaptation options and generate a PDF report.

Automated Screening Studies

The user can perform an "automated screening study" for a number of supported metropolitan regions to assess the impact of heat wave events on population (mortality rate) referring to a specific RCP, time period and event frequency. Later also pluvial flood will be added.
The user can show HC (heat wave, pluvial flood), HC-LE ("downscaled" TMRT taking local land use information from e.g. Urban Atlas into account), exposure (population distribution) as well as calculated impact (mortality rate) on a map. Rudimentary tabular visualisation of HC, EE and IA data and CSV and GeoJSON export is available. The user can add a few "twins" (hazard twins, solution offers, showcases) and generic Adaptation Options to the report, rudimentary "scenario analysis" for one indicator (mortality rate) is available, too.

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

Did you have a look at this @DanielRodera

[DanielRodera]

Hi, I will take a look with Alejandro withing today

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

See #60

[DanielRodera]

I have tried this module in my local instance and it works,

Is quite straight forward to use, once installed you have to clear the cache and in the Data Package module will appear a button called "clone". Is just a matter of clicking it and a copy of the DP will be generated.

@patrickkaleta, would you mind install the module on the CSIS? once installed I will remove the Emikat resources.

Thank you!

[patrickkaleta]

I have tried this module in my local instance and it works,

Is quite straight forward to use, once installed you have to clear the cache and in the Data Package module will appear a button called "clone". Is just a matter of clicking it and a copy of the DP will be generated.

@patrickkaleta, would you mind install the module on the CSIS? once installed I will remove the Emikat resources.

Thank you!

The module is now available in the CSIS.

[DenoBeno]

Cloning the data packages is probably OK, but cloning the lower level entities could cause trouble. What is the consequence of cloning the data package on all the resources and other entities that are linked within it? Do they all get cloned too? Ideally they shouldn't be, but the paragraphs (do we use any?) should.
Assuming that this both works as it should, we still have one problem: cloning an entity where sub-entities are used where paragraphs should have been used...

---

Use cloning with care and don't let the normal users use this, at least for now.

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

We just need a shallow copy of the Screening Data Package. Resources have to be cloned by reference not by value. Otherwise updates in either data package won't be reflected. We don't want to duplicate all resources.

[patrickkaleta]

Use cloning with care and don't let the normal users use this, at least for now.

Yes, you're absolutely right. For this very specific use case here it's ok to use this module and @DanielRodera is aware of what the module can and can't do. This module can only be used by admins and no one else.

[DanielRodera]

Hi,

The module only clones the Data Package (only the first level) not the dp_resource, dp_source neither the dp_contributor, the rest are references to the original nodes. If we want to add/remove more resources or other of the DP attributes we will have to do it manually.

@patrickkaleta could you please install the module on the csis-dev.ait.ac.at.?? thanks!

[patrickkaleta]

@patrickkaleta could you please install the module on the csis-dev.ait.ac.at.?? thanks!

@DanielRodera it's done, you should be able to use is on that site.

[DanielRodera]

Thank you @patrickkaleta,

I have cloned the Data Package, I have named Clone of European Wide Data Package,

@p-a-s-c-a-l , could you please check if is what we are looking for? thanks!

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

O.K. This looks good, thanks!
I think can now go ahead , clone the DP in csis.myclimateservice.eu instance and remove resources that require a EMIKAT Study ID.

[DanielRodera]

Good to know ^^, I have cloned the DP and I named it as Clone of European Wide Data Package. I will remove the references to EMIKAT ASAP and I will let you know.

[DanielRodera]

Done,

FYI, making some tests in the dev instance of the CSIS I have removed one dp_resource by mistake. My apologies...

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

FYI, making some tests in the dev instance of the CSIS I have removed one dp_resource by mistake. My apologies...

which one? Did you delete the actual dp_resource instance or did you just remove it from the data package?

[patrickkaleta]

Done,

FYI, making some tests in the dev instance of the CSIS I have removed one dp_resource by mistake. My apologies...

@DanielRodera with "dev instance of the CSIS" I'm guessing that you're talking about this URL:
https://csis-dev.ait.ac.at/ right?
If that's the case than it doesn't really matter that a resource got deleted.

Looking at the log files of or "main" CSIS I don't see anything about a deleted resource yesterday, so everthing should be fine.

[DanielRodera]

@DanielRodera with "dev instance of the CSIS" I'm guessing that you're talking about this URL:
https://csis-dev.ait.ac.at/ right?

@patrickkaleta, yes, I am talking about https://csis-dev.ait.ac.at/.

If that's the case than it doesn't really matter that a resource got deleted.

Uff, good to know^^

which one? Did you delete the actual dp_resource instance or did you just remove it from the data package?

@p-a-s-c-a-l , In the "main" CSIS (https://csis.myclimateservice.eu), I removed the references to the dp_resources from the cloned DP which requires an EMIKAT Study ID, as we agreed. I didn't touch the original one.

Sorry again for this!

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

In the Basic Screening Study, we need to show some Exposure, Hazard and "Impact" because EMIKAT result's aren't available.:

• Hazard: This is easy, We can directly use the European Hazard resources
• Exposure: Here we want to the the HC-LE input layers, re-tagging them as exposure
• Impact: Here we want to show Hazard and Exposure resources (see above)

In order to re-tag the resources, we have to assign different EU-GL step taxonomy terms. Therefore we would have to copy the respective resource, including all hazard resources. But only after this issue has been resolved.

However copying the resources just for the purpose of assigning different tags is not only conceptually inconsistent (hazard != impact), it introduces also redundancy that we don't want.

Instead, we could delegate the different handling of resources in different contexts (basic vs. automated screening) to step templates. We could extend the GL-STEP entity type's field field_field_eu_gl_methodology (btw, why field_field?) by a secondary field_alternate_eu_gl_methodology and change the Basic Screening Templates accordingly.

While this could influence the map layers shown for each step if the map component respects the alternate field, it would not change the 'data tab'. Furthermore, HC-LE resources like this one are not assigned a EU-GL taxonomy tag, so we would have to copy & change them anyway.

@fgeyer16 @patrickkaleta
Any idea for a clean solution that does not require to copy all resources?

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

Generic filtering by arbitrary taxonomy id is not easily possible. See clarity-h2020/map-component#96 (comment)

So we have to use the name field, which is also the "title" of a taxonomy term. 😒

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

Map is updated and shows e.g. on RA/IA Map 'CLARITY Background' as 'Elements at Risk' + Hazard Layers. Test Study available here.

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

It's not perfect yet, but it's working. So closing. Ideas for improvement are discussed here.