<?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: Street Edge Detection in ArcGIS CityEngine Questions</title>
    <link>https://community.esri.com/t5/arcgis-cityengine-questions/street-edge-detection/m-p/212855#M2812</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I was dreading that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;CGA shape grammars are relatively well documented, but my experience with Python integration is not... great.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Not to mention my complete role as a naif re python. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks, anyway, for the swift reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;EDIT: &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheap cludge, but occlusion checks on all works relatively neatly. Thanks! Red faces will be used to spawn assets....&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[ATTACH=CONFIG]28361[/ATTACH]&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Oct 2013 08:18:44 GMT</pubDate>
    <dc:creator>TomMorgan</dc:creator>
    <dc:date>2013-10-16T08:18:44Z</dc:date>
    <item>
      <title>Street Edge Detection</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-questions/street-edge-detection/m-p/212853#M2810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Is there a simple way to detect the presence of an adjacent block from a street shape?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To clarify, this is distinct from finding street.front in a generated block/lot. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;An example would involve instancing a different set of geometries onto street surfaces that are adjacent to lots on &lt;/SPAN&gt;&lt;STRONG&gt;both &lt;/STRONG&gt;&lt;SPAN&gt;sides as opposed to those that only share one edge with a generated lot.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;(In this case, the orange area is NOT a generated lot...)&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Oct 2013 05:58:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-questions/street-edge-detection/m-p/212853#M2810</guid>
      <dc:creator>TomMorgan</dc:creator>
      <dc:date>2013-10-16T05:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: Street Edge Detection</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-questions/street-edge-detection/m-p/212854#M2811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;On the CGA side of things, I'd say occlusion queries.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But since ( and this is a crucial fact ) CGA starts operating on all shapes as they exist. CGA can not (yet) change shapes or query neighboring shapes or such --&amp;gt; a shapes needs to be given with a set of attributes, that's the base for CGA model generation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;--&amp;gt; in your case, maybe the best choice would be to write a python script to do these things or to pre-process the data within ArcGIS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Let me know.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Matt&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Oct 2013 07:18:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-questions/street-edge-detection/m-p/212854#M2811</guid>
      <dc:creator>MatthiasBuehler1</dc:creator>
      <dc:date>2013-10-16T07:18:28Z</dc:date>
    </item>
    <item>
      <title>Re: Street Edge Detection</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-questions/street-edge-detection/m-p/212855#M2812</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I was dreading that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;CGA shape grammars are relatively well documented, but my experience with Python integration is not... great.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Not to mention my complete role as a naif re python. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks, anyway, for the swift reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;EDIT: &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheap cludge, but occlusion checks on all works relatively neatly. Thanks! Red faces will be used to spawn assets....&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[ATTACH=CONFIG]28361[/ATTACH]&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Oct 2013 08:18:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-questions/street-edge-detection/m-p/212855#M2812</guid>
      <dc:creator>TomMorgan</dc:creator>
      <dc:date>2013-10-16T08:18:44Z</dc:date>
    </item>
  </channel>
</rss>

