New issue
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
Wizard - Volcano Polygon Population IF option #2107
Comments
PROBLEMAlso If we choose classified polygon hazard on population (fig.1) then the hazard layer will not be detected on (fig.2). Then we can not continue to run this IF wizard. Proposed SolutionMake it detect and run. CC : @samnawi @ismailsunni @timlinux @Charlotte-Morgan |
Hi @samnawi I can make one of them (or both) work for single event. But, we need to ask @Charlotte-Morgan whether is it right to make it so or not. Hi @fredychandra |
@fredychandra & @samnawi - can you please look at this again |
@ismailsunni I've used the latest version of InaSAFE 3.2, and it's look like I expect in the issue. But, for the IF that should be just in multiple event or also available in single event, my expectation is just if there is a data like pyroclastic flow or spread of the heat cloud, I think InaSAFE must have tool to calculate this impact. The data maybe just a footprint, so the attribute can be like the flood (impacted : yes or no). Thank you |
@ismailsunni I have check it and tested it again using Qgis 2.8.3 and InaSAFE 3.2 Dev-Master. It works :) . I am not sure for the last keyword that I using when rise this problem issue, but for this recent test I am using both generic classes and volcanic classes, and it works. |
Since we have set all IF to have both single and multiple event hazard category, we can close this ticket. See the PR #2251 |
Problem
There is a few confusion in the step of InaSAFE wizard.
I try to do an analysis volcano polygon population IF using the InaSAFE wizard.
In the step to select the polygon volcano hazard, there are 2 options:
Proposed Solution
Make it happy.
Make the overview for each class is clearer, because it's like ambiguously.
Maybe the overview can be written like this:
CC
Please add some comment from @ismailsunni and @fredychandra like we have been discussed before
The text was updated successfully, but these errors were encountered: