<?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: reducing zone area v19 in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/reducing-zone-area-v19/m-p/234897#M30165</link>
    <description>We use different zones for the 'usable space' square meters and the 'gross volume' (and quantity take off). Might not be what you like, but it works quite fast.&lt;BR /&gt;
&lt;BR /&gt;
You can use 2d linework as a zone boundary and we use that to communicate where the 1.500 mm and 2.600 mm heights, that are of interest in determining the 'usable space' according to our building regulations, are anyway.</description>
    <pubDate>Fri, 07 Oct 2016 07:22:47 GMT</pubDate>
    <dc:creator>Erwin Edel</dc:creator>
    <dc:date>2016-10-07T07:22:47Z</dc:date>
    <item>
      <title>reducing zone area v19</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/reducing-zone-area-v19/m-p/234895#M30163</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;hi! &lt;BR /&gt;
I'm calculating zones according to our principles and we have to calculate volume of the roof, but we shouldn't include the area. &lt;BR /&gt;
so I'm kind of working around - zone is trimmed by  SEO operations to the roof so the volume is correct, but, since I have to reduce area to 0, usually I was including the option Reduce by  and set that to 100%  &lt;BR /&gt;
it worked until AC v19 where area isn't reduced even after updating. &lt;BR /&gt;
 &lt;BR /&gt;
I know about reducing area by zone preferences but I cannot include that because other zones would by reduced also (it's already set to reduce zones lower than 200cm by 100%) &lt;BR /&gt;
 &lt;BR /&gt;
any suggestions what to do? &lt;BR /&gt;
except export that to xls and make the change there...&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 06 Oct 2016 13:19:42 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/reducing-zone-area-v19/m-p/234895#M30163</guid>
      <dc:creator>Sasa Glagolic Ogorel</dc:creator>
      <dc:date>2016-10-06T13:19:42Z</dc:date>
    </item>
    <item>
      <title>Re: reducing zone area v19</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/reducing-zone-area-v19/m-p/234896#M30164</link>
      <description>Can you post a screenshot which show the Area Reduction panel of your Zone Settings Dialog, and another that shows the resulting info displayed in the Zone Stamp.&lt;BR /&gt;
I am trying to figure out if this is a bug, because if the Area is not reduced, then it may be.</description>
      <pubDate>Thu, 06 Oct 2016 17:36:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/reducing-zone-area-v19/m-p/234896#M30164</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2016-10-06T17:36:13Z</dc:date>
    </item>
    <item>
      <title>Re: reducing zone area v19</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/reducing-zone-area-v19/m-p/234897#M30165</link>
      <description>We use different zones for the 'usable space' square meters and the 'gross volume' (and quantity take off). Might not be what you like, but it works quite fast.&lt;BR /&gt;
&lt;BR /&gt;
You can use 2d linework as a zone boundary and we use that to communicate where the 1.500 mm and 2.600 mm heights, that are of interest in determining the 'usable space' according to our building regulations, are anyway.</description>
      <pubDate>Fri, 07 Oct 2016 07:22:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/reducing-zone-area-v19/m-p/234897#M30165</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2016-10-07T07:22:47Z</dc:date>
    </item>
  </channel>
</rss>

