<?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: Zones on Zones in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Zones-on-Zones/m-p/48070#M4428</link>
    <description>&lt;BLOCKQUOTE&gt;vincon2 wrote:&lt;BR /&gt;Are there any known issues with puting zones on top of zones?&lt;/BLOCKQUOTE&gt;

As long as you create a system for the zones (e.g. separate layers) it should not be problematic at all.</description>
    <pubDate>Sat, 17 Sep 2005 03:19:00 GMT</pubDate>
    <dc:creator>Djordje</dc:creator>
    <dc:date>2005-09-17T03:19:00Z</dc:date>
    <item>
      <title>Zones on Zones</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Zones-on-Zones/m-p/48069#M4427</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Before I get carried away on something that may cause me a bigger &lt;BR /&gt;
problem.  I was hoping someone could answer a question for me.&lt;BR /&gt;
&lt;BR /&gt;
So here goes:&lt;BR /&gt;
&lt;BR /&gt;
Are there any known issues with puting zones on top of zones?&lt;BR /&gt;
&lt;BR /&gt;
For instance, I plan to create:&lt;BR /&gt;
&lt;BR /&gt;
1. zones to delieneate and name each room from the interior edge of &lt;BR /&gt;
walls&lt;BR /&gt;
&lt;BR /&gt;
2. an overall zone by floor that will reprent the entire perimeter and &lt;BR /&gt;
all porchs and patios based on the exterior of the walls(ie framing square feet)&lt;BR /&gt;
&lt;BR /&gt;
3. zones that correspond to my HVAC system so I can show which unit &lt;BR /&gt;
serves which area in a house&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 17 Sep 2005 01:56:36 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Zones-on-Zones/m-p/48069#M4427</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-09-17T01:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: Zones on Zones</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Zones-on-Zones/m-p/48070#M4428</link>
      <description>&lt;BLOCKQUOTE&gt;vincon2 wrote:&lt;BR /&gt;Are there any known issues with puting zones on top of zones?&lt;/BLOCKQUOTE&gt;

As long as you create a system for the zones (e.g. separate layers) it should not be problematic at all.</description>
      <pubDate>Sat, 17 Sep 2005 03:19:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Zones-on-Zones/m-p/48070#M4428</guid>
      <dc:creator>Djordje</dc:creator>
      <dc:date>2005-09-17T03:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: Zones on Zones</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Zones-on-Zones/m-p/48071#M4429</link>
      <description>If the zones are only for extracting area and volume information, then I don't see a problem, as Djordje says.&lt;BR /&gt;
&lt;BR /&gt;
But, if you plan on creating schedules that indicate what zones objects are in (furnishing schedule), or into which zones doors swing, etc. ... then you will have a bit of a mess.&lt;BR /&gt;
&lt;BR /&gt;
ArchiCAD keeps track of the multiplicity of zones,  and using SQL or ODBC, you can extract and display the complete list of overlapping zones that an object resides in.&lt;BR /&gt;
&lt;BR /&gt;
BUT, within ArchiCAD itself - the Interactive Scheduler for instance - there is only one zone field.  It is a game of roulette which zone will be reported when there are multiples from what I know a the moment.&lt;BR /&gt;
&lt;BR /&gt;
Karl</description>
      <pubDate>Sat, 17 Sep 2005 15:34:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Zones-on-Zones/m-p/48071#M4429</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2005-09-17T15:34:00Z</dc:date>
    </item>
  </channel>
</rss>

