<?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 Redesign Subregion Functionality en Revit Ideas</title>
    <link>https://forums.autodesk.com/t5/revit-ideas/redesign-subregion-functionality/idi-p/11658151</link>
    <description>&lt;P&gt;Today was my first attempt at creating subregions on a topo surface. I was attempting to trace out roads, forest extents, and fields from a satellite topo so there was no model geometry to pick out region boundaries. I was shocked by how poor the current procedure is to define subregions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Each boundary has to be drawn twice, and the slightest overlap of these duplicate boundaries is rewarded with a "subregions cannot intersect" error. With a properly designed UI, this error would be impossible to generate. Instead of expecting users to tediously outline each subregion, the UI should simply accept a sketch of proposed boundaries. To the extent the user drawn boundaries form closed loops, subregions would be created from the boundary lines.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jan 2023 01:32:39 GMT</pubDate>
    <dc:creator>scenesketcher</dc:creator>
    <dc:date>2023-01-05T01:32:39Z</dc:date>
    <item>
      <title>Redesign Subregion Functionality</title>
      <link>https://forums.autodesk.com/t5/revit-ideas/redesign-subregion-functionality/idi-p/11658151</link>
      <description>&lt;P&gt;Today was my first attempt at creating subregions on a topo surface. I was attempting to trace out roads, forest extents, and fields from a satellite topo so there was no model geometry to pick out region boundaries. I was shocked by how poor the current procedure is to define subregions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Each boundary has to be drawn twice, and the slightest overlap of these duplicate boundaries is rewarded with a "subregions cannot intersect" error. With a properly designed UI, this error would be impossible to generate. Instead of expecting users to tediously outline each subregion, the UI should simply accept a sketch of proposed boundaries. To the extent the user drawn boundaries form closed loops, subregions would be created from the boundary lines.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jan 2023 01:32:39 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-ideas/redesign-subregion-functionality/idi-p/11658151</guid>
      <dc:creator>scenesketcher</dc:creator>
      <dc:date>2023-01-05T01:32:39Z</dc:date>
    </item>
    <item>
      <title>Re: Redesign Subregion Functionality</title>
      <link>https://forums.autodesk.com/t5/revit-ideas/redesign-subregion-functionality/idc-p/11923311#M51324</link>
      <description>&lt;P&gt;We use subregions extensively to delineate features on a site model, and the overlapping subregion error is a major obstacle because many of the subregions share complex borders that can easily overlap by tiny amounts.&amp;nbsp; We would really appreciate an automated procedure to resolve overlaps, e.g. "Subregions overlap.&amp;nbsp; Resolve overlaps (yes/no)?"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 13:56:35 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-ideas/redesign-subregion-functionality/idc-p/11923311#M51324</guid>
      <dc:creator>ellison</dc:creator>
      <dc:date>2023-04-26T13:56:35Z</dc:date>
    </item>
  </channel>
</rss>

