Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E exposure-lib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynamic ExposureDynamic Exposure
  • Global Dynamic ExposureGlobal Dynamic Exposure
  • exposure-lib
  • Merge requests
  • !9

Add damage tables

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Danijel Schorlemmer requested to merge feature/add-damage-table into master Mar 29, 2022
  • Overview 33
  • Commits 1
  • Pipelines 11
  • Changes 1

To enable the loss calculator to store multiple damage assessments per exposure asset, a couple of tables need to be added to the exposure-lib database definition. The tables are:

  • DamageAssessment storing the metadata of each damage assessment, being manual through inspection or fully automatic in the loss calculator
  • Damage storing the probability of a damage state with the dataset being linked to a damage assessment dataset
  • DamageState storing the names of the different damage states
  • DamageMethod storing the names of the different damage-assessment methods

A problem remains not perfectly solved: Each damage assessment currently carries a building_id and a quadkey to relate it to either a BuildingAsset or TileAsset. As a consequence, the BuildingAsset and TileAsset tables were unified into an Asset table.

\approve @tara @shinde

Edited Mar 30, 2022 by Danijel Schorlemmer
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/add-damage-table