<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Base Quantities for Objects (2025) in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Base-Quantities-for-Objects-2025/m-p/652904#M43722</link>
    <description>&lt;P&gt;This is something important, indeed. As long as there are more elements built from a GDL-object perspective, that could be an issue regarding the publication of QTO and Bill of Quantities based on openBIM approach from Archicad.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 24 Feb 2025 11:26:15 GMT</pubDate>
    <dc:creator>davdelven</dc:creator>
    <dc:date>2025-02-24T11:26:15Z</dc:date>
    <item>
      <title>Base Quantities for Objects (2025)</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Base-Quantities-for-Objects-2025/m-p/652161#M43712</link>
      <description>&lt;P&gt;There is a 2019 post with a similar subject, but I'm looking for a more general solution.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm setting up modelling conventions based on IFC and need to confirm if this also works inside Archicad.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Base Quantities for beams, columns and quite a few other Archicad categories are calculated automatically, when you active &lt;EM&gt;IFC Base Quantities&lt;/EM&gt; in the IFC Translator. However, when using GDL objects, this doesn't seem to be the case.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;E.g., when I use a "Beam" GDL Object, no quantities are exported (I did classify the object as a Beam so it becomes an &lt;EM&gt;IfcBeam&lt;/EM&gt; upon export).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I added a custom IFC property named &lt;EM&gt;Qto_BeamBaseQuantities.NetVolume&lt;/EM&gt; in the IFC project manager to the GDL Beam.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="stefan_1-1739865624669.png" style="width: 640px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/83348i41892DE1E1CB3520/image-dimensions/640x623?v=v2" width="640" height="623" role="button" title="stefan_1-1739865624669.png" alt="stefan_1-1739865624669.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;and also set a mapping rule inside the IFC Translator to map the default "volume (net)" to this IFC Quantity.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="stefan_0-1739865514713.png" style="width: 800px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/83346iE126749E8CB4B3BA/image-dimensions/800x481?v=v2" width="800" height="481" role="button" title="stefan_0-1739865514713.png" alt="stefan_0-1739865514713.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And as a result, the Quantity is there in the IFC file...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="stefan_2-1739865754277.png" style="width: 800px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/83350i2371A560B4F36017/image-dimensions/800x420?v=v2" width="800" height="420" role="button" title="stefan_2-1739865754277.png" alt="stefan_2-1739865754277.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Alas... this is not a real Quantity (&lt;EM&gt;IfcVolumeMeasure&lt;/EM&gt;), but an&amp;nbsp;&lt;EM&gt;IfcPropertySingleValue&lt;/EM&gt; in the IFC file. So it only looks about right, but is semantically wrong...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="stefan_3-1739865865488.png" style="width: 640px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/83351i9DAFA34CB9851202/image-dimensions/640x270?v=v2" width="640" height="270" role="button" title="stefan_3-1739865865488.png" alt="stefan_3-1739865865488.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;At the same time, I assume that actual beams get properly calculated, so there is no reason to override this calculation based on my rule. What would be the correct approach? I don't want to recreate the full set of all IFC Base Quantities for all objects, based on the built-in quantities for Archicad objects, if they are already properly calculated for regular categories.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Are custom quantities properly supported in the Archicad IFC mappings and translators?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2025 03:29:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Base-Quantities-for-Objects-2025/m-p/652161#M43712</guid>
      <dc:creator>stefan</dc:creator>
      <dc:date>2025-02-19T03:29:48Z</dc:date>
    </item>
    <item>
      <title>Re: Base Quantities for Objects (2025)</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Base-Quantities-for-Objects-2025/m-p/652904#M43722</link>
      <description>&lt;P&gt;This is something important, indeed. As long as there are more elements built from a GDL-object perspective, that could be an issue regarding the publication of QTO and Bill of Quantities based on openBIM approach from Archicad.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 11:26:15 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Base-Quantities-for-Objects-2025/m-p/652904#M43722</guid>
      <dc:creator>davdelven</dc:creator>
      <dc:date>2025-02-24T11:26:15Z</dc:date>
    </item>
  </channel>
</rss>

