Revising available GL-Steps in Study type "Basic Screening: General"

[patrickkaleta]

Based on the Study Type, external services (like Emikat) can either be triggered for further calculations or not (see this).

Now, since for Basic Screening: General Emikat is not listed as the calculation method, Emikat is not triggered. Nonetheless the "Risk and Impact Assessment" step is available for this Study type and in the map the user can request the "heat mortality risk/impact screening" layer, but nothing is then shown, since nothing is available in Emikat (example: https://csis.myclimateservice.eu/study/19/step/1946/view/maps).

Question now is: Should Emikat also be triggered for this Study type or should we remove/replace the "Risk and Impact Assessment" step?

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

EMIKAT should not be triggered. This is a "show available EU-level data only" study type.

Whether we can remove the RA/IA step depends on whether there will be some EU-level RA/IA data available. ATM we even lack Exposure.

[DenoBeno]

I had some discussion about exposure last week and I'm convinced that we should be able to use the "local model input data " for exposure. If we could also visually superpose the hazard & exposure data on a map, we would even have something for the risk section. Pascal Dihé <[email protected]> schrieb am Fr., 17. Jan. 2020, 15:08:

…

EMIKAT should not be triggered. This is a "show available EU-level data only" study type. Whether we can remove the RA/IA step depends on whether there will be some EU-level RA/IA data available. ATM we even lack Exposure. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#132?email_source=notifications&email_token=AAWTC7TQIPKI6FFRUW5D2A3Q6G3XLA5CNFSM4KIIQKZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJHZDNA#issuecomment-575639988>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWTC7VJRMNRI2RZOWUFWHTQ6G3XLANCNFSM4KIIQKZA> .

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

in the map the user can request the "heat mortality risk/impact screening" layer

This is the expected behaviour. 😀

The reason for this is that for this Basic Screening Study, the European Wide Data Package for Automated Screening Studies is used instead of a Basic European Wide Data Package for Basic Screening Studies.