Replies: 7 comments 33 replies
-
|
Why can't we use Pier to map to deep foundation. What does Pier mean? Is that different than Pile? |
Beta Was this translation helpful? Give feedback.
-
|
In terms of basements, we could combine the two with a uniform distribution for finished and unfinished and allow for random sampling. |
Beta Was this translation helpful? Give feedback.
-
|
In terms of construction engineered vs non-engineered, it seems we do not have a clear identification of either - can we map an uncertainty distribution that averages them both using a uniform? I do not believe the construction type is universally dependable. |
Beta Was this translation helpful? Give feedback.
-
|
I think we could take a stab at assigning the content curves by occupancy type - will you propose a map based on occupancy class? |
Beta Was this translation helpful? Give feedback.
-
|
Hello all, I just joined the discussion thread. We are just talking about coastal storm surge depth damage functions, correct? |
Beta Was this translation helpful? Give feedback.
-
|
Some considerations: It seems like for the NACCS functions, whether you use the minimum, most likely, or maximum DDF is dependent on foundation type, construction type, age, # stories and height above the 1st floor, etc.. You could create a "damage function matrix" that would assign a damage function by linking these factors from the NACCS function to the cooresponding factor in the NSI. This is similar to how damage functions are assigned in Beach-fx. For example, Your matrix headings would be occupancytype, construction type, foundation type, age, number of stories, height above the 1st floor, 1st floor use. Pulling these criteria out of the NACCS Depth Damage Function Summary document tabular descriptions would be somewhat messy and there would be some transcription involved due to lack of uniformity in the tables, but it seems like it could be done. (for example, Table 48 of the document in the following link) |
Beta Was this translation helpful? Give feedback.
-
|
This is the document that we tend to use for our non-residential depth damage functions. This is the IWR 2013 nonresidential DDFs based on expert ellicitation. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
go-consequences is attempting to develop a library that supports evaluation of damages to consequences receptors across multiple hazard types. For a structure, the process for computing consequences boils down to a single method "Compute(h hazards.HazardEvent)" where a HazardEvent can be a flood event, or a coastal event. This means that a structure is intended to be able to respond to either hazard. In order to do that we leverage the occupancy type to store damage functions for many hazards.
Currently, the data source for structures is the National Structure Inventory. This means we are attempting to assign damage functions to the standardized occupancy types defined in the NSI schema.
There are some rigidities to overcome in mapping coastal damage functions (PFRA and NACCS) to the existing 40 occupancy types. These rigidities come down to the existence of coastal damage functions unique to structure attributes (some existing in NSI, and some not) so that many coastal damage functions may potentially be mapped to a single existing occupancy type.
Beta Was this translation helpful? Give feedback.
All reactions