<?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: Migrating Terrain ISDEF to Mosaic Dataset (where has pixeltype=Elevation gone?) in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/migrating-terrain-isdef-to-mosaic-dataset-where/m-p/423215#M24164</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;According to the help page Catalog will choose the bit depth based on the first image it finds.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I have found, and what I can only think is a bug, is that this functionality works for me (I get an image)&amp;nbsp; if I invoke the AddRasters tool with the RPDefs (but not if I use the ISDef file).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regarding the second part of migration, it appears as though you do have to add the hillshade function manually yourself (i.e. the AddRasters tool will not do it for you).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What would have been nice is an all-encompassing ISDef-to-MosaicDataset tool.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 12 Sep 2011 18:02:24 GMT</pubDate>
    <dc:creator>philippenn</dc:creator>
    <dc:date>2011-09-12T18:02:24Z</dc:date>
    <item>
      <title>Migrating Terrain ISDEF to Mosaic Dataset (where has pixeltype=Elevation gone?)</title>
      <link>https://community.esri.com/t5/data-management-questions/migrating-terrain-isdef-to-mosaic-dataset-where/m-p/423213#M24162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I've happily migrated some Aerial photography ISDEFs to Mosaic Datasets but am having an issue with migrating ISDEFs with elevation rasters. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm able to successfully run the AddRasters tool but I get a blank image when it comes to visualizing the dataset image (footprint/boundary are fine).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In ImageServer there was a pixeltype = Elevation value, but in the Create Mosaic Dataset tool there is no such equivalent. I tried the default (8bit) and 32_bit_float but to no avail. Also, the ImageServer definition just says Bit Depth 32, not whether floating/signed/unsigned.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The ISDEF also has a serviceprocess visualizing the elevation as Shaded Relief. I'm hoping that migration carries that sort of property across, but do not see any functions added in the mosaic dataset after importing the ISDEF rasters. Does that kind of process have to be manually recreated as a function within the new mosaic dataset or does it get imported?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;TIA,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Phil&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Sep 2011 15:59:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/migrating-terrain-isdef-to-mosaic-dataset-where/m-p/423213#M24162</guid>
      <dc:creator>philippenn</dc:creator>
      <dc:date>2011-09-12T15:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating Terrain ISDEF to Mosaic Dataset (where has pixeltype=Elevation gone?)</title>
      <link>https://community.esri.com/t5/data-management-questions/migrating-terrain-isdef-to-mosaic-dataset-where/m-p/423214#M24163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;When creating the mosaic dataset you will need to change the Pixel Properties to 1 band and the Pixel type to match the data you are using.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00170000008n000000"&gt;Create Mosaic Dataset (Data Management) &lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Sep 2011 16:27:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/migrating-terrain-isdef-to-mosaic-dataset-where/m-p/423214#M24163</guid>
      <dc:creator>TimothyHales</dc:creator>
      <dc:date>2011-09-12T16:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating Terrain ISDEF to Mosaic Dataset (where has pixeltype=Elevation gone?)</title>
      <link>https://community.esri.com/t5/data-management-questions/migrating-terrain-isdef-to-mosaic-dataset-where/m-p/423215#M24164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;According to the help page Catalog will choose the bit depth based on the first image it finds.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I have found, and what I can only think is a bug, is that this functionality works for me (I get an image)&amp;nbsp; if I invoke the AddRasters tool with the RPDefs (but not if I use the ISDef file).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regarding the second part of migration, it appears as though you do have to add the hillshade function manually yourself (i.e. the AddRasters tool will not do it for you).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What would have been nice is an all-encompassing ISDef-to-MosaicDataset tool.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Sep 2011 18:02:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/migrating-terrain-isdef-to-mosaic-dataset-where/m-p/423215#M24164</guid>
      <dc:creator>philippenn</dc:creator>
      <dc:date>2011-09-12T18:02:24Z</dc:date>
    </item>
  </channel>
</rss>

