Overview

In this section we are going to discuss the steps for ingesting building data into a format that MAEviz can understand and use in the building analyses. Before we launch the software, we will go over the MAEviz building data format so that if any changes need to be made, we can make those now.

Data Format

We will need two datasets for running a building damage analysis, a building dataset ingested into MAEviz and a Fragility Mapping dataset ingested into MAEviz. The building dataset will contain columns such as structure type, year built, etc and the fragility mapping dataset tells MAEviz which fragility curves should be used for which buildings.

Building Data

Let's start out by looking at the building data requirements. The building data for MAEviz needs to be in ESRI's Shapefile format. Below you will find the column names, a short description and the column types that MAEviz 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, MAEviz will ask you to map your columns to the columns that MAEviz needs. For example, your structure type information might be in a column called s_type and MAEviz expects it to be called str_type so you can tell MAEviz 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.

...

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 MAEviz 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 MAEviz will expect all of the columns to be there upon ingestiongingestion. In the next version of MAEviz, this restriction of all columns being present, even with no data, should be eliminated.

Fragility Mapping

This section will require a very basic understanding of XML and is something that we can help the user with putting together if you contact us by email. The basic concept behind the fragility mapping is to tell MAEviz which fragilities should be used with which "objects". In the case of a building dataset, which fragilities should be mapped to which buildings. The mapping file allows you to use a specific set of rules to map fragilities to buildings (e.g. if a building has a structure type S1 and has 6 stories, use fragility curve with ID SF_S1_1).

Using the example below, we'll go through the various parts of the fragility mapping.

...

<match-filter-map>
  <property-match>
    <success-value>

      <map>
        <entry key="Non-Retrofit Fragility ID Code" value="SF_S1_1"/>
      </map>
    </success-value>
    <filter>
      <statement>
        <rule>int no_stories GE 4</rule>
        <rule>int no_stories LE 7</rule>
        <rule>String struct_typ EQUALS S1</rule>
      </statement>
    </filter>
  </property-match>
</match-filter-map>

Ingest Building Dataset

First, we will need to launch the MAEviz application. The default installation directory for MAEviz is a folder with the same name, "MAEviz" so you should be able to launch the software by going to Start -> Programs -> MAEviz.

Ingestion Steps

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.

Create Local Repository

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 MAEviz. With MAEviz open, you should see a Catalog View similar to the one in the image below:

Image Added

Steps to create repository:

1. Click on the New Repository button that is highlighted by the mouse in the above image and a dialog box similar to the one in the image below should open and walk you through the steps of creating a new repository.
   Image Added
2. Select Local Repository from the drop down menu and click the Next button. You should now see a dialog similar to the one below.
   Image Added
3. Enter a name for the repository and browse for a directory to use to store ingested datasets. Click Finish to create the new repository. You should now see your new repository in the Catalog View and it is ready to store data

In the section that says <map> </map> is where the fragility identifier is specified. Where it says key is for MAEviz internal use and that must match exactly because the "Non-Retrofit Fragility ID Code" tells MAEviz this is the as-built fragility. The second part where it says value is a fragility ID in your fragility dataset (e.g. SF_S1_1), this must match match a fragility in your fragility dataset.

In the next section of the example above you will see some <rule> </rule> tags between <statement> </statement> tags. These are the rules to determine if SF_S1_1 fragility should be used for a particular building. If you look at the first rule where it says:

<rule>int no_stories GE 4</rule>

The first part that says int tells MAEviz what type of data to look for. The second part where it says no_stories tells MAEviz which column to look at, so in this case, there should be a column in the building dataset called no_stories. For reference, if you look in the previous section it was specified that the column no_stories should be of type integer. Now, the third part tells MAEviz what type of comparison to perform. In this case, we are looking for something that is greater than or equal to (GE) 4. For a building to pass this first rule, it must have a no_stories column with a value greater than or equal to 4. If it matches, MAEviz will check the next rule. Looking at the next rule, it states that there must be a column called no_stories that is of type integer, with a value Less Than or Equal to 7 (LE). In order to use this set of fragilities a building must match all of the rules between <statement> </statement> tags. If any fail, MAEviz will move onto the next <property-match> </property-match> tags set that contain the next fragility curve and its rules.

You can make these rules as complex or as simple as you want. You could simply have a single rule:

<rule>String STRUCT_TYP EQUALS S1</rule>

In this case, we are looking at a column called STRUCT_TYP (structure type) with a value of S1. If it matches, then use the fragility we specified.

If you need to create a fragility mapping file that maps your fragilities to your building dataset, you just need to come up with a list of rules that maps a fragilities to buildings and save them to an XML file. After creating the file, you need to ingest it into MAEviz. Ingesting data into MAEviz will be detailed in the next sections.

Launch MAEviz

The default installation directory for MAEviz is a folder with the same name, "MAEviz" so you should be able to launch the software by going to Start -> Programs -> MAEviz.

Ingestion Steps

Create Local Repository

...

1. .

Building Dataset

1. Go to the File menu near the top of the application and select Import. This should bring up the dialog seen below.
   Image Modified
2. From the dialog box, expand the Data selection and select Dataset and click Next. You should see something similar to the image below.
   Image Added
3. From the dialog drop down menu, select Shapefile and click Next. You should see a dialog similar to the one in the image below.
   Image Added
4. From the dialog, click the Browse button and select the building shapefile you want to ingest and click the Next button. You should see a dialog similar to the one below.
   Image Added
5. From the dialog drop down menu, select Building Inventory v5.0 and click Next. You should see a dialog similar to the one below.
   Image Added
6. From this dialog, you will notice each field has a drop down menu next to it. The field name on the far left is the field MAEviz found expects to find in your dataset and the drop down menu next to the field contains all of the fields in your dataset that you could map it tooto. Select the appropriate mappings (e.g. as we mentioned above, you could map s_type to struct_typ). For some fields, there will also be a unit type drop down selection (e.g. dollars for building value). Currently, if other currency types besides dollar and turkish lira are required we will need to add the conversion to MAEviz. When finished, click Next.
7. If other fields are present, the next dialog screen will give you some options to assign friendly names and units to those fields. You can safely ignore this and click the Next button. You should now see the dialog below.
   Image Added
8. From this dialog you can select the repository to ingest the dataset to, provide a descriptive name for the dataset (e.g. Memphis Residential Buildings), and a version number. After entering the required information, click the Finish button.

If your dataset is large, you may need to wait a few minutes for MAEviz to ingest the dataset. A progress bar will indicate if MAEviz is still working on the dataset. Once that finishes, your dataset should now be available in the repository you ingested to.

Fragility Mapping Dataset

...

to

...

.

...

Conclusion

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 for your ingested building datafrom 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.