<?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 NAServer/Route: Separate Line into Polyline in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/naserver-route-separate-line-into-polyline/idi-p/945400</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;If setting returnRoutes=true in the response if the "NAServer/Route" operation only one Line Geometry&amp;nbsp;comes back for the whole route, even though the returned JSON object is a Polyline. In other words: W&lt;/SPAN&gt;&lt;SPAN&gt;e get an array of lines&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;that always contains&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;only one line. &lt;BR /&gt;&lt;STRONG&gt;I'm suggesting that this&amp;nbsp;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;STRONG&gt;should be separated into sections between stops (or the directions segments as uncompressed geometry) by the NAServer.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Use case for this is that only a section between two stops is supposed to be drawn. If you want to do that with the JS API, you currently need to iterate&amp;nbsp;through the segments (in&amp;nbsp;&lt;/SPAN&gt;&lt;CODE style="border: 0px; font-weight: inherit;"&gt;routeResults&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;.&lt;/SPAN&gt;result&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;.&lt;/SPAN&gt;routeResults&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;[&lt;/SPAN&gt;&lt;SPAN class="" style="color: #990000; border: 0px; font-weight: inherit;"&gt;0&lt;/SPAN&gt;&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;]&lt;/SPAN&gt;&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;.&lt;/SPAN&gt;directions&lt;/CODE&gt;&lt;SPAN&gt;) while looking&amp;nbsp;&lt;SPAN style="background-color: #ffffff;"&gt;for&amp;nbsp;the "esriDMTDepart"&amp;nbsp;direction where the section starts and "esriDMTStop" where it ends, then&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;decode the compressedGeometries, combine all segments from one stop to the next and draw the line&lt;/SPAN&gt;&lt;SPAN&gt;. I&lt;/SPAN&gt;&lt;SPAN&gt;t's&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;possible&lt;SPAN&gt;&amp;nbsp;but ugly, from a development point of view&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Aug 2017 09:20:18 GMT</pubDate>
    <dc:creator>NiklasKöhn</dc:creator>
    <dc:date>2017-08-18T09:20:18Z</dc:date>
    <item>
      <title>NAServer/Route: Separate Line into Polyline</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/naserver-route-separate-line-into-polyline/idi-p/945400</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;If setting returnRoutes=true in the response if the "NAServer/Route" operation only one Line Geometry&amp;nbsp;comes back for the whole route, even though the returned JSON object is a Polyline. In other words: W&lt;/SPAN&gt;&lt;SPAN&gt;e get an array of lines&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;that always contains&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;only one line. &lt;BR /&gt;&lt;STRONG&gt;I'm suggesting that this&amp;nbsp;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;STRONG&gt;should be separated into sections between stops (or the directions segments as uncompressed geometry) by the NAServer.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Use case for this is that only a section between two stops is supposed to be drawn. If you want to do that with the JS API, you currently need to iterate&amp;nbsp;through the segments (in&amp;nbsp;&lt;/SPAN&gt;&lt;CODE style="border: 0px; font-weight: inherit;"&gt;routeResults&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;.&lt;/SPAN&gt;result&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;.&lt;/SPAN&gt;routeResults&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;[&lt;/SPAN&gt;&lt;SPAN class="" style="color: #990000; border: 0px; font-weight: inherit;"&gt;0&lt;/SPAN&gt;&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;]&lt;/SPAN&gt;&lt;SPAN class="" style="color: #999999; border: 0px; font-weight: inherit;"&gt;.&lt;/SPAN&gt;directions&lt;/CODE&gt;&lt;SPAN&gt;) while looking&amp;nbsp;&lt;SPAN style="background-color: #ffffff;"&gt;for&amp;nbsp;the "esriDMTDepart"&amp;nbsp;direction where the section starts and "esriDMTStop" where it ends, then&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;decode the compressedGeometries, combine all segments from one stop to the next and draw the line&lt;/SPAN&gt;&lt;SPAN&gt;. I&lt;/SPAN&gt;&lt;SPAN&gt;t's&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;possible&lt;SPAN&gt;&amp;nbsp;but ugly, from a development point of view&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 09:20:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/naserver-route-separate-line-into-polyline/idi-p/945400</guid>
      <dc:creator>NiklasKöhn</dc:creator>
      <dc:date>2017-08-18T09:20:18Z</dc:date>
    </item>
  </channel>
</rss>

