5.12.  Classify
5.12.16.  Automatic Class Mapping: Edit...
Prev  Next

5.12.16.  Automatic Class Mapping: Edit...

With V12 there is a new function Automatic class mapping: Edit.... [Automatic Class Mapping: Edit...]

Dialog: Edit automatic class mapping [Edit Automatic Class Mapping]

Dialog: Edit automatic class mapping [Edit Automatic Class Mapping]

An important difference to the existing Mapping class systems [Map class systems] function is that virtual mapping takes place here, so that although the mapped classes and features are transferred to the target systems during export, the classification data is not physically written to the project files.

[Note]Note

  • Prerequisite: The directory $CADENAS_DATA/datasetup the directory class2class must exist.

  • An important restriction is that features cannot be mapped to existing classes (even if the specific feature is not set). If the mapping is used, for example, to map from eClass 11.1 to a completely empty eClass 12.0, this point is irrelevant. However, if you want to map from the Revit classification to the CNS classification, for example, the mapping will probably not be executed in many cases.

  • If a project contains mappings from the Proposed tab page Elements [Suggested items], classes and features appear with reddish background color , it contains mappings from the tab page mapped elements [Mapped elements], classes and Characteristics in bluish Background color displayed.

    Mapping from "Suggested elements [Suggested items] "

    Mapping from "Suggested elements [Suggested items] "

    Mapping from "Mapped elements [Mapped elements] "

    Mapping from "Mapped elements [Mapped elements] "

Example

In the following example, a class feature of the CNS classification is to be mapped to a class feature of the eClass 9 .1 classification. This means that the class data is entered starting in the upper table ( mapping between classes [Mapping between classes] ) and then the characteristic data is entered in the lower table (mapping between characteristics [Mapping between characteristics] ).

  1. In the upper table, click on Add system [Add System].

    -> The same-named dialog box is opened.

  2. Enter the name of the desired classification in the exact wording in lower case and confirm with OK.

    -> A new line is created in the upper table.

  3. Click on Add element [Add Item].

    -> A new line with input fields is created.

  4. Fill out the fields:

    [Note]Note

    When clicking into an input field, a list field is shown with all possible options. Otherwise: If wanted activate the respective checkbox.

    • Class of origin [Origin Class]:

    • Target system [Target System]: Enter the name of the desired classification in the exact wording, in lower case, and confirm with Enter.

    • Target class [Target Class]: Open the list field and select the desired class.

    • Number: One instance is created by default. You could also create several instances of the class.

    • Bidirectional: By default, mapping only takes place in the specified direction. If you activate the option, mapping is performed from the source class [Origin Class] to the target class [Target Class] and vice versa.

    • Copy instance [Copy Instance]: The entire content of the class is copied.

    • Copy restrictions [Copy Restrictions]:

    • Copy characteristics [Copy features]: All exactly the same features are copied. This option excludes entries in the lower table.

      Or

      Copy mapped characteristics [Copy mapped features] (default): Only the characteristics that are explicitly specified in the table below are mapped.

      Only one of the two points can be chosen!

  5. In the table below, click on Add system [Add System].

  6. Enter the name of the desired classification in the exact wording in lower case and confirm with OK.

  7. Click on Add element [Add Item].

    -> A new line with input fields is created.

  8. Fill out the single fields:

    • Origin class [Origin Class]: Open the list field and select the same class as in the table above. Alternatively, you can also use the wildcard symbol (*), although this has a negative impact on performance.

    • Origin Characteristic: Open the list field and select the desired attribute.

    • Origin ID: Is filled automatically.

    • Target system [Target System]: Enter the name of the desired classification in the exact wording, in lower case, and confirm with Enter.

    • Target class [Target Class]: Open the list field and select the desired class.

    • Target feature [Target Feature]: Open the list field and select the desired feature.

    • Target ID: Is filled automatically.

    • Copy characteristic name [Copy Characteristic Name] ("Copy variable name"): Select this option if a specific variable is to be mapped.

      Or

      Copy feature value [Copy Characteristic Value]: Select this option if a fixed value is to be mapped.

    • Value mapping [Value Mapping] (optional): Click on the button button if you want to adjust the original value.

      -> The same-named dialog box is opened.

      Values mapping [Value Mapping] "Dialog box"

      Values mapping [Value Mapping] "Dialog box"

      You can adjust the target value by making entries under Source value [Original Value] and Target value [Target Value]. After confirming with OK, the appearance of the button changes to .

    • Copy flags:

    • Copy unit: Default is activated.

    • Target unit [Objective Unit] (optional): If a unit is specified, the values are automatically converted.

  9. Execute the mapping by clicking on OK.

    [Note]Note

    A mapping is only executed if the target is empty.

    Changes to mappings require a restart of PARTproject ; for changes to projects, simply refresh (F5) the project selection [Project selection].

Test:

In this example, a mapping between

Klassfikation "CNS" > Klasse "CNSERPBASE" > Merkmal "CNSORDERNO"

and

Klassfikation "eclass 9.1" > Klasse "27-29-13-90" > Merkmal "AAO676002"

set up.

  1. Select a component with the corresponding origin class [Origin Class] and origin characteristic [Origin Characteristic].

  2. In the list field below the Classification tab, select the desired classification to which the mapping has been set up.Jpara

    -> The mapped classes and features are displayed with a blue background color.

User interface

Main features are the "table area" at the top (for Class Mapping) and the "table area" at the bottom (for Attribute Mapping).

Each table area has 2 tabs, one for mapped elements [Mapped elements] and one for suggested elements [Suggested items]. These are separate tables with separate data.

Each "table area" has it's own buttons. They work on the current active tab.

Buttons on the right above the tables

  • Add system [Add System]: Adds a source system (e.g. eclass8.0, eclass8.1, etc.). (Duplicates are not possible.)

  • Add element [Add Item]: Adds a new element with empty data and default values under a top node.

    Element is inserted at last position under current selected Top Node or current selected element.

  • Remove: Deletes the currently selected element or top node (alternatively also delete button)

    When deleting a Top Node all elements under the Top Node will be deleted, too. So there is a dialog for asking the user if he really wants to delete it.

Search bar

Each table area has its own search bar for searching all source and target data (system and classes (and variables and ID if variables are searched)).

Buttons below the table areas

  • import eClass XML [Import eClass XML]: Imports eClass data from a directory with suitable .xml files (legacy case)

  • import eClass CSV [Import eClass CSV]: Imports eClass data from a directory with suitable csv files (upgrade to next eClass version)

  • Import CSV [import CSV]: Imports eClass data from a directory with suitable csv files (e.g. eclass8.0_classes_mapped.csv).

  • Export CSV: Exports table data in the form of several csv files () to a directory (like import format above)

    The exported csv files are separated by classification system, class data / variable data and mapped / suggested (e.g. eclass5.1_classes_mapped.csv or eclass5.1_variables_suggested.csv).

  • OK: Saves the data under $CADENAS_DATA/datasetup -> Directory class2class -> File mapping.c2c and closes the dialog.

    Under $CADENAS_DATA/datasetup the directory class2class must exist.

  • Cancel: Discards the changes and closes the dialog (alternatively, the x button in the top right-hand corner works).

When importing data (via .csv files), duplicates are removed (may take some time).

When exporting data (via .csv files), duplicates are removed (only changed Elements will be checked).

When saving data (via the OK button), duplicates are removed (only changed elements are checked) and variable mapping data is checked for missing corresponding class mapping data. In the event that elements are found, there is a dialog where either missing class mapping data can be added or incorrect variable mapping data can be deleted.

Normally the table cells are editable strings or checkboxes.

Special cases:

  • Some cells give you a List of possible string values, when clicked (e.g. source class if source system is existing).

  • In the table Mapping between features [Mapping between characteristics], in the column Values mapping [Value Mapping] there is a button in the table cell (), which opens a special dialog. Here, source values (several if required) can be mapped to target values (warning if it is a duplicate). The value is therefore changed in the mapped variable or the fixed value is changed.

  • Target unit [Objective Unit]: If the field is activated, the unit is converted. If values exist, they are automatically converted to the new unit.

Special note

There are classes without attributes. In this case, entries in the lower table are obsolete. The reverse case is not possible. The upper table always has to contain entries.

Prev Up Next
5.12.15.4. Map class systems: Example  Home 5.12.17.  Collect classification data...