-
For example :
- earthquake and landslide
- flood and landslide
could be a batch process
-
# Problem
InaSAFE's metadata infrastructure is not designed, its evolved. Metadata is a critical of the whole application and it needs to be reviewed, revised and re-implemented in a globally consist…
-
Version -04
Push and Pull Access: There MUST be support for three methods of data access. The standard Pull model as well as solicited and unsolicited Push models. All of the methods of data acces…
-
Ariel would like to have (on top of each other):
- 1 map for admin unit level 0
- 1 map for admin unit level 1
- 1 map for admin unit level 2 (if admin level 2 has been selected for report generation)…
-
Additional detailed text should be available for users for each technical recommendation.
A "more information" link should be added in the UI. Clicking on the link should open a modal window.
-
# problem
Classified hazard data and data for hazard zones are not 'scenarios'
InaSAFE was designed to present users with a single hazard scenario. However, by introducing data for hazard zones (ras…
-
# problems
Firstly, the building inundation function (tsunami) allows users to specify an inundation threshold.
The results are reported as inundated (in water deeper than the threshold) and not inun…
-
# About the Climate Data
This page gives some information and links about the climate data used in this tool. if you read this page, you will understand:
1. The climatic component of the Biogeoclim…
-
@wmwv @cdfassnacht @saurabhwjha and @DarkEnergyScienceCollaboration/twinkles
In the SRM we hazarded a guess at what an appropriate division between Twinkles 1 and 2 should be, and came up with somet…
-
# Background:
We (RnV) have been invited to contribute display materials for the CDSP (Capacity Development Support Program) closing event. This is an opportunity to showcase the work of AIFDR and in…