inasafe
inasafe copied to clipboard
inasafe
analysis area without aggregation
Problem
The multi exposure analysis tool is not recognising the analysis extent set by the set analysis area tool.
When I set the analysis area by dragging on the map (no aggregation data loaded) the multi exposure analysis ran successfully. However, it ran for the extent of the data not the defined analysis area.
eg Maumere tsunami on raster pop, OSM buildings and OSM roads
When a single exposure was run using the same data and environment, the analysis was limited to the analysis area that had been set as expected.
proposed solution
make it happy
For now, we don't support any extent options in the multiexposure analysis. Only the intersection of hazard and exposure is supported, the one that will be used on realtime. Some options are not well suited for a multiexposure analysis, such as exposure extent.
We got some discussions with Tim on gitter: November 16, 2017 2:07 PM
We should add some help.
My take on this is that the primary use is to mirror what will happen in realtime when a shake / volcano etc occurs. In those cases we would not be setting any analysis extent and the analysis should reflect either the intersection of the hazard and exposure or (my preferred option) the aggregation areas that intersect the hazard. That said I guess it should not be (too?) hard for @Gustry to have an analysis extent property for the multi-exposure IF that is then propagated to each of the internal impact function runs...?
Having chatted more to @Gustry I dont think it makes sense trying to support rectangular extents here...feel free to make a good case for it if you have one @Charlotte-Morgan otherwise I suggest we mark this as 'not supported'
@timlinux - I agree that it does not make sense ... but I'm thinking about what we should say in the help. .. and what our default extents should be. Jakarta flood analysis should be extent of population - ie pop outside flood extent are not exposed - assumes a default aggregation of the DKI boundary as pop data are clipped to that EQ extent should be the hazard extent or aggregation if used Ash is a bit like flood but we don't have a constantly defined extent