Database import allows the user to import gdb, kml/kmz, shapefiles, and other excel templates to bring data from PODS/UPDM into the hub platform. When the file is successfully imported, the application provides a data mapping screen for the user to accept, deny and/or edit the data mapping fields.

When a user does not have permissions for Maps, the user can use the DB Import to bring in data into the hub platform. If the user was previously using PLTB desktop versions, all cases for the user can be ported from desktop to hub (cloud or desktop) using this feature.

1. Log in to the application using the credentials provided by Technical Toolboxes.
2. Click on “DB Import” from the application menu bar, which loads the Ad-hoc widget on the canvas.
   
3. This functionality is used when users have to import/export data to the application DB in the absence of Map. Following are the types of data that are supported for an import:
   1. SQL Server Data Source
   2. Gdb/shapefile/klm/kmz
      1. Click on “Upload File(KLM/Shape File/GDB)”
      2. This will open a browser to select the file to import.
      3. Select the file and click on “Open”
      4. Once the file is selected, the data mapping UI opens so that the entities and parameters in the file imported can be mapped to the application. The system logically maps attributes that can be confirmed or the user may choose to edit the data mapping. After the user maps the entities, the user will have to map the attributes associated within each entity by clicking on “Map Attributes” in the last column. The first column being the “Destination Table” or the DB table; the second, “Source Table” which is from the file imported.
      5. The mapping UI contains 3 columns:
         1. Destination Table – UPDM tables existing in the application database.
         2. Source Table – The tables that are being imported into the application database.
         3. Column Mapping – Mapping of the imported tables to selected layer attributes.
      6. When this is done click on Save, and you will see the pipes imported in the hierarchy table
         Non-Spatial Data or an excel.
   3. Click on “Upload File (xlsx/xls Files)”
      1. A template will be provided if the user wants to import from a generic excel file. When the user click =s on the download template
      2. This will open a browser to select the appropriate file to import.
      3. Select the file and click on “Open”
      4. Mapping UI opens so that the parameters in the file can be mapped to the parameters in the application. The system logically maps attributes that can either be changed or committed by the use.
      5. The mapping UI contains 2 columns:
         1. Destination Column – dropdown option for the user to map UPDM tables existing in the application database to the source table (excel file being imported).
         2. Source Column – The tables that are being imported into the application database. All parameters from the excel are dynamically displayed here which have to be mapped to the UPDM application database.
      6. When this is done click on Save, and you will see the pipes imported in the hierarchy table.
   4. PLTB Desktop Database
      1. Click on Upload File (MDB)
      2. From the explorer window, browse the mdb file on your machine. Usually, the path to PLTB mdb file is in the following
         C:\Users\(USER NAME)\AppData\Local\VirtualStore\Program Files (x86)\Technical Toolboxes\(APPLICATION).
      3. Select the file and click on open. This will migrate all PLTB desktop cases to the Hub.
   5. Export Database
      1. This feature is available for the user which enables the user to download the database in a flat excel file format.
         
      2. When user clicks on the export button, an excel file is generated with the data from the database.

Limitations

The current version of the KML/KMZ file import feature on the Hub does not support KML/KMZ files with multiple layers. Users must ensure that the KML/KMZ file used contains only a single layer. A future release will include the capability to support the import of KML/KMZ layer groups.

Related Links

Pipeline HUB – User Resources