-
For each specific function we need to document standard information:
- What formats are supported (raster / vector)
- For vector what attributes are mandatory
- For vector what attributes are optional…
-
### problem
The terminology used to describe relative hazard is inconsistent.
We should use the term medium and not moderate.
The term in the impact function notes should be the same as the term used…
-
I set up a first form to add disaster info!
![capture d ecran 2016-09-07 a 22 34 12](https://cloud.githubusercontent.com/assets/10407788/18335464/83600c42-754d-11e6-918f-f6db45c622f8.png)
I tried t…
-
We should copy small versions to the unit data directory that let the fast tests run. Here is the full log of the 34 tests that are failing because of missing datasets.
```
geonode)ubuntu@domU-12-31…
-
### Problem
Titles vary from map to map. We need consistency across maps.
### Proposed Solution
Make all report titles consistent with the new standards found in https://github.com/inasafe/inasafe/b…
-
# Problem
The Building Type Report Table still reporting zero (o) and No data if run IF with aggregation. The implication is the report become too long and truncation in the lateral side.
The table …
-
### Problem
I get some problems when I run with InaSAFE develop 3.5, and process the population raster data with some hazards (earthquake, flood, landslide). The process can not work properly. All of…
-
@samnawi could you please add your feedback to this ticket on filtering on the website. In particular your feedback on MMI, timeframe and number of records.
-
### Problem
I run analysis using the continuous raster earthquake hazard vs building polygon in InaSAFE 3.4.0 on QGIS 2.14.1 but I got an aggregation error, eventhough i did not load any aggregation …
-
# Proposal
We need a better system for impact functions to describe their metadata. Major features of the improved system should be:
- deprecate the use of docstrings to store the metadata. These are…