2.4.1. Inputs

The following files must be provided by the user to execute the workflow.

2.4.1.1. Configuration File

JSON file containing simulation details and specifies the application selected for each workflow step.

properties

  • runDir

Directory where input_data folder is located.

type

path

  • localAppDir

Directory where applications folder is located.

type

path

  • units

Dictionary of strings which specifiy units for force, length, and time.

type

string

default

N, m, sec

  • outputs

Indicator (True/False) of which workflow outputs (EDP, DM, DV) are provided in the simulation.

type

bool

default

true

  • Applications

Dictionary of applications selected for each workflow step, with their associated application-specific inputs.

type

dict

2.4.1.2. Building Source File

CSV file containing building properties for the response simulation and damage/loss estimation steps of the workflow. This file contains all information necessary for constructing BIM files for each building asset. Required headers are grouped into categories, as follows:

properties

  • Basic

Headers required for all hazard types, including Earthquake/Wind/Flood.

  • Wind

Headers only required for Wind hazards.

  • Flood

Headers only required for Flood hazards.

  • OptionalInputs

(Optional) Additional column headers which may be included for custom building definitions. For example, structural model parameters used in the Simulation application or alternate building classifications used in the DL application may be specified here.

The header schema, followed by an example input, is provided. Definitions for the keywords are given in the Custom Inventory sheet.

Table 2.4.1.1 InputDataSchema.csv

Basic

Basic

Basic

Basic

Basic

Basic

Basic

Basic

Basic

Basic

Wind

Wind

Wind

Wind

Wind

Wind

Wind

Wind

Wind

Wind

Wind

Wind

Wind

Flood

Flood

Flood

Flood

*OptionalInputs

id

Longitude

Latitude

OccupancyClass

BuildingType

StructureType

YearBuilt

NumberofStories

PlanArea

ReplacementCost

RoofShape

RoofSlope

RoofCover

RoofSystem

MeanRoofHt

WindowArea

Garage

NoUnits

DesignLevel

DSWII

WindZone

AvgJanTemp

z0

SplitLevel

FirstFloorHt

FoundationType

FloodZone

1

39.41770296

-74.50360821

RES1

3001

1956

2

1310.670302

1

Gable

0

5701

Wood

26.76835396

0

0

1

NE

122.279935

I

Above

0.35

NO

-2.97

3505

6112

2.4.1.3. Transportation Network Source File Option 1

A JSON file containing highway transportation roadways, bridges, and tunnels for the response simulation and damage/loss estimation steps of the workflow. This file contains all the information necessary for constructing AIM files for each bridge, tunnel, and roadway. The JSON file must contain the “nodes” object and at lease one of the “hwy_bridges”, “hwy_tunnels”, and “roadways” object. Involved key-item pairs are:

  • “hwy_bridges”: A JSON array of JSON Objects, each containing the following key/item pairs

Table 2.4.1.2 InputDataSchemaBridge.csv

Earthquake Required

Earthquake Required

Earthquake Required

Earthquake Required

Basic

Basic

Basic

*OptionalInputs

Key

ID

location

bridge_class

year_built

state_code

nspans

lmaxspan

Item

A string of the bridge ID.

An integer of the ID of the node that describes the location of the bridge.

A three-digit integer describes the bridge class as defined in the HAZUS Inventory Technical Manual (FEMA 2022).

A four-digit interger describes the built year of the bridge.

A two-digit string of the FIPS Code of the state that the bridge is located in.

An integer describes the number of spans, as defined in the HAZUS Inventory Technical Manual (FEMA 2022).

A floating point number describes the length of the longest span of the bridge, as defined in the HAZUS Inventory Technical Manual (FEMA 2022).

(Optional) Additional items which may be included for custom bridge definitions.

Example

“ID”: “330086”

“location”: 6

“bridge_class”: 316

“year_built”: 1953

“state_code”: “06”

“nspans”: 1

“lmaxspan”: 31.9

  • “hwy_tunnels”: A JSON array of JSON Objects, each containing the following key/item pairs

Table 2.4.1.3 InputDataSchemaTunnel.csv

Earthquake Required

Earthquake Required

Earthquake Required

*OptionalInputs

Key

ID

location

cons_type

Item

A string of the tunnel ID.

An integer of the ID of the node that describes the location of the tunnel.

A string describes the construction type as defined in HAZUS Earthquake Model Technical Manual (FEMA 2022). Values allowed are ‘Bored’, ‘Cut’, or ‘unclassified’.

(Optional) Additional items which may be included for custom tunnel definitions.

Example

“ID”: “330106L”

“location”: 8

“cons_type”: “unclassified”

  • “roadways”: A JSON array of JSON Objects, each containing the following key/item pairs

Table 2.4.1.4 InputDataSchemaRoadway.csv

Earthquake Required

Earthquake Required

Earthquake Required

Earthquake Required

*OptionalInputs

Key

ID

start_node

end_node

road_type

Item

A string of the road ID.

An integer of the ID of the node that describes the road start

An integer of the ID of the node that describes the road end

A string describes the road type. Values allowed are ‘primary’, ‘secondary’, ‘residential’, and ‘unclassified’.

(Optional) Additional items which may be included for custom roadway definitions.

Example

“ID”: “110167234853_0”

“start_node”: 480

“end_node”: 481

“road_type”: “residential”

  • “nodes”: A long JSON Objects containing the following key/item pairs

Table 2.4.1.5 InputDataSchemaTransportNode.csv

Key

Item

Example

A string ID. The string should be able to convert to integer.

A JSON object containing two key/item pairs which are the latitude and longitude of the node

“0”: {

“lat”: 37.7641499997259, “lon”: -122.2612529999318

}, “1”: {

“lat”: 37.769650000195966, “lon”: -122.28610800043785

}

2.4.1.4. Model File

If the simulation application chosen is OpenSees-Simulation or OpenSeesPy-Simulation, then a model file must be provided. It consists of an OpenSees/OpenSeesPy script with functions for building and analyzing a custom structural model. See the Simulation Applications page for more details on application-specific inputs.

2.4.1.5. EDP specifications file

JSON file specifying types, locations, and directions of EDPs to record in the structural model during response simulation.The EDP specifications file is only necessary as an input if UserDefinedEDP is chosen as the EDP application.

2.4.1.6. Event Files

To specify the type, location, and intensity of each event, the following files must be provided in the input_data/records folder.

properties

  • EventGrid

CSV file which specifies the coordinate (latitude/longitude) location of each event site.

properties

  • sta

Name of event file associated with the given event site. If running time history analysis, then the name of the site file is provided instead.

type

string

  • lon

Longitude coordinate of the site location.

type

float

  • lat

Latitude coordinate of the site location.

type

float

  • Event IM Files

CSV or JSON files containing information on the intensity measure of the event.

properties

  • name

Name of ground motion record.

type

string

  • dT

Time step of ground motion recording.

type

float

  • data_x

List of acceleration points in the x-direction ground motion record.

type

list

  • data_y

List of acceleration points in the y-direction ground motion record.

type

list

  • PGA_x

Value of peak ground acceleration in the x-direction ground motion record.

type

float

  • PGA_y

Value of peak ground acceleration in the y-direction ground motion record.

type

float

  • Site Files

CSV files listing the names of the event file(s) assigned to the site for time history analysis. This file can also provide other properties, such as a ground motion scale factor.

properties

  • GM_file

Name of the ground motion event file (for Earthquake hazard events).

type

string

  • factor

Factor for scaling the ground motion.

type

float