-
Notifications
You must be signed in to change notification settings - Fork 0
EMIKAT tables always show the same data #20
Comments
This comment has been minimized.
This comment has been minimized.
As you see in the screenshot the displayed data are in both cases from Emikat-ID=3189 (SZM_SZENARIO_REF). |
As you can see, the requests to EMIKAT API contain different scenario ids (3174, 3210). So the problem is most likely on EMIKAT side.
Period: historical, Scenario: Historical, Frequency: yearly, Variant: no Adaptation Options
Period: historical, Scenario: Historical, Frequency: yearly, Variant: no Adaptation Options |
In which screenshot? The screenshots above (#20 (comment)) show the ids 3174 and 3210. |
You see it in the displayed table. The last column is SZM_SZENARIO_REF (which should be the same as the 'emikatId') |
I updated the server and the error should be corrected! |
Hu. Good. Don't do this to me. I'm not so young anymore... :-D |
I'm not sure if this is correct data now or not, but it would be nice if the coordinates we show would all be in the same coordinate system: https://csis.myclimateservice.eu/study/35/step/1524/view/table Same for exposure and for impact table. but |
Not sure if it's because of EMIKAT or because of the table component, but https://csis.myclimateservice.eu/study/30/step/1613/view/table and https://csis.myclimateservice.eu/study/14/step/1651/view/table show exactly the same data.
One is in Naples and the other in Vienna. Not good. Not good at all. :-(
The same is true also for the impact tables
https://csis.myclimateservice.eu/study/14/step/1650/view/table
https://csis.myclimateservice.eu/study/30/step/1612/view/table
E.g., sort by population and this is what you will see:
The text was updated successfully, but these errors were encountered: