<?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: Problems using path distance tool in ArcGIS Spatial Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512631#M7358</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt; I've tried to construct a cost surface based on slope, but I haven't been able to figure out how to do it so it takes into account the direction of travel. I need it to do so because there are different costs to going up and to going down a particular slope degree.Is there any way to calculate slope relative to a starting point other than the path distance tool?&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The path distance tool does do this complex analysis I'd maybe go back and check the inputs you are giving the tool in terms of units and such.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would also give very high-slope areas an additionally high general (nondirectional) cost as travel is difficult on a steep slope no matter what direction you are going.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Units are a huge thing to worry about here because your x y and z units need to be the same (or differences accounted for) and your costs need to be scaled in a way that doesn't overcome the topographic costs pathdistance is modeling.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Apr 2013 04:04:54 GMT</pubDate>
    <dc:creator>curtvprice</dc:creator>
    <dc:date>2013-04-05T04:04:54Z</dc:date>
    <item>
      <title>Problems using path distance tool</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512628#M7355</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi all,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've been trying to use the path distance tool (ArcGIS 10) in order to delineate a 2 hour walking distance around archaeological sites.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm trying to model the calculation in a way that will take into account the changing slope in the area.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After consulting the forums and past posts, I'm using the following inputs:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1. a shapefile with the site's location&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. a DEM (floating, 32 bit) of topography, cell size=25m, as a surface raster&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. the same DEM as the vertical factor surface&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4. a vertical factor table (created by Nico Tripcevich based on Tobler's hiking function, discussed here &lt;/SPAN&gt;&lt;A href="http://forums.esri.com/Thread.asp?c=93&amp;amp;f=995&amp;amp;t=138683"&gt;http://forums.esri.com/Thread.asp?c=93&amp;amp;f=995&amp;amp;t=138683&lt;/A&gt;&lt;SPAN&gt;, among other places).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;the results I'm getting do not seem to be reasonable; it seems that the DEM has no effect, as I'm getting a very much circular pattern even when a site is located within a steep valley (in such a case I would expect a more elongated radius, following the valley route).&amp;nbsp; I've tried running the tool without the vertical factor, and indeed I'm getting a spider-web-like result, with the cost just increasing with distance in straight lines... this again makes me think that for some reason the tool isn't taking the DEM into account.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've been going almost crazy trying to solve this... any ideas?? I don't know if there's something I'm not doing properly, or if there's a problem with the tool itself...&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Michal&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Apr 2013 19:57:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512628#M7355</guid>
      <dc:creator>MichalBirkenfeld</dc:creator>
      <dc:date>2013-04-03T19:57:35Z</dc:date>
    </item>
    <item>
      <title>Re: Problems using path distance tool</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512629#M7356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I don't have an answer, but some guidance based on experience:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The place to focus your attention is the cost raster. If you can solve that problem and get cost values that make sense, you will be 95% of the way there.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 03:21:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512629#M7356</guid>
      <dc:creator>curtvprice</dc:creator>
      <dc:date>2013-04-04T03:21:04Z</dc:date>
    </item>
    <item>
      <title>Re: Problems using path distance tool</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512630#M7357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Curtis, thanks for the advice.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I've tried to construct a cost surface based on slope, but I haven't been able to figure out how to do it so it takes into account the direction of travel. I need it to do so because there are different costs to going up and to going down a particular slope degree.Is there any way to calculate slope relative to a starting point other than the path distance tool?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks again&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Michal&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 08:57:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512630#M7357</guid>
      <dc:creator>MichalBirkenfeld</dc:creator>
      <dc:date>2013-04-04T08:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: Problems using path distance tool</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512631#M7358</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt; I've tried to construct a cost surface based on slope, but I haven't been able to figure out how to do it so it takes into account the direction of travel. I need it to do so because there are different costs to going up and to going down a particular slope degree.Is there any way to calculate slope relative to a starting point other than the path distance tool?&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The path distance tool does do this complex analysis I'd maybe go back and check the inputs you are giving the tool in terms of units and such.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would also give very high-slope areas an additionally high general (nondirectional) cost as travel is difficult on a steep slope no matter what direction you are going.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Units are a huge thing to worry about here because your x y and z units need to be the same (or differences accounted for) and your costs need to be scaled in a way that doesn't overcome the topographic costs pathdistance is modeling.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Apr 2013 04:04:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/problems-using-path-distance-tool/m-p/512631#M7358</guid>
      <dc:creator>curtvprice</dc:creator>
      <dc:date>2013-04-05T04:04:54Z</dc:date>
    </item>
  </channel>
</rss>

