<?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 Can We Change Default Re-Sampling For Rasters? in Elevation Data Questions</title>
    <link>https://community.esri.com/t5/elevation-data-questions/can-we-change-default-re-sampling-for-rasters/m-p/870933#M181</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The default or first option for any raster re-sampling / re-projection geoprocessing tools is "nearest neighbor". This re-sampling algorithm is explicitly for integer or categorical data. The other two options are for continuous data and represent interpolation schemes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because "nearest neighbor" is the default re-sampling algorithm, when re-sampling or re-projecting a continuous data raster, numerical artifacts are introduced.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I work with continuous data almost explicitly (digital elevation models, hydrologic/snow data, etc). I also teach undergrads GIS. I have been teaching them about the difference in these re-sampling algorithms. However, having to choose an appropriate interpolation scheme for re-sampling continuous data (bilinear or cubic), but it is often a step that is neglected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can ESRI change the default re-sampling algorithm to either bilinear or cubic?&amp;nbsp; OR can they add some sort of warning / prompt / flag on the geoprocessing tools that advises the user as to the appropriate sampling scheme?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know what you think!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joel Sholtes&lt;/P&gt;&lt;P&gt;Colorado Mesa University&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Dec 2019 18:49:40 GMT</pubDate>
    <dc:creator>JoelSholtes</dc:creator>
    <dc:date>2019-12-05T18:49:40Z</dc:date>
    <item>
      <title>Can We Change Default Re-Sampling For Rasters?</title>
      <link>https://community.esri.com/t5/elevation-data-questions/can-we-change-default-re-sampling-for-rasters/m-p/870933#M181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The default or first option for any raster re-sampling / re-projection geoprocessing tools is "nearest neighbor". This re-sampling algorithm is explicitly for integer or categorical data. The other two options are for continuous data and represent interpolation schemes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because "nearest neighbor" is the default re-sampling algorithm, when re-sampling or re-projecting a continuous data raster, numerical artifacts are introduced.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I work with continuous data almost explicitly (digital elevation models, hydrologic/snow data, etc). I also teach undergrads GIS. I have been teaching them about the difference in these re-sampling algorithms. However, having to choose an appropriate interpolation scheme for re-sampling continuous data (bilinear or cubic), but it is often a step that is neglected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can ESRI change the default re-sampling algorithm to either bilinear or cubic?&amp;nbsp; OR can they add some sort of warning / prompt / flag on the geoprocessing tools that advises the user as to the appropriate sampling scheme?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know what you think!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joel Sholtes&lt;/P&gt;&lt;P&gt;Colorado Mesa University&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Dec 2019 18:49:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/elevation-data-questions/can-we-change-default-re-sampling-for-rasters/m-p/870933#M181</guid>
      <dc:creator>JoelSholtes</dc:creator>
      <dc:date>2019-12-05T18:49:40Z</dc:date>
    </item>
  </channel>
</rss>

