[WIP] Added vulnerability score #5072
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pierrealixt
force-pushed
the
fbf-vulnerability-post-processor
branch
from
2d05220
to
fbfd064
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First attempt to add the concept of vulnerability score to Inasafe.
Given an exposure layer with a field
vul_score(hard-coded in the xml metadata), it will sum the buildings' vulnerability score by hazard and aggregation.I'm sure a more elegant solution is out there, I'm not a big fan of the
ifconditions insummary_1_aggregate_hazard.py.