<?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 Display cell size of an image cache in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/display-cell-size-of-an-image-cache/m-p/174810#M6928</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a number of image services which have caches created in either 10.2.1 or 10.3 (our servers are currently 10.3)&amp;nbsp; For all of our 1-meter imagery, the dynamic data displays with the correct Cell Size under the Source tab in Properties. Our caches (default AGOL/Google levels) were built to L17 (1.19 m cell size).&amp;nbsp; However, when I look at the properties for the cached service, the cell size under the Source tab reads ~0.2986 meters. Zooming in to a ridiculous scale and measuring an individual pixel confirms the size. Similar issues are found for any sub-meter imagery. I am having a hard time convincing my coworkers that I would not try to create cache tiles with a resolution that is better than the original raster data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have searched around for a couple of days for an answer, but have been unable to find anything. Why would the displayed cache tile pixel be almost one-quarter of the set pixel size? Am I overlooking something in the documentation for creating image caches?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Mar 2015 23:39:48 GMT</pubDate>
    <dc:creator>JamesMonty1</dc:creator>
    <dc:date>2015-03-03T23:39:48Z</dc:date>
    <item>
      <title>Display cell size of an image cache</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/display-cell-size-of-an-image-cache/m-p/174810#M6928</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a number of image services which have caches created in either 10.2.1 or 10.3 (our servers are currently 10.3)&amp;nbsp; For all of our 1-meter imagery, the dynamic data displays with the correct Cell Size under the Source tab in Properties. Our caches (default AGOL/Google levels) were built to L17 (1.19 m cell size).&amp;nbsp; However, when I look at the properties for the cached service, the cell size under the Source tab reads ~0.2986 meters. Zooming in to a ridiculous scale and measuring an individual pixel confirms the size. Similar issues are found for any sub-meter imagery. I am having a hard time convincing my coworkers that I would not try to create cache tiles with a resolution that is better than the original raster data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have searched around for a couple of days for an answer, but have been unable to find anything. Why would the displayed cache tile pixel be almost one-quarter of the set pixel size? Am I overlooking something in the documentation for creating image caches?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Mar 2015 23:39:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/display-cell-size-of-an-image-cache/m-p/174810#M6928</guid>
      <dc:creator>JamesMonty1</dc:creator>
      <dc:date>2015-03-03T23:39:48Z</dc:date>
    </item>
  </channel>
</rss>

