We build and update image cache for a map service.
At some stage, it started to produce gaps (bundles with complete/partially no data) in an updated cache by AOI polygon. Not every time the gap is the same area of AOI.
We compare two counting machine: Local (physical machine) and virtual box.
While we can "fix" the issue on the local machine it is no way to produce good update on the virtual box.
Let’s compare runs on the same AOI.
95% (means 15)
95% (means 23) /or other run 15
Remote AOI layer
Local (D:\) cache folder
Local (D:\) input mosaic
Windows Server 2016
Levels try to build (in one run)
Gaps on levels (as a result of run for 12-20 Levels)
Repaired by one run per level, 12 Level
Repaired by one run per level, 13 Level
Repaired by one run per level, 17 Level
What makes a trouble?
What else can we compare in order to get closer to a solution?
Desktop 10.5.1. Manage Tile Cache GP. The mosaic had been created in 10.3, then upgraded to 10.5.1
Any help please.
I am having the same issue in 10.5 building imagery cache and was wondering if you were ever able to figure this out. The last time I updated our imagery caches it was done in 10.2.1 and did not have any issues.
It caches fine for the scales 1:4,622,324 down to 1:18,055 but starting with 1:9,027 down to 1:2,256 it starts to leave gaps and does not give an error at all.
First, we have analysed the overviews, found and removed empty records. It helped for some gaps.
Next, we have removed all overviews. It completely fixed the gaps. When you remove overviews you should change MaxPS values for source raster (category 1)
Note that a number of improvements and fixes related to caching have gone into 'Manage Tile Cache' in version 10.6 (& Pro 2.1). I would suggest you try using these. They will be out later this week.
Concerning the requirement for overviews. Note that the tool has a "Maximum Source Cell Size" parameter. Lets say you have imagery at 1m resolution you can set the value to 1.5m and for all levels with pixels sizes larger (Ie levels <=16) the levels imagery will be generated by sampling the higher level and so overviews are not required. Use of this parameter depends on the content of the mosaic dataset. If the data is all from one source you may want to not bother creating overviews (to just cache), but use suitably small 'Maximum Source Cell Size'. If you have a mosaic dataset with multiple sources at different resolutions then you might set this value much larger or exclude.
When you refer to "Maximum Source Cell Size" and we are using a mosaic dataset, does this refer to the image cell size or the MinPS/LowPS in the footprint table?
I'm referring here to the "Maximum Source Cell Size" parameter that is part of 'Manage Tile Cache' GPTool. This parameters should be set based on which output levels you want to created by reading the mosaic dataset and which levels you want created by resampling the higher resolution levels in the cache. Has nothing really do to with the Pixelsize values in the mosaic dataset. Lets say you have imagery in a mosaic dataset that contains NAIP imagery as 1m and Landsat imagery at 15m. If you set "Maximum Source Cell Size" at 2m then you will get a tile cache that at all scales shows NAIP. If you set the value to greater than 15m you will find that the lower levels (resolution) will contain Landsat Imagery.
Did you build a new cache at 10.5.1 or migrate the cache from 10.3? I would suggest rebuilding the cache from scratch in 10.5.1 so the cache has not been used in any other ArcGIS version than 10.5.1.
I would also suggest building the Raster Mosaic Dataset from scratch as well to see if that addresses your issues.