john.c.cartwright

combining cached and dynamic versions of mapservice

Discussion created by john.c.cartwright on May 8, 2010
Latest reply on Aug 9, 2011 by a.schaefer-esri-de-esridist
Hello All,

Probably not strictly a JS API topic, but I'm seeking advice on the best way to handle a particular situation.  We often have a mapservice that is cached down to a particular level and below that level want to use a dynamic version of the mapservice. 

Currently I accommodate this by creating two mapservices using the same mxd and loading them both into the Map - one as a ArcGISDynamicMapServiceLayer and one as a ArcGISTiledMapServiceLayer.  Then, using the JS API, toggle the visibility depending on the zoom level so that only one is ever visible.

This works but seems rather clumsy and requires that I have two mapservices instantiated for each mxd.  I'd hoped that I could simply use the cached mapservice in a ArcGISDynamicMapServiceLayer, but that still doesn't display once I've zoomed in beyond the limits of the cache. I don't want to enable dynamic tile creation to populate the higher zoom levels - both out of performance concerns and control of disk space.

Can anyone suggest an alternative to the approach I'm currently using?  Ideally, I'd like the ArcGISTiledMapServiceLayer to have the option of switching to dynamically generate images once the limits of the cache have been passed.

Thanks!

--john

Outcomes