Cached Image Service behaving dynamically in basemap gallery

[BillDaigle]

I am attempting to load a cached Image Service into a basemap gallery.  The image service does work, but it is behaving like a dynamic image service, not a cached one.  By that, I mean that it is running a export image request each time the map pans instead of fetching the pregenerated tiles.

Here is a link to the service: https://gisservicemt.gov/arcgis/rest/services/MSL/Reference100k_cached/ImageServer

Here is the link to a jsFiddle demonstrating a basemap gallery with one tiled map service and one tiled image service.

https://jsfiddle.net/bdaigle/22Lgp45f/

If you watch the network traffic, you will see that the two basemaps handle the request very differently -- the tiled map service fetches map tiles, whereas the tile image service runs an exportImage task.

The service does behave like a cached service if I explicitly define it as a ArcGISTiledMapServiceLayer and load it to the map manually (without the use of the Basemap Gallery), so I believe this is an issue with the BasemapGallery itself.

I have a couple of ideas for work arounds, but thought I would check with the community before going down that road.

Any ideas???

[BillDaigle]

I'm working in firefox with firebug, but the network tab in Chrome will give you similar results.

Here is what the calls look when the layer is loaded to the basemapGallery.

Here is what they look like when they are loaded as a regular Tiled Layer:

[MichaelVolz]

This is supposed to be a tiled mapservice but it looks more like your image service return.

Can you tell me if this returning the correct object for a tiled mapservice?

[BillDaigle]

That looks like a dynamic map service request to me as well.  Here is how they should behave:

• Dynamic map service: When you pan the map, you should see a single map service request for the current map extent
• Tile map service:  When you pan the map, you should see zero or more tiles fetched for the given extent.  If you already have the tiles cached locally, zero tiles will be returned.  If not, one or more tiles will get returned.

[MichaelVolz]

Based on your network traffic examples I would agree that it is behaving like a dynamic mapservice, but the performance of the imagery in javascript applications and the javascript viewer made me think it was working as expected like a tiled mapservice as the panning and zooming of the imagery was near instantaneous.

[Anonymous User]

I'm also running into this. I published an ImagerServer service and tiled and it works great.. except then I noticed what you all have, that the Esri Basemap widget incorrectly requests it as dynamic. And that while this has apparently been assigned a Bug, they have determined they will not be fixing this. (I called Support who verified that it will not be fixed)

So the workaround as Robert Scheitlin, GISP​ has identified is to publish Dynamic and link it to the Cache. I think I have run into another bug. We have 10.2.2  but we have not installed this patch (Yet) ArcGIS 10.2.2 for Server Map Cache Consumption Patch  Hm. I am currently still trying to get my dynamic map service to behave and to show tiles, they keep giving a 404. I think it's just a matter of getting some directory pathing and/or permissions set up right and I feel like I"m getting close... Will update here, when done.