NRML model for aggregate loss curves

Bug #823801 reported by Lars Butler
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenQuake (deprecated)
Fix Released
Medium
Lars Butler

Bug Description

[et=8h]
[at=1.5h]

We are modeling aggregate loss curves in the database, but we do not have a corresponding NRML model.

For this bug, schema (xsd) and example files need to be created. The actual serializer code and integration into the calculators should be implemented in separate bugs. (Aggregate loss curve export: bug # 920543)

Here's what I have in mind for aggregate loss curve XML structure. It's roughly the structure of loss curve results, except simpler.

<?xml version="1.0"?>
<nrml xmlns:gml="http://www.opengis.net/gml"
      xmlns="http://openquake.org/xmlns/nrml/0.3"
      gml:id="n1">

    <!-- riskResult is a gml:Feature -->
    <riskResult gml:id="alc1">
        <config/>
        <!-- There is a single aggregate loss curve associated with the input exposure model. Thus, there is only a single aggregate loss curve per calculation. -->
        <aggregateLossCurve>
          <loss>0.0 100.0 200.0</loss>
          <poE>0.4 0.2 0.1</poE>
        </aggregateLossCurve>
    </riskResult>
</nrml>

Tags: nrml risk
description: updated
tags: added: nrml
tags: added: risk
John Tarter (toh2)
Changed in openquake:
milestone: none → 0.5.1
John Tarter (toh2)
Changed in openquake:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Lars Butler (lars-butler)
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Lars Butler (lars-butler) wrote :

This bug should be addressed first: bug # 904202 (boot strapping the NRML repo).

Changed in openquake:
status: Confirmed → In Progress
Revision history for this message
Lars Butler (lars-butler) wrote :
Changed in openquake:
status: In Progress → Fix Committed
description: updated
Changed in openquake:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.