Which EMIKAT-generated resources do we need to include in the screening Data Package(s)?

[DenoBeno]

This is related to #18 and clarity-h2020/csis#91
Also related to: #45, #46, #47, #49

Issue at hand: if I understand our application model correctly, we have to list all the EMIKAT results as ressources with EMIKAT-specific variables in the URIs in the Data Packages that will be used for screening. Otherwise CSIS will not be able to visualize them.

@p-a-s-c-a-l , @helllth : is this correct/is this the way to go or not?

One example of such a resource is the "population density within the EU-wide data package (see https://csis.myclimateservice.eu/node/682 and https://csis.myclimateservice.eu/node/754)

@humerh: Which other resources is EMIKAT producing (or will produce) that need to be listed in this ? Impact tables? Impact maps? Impact tables and maps with adaptation options applied (in development/future)? Other? What are the links that need to be added?

Alternatively, we could produce special "screening" versions of the embedded applications that know what needs to be done. This would make it easier to produce screening data packages, but we would have to invest more in javascript application developments.

@p-a-s-c-a-l , @helllth : which way should we go in your opinion?

Any other issues that you are aware of, or ideas how to handle this?

[DenoBeno]

This is pretty much a showstopper IMO. We have to resolve this in order to produce screening results.

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

I want to keep everything as it is now! That is, no special apps for screening. Our current apps will replace EMIKAT variables like $emikat_id in resource URIs with values obtained from concrete studies.

This works and is implemented in the new map component. So there is no need for further action here.

ATM deployment of the new map component is delay until clarity-h2020/csis-helpers-module#10 is implemented.

[DenoBeno]

OK, but I presume that we still miss some resources in the data package ATM. E.g., there are no resources corresponding to EMIKAT impact calculation in the data package atm. Or are they?

[DenoBeno]

OK, I have just discussed this with Heinrich, and we have defined a second EMIKAT-generated data layer for the european data package:

https://csis.myclimateservice.eu/node/1272

This is based on the information in the wiki: https://github.com/clarity-h2020/csis/wiki/Services-endpoints-(used-by-CSIS)

etc.

As you can see, there is a whole lot of variables in this resource file. E.g.:

https://service.emikat.at/geoserver/clarity/wms?service=WMS&version=1.1.0&request=GetMap&layers=clarity%3Aview.2974&bbox=4672000.0%2C1979500.0%2C4687500.0%2C1988000.0&width=768&height=421&srs=EPSG%3A3035&format=image%2Fgif&CQL_FILTER=PROJECT%3D**$emikat_variant**%20and%20PERIOD=%27**$emikat_period**%27%20AND%20RCP=%27**$emikat_rcp**%27%20AND%20FREQUENCE=%27**$emikat_frequency**%27%20AND%20SZ_ID=**$emikat_id**&styles=T_A

See the wiki page for explanation of possible values for each of the variables.

An alternative would be to produce a ressource fiel for all combinations of the parameters, but this would be completely a nightmare to maintain.

How to proceed with this?

[DenoBeno]

The third resource produced by emikat is the "Impact Calculation (Mortality) for each Scenario, Time period, typical Events and for each Adaptation Project", also described in the wiki. Will require the same variables.