Reference Levels (Non-Story Levels for Better Model Control)

[Pedro Melo]

It would be extremely helpful to introduce the concept of Reference Levels in Archicad — similar to Revit’s Levels — which are non-structural, non-story markers used to define key vertical positions in a model (e.g. ceiling heights, parapets, window datum lines, etc.).

These levels would not function as actual stories, and would not be exported as separate floors in IFC, but would provide a consistent and visible reference for modeling and coordination.

---

Proposed Implementation:

• Add a new category of levels in the Story Settings dialog, called Reference Levels

• Reference Levels would:

  • Appear in Section/Elevation views with custom markers

  • Be usable as snapping and alignment guides

  • Be selectable in element settings (e.g. set top of wall or beam to “Ceiling RL +2.7m”)

  • Not generate story markers or impact IFC story structure

  • Have their own layer or visibility control

Optional extras:

• Reference Levels could be grouped (e.g., Ceiling Levels, Façade Datums)

• Could be color-coded or styled differently from real stories

---

Why This Is Important:

• Improved Coordination: Ceiling levels, bulkhead lines, parapet heights, etc., can be defined and referenced clearly, without cluttering the Story structure or requiring dummy stories.

• Cleaner IFC Export: No need for fake stories that confuse consultants or clash with structural models.

• More Accurate Modeling: Allows modeling elements like walls, ceilings, and beams in relation to a defined height, not just the nearest story or manual height input.

• Industry-Standard Workflow: This aligns with how many multidisciplinary teams work — especially when integrating with Revit-based consultants.

---

Example Use Case:

In a commercial building:

• Ground Floor is at 0.00

• Ceiling RL at +3.200

• Bulkhead RL at +2.600

These are critical modeling guides, but don't warrant actual stories. Currently, workarounds like 2D lines or fake stories are used, which are not robust or parametric.

[Rve]

@Botonis 

Thank you for the info. That sounds very usefull.

I can't find any video's about it on Youtube. Could you record a small video to show how is works?

[Botonis]

Just uploaded a video to show how easy it is to add additional story levels.

And those settings are integrated inside the story marker. Not an object. 

You can have a favorite section marker saved for every case with additional stories or settings.

VIDEO STORY MARKER 

[GG_rakurs]

I think Building > Story > Level is an excellent approach. But, to take it a step further, it could also be Folder > Subfolder (1) > ... > Subfolder (n) and it would be more consistent with some other parts of the interface. On a not-this-wish note, it would be great to have everything in Project Map "subfolderable" and not just basic level. It would make so much more sense, and it would be much easier to organize everything. For people that don't need it - don't use it! But I believe most people would actually use it, especially when localization firms that produce templates for their users start to implement it. THAT would bring consistency to more parts of the UX / UI.