<?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 Line Barrier Costs from External Geometry in ArcGIS Network Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-network-analyst-questions/line-barrier-costs-from-external-geometry/m-p/573328#M5509</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am playing around with Line Barrier - Scaled Costs based on an external set of geometry.&amp;nbsp; I have the base road data with costs in minutes and the barrier I am adding is scenic byways (road that are fun to drive on). &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I loaded byway data via 'Load Locations' and use the Geometry as the 'Location Position'.&amp;nbsp; I expected that it would snap to the street data but it doesn't. Therefore because the byway data isn't coincident with the street data the route analysis essentially ignores it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am able to select roads from the street data (ones that are on scenic byways) and the load those into the line barriers and get expected results.&amp;nbsp; I can also add a buffer of the byway data and use that as a polygon barrier and get expected results. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas on the simplest way to do this? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think buffer is straight forward, and probably most accurately reflects the physical phenomena. It would tag some side roads, but I would expect those roads to be somewhat scenic also. Does the polygon come at a much higher computational cost?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;George&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Apr 2011 16:17:30 GMT</pubDate>
    <dc:creator>GeorgeNewbury</dc:creator>
    <dc:date>2011-04-08T16:17:30Z</dc:date>
    <item>
      <title>Line Barrier Costs from External Geometry</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/line-barrier-costs-from-external-geometry/m-p/573328#M5509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am playing around with Line Barrier - Scaled Costs based on an external set of geometry.&amp;nbsp; I have the base road data with costs in minutes and the barrier I am adding is scenic byways (road that are fun to drive on). &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I loaded byway data via 'Load Locations' and use the Geometry as the 'Location Position'.&amp;nbsp; I expected that it would snap to the street data but it doesn't. Therefore because the byway data isn't coincident with the street data the route analysis essentially ignores it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am able to select roads from the street data (ones that are on scenic byways) and the load those into the line barriers and get expected results.&amp;nbsp; I can also add a buffer of the byway data and use that as a polygon barrier and get expected results. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas on the simplest way to do this? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think buffer is straight forward, and probably most accurately reflects the physical phenomena. It would tag some side roads, but I would expect those roads to be somewhat scenic also. Does the polygon come at a much higher computational cost?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;George&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2011 16:17:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/line-barrier-costs-from-external-geometry/m-p/573328#M5509</guid>
      <dc:creator>GeorgeNewbury</dc:creator>
      <dc:date>2011-04-08T16:17:30Z</dc:date>
    </item>
  </channel>
</rss>

