<?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: Documenting proposed site levels in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239405#M36417</link>
    <description>Or you could use another mesh as your SOE operator using &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;subtraction with upwards extrusion&lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;, then dimension that mesh instead?&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Ling.</description>
    <pubDate>Wed, 27 Jan 2021 01:34:31 GMT</pubDate>
    <dc:creator>Lingwisyer</dc:creator>
    <dc:date>2021-01-27T01:34:31Z</dc:date>
    <item>
      <title>Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239402#M36414</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I'm not sure if I'm using the correct workflow.&lt;BR /&gt;
I have a sloping site (mesh), I have used a slab and performed a SEO to create a flat building platform.&lt;BR /&gt;
I then need to add level dimensions to indicate what the proposed levels are.&lt;BR /&gt;
When I use the level dimension tool, the dimensions only return the original heights, not the new cut heights.&lt;BR /&gt;
&lt;BR /&gt;
This seems like a silly question, but can the level dimension tool be used to dimension the levels of a cut+fill site?&lt;BR /&gt;
Or is it a case that we can not (should not) use the SEO to cut meshes?&lt;BR /&gt;
&lt;BR /&gt;
I'm hoping I'm just using the tools incorrectly.&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance for any assistance.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 22 May 2023 21:51:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239402#M36414</guid>
      <dc:creator>Josh Verran</dc:creator>
      <dc:date>2023-05-22T21:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239403#M36415</link>
      <description>A follow-up query would be how to show the actual mesh in plan view.&lt;BR /&gt;
Currently, it shows as a green rectangle, whereas I would have expected to see something that resembled the new shape of the mesh.&lt;BR /&gt;
&lt;BR /&gt;
Something like in the image below.&lt;BR /&gt;</description>
      <pubDate>Sun, 24 Jan 2021 21:07:52 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239403#M36415</guid>
      <dc:creator>Josh Verran</dc:creator>
      <dc:date>2021-01-24T21:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239404#M36416</link>
      <description>Solid Element Operations do not show in floor plan views.&lt;BR /&gt;
That is why you will not be able to dimension them there either.&lt;BR /&gt;
&lt;BR /&gt;
You could try converting the mesh into a morph.&lt;BR /&gt;
Then you will see the cuts in plan.&lt;BR /&gt;
I would keep a copy of the original mesh in a hidden layer so you can edit it as needed.&lt;BR /&gt;
Sometimes it is not so easy to edit the morph as you want.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Mon, 25 Jan 2021 02:17:35 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239404#M36416</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2021-01-25T02:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239405#M36417</link>
      <description>Or you could use another mesh as your SOE operator using &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;subtraction with upwards extrusion&lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;, then dimension that mesh instead?&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Ling.</description>
      <pubDate>Wed, 27 Jan 2021 01:34:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239405#M36417</guid>
      <dc:creator>Lingwisyer</dc:creator>
      <dc:date>2021-01-27T01:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239406#M36418</link>
      <description>Thanks for the feedback guys. Guess we'll keep plodding along with workarounds for now.&lt;BR /&gt;
&lt;BR /&gt;
This is one of the aspects of Archicad (and other packages too) that surprises me.&lt;BR /&gt;
It seems like such a fundamental requirement for documenting the construction of a building (the ability to be able to document siteworks, before the building is even established).&lt;BR /&gt;
Yet the tools aren't up to the task.&lt;BR /&gt;
&lt;BR /&gt;
A mesh tool that doesn't display in plan view, the way it does in all other views.&lt;BR /&gt;
A level dimension tool that can't return the dimension level of the element it's associated too.&lt;BR /&gt;
&lt;BR /&gt;
How does something like this get overlooked for so long?</description>
      <pubDate>Thu, 28 Jan 2021 22:16:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239406#M36418</guid>
      <dc:creator>Josh Verran</dc:creator>
      <dc:date>2021-01-28T22:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239407#M36419</link>
      <description>&lt;BLOCKQUOTE&gt;Josh wrote:&lt;BR /&gt;
A mesh tool that doesn't display in plan view, the way it does in all other views.&lt;BR /&gt;
A level dimension tool that can't return the dimension level of the element it's associated too.
&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
The mesh tool does display in the plan view as it does in the other views.&lt;BR /&gt;
It is the Solid Element Operation that does not show.&lt;BR /&gt;
&lt;BR /&gt;
If you edit the mesh by adding contours and adjusting levels, or in the example you show, cut a hole and add another mesh inside, you will see exactly what you want and you can use the level dimension tool.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Fri, 29 Jan 2021 00:52:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239407#M36419</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2021-01-29T00:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239408#M36420</link>
      <description>To cut into a Mesh, you could also try to use the Opening Tool (added in AC23).&lt;BR /&gt;
Which you'll see on the Floor Plan.&lt;BR /&gt;
&lt;BR /&gt;
I made a video early last year, you can skip towards the end.&lt;BR /&gt;
&lt;IFRAME width="640" height="360" src="https://www.youtube.com/embed/Y3bAEEGgOVU" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""&gt;&lt;/IFRAME&gt;</description>
      <pubDate>Fri, 29 Jan 2021 16:40:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239408#M36420</guid>
      <dc:creator>James B</dc:creator>
      <dc:date>2021-01-29T16:40:21Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239409#M36421</link>
      <description>&lt;BLOCKQUOTE&gt;Barry wrote:&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;Josh wrote:&lt;BR /&gt;
A mesh tool that doesn't display in plan view, the way it does in all other views.&lt;BR /&gt;
A level dimension tool that can't return the dimension level of the element it's associated too.
&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
The mesh tool does display in the plan view as it does in the other views.&lt;BR /&gt;
It is the Solid Element Operation that does not show.&lt;BR /&gt;
&lt;BR /&gt;
If you edit the mesh by adding contours and adjusting levels, or in the example you show, cut a hole and add another mesh inside, you will see exactly what you want and you can use the level dimension tool.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Barry.
&lt;/BLOCKQUOTE&gt;

Hi Barry&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your response and I hear what you're saying.&lt;BR /&gt;
The point I was trying to make, is that in the elevations, sections, perspectives, 3D documents etc it is the mesh that is showing, not the SEO and it all looks as expected and intended.&lt;BR /&gt;
It is the plan view that is the odd one out. One would expect the plan view to reflect. &lt;BR /&gt;
In the Elevations, Sections etc, we are seeing the surface of the mesh using the defined settings of that surface, where the mesh is cut we see the building material of the mesh with its defined settings.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;3D View&lt;/B&gt;


&lt;B&gt;3D Document&lt;/B&gt;


&lt;B&gt;Elevation&lt;/B&gt;


&lt;B&gt;Section&lt;/B&gt;</description>
      <pubDate>Mon, 01 Feb 2021 18:50:16 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239409#M36421</guid>
      <dc:creator>Josh Verran</dc:creator>
      <dc:date>2021-02-01T18:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239410#M36422</link>
      <description>&lt;B&gt;Plan View I was expecting&lt;/B&gt;


&lt;B&gt;Plan view we get&lt;/B&gt;


Whilst the workarounds of drawing elements over can work it's not an efficient workflow.&lt;BR /&gt;
&lt;BR /&gt;
In order to see the cut + fill in plan view as described you need to have SEO on and set the cover fill to match that of the element you are trying to indicate. Kind of drawing a fill over it.&lt;BR /&gt;
The idea of not using SEOs and instead drawing new contours achieves a few requirements but then fails on others. New contours instead of SEOs would then mean you are limited to one surface, you can't then show the cut areas as earth/soil. Also the new contours are not often known. In the "Plan View Expected" above, we can see where the contours should be as the SEO has already been curved on the downward slope region, trying to work this out thou without SEOs would be time consuming.&lt;BR /&gt;
&lt;BR /&gt;
As described earlier with the level dimesnion tool and setting the SEO to zero thickness means you can't batter edges as I have done on above examples.&lt;BR /&gt;
&lt;BR /&gt;
I'm very grateful for the assistance, my frustration is more at how the software can't show the operations (not to be confused with operators) in plan view. &lt;BR /&gt;
&lt;BR /&gt;
Why would we want to have an object appear in all other views as "operated on". But in plan view have zero ability to represent it's true shape?</description>
      <pubDate>Mon, 01 Feb 2021 19:00:56 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239410#M36422</guid>
      <dc:creator>Josh Verran</dc:creator>
      <dc:date>2021-02-01T19:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239411#M36423</link>
      <description>&lt;BLOCKQUOTE&gt;James wrote:&lt;BR /&gt;
To cut into a Mesh, you could also try to use the Opening Tool (added in AC23).&lt;BR /&gt;
Which you'll see on the Floor Plan.&lt;BR /&gt;
&lt;BR /&gt;
I made a video early last year, you can skip towards the end.&lt;BR /&gt;
&lt;IFRAME width="640" height="360" src="https://www.youtube.com/embed/Y3bAEEGgOVU" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""&gt;&lt;/IFRAME&gt;
&lt;/BLOCKQUOTE&gt;

Thanks James, I didn't realise the opening tool worked on meshes as well.&lt;BR /&gt;
I think this will work in some situations.&lt;BR /&gt;
You can't batter edges (angle/slope) or curve in plan view thou I think.</description>
      <pubDate>Mon, 01 Feb 2021 19:06:58 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239411#M36423</guid>
      <dc:creator>Josh Verran</dc:creator>
      <dc:date>2021-02-01T19:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239412#M36424</link>
      <description>&lt;BLOCKQUOTE&gt;Josh wrote:&lt;BR /&gt;The point I was trying to make, is that in the elevations, sections, perspectives, 3D documents etc it is the mesh that is showing, not the SEO and it all looks as expected and intended.
&lt;/BLOCKQUOTE&gt;


&lt;BLOCKQUOTE&gt;Josh wrote:&lt;BR /&gt;
Why would we want to have an object appear in all other views as "operated on". But in plan view have zero ability to represent it's true shape?
&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
Sections and elevation are all 3D views, just from a particular angle.&lt;BR /&gt;
That is why the SEO results show as they can only be seen in 3D.&lt;BR /&gt;
&lt;BR /&gt;
The 2D (plan) view is not a 3D view, it is somehow recreated based on the model elements, but it ignores SEOs.&lt;BR /&gt;
I don't know the reason why but I suspect it is a legacy code thing, when Archicad was first written, there were no SEOs to worry about and the 2D view has always been a 'symbolic' view..&lt;BR /&gt;
You will find new tools like the opening and multi-plane roofs do show the results of SEOs (or connections/trims) in plan.&lt;BR /&gt;
Eventually the 2D view may be based entirely from the 3D.&lt;BR /&gt;
Actually you can do this now with 3D documents - but the level dimension tool will not work.&lt;BR /&gt;
You can copy and paste the mesh contours from the 3D Document back to the floor plan.&lt;BR /&gt;
Not that that will help with the levels still.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 02 Feb 2021 00:17:56 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239412#M36424</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2021-02-02T00:17:56Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239413#M36425</link>
      <description>Hi Barry&lt;BR /&gt;
&lt;BR /&gt;
Hopefully one day it will be implemented.&lt;BR /&gt;
I always find it funny (maybe frustrating is a better word) when I come across things like this from yonks ago.&lt;BR /&gt;
Why isn't there more focus on "hey these workflows and/or tools are outdated and not functioning the same as newer tools, perhaps we should bring these up to spec before we go creating and developing new tools".&lt;BR /&gt;
I know the development of these features is no simple task, probably a lot more complicated than I even suspect now. But, it's possible and other features are more complex.</description>
      <pubDate>Tue, 02 Feb 2021 04:40:09 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239413#M36425</guid>
      <dc:creator>Josh Verran</dc:creator>
      <dc:date>2021-02-02T04:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: Documenting proposed site levels</title>
      <link>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239414#M36426</link>
      <description>&lt;BLOCKQUOTE&gt;Josh wrote:&lt;BR /&gt;
Hi Barry&lt;BR /&gt;
&lt;BR /&gt;
Hopefully one day it will be implemented.&lt;BR /&gt;
I always find it funny (maybe frustrating is a better word) when I come across things like this from yonks ago.&lt;BR /&gt;
Why isn't there more focus on "hey these workflows and/or tools are outdated and not functioning the same as newer tools, perhaps we should bring these up to spec before we go creating and developing new tools".&lt;BR /&gt;
I know the development of these features is no simple task, probably a lot more complicated than I even suspect now. But, it's possible and other features are more complex.
&lt;/BLOCKQUOTE&gt;

I do hope for that too. Yet the more i look into this problem i tend to believe it´s not implemented for it has a chance to backfire on performance due to 3 to 2D conversion, as may happen when you have a couple GDL objects that will use Project2 variants.&lt;BR /&gt;
&lt;BR /&gt;
Funny thing: Roofs behave that way. They'll show SOE in plan.</description>
      <pubDate>Thu, 04 Feb 2021 14:44:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Documenting-proposed-site-levels/m-p/239414#M36426</guid>
      <dc:creator>vdentello</dc:creator>
      <dc:date>2021-02-04T14:44:34Z</dc:date>
    </item>
  </channel>
</rss>

