<?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: .mod vs .pln as hotlink file in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/mod-vs-pln-as-hotlink-file/m-p/161925#M5717</link>
    <description>It depends on the circumstances. &lt;BR /&gt;
&lt;BR /&gt;
MODs are best for linking small collections of elements that may be repeated within a project or reused in various projects. Examples of this would be unit plans for multi-family developments and standard lavatory layouts respectively.&lt;BR /&gt;
&lt;BR /&gt;
Linking PLNs is preferable for entire floors or buildings which are subject to frequent change and updating. An example of this would be linking multiple buildings being designed for a single campus. I have also used this approach for linking the architectural and structural models of large projects.&lt;BR /&gt;
&lt;BR /&gt;
The main difference is that PLNs bring with them &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;all&lt;E&gt;&lt;/E&gt; their attributes (layers, materials, etc.) while MODs contain only those actually used by the components of the module.</description>
    <pubDate>Fri, 25 Dec 2009 15:06:23 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2009-12-25T15:06:23Z</dc:date>
    <item>
      <title>.mod vs .pln as hotlink file</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/mod-vs-pln-as-hotlink-file/m-p/161924#M5716</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Hi all,&lt;BR /&gt;
Can you guys tell me, which one better using .mod and .pln as hotlink file?&lt;BR /&gt;
thanks a lot. &lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Regards &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_smile.gif" style="display : inline;" /&gt;&lt;BR /&gt;
&lt;BR /&gt;
Pandji&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 May 2023 09:11:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/mod-vs-pln-as-hotlink-file/m-p/161924#M5716</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-26T09:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: .mod vs .pln as hotlink file</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/mod-vs-pln-as-hotlink-file/m-p/161925#M5717</link>
      <description>It depends on the circumstances. &lt;BR /&gt;
&lt;BR /&gt;
MODs are best for linking small collections of elements that may be repeated within a project or reused in various projects. Examples of this would be unit plans for multi-family developments and standard lavatory layouts respectively.&lt;BR /&gt;
&lt;BR /&gt;
Linking PLNs is preferable for entire floors or buildings which are subject to frequent change and updating. An example of this would be linking multiple buildings being designed for a single campus. I have also used this approach for linking the architectural and structural models of large projects.&lt;BR /&gt;
&lt;BR /&gt;
The main difference is that PLNs bring with them &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;all&lt;E&gt;&lt;/E&gt; their attributes (layers, materials, etc.) while MODs contain only those actually used by the components of the module.</description>
      <pubDate>Fri, 25 Dec 2009 15:06:23 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/mod-vs-pln-as-hotlink-file/m-p/161925#M5717</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-12-25T15:06:23Z</dc:date>
    </item>
  </channel>
</rss>

