<?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 IFC import in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-import/m-p/284533#M37296</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi again.&lt;BR /&gt;
&lt;BR /&gt;
So we are importing an ifc and some elements were converted to archicad columns and beams and others are just objects (based on our ifc translator)&lt;BR /&gt;
&lt;BR /&gt;
Is there any setting I can tweak to make every ifc element converted to real archicad elements and not objects or morphs?&lt;BR /&gt;
&lt;BR /&gt;
Also the Archicad reference guide advises to set the translator to translate construction elements to objects instead of morphs. I prefer conversion to morphs because they have the same floor plan display options as in archicad columns, beams, walls etc....&lt;BR /&gt;
&lt;BR /&gt;
Is there any disadvantage from converting elements to morphs instead of objects? &lt;BR /&gt;
&lt;BR /&gt;
Looking forward to your wisdom!!! thanks in advance!!!&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 08 Jan 2020 10:36:51 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2020-01-08T10:36:51Z</dc:date>
    <item>
      <title>IFC import</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-import/m-p/284533#M37296</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi again.&lt;BR /&gt;
&lt;BR /&gt;
So we are importing an ifc and some elements were converted to archicad columns and beams and others are just objects (based on our ifc translator)&lt;BR /&gt;
&lt;BR /&gt;
Is there any setting I can tweak to make every ifc element converted to real archicad elements and not objects or morphs?&lt;BR /&gt;
&lt;BR /&gt;
Also the Archicad reference guide advises to set the translator to translate construction elements to objects instead of morphs. I prefer conversion to morphs because they have the same floor plan display options as in archicad columns, beams, walls etc....&lt;BR /&gt;
&lt;BR /&gt;
Is there any disadvantage from converting elements to morphs instead of objects? &lt;BR /&gt;
&lt;BR /&gt;
Looking forward to your wisdom!!! thanks in advance!!!&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 08 Jan 2020 10:36:51 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-import/m-p/284533#M37296</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-01-08T10:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: IFC import</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-import/m-p/284534#M37297</link>
      <description>Hello Luiscardoso,&lt;BR /&gt;
&lt;BR /&gt;
A object can be repeat into your model to reduce the weight of your file : not a morph.&lt;BR /&gt;
A morph is not as easy to modify than a bim conception tool like slab, beam or column.&lt;BR /&gt;
&lt;BR /&gt;
To modify easily an ifc with archicad nativ tools, it might be even more easy by importing an IFC 4 by design transfer view. But today there are not many software to do this with the right certification : &lt;A href="https://www.buildingsmart.org/compliance/software-certification/certified-software/" target="_blank"&gt;&lt;LINK_TEXT text="https://www.buildingsmart.org/complianc ... -software/"&gt;https://www.buildingsmart.org/compliance/software-certification/certified-software/&lt;/LINK_TEXT&gt;&lt;/A&gt;</description>
      <pubDate>Wed, 08 Jan 2020 14:39:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-import/m-p/284534#M37297</guid>
      <dc:creator>Christophe Fortineau</dc:creator>
      <dc:date>2020-01-08T14:39:21Z</dc:date>
    </item>
  </channel>
</rss>

