<?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>idea try: for cga in ArcGIS CityEngine Ideas</title>
    <link>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idi-p/1233845</link>
    <description>&lt;P&gt;Hi, this is a thing which is in my unformulated wish list for a long time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wondering if it would possible to have something similar to the try | except python version, but in cga.&lt;/P&gt;&lt;P&gt;This would be mainly for geometrical manipulation operators which "silently" fail to process a rule geometry (thinking of roofs in certain weird cases, offsets, setbacks etc). When that happens there's no way -in cga, for example with some case/else- to catch those errors because derivation stops at faulty shape and keeps input geometry in its current state (meaning if at beginning of a rule set, most of the cases without a proper material, name etc).&lt;/P&gt;&lt;P&gt;Of course these problems are somehow catchable in cga log afterwards, but I think (imho) it would really streamline and robustify generation process when dealing with massive batches.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, this is not urgent...&lt;/P&gt;</description>
    <pubDate>Mon, 21 Nov 2022 17:39:19 GMT</pubDate>
    <dc:creator>romainjanil</dc:creator>
    <dc:date>2022-11-21T17:39:19Z</dc:date>
    <item>
      <title>try: for cga</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idi-p/1233845</link>
      <description>&lt;P&gt;Hi, this is a thing which is in my unformulated wish list for a long time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wondering if it would possible to have something similar to the try | except python version, but in cga.&lt;/P&gt;&lt;P&gt;This would be mainly for geometrical manipulation operators which "silently" fail to process a rule geometry (thinking of roofs in certain weird cases, offsets, setbacks etc). When that happens there's no way -in cga, for example with some case/else- to catch those errors because derivation stops at faulty shape and keeps input geometry in its current state (meaning if at beginning of a rule set, most of the cases without a proper material, name etc).&lt;/P&gt;&lt;P&gt;Of course these problems are somehow catchable in cga log afterwards, but I think (imho) it would really streamline and robustify generation process when dealing with massive batches.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, this is not urgent...&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2022 17:39:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idi-p/1233845</guid>
      <dc:creator>romainjanil</dc:creator>
      <dc:date>2022-11-21T17:39:19Z</dc:date>
    </item>
    <item>
      <title>Re: try: for cga</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idc-p/1236323#M280</link>
      <description>&lt;P&gt;It's not what you asked for, but &lt;FONT face="courier new,courier"&gt;resetGeometry&lt;/FONT&gt; might be able to help in some (probably not all) cases (though it might be tedious).&lt;/P&gt;&lt;P&gt;&lt;A href="https://doc.arcgis.com/en/cityengine/latest/cga/cga-reset-geometry-operation.htm" target="_blank"&gt;https://doc.arcgis.com/en/cityengine/latest/cga/cga-reset-geometry-operation.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 12:57:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idc-p/1236323#M280</guid>
      <dc:creator>CherylLau</dc:creator>
      <dc:date>2022-11-30T12:57:27Z</dc:date>
    </item>
    <item>
      <title>Re: try: for cga</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idc-p/1236891#M281</link>
      <description>&lt;P&gt;HI , no unfortunately, it's impossible to catch those pure geometrical error at the moment, as I said derivation stops and leaves rule geometry -as is- as a terminal leaf. No matter what you code after. This is a very special tricky usecase, I should probably package an exemple.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Dec 2022 17:53:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idc-p/1236891#M281</guid>
      <dc:creator>romainjanil</dc:creator>
      <dc:date>2022-12-01T17:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: try: for cga - Status changed to: Under Consideration</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idc-p/1252766#M282</link>
      <description />
      <pubDate>Mon, 30 Jan 2023 07:27:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-ideas/try-for-cga/idc-p/1252766#M282</guid>
      <dc:creator>ChristianIten</dc:creator>
      <dc:date>2023-01-30T07:27:21Z</dc:date>
    </item>
  </channel>
</rss>

