Globe cache creation based on feature boundaries

An effective caching strategy for building globe caches is to precreate tiles for heavily visited areas of your map and create tiles on demand for rarely visited areas. You can use the Update specific areas using a feature class option to create tiles that only cover the features of a feature class. For example, if you are caching a country, you might supply a feature class of major urban areas. By doing so, you are requesting that the server only precreate tiles that cover those urban areas. The rest of the areas can be cached on demand when requested by clients. This can save you time and disk space that would be consumed by creating unneeded tiles in rural areas.

When you use this option, you can choose to have the tool track the status of each feature. If you choose to enable the status tracking, a Cached field is added to the feature class against which you are caching. When tiles have been created for the extent of a feature, that feature's Cached field is marked Yes.

If you run the tool to Update specific areas using a feature class again on the same feature class, the tool only creates tiles for records whose Cached field has not been marked Yes. If you do not want this to happen, you must either remove the Cached field, change its values to something other than Yes, or uncheck the option that enables status tracking.


Avoid feature classes with numerous small features, such as parcel boundaries or building footprints, when updating based on a feature class. It may be helpful to create a more generalized feature class to use specifically with this option. For example, if you want to update areas where buildings exist, instead of using the building footprints feature class, you might be able to create a feature class with a few large polygon features covering the general areas where the buildings can be found.