<?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 Unexpected values when extracting values to points with slope function applied to Terrain Image Service in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/unexpected-values-when-extracting-values-to-points/m-p/378660#M16682</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am testing out various methods for extracting values from raster datasets to points as a demonstration to my students of various surface analysis workflows.&amp;nbsp; This example in particular is extracting slope (degrees) values.&lt;/P&gt;&lt;P&gt;Here are the methods I'm using:&lt;/P&gt;&lt;P&gt;Traditional/local data:&amp;nbsp; Use GP tools to derive a slope raster from a local elevation dataset, then extract the values to points (works as expected).&lt;/P&gt;&lt;P&gt;Local data/raster functions:&amp;nbsp; Use the slope raster function on the local DEM, extract values to points (works as expected).&lt;/P&gt;&lt;P&gt;Terrain (Slope in Degrees) Image service:&amp;nbsp; Extract slope values from the Image service.&amp;nbsp; The values are integer, which is fine, and the results are comparable to the traditional methods (works as expected).&lt;/P&gt;&lt;P&gt;Terrain Image Service with slope raster function:&amp;nbsp; I apply the slope raster function to the Terrain Image Service, then extract the values to points...This returns slope values that are much greater than expected (ex. expected value of 4 deg, but a returned value of 23 deg) and I can't figure out the reason why.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I suspect this may be related to the display scale of the terrain image service, but I can't seem to find out why in order to fix the workflow on my end.&amp;nbsp; My biggest concern is that my students (or I) will end up with erroneous data by incorrectly using this method in the future.&amp;nbsp; I need to better understand what's going on under the hood to avoid potential pit-falls.&lt;/P&gt;&lt;P&gt;As a side note, I ran the 'Difference' process tool/function on the correct slope dataset and the incorrect one and the results were zero, indicating to me that the correct values are in there somewhere.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Using ArcGIS Pro 2.3.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Mar 2019 17:48:01 GMT</pubDate>
    <dc:creator>JonathanFleming</dc:creator>
    <dc:date>2019-03-27T17:48:01Z</dc:date>
    <item>
      <title>Unexpected values when extracting values to points with slope function applied to Terrain Image Service</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/unexpected-values-when-extracting-values-to-points/m-p/378660#M16682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am testing out various methods for extracting values from raster datasets to points as a demonstration to my students of various surface analysis workflows.&amp;nbsp; This example in particular is extracting slope (degrees) values.&lt;/P&gt;&lt;P&gt;Here are the methods I'm using:&lt;/P&gt;&lt;P&gt;Traditional/local data:&amp;nbsp; Use GP tools to derive a slope raster from a local elevation dataset, then extract the values to points (works as expected).&lt;/P&gt;&lt;P&gt;Local data/raster functions:&amp;nbsp; Use the slope raster function on the local DEM, extract values to points (works as expected).&lt;/P&gt;&lt;P&gt;Terrain (Slope in Degrees) Image service:&amp;nbsp; Extract slope values from the Image service.&amp;nbsp; The values are integer, which is fine, and the results are comparable to the traditional methods (works as expected).&lt;/P&gt;&lt;P&gt;Terrain Image Service with slope raster function:&amp;nbsp; I apply the slope raster function to the Terrain Image Service, then extract the values to points...This returns slope values that are much greater than expected (ex. expected value of 4 deg, but a returned value of 23 deg) and I can't figure out the reason why.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I suspect this may be related to the display scale of the terrain image service, but I can't seem to find out why in order to fix the workflow on my end.&amp;nbsp; My biggest concern is that my students (or I) will end up with erroneous data by incorrectly using this method in the future.&amp;nbsp; I need to better understand what's going on under the hood to avoid potential pit-falls.&lt;/P&gt;&lt;P&gt;As a side note, I ran the 'Difference' process tool/function on the correct slope dataset and the incorrect one and the results were zero, indicating to me that the correct values are in there somewhere.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Using ArcGIS Pro 2.3.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Mar 2019 17:48:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/unexpected-values-when-extracting-values-to-points/m-p/378660#M16682</guid>
      <dc:creator>JonathanFleming</dc:creator>
      <dc:date>2019-03-27T17:48:01Z</dc:date>
    </item>
  </channel>
</rss>

