Reading Hazard/Risk Outputs

Registered by John Tarter on 2012-01-25

The intent of this blueprint is to identify options to enable the reading of Hazard/Risk outputs from the database or user folders, if security settings allow.
As the approach to do this work will be the same for both Hazard and Risk output, I have expanded the scope of this blueprint to cover both areas of interest.

Background:

At this time all the Hazard calculators write to the database with the exception of the Disaggregation calculator which writes to the user's folders. Examples of the data in the user folders are XML/HDF5

The data stored in the database is normalized without any XML encoding. Geometry information such as Point info for hazard curves is also stored in the database.

Suggested solution
We would start with an API that would support some common functions such as: list_foo(some_id), list_bar(some_id), export_this(id), export_that(id), etc. display calculation id and a brief description

These API functions could be called either by a CLI or a lightweight GUI.

As we have Django model class to represent each table in the DB, we don't actually have to write any queries; instead, we would do Django ORM operations within the code

Next stage would be enable a number of formats for data export. Examples would be NRML XML, SHP....

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
John Tarter
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.