Hazus AEBM card 2 progress

[karenng-civicsoftware]

Keep track of the production of AEBM story card 1. Progress was previously documented at gist

Link to card : link
LInk to front-end files: link
Link to file specifying REST API view: link

Team disaster

Here is a list of tasks to be completed to make sure the suggestions from Jordan, Doug, Ujvala are incorporated into our working demos of our cards.

1. make data science improvements

modify our data to represent the uncertainty

• round up casualty estimates. e.g.

  • <10 casualty at a location in the raw data should be displayed as 10
  • round up other estimates, e.g. raw number 15 should be rounded up to 20 in the API calls

• write out corrected data set as GeoJSON with a .shp shape file

• upload the ipynb files for generating the datasets that would be made available via the REST API calls

2. add the data to GitHub

• ask what column names could be accepted properly, the previous column names were not properly concatenated
• use the new API for serving static json

3. make backend improvements

make REST data API modifications

• profile PostGIS database and REST API calls to see which part is taking 40s - issue submitted here

• make sure new data set is used by the API by closing Update Aebm static json backend with rounded up data disaster-resilience-backend#54 and adopting PR Change views to use new AEBM json file #54 disaster-resilience-backend#55

• test that the API calls work https://service.civicpdx.org/disaster-resilience/

• ask the backend team to improve the load time for the REST API call

4. modify content in the frontend card files

see [guide]

Hazus card 2: link to card 2 frontend files

• check that we have restricted a minimum zoom level

Content checking

• validate that the words are copied correctly from google doc 2 link to the card

[karenng-civicsoftware]

Adding PR links to understand which files need to be changed for the cards:

https://github.com/hackoregon/civic/pull/1085/files
hackoregon/civic#1086