inasafe/inasafe-fba
Next generation of InaSAFE that includes support for forecast based action
JavaScriptMIT
Issues
- 2
Duplicate rows in summary tables
#56 opened by timlinux - 2
Document Road Type Vulnerability score mapping
#76 opened by lucernae - 3
Caching vs WMS
#48 opened by NyakudyaA - 1
We need to add population support
#5 opened by lucernae - 1
Discuss why trigger evaluation is blocking
#3 opened by lucernae - 1
Document server side development process
#2 opened by lucernae - 3
Adding population to the summary tables
#57 opened by timlinux - 2
Landing page updates
#70 opened by timlinux - 6
Document/dump the staging schema to the repo
#42 opened by lucernae - 1
Impacted roads legend should match buildings
#47 opened by timlinux - 2
Clean up production db
#51 opened by timlinux - 1
fix upload flood on front end
#63 opened by anitanh - 0
- 5
Please show reporting points on the map
#60 opened by timlinux - 1
- 0
Finalising FBA
#55 opened by timlinux - 5
- 0
Kartoza logo in sheet
#45 opened by timlinux - 0
- 1
github pages with a DNS entry
#50 opened by anitanh - 1
Highlight which tab is active
#34 opened by NyakudyaA - 0
- 1
- 6
- 4
Incorrect legend shown when roads tab is active
#36 opened by NyakudyaA - 0
- 1
- 4
Affected roads must go on the map
#16 opened by timlinux - 2
Building and roads charts should be tabbed
#21 opened by timlinux - 2
Chart scaling needs to be adjusted
#26 opened by timlinux - 1
Legend font should match site
#18 opened by timlinux - 0
Github link should be updated
#20 opened by timlinux - 0
Spreadsheet cartography
#27 opened by timlinux - 1
- 0
Improve developer docs
#15 opened by timlinux - 4
We need to finish supporting roads
#7 opened by anitanh - 1
Spatial files for reporting point
#11 opened by lucernae - 0
Action points from Hassan regarding flood map
#12 opened by lucernae - 1
- 0
Anita please document the client / front end process. Including coding standards, deployment process etc. Put in documents/3-front-end-development.md
#4 opened by lucernae - 0