Use property values for specific class mapping - Intergraph Smart Interop Publisher - Help

Intergraph Smart Interop Publisher Help

Language
English
Product
Intergraph Smart Interop Publisher
Search by Category
Help
Smart Interop Publisher Version
17

The default class mapping for source files generally assigns a generic class for a range of similar objects. For more granular mapping, you can add one or more values to a new custom property to map a single Smart Interop Publisher source class to other classes. This provides the flexibility to map a generic source class to multiple, specific Smart Interop Publisher classes.

For example, in PDMS, if you use the generic STRUCTURE /SUBSTRUCTURE /FRAMEWORK /SUBFRAMEWORK to design equipment, vehicles, handrails and platforms, all these objects are mapped to the Smart Interop Publisher CR3DGenericStructure class. When you open the translated model containing these objects in Smart 3D, some of the objects may not be visible or easily identified. Using property values to map your source class to other, more specific Smart Interop Publisher classes ensures the object display and makes objects distinguishable.

The entry in the custom mapping sheet to create the mapping is shown below. The syntax is not case sensitive.

Source class name[property name=value]

where:

  • Source class name is the source object class name.

  • property name is the name of your new custom property or your designated existing property. This property must be in the source file.

  • value is the property value of the object type defined in your source file.

How To

  1. Copy the format-specific custom mapping template file to a different folder location.

  2. From the ClassMap tab in the custom mapping template file, enter the property syntax under Source Class with the values you added in the PropertyMap sheet.

    During translation, when Smart Interop Publisher encounters the source class object, STRU in the below example, the software checks whether the property exists on the object. In the example, the software checks for TYPE2. If the property exists, the software compares the value with the value you enter. If there is a match, Smart Interop Publisher maps the object to the designated, specific class and not the default or generic class. The PDMS example below shows that ladder, stair, and handrail objects from PDMS STRU class are mapped to the Smart Interop Publisher ladder, stair, and handrail classes instead of the default CR3DGenericStructure class.

  3. To add the custom secondary property and values, open the custom mapping template.

  4. In the PropertyMap sheet, add a new row and under Source Class, enter the syntax. The example below shows a PDMS custom mapping with TYPE2 as a new property with three different values: LADDER, STAIR, and HANDRAIL.

    The TYPE2 object type and these three values should be defined in the PDMS source file..

  5. In the Source Property column for the class, type the value to map. As an example, type Name. For the corresponding Target Property, type the value to display in the translated model. For example, type Name42 to map the source property value Name to Name42.

  6. Repeat steps 3-7 to add more custom properties with values to specify classes. Using the PDMS example, you can define a 'TYPE3' for the STRU PDMS class. Smart Interop Publisher selects each custom property syntax as it is listed in the ClassMap sheet. Both the property name and value you provide must match the source file properties.

  7. Save your edits and Set the custom option for translation.