I would like to create an image service with a cache. I have created a raster mosaic which consist of images with various resolution (ground sample distance). I know how to publish the service an create the cache but I am not sure how to optimize my service.
Here is a practical example. At the image below there is a blue zone, that is the area which I want to publish an image service for. The GSD for the whole blue zone is 50 cm. However within that area there are some other zones, in this case zone 2 and 3 where I have an additional images with resolution of 10 cm. I want a user to be able to zoom to the greatest detail possible.
Option 1:
So I will set the service to be cached to the actual resolution of images with 10 cm GSD. This will work fine, but the problem is that the whole blue area will be cached to GSD of 10cm even though the actual resolution for the most of the area is 50 cm. This will result in unnecessary big cache size and if the area is big enough, then the cache size can be easily 100 times greater than necessary.
Option 2:
I can create 2 image services. One for the high resolution imagery and other for low resolution imagery. However, when user request the tiles from the services and the map extent is located in the area of high resolution imagery, the tiles from both image services will be sent to the user from the server. The high resolution will overlap the low resolution image, but this will increase the response time, as two sets of tiles have to be downloaded.
So I wonder, what is the best practice to solving this dilema?
Thank you.
Martin