Serialize Loss Maps to the OQ DB
Bug #797708 reported by
Lars Butler
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenQuake (deprecated) |
Fix Released
|
Critical
|
Gabriele Favalessa | ||
Bug Description
Currently, loss maps are only serialized to to XML (and I think GeoTiff as well). We should be able to support a user option for serializing to the DB or to XML.
| Changed in openquake: | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
Revision history for this message
| Gabriele Favalessa (favalex) wrote | #1 |
| tags: | added: database risk |
| Changed in openquake: | |
| assignee: | nobody → Gabriele Favalessa (favalex) |
| status: | Confirmed → In Progress |
| Changed in openquake: | |
| status: | In Progress → Fix Committed |
| Changed in openquake: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
There are two types of loss maps:
- Type 1: Output of the classical psha-based or probabilistic based
calculation and it is a map that provides the expected losses for a
certain probability of exceedance in a given time span. Example: expected
losses for a PE of 1% in 50 years
- Type 2: Output from the deterministic event-based calculator that provides
the mean loss and standard deviation for each asset for a given event
The only difference is in Type one, also the time span and probability of
exceedance needs to be stored, and per asset, we only have one value. In type
two it's only an event so nothing regarding probability needs to be stored and
per asset two values are stored, mean and stddev
Summing the loss values per site needs to be done to display loss maps.