Support for Hazard Events [HC API]

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

This is related to the production of Heat Wave Hazard Events for Europe.

While hazard indexes are currently stored on METEOROID Geoserver and accessed by the Map Component for informative purposes, we need another API that is accessed by the [HC Events Table]() and the Scenario Selection UI.

The API would expect a parameter '$studyArea' or, if the study is already initialised, the '$studyId' (EMIKAT internal id) and additional a parameter $hazardEventType (name/id from the CSIS Hazards Taxonomy).

It's currently unclear, if it would make sense to show HC Events Layers in the HC Map. Therefore there is currently no need for an additional WMS Endpoint.

The respective HC Data Package Resource has to be updated accordingly and example request / response URLs have to be added to the Wiki.

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

See https://github.com/clarity-h2020/csis/issues/57#issuecomment-509101067

[bernhardsk]

The available requests are documented via Swagger: https://service.emikat.at/EmiKatTst/swagger/index.html

Some of the relevant functionalities:

1) For Europe wide Hazard Layers (currently: heat wave only): Table in AIT EMIKAT:

Requests:

JSON: https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_HAZARD_EVENTS_EUROPE.2036/table/data?rownum=1000

2846 = internal studyID (in emikat: scenarioID). "tab.CLY_HAZARD_EVENTS_EUROPE.2036" = emikat featureName For the first 1000 datasets. Total number of datasets in this table: 1210950

CSV: https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_HAZARD_EVENTS_EUROPE.2036/table/csv?rownum=1000

2) For regional Hazard Event datasets: Table in AIT EMIKAT:

JSON: https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_HAZARD_EVENTS_STUDY.2036/table/data?rownum=1000

CSV: https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_HAZARD_EVENTS_STUDY.2036/table/csv?rownum=1000

Also available (in general): GEOJSON and GEOTIFF. ...."/table/geojson?rownum=1000" or: ....."/table/geotiff"

Please let me know, if additional info is required.

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

Thanks @bernhardsk

Two more questions: 1) "The API would expect a parameter $studyArea or $studyId" This is currently not supported? We need the events relevant for the selected study area (bounding box). This bounding box is IMHO stored in EMIKAT when EMIKAT is notified about a new study. So an additional parameter $studyId (the EMIKAT internal id of the study) should be sufficient. However, the scenario id is already part of the URI (.../scenarios/2846/...), right? So the filtering by study area is not yet implemented? 2) The table layout will change when the new Hazard Events are available. So the new table structure would look like this, right?:

latitude	longitude	urban area	country	RCP	Period	Tx95p	Frequent(1.0)	Occasional(0.2)	Rare(0.05)
30.055091	-8.120772			baseline	19710101-20001231	39C	36C	38C	40C

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

FYI: Here are the heat wave events for the baseline climate for all of Europe.

[humerh]

The call

https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_HAZARD_EVENTS_STUDY.2036/table/data?rownum=1000

returns now all "relevant" events inside of study area.

The id "2846" has to be replaced by the $emikat_id .

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

ATM the API events for RCP45 only. Did you import all files from https://github.com/clarity-h2020/csis/issues/57#issuecomment-516723092 ?

[humerh]

All events are now imported.

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

No Hazard Data seems to be available for this study (AgiosDimitrios): https://service.emikat.at/EmiKatTst/api/scenarios/3189/feature/tab.CLY_HAZARD_EVENTS_STUDY.2036/table/data?rownum=1000

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

Same for this study (ALBA_IULIA): https://service.emikat.at/EmiKatTst/api/scenarios/3209/feature/tab.CLY_HAZARD_EVENTS_STUDY.2036/table/data?rownum=1000

[DenoBeno]

maybe the input data is still not on atos server?

On Wed, 25 Sep 2019, 14:21 Pascal Dihé, notifications@github.com wrote:

Same for this study https://csis.myclimateservice.eu/study/33/step/1460/view/table (ALBA_IULIA): https://service.emikat.at/EmiKatTst/api/scenarios/3209/feature/tab.CLY_HAZARD_EVENTS_STUDY.2036/table/data?rownum=1000

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/clarity-h2020/emikat/issues/11?email_source=notifications&email_token=AAWTC7TMFIWY7QKPLSO6WNLQLNJWLA5CNFSM4H4TNSC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7RWFJA#issuecomment-534995620, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWTC7SWEUHPQKBXHVT7EALQLNJWLANCNFSM4H4TNSCQ .

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

Then this would just affect HC-LE and not HC.

[humerh]

There are no "LAND_USE" date (Urban atlas data) available, so Emikat can not calculate.

[humerh]

If you want a support to calculate each location in Europe we have to define for all cities also the location specific parameters.

As an example:

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

There are no "LAND_USE" date (Urban atlas data) available, so Emikat can not calculate.

Cannot calculate what? HC or HC-LE. I thought HC (events) is independent of the HC-LE Urban Atlas input layers. So at least the EE and HC data should be available for whole Europe.

@negroscuro Can you please check if HC-LE input data is available for the following study areas: Alba Iulia and Athens. I could select both cities from the cities taxonomy, so I assume that a complete set of HC-LE input layers is available for those? Maybe they haven't been generated by your script yet?

[humerh]

Sorry, now I understand. Yes, I had a simlified implementation of the script for searching the "relevant events" for the study area. I filtered the table for the city names, which was placticable for NAPOLI and STOCKHOLM. But the table of Robert had not filled all cities. So I implemented yesterday an imporved script, which looks for the EVENTS, which are NEAREST the middlepoint of the study area, ignoring the given city names (urban area). This is now the functionality we decided in Frankfurt.