<?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 IfcMaterial mapping by IfcExport in Installation &amp; update</title>
    <link>https://community.graphisoft.com/t5/Installation-update/IfcMaterial-mapping-by-IfcExport/m-p/269700#M27970</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Is there a workaround for overriding the Building Material mapping to IfcMaterial. When Exporting to Ifc, ArchiCAD fills the IfcMaterial string with the predefined Building Material. &lt;BR /&gt;
Building Materials are usefull for giving materials priority. In the same time a list of Building Materials appear by using those priorities. For Example we use different names for the same Building Material in context of IsExternal and LoadBearing. It looks like this.&lt;BR /&gt;
&lt;BR /&gt;
21 - Kalkzandsteen C&lt;BR /&gt;
21 - Kalkzandsteen NC&lt;BR /&gt;
22 - Kalkzandsteen C&lt;BR /&gt;
22 - Kalkzandsteen NC&lt;BR /&gt;
&lt;BR /&gt;
21 = refering to IsExternal = true&lt;BR /&gt;
22 = refering to IsExternal = false&lt;BR /&gt;
C = refering to LoadBearing = true&lt;BR /&gt;
NC = refering to LoadBearing = false&lt;BR /&gt;
&lt;BR /&gt;
The use of priorities is intergraded in the use of namegiving.&lt;BR /&gt;
&lt;BR /&gt;
By reading the Ifc in, for example Solibri, the IfcMaterial is filled with the names above. &lt;BR /&gt;
IsExternal and LoadBearing is material independent. So the name of the IfcMaterial should be 'Kalkzandsteen'.&lt;BR /&gt;
There for I'm looking fo a workaround to get IfcMaterial mapped to 'Kalkzandsteen' instead of, for example '21 - Kalkzandsteen C'&lt;BR /&gt;
&lt;BR /&gt;
I hope someone can help&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Sat, 18 Mar 2017 07:45:29 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-03-18T07:45:29Z</dc:date>
    <item>
      <title>IfcMaterial mapping by IfcExport</title>
      <link>https://community.graphisoft.com/t5/Installation-update/IfcMaterial-mapping-by-IfcExport/m-p/269700#M27970</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Is there a workaround for overriding the Building Material mapping to IfcMaterial. When Exporting to Ifc, ArchiCAD fills the IfcMaterial string with the predefined Building Material. &lt;BR /&gt;
Building Materials are usefull for giving materials priority. In the same time a list of Building Materials appear by using those priorities. For Example we use different names for the same Building Material in context of IsExternal and LoadBearing. It looks like this.&lt;BR /&gt;
&lt;BR /&gt;
21 - Kalkzandsteen C&lt;BR /&gt;
21 - Kalkzandsteen NC&lt;BR /&gt;
22 - Kalkzandsteen C&lt;BR /&gt;
22 - Kalkzandsteen NC&lt;BR /&gt;
&lt;BR /&gt;
21 = refering to IsExternal = true&lt;BR /&gt;
22 = refering to IsExternal = false&lt;BR /&gt;
C = refering to LoadBearing = true&lt;BR /&gt;
NC = refering to LoadBearing = false&lt;BR /&gt;
&lt;BR /&gt;
The use of priorities is intergraded in the use of namegiving.&lt;BR /&gt;
&lt;BR /&gt;
By reading the Ifc in, for example Solibri, the IfcMaterial is filled with the names above. &lt;BR /&gt;
IsExternal and LoadBearing is material independent. So the name of the IfcMaterial should be 'Kalkzandsteen'.&lt;BR /&gt;
There for I'm looking fo a workaround to get IfcMaterial mapped to 'Kalkzandsteen' instead of, for example '21 - Kalkzandsteen C'&lt;BR /&gt;
&lt;BR /&gt;
I hope someone can help&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 18 Mar 2017 07:45:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Installation-update/IfcMaterial-mapping-by-IfcExport/m-p/269700#M27970</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-03-18T07:45:29Z</dc:date>
    </item>
  </channel>
</rss>

