In this section we are going to discuss the steps for ingesting building data into a format that Ergo can understand and use in the building analyses. Before we launch the software, we will go over the Ergo building data format so that if any changes need to be made, we can make those now.
We will need two datasets for running a building damage analysis, a building dataset ingested into Ergo and a Fragility Mapping dataset ingested into Ergo. The building dataset will contain columns such as structure type, year built, etc and the fragility mapping dataset tells Ergo which fragility curves should be used for which buildings.
Let's start out by looking at the building data requirements. The building data for Ergo needs to be in ESRI's Shapefile format. Below you will find the column names, a short description and the column types that Ergo requires. Only the column types (e.g. integer, double, string, etc) must explicitly match what is listed in the table. We do not need to worry about column names matching because when we ingest the dataset, Ergo will ask you to map your columns to the columns that Ergo needs. For example, your structure type information might be in a column called s_type and Ergo expects it to be called str_type so you can tell Ergo that s_type maps to str_type and thus no changes need to be made to your dataset. The columns are categorized into three categories: Very Important, Less Important and Least Important.
General structure type of the building
Broad HAZUS Occupancy Category (e.g. RES3 - multi-family residential)
Appraised value for the building
total building area in square feet
total number of dwelling units in the building
total number of stories for the building
value of building contents
detailed structure type as per HAZUS MR-3 specifications
essential facility designation
building identifier (unique)
probability that the structure type specified is correct
the year the structure was built
the number of above ground stories
the number of below ground stories
the basement type
total ground floor area of the building in square feet
specific occupancy category, describing the detailed use of the building
major occupancy category for the parcel in which the building is sited
general occupancy categories
replacement cost for the building from R.S. means square foot cost
structural component of the replacement cost
acceleration sensitive component of replacement cost
drift sensitive component of replacement cost
design level for the building as per HAZUS MR-3 specifications
detailed HAZUS occupancy category for the building
census tract identifier
Now, it's ok if you don't have all of the above information for your buildings; however, the more detail you have about your building means you can be more explicit in mapping your fragilities to your buildings for the damage analysis. Only in the more advanced analyses will Ergo start requiring some of those other attributes (e.g. estimating structural damage cost requires the APPR_BLDG column since the cost of the structure needs to be known). One stipulation, all of these columns do need to be present in the dataset, even if they contain no data because Ergo will expect all of the columns to be there upon ingestion. In the next version of Ergo, this restriction of all columns being present, even with no data, should be eliminated.
First, we will need to launch the Ergo application. The default installation directory for Ergo is a folder with the same name, "Ergo" so you should be able to launch the software by going to Start -> Programs -> Ergo.
In this section we will go through the steps to create a new local data repository for ingesting data into and then through the steps to ingest a building dataset and a fragility mapping dataset.
This step is optional if you have already created a local repository to ingest your data into, otherwise the steps below will take you through the process of creating a local repository for Ergo. With Ergo open, you should see a Catalog View similar to the one in the image below:
Steps to create repository:
If your dataset is large, you may need to wait a few minutes for Ergo to ingest the dataset. A progress bar will indicate if Ergo is still working on the dataset. Once that finishes, your dataset should now be available in the repository you ingested to.
At this point, you should have all of the data required to be able to use the building damage tutorial to create a building damage result from your ingested buildings provided they default fragilities and fragility mapping files work with your dataset. If not, you will need to create a set of fragilities and fragility mappings for your dataset. You can find more information about that here.