Import (Convert) Feature Definitions from a Custom CSV (.csv) File

Use the Convert CSV to FXL command to import into your project's Feature Library feature definitions and control codes specified in records contained in a custom CSV (.csv) data file.

For each feature definition record contained in the CSV file, you can import the definition name (required), code (required), and any additional supported feature properties and/or attributes (optional).

Note: If the import file includes duplicate definition names or codes, they are appended with a number on import (for example, Bush, Bush_1, Bush_2, and so on).

For each control code record contained in the CSV file, you can import the control code name (required) and code (required). You then select from a list of predefined actions to associate with each control code on import.

If a feature definition or control code record includes any fields that do not map to corresponding predefined Feature Library properties for the selected feature type or control code, you can select to skip it during the import.

After import, you can edit the imported feature definitions and/or control codes as necessary (for example, specify feature symbols or edit attributes). See View a Project's Feature Library for more information.

Prerequisites:

  • Your project must include a Feature Library into which feature definitions and/or control codes can be imported.
  • You must have a CSV (.csv) file containing feature definition and/or control code data in a delimited record format.

To import feature definitions and control codes from a CSV file into a Feature Library:

  1. Select Convert CSV to FXL in Survey > Field Data.
  2. In the Convert CSV to FXL dialog, click the Source file browse button and select the CSV (.csv) file containing the feature definitions and/or control codes you want to import.

    All of the records contained in the CSV file display in a spreadsheet view on the Original File tab in the same order and record format used in the CSV file.

    The procedure for importing the various feature and control code types is basically the same, as shown in the following steps.

  3. On the Original File tab, select all of the records of the same type (point, line, polygon, or block feature definition; or line or block control code) that you want to import.

    You will repeat the next several steps as necessary for each additional record type you want to add. But for this procedure you will add one record type at a time.

    Note the following:

    • If necessary, use the Find field located above the tabs to search for a character string contained in the records.
    • You can click and drag or use Shift+click and/or Ctrl+click to make a multi-cell selection.
    • For each record, you can import just the fields (column cells) you select, or you can simply select all of the fields in the record and then select to skip the non-importable fields later in this procedure. This is a good option if you are selecting multiple records to import at the same time. Only the feature definition or control code name and code are required for the import.
  4. After you have made your cell selections on the Original Files tab, click the appropriate Add button located beneath the tab.

    On the Original File tab, the selected cells are highlighted with a light color to indicate they have been selected for import and are now displayed on the appropriate record type tab.

  5. Select the appropriate tab to view the newly selected feature definitions or control codes.

    Note that on any of the tabs other than the Original File tab, you can double-click any cell to edit its contents or enter new content. To enter a new record on the tab (instead of using imported data), double-click in any cell in the gray row at the bottom of the spreadsheet and enter content.

  6. For feature definitions, do the following:

    (See step 7 for control codes.)

    1. On the selected feature definition type tab, right-click the header for each populated column and select the appropriate data type contained in the column. At a minimum, the Name and Code fields are required to import a record.
    2. If a column contains data other than one of the types of data included in the data type drop-down list, select Skip so that the data is ignored during the import.

      Note the following:

      • If an imported feature definition includes a Category name that does not exist in the project's Feature Library, the category is imported into it.
      • If an imported feature definition includes a Feature layer and/or Point layer name that does not exist in the project's Feature Library, or it does not include a name at all, the default 0 option is imported. If necessary, you can change the layer properties after import.
      • If an imported feature definition includes a Line style, Field line style, Border line style, and/or Field border line style name that does not exist in the project's Feature Library, or it does not include a name at all, the default Solid option is imported. If necessary, you can change the line style properties after import.

        To import a feature definition with the line style By Block / Feature, the import line style option name must be By Block. If the import name is By Block / Feature, it will be ignored and the default Solid option will be imported.

      • If an imported feature definition includes a Label style, Line label style, Point label style, and/or Polygon label style name that does not exist in the Feature Library, or it does not include a name at all, the default <<None>> style option is imported. If necessary, you can change the label style properties after import.
      • If an imported feature definition includes a Color, Fill color, and/or Border color textual name that does not exist in the Feature Library, or it does not include a name at all, the default By Layer color option is used. If necessary, you can change the color properties after import.

        If the imported Color field includes a valid RGB channel, hexadecimal, or decimal color code, the corresponding color is imported.

      • Valid imported values for the Include in Surface field are Yes/No, True/False, and 0/1.
      • If an import feature definition includes an invalid Attribute type name, or it does not include a name at all, an error indicator displays on the cell. Prior to import, you must click the button next to the error indicator and select a valid attribute type from the New type list in the Change Attribute Type dialog. Optionally, check the Change all check box to change the name of any Attribute type cells on the tab that have the same Current type name to the New type name.
      • Before you can import a block feature definition, the block (DWG or DXF file) on which it is based must have already been imported into the project.
  7. For control codes, do the following:
    1. On the selected control code tab, right-click the header for the column containing control code names and select Name.
    2. Right-click the header for the column containing control codes and select Code.
    3. In the Action column, select the appropriate predefined action for each control code. This action is added to the control code on import.

      You cannot import values into this column.

    If additional columns contain data, Skip is automatically selected in the column header and cannot be changed. Control codes require only a name, code, and action, so any other data will be skipped during the import.

  8. Repeat steps 3 through 7 as necessary to add additional feature definitions and/or control codes to the import.
  9. After you have made all of your record and field selections, select each tab to which you moved (and edited if necessary) feature definitions and/or control codes and click the Add to Feature Library button to import the records included on that tab into the current Feature Library.

    Each time you click the Add to Feature Library button, a message displays stating how many records were imported into the Feature Library from the selected tab. In addition, the imported records are highlighted on the tab.

    Note: If applicable, you can make edits to any records that did not import and attempt to import them a second time.

  10. When you are done performing imports, click the Close button.

    The Convert CSV to FXL dialog closes and the newly imported feature definitions and/or control codes are displayed in the Project Explorer nested beneath the Feature Libraries node.

  11. If necessary, modify the newly imported definitions and/or control codes.

    See View a Project's Feature Library for more information.

Related topics

Work with the Feature Library and Feature Definition Files

Create a Feature Library

Export Feature Definitions to a Custom CSV File

View a Project's Feature Library