<?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: Identifying &amp;quot;Undefined&amp;quot; roof edges in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282400#M37021</link>
    <description>&lt;BLOCKQUOTE&gt;poco2013 wrote:&lt;BR /&gt;
AFAIK -- There is no property which reports roof edge(s) type so I think you are out of luck&lt;BR /&gt;
&lt;BR /&gt;
However, there are length properties for eaves, gables, hips, peaks, ridges, and valleys. Side, end wall &amp;amp; Dome, Hollow are not reported. An edge should be defined as one of these. A undefined edge will report all lengths as 0. You could create an expression (reporting true/false) to check that the edge in question is not zero for the roof(s) your interested in. ( by classification filter)&lt;BR /&gt;
&lt;BR /&gt;
Then create a  graphic override rule using that expression which identifies any roof plane which has a zero length edge -- IOW - undefined. The problem I see is that any plane will not use all of the available edge types so you could not use a blanket inquiry.&lt;BR /&gt;
&lt;BR /&gt;
With more info might be able to define something more specific. Are you only interested in eaves, etc. or all edges??
&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
Yes I am just in the process of testing this.&lt;BR /&gt;
I thought of it just after I made this post.&lt;BR /&gt;
&lt;BR /&gt;
Still the problem is if ALL edges are undefined then it will be easy to spot.&lt;BR /&gt;
If only one or two edges are undefined, you will still get values for other edges, so it will still be hard to spot.&lt;BR /&gt;
&lt;BR /&gt;
However I did think of using properties for all the edge lengths and also one for the 3D perimeter.&lt;BR /&gt;
Then compare the total of all the edge lengths with the perimeter (have to double hips, ridges and valleys as they report half lengths).&lt;BR /&gt;
If they are the same (or within a small difference) the I can assume all the edge types have been set.&lt;BR /&gt;
If not the same then use a GO as you suggest to highlight the roof plane.&lt;BR /&gt;
&lt;BR /&gt;
Basically I need to determine if all the edges have been defined so I can schedule them.&lt;BR /&gt;
This doesn't help if the edge is defined as the wrong type of course.&lt;BR /&gt;
It would be great if we could label the roof edges or GO individual parts of an element.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
    <pubDate>Tue, 05 Feb 2019 06:08:07 GMT</pubDate>
    <dc:creator>Barry Kelly</dc:creator>
    <dc:date>2019-02-05T06:08:07Z</dc:date>
    <item>
      <title>Identifying "Undefined" roof edges</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282398#M37019</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I am trying to schedule the roof edges - eaves, ridges, hips,  etc., which is easy enough.&lt;BR /&gt;
&lt;BR /&gt;
But the problem I am having is with single plane roofs - when the edges are "Undefined".&lt;BR /&gt;
There is no way to schedule these edges so that I could at least be aware that the 'edge type' has not been set.&lt;BR /&gt;
&lt;BR /&gt;
Currently I must check the edge of every single roof plane one by one to see that the correct edge type is set.&lt;BR /&gt;
There could be dozens of the edges to check.&lt;BR /&gt;
This is not a problem for multi-plane roofs as the edges are set correctly.&lt;BR /&gt;
Even when splitting a multi-plane roof into single planes all is good.&lt;BR /&gt;
It is only a problem when modifying a single plane roof or modelling a new one - something we do a lot.&lt;BR /&gt;
Plus my office has many plans based on old plans originally modelled before the multi-plane roof was around and hence no edge types are set.&lt;BR /&gt;
&lt;BR /&gt;
Does anyone have any clever ways of showing the edge type in plan?&lt;BR /&gt;
I have looked in Graphic Overrides but there is nothing - plus the fact that GOs don't work on individual parts on an element any way.&lt;BR /&gt;
I can't even find a solution in GDL, as there seems no command that recognises the roof edge type.&lt;BR /&gt;
&lt;BR /&gt;
If anyone has any ideas of how I can identify an 'Undefined' roof edge, or better still identify all roof edge types in plan, then please let me know.&lt;BR /&gt;
&lt;BR /&gt;
Barry.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 05 Feb 2019 03:14:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282398#M37019</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2019-02-05T03:14:31Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying "Undefined" roof edges</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282399#M37020</link>
      <description>AFAIK -- There is no property which reports roof edge(s) type so I think you are out of luck&lt;BR /&gt;
&lt;BR /&gt;
However, there are length properties for eaves, gables, hips, peaks, ridges, and valleys. Side, end wall &amp;amp; Dome, Hollow are not reported. An edge should be defined as one of these. A undefined edge will report all lengths as 0. You could create an expression (reporting true/false) to check that the edge in question is not zero for the roof(s) your interested in. ( by classification filter)&lt;BR /&gt;
&lt;BR /&gt;
Then create a  graphic override rule using that expression which identifies any roof plane which has a zero length edge -- IOW - undefined. The problem I see is that any plane will not use all of the available edge types so you could not use a blanket inquiry.&lt;BR /&gt;
&lt;BR /&gt;
With more info might be able to define something more specific. Are you only interested in eaves, etc. or all edges??</description>
      <pubDate>Tue, 05 Feb 2019 04:47:41 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282399#M37020</guid>
      <dc:creator>poco2013</dc:creator>
      <dc:date>2019-02-05T04:47:41Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying "Undefined" roof edges</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282400#M37021</link>
      <description>&lt;BLOCKQUOTE&gt;poco2013 wrote:&lt;BR /&gt;
AFAIK -- There is no property which reports roof edge(s) type so I think you are out of luck&lt;BR /&gt;
&lt;BR /&gt;
However, there are length properties for eaves, gables, hips, peaks, ridges, and valleys. Side, end wall &amp;amp; Dome, Hollow are not reported. An edge should be defined as one of these. A undefined edge will report all lengths as 0. You could create an expression (reporting true/false) to check that the edge in question is not zero for the roof(s) your interested in. ( by classification filter)&lt;BR /&gt;
&lt;BR /&gt;
Then create a  graphic override rule using that expression which identifies any roof plane which has a zero length edge -- IOW - undefined. The problem I see is that any plane will not use all of the available edge types so you could not use a blanket inquiry.&lt;BR /&gt;
&lt;BR /&gt;
With more info might be able to define something more specific. Are you only interested in eaves, etc. or all edges??
&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
Yes I am just in the process of testing this.&lt;BR /&gt;
I thought of it just after I made this post.&lt;BR /&gt;
&lt;BR /&gt;
Still the problem is if ALL edges are undefined then it will be easy to spot.&lt;BR /&gt;
If only one or two edges are undefined, you will still get values for other edges, so it will still be hard to spot.&lt;BR /&gt;
&lt;BR /&gt;
However I did think of using properties for all the edge lengths and also one for the 3D perimeter.&lt;BR /&gt;
Then compare the total of all the edge lengths with the perimeter (have to double hips, ridges and valleys as they report half lengths).&lt;BR /&gt;
If they are the same (or within a small difference) the I can assume all the edge types have been set.&lt;BR /&gt;
If not the same then use a GO as you suggest to highlight the roof plane.&lt;BR /&gt;
&lt;BR /&gt;
Basically I need to determine if all the edges have been defined so I can schedule them.&lt;BR /&gt;
This doesn't help if the edge is defined as the wrong type of course.&lt;BR /&gt;
It would be great if we could label the roof edges or GO individual parts of an element.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 05 Feb 2019 06:08:07 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282400#M37021</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2019-02-05T06:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying "Undefined" roof edges</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282401#M37022</link>
      <description>This would work well in theory, but for the life of me I can not add any criteria to the rules that use a property using a roof parameter.&lt;BR /&gt;
Not even if I set up a simple expression for just the roof area or hip length.&lt;BR /&gt;
&lt;BR /&gt;



&lt;BR /&gt;
So close and yet so far.  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_exclaim.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 05 Feb 2019 08:00:09 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Identifying-quot-Undefined-quot-roof-edges/m-p/282401#M37022</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2019-02-05T08:00:09Z</dc:date>
    </item>
  </channel>
</rss>

