<?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: Pathdistance problem in ArcGIS Spatial Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/pathdistance-problem/m-p/487883#M6988</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks for your interest in my question. I am implementing Tobler's hiking function using the vertical factor table created by Nico Tripcevich, something I first did in the mid-1990s in Arc/Info using a 30-m DEM (output attached). I wanted to update that earlier analysis using a 10-m DEM and with the full anisotropic implementation that I couldn't figure out how to do 15 years ago. I'm attaching an image of the base DEM, as well as a larger image of the whole 10-m cost-surface showing the "holes"/"ridges" I refer to -- if I try to generate cost-paths away from the cyan dot to, e.g., a point on the north end of my cost-surface, ArcGIS creates short cost-paths from the center of each "hole" to the nearby ridges (no image available at the moment), and does not connect my source with destinations; i.e., there's no way "around" the ridges.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Aug 2010 13:54:13 GMT</pubDate>
    <dc:creator>JohnKantner</dc:creator>
    <dc:date>2010-08-17T13:54:13Z</dc:date>
    <item>
      <title>Pathdistance problem</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/pathdistance-problem/m-p/487882#M6987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm trying to use Pathdistance and a custom vertical factor table to create a cumulative cost-surface that represents travel time away from the source point. It works just fine with a 30-m DEM and/or a small extent, but if I try a large 10-m DEM, I get "holes" and "ridges" in the resulting cost-surface in which the accumulated cost begins to decrease as you move away from the source -- and then starts to increase again. See attached image for an example (blue point is source; note decreasing accumulated cost to west).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've tried all kinds of trouble-shooting -- rebuilding the DEM, reprojecting it, using source from a raster, using source from a shapefile -- all to no avail. I suspect there must be computational limitations in Pathdistance??&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;All thoughts on this welcome!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Aug 2010 17:59:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/pathdistance-problem/m-p/487882#M6987</guid>
      <dc:creator>JohnKantner</dc:creator>
      <dc:date>2010-08-16T17:59:35Z</dc:date>
    </item>
    <item>
      <title>Re: Pathdistance problem</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/pathdistance-problem/m-p/487883#M6988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks for your interest in my question. I am implementing Tobler's hiking function using the vertical factor table created by Nico Tripcevich, something I first did in the mid-1990s in Arc/Info using a 30-m DEM (output attached). I wanted to update that earlier analysis using a 10-m DEM and with the full anisotropic implementation that I couldn't figure out how to do 15 years ago. I'm attaching an image of the base DEM, as well as a larger image of the whole 10-m cost-surface showing the "holes"/"ridges" I refer to -- if I try to generate cost-paths away from the cyan dot to, e.g., a point on the north end of my cost-surface, ArcGIS creates short cost-paths from the center of each "hole" to the nearby ridges (no image available at the moment), and does not connect my source with destinations; i.e., there's no way "around" the ridges.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Aug 2010 13:54:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/pathdistance-problem/m-p/487883#M6988</guid>
      <dc:creator>JohnKantner</dc:creator>
      <dc:date>2010-08-17T13:54:13Z</dc:date>
    </item>
    <item>
      <title>Re: Pathdistance problem</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/pathdistance-problem/m-p/487884#M6989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Sorry for not providing more detail earlier. Pathdist.pdf is a large region of New Mexico where I do my work as an archaeologist. All of the other maps are smaller sections from the southeastern corner of the larger map, and the dots are archaeological sites. The problem is when I try to implement Tobler's hiking function in Pathdistance using the vertical factor table that Nico Tripcevich generated from Tobler's formula (see &amp;lt;&lt;/SPAN&gt;&lt;A href="http://mapaspects.org/courses/gis-and-anthropology/workshop-2009-viewshed-and-cost-distance/ii-cost-distance-2009"&gt;his page here&lt;/A&gt;&lt;SPAN&gt;&amp;gt;. It works just fine with a 30m DEM, but at at 10m, I get the results seen in pathdist.pdf. The Pathdistance implementation is pretty basic, using a DEM as input with no additional friction surface beyond the vertical factor table. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Your suggestion to try a simpler landscape is a good one, and I'll try that next. Thanks for the advice...&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Aug 2010 20:53:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/pathdistance-problem/m-p/487884#M6989</guid>
      <dc:creator>JohnKantner</dc:creator>
      <dc:date>2010-08-19T20:53:44Z</dc:date>
    </item>
  </channel>
</rss>

