<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to prevent two polygons from merging as same soil/material in python API? Seems that when you add a different polygon on top of an already existing polygon, Plaxis automatically assigns a soil material of the polygon underneath?</title><link>https://communities.bentley.com/products/geotech-analysis/f/forum/209830/how-to-prevent-two-polygons-from-merging-as-same-soil-material-in-python-api-seems-that-when-you-add-a-different-polygon-on-top-of-an-already-existing-polygon-plaxis-automatically-assigns-a-soil-material-of-the-polygon-undern</link><description>As further description to the title, it seems in the python API when you add a polygon on top of an already existing soil polygon, when you run a gotostages or gotoflows function, the soil/material assigned to the smaller polygon (yellow below) in the</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: How to prevent two polygons from merging as same soil/material in python API? Seems that when you add a different polygon on top of an already existing polygon, Plaxis automatically assigns a soil material of the polygon underneath?</title><link>https://communities.bentley.com/thread/751489?ContentTypeID=1</link><pubDate>Wed, 01 Feb 2023 13:32:42 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:57b2b980-d277-459a-bd30-51fce6701c75</guid><dc:creator>Stefanos Papavasileiou</dc:creator><description>&lt;p&gt;Hello Tom,&lt;/p&gt;
&lt;p&gt;The material assigned to a soil layer created by a borehole takes precedence.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The moment you switch to Staged construction, intersection takes place. Then PLAXIS needs to make sure that all created new objects (here polygons) have all properties assigned.&lt;/p&gt;
&lt;p&gt;Naturally in conflicts, a choice has to be made. In this case, for the materials of polygons the configured soil layer will &amp;quot;win&amp;quot; over any polygon created in Structures mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to prevent two polygons from merging as same soil/material in python API? Seems that when you add a different polygon on top of an already existing polygon, Plaxis automatically assigns a soil material of the polygon underneath?</title><link>https://communities.bentley.com/thread/638041?ContentTypeID=1</link><pubDate>Tue, 09 Mar 2021 10:32:38 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:d52c6704-d2f8-45b9-8db4-efd94af77023</guid><dc:creator>Iman Warsame</dc:creator><description>&lt;p&gt;I am also having this issue. Are there any solutions yet?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>