Closed p-a-s-c-a-l closed 5 years ago
Visualisation of EMIKAT Impact Model Output in the Scenario Analysis Component (@bernhardsk values are probably wrong):
@stefanon / PLINIVS: Should we aggregate the values, e.g. by age groups or damage classes to make the indicator/criteria table look a bit simpler? For Example:
Information for single groups is still available in the IA Table.
@p-a-s-c-a-l yes, I think that the grouping you shown, by age classes (vulnerability classes), is the one to choose to show indicator table results in a more concise way.
ps.: that there is something weird with the vulnerability functions appear clearly looking at the impact and noting that it decreases with the increase of temperature.
Integrated branch 'feature/09-emikat-api (a9d37eb4296fa7d1f7c4d15337c0886201d73feb)' into 'dev (eff791b0f3c17dc8fce042cb3043a0d21e1614b8)' -- Build 25
done
Use EMIKAT REST API for Impact Results and perform some aggregation for Scenario Analysis. Follw the 4-step approach described here. Later, following the internal state data model of the table component.