-
# Problem
The current IF inheritance architecture follows the commonality of layer types interacting. This is helping consolidate the impact function calculations. The reports have commonality along …
-
# Status
**This is a draft** This RFC is a formalisation of the requirements described in #410
# Problem
Our tools are already pretty easy to use, but in #410 and the Jogja workshop of Nov 2012 (che…
-
# problem
the following errors are reported for EQ Building function. InaSAFE 3.0 & Padang earthquake scenario.
1. python error when running EQ impact function using data preloaded in QGIS.
```
An …
-
# problem
the default threshold values of 0.34, 0.67, 1 seem a little low for MMI values and return 0 impacted people.
I'm not sure what these defaults relate to.
# proposed solution
Generic impact…
-
# Problem
The InaSAFE Window when you first open QGIS (with no data has the below text. This information needs to be updated due to InaSAFE2.0 new functionality and the change from AusAID to Australi…
-
Hi all,
I prepared an exercise for tomorrow's InaSAFE session.
in case of utilising OSM data (I used HOT export to extract available OSM building polygon features) for exposure data. I discovered tha…
-
# Problem
We need to have proper metadata available for each impact function. This is needed for wizards (see #862 and #703). In general too all Impact Functions should have their metadata well defin…
-
While preparing for the 0.5 release Ismail and myself discovered a case where an analysis can fail. The scenario used was Padang earthquake sumatra and the population layer. If you zoom in a lot so th…
-
Kristy Van Putten recently wrote two new impact functions:
impact_functions.generic.categorised_hazard_building_impact
impact_functions.generic.categorised_hazard_population
However,…
-
With Polygon hazard layers coming on (issues #36 and #48) we need to rewrite the impact functions to sensibly make use of this layer type. Kristy made a start in flood_building_impact.py.