<?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: Need Help with analysis in ArcGIS Spatial Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/need-help-with-analysis/m-p/442331#M6257</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Greetings,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'd like to add one more thing aside from ensuring the x,y,z are all the same unit.&amp;nbsp; It is still technically possible to get slopes in excess of 100%, in particular if your data is in rugged terrain.&amp;nbsp; After all, a slope of 100% is equivalent to a 45 degree slope.&amp;nbsp; Knowing that degree slope ranges from 0 -90 (flat to vertical) we can easily infer slope can exceed 100%.&amp;nbsp; Our own graphics in the help system show a slope of 373% as an example output.&amp;nbsp; It may help if you review, &lt;/SPAN&gt;&lt;A href="http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/How_Slope_works/009z000000vz000000/"&gt;How Slope Works&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The reason your numbers are so high right now is because your dividing the rise (in feet/meters) by the run (in decimal degrees).&amp;nbsp; Essentially your denominator is a very small number compared to the rise value.&amp;nbsp; We also multiply the quotient by 100 making that large value even larger. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Eric&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 May 2012 20:15:23 GMT</pubDate>
    <dc:creator>EricRice</dc:creator>
    <dc:date>2012-05-18T20:15:23Z</dc:date>
    <item>
      <title>Need Help with analysis</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/need-help-with-analysis/m-p/442329#M6255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok, I am sure this has been asked but i cant seem to find the answer.&amp;nbsp; I need to create a "slope analysis" where i determine the slope percentage and classify by usability by a vehicle (1-5% flat to mild, unrestricted, 6-12% mildly restricted, etc) .&amp;nbsp; I am using NED 1/3 data from USGS.&amp;nbsp; I have run the "slope" tool a few times and used the "percent Rise" option and i get weird numbers like 1,219.&amp;nbsp; I thought this option would give me the percentages so I assumed 100% would be the greatest number.&amp;nbsp; I also used the degrees and i but i see that the slope is counted in degrees so percentage is out.&amp;nbsp; And maybe degrees makes more sense for this problem but I am not sure.&amp;nbsp; I am new with this type of analyis and have scoured the help functions and cannot seem to get an answer that helps.&amp;nbsp; Just so you (but you can probably tell) i am an occasional user and a novice.&amp;nbsp; Any help would be greatly appreciated.&amp;nbsp; Thanks.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 17:33:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/need-help-with-analysis/m-p/442329#M6255</guid>
      <dc:creator>GregSoviak</dc:creator>
      <dc:date>2012-05-18T17:33:58Z</dc:date>
    </item>
    <item>
      <title>Re: Need Help with analysis</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/need-help-with-analysis/m-p/442330#M6256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Project your data and ensure that you X, Y and Z values are in the same units (ie meters or feet), then run the slope tool.&amp;nbsp; You can't use decimal degree coordinates mixed in with elevations in other units.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 17:45:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/need-help-with-analysis/m-p/442330#M6256</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2012-05-18T17:45:20Z</dc:date>
    </item>
    <item>
      <title>Re: Need Help with analysis</title>
      <link>https://community.esri.com/t5/arcgis-spatial-analyst-questions/need-help-with-analysis/m-p/442331#M6257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Greetings,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'd like to add one more thing aside from ensuring the x,y,z are all the same unit.&amp;nbsp; It is still technically possible to get slopes in excess of 100%, in particular if your data is in rugged terrain.&amp;nbsp; After all, a slope of 100% is equivalent to a 45 degree slope.&amp;nbsp; Knowing that degree slope ranges from 0 -90 (flat to vertical) we can easily infer slope can exceed 100%.&amp;nbsp; Our own graphics in the help system show a slope of 373% as an example output.&amp;nbsp; It may help if you review, &lt;/SPAN&gt;&lt;A href="http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/How_Slope_works/009z000000vz000000/"&gt;How Slope Works&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The reason your numbers are so high right now is because your dividing the rise (in feet/meters) by the run (in decimal degrees).&amp;nbsp; Essentially your denominator is a very small number compared to the rise value.&amp;nbsp; We also multiply the quotient by 100 making that large value even larger. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Eric&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 20:15:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-spatial-analyst-questions/need-help-with-analysis/m-p/442331#M6257</guid>
      <dc:creator>EricRice</dc:creator>
      <dc:date>2012-05-18T20:15:23Z</dc:date>
    </item>
  </channel>
</rss>

