p-a-s-c-a-l
commented
5 years ago Now the result of Local effect calculation is also available as WMS-Maps:
In this link you can adapt the follwing parameters:
PROJECT=BASELINE ... (for future selection of an alternative ADAPTATION variants) PERIOD='Baseline' ... (Alternatives are: '20110101-20401231', '20410101-20701231' and '20710101-21001231') RCP='Baseline' ... (Alternatives are: 'rcp26', 'rcp45' and 'rcp85') FREQUENCE='Rare' ... (Alternatives are: 'Occassional' or 'Frequent')
@p-a-s-c-a-l , @therter please test and give me feedback, if this approach is ok.
SZ_ID=2846 has to be set to the current $emikatID
styles=T_A for Apparent temparature styles=T_TMRT for Mean Radiant Temperature styles=T_UTCI for UTCI Temperature
The color schemas (STYLE colors) are currently fixed but not optimized !!!!
humerh
DenoBeno
This is related to the calculation of tmrt.
Hazards with local effects /currently (tmrt based on Heat Wave Events) are (re-)calculated in EMIKAT and will be shown on the HC-LE Map and eventually in the HC-LE Table.
The API would probably expect just two parameters:
$studyAreaor, if the study is already initialised, just the '$studyId'$hazardEvents[]See this comment for the related explanation.That means, in contrast to previous ideas, we don't need parameters for RCP and time period because we force the user in the Scenario Selection UI (probably better called Event Selection UI) to chose one event from the baseline and one corresponding event of the same type (frequent, occasional, rare) from the future.
In principle, the API then returns the two HC-LE layers (tmrt) related to the two events chosen by the user. Atm, the implementation of the HC-LE Table is on hold, so we are currently just in need of a WMS Endpoint for the map.
The respective HC-LE Data Package Resource has to be updated accordingly and example request / response URLs have to be added to the Wiki.