Selecting attribute mapping for precast elements

The CSV file required to select attribute mapping in Allplan (referred to below as the definition file), namely PrecastAttributeMap.csv , has a fixed, defined structure as defined below.

#attribute mapping for precast elements
#AttributeNumber	Data type	ObjectType	ObjectField	ContentMap

#valid for all precast elements
@PrecastGeneral

#specific for precast slabs
@PrecastSlab

#specific for precast walls
@PrecastWall

#specific for precast structural elements
@PrecastStructuralElement

The syntax of the definition file is generally structured as shown below:

Comments; lines starting with the # character (for example, #AttributeNumber in the above illustration)
Beginning of an attribute group = lines starting with the @ character (for example, PrecastGeneral in the above illustration)
Other lines; lines for attribute mapping

The lines in the definition file contain the following entries:

The Headers contain explanations used as comments; e.g. #valid for all precast elements or #AttributeNumber
The @PrecastGeneral block contains the Attribute mapping lines for the Attribute groups of all precast elements
The @PrecastSlab block contains the Attribute mapping lines for the Attribute groups of all precast slabs
The @PrecastWall block contains the Attribute mapping lines for the Attribute groups of all precast walls and precast elements
The @PrecastStructuralElement block contains the Attribute mapping lines for the Attribute groups of structural precast elements

The columns in the definition file contain the following entries:

AttributeNumber: Number of object attribute
Data type:
- Default attribute: empty
- User-defined attribute: 0 = value, 1 = text
ObjectType: Object type to which the attribute is to be transferred
- Default attribute: empty
- User-defined attribute:
  - PrecastElement; Attribute refers to the entire precast element
  - PrecastLayer#n; Attribute refers to a particular layer of the precast element (#n)
ObjectField; Dialog box of the precast element to which the attribute is to be transferred
ContentMap; here you can enter as an option the name of a definition file for mapping attribute value (i.e. the contents of the attributes). You can, where necessary, also replace attribute values taken from the component with other values so that the program transfers these new values to the corresponding dialog box.
To configure this, you must specify a CSV file for mapping attribute values in the ContentMap column of the PrecastAttributeMap.csv definition file. You can name CSV files for mapping attribute values as you like. However, make sure that the files are in the ...\std folder of Allplan.

The following contains an example of a definition file for mapping attribute values for the concrete grade:

C25 / 30	C25/30
C25-30	C25/30
C25 - 30	C25/30
C25 \ 30	C25/30
C30 / 37	C30/37
C30-37	C30/37
C30 - 37	C30/37
C30 \ 37	C30/37

In this particular instance, the C25 / 30, C25-30, C25 – 30 and C25 \ 30 attribute values would be automatically converted to the C25/30 attribute value. The first column contains the attribute values for the object attribute, and the second column contains the new attribute values. The program transfers these values to the corresponding dialog box.