Advanced options for defining the height settings of architectural elements

In earlier versions, the height settings of architectural elements were set relative to the upper plane and lower plane in a drawing file. As an alternative, you could define the height by entering absolute values. Custom pairs of reference planes and roof frames or roofscapes were available for special cases.

Using the plane model, you could also create components across stories by associating the components with the top level and bottom level of the building.

This concept is ideally suited for early planning phases involving planar components. However, this concept reaches its limit when it comes to subsequent planning phases (LOD 300/400). Detailing usually involves complex and inclined components. Here, planners used custom pairs of reference planes, which were often derived from 3D solids. However, this sometimes resulted in a large number of custom pairs of reference planes consisting of discrete triangular surfaces, which could not be edited quickly or easily.

Reference surfaces

Instead of custom pairs of reference planes, you can now use reference surfaces, which you can create from any polygonal 3D surfaces or general 3D surfaces. Local reference surfaces are in a drawing file. Consequently, you can only use them in this drawing file for the height definition of architectural elements. As with custom planes, the component must be in the area of the reference surface from which the component takes its height settings.

Using the Planes palette, you can insert local reference surfaces - like roofscapes - in a plane model. Once inserted, the reference surfaces are no longer linked with the local reference surfaces, but you can then use the reference surfaces in other drawing files too.

Defining height settings across stories

If a plane model is available, you can now use all planes in the plane model - independently of the default reference planes - for height definition in any drawing file. Roof planes and custom reference planes have precedence over default reference planes.

Roof planes and custom reference planes have no effect on components associated with local reference surfaces. If the component projects beyond the reference surface, the default reference planes or custom planes defined in the drawing file apply.