Attributes, such as Composites, Surfaces, Complex Profiles should allow for the creation of Custom Data Fields.
For example, wall types are typically created as Composites.
There are performance data that belong to the Wall Type and not to the components of the wall type.
Such as:
Wall Type Code
-All walls that use the same composite would be coded / documented as the same wall type, therefore the wall type can't / should not be allocated at the instance level, but it should be assigned at the composite (attribute) level.
Fire Performance
- It is defined by the wall type, not the individual layers of the wall buildup.
In other words, you can't get the Fire performance of a wall by adding up the Fire Performance values of it's components.
Acoustic Performance
- Same as Fire Performance, Acoustic performance belongs to the Composite, not to the elements of the composite
etc
Currently the only data field available for composites is their name.
Using a very cumbersome workaround, we can name the composites in a particular way, putting all the relevant info into the name field, then we can split the info using expressions, however this is a very clunky and error prone workaround.
A wall type legend, similar to below is commonly used.
These wall types then are annotated in plan view using labels.
Attribute level properties should be edited at each attribute's editing window.
These attributes belong to that specific set of attribute only, not used anywhere else.
For example:
Composits should have their own set of properties / custom data fields that should be set up and edited in the Composite Settings dialogue box.
A thread working towards similar goal is , however that wish only asks for ID's for surfaces.
I am certain that something like what I wish for is a more global solution and would please many-many users.
Open