Skip to content

Faulted Earth 0.3 Fault Sources Generator

Jump to bottom
bwyss edited this page May 10, 2011 · 6 revisions

Notes

The Global Active Fault and Seismic Zone Database project will produce a database with two fundamental layers:

  • an active fault layer containing site data – primarily the field observational data (observed data)
  • a seismic source layer containing parameters required for PSHA (inferred data)

The seismic source layer is considered an initial “strawman” to be improved via integration and collaboration with other GEM (database) projects. The project will progress in close collaboration with past, present, and new regional active fault and seismic source database projects such as the ILP databases, ReSeis in Central America, FAUST, SHARE, EMME, SEA, national programmes (e.g. Japan, USA, New Zealand, China), with GEM MF, and with other global and regional seismicity and geodesy projects.

The Global Active Fault and Seismic Zone Database project requires a tool to gather the geometry of faults and fault sections, associate observations with that geometry, create a summary form that represents the properties of the fault section, and generates a fault section from the summary table. This project aims to provide non-technical users an easy to use tool to add their information into the system. Please see a brief outline of the workflow for the tool under 'Design' (Figure 1):

Assumptions

  • The Fault database has a pre-calculating step that prepares the fault observations data into the expected 10 required attributes (could be as simple as documentation)
  • The user has fault section geometry in .shp format, or has the ability to accurately digitize a fault section
  • The user has (in some cases) field observations for fault sections
  • The 10 required fields in the fault section summary form are enough information to generate a fault source
  • The fault source output has the required attributes for the modeler's toolkit

Design

The main workflow of version one of the Fault Source Generator tool is as follows:

  • The user will fill in an observation form that captures the observation attributes, this will be written to a db.
  • The user will need to create a polyline or upload a .shp file that contains a poly line that represents fault sections
  • They can then use the feature editor tool to edit an existing fault section.
  • The user will then be presented a fault summary form that describes the fault section
  • In the fault summary from the user can then select observations to associate with that fault section
  • A graphical representation of the geometry associated with the summary table and or fault table is available to the user through each step of the process.

future versions should be able to…

  • The tool should allow the user to capture uncertainty in the fault section.
  • The user should be able to take several fault sections and join them into a fault, or take a fault and break it into sections.
  • The summary form should be made semi-automated by the fields in the observation table.
  • The summary table is then passed through a computation process to generate a fault source.
  • The system should be auditable, the metadata should allow full transparency of all the steps taken derive the fault source.
  • The future version will allow for observation editing.
  • Future versions of the tool will allow for multiple summary tables to be joined to create a SuperSection(©) that is editable.

Figure 1: work-flow for the Faulted Source Fault Source Generator Tool:

The tool requires a Django server API for the observation forms that can be found here:Django server api

User stories:

  • Implement an instance of a web mapping client template for example readygxp
  • Implement an instance of GeoNode (or build upon a centralized GEM GeoNode instance)
  • Geometry uploader with .shp file support (other formats?)
  • Observation uploader will allow for attributes to be added to the system (file/data formats?)
  • Python computation to generate fault sources
  • NRML (Natural hazards’ Risk Markup Language) schema for fault sources

Suggested Implementation

The tool should use an instance of GeoNode, or it should be based on an centralized GEM GeoNode instance. Consider a tool called readygxp (http://github.com/opengeo/readygxp) which gives us an all-purpose web mapping client template that includes the GeoNode stack.

Back to Blueprints

Clone this wiki locally