We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep track of the production of AEBM story card 1. Progress was previously documented at gist
Link to card: link
Link to frontend files: link
Link to file specifying REST API view: link
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.
ipynb
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
see [guide]
The text was updated successfully, but these errors were encountered:
karenng-civicsoftware
No branches or pull requests
Keep track of the production of AEBM story card 1. Progress was previously documented at gist
Link to card: link
Link to frontend 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
ipynb
files for generating the datasets that would be made available via the REST API calls2. add the data to GitHub
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 1: Building loss ratio link to card 1 frontend files
Content checking
The text was updated successfully, but these errors were encountered: