<?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: Intersect - false order attribute table! in ArcGIS Online Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-questions/intersect-false-order-attribute-table/m-p/179267#M8798</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have found a solution to my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, the command "Create Routes" requires a corner for the beginning of a route (Coordinae Priority), although it should be an optional subroutine. If you have several terrain cuts from different directions (e.g. corner up/left to down/right and vice versa) you have to take into account that the output values in the table will also be reversed.&lt;BR /&gt;Someone might have a solution that it always works no matter how the terrain cut is applied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope the next one will have to think less than I did.&lt;/P&gt;&lt;P&gt;&lt;IMG alt="ArcGIS ModellBuilder solution" class="image-1 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/488319_ModelBuilder.jpg" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 12 Apr 2020 18:42:18 GMT</pubDate>
    <dc:creator>GerritKopmann</dc:creator>
    <dc:date>2020-04-12T18:42:18Z</dc:date>
    <item>
      <title>Intersect - false order attribute table!</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/intersect-false-order-attribute-table/m-p/179265#M8796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I figured out that "Intersect" doesn't work that well!? I use the command to extract data of a 2D mesh for elivation data and the 2D runoff results (water surface level) with a line feature (terrain section). The command doesn't put the parts of the seperatet lines not in the rigth order at the attribute table (see picture).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has someone a solution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I like to export the data later with "Export Feature Attribute to ASCII" to create my own grafics.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Gerrit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Apr 2020 13:41:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/intersect-false-order-attribute-table/m-p/179265#M8796</guid>
      <dc:creator>GerritKopmann</dc:creator>
      <dc:date>2020-04-10T13:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: Intersect - false order attribute table!</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/intersect-false-order-attribute-table/m-p/179266#M8797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Addendum:&lt;/P&gt;&lt;P&gt;The Intersect command intersects 2D meshes and line features based on the ID of the 2D mesh! Small ID's are first intersected with the line! &lt;BR /&gt;There is probably no setting for Intersect to follow the course of the line feature? Is there a command to re-sort the line parts later?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Apr 2020 14:58:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/intersect-false-order-attribute-table/m-p/179266#M8797</guid>
      <dc:creator>GerritKopmann</dc:creator>
      <dc:date>2020-04-10T14:58:02Z</dc:date>
    </item>
    <item>
      <title>Re: Intersect - false order attribute table!</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/intersect-false-order-attribute-table/m-p/179267#M8798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have found a solution to my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, the command "Create Routes" requires a corner for the beginning of a route (Coordinae Priority), although it should be an optional subroutine. If you have several terrain cuts from different directions (e.g. corner up/left to down/right and vice versa) you have to take into account that the output values in the table will also be reversed.&lt;BR /&gt;Someone might have a solution that it always works no matter how the terrain cut is applied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope the next one will have to think less than I did.&lt;/P&gt;&lt;P&gt;&lt;IMG alt="ArcGIS ModellBuilder solution" class="image-1 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/488319_ModelBuilder.jpg" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Apr 2020 18:42:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/intersect-false-order-attribute-table/m-p/179267#M8798</guid>
      <dc:creator>GerritKopmann</dc:creator>
      <dc:date>2020-04-12T18:42:18Z</dc:date>
    </item>
  </channel>
</rss>

