<?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: Hillshade coming out pixelated after using the Mosaic to New Raster tool to merge DEM's in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270213#M67006</link>
    <description>&lt;P&gt;If the dems were side-by-side, they should have the same properties and you shouldn't have had to change any of the optional parameters... What were your too inputs?&lt;/P&gt;&lt;P&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/mosaic-to-new-raster.htm" target="_blank"&gt;Mosaic To New Raster (Data Management)—ArcGIS Pro | Documentation&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Mar 2023 03:01:02 GMT</pubDate>
    <dc:creator>DanPatterson</dc:creator>
    <dc:date>2023-03-22T03:01:02Z</dc:date>
    <item>
      <title>Hillshade coming out pixelated after using the Mosaic to New Raster tool to merge DEM's</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270197#M67000</link>
      <description>&lt;P&gt;I am trying to create a hillshade from&amp;nbsp; DEM datasets. When I run the hillshade tool on just one of the datasets, it turns out fine. But when I use the Mosaic to New Rater tool to merge 2 DEM datasets and then run the hillshade tool, it turns out super pixelated. I'm not sure what's causing this, and I've changed every resampling method that i can find to bilinear and I am stumped.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attached are the hillshade using a single DEM dataset, which turns out fine and the hillshade after merging the same exact DEM dataset with the one next to it for a larger area than the first.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Mar 2023 01:15:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270197#M67000</guid>
      <dc:creator>SeanM</dc:creator>
      <dc:date>2023-03-22T01:15:42Z</dc:date>
    </item>
    <item>
      <title>Re: Hillshade coming out pixelated after using the Mosaic to New Raster tool to merge DEM's</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270213#M67006</link>
      <description>&lt;P&gt;If the dems were side-by-side, they should have the same properties and you shouldn't have had to change any of the optional parameters... What were your too inputs?&lt;/P&gt;&lt;P&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/mosaic-to-new-raster.htm" target="_blank"&gt;Mosaic To New Raster (Data Management)—ArcGIS Pro | Documentation&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Mar 2023 03:01:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270213#M67006</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2023-03-22T03:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: Hillshade coming out pixelated after using the Mosaic to New Raster tool to merge DEM's</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270214#M67007</link>
      <description>&lt;P&gt;Here is the dems side by side, the reason I'm running the mosaic is because they both have a different min and max elevation so the symbolization isn't the same.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Mar 2023 03:09:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270214#M67007</guid>
      <dc:creator>SeanM</dc:creator>
      <dc:date>2023-03-22T03:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: Hillshade coming out pixelated after using the Mosaic to New Raster tool to merge DEM's</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270215#M67008</link>
      <description>&lt;P&gt;And the DEM looks fine after the mosaic (here it is clipped to my area of focus so its smaller), but the hillshade is what turns out bad.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Mar 2023 03:12:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1270215#M67008</guid>
      <dc:creator>SeanM</dc:creator>
      <dc:date>2023-03-22T03:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: Hillshade coming out pixelated after using the Mosaic to New Raster tool to merge DEM's</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1311511#M71398</link>
      <description>&lt;P&gt;I just had the exact same problem and eventually figured it out. When you run the Mosaic to New Raster tool, make sure you select one of the "float" pixel types, otherwise the pixel values in the mosaic will all be converted to integers, which will result in the pixelated/contoured hillshade effect. ESRI's "&lt;A href="https://nps.maps.arcgis.com/home/item.html?id=3cedfc19d7b941d89ee15b0e2f454070" target="_self"&gt;Terrain: Multi-Directional Hillshade&lt;/A&gt;" layer from the Living Atlas is another option.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 14:16:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/hillshade-coming-out-pixelated-after-using-the/m-p/1311511#M71398</guid>
      <dc:creator>EvanR</dc:creator>
      <dc:date>2023-07-25T14:16:28Z</dc:date>
    </item>
  </channel>
</rss>

