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) 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). 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.
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?