[ ] Design of a simplified internal state data model in JSON (the "table model") and definition of static JSON constants (example) as initial reference / example data based on the example table content from the mock-up screens. The internal model should be identical to the JSON model implemented by EMIKAT REST API
[ ] Query EMIKAT REST API and retrieve all events (Baseline + all RCP/time combinations) and map to internal state model
[ ] Mapping of the actual Data Package Data Model to the internal JSON state data model with help of the JSON:API and/or REST Views and additional REST Micro Services for simple data aggregation and transformation.
Basic flow:
get meta information about EMIKAT REST API from Data Package (HC Resource) from cSIS REST API.
query EMIKAT Rest API with study area bbox to retrieve a table representative events for this area (30 events: 3 baseline and 27 future).
Goal is to show to the user a list of rare / frequent / occasional events in relation to RCP and time period so that he can make an informed choice for a RCP/time period of interest for impact calculation and adaption calculation.
For the table layout we start wit a simple list following the CSV structure, possibly highlighting the 3 baseline events.
humerh
commented
5 years ago
We have to provide a table component that shows events relevant for the chosen study area. In the long term, it could replace the current HC Table.
Status:
Basic flow:
Goal is to show to the user a list of rare / frequent / occasional events in relation to RCP and time period so that he can make an informed choice for a RCP/time period of interest for impact calculation and adaption calculation.
For the table layout we start wit a simple list following the CSV structure, possibly highlighting the 3 baseline events.