Globe caching based on feature boundaries
In this topic
The Manage Globe Server Cache Tiles tool allows you to spatially constrain tile creation to the boundaries of a feature class. To do this, use the Area of interest parameter at the bottom of the Manage Globe Server Cache Tiles tool. This parameter allows you to browse to the feature class.
Note:
If you're running the tool in ArcMap or ArcGlobe, you also have the option to sketch an area of interest on the screen. This is helpful for onetime runs of the tool where you are trying to patch up a cache or ensure coverage in a given area. However, for most structured caching jobs or updates, it's recommended that you supply a feature class.
Tracking the status of your cache
Caching by feature class not only saves you space but also helps you track the status of your cache. You can use the Manage Globe Server Cache Tiles tool to mark which features have had tiles created over their areas. If you choose to use 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 again with the same feature class supplied for the Area of interest parameter, the tool creates tiles only for records whose Cached field has not been marked Yes. This can be helpful if your previous caching job was interrupted and is usually faster than choosing the Recreate Empty Tiles option (which checks every tile in the cache). If you do not want the tool to start where it left off, you must either remove the Cached field, change its value to something other than Yes, or check the box to ignore status tracking.
Tip:
Enabling status tracking allows you to recover from failed caching jobs much faster than using the Recreate Empty Tiles option.
Best practices
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.