2.4. ASD: Asset Definition

In this panel the user can import the databases of different asset classes. The user can select the type of asset from the Asset Selection Ribbon, e.g., Buildings and Gas Network, as shown on the left-hand side of Fig. 2.4.1.1.2. The Asset Selection Ribbon appears when more than one type of asset is selected in the GI: General Information panel. Moreover, only the assets that are checked in the GI: General Information panel will appear in the Asset Selection Ribbon. As the user switches between assets, the main panel changes to reflect the applications available for the import of each type of asset.

2.4.1. Buildings

The buildings input panel, as shown in Fig. 2.4.1.1.2, allows a user to input a building inventory database. The Building Import Selection combo box is where the user selects the application for the import of buildings, and for the generation of a asset information model (AIM).

2.4.1.1. CSV to AIM

The CSV to AIM application imports a building inventory database from a user provided .csv file.

1. The Path to Buildings Database box is where the user supplies the file path to the .csv file that contains the building inventory. At a minimum, the .csv file must contain columns providing the building identification numbers (ID), in sequential order, and the latitudes and the longitudes of the locations of the buildings. Any number of columns can be added to the file to provide information required by other applications in the workflow.

2. The Building Selection Filtering box is where the user can select a subset of buildings for analysis. There are two ways to select and filter buildings:

   1. Input a string of numbers that correspond to the building IDs that you want to analyze. A range of buildings is specified with a dash, and multiple buildings are separated with a comma, e.g., 2-8, 9, 13, 15, 21, 34-38.

   2. Employ the Advanced Filtering capabilities by clicking on the Advanced Filter button. The Query Builder dialog will appear, as seen in Fig. 2.4.1.1.1. You can create a custom filter expression (SQL format) using operators, e.g., <, =, OR, and fields available in the imported building inventory, e.g., BuildingType. Operators and fields can be combined to perform complex filtering expressions such as "YearBuilt" < 1970  AND  "BuildingType"  =  'Wood'

Fig. 2.4.1.1.1 Query Builder Dialog.

When the Select button is pressed, the buildings that are specified in the Building Selection box are added to the list of buildings that will be analyzed. Pressing the Clear Selection button will clear the list of buildings that will be analyzed.

The Building Information table, shown in Fig. 2.4.1.1.2, provides a user-editable spreadsheet containing the information provided by the building inventory database file.

Fig. 2.4.1.1.2 CSV to AIM input panel.

2.4.1.2. GIS to AIM

The GIS to AIM application imports a building inventory database from a user-provided GIS file (e.g., shapefile, geodatabase). The input panel is shown in Fig. 2.4.1.2.1.

1. The GIS Input File box is where the user supplies the file path to the GIS file that contains the building inventory. Clicking on the Browse button will open a dialog where you can select the appropriate file.

2. The Building Selection Filtering box is where the user can select a subset of buildings for analysis. There are two ways to select and filter buildings:

   1. Input a string of numbers that correspond to the building IDs that you want to analyze. A range of buildings is specified with a dash, and multiple buildings are separated with a comma, e.g., 2-8, 9, 13, 15, 21, 34-38.

   2. Employ the Advanced Filtering capabilities by clicking on the Advanced Filter button. The Query Builder dialog will appear, as seen in Fig. 2.4.1.1.1. You can create a custom filter expression (SQL format) using operators, e.g., <, =, OR, and fields available in the imported building inventory, e.g., BuildingType. Operators and fields can be combined to perform complex filtering expressions such as "YearBuilt" < 1970  AND  "BuildingType"  =  'Wood'. When the Select button is pressed, the buildings that are specified in the Building Selection box are added to the list of buildings that will be analyzed. Pressing the Clear Selection button will clear the list of buildings that will be analyzed.

3. The Building Information table provides a user-editable spreadsheet containing the information provided by the building inventory database file. When a subset of buildings is selected for analysis, only the selected buildings will appear in the Building Information table.

Fig. 2.4.1.2.1 GIS to AIM input panel.

2.4.1.3. GeoJSON to Asset

The GeoJSON to Asset application, shown in Fig. 2.4.1.3.1, is SimCenter’s preferred method to load regional infrastructure inventory. Listing 2.4.1.3.1 is an example of a .geojson formatted database for buildings. It follows the format convention of the official .geojson structure as described here. A “CRS” key-item pair is necessary to define the coordinate reference system, and the building stock information is described in the “features” array. Each feature in the features array stands for one asset. Each feature must include a {“type”:”Feature”} key-item pair, a “geometry” item, and a “properties” item. It can also contain an optional “id” item, and the value of this item is either a JSON string or number. The building information needed in later workflow should be included in the “properties” item. All information needed in the subsequent workflow (e.g., IMasEDP asset analysis and HAZUS-MH EQ damage and loss analysis) must be provided, otherwise, R2D may return errors. The information required for typical analysis workflows can be found in File Types and Schemas and in R2D examples. A special SimCenter convention is an attribute “type” must be included in the “properties” items. The value of “type” describes the component type of this feature. For building inventory, the component type is always “Building”, i.e., {“type”:”Building”}. For other infrastructure, such as transportation infrastructure, the value of “type” could be Bridge, Roadway, and Tunnel. Depending on the component type, the asset will be managed differently in later simulation workflow. More descriptions can be found at Regional Transportation Infrastructure and example 14 in R2D examples.

Fig. 2.4.1.3.2 is the panel after a .geojson buidling inventory database is loaded in R2D. Users should select the buildings they want to analyze in the Building Selection Filtering box. The selected buildings can be visualized in the VIZ panel.

Fig. 2.4.1.3.1 GeoJSON to Asset input panel.

Listing 2.4.1.3.1 GeoJSON formatted database for buildings.

{
  "type": "FeatureCollection",
  "crs": {
    "type": "name",
    "properties": {
      "name": "urn:ogc:def:crs:OGC:1.3:CRS84"
    }
  },
  "features": [
    {
      "id": 0,
      "type": "Feature",
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[-122.293878,37.771004],[-122.293973,37.771029],...]]
      },
      "properties": {
        "AIM_id": "1",
        "Latitude": 37.7709536,
        "Longitude": -122.2939517,
        "NumberOfStories": 1,
        "YearBuilt": 1953,
        "OccupancyClass": "IND2",
        "StructureType": "W1",
        "PlanArea": 18615.30048,
        "ReplacementCost": 38781.876,
        "Population": 1,
        "type": "Building"
      }
    },...]
}

Fig. 2.4.1.3.2 GeoJSON to Asset input panel after loading a building .geojson database.

2.4.2. Regional Water Distribution Networks

The water distribution network input panel, as shown in Fig. 2.4.2.1.1, allows a user to input the nodes and pipelines of a water distribution network. The Regional Water Network Selection combo box is where the user selects the application for the import of water distribution networks, and for the generation of a asset information model (AIM).

2.4.2.1. CSV to Regional Water Network

The CSV to Water Network application imports a water distribution network from a set of user provided .csv files that represent the nodes and pipelines of the network.

1. The Path to Nodes box is where the user supplies the file path to the .csv file that contains the nodes of the water distribution network. At a minimum, the .csv file must contain columns providing the node identification numbers (ID), in sequential order, and the latitudes and the longitudes of the locations of each node. Any number of columns can be added to the file to provide information that may be required by other applications in the workflow.

2. Similar to the nodes, the Path to Pipelines box is where the user supplies the file path to the .csv file that contains the pipelines of the water distribution network. At a minimum, the .csv file must contain columns providing the pipe identification numbers (ID), in sequential order, and two subsequent columns containing the node ids of the nodes where the pipe starts and where the pipe ends. Any number of columns can be added to the file to provide additional pipeline information that may be required by other applications in the workflow.

The Node and Pipeline Information table, shown in Fig. 2.4.2.1.1, provides a user-editable spreadsheet containing the information provided by the csv files, respectively.

1. The Selection Filtering box for nodes and pipes is where the user can select a subset of assets for analysis.

There are two ways to select and filter assets:

1. Input a string of numbers that correspond to the asset IDs that you want to analyze. A range of assets is specified with a dash, and multiple assetes are separated with a comma, e.g., 2-8, 9, 13, 15, 21, 34-38.

2. Employ the Advanced Filtering capabilities by clicking on the Advanced Filter button. The Query Builder dialog will appear, as seen in Fig. 2.4.1.1.1. You can create a custom filter expression (SQL format) using operators, e.g., <, =, OR, and the fields available in the imported asset inventory, e.g., BuildingType. Operators and fields can be combined to perform complex filtering expressions such as "YearBuilt" < 1970  AND  "BuildingType"  =  'Wood'. When the Select button is pressed, the assets that are specified in the Asset Selection box are added to the list of assets that will be analyzed. Pressing the Clear Selection button will clear the list of assets that will be analyzed.

Fig. 2.4.2.1.1 CSV to regional water network input panel.

2.4.2.2. GIS to Regional Water Network

The GIS to Regional Water Network application imports a water distribution network from a set of user provided GIS files that represent the nodes and pipelines of the network. The input panel is shown in Fig. 2.4.2.2.1. The GIS files can be in one of many common GIS file formats, e.g., shp, gdb, etc.

1. The Path to Nodes box is where the user supplies the file path to the GIS file that contains the nodes of the water distribution network. At a minimum, the GIS file must contain a field providing the node identification numbers (id), in sequential order. Any number of attributes can be added to the node features to provide information that may be required by other applications in the workflow. R2D will load all feature attributes as columns in the Node Information table.

2. Similar to the nodes, the Path to Pipelines box is where the user supplies the file path to the GIS file that contains the pipelines of the water distribution network. Any number of attributes can be added to the pipeline features to provide information that may be required by other applications in the workflow. R2D will load all feature attributes as columns in the Pipeline Information table.

The Node and Pipeline Information table, shown in Fig. 2.4.2.1.1, provides a spreadsheet containing the information provided by the GIS files, respectively.

1. The Coordinate Reference System (CRS) dropdowns is where the coordinate reference system for a particular GIS file is specified. Each GIS file should have an accompanying CRS that will need to be specified so that R2D can place the features in the correct projected coordinate system.

Fig. 2.4.2.2.1 GIS to regional water network input panel.

2.4.3. Regional Transportation Infrastructure

The transportation infrastructure input panel allows users to input the inventory of a transportation network. The Transportation Network Selection combo box is where users select the application for importing transportation network inventory generating asset information models (AIM).

2.4.3.1. GeoJSON to Asset

The GeoJSON to Asset application, shown in Fig. 2.4.1.3.1, is SimCenter’s preferred method to load regional infrastructure inventory. Listing 2.4.1.3.1 is an example of a .geojson formatted database for transportation infrastructure. It follows the format convention of the official .geojson structure as described here. A “CRS” key-item pair is necessary to define the coordinate reference system, and the infrastructure information is described in the “features” array. Each feature in the features array stands for one asset. Each feature must include a {“type”:”Feature”} key-item pair, a “geometry” item, and a “properties” item. It can also contain an optional “id” item, and the value of this item is either a JSON string or number. The information needed in later workflow should be included in the “properties” item. All information needed in the subsequent workflow (e.g., IMasEDP asset analysis and HAZUS-MH EQ damage and loss analysis) must be provided. Otherwise, R2D may return errors. The information required for typical analysis workflows can be found in File Types and Schemas and in R2D examples. A special SimCenter convention is an attribute “type” must be included in the “properties” items. The value of “type” describes the component type of this feature. For transportation infrastructure, the value of “type” could be Bridge, Roadway, Tunnel, or other values. Assets with the same “type” (e.g., all bridges) will be visualized in the same visualization layer. Assets with the same “type” will also be placed in the same working directory in the Results folder is in the Output Directory folder that is specified in R2D preferences. For each bridge (or other component type), there can be other identification keys (such as, “assetSubtype”: “HwyBridge” in Listing 2.4.3.1.1). The key “assetSubtype” is used by the R2D built-in Damage and Loss (DL) application Pelicun3 when the HAZUS-MH damage and loss methods are selected. “HwyBridge” stands for highway bridge as classified in the Hazus Inventory Technical Manual and the Hazus Earthquake Model Technical Manual. If a user selected to use User-provided Fragilities in Pelicun3, the key “assetSubtype” is not needed. More descriptions can be found in example 14 in R2D examples.

Fig. 2.4.3.1.1 is the panel after a .geojson transportation infrastructure inventory database is loaded in R2D. Users should switch the viewing panel with the component selection panel and select the assets they want to analyze in the Asset Selection Filtering box. The selected assets can be visualized in the VIZ panel.

Note

The outputs of the BRIALS Transportation tool use the default units of the inventory databse described in Section 3.7. Users need to convert the units to those defined in the General Information panel before loading the units to this Asset panel.

Listing 2.4.3.1.1 GeoJSON formatted database for buildings.

{
  "type": "FeatureCollection",
  "crs": {
    "type": "name",
    "properties": {
      "name": "urn:ogc:def:crs:OGC:1.3:CRS84"
    }
  },
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [-122.2612529999318,37.7641499997259]
      },
      "properties": {
        "AIM_id": "0",
        "StructureNumber": "33C0229",
        "BridgeClass": 201,
        "YearBuilt": 1958,
        "NumOfSpans": 3,
        "MaxSpanLength": 358.26771653543307,
        "StateCode": "06",
        "Skew": 0,
        "DeckWidth": 905.511811023622,
        "Location": 0,
        "type": "Bridge",
        "assetSubtype": "HwyBridge"
      }
    },{
      "type": "Feature",
      "geometry": {
        "type": "LineString",
        "coordinates": [[-122.29349499973279,37.7719390001118],
          [-122.29350599960344,37.77174100030729],...]
      },
      "properties": {
        "AIM_id": "2868",
        "TigerOID": "1102159726459",
        "RoadType": "unclassified",
        "NumOfLanes": 1,
        "MaxMPH": 25,
        "StartNode": 695,
        "EndNode": 1859,
        "ExplodeID": 0,
        "SegID": 0,
        "type": "Roadway",
        "assetSubtype": "Roadway"
      }
    },
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [-122.27657404019031,37.78744034988232]
      },
      "properties": {
        "AIM_id": "0",
        "TunnelNumber": "33 0106R",
        "ConstructType": "unclassified",
        "Location": 7,
        "type": "Tunnel",
        "assetSubtype": "HwyTunnel"
      }
    },
    ...
  ]
}

Fig. 2.4.3.1.1 GeoJSON to Asset input panel after loading a transportation infrastructure .geojson database.

2.4.3.2. GIS to Transportation Network AIM

The GIS to Transportation Network AIM application imports a transportation network from user-provided GIS files that contain information on highway bridges, tunnels, and/or roadways. The input panel is shown in Fig. 2.4.3.2.1. The GIS files can be in one of many common GIS file formats, e.g., shp, gdb, etc.

The Path to Roadways/Bridges/Tunnels box is where the user supplies the file path to the GIS file that contains the roadways/bridges/tunnels features in the transportation network. At a minimum, the GIS file must contain a field providing the identification numbers (id), in sequential order. Any number of attributes can be added to the features to provide information that may be required by other applications in the workflow. R2D will load all feature attributes as columns in a table in a similar way to Fig. 2.4.2.2.1. Only the Roadways/Bridges/Tunnels selected in the corresponding selection box will be analyzed in the later part of the workflow.

Example GIS files for roadways, bridges, and tunnels that can be loaded to R2D with GIS to Transportation Network AIM can be found in the github data repository of example 14 of R2D examples

Fig. 2.4.3.2.1 GIS to regional transportation network input panel.